Pim wg multicast YANG team Meeting 20151216 https://www.ietf.org/mailman/listinfo/yang-multicast https://github.com/mcallisterjp/pim-yang.

Slides:



Advertisements
Similar presentations
Presentation_ID © 2003, Cisco Systems, Inc. All rights reserved
Advertisements

Group-to-RP Mapping Algorithm PIM Working Group Bharat Joshi Infosys Technologies Ltd. draft-joshi-pim-group-rp-mapping-00.txt.
Draft-zhang-pim-multi-upstream-igmp-mld-proxy-01 Shuai Gao Beijing Jiaotong University HAW Hamburg Multi-Upstream Interfaces IGMP/MLD Proxy.
Xing Li CERNET NOC/TEIN2 NOC
YANG Data Model for VRRP draft-liu-rtgwg-yang-vrrp-02
IPv6 Multicast Δημήτριος Α Αδάμος ΑΠΘ - ΕΔΕΤ 107 NW’
IPv4-Embedded IPv6 Multicast Address draft-ietf-mboned-64-multicast-address-format IETF 84 Vancouver 1.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 Diffserv Yang Model
IPv6 Multicast 6DEPLOY. IPv6 Deployment and Support.
UKERNA IP Multicast Mini Workshop Intra-domain Multicast Hands-on Lab Exercises Networkshop 2006.
Multicast addresses for documentation purposes draft-venaas-mboned-mcaddrdoc-03.
Multrans Path Optimization draft-zhou-mboned-multrans-path-optimization-02 Cathy ZHOU Qiong SUN IETF 84, Vancouver.
IETF77 Multimob California1 Proposal for Tuning IGMPv3/MLDv2 Protocol Behavior in Wireless and Mobile networks draft-wu-multimob-igmp-mld-tuning-00 Qin.
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:
IETF 92 Dallas, TX Yang Data Model for OSPF Protocol draft-ietf-ospf-yang-00 Yingzhen Qu Derek Yeung YingZhen Qu
Issues In Multicast Transition For presentation to the Multrans BOF Tom Taylor Cathy Zhou.
Desired Behavior  This proposed mechanism provides a robust means of electing an RP from a subset of the domain’s PIM routers which are configured and.
6DEPLOY. IPv6 Deployment and Support
1 Behcet Sarikaya Frank Xia November 2010 NAT64 for DSMIPv6 IETF 79
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.
Pim wg multicast YANG team Meeting Interface Hierarchy (Option 1) +--rw routing +--rw routing-instance* [name] +--rw routing-protocols +--rw.
PIM YANG Model draft-liu-pim-yang-00 Yisong Liu, Feng Guo (Huawei) IETF 91, Honolulu.
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.
Agenda Problem Statement Solution Overview and Applicability
A use case for Schema Mount
YANG Data Model For RIB Extensions IETF 97, Seoul
Presentation_ID © 2003, Cisco Systems, Inc. All rights reserved
YANG Data Model for RIP draft-liu-rtgwg-yang-rip-01
draft-ietf-teas-yang-te-topo-05
Routing BY, P.B.SHANMATHI.
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.
(draft-archana-pimwg-pim-ping-00.txt)
Routing Area Yang Architecture Design Team Update
draft-ietf-teas-yang-te-topo-04
Summary Issued adoption call for draft-zhou-pim-vrrp.
IGMP & MLD Snooping YANG Model
draft-lts-pim-hello-mtu-01
draft-ietf-pim-igmp-mld-yang-04
YANG data model for Flexi-Grid Optical Networks
RIFT YANG draft-zhang-rift-yang-00
YANG Mount draft-clemm-netmod-mount IETF 98 Chicago, 30 March 2017
IGMP & MLD Snooping YANG Model
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
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-lee-rtgwg-actn-applicability-enhanced-vpn-03
Y. Lee, D. Dhody, X. Zhang, A. Guo (Huawei)
YANG Data Model for FlexE Interface Management
IETF Prague BFD Unsolicited
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-19 draft-ietf-teas-yang-rsvp-10 draft-ietf-teas-yang-rsvp-te-05 draft-ietf-teas-yang-te-mpls-01.
draft-ietf-teas-yang-l3-te-topo-02
YANG data model for Flexi-Grid Optical Networks
YANG Models for MPLS-TP
Deprecating ASM for Interdomain Multicast IETF 102 Montreal 2018
RIFT YANG draft-zhang-rift-yang-01
draft-ietf-pim-igmp-mld-yang-06
Presentation transcript:

pim wg multicast YANG team Meeting

df-election augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-bidir:address-family: +--ro rp augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-rp:rp: +--ro bidir +--ro df-election // | +--ro ipv4-source-address* [ipv4-addr interface] |... | +--ro ipv6-rp* [ipv6-rp-addr] | +--ro ipv6-rp-addr inet:ipv6-address // | +--ro active-groups?* inet:ipv6-address-prefix | +--ro df-election-interfaces* [interface-name] | +--ro interface-name string | +--ro interface-state? enum // {elected | backup | not} | +--ro df? inet:ipv6-address Alternative: +--ro ipv6-rp* [ipv6-rp-addr interface-name] | +--ro interface-name string | +--ro interface-state? enum // {elected | backup | not} | +--ro df? inet:ipv6-address

Interface DF State Type + typedef intf-df-state { + type enumeration { + enum "offer" { + description + "Initial election state.."; + } + enum "lose" { + description + "There either is a different election winner or that no + router on the link has a path to the RPA.."; + } + enum "win" { + description + "The router is the acting DF without any contest."; + } + enum "backoff" { + description + "The router is the acting DF but another router has made a + bid to take over.."; + } + description + "Interface DF election state type."; + reference + "RFC5015: Bidirectional Protocol Independent Multicast + (BIDIR-PIM)."; + } // intf-df-state

DF Election State +augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-rp:rp: + +--ro bidir + +--ro df-election + | +--ro ipv4-rp* [ipv4-addr] + | | +--ro ipv4-addr inet:ipv4-address + | +--ro ipv6-rp* [ipv6-addr] + | +--ro ipv6-addr inet:ipv6-address + +--ro interface-df-election + +--ro ipv4-rp* [ipv4-addr interface-name] + | +--ro ipv4-addr inet:ipv4-address + | +--ro interface-name if:interface-ref + | +--ro df-address? inet:ipv4-address + | +--ro interface-state? intf-df-state + +--ro ipv6-rp* [ipv6-addr interface-name] + +--ro ipv6-addr inet:ipv6-address + +--ro interface-name if:interface-ref + +--ro df-address? inet:ipv6-address + +--ro interface-state? intf-df-state

interace-df-election augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-bidir:address-family: +--ro interfaces augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:interfaces: ro interface-df-election +--ro interface* [interface-name] // Anish to check if we can get all the info. +--ro interace-name string +--ro offer-multiple uint8 +--ro offer-interval uint32 +--ro backoff-interval uint32 +--ro ipv4-source-address* [ipv4-addr interface] ro ipv6-rp* [ipv6-rp-addr] +--ro ipv6-rp-addr inet:ipv6-address +--ro interface-state? enum +--ro df? inet:ipv6-address

SM State 1/2 augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family: + +--ro asm + | +--ro anycast-rp! + | | +--ro ipv4 + | | | +--ro ipv4-anycast-rp* [anycast-addr rp-addr] + | | | +--ro anycast-addr inet:ipv4-address + | | | +--ro rp-addr inet:ipv4-address + | | +--ro ipv6 + | | +--ro ipv6-anycast-rip* [anycast-addr rp-addr] + | | +--ro anycast-addr inet:ipv6-address + | | +--ro rp-addr inet:ipv6-address + | +--ro spt-switch + | +--ro infinity! {spt-switch-infinity}? + | +--ro policy-name? string {spt-switch-policy}? + +--ro ssm! + +--ro range-poligy? string // +--ro address-range* inet:ip-prefix // Not this way

SM State 2/2 augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:interfaces/pim-base:interface/pim-base:address-family: +--rw sm! +--rw passive? empty augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-rp:rp/pim-rp:static-rp/pim-rp:ipv4-rp: +--rw sm! +--rw policy-name? string +--rw override? boolean {static-rp-override}? augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-rp:rp/pim-rp:static-rp/pim-rp:ipv6-rp: +--rw sm! +--rw policy-name? string +--rw override? boolean {static-rp-override}? augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:interfaces/pim-base:interface/pim-base:address-family: +--ro sm! +--ro passive? empty augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-rp:rp/pim-rp:static-rp/pim-rp:ipv4-rp: +--ro sm! +--ro policy-name? string +--ro override? boolean {static-rp-override}? augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family/pim-rp:rp/pim-rp:static-rp/pim-rp:ipv6-rp: +--ro sm! +--ro policy-name? string +--ro override? boolean {static-rp-override}?

Static RP Applied State module: ietf-pim-rp augment /rt:routing/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family: +--rw rp +--rw static-rp | +--rw ipv4-rp* [ipv4-addr] | | +--rw ipv4-addr inet:ipv4-address | +--rw ipv6-rp* [ipv6-addr] | +--rw ipv6-addr inet:ipv6-address augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/pim- base:pim/pim-base:address-family: +--ro rp +--ro static-rp | +--ro ipv4-rp* [ipv4-addr] | | +--ro ipv4-addr inet:ipv4-address | +--ro ipv6-rp* [ipv6-addr] | +--ro ipv6-addr inet:ipv6-address // Derived state has already been defined and unchanged

IGMP The possible points for augmentation consideration are 1. augment /if:interfaces/if:interface/ip:ipv4: 2. augment /rt:routing/rt:routing-instance/rt:routing-protocols: 3. augment /rt:routing/rt:routing-protocols

IGMP module: ietf-igmp augment /rt:routing/rt:routing-instance/rt:routing-protocols: +--rw igmp +--rw global +--rw interfaces +-- rw interface* +--rw ssm-map* [source-ip-address] | +--rw source-ip-address inet:ipv4-address | +--rw group-access-list-name string +--rw static-group* [group-ip-address] | +--rw group-ip-address inet:ipv4-address | +--rw source-ip-address? inet:ipv4-address +--rw access-group? string +--rw join-group? inet:ipv4-address +--rw last-member-query-interval? uint16 +--rw query-interval? uint16 +--rw query-max-response-time? uint8 +--rw query-solicitation? empty +--rw robust? uint8 +--rw verify-source-subnet? empty +--rw version? uint8

MLD module: ietf-mld augment /if:interfaces/if:interface/ip:ipv4: +--rw mld +--rw ssm-map* [source-ip-address] | +--rw source-ip-address inet:ipv6-address | +--rw group-access-list-name string +--rw static-group* [group-ip-address] | +--rw group-ip-address inet:ipv6-address | +--rw source-ip-address? inet:ipv6-address // list +--rw access-group? string +--rw last-member-query-interval? uint16 +--rw query-interval? uint16 +--rw query-max-response-time? uint8 +--rw query-solicitation? empty +--rw robust? uint8 +--rw version? uint8