draft-ietf-rtgwg-yang-rip-09.txt   draft-ietf-rtgwg-yang-rip-10.txt 
Network Working Group X. Liu Network Working Group X. Liu
Internet-Draft Jabil Internet-Draft Jabil
Intended status: Standards Track P. Sarda Intended status: Standards Track P. Sarda
Expires: August 4, 2018 Ericsson Expires: August 8, 2018 Ericsson
V. Choudhary V. Choudhary
Individual Individual
January 31, 2018 February 4, 2018
A YANG Data Model for Routing Information Protocol (RIP) A YANG Data Model for Routing Information Protocol (RIP)
draft-ietf-rtgwg-yang-rip-09 draft-ietf-rtgwg-yang-rip-10
Abstract Abstract
This document describes a data model for the management of the This document describes a data model for the management of the
Routing Information Protocol (RIP). Both RIP version 2 and RIPng are Routing Information Protocol (RIP). Both RIP version 2 and RIPng are
covered. The data model includes definitions for configuration, covered. The data model includes definitions for configuration,
operational state, and Remote Procedure Calls (RPCs). operational state, and Remote Procedure Calls (RPCs).
The YANG model in this document conforms to the Network Management The YANG model in this document conforms to the Network Management
Datastore Architecture (NMDA). Datastore Architecture (NMDA).
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 4, 2018. This Internet-Draft will expire on August 8, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 10, line 29 skipping to change at page 10, line 29
+--ro responses-rcvd? yang:counter32 +--ro responses-rcvd? yang:counter32
+--ro responses-sent? yang:counter32 +--ro responses-sent? yang:counter32
rpcs: rpcs:
+---x clear-rip-route +---x clear-rip-route
+---w input +---w input
+---w rip-instance? leafref +---w rip-instance? leafref
4. YANG Module 4. YANG Module
<CODE BEGINS> file "ietf-rip@2018-01-17.yang" <CODE BEGINS> file "ietf-rip@2018-02-03.yang"
module ietf-rip { module ietf-rip {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-rip"; namespace "urn:ietf:params:xml:ns:yang:ietf-rip";
prefix rip; prefix rip;
import ietf-inet-types { import ietf-inet-types {
prefix "inet"; prefix "inet";
} }
skipping to change at page 12, line 7 skipping to change at page 12, line 7
Redistribution and use in source and binary forms, with or Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX; see the This version of this YANG module is part of RFC XXXX; see the
RFC itself for full legal notices."; RFC itself for full legal notices.";
revision 2018-01-17 { revision 2018-02-03 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for Routing Information Protocol "RFC XXXX: A YANG Data Model for Routing Information Protocol
(RIP). (RIP).
RFC 2453: RIP Version 2. RFC 2453: RIP Version 2.
RFC 2080: RIPng for IPv6. RFC 2080: RIPng for IPv6.
RFC 1724: RIP Version 2 MIB Extension."; RFC 1724: RIP Version 2 MIB Extension.";
} }
skipping to change at page 30, line 36 skipping to change at page 30, line 36
description description
"IPv4 route information."; "IPv4 route information.";
list route { list route {
key "ipv4-prefix"; key "ipv4-prefix";
description description
"A RIPv2 IPv4 route."; "A RIPv2 IPv4 route.";
leaf ipv4-prefix { leaf ipv4-prefix {
type inet:ipv4-prefix; type inet:ipv4-prefix;
description description
"IP address (in the form A.B.C.D) and prefix length, "IPv4 address and prefix length, in the format
separated by the slash (/) character. The range of specified in RFC6991.";
values for the prefix-length is 0 to 32.";
} }
leaf next-hop { leaf next-hop {
type inet:ipv4-address; type inet:ipv4-address;
description description
"Next hop IPv4 address."; "Next hop IPv4 address.";
} }
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description description
"The interface that the route uses."; "The interface that the route uses.";
skipping to change at page 32, line 15 skipping to change at page 32, line 14
description description
"IPv6 route information."; "IPv6 route information.";
list route { list route {
key "ipv6-prefix"; key "ipv6-prefix";
description description
"A RIPng IPv6 route."; "A RIPng IPv6 route.";
leaf ipv6-prefix { leaf ipv6-prefix {
type inet:ipv6-prefix; type inet:ipv6-prefix;
description description
"IP address (in the canonical format defined in "IPv6 address and prefix length, in the format
RFC5952) and prefix length, separated by the slash specified in RFC6991.";
(/) character. The range of values for the
prefix-length is 0 to 128.";
} }
leaf next-hop { leaf next-hop {
type inet:ipv6-address; type inet:ipv6-address;
description description
"Next hop IPv6 address."; "Next hop IPv6 address.";
} }
leaf interface { leaf interface {
type if:interface-ref; type if:interface-ref;
description description
"The interface that the route uses."; "The interface that the route uses.";
 End of changes. 8 change blocks. 
13 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/