< draft-ietf-rtgwg-yang-rip-07.txt   draft-ietf-rtgwg-yang-rip-08.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: June 16, 2018 Ericsson Expires: July 14, 2018 Ericsson
V. Choudhary V. Choudhary
Individual Individual
December 13, 2017 January 10, 2018
A YANG Data Model for Routing Information Protocol (RIP) A YANG Data Model for Routing Information Protocol (RIP)
draft-ietf-rtgwg-yang-rip-07 draft-ietf-rtgwg-yang-rip-08
Abstract Abstract
This document describes a data model for the Routing Information This document describes a data model for the management of the
Protocol (RIP). Both RIP version 2 and RIPng are covered. Routing Information Protocol (RIP). Both RIP version 2 and RIPng are
covered. The data model includes definitions for configuration,
operational state, and Remote Procedure Calls (RPCs).
The YANG model in this document conforms to the Network Management
Datastore Architecture (NMDA).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 June 16, 2018. This Internet-Draft will expire on July 14, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3 1.3. Prefixes in Data Node Names . . . . . . . . . . . . . . . 3
2. Design of the Data Model . . . . . . . . . . . . . . . . . . 4 2. Design of the Data Model . . . . . . . . . . . . . . . . . . 3
2.1. Scope of the Model . . . . . . . . . . . . . . . . . . . 4 2.1. Scope of the Model . . . . . . . . . . . . . . . . . . . 3
2.2. Relation with Core Routing Framework . . . . . . . . . . 4 2.2. Relation with Core Routing Framework . . . . . . . . . . 4
2.3. Protocol Configuration . . . . . . . . . . . . . . . . . 4 2.3. Protocol Configuration . . . . . . . . . . . . . . . . . 4
2.4. Protocol States . . . . . . . . . . . . . . . . . . . . . 5 2.4. Protocol States . . . . . . . . . . . . . . . . . . . . . 5
2.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 7 2.5. RPC Operations . . . . . . . . . . . . . . . . . . . . . 6
2.6. Notifications . . . . . . . . . . . . . . . . . . . . . . 7 2.6. Notifications . . . . . . . . . . . . . . . . . . . . . . 6
2.7. Optional Features . . . . . . . . . . . . . . . . . . . . 7 2.7. Optional Features . . . . . . . . . . . . . . . . . . . . 6
3. Tree Structure . . . . . . . . . . . . . . . . . . . . . . . 7 3. Tree Structure . . . . . . . . . . . . . . . . . . . . . . . 6
4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 11 4. YANG Module . . . . . . . . . . . . . . . . . . . . . . . . . 10
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34
6. Security Considerations . . . . . . . . . . . . . . . . . . . 35 6. Security Considerations . . . . . . . . . . . . . . . . . . . 34
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 36 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.1. Normative References . . . . . . . . . . . . . . . . . . 36 7.1. Normative References . . . . . . . . . . . . . . . . . . 35
7.2. Informative References . . . . . . . . . . . . . . . . . 37 7.2. Informative References . . . . . . . . . . . . . . . . . 37
Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 39 Appendix A. Data Tree Example . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 43
1. Introduction 1. Introduction
This document introduces a YANG [RFC7950] data model for the Routing This document introduces a YANG [RFC7950] data model for the Routing
Information Protocol (RIP) [RFC2453][RFC2080]. RIP was designed to Information Protocol (RIP) [RFC2453][RFC2080]. RIP was designed to
work as an Interior Gateway Protocol (IGP) in moderate-size work as an Interior Gateway Protocol (IGP) in moderate-size
Autonomous Systems (AS). Autonomous Systems (AS).
skipping to change at page 3, line 4 skipping to change at page 3, line 11
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The following terms are defined in [RFC7950] and are not redefined The following terms are defined in [RFC7950] and are not redefined
here: here:
o augment o augment
o data model o data model
o data node o data node
1.2. Tree Diagrams 1.2. Tree Diagrams
A simplified graphical representation of the data model is used in A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as this document. The meaning of the symbols in these diagrams is
follows: defined in [I-D.ietf-netmod-yang-tree-diagrams].
o Brackets "[" and "]" enclose list keys.
o Curly braces "{" and "}" contain names of optional features that
make the corresponding node conditional.
o Abbreviations before data node names: "rw" means configuration
(read-write), and "ro" means state data (read-only).
o Symbols after data node names: "?" means an optional node, "!"
means a presence container, and "*" denotes a list and leaf-list.
o Parentheses enclose choice and case nodes, and case nodes are also
marked with a colon (":").
o Ellipsis ("...") stands for contents of subtrees that are not
shown.
1.3. Prefixes in Data Node Names 1.3. Prefixes in Data Node Names
In this document, names of data nodes, actions, and other data model In this document, names of data nodes, actions, and other data model
objects are often used without a prefix, as long as it is clear from objects are often used without a prefix, as long as it is clear from
the context in which YANG module each name is defined. Otherwise, the context in which YANG module each name is defined. Otherwise,
names are prefixed using the standard prefix associated with the names are prefixed using the standard prefix associated with the
corresponding YANG module, as shown in Table 1. corresponding YANG module, as shown in Table 1.
+-----------+-----------------+-----------------------------------+ +-----------+-----------------+-------------------------------+
| Prefix | YANG module | Reference | | Prefix | YANG module | Reference |
+-----------+-----------------+-----------------------------------+ +-----------+-----------------+-------------------------------+
| yang | ietf-yang-types | [RFC6991] | | yang | ietf-yang-types | [RFC6991] |
| inet | ietf-inet-types | [RFC6991] | | inet | ietf-inet-types | [RFC6991] |
| if | ietf-interfaces | [I-D.bjorklund-netmod-rfc7223bis] | | if | ietf-interfaces | [I-D.ietf-netmod-rfc7223bis] |
| ip | ietf-ip | [I-D.bjorklund-netmod-rfc7277bis] | | ip | ietf-ip | [I-D.ietf-netmod-rfc7277bis] |
| rt | ietf-routing | [I-D.acee-netmod-rfc8022bis] | | rt | ietf-routing | [I-D.ietf-netmod-rfc8022bis] |
| bfd-types | ietf-bfd-types | [I-D.ietf-bfd-yang] | | bfd-types | ietf-bfd-types | [I-D.ietf-bfd-yang] |
| isis | ietf-isis | [I-D.ietf-isis-yang-isis-cfg] | | isis | ietf-isis | [I-D.ietf-isis-yang-isis-cfg] |
| key-chain | ietf-key-chain | [RFC8177] | | key-chain | ietf-key-chain | [RFC8177] |
| ospf | ietf-ospf | [I-D.ietf-ospf-yang] | | ospf | ietf-ospf | [I-D.ietf-ospf-yang] |
+-----------+-----------------+-----------------------------------+ +-----------+-----------------+-------------------------------+
Table 1: Prefixes and Corresponding YANG Modules Table 1: Prefixes and Corresponding YANG Modules
2. Design of the Data Model 2. Design of the Data Model
2.1. Scope of the Model 2.1. Scope of the Model
The model covers RIP version 2 [RFC2453] and RIPng [RFC2080] The model covers RIP version 2 [RFC2453] and RIPng [RFC2080]
protocols. The model is designed to be implemented on a device where protocols. The model is designed to be implemented on a device where
RIP version 2 or RIPng is implemented, and can be used to: RIP version 2 or RIPng is implemented, and can be used to:
skipping to change at page 4, line 24 skipping to change at page 4, line 14
o Manage the protocol operational behaviors. o Manage the protocol operational behaviors.
o Retrieve the protocol operational status. o Retrieve the protocol operational status.
The capabilities describe in [RFC1724] are covered. The capabilities describe in [RFC1724] are covered.
2.2. Relation with Core Routing Framework 2.2. Relation with Core Routing Framework
This model augments the core routing data model "ietf-routing" This model augments the core routing data model "ietf-routing"
specified in [I-D.acee-netmod-rfc8022bis]. specified in [I-D.ietf-netmod-rfc8022bis].
+--rw routing +--rw routing
+--rw router-id? +--rw router-id?
+--rw control-plane-protocols +--rw control-plane-protocols
| +--rw control-plane-protocol* [type name] | +--rw control-plane-protocol* [type name]
| +--rw type | +--rw type
| +--rw name | +--rw name
| +--rw rip <= Augmented by this Model | +--rw rip <= Augmented by this Model
... ...
skipping to change at page 7, line 13 skipping to change at page 6, line 18
o Route o Route
2.5. RPC Operations 2.5. RPC Operations
This model defines one RPC "clear-rip-route" that can be used to This model defines one RPC "clear-rip-route" that can be used to
clear RIP routes from the routing table. clear RIP routes from the routing table.
2.6. Notifications 2.6. Notifications
This model does not define RIP specific notifications. To enable This model does not define RIP specific notifications. To enable
notifications, the mechanism defined in [I-D.ietf-netconf-yang-push] notifications, the mechanism defined in
and [I-D.ietf-netconf-rfc5277bis] can be used. This mechanism [I-D.ietf-netconf-subscribed-notifications] and
currently allows the user to: [I-D.ietf-netconf-yang-push] can be used. This mechanism currently
allows the user to:
o Subscribe notifications on a per client basis. o Subscribe notifications on a per client basis.
o Specify subtree filters or xpath filters so that only interested o Specify subtree filters or xpath filters so that only interested
contents will be sent. contents will be sent.
o Specify either periodic or on-demand notifications. o Specify either periodic or on-demand notifications.
2.7. Optional Features 2.7. Optional Features
skipping to change at page 8, line 17 skipping to change at page 7, line 24
| +--rw cg-nat! | +--rw cg-nat!
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw connected! | +--rw connected!
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw ipsec! | +--rw ipsec!
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw isis* [instance] | +--rw isis* [instance]
| | +--rw instance -> ../../../../.. | | +--rw instance
/rt:control-plane-protocol/name | | | -> ../../../../../rt:control-plane-protocol/name
| | +--rw level? enumeration | | +--rw level? enumeration
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw nat! | +--rw nat!
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw ospfv2* [instance] | +--rw ospfv2* [instance]
| | +--rw instance -> ../../../../.. | | +--rw instance
/rt:control-plane-protocol/name | | | -> ../../../../../rt:control-plane-protocol/name
| | +--rw route-type? ospf:route-type | | +--rw route-type? ospf:route-type
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw ospfv3* [instance] | +--rw ospfv3* [instance]
| | +--rw instance -> ../../../../.. | | +--rw instance
/rt:control-plane-protocol/name | | | -> ../../../../../rt:control-plane-protocol/name
| | +--rw route-type? ospf:route-type | | +--rw route-type? ospf:route-type
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw ripv2* [instance] | +--rw ripv2* [instance]
| | +--rw instance -> ../../../../.. | | +--rw instance
/rt:control-plane-protocol/name | | | -> ../../../../../rt:control-plane-protocol/name
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw ripng* [instance] | +--rw ripng* [instance]
| | +--rw instance -> ../../../../.. | | +--rw instance
/rt:control-plane-protocol/name | | | -> ../../../../../rt:control-plane-protocol/name
| | +--rw metric? uint8 | | +--rw metric? uint8
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw static! | +--rw static!
| +--rw metric? uint8 | +--rw metric? uint8
| +--rw route-policy? route-policy-ref | +--rw route-policy? route-policy-ref
+--rw timers +--rw timers
| +--rw update-interval? uint16 | +--rw update-interval? uint16
| +--rw invalid-interval? uint16 | +--rw invalid-interval? uint16
| +--rw holddown-interval? uint16 | +--rw holddown-interval? uint16
| +--rw flush-interval? uint16 | +--rw flush-interval? uint16
skipping to change at page 9, line 23 skipping to change at page 8, line 30
| | | +--rw key-chain? | | | +--rw key-chain?
key-chain:key-chain-ref key-chain:key-chain-ref
| | +--:(auth-key) | | +--:(auth-key)
| | +--rw key? string | | +--rw key? string
| | +--rw crypto-algorithm? identityref | | +--rw crypto-algorithm? identityref
| +--rw bfd {bfd}? | +--rw bfd {bfd}?
| | +--rw enable? boolean | | +--rw enable? boolean
| | +--rw local-multiplier? multiplier | | +--rw local-multiplier? multiplier
| | +--rw (interval-config-type)? | | +--rw (interval-config-type)?
| | +--:(tx-rx-intervals) | | +--:(tx-rx-intervals)
| | | +--rw desired-min-tx-interval uint32 | | | +--rw desired-min-tx-interval? uint32
| | | +--rw required-min-rx-interval uint32 | | | +--rw required-min-rx-interval? uint32
| | +--:(single-interval) | | +--:(single-interval)
| | +--rw min-interval uint32 | | +--rw min-interval? uint32
| +--rw cost? uint8 | +--rw cost? uint8
| +--rw neighbors {explicit-neighbors}? | +--rw neighbors {explicit-neighbors}?
| | +--rw neighbor* [address] | | +--rw neighbor* [address]
| | +--rw address inet:ip-address | | +--rw address inet:ip-address
| +--rw no-listen? empty | +--rw no-listen? empty
| +--rw originate-default-route | +--rw originate-default-route
| | +--rw enabled? boolean | | +--rw enabled? boolean
| | +--rw route-policy? route-policy-ref | | +--rw route-policy? route-policy-ref
| +--rw passive? empty | +--rw passive? empty
| +--rw split-horizon? enumeration | +--rw split-horizon? enumeration
skipping to change at page 11, line 17 skipping to change at page 10, line 25
+--ro statistics {global-statistics}? +--ro statistics {global-statistics}?
+--ro discontinuity-time? yang:date-and-time +--ro discontinuity-time? yang:date-and-time
+--ro requests-rcvd? yang:counter32 +--ro requests-rcvd? yang:counter32
+--ro requests-sent? yang:counter32 +--ro requests-sent? yang:counter32
+--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? -> /rt:routing +---w rip-instance? leafref
/control-plane-protocols/control-plane-protocol/name
4. YANG Module 4. YANG Module
<CODE BEGINS> file "ietf-rip@2017-12-05.yang" <CODE BEGINS> file "ietf-rip@2018-01-09.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 25 skipping to change at page 11, line 30
import ietf-isis { import ietf-isis {
prefix "isis"; prefix "isis";
} }
organization "IETF Routing Area Working Group (rtgwg)"; organization "IETF Routing Area Working Group (rtgwg)";
contact contact
"WG Web: <http://tools.ietf.org/wg/rgtwg/> "WG Web: <http://tools.ietf.org/wg/rgtwg/>
WG List: <mailto:rgtwg@ietf.org> WG List: <mailto:rgtwg@ietf.org>
WG Chair: Jeff Tantsura
<mailto:jefftant.ietf@gmail.com>
WG Chair: Chris Bowers
<mailto:cbowers@juniper.net>
Editor: Xufeng Liu Editor: Xufeng Liu
<mailto:xufeng_liu@jabil.com> <mailto:xufeng_liu@jabil.com>
Editor: Prateek Sarda Editor: Prateek Sarda
<mailto:prateek.sarda@ericsson.com> <mailto:prateek.sarda@ericsson.com>
Editor: Vikram Choudhary Editor: Vikram Choudhary
<mailto:vikschw@gmail.com>"; <mailto:vikschw@gmail.com>";
description description
"This YANG module defines a model for managing Routing "This YANG module defines a model for managing Routing
Information Protocol (RIP), including RIP version 2 and RIPng. Information Protocol (RIP), including RIP version 2 and RIPng.
Copyright (c) 2016 IETF Trust and the persons identified as Copyright (c) 2018 IETF Trust and the persons identified as
authors of the code. All rights reserved. authors of the code. All rights reserved.
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
RFC itself for full legal notices.";
revision 2017-12-05 { revision 2018-01-09 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC 2453: RIP Version 2. "RFC XXXX: A YANG Data Model for Routing Information Protocol
(RIP).
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.";
} }
/* /*
* Features * Features
*/ */
feature bfd { feature bfd {
description description
"This feature indicates that the RIP implementation on the "This feature indicates that the RIP implementation on the
skipping to change at page 35, line 31 skipping to change at page 34, line 35
-------------------------------------------------------------------- --------------------------------------------------------------------
name: ietf-rip name: ietf-rip
namespace: urn:ietf:params:xml:ns:yang:ietf-rip namespace: urn:ietf:params:xml:ns:yang:ietf-rip
prefix: rip prefix: rip
reference: RFC XXXX reference: RFC XXXX
-------------------------------------------------------------------- --------------------------------------------------------------------
6. Security Considerations 6. Security Considerations
The configuration, state, and action data defined in this document The YANG module specified in this document defines a schema for data
are designed to be accessed via a management protocol with a secure that is designed to be accessed via network management protocols such
transport layer, such as NETCONF [RFC6241]. The NETCONF access as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer
control model [RFC6536] provides the means to restrict access for is the secure transport layer, and the mandatory-to-implement secure
particular NETCONF users to a preconfigured subset of all available transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer
NETCONF protocol operations and contents. is HTTPS, and the mandatory-to-implement secure transport is TLS
[RFC5246].
A number of configuration data nodes defined in this document are The NETCONF access control model [RFC6536] provides the means to
writable/creatable/deletable (i.e., "config true" in YANG terms, restrict access for particular NETCONF or RESTCONF users to a
which is the default). These data nodes may be considered sensitive preconfigured subset of all available NETCONF or RESTCONF protocol
or vulnerable in some network environments. Write operations to operations and content.
these data nodes, such as "edit-config" in NETCONF, can have negative
effects on the network if the protocol operations are not properly There are a number of data nodes defined in this YANG module that are
protected. The vulnerable "config true" parameters and subtrees are writable/creatable/deletable (i.e., config true, which is the
the following: default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability:
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/ /rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
rip:rip rip:rip
Unauthorized access to any node of these can adversely affect the Unauthorized access to any data node of these subtrees can adversely
routing subsystem of both the local device and the network. This may affect the routing subsystem of both the local device and the
lead to network malfunctions, delivery of packets to inappropriate network. This may lead to network malfunctions, delivery of packets
destinations, and other problems. to inappropriate destinations, and other problems.
This data model also defines a RPC "clear-rip-route", which may Some of the readable data nodes in this YANG module may be considered
affect the routing subsystem in the same way as described above. sensitive or vulnerable in some network environments. It is thus
important to control read access (e.g., via get, get-config, or
notification) to these data nodes. These are the subtrees and data
nodes and their sensitivity/vulnerability:
/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol/
rip:rip
Unauthorized access to any data node of these subtrees can disclose
the operational state information of RIP on this device.
Some of the RPC operations in this YANG module may be considered
sensitive or vulnerable in some network environments. It is thus
important to control access to these operations. These are the
operations and their sensitivity/vulnerability:
RPC clear-rip-route:
Unauthorized access to the RPC above can adversely affect the routing
subsystem of both the local device and the network. This may lead to
network malfunctions, delivery of packets to inappropriate
destinations, and other problems.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC1724] Malkin, G. and F. Baker, "RIP Version 2 MIB Extension",
RFC 1724, DOI 10.17487/RFC1724, November 1994,
<https://www.rfc-editor.org/info/rfc1724>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
editor.org/info/rfc2119>. editor.org/info/rfc2119>.
[RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453, [RFC2453] Malkin, G., "RIP Version 2", STD 56, RFC 2453,
DOI 10.17487/RFC2453, November 1998, <https://www.rfc- DOI 10.17487/RFC2453, November 1998, <https://www.rfc-
editor.org/info/rfc2453>. editor.org/info/rfc2453>.
[RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080, [RFC2080] Malkin, G. and R. Minnear, "RIPng for IPv6", RFC 2080,
DOI 10.17487/RFC2080, January 1997, <https://www.rfc- DOI 10.17487/RFC2080, January 1997, <https://www.rfc-
editor.org/info/rfc2080>. editor.org/info/rfc2080>.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
DOI 10.17487/RFC3688, January 2004, <https://www.rfc- DOI 10.17487/RFC3688, January 2004, <https://www.rfc-
editor.org/info/rfc3688>. editor.org/info/rfc3688>.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246,
DOI 10.17487/RFC5246, August 2008, <https://www.rfc-
editor.org/info/rfc5246>.
[RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
and A. Bierman, Ed., "Network Configuration Protocol and A. Bierman, Ed., "Network Configuration Protocol
(NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
<https://www.rfc-editor.org/info/rfc6241>. <https://www.rfc-editor.org/info/rfc6241>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types",
RFC 6991, DOI 10.17487/RFC6991, July 2013, RFC 6991, DOI 10.17487/RFC6991, July 2013,
<https://www.rfc-editor.org/info/rfc6991>. <https://www.rfc-editor.org/info/rfc6991>.
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016, RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>. <https://www.rfc-editor.org/info/rfc7950>.
[RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017,
<https://www.rfc-editor.org/info/rfc8040>.
[RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J. [RFC8177] Lindem, A., Ed., Qu, Y., Yeung, D., Chen, I., and J.
Zhang, "YANG Data Model for Key Chains", RFC 8177, Zhang, "YANG Data Model for Key Chains", RFC 8177,
DOI 10.17487/RFC8177, June 2017, <https://www.rfc- DOI 10.17487/RFC8177, June 2017, <https://www.rfc-
editor.org/info/rfc8177>. editor.org/info/rfc8177>.
[I-D.bjorklund-netmod-rfc7223bis] [I-D.ietf-netmod-rfc7223bis]
Bjorklund, M., "A YANG Data Model for Interface Bjorklund, M., "A YANG Data Model for Interface
Management", draft-bjorklund-netmod-rfc7223bis-00 (work in Management", draft-ietf-netmod-rfc7223bis-02 (work in
progress), August 2017. progress), January 2018.
[I-D.bjorklund-netmod-rfc7277bis] [I-D.ietf-netmod-rfc7277bis]
Bjorklund, M., "A YANG Data Model for IP Management", Bjorklund, M., "A YANG Data Model for IP Management",
draft-bjorklund-netmod-rfc7277bis-00 (work in progress), draft-ietf-netmod-rfc7277bis-02 (work in progress),
August 2017. January 2018.
[I-D.acee-netmod-rfc8022bis] [I-D.ietf-netmod-rfc8022bis]
Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for Lhotka, L., Lindem, A., and Y. Qu, "A YANG Data Model for
Routing Management (NDMA Version)", draft-acee-netmod- Routing Management (NDMA Version)", draft-ietf-netmod-
rfc8022bis-06 (work in progress), October 2017. rfc8022bis-08 (work in progress), January 2018.
[I-D.ietf-bfd-yang] [I-D.ietf-bfd-yang]
Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and Rahman, R., Zheng, L., Jethanandani, M., Networks, J., and
G. Mirsky, "YANG Data Model for Bidirectional Forwarding G. Mirsky, "YANG Data Model for Bidirectional Forwarding
Detection (BFD)", draft-ietf-bfd-yang-07 (work in Detection (BFD)", draft-ietf-bfd-yang-07 (work in
progress), October 2017. progress), October 2017.
[I-D.ietf-isis-yang-isis-cfg] [I-D.ietf-isis-yang-isis-cfg]
Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L. Litkowski, S., Yeung, D., Lindem, A., Zhang, Z., and L.
Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf- Lhotka, "YANG Data Model for IS-IS protocol", draft-ietf-
isis-yang-isis-cfg-19 (work in progress), November 2017. isis-yang-isis-cfg-19 (work in progress), November 2017.
[I-D.ietf-ospf-yang] [I-D.ietf-ospf-yang]
Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem, Yeung, D., Qu, Y., Zhang, Z., Chen, I., and A. Lindem,
"Yang Data Model for OSPF Protocol", draft-ietf-ospf- "Yang Data Model for OSPF Protocol", draft-ietf-ospf-
yang-09 (work in progress), October 2017. yang-09 (work in progress), October 2017.
[I-D.ietf-netmod-revised-datastores] [I-D.ietf-netmod-revised-datastores]
Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
and R. Wilton, "Network Management Datastore and R. Wilton, "Network Management Datastore
Architecture", draft-ietf-netmod-revised-datastores-07 Architecture", draft-ietf-netmod-revised-datastores-09
(work in progress), November 2017. (work in progress), December 2017.
7.2. Informative References 7.2. Informative References
[RFC1724] Malkin, G. and F. Baker, "RIP Version 2 MIB Extension",
RFC 1724, DOI 10.17487/RFC1724, November 1994,
<https://www.rfc-editor.org/info/rfc1724>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
DOI 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>.
[RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG", [RFC7951] Lhotka, L., "JSON Encoding of Data Modeled with YANG",
RFC 7951, DOI 10.17487/RFC7951, August 2016, RFC 7951, DOI 10.17487/RFC7951, August 2016,
<https://www.rfc-editor.org/info/rfc7951>. <https://www.rfc-editor.org/info/rfc7951>.
[I-D.ietf-netconf-rfc5277bis] [I-D.ietf-netconf-subscribed-notifications]
Clemm, A., Prieto, A., Voit, E., Nilsen-Nygaard, E., Voit, E., Clemm, A., Prieto, A., Nilsen-Nygaard, E., and
Tripathy, A., Chisholm, S., and H. Trevino, "Subscribing A. Tripathy, "Custom Subscription to Event Streams",
to Event Notifications", draft-ietf-netconf-rfc5277bis-01 draft-ietf-netconf-subscribed-notifications-08 (work in
(work in progress), October 2016. progress), December 2017.
[I-D.ietf-netconf-yang-push] [I-D.ietf-netconf-yang-push]
Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen- Clemm, A., Voit, E., Prieto, A., Tripathy, A., Nilsen-
Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore Nygaard, E., Bierman, A., and B. Lengyel, "YANG Datastore
Subscription", draft-ietf-netconf-yang-push-11 (work in Subscription", draft-ietf-netconf-yang-push-12 (work in
progress), October 2017. progress), December 2017.
[I-D.ietf-netmod-rfc6087bis] [I-D.ietf-netmod-rfc6087bis]
Bierman, A., "Guidelines for Authors and Reviewers of YANG Bierman, A., "Guidelines for Authors and Reviewers of YANG
Data Model Documents", draft-ietf-netmod-rfc6087bis-14 Data Model Documents", draft-ietf-netmod-rfc6087bis-15
(work in progress), September 2017. (work in progress), December 2017.
[I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-04 (work in progress),
December 2017.
Appendix A. Data Tree Example Appendix A. Data Tree Example
This section contains an example of an instance data tree in the JSON This section contains an example of an instance data tree in the JSON
encoding [RFC7951], containing both configuration and state data. encoding [RFC7951], containing both configuration and state data.
+---------------------+ +---------------------+
| | | |
| Router 203.0.113.1 | | Router 203.0.113.1 |
| | | |
 End of changes. 46 change blocks. 
129 lines changed or deleted 160 lines changed or added

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