SDN/NFV YANG 2015/11/9 ( ) tochio<at>jp.fujitsu.com
: Writable MIB Module IESG Statement https://www.ietf.org/iesg/statement/writable-mib-module.html March 2, 2014 The IESG is aware of discussions in the OPS area and in a number of working groups about the current practice for standards-based approaches to configuration. The OPS area has shown strong support for the use of NETCONF/YANG while many working groups continue to specify MIB modules for this purpose. The IESG wishes to clarify this situation with this statement: IETF working groups are therefore encouraged to use the NETCONF/YANG standards for configuration, especially in new charters. SNMP MIB modules creating and modifying configuration state should only be produced by working groups in cases of clear utility and consensus to use SNMP write operations for configuration, and in consultation with the OPS ADs/MIB doctors. 2
SDN NETCONF/YANG RFC 7426 Open Daylight https://wiki.opendaylight.org/view/opendaylight_controller:md-sal:md-sal_document_review:md_sal? (L0, 3
IETF YANG IETF 94 ( ) YANG Device model OAM Topology IETF Information model ITU-T/ONF ITU-T ONF - Information model 4
Information Model/Data Model Information model (IM) Data model (DM) RFC 3444 On the Difference between Information Models and Data Models IM DM specify relationships between objects model managed objects at a conceptual level, independent of any specific implementations or protocols used to transport the data. define managed objects at a lower level of abstraction. They include implementation- and protocol-specific details, e.g. rules that explain how to map managed objects onto lower-level protocol constructs. DM IETF YANG IM SDO IM --> conceptual/abstract model for designers and operators +----------+---------+ DM DM DM --> concrete/detailed model for implementors 5
) IETF NETCONF/YANG Data Model (DM) SNMP MIB NETCONF/YANG IESG YANG NETCONF NETCONF WG YANG NETMOD WG YANG (MPLS, Routing, OAM) WG MPLS, RTGWG, TEAS, CCAMP, Routing Area YANG IM WG DM? ITU-T/ONF ITU-T SG15 NE(Network Equipment) NE : Q10, Q11 / NE Q14 Information model (IM) ONF IM ONF OF-config NETCONF ONF Transport API IM 6
) IEEE 802.1 MIB SNMP (IETF) YANG module IEEE802.1Q(MAC), IEEE802.1X(Sec) IEEE802.1Q IEEE802.3 (PHY) IETF (Design Team ) MEF MEF OAM YANG module (MEF38, 39) MEF6.2 YANG Information model MEF 7.2 TMF, ITU-T TMF ITU-T/ONF Network Function, Network Resource IM Service Management model IETF SUPA WG 7
YANG YANG (RFC 6020) NETMOD WG Data modeling language RFC6087 NETCONF API NETCONF XML YANG (Data modeling ) Leaf Nodes Leaf-List Nodes Container Nodes List Nodes 1 list Leaf Configuration data State Data Tree (RFC 6087bis) pyang code.google.com/p/pyang 8
[NETMOD] YANG NETMOD WG YANG1.1(rfc6020bis) Issue list - http://svn.tools.ietf.org/svn/wg/netmod/yang-1.1/issues.html YANG to JSON 1.1 1.0 I2RS Routing, ACL, DiffServ YANG draft-ietf-netmod-routing-cfg, draft-bogdanovic-netmod-acl-model, draft-asechoud-netmod-diffserv-model DIffServ QoS YANG Interface (RFC 7277) L2 draft-wilton-netmod-intf-ext-yang-00, draft-wilton-netmod-intf-vlan-yang-00 draft-bogdanovic-netmod-yang-model-classification NE YANG, Service YANG YANG / model Operational State Data draft-openconfig-netmod-opstate NETCONF configuration / operational state data State UML (Info model) YANG (Data model) [ ] 9
YANG in RTG Area YANG IETF RTG (Routing Area) WG YANG WG MPLS MPLS WG RSVP-TE TEAS WG RTG Area Wiki, ML http://trac.tools.ietf.org/area/rtg/trac/wiki/rtgyangcoord rtg-yang-coord@ietf.org RTG (& OPS) ( ) Core Routing (Generic) draft-ietf-netmod-routing-cfg (NETMOD and RTGWG) OSPF, ISIS, BGP Specific WG Topology (Physical, Logical) draft-rtgyangdt-rtgwg-device-model draft-ietf-yang-abstract-te-topo (TEAS) draft-ietf-i2rs-yang-network-topo (I2RS) OAM draft-ietf-lime-yang-oam-model (LIME (OPSArea)) MPLS, BFD WG OAM LIME WG 10
YANG Device model (-00, IETF93) draft-rtgyangdt-rtgwg-device-model Design Team YANG draft-openconfig-netmod-model-structure Device (Physical or VM) Root Interface (RFC 7223) +--rw device +--rw info +--rw device-type? enumeration +--rw hardware +--rw interfaces +--rw interface* [name]... +--rw qos +--rw logical-network-elements Logical-network-elements ( ) networking instance (VRF/VSI) networking instance OAM, Control plane, policy +--rw device +--rw logical-network-elements +--rw logical-network-element* [network-element-id] +--rw network-element-id uint8 +--rw network-element-name? string +--rw default-networking-instance-name? string +--rw system-management... +--rw ietf-acl +--rw ietf-key-chain +--rw networking-instances... 11
YANG Device model (-01, IETF94) ( https://www.ietf.org/proceedings/94/slides/slides-94-netmod-7.pdf ) Top Level Device Network Device (Module) Interface augment Logical Network element Network instance Logical Network Element: Sub LNE, System management DT 12
OAM for YANG [LIME] Layer Independent OAM Management in the Multi-Layer Environment 91 ( ) OPS Area WG OAM generic (layer independent) Data model (YANG) OAM (IM ) OAM (Operations, Administration, and Maintenance) IP BFD LSP ping, ippm, ( ) draft-ietf-lime-yang-oam-model draft-wang-lime-yang-pm draft-wang-lime-rpc-yang-oam-management draft-zhuang-lime-yang-oam-model-applicability draft-txh-lime-gap-analysis draft-lam-lime-summary-l0-l2-layer-independent Layer independent L0-L2 L3 generic IP, MPLS IM DM L0 -L2 (@ITU-T, ONF) WG OAM Framework YANG (NVO3, SFC, TRILL, MPLS) YANG Ethernet (IEEE, MEF) Notification ( ) 13
Generic OAM YANG [YANG] draft-ietf-lime-yang-oam-model Overview Ietf-gen-oam module : : rpc (Remote Procedure Call) (MEP augment) Notification module: ietf-gen-oam +--rw domains +--rw domain* [technology MD-name-string] +--rw technology identityref +--rw MD-name-string MD-name-string +--rw MD-name-format? identityref +--rw (MD-name)? +--:(MD-name-null) +--rw MD-name-null? empty +--rw md-level? MD-level +--rw MAs +--rw MA* [MA-name-string] : +--rw MEP* [mep-name] +--rw mep-name MEP-name +--rw (MEP-ID)? : : +--rw priority? uint8 +--rw session* [session-cookie] : : : +--rw MIP* [interface] +--rw interface if:interface-ref +--rw related-oam-layer* [offset] rpcs: +---x continuity-check +--ro input : : : +--ro output +---x continuity-verification +--ro input : : : +--ro output : : +---x path-discovery +--ro input : : : +--ro output : : +---x Loss-measurement (to added?) : : +---x delay-measurement (to added?) : : notifications: +---n defect-condition-notification +--ro technology +--ro MD-name-string +--ro MA-name-string? +--ro mep-name? +--ro defect-type? +--ro generating-mepid : +--ro (error)? +--:(error-null) +--ro error-null? +--:(error-code) +--ro error-code? +--ro error-code? 14
Topology YANG [TEAS] TEAS WG: IETF 92 CCAMP TE draft-ietf-teas-yang-te-topo Technology Agonistic TE Topology YANG Topology Root Node, -link, TE matrix ( TE Topology as a Service : ) : Overlay/Underlay module: ietf-te-topology +--rw te-topologies +--rw topology* [te-topology-id +--rw node* [te-node-id] +--rw te-node-id te-node-id +--rw te-node-template? leafref +--rw te-node-attributes +--rw schedules* [schedule-id]... +--rw underlay-topology? leafref {tetopology-hierarchy}? +--rw te-link* [te-link-id] +--rw te-link-id te-link-id... +--rw connectivity-matrix* [id] +--rw id uint32 +--rw from-link... +--rw to-link... +--rw ted :... +--rw node-template* [name]... +--rw te-node-attributes +--rw underlay-topology? leafref {tetopology-hierarchy}? +--rw link-template* [name] +--ro te-topologies-state +--ro topology* [te-topology-id] +--ro node* [te-node-id] +--ro te-node-attributes +--ro underlay-topology? leafref {te- topology-hierarchy}? configuration data operational state data : +--ro link* [source-te-node-id source-te-link-id dest-te-node-id dest-te-link-id] +--ro is-abstract? boolean +--ro underlay! {te-topology-hierarchy}? 15
Topology YANG [I2RS] I2RS WG: Application - Routing RIB Topology IM/DM draft-medved-i2rs-topology-im (Expired) draft-ietf-i2rs-yang-network-topo module: network-topology +--rw network-topology +--rw topology [topology-id] +--rw topology-id topology-id +--ro server-provided? boolean +--rw topology-types +--rw underlay-topology [topology-ref] +--rw topology-ref topology-ref +--rw node [node-id] +--rw node-id node-id +--rw supporting-node [node-ref] +--rw node-ref node-ref +--rw termination-point [tp-id] +--rw tp-id tp-id +--ro tp-ref* tp-ref +--rw link [link-id] 16 +--rw link-id link-id +--rw source +--rw source-node node-ref +--rw source-tp? tp-ref +--rw destination +--rw dest-node node-ref +--rw dest-tp? tp-ref +--rw supporting-link [link-ref] +--rw link-ref link-ref
Topology YANG: TEAS and I2RS (IETF93) I2RS draft-ietf-i2rs-yang-network-topo draft-clemm-i2rs-yang-l3-topo draft-ietf-i2rs-l2-network-topology draft-hares-i2rs-info-model-service-topo draft-wang-i2rs-yang-service-topo-dm draft-zhang-i2rs-l1-topo-yang-model-01 TEAS (draft-ietf-teas-yang-te-topo), I2RS I2RS Service Topology TEAS TE Topology TE Topology model I2RS Topology model augment ( I2RS ) L1(/L0) Topology (I2RS) TE Topology Model augment CCAMP L2, L3 Topologies TE Topology Model augment L2 Router (L3) (L0 -L2) topology? 17
YAMG (DM) IM IETF (TEAS NETMOD ) 18
IM [TEAS] draft-lam-teas-usage-info-model-net-topology ITU-T/ONF Core information model I-D ITU-T G.7711 Generic protocol-neutral information model for transport resources ONF TR-512 Core information model ONF Topology IM Topology YAMG (draft-liu-teas-yang-te-topo-00) YANG - https://www.ietf.org/proceedings/94/slides/slides-94-teas-6.pdf 19
IM [NETMOD] draft-mansfield-netmod-uml-to-yang Guidelines for Translation of UML Information Model to YANG Data Model ONF IM(UML) DM(YANG) I-D (Informational RFC ) 20
ITU-T/ONF 21
ITU-T, ONF IM ( ) ITU-T ONF ITU-T SG15 NE(Network Equipment) NE : Q10(Packet(L2)), Q11 (OTN(L1), WDM(L0)) / NE Q14 Q14 Information model (IM) G.874.1 (OTN(WDM )), G.8052 (Ethernet), draft G.8152 (MPLS) Area, Project https://www.opennetworking.org/technical-communities Services Area > Information Modeling Project (IMP) Generic (Protocol neutral) IM Specification Area > Open Transport project ( Optical TransportWG) (L0, L1, L2) OpenFlow SDN Information Model Transport API (TAPI) IM OTN, Ethernet, MPLS IM TAPI ITU-T ONF ONF IPR A.5 Justification NG 22
G.7711 (G.gim) & ONF TR-512 + 513 Generic Protocol-Neutral Information model for transport resources G.7711 (ITU-T G.874.1, G.8052, G.8152) scope ONF Network Equipment Network Resource (Element) 2014 ONF IMP (Information model project) G.7711 TR512: Core Information Model (CIM) + UML TR-512 G.7711 / (by ) G.7711 2015/08 (http://www.itu.int/rec/t-rec-g.7711) G.7711 Scope TR-513: CIM overview ONF/ITU-T TR-514: UML Modeling Guideline Common Information model (Technology specific) Data Schema (i.e. YANG) Figure 1-1/G.7711( ) 23 Figure 1-2/G.7711 or Figure1-1/TR-512
TR514: UML Modeling Guidelines 1.0 Figure 4.1: ONF Specification Architecture 24
G.7711 (G.gim) & ONF TR-512 LTP, LP G.874.1 ( G.852.2) CTP TTP CTP, TTP LTP (LogicalTerminationPoint), LP (LayerProtocol) Object class Layer examples LR x = MS LR y = VC4 (flexible) LR z = 140 (flexible) LR z Expanded G.805 Representation CP CP = Connection Point AP = Access Point TCP =Termination Connection Point TTP = Trail Termination Point CTP = Connection Termination Point PTP = Physical Termination Point LT = Layer Termination TPE = Termination Point Encapsulation Rationalized Representation (G.805 / G.800 terms) CP Layered parameter list ITU-T used to capture TMF entities ONF per-layer detail LT Per-layer detail captured in LT n TPE LP n LTP AP AP LR y TCP TCP CP Semi -flexible SNC / FR ITU TTP ITU CTP TMF CTP LT n TPE LP n LTP AP AP LR x TCP TCP CP Fixed (degenerate) SNC / FR LT TPE LP LTP AP TCP LR w AP TCP TMF PTP LT LP ITU-T G.774 TTP /CTP LT = LayerTermination TPE = Termination Point Encapsulation 25
G.7711 (G.gim) & ONF TR-512 Core Model 2 TR225 Logical Resource: Network Function Model ITU-T G.874.1, G.8052, draftg.8152 (OTN, Ethernet, MPLS-TP) LTP, LP ( ) SNC (SubNetworkConnection), SN (SubNetwork) FD (ForwardingDomain), FC (ForwardingConstruct) Connection Flow UML Papyrus (Eclipse ) 26 Controller for NE Network Resource Linear Protection
G.7711 & ONF TR-512 FD, Link TopologicalEntity (Topology Subset) Termination (LTP) Subset OAM (MEP, MIP, Jo class) G.8052 MEP (source/sink) class (MEP Refactoring) ONF UML YANG mapping guideline TR draft-mansfield-netmod-uml-to-yang 27
28
NETCONF/YANG / Interface ( ) WDM draft-dharininetmod-g-692-2dwdm-if-yang Data plane (L0-L2) NETCONF/YANG Data plane {G.874.1/G.8052/draft G.8152} (or ONF OT IM) UML YANG NETCONF/YANG Figure 1-2/G.7711 or Figure1-1/TR-512 29
https://datatracker.ietf.org/liaison/1433/ LS: ITU-T Q14/15 NETMOD, CCAMP, TEAS, MPLS LS on protocol-specific data modelling work We would like to inform you that ITU-T Q14/15 has initiated work on protocol-specific data modelling for the management of transport specific technologies, such as OTN, Carrier Ethernet and MPLS-TP. These protocol-specific data models will be developed based on the protocol-neutral UML models that are specified by Q14/15, including ITU-T G.7711/Y.1702 (generic information model), ITU-T G.874.1 for OTN, ITU-T G.8052/Y.1346 for Carrier Ethernet, and ITU-T G.8152/Y.1375 (draft) for MPLS-TP. During the October 2015 Q14/15 interim meeting, we received a contribution for a YANG data model proposal for Ethernet Ring Protection (ERP) management. < > 30
: draft-dharini-netmod-g-692-2dwdm-if-yang UML YAMG draft-mansfield-netmod-uml-to-yang (pdf) ITU-T YANG (Fig 21 & 22) Figure 12-8 & 10/G.798 Figure 7-4/G.874.1( ) UML(Fig 23) 31
( ) IETF (YANG) L2 (Ethernet) IEEE, MEF, ITU-T ( ) IEEE YANG ( ) Service ( MEF) OAM Protection ( ITU-T) RFC 6244 Notification (Netconf) draft-ietf-lime-yang-oam-model +----------------------------+ Server (device) +--------------------+ configuration +----+ --------------- YANG + m d state data mods + e a --------------- +----+ -----> t t notifications +----+ a a --------------- +----+ operations +--------------------+ ^ v +------+ +-------------+ -------------> Client <rpc> NETCONF (app) engine <------------ +------+ <rpc-reply> +-------------+ / / / +--------+ +---------+ config system + data- software + base component +--------+ +---------+ +---------+ configuration / operational state data +---------+ +----------------------------+ RFC 5277, RFC 6470 32
SDN/NFV IM) IETF YANG ITU-T/ONF IM L2) Data Model (YANG, JSON) Information Model Data plane, Network Architeture ( 33
34