Pim wg multicast YANG team Meeting 20150520. Interface Hierarchy (Option 1) +--rw routing +--rw routing-instance* [name] +--rw routing-protocols +--rw.

Slides:



Advertisements
Similar presentations
Release 5.1, Revision 0 Copyright © 2001, Juniper Networks, Inc. Advanced Juniper Networks Routing Module 9: Static Routes & Routing Table Groups.
Advertisements

YANG Data Model for VRRP draft-liu-rtgwg-yang-vrrp-02
YANG Data Models for TE and RSVP Tunnels and Interfaces draft-saad-teas-yang-te-00 draft-saad-teas-yang-rsvp-00 Tarek Saad (Presenter) and Rakesh Gandhi,
IETF YANG routing models VRF centric vs Protocol centric.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 Diffserv Yang Model
UKERNA IP Multicast Mini Workshop Intra-domain Multicast Hands-on Lab Exercises Networkshop 2006.
IETF 90 Toronto Yang Data Model for OSPF Protocol draft-yeung-netmod-ospf-01 and beyond Derek Yeung Derek Yeung Dean Bogdanovic
Pim wg multicast YANG team Meeting Graceful Restart Config module: ietf-pim-base augment /rt:routing/rt:routing-instance/rt:routing-protocols:
Members: Acee Lindem, Anees Shaikh, Christian Hopps, Dean Bogdanovic, Lou Berger, Qin Wu, Rob Shakir, Stephane Litkowski, Yan Gang Wiki:
MPLS YANG Data Models IETF91 Submitted I-Ds: draft-chen-mpls-ldp-yang-cfg X. Chen, and Z. Li draft-chen-mpls-te-yang-cfg X. Chen, Z. Li, and X. Zeng draft-gandhi-mpls-te-yang-model.
IETF 92 Dallas, TX Yang Data Model for OSPF Protocol draft-ietf-ospf-yang-00 Yingzhen Qu Derek Yeung YingZhen Qu
Pim wg multicast YANG team Meeting
Pim wg multicast YANG team Meeting
Pim wg multicast YANG team Meeting Interface Hierarchy augment /rt:routing/rt:routing-instance/rt:routing-protocols: +--rw pim +--rw graceful-restart.
draft-ietf-teas-yang-te-topo-04
IETF 95 – Buenos Aires April 2016 A YANG Data Model for MPLS Base and Static LSPs (draft-saad-mpls-static-yang-02) Tarek Saad(Cisco) -- Presenter Kamran.
PIM YANG Model draft-liu-pim-yang-00 Yisong Liu, Feng Guo (Huawei) IETF 91, Honolulu.
BGP. BGP Configuration Create Fabric ASN Enable BGP on a given Tenant & VRF Create BGP Neighbor and associated config eBGP Vs iBGP Route Maps BGP over.
Network Device YANG Organizational Model draft-rtgyangdt-rtgwg-device-model-03 Authors: Acee Lindem, Christian Hopps, Dean Bogdanovic, Lou Berger (Ed.)
Draft-ietf-isis-yang-isis-cfg-01 IETF 91 S. Litkowski, Orange D. Yeung, Cisco A. Lindem, Cisco J. Zhang, Juniper L. Lhotka.
Pim wg multicast YANG team Meeting
Connectionless OAM yang model Deepak Kumar Qin WU Zitao Wang Reshad Rahman Srihari Raghavan 1IETF96, Berlin, Germany.
A use case for Schema Mount
Yang Data Model for Tunnel Policy draft-li-rtgwg-tunnel-policy-yang-00
YANG Data Model For RIB Extensions IETF 97, Seoul
YANG Data Model for RIP draft-liu-rtgwg-yang-rip-01
draft-ietf-teas-yang-te-topo-05
IETF 96 Berlin, Germany Key Chain Yang Data Model
draft-ietf-l3sm-l3vpn-service-model IETF 94 - Yokohama
draft-litkowski-isis-yang-isis-cfg IETF 90 - Toronto
pim wg multicast YANG team
Can SUPA Aid ECA Policy Development in I2RS Yang
Routing Area Yang Architecture Design Team Update
Multicast Information Model draft-zhang-mboned-multicast-info-model-00 Sandy. Zhang Linda Wang (Presenting) Mboned WG IETF 97#Seoul.
draft-ietf-teas-yang-te-topo-01
IETF 95 – Buenos Aires April 2016
pim wg multicast YANG team
L2VPN/EVPN/L3VPN Yang IETF-96 Berlin.
Routing Area Yang Architecture Design Team Update
Subscribing to YANG datastore push updates draft-ietf-netconf-yang-push-02 NETMOD WG IETF #95 Buenos Aires 4-April-2015 Alexander Clemm Alberto Gonzalez.
draft-ietf-teas-yang-te-topo-04
IGMP & MLD Snooping YANG Model
draft-ietf-pim-igmp-mld-yang-04
Comparison of NMDA datastores draft-ietf-netmod-nmda-diff-00
YANG Key-Chain Model IETF 97, Seoul
draft-ietf-rtgwg-ni-model-03 Impact on LxVPN device models
Interface extensions YANG & VLAN sub-interface YANG Status update
RIFT YANG draft-zhang-rift-yang-00
YANG Mount draft-clemm-netmod-mount IETF 98 Chicago, 30 March 2017
Routing Area Yang Architecture Design Team Update
IGMP & MLD Snooping YANG Model
draft-liu-netmod-yang-schedule-02
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-08 draft-ietf-teas-yang-rsvp-07 draft-ietf-teas-yang-rsvp-te-01
Updates to YANG Data Model for IEEE 1588v2
Yingzhen Qu YANG Data Model for OSPF Protocol draft-ietf-ospf-yang-08 draft-ietf-ospf-sr-yang-02 IETF99, Prague Derek Yeung
Routing Area Common YANG Data Types
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-06 draft-ietf-teas-yang-rsvp-07 draft-ietf-teas-yang-rsvp-te-00 draft-ietf-mpls-base-yang-04 code.
draft-ietf-teas-yang-te-topo-08
RFC4601 Implementation & Deployment Survey
LSR YANG Status IETF 101, London
draft-pim-with-ipv4-prefix-over-ipv6-nh
YANG Data Model for FlexE Interface Management
IETF Prague BFD Unsolicited
draft-ietf-teas-yang-l3-te-topo-04
draft-gulrajani-pim-hello-intid-00
draft-ietf-teas-yang-l3-te-topo-02
QoS Yang Model Aseem Choudhary, Norm Strahle, Ing-Whar Chen,
RIFT YANG draft-zhang-rift-yang-01
Microwave Model <next>
Interface extensions YANG & VLAN sub-interface YANG Status update
Presentation transcript:

