isoc-jp IETF93 (RTG and OPS)

Size: px

Start display at page:

Download "isoc-jp IETF93 (RTG and OPS)"

もえりたかはし
7 years ago
Views:

1 IETF 94 ( ) RTG, OPS (YANG ) 2015/12/8 ( )

2 (IETF92, IETF93) RTG OPA Data model (YANG) WG OPS Area: NETMOD, SUPA, L3SM, LIME RTG Area: RTGWG, TEAS, BESS (or PALS), I2RS Overview PCE, TEAS Bonus Tracks ( ) %5Fietf92%5Frtg%2Epdf date%5f10%5ftochio%2epdf&page=ietf93update 2

3 (1) DATA MODEL (YANG) 3

Information Model/Data Model Information model (IM) Data model (DM) RFC 3444 On the Difference between Information Models and Data Models IM Conceptual/Abstract model specify relationships between

4 Information Model/Data Model Information model (IM) Data model (DM) RFC 3444 On the Difference between Information Models and Data Models IM Conceptual/Abstract model specify relationships between objects model managed objects at a conceptual level, independent of any specific implementations or protocols used to transport the data. DM Concrete/Detailed model define managed objects at a lower level of abstraction. They include implementationand protocol-specific details, e.g. rules that explain how to map managed objects onto lower-level protocol constructs. DM IETF YANG IEEE, MEF model IM IM WG: I2RS (RIB info model ) IM (UML) SDO: ITU-T, ONF, TMF, MEF draft-lam-teas-usage-info-model-net-topology draft-betts-netmod-framework-data-schema-uml draft-mansfield-netmod-uml-to-yang # IM MPLS Japan 2015 J 4

5 [NETMOD] YANG YANG (RFC 6020) 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 IETF 94 (2015/12/8) 5

6 YANG Tutorial in Yokohama YANG Tutorial NETCONF (RFC6241) ( ) YANG (Router IF ) PYANG Tutorial YANG Doctors ( ) Videos on Youtube: - YANG by Example: - NETCONF by Example: - PYANG: Slides NETCONF & YANG: PYANG(@IETF90): 6

7 YANG in RTG Area YANG (RFC 6020) Data model IETF RTG WG YANG RTG Area Wiki, ML RTG ( ) Core Routing (Generic) draft-ietf-netmod-routing-cfg (NETMOD and RTGWG) OSPF, ISIS, BGP Specific WG Topology OAM draft-liu-yang-abstract-te-topo (TEAS) or draft-clemm-i2rs-yang-network-topo (I2RS) I2RS L1, L2, L3 topo draft-tissa-lime-yang-oam-model (LIME (OPSArea)) MPLS, BFD WG Overlap NVO3, SFC(, TRILL) VPN 7

8 YANG in RTG Area RTG Area NETMOD IETF YANG Models Inventory, status and observation : Routing 8

9 YANG in RTG Area RTG Area NETMOD ( ) IETF YANG Models Inventory, status and observation Routing Interrelation between YANG Models OAM, Topology, TE Missing parts Tunnel. TE Tunnel (MPLS vs IP ) QoS. draft-asechoud-netmod-diffserv-model Interrelation Layer draft-bogdanovicietf-netmod-yang-model-classification Network Elements Network Service OSS/BSS Network Service YANG data models VPWS - VPLS L3VPN - L2VPN - L2VPN Network Element YANG data models MPLS BGP IPv4 & IPv6 Ethernet

10 YANG Device model (-00, IETF93) draft-rtgyangdt-rtgwg-device-model Design Team YANG NETMOD 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... 10

YANG Device model (-01, IETF94) ( https://www.ietf.

pdf ) Top Level Device Network Device (Module) Interface augment

11 YANG Device model (-01, IETF94) ( ) Top Level Device Network Device (Module) Interface augment Logical Network element Network instance Logical Network Element: Sub LNE, System management DT 11

