YANG Data Model for RIP draft-liu-rtgwg-yang-rip-01

Slides:



Advertisements
Similar presentations
RIP2 CCNA Exploration Semester 2 Chapter 7
Advertisements

RIP V2 CCNP S1(5), Chapter 4.
Copyright 2008 Kenneth M. Chipps Ph.D. Cisco CCNA Exploration CCNA 2 Routing Protocols and Concepts Chapter 4 Distance Vector Routing Protocols.
YANG Data Model for VRRP draft-liu-rtgwg-yang-vrrp-02
RIP – Routing Information Protocol Syeda Momina Tabish MIT - 7.
Routing Information Protocol (RIP) Josh Timmons, CCNA Datacom II February 15, 2000.
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 Diffserv Yang Model
Dynamic Routing Protocols  Function(s) of Dynamic Routing Protocols: – Dynamically share information between routers (Discover remote networks). – Automatically.
M. Menelaou CCNA2 DYNAMIC ROUTING. M. Menelaou DYNAMIC ROUTING Dynamic routing protocols can help simplify the life of a network administrator Routing.
1 © 2003, Cisco Systems, Inc. All rights reserved. CCNA 2 Module 7 Distance Vector Routing Protocols.
Slide /2009COMM3380 Routing Algorithms Distance Vector Routing Each node knows the distance (=cost) to its directly connected neighbors A node sends.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 2 v3.1 Module 7 Distance Vector Routing Protocols.
TCOM 515 Lecture 2. Lecture 2 Objectives Dynamic Routing Distance Vector Routing Link State Routing Interior vs Exterior RIP - Routing Information Protocol.
Distance Vector Routing Protocols Routing Protocols and Concepts Lecture Week 4.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 2 v3.1 Module 7 Distance Vector Routing Protocols.
IETF 92 Dallas, TX Yang Data Model for OSPF Protocol draft-ietf-ospf-yang-00 Yingzhen Qu Derek Yeung YingZhen Qu
 RIP — A distance vector interior routing protocol  IGRP — The Cisco distance vector interior routing protocol (not used nowadays)  OSPF — A link-state.
Routing Information Protocol
CCNA2 v3 Module 7 v3 CCNA 2 Module 7 JEOPARDY K. Martin.
RIP Routing Protocol. 2 Routing Recall: There are two parts to routing IP packets: 1. How to pass a packet from an input interface to the output interface.
Pim wg multicast YANG team Meeting
Pim wg multicast YANG team Meeting Interface Hierarchy (Option 1) +--rw routing +--rw routing-instance* [name] +--rw routing-protocols +--rw.
draft-ietf-teas-yang-te-topo-04
RIP.
Yang Data Model for Tunnel Policy draft-li-rtgwg-tunnel-policy-yang-00
YANG Data Model For RIB Extensions IETF 97, Seoul
Distance Vector Routing Protocols
Dynamic Routing Protocols part2
draft-ietf-teas-yang-te-topo-05
Connectionless OAM yang model
Routing Loops.
draft-litkowski-isis-yang-isis-cfg IETF 90 - Toronto
pim wg multicast YANG team
draft-ietf-teas-yang-te-topo-06
Can SUPA Aid ECA Policy Development in I2RS Yang
Routing Area Yang Architecture Design Team Update
draft-ietf-teas-yang-te-topo-01
IETF 95 – Buenos Aires April 2016
pim wg multicast YANG team
Routing Information Protocol (RIP)
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-03 draft-ietf-teas-yang-rsvp-03 Tarek Saad (Presenter)
CCNA 2 v3.1 Module 7 Distance Vector Routing Protocols
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
Dynamic Routing Protocols part2
draft-ietf-pim-igmp-mld-yang-04
Distance Vector Routing Protocols
Distance Vector Routing Protocols
RFC 1058 & RFC 2453 Routing Information Protocol
RIFT YANG draft-zhang-rift-yang-00
YANG Mount draft-clemm-netmod-mount IETF 98 Chicago, 30 March 2017
YANG Data Models MPLS Base and Static LSPs draft-ietf-mpls-base-yang-04 draft-ietf-mpls-static-yang-04 Tarek.
IGMP & MLD Snooping YANG Model
Post WG LC NMDA datastore architecture draft
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
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.
Distance Vector Routing Protocols
draft-ietf-teas-yang-te-topo-08
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-04
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
YANG Data Models for TE and RSVP draft-ietf-teas-yang-te-21 draft-ietf-teas-yang-rsvp-11 draft-ietf-teas-yang-rsvp-te-07 Tarek Saad, Juniper Networks Rakesh.
Presentation transcript:

YANG Data Model for RIP draft-liu-rtgwg-yang-rip-01 Xufeng Liu (Ericsson) Prateek Sarda (Ericsson) Vikram Choudhary (Huawei) IETF93

Scope YANG Data Model for configuring and monitoring RIP (Routing Information Protocol) RIP version 2 (RFC2453) for IPv4 RIPng (RFC2080) for IPv6 Covers configuration, operational states, and actions.

Goals Keep simple Avoid vendor specific features Support vendor extensions Be consistent with other protocol models

Relationship with Other Modules Augments ietf-routing (draft-ietf-netmod-routing-cfg) ietf-routing augments ietf-rip