pim wg multicast YANG team Meeting

Interface Hierarchy (Option 1) +--rw routing +--rw routing-instance* [name] +--rw routing-protocols +--rw pim +--rw address-family* [address-family] +--rw address-family enumeration +--rw pim-interfaces +--rw pim-interface* [if-name] +--rw if-name if-name +--rw hello-interval? uint32 +--rw dr-priority? uint32

Interface Hierarchy (Reference) augment /rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing- protocol: +--rw isis +--rw instance* [routing-instance] +--rw interfaces +--rw interface* [name] +--rw name if:interface-ref +--rw level-type? level +--rw af* [af] | +--rw af identityref | +--rw segment-routing {segment-routing}? | | +--rw prefix-sid* [value] | | +--rw value-type? enumeration | | +--rw value uint32 | | +--rw node-flag? boolean | | +--rw last-hop-behavior? enumeration | +--rw bfd {bfd}? | +--rw enabled? boolean Similar to isis (shown below). An ISIS interface can support any AF.

Interface Hierarchy (Reference) module: ietf-ospf augment /rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing- protocol: +--rw ospf +--rw instance* [routing-instance af] +--rw routing-instance rt:routing-instance-ref +--rw af identityref +--rw area* [area-id] | +--rw area-id area-id-type | +--rw interface* [interface] | +--rw interface if:interface-ref | +--rw network-type? enumeration | +--rw passive? boolean OSPF as reference An OSPF interface can support only one AF.

Interface Hierarchy (Option 2) +--rw routing +--rw routing-instance* [name] +--rw routing-protocols +--rw pim +--rw pim-interfaces +--rw pim-interface* [if-name] +--rw if-name if-name +--rw hello-interval? uint32 +--rw dr-priority? Uint32 +--rw address-family* [address-family] +--rw address-family enumeration

PIM Model Structure Consensus from last meeting: Base PIM model, common to all pim PIM SM – Yes, includes SSM PIM DM – Yes Proposed YANG modules: ietf-pim-base.yang +-- ietf-pim-sm.yang +-- ietf-pim-dm.yang

Model Structure Tree augment /rt:routing/rt:routing-instance/rt:routing-protocols: +--rw pim +--rw graceful-restart {graceful-restart}? +--rw address-family* [address-family] +--rw address-family identityref +--rw interfaces | +--rw interface* [interface] | +--rw interface if:interface-ref | +--rw dr-priority? uint32 | +--rw hello-interval? uint16 | +--rw pim-sm:sm! | +--rw pim-sm:passive? empty +--rw pim-sm:sm | +--rw pim-sm:anycast-rp! | +--rw pim-sm:static-rp | +--rw pim-sm:ssm! | +--rw pim-sm:range-poligy? string +--rw pim-dm:dm

Where PIM should be Option 1: module: ietf-pim-base augment /rt:routing/rt:routing-instance/rt:routing-protocols: +--rw pim Option 2: module: ietf-pim-base augment /rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing- protocol: +--rw pim Option 3: module: ietf-pim-base augment /rt:routing/rt:routing-instance: +--rw pim

SM Model Structure (1/2) augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family: +--rw sm +--rw anycast-rp! | +--rw ipv4 | | +--rw anycast-addr inet:ipv4-address | | +--rw rp-addr inet:ipv4-address | +--rw ipv6 | +--rw anycast-addr inet:ipv6-address | +--rw rp-addr inet:ipv6-address +--rw static-rp | +--rw ipv4-addr? inet:ipv4-address | +--rw ipv6-addr? inet:ipv6-address | +--rw policy-name? string +--rw spt-switch +--rw bsr {bsr}? | +--rw bsr-candidate! | | +--rw interface if:interface-ref | | +--rw hash-mask-length uint8 | | +--rw priority uint8 | +--rw rp-candidate! | +--rw interface if:interface-ref | +--rw policy? string +--rw ssm! +--rw range-poligy? string

SM Model Structure (2/2) augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-base:interfaces/pim-base:interface: +--rw sm! +--rw passive? empty

DM Model Structure module: ietf-pim-dm augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family: +--rw dm augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family: +--ro dm

Interface Config Leaves pimInterfaceDRPriority pimInterfaceHelloInterval pimInterfaceTrigHelloInterval Probably not this one pimInterfaceHelloHoldtime pimInterfaceJoinPruneInterval pimInterfaceJoinPruneHoldtime pimInterfacePropagationDelay pimInterfaceOverrideInterval