12 YANG Model in NETMOD IETF 94 Operational State Data draft-openconfig-netmod-opstate & kwatsen-netmod-opstate, wilton-netmod-opstate-yang Configuration data Operational State data YANG Conf call > draft-ietf-netmod-opstate-reqs 3 Interface (RFC 7277) L2 draft-wilton-netmod-intf-ext-yang draft-wilton-netmod-intf-vlan-yang L2 IEEE802.1Q YANG Physical Entity Model draft-entitydt-netmod-entity-00 ( ) YANG model, RFC6933 Entity MIB v4 Physical Entity Catalog and registry for YANG models augment /if:interfaces/if:interface/if-cmn:encapsulation/ if-cmn:encaps-type: +--:(vlan) +--rw vlan +--rw tags +--rw tag* [index] module: ietf-entity +--rw index +--rw dot1q-tag +--rw tag-type +--rw vlan-id uint8 dot1q-tag-type dot1q-vlan-id +--ro entity-state +--ro last-change? yang:date-and-time +--ro physical-entity* [name] +--ro name string +--ro class? identityref +--ro physical-index? int32 {entity-mib}? +--ro description? string +--ro contained-in* ->../../physical-entity/name +--ro contains-child* ->../../physical-entity/name +--ro parent-rel-pos? int32 +--ro hardware-rev? string +--ro firmware-rev? string +--ro software-rev? string 12