Augmentation Each RIP instance is modeled as an instance of routing-protocol with type “ripv2” or “ripng”. Model supports multiple RIP instances in a routing-instance. module: ietf-routing +--ro routing-state | +--ro routing-instance* [name] | +--ro routing-protocols | +--ro routing-protocol* [name] | +--ro name string | +--ro type identityref | +--ro rip:rip +--rw routing +--rw routing-instance* [name] +--rw routing-protocols +--rw routing-protocol* [name] +--rw name string +--rw description? string +--rw enabled? boolean +--rw type identityref +--rw rip:rip

Instance Configuration Model covers RIP instance level attributes Timers, route characteristic parameters, and redistribution option. augment /rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol: +--rw rip +--rw originate-default-route! | +--rw route-map? string +--rw default-metric? uint8 +--rw distance? uint8 +--rw flash-update-threshold? uint8 +--rw maximum-paths? uint8 +--rw output-delay? uint8 +--rw distribute-list* [prefix-list-name direction] | +--rw prefix-list-name string | +--rw direction enumeration | +--rw if-name? if:interface-ref +--rw timers | +--rw update-interval? uint16 | +--rw invalid-interval? uint16 | +--rw holddown-interval? uint16 | +--rw flush-interval? uint16

Interface Configuration Model covers RIP interface level attributes Timers, route characteristic parameters, neighbor specification, split-horizon option, and authentication reference. +--rw rip +--rw interface* [interface] +--rw interface if:interface-ref +--rw authentication +--rw bfd? boolean {bfd}? +--rw cost? uint8 +--rw neighbors {neighbor-configuration}? | +--rw neighbor* [address] | +--rw address inet:ip-address +--rw no-listen? empty +--rw no-supply? empty +--rw originate-default-route! | +--rw route-map? string +--rw split-horizon? enumeration +--rw summary-address | +--rw address? inet:ip-prefix | +--rw metric? uint8 +--rw timers

Instance States Model covers RIP instance level state attributes augment /rt:routing-state/rt:routing-instance/rt:routing-protocols/ rt:routing-protocol: +--ro rip +--ro originate-default-route! | +--ro route-map? string +--ro default-metric? uint8 +--ro distance? uint8 +--ro flash-update-threshold? uint8 +--ro maximum-paths? uint8 +--ro output-delay? uint8 +--ro distribute-list* [prefix-list-name direction] | +--ro prefix-list-name string | +--ro direction enumeration | +--ro if-name? if:interface-ref +--ro timers ... ... +--ro next-flash-update? uint32 +--ro num-of-routes? uint32

Instance Statistics Model covers RIP instance level statistic data augment /rt:routing-state/rt:routing-instance/rt:routing-protocols /rt:routing-protocol: +--ro rip +--ro statistics {global-statistics}? +--ro discontinuity-time? yang:date-and-time +--ro requests-rcvd? yang:counter32 +--ro requests-sent? yang:counter32 +--ro responses-rcvd? yang:counter32 +--ro responses-sent? yang:counter32

Neighbor States Model captures neighbor state attributes augment /rt:routing-state/rt:routing-instance/rt:routing-protocols /rt:routing-protocol: +--ro rip +--ro ipv4 | +--ro neighbors | +--ro neighbor* [ipv4-address] | +--ro ipv4-address inet:ipv4-address | +--ro last-update? yang:date-and-time | +--ro bad-packets-rcvd? yang:counter32 | +--ro bad-routes-rcvd? yang:counter32 +--ro ipv6 +--ro neighbors +--ro neighbor* [ipv6-address] +--ro ipv6-address inet:ipv6-address +--ro last-update? yang:date-and-time +--ro bad-packets-rcvd? yang:counter32 +--ro bad-routes-rcvd? yang:counter32

Route States Model captures route state attributes augment /rt:routing-state/rt:routing-instance/rt:routing-protocols /rt:routing-protocol: +--ro rip +--ro ipv4 | +--ro routes | +--ro route* [ipv4-prefix] | +--ro ipv4-prefix inet:ipv4-prefix | +--ro next-hop? inet:ipv4-address | +--ro interface? if:interface-ref | +--ro redistributed? boolean | +--ro route-type? enumeration | +--ro metric? uint8 | +--ro expire-time? uint16 | +--ro deleted? boolean | +--ro holddown? boolean | +--ro need-flash? boolean | +--ro need-download-to-rib? boolean | +--ro inactive? boolean | +--ro next-hop-flags? bits

Interface States Model covers interface state data, including interface level statistics. +--ro interface* [interface] | +--ro interface if:interface-ref | +--ro oper-status? enumeration | +--ro cost? uint8 | +--ro listen? boolean | +--ro next-full-update? uint32 | +--ro originate-default-route? boolean | +--ro poison-reverse? boolean | +--ro split-horizon? boolean | +--ro supply? boolean | +--ro valid-address? boolean | +--ro timers ... ... | +--ro statistics {interface-statistics}? | +--ro discontinuity-time? yang:date-and-time | +--ro bad-packets-rcvd? yang:counter32 | +--ro bad-routes-rcvd? yang:counter32 | +--ro updates-sent? yang:counter32

Actions Model specifies actions that can be applied to a RIP instance. rpcs: +---x clear-rip-route +--ro input +--ro instance-name? leafref

Next Steps Align with other models, including BFD, routing policy, and authentication. Solicit comments WG adoption