YANG Model in NETMOD Catalog and registry for YANG models draft-openconfig-netmod-model-catalog-00 OpenConfig Registry, Catalog draft-openconfig-netmod-model-structure (Organization, Classification

13 YANG Model in NETMOD Catalog and registry for YANG models draft-openconfig-netmod-model-catalog-00 OpenConfig Registry, Catalog draft-openconfig-netmod-model-structure (Organization, Classification of Module, dependency ) Hackathon Cisco Demo +--rw organizations +--rw organization* [name] +--rw name string +--rw type? identityref +--rw contact? string +--rw modules +--rw module* [name] +--rw name +--rw namespace? +--rw prefix? +--rw revision? +--rw summary? +--rw module-version? +--rw module-hierarchy rw classification rw dependencies rw module-usage rw implementations... string string string string string string 13

14 YANG for VPN Services L2 BESS (+ PALS) WG L3 L3SM(, BESS) L2 VPN(VPLS, VPWS, EVPN) draft-shah-bess-l2vpn-yang (VPLS, VPWS) draft-brissette-bess-evpn-yang (EVPN) L3 VPN(BGP IP/MPLS VPN) draft-ietf-l3sm-l3vpn-service-mode ( ) draft-li-bess-l3vpn-yang (VPN ) L2VPN VPLS YANG L2VPN(VPLS, VPWS, EVPN ) YANG L3VPN L3SM BESS (MEF) ( MEF ) MEF Ethernet Service (E-Line, E-LAN) L3SM WG YANG ( ) draft-wang-l3sm-service-automation-architecture 14

15 SUPA Simplified Use of Policy Abstractions Policy 2 BoF OPS Area WG WG Charter Info Model Charter YANG (Data Model) IM Content / WG QoS YANG Value proposition (Problem statement), IM/DM, Use case Value: Vendor and Technology Independent Policy Framework Unified Network Infrastructure Policy Management Real-time and event-based Network Management New Independent Network Management Layer SUPA Generic Policy IETF Information Model / Assignments Defines Policy Concepts and Manage Preferred SUPA Generic Policy Approach YANG Data Models / * * * * A Possible * / Approach * * Technology and * Vendor-specific * Data Models */ Fills Forms Policy Interface / Operator (locally defined Runs / forms, scripts,...) Scripts Produces Policy Rules / Local SUPA SUPA Data Model- Local Devices Execution Specific Translation and Management Environment Functions / Systems

16 SUPA Model draft-chen-supa-eca-data-model-05 (ECA: Event-Condition-Action) Target Atomic Statement ECA policy rule Atomic TMF ZOON (Zero-touch Orchestration, Operations, and Management) draft-strassner-supa-generic-policy-info-model 16

17 : -T ITU 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 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. < > L0, L1, L2 UML (Info model) YANG (See draft-mansfield-netmod-uml-to-yang) 17

18 (2) 18

[PCE] Path Computation Element WG 2005 WG (G)MPLS (Routing controller Ingress LSR GMPLS (RFC 4655) PCE: PCC: (Client) LER PCEP: PCE-PCC (RFC 5440) TED: TE database PCE TED TED, LSP DB Stateful PCE

19 [PCE] Path Computation Element WG 2005 WG (G)MPLS (Routing controller Ingress LSR GMPLS (RFC 4655) PCE: PCC: (Client) LER PCEP: PCE-PCC (RFC 5440) TED: TE database PCE TED TED, LSP DB Stateful PCE PCE LER LSP ( ) PCE initiation PCC Request PCE Reply (PCE) TED < > TED synchronization mechanism (for example, routing protocol) v PCE ^ Request/ Response v Service Signaling Request Head-End Protocol Adjacent ----> Node < > Node Copyright 2010 FUJITSU LIMITED

PCRep, PCRpt PCE initiation (draft-ietf-pce-pceinitiated-lsp) PCC initiate (12) PCE WG MPLS, GMPLS SR(Segment

20 [PCE] PCEP RFC 5440 (, RFC5886) PCReq(3), PCRep(4) PCNtf(5), PCErr(6) Open(1), Keepalive(2), Close(7), Stateful PCE (draft-ietf-pce-statefulpce) RFC 5886 PCMonReq 8, PCMonRep(9) Active: PCRpt(10), PCUpd(11) Passive: PCReq, PCRep, PCRpt PCE initiation (draft-ietf-pce-pceinitiated-lsp) PCC initiate (12) PCE WG MPLS, GMPLS SR(Segment Routing), SR(+SFC(Service Changing Function)) PCE (PCEP ) TE PCE(P) YANG Module TED 20 Copyright 2015 FUJITSU LIMITED

PCE as Central Controller PCE (Path computation Element) SDN ( ) Stateful PCE (LSP DB PCE) initiation (PCE ) RFC 7491 A PCE-Based Architecture for Application-Based Network Operations PCE Central

21 PCE as Central Controller PCE (Path computation Element) SDN ( ) Stateful PCE (LSP DB PCE) initiation (PCE ) RFC 7491 A PCE-Based Architecture for Application-Based Network Operations PCE Central controller packet classification PCEP Scheduling or slides/slides-94-pce-3.pdf slides/slides-94-teas-12.pdf draft-zhuang-teas-scheduled-resources draft-zhao-pce-central-controller-user-cases ACTN/TEAS OSS / NMS / Application Service Coordinator : : : : : Policy+--+ ABNO Controller : : Agent +--+ OAM : : Handler : : : : : : ALTO +-+ VNTM --+ : : Server : : PCE I2RS : : Client : : : : : : Databases :----+ : : TED : : LSP-DB : : : : Provisioning Manager : : : / Client Network Layer / Server Network Layers

ACTN (TEAS) Abstraction and Control of Transport Networks BoF TEAS WG Virtual Network Control layer ( ) Data model BoF Charter The ACTN working group works to develop a high-level architecture that

22 ACTN (TEAS) Abstraction and Control of Transport Networks BoF TEAS WG Virtual Network Control layer ( ) Data model BoF Charter The ACTN working group works to develop a high-level architecture that describes the basic building-blocks necessary to enable the multi-domain virtual service coordination. It will identify key building components and the corresponding interfaces among these components. TEAS abstraction ACTN ACTN WG adaptation draft-ietf-teas-actn-requirements Framework YANG (?) 22

23 (Bonus tracks): RTG Area and IRTF RTG Area WG ( ) Wiki IRTF NML Machine learning( ) RG (IRTF) SDN ( ) Security SDN Automation NMRG, Anima (WG) post SDN? DetNet WG (Deterministic networking) L2, L3 Time sensitive IEEE802.1 ( TSN) TSN Scope Encapsulation, OAM, Control Plane BESS EVPN WG Last call ML VxLAN (RFC 7348) RTG area WG VxLAN(RFC 7348) BFD for VxLAN, BIER VxLAN, VxLAN path detection, YANG NVO3 independent stream RFC? 23

24 IETF 94 RTG OPS Data model (YANG) WG OPS Area: NETMOD, SUPA, L3SM, LIME RTG Area: RTGWG, TEAS, BESS (or PALS), I2RS Overview PCE, TEAS 24

25 25

MPLS Japan 2015

MPLS Japan 2015 SDN/NFV YANG 2015/11/9 ( ) tochiojp.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