draft-ietf-netmod-rfc7277bis-00.txt   draft-ietf-netmod-rfc7277bis-01.txt 
Network Working Group M. Bjorklund Network Working Group M. Bjorklund
Internet-Draft Tail-f Systems Internet-Draft Tail-f Systems
Obsoletes: rfc7277 (if approved) October 16, 2017 Obsoletes: rfc7277 (if approved) December 17, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: April 19, 2018 Expires: June 20, 2018
A YANG Data Model for IP Management A YANG Data Model for IP Management
draft-ietf-netmod-rfc7277bis-00 draft-ietf-netmod-rfc7277bis-01
Abstract Abstract
This document defines a YANG data model for management of IP This document defines a YANG data model for management of IP
implementations. The data model includes configuration and system implementations. The data model includes configuration and system
state. This document obsoletes RFC 7277. state. This document obsoletes RFC 7277.
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
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 April 19, 2018. This Internet-Draft will expire on June 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 2, line 34 skipping to change at page 2, line 34
1. Introduction 1. Introduction
This document defines a YANG [RFC7950] data model for management of This document defines a YANG [RFC7950] data model for management of
IP implementations. IP implementations.
The data model covers configuration of per-interface IPv4 and IPv6 The data model covers configuration of per-interface IPv4 and IPv6
parameters, and mappings of IP addresses to link-layer addresses. It parameters, and mappings of IP addresses to link-layer addresses. It
also provides information about which IP addresses are operationally also provides information about which IP addresses are operationally
used, and which link-layer mappings exist. Per-interface parameters used, and which link-layer mappings exist. Per-interface parameters
are added through augmentation of the interface data model defined in are added through augmentation of the interface data model defined in
[I-D.bjorklund-netmod-rfc7223bis]. [I-D.ietf-netmod-rfc7223bis].
This version of the IP data model supports the Network Management This version of the IP data model supports the Network Management
Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores]. Datastore Architecture (NMDA) [I-D.ietf-netmod-revised-datastores].
1.1. Summary of Changes from RFC 7277 1.1. Summary of Changes from RFC 7277
The "ipv4" and "ipv6" subtrees with "config false" data nodes in the The "ipv4" and "ipv6" subtrees with "config false" data nodes in the
"/interfaces-state/interface" subtree are deprecated. All "config "/interfaces-state/interface" subtree are deprecated. All "config
false" data nodes are now present in the "ipv4" and "ipv6" subtrees false" data nodes are now present in the "ipv4" and "ipv6" subtrees
in the "/interfaces/interface" subtree. in the "/interfaces/interface" subtree.
Servers that do not implement NMDA, or that wish to support clients Servers that do not implement NMDA, or that wish to support clients
that do not implement NMDA, MAY implement the deprecated "ipv4" and that do not implement NMDA, MAY implement the deprecated "ipv4" and
"ipv6" subtrees in the "/interfaces-state/interface" subtree. "ipv6" subtrees in the "/interfaces-state/interface" subtree.
1.2. Terminology 1.2. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
The following terms are defined in The following terms are defined in
[I-D.ietf-netmod-revised-datastores] and are not redefined here: [I-D.ietf-netmod-revised-datastores] and are not redefined here:
o client o client
o server o server
o configuration o configuration
o system state o system state
skipping to change at page 3, line 40 skipping to change at page 3, line 46
o data model o data model
o data node o data node
The terminology for describing YANG data models is found in The terminology for describing YANG data models is found in
[RFC7950]. [RFC7950].
1.3. Tree Diagrams 1.3. Tree Diagrams
A simplified graphical representation of the data model is used in Tree diagrams used in this document follow the notation defined in
this document. The meaning of the symbols in these diagrams is as [I-D.ietf-netmod-yang-tree-diagrams].
follows:
o Brackets "[" and "]" enclose list keys.
o Abbreviations before data node names: "rw" means configuration
data (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.
2. IP Data Model 2. IP Data Model
This document defines the YANG module "ietf-ip", which augments the This document defines the YANG module "ietf-ip", which augments the
"interface" and "interface-state" lists defined in the "interface" and "interface-state" lists defined in the
"ietf-interfaces" module [I-D.bjorklund-netmod-rfc7223bis] with IP- "ietf-interfaces" module [I-D.ietf-netmod-rfc7223bis] with IP-
specific data nodes. specific data nodes.
The data model has the following structure for IP data nodes per The data model has the following structure for IP data nodes per
interface, excluding the deprecated data nodes: interface, excluding the deprecated data nodes:
module: ietf-ip module: ietf-ip
augment /if:interfaces/if:interface: augment /if:interfaces/if:interface:
+--rw ipv4! +--rw ipv4!
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw forwarding? boolean | +--rw forwarding? boolean
skipping to change at page 6, line 26 skipping to change at page 7, line 5
The IP-MIB defines objects to control IPv6 Router Advertisement The IP-MIB defines objects to control IPv6 Router Advertisement
messages. The corresponding YANG data nodes are defined in messages. The corresponding YANG data nodes are defined in
[RFC8022]. [RFC8022].
The entries in "ipv4/neighbor" and "ipv6/neighbor" are mapped to The entries in "ipv4/neighbor" and "ipv6/neighbor" are mapped to
ipNetToPhysicalTable. ipNetToPhysicalTable.
The following table lists the YANG data nodes with corresponding The following table lists the YANG data nodes with corresponding
objects in the IP-MIB. objects in the IP-MIB.
+--------------------------------------+----------------------------+ +----------------------------------+--------------------------------+
| YANG data node in | IP-MIB object | | YANG data node in | IP-MIB object |
| /if:interfaces/if:interface | | | /if:interfaces/if:interface | |
+--------------------------------------+----------------------------+ +----------------------------------+--------------------------------+
| ipv4 | ipv4InterfaceEnableStatus | | ipv4 | ipv4InterfaceEnableStatus |
| | | | ipv4/enabled | ipv4InterfaceEnableStatus |
| | ipv4/enabled | | ipv4/address | ipAddressEntry |
| ipv4InterfaceEnableStatus | | | ipv4/address/ip | ipAddressAddrType |
| | | | | ipAddressAddr |
| ipv4/address | ipAddressEntry | | ipv4/neighbor | ipNetToPhysicalEntry |
| | | | ipv4/neighbor/ip | ipNetToPhysicalNetAddressType |
| | ipv4/address/ip | | | ipNetToPhysicalNetAddress |
| ipAddressAddrType ipAddressAddr | | | ipv4/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| | | | ipv4/neighbor/origin | ipNetToPhysicalType |
| ipv4/neighbor | ipNetToPhysicalEntry | | ipv6 | ipv6InterfaceEnableStatus |
| | | | ipv6/enabled | ipv6InterfaceEnableStatus |
| | ipv4/neighbor/ip | | ipv6/forwarding | ipv6InterfaceForwarding |
| ipNetToPhysicalNetAddressType | | | ipv6/address | ipAddressEntry |
| ipNetToPhysicalNetAddress | | | ipv6/address/ip | ipAddressAddrType |
| | | | | ipAddressAddr |
| ipv4/neighbor/link-layer-address | ipNetToPhysicalPhysAddress | | ipv4/address/origin | ipAddressOrigin |
| | | | ipv6/address/status | ipAddressStatus |
| | ipv4/neighbor/origin | | ipv6/neighbor | ipNetToPhysicalEntry |
| ipNetToPhysicalType | | | ipv6/neighbor/ip | ipNetToPhysicalNetAddressType |
| | | | | ipNetToPhysicalNetAddress |
| ipv6 | ipv6InterfaceEnableStatus | | ipv6/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| | | | ipv6/neighbor/origin | ipNetToPhysicalType |
| | ipv6/enabled | | ipv6/neighbor/state | ipNetToPhysicalState |
| ipv6InterfaceEnableStatus | | +----------------------------------+--------------------------------+
| | |
| ipv6/forwarding | ipv6InterfaceForwarding |
| | |
| | ipv6/address |
| ipAddressEntry | |
| | |
| ipv6/address/ip | ipAddressAddrType |
| | ipAddressAddr |
| | |
| | ipv4/address/origin |
| ipAddressOrigin | |
| | |
| ipv6/address/status | ipAddressStatus |
| | ipv6/neighbor |
| ipNetToPhysicalEntry | ipv6/neighbor/ip |
| ipNetToPhysicalNetAddressType | |
| ipNetToPhysicalNetAddress | |
| | |
| ipv6/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| | |
| | ipv6/neighbor/origin |
| ipNetToPhysicalType | |
| | |
| ipv6/neighbor/state | ipNetToPhysicalState |
| | |
| |
+--------------------------------------+----------------------------+
YANG Interface Data Nodes and Related IP-MIB Objects YANG Interface Data Nodes and Related IP-MIB Objects
4. IP Management YANG Module 4. IP Management YANG Module
This module imports typedefs from [RFC6991] and This module imports typedefs from [RFC6991] and
[I-D.bjorklund-netmod-rfc7223bis], and it references [RFC0791], [I-D.ietf-netmod-rfc7223bis], and it references [RFC0791], [RFC0826],
[RFC0826], [RFC2460], [RFC4861], [RFC4862], [RFC4941] and [RFC7217]. [RFC2460], [RFC4861], [RFC4862], [RFC4941] and [RFC7217].
RFC Ed.: update the date below with the date of RFC publication and RFC Ed.: update the date below with the date of RFC publication and
remove this note. remove this note.
<CODE BEGINS> file "ietf-ip@2017-08-21.yang" <CODE BEGINS> file "ietf-ip@2017-12-16.yang"
module ietf-ip { module ietf-ip {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-ip"; namespace "urn:ietf:params:xml:ns:yang:ietf-ip";
prefix ip; prefix ip;
import ietf-interfaces { import ietf-interfaces {
prefix if; prefix if;
} }
import ietf-inet-types { import ietf-inet-types {
prefix inet; prefix inet;
} }
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
} }
organization organization
"IETF NETMOD (NETCONF Data Modeling Language) Working Group"; "IETF NETMOD (Network Modeling) Working Group";
contact contact
"WG Web: <http://tools.ietf.org/wg/netmod/> "WG Web: <http://tools.ietf.org/wg/netmod/>
WG List: <mailto:netmod@ietf.org> WG List: <mailto:netmod@ietf.org>
Editor: Martin Bjorklund Editor: Martin Bjorklund
<mailto:mbj@tail-f.com>"; <mailto:mbj@tail-f.com>";
description description
"This module contains a collection of YANG definitions for "This module contains a collection of YANG definitions for
managing IP implementations. managing IP implementations.
skipping to change at page 8, line 40 skipping to change at page 8, line 40
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 without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions set 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 This version of this YANG module is part of RFC XXXX; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
revision 2017-08-21 { revision 2017-12-16 {
description description
"Updated to support NMDA."; "Updated to support NMDA.";
reference reference
"RFC XXXX: A YANG Data Model for IP Management"; "RFC XXXX: A YANG Data Model for IP Management";
} }
revision 2014-06-16 { revision 2014-06-16 {
description description
"Initial revision."; "Initial revision.";
reference reference
skipping to change at page 27, line 39 skipping to change at page 27, line 39
7. Acknowledgments 7. Acknowledgments
The author wishes to thank Jeffrey Lange, Ladislav Lhotka, Juergen The author wishes to thank Jeffrey Lange, Ladislav Lhotka, Juergen
Schoenwaelder, and Dave Thaler for their helpful comments. Schoenwaelder, and Dave Thaler for their helpful comments.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.bjorklund-netmod-rfc7223bis]
Bjorklund, M., "A YANG Data Model for Interface
Configuration", draft-bjorklund-netmod-rfc7223bis-00 (work
in progress), August 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-03 Architecture", draft-ietf-netmod-revised-datastores-07
(work in progress), July 2017. (work in progress), November 2017.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [I-D.ietf-netmod-rfc7223bis]
DOI 10.17487/RFC0791, September 1981, <https://www.rfc- Bjorklund, M., "A YANG Data Model for Interface
Management", draft-ietf-netmod-rfc7223bis-00 (work in
progress), October 2017.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, DOI
10.17487/RFC0791, September 1981, <https://www.rfc-
editor.org/info/rfc791>. editor.org/info/rfc791>.
[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/
DOI 10.17487/RFC2119, March 1997, <https://www.rfc- RFC2119, March 1997, <https://www.rfc-editor.org/info/
editor.org/info/rfc2119>. rfc2119>.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460,
December 1998, <https://www.rfc-editor.org/info/rfc2460>. December 1998, <https://www.rfc-editor.org/info/rfc2460>.
[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>.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
"Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
DOI 10.17487/RFC4861, September 2007, <https://www.rfc- DOI 10.17487/RFC4861, September 2007, <https://www.rfc-
editor.org/info/rfc4861>. editor.org/info/rfc4861>.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, Address Autoconfiguration", RFC 4862, DOI 10.17487/
DOI 10.17487/RFC4862, September 2007, <https://www.rfc- RFC4862, September 2007, <https://www.rfc-editor.org/info/
editor.org/info/rfc4862>. rfc4862>.
[RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy [RFC4941] Narten, T., Draves, R., and S. Krishnan, "Privacy
Extensions for Stateless Address Autoconfiguration in Extensions for Stateless Address Autoconfiguration in
IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007, IPv6", RFC 4941, DOI 10.17487/RFC4941, September 2007,
<https://www.rfc-editor.org/info/rfc4941>. <https://www.rfc-editor.org/info/rfc4941>.
[RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for
the Network Configuration Protocol (NETCONF)", RFC 6020, the Network Configuration Protocol (NETCONF)", RFC 6020,
DOI 10.17487/RFC6020, October 2010, <https://www.rfc- DOI 10.17487/RFC6020, October 2010, <https://www.rfc-
editor.org/info/rfc6020>. editor.org/info/rfc6020>.
[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>.
[RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", [RFC6991] Schoenwaelder, J., Ed., "Common YANG Data Types", RFC
RFC 6991, DOI 10.17487/RFC6991, July 2013, 6991, DOI 10.17487/RFC6991, July 2013, <https://www.rfc-
<https://www.rfc-editor.org/info/rfc6991>. 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>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[I-D.ietf-netmod-yang-tree-diagrams]
Bjorklund, M. and L. Berger, "YANG Tree Diagrams", draft-
ietf-netmod-yang-tree-diagrams-02 (work in progress),
October 2017.
[RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or [RFC0826] Plummer, D., "Ethernet Address Resolution Protocol: Or
Converting Network Protocol Addresses to 48.bit Ethernet Converting Network Protocol Addresses to 48.bit Ethernet
Address for Transmission on Ethernet Hardware", STD 37, Address for Transmission on Ethernet Hardware", STD 37,
RFC 826, DOI 10.17487/RFC0826, November 1982, RFC 826, DOI 10.17487/RFC0826, November 1982,
<https://www.rfc-editor.org/info/rfc826>. <https://www.rfc-editor.org/info/rfc826>.
[RFC4293] Routhier, S., Ed., "Management Information Base for the [RFC4293] Routhier, S., Ed., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, DOI 10.17487/RFC4293, Internet Protocol (IP)", RFC 4293, DOI 10.17487/RFC4293,
April 2006, <https://www.rfc-editor.org/info/rfc4293>. April 2006, <https://www.rfc-editor.org/info/rfc4293>.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011,
<https://www.rfc-editor.org/info/rfc6242>. <https://www.rfc-editor.org/info/rfc6242>.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536, Protocol (NETCONF) Access Control Model", RFC 6536, DOI
DOI 10.17487/RFC6536, March 2012, <https://www.rfc- 10.17487/RFC6536, March 2012, <https://www.rfc-
editor.org/info/rfc6536>. editor.org/info/rfc6536>.
[RFC7217] Gont, F., "A Method for Generating Semantically Opaque [RFC7217] Gont, F., "A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless Address Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)", RFC 7217, Autoconfiguration (SLAAC)", RFC 7217, DOI 10.17487/
DOI 10.17487/RFC7217, April 2014, <https://www.rfc- RFC7217, April 2014, <https://www.rfc-editor.org/info/
editor.org/info/rfc7217>. rfc7217>.
[RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing [RFC8022] Lhotka, L. and A. Lindem, "A YANG Data Model for Routing
Management", RFC 8022, DOI 10.17487/RFC8022, November Management", RFC 8022, DOI 10.17487/RFC8022, November
2016, <https://www.rfc-editor.org/info/rfc8022>. 2016, <https://www.rfc-editor.org/info/rfc8022>.
Appendix A. Example: NETCONF <get-config> reply Appendix A. Example: NETCONF <get-config> reply
This section gives an example of a reply to the NETCONF <get-config> This section gives an example of a reply to the NETCONF <get-config>
request for the running configuration datastore for a device that request for the running configuration datastore for a device that
implements the data model defined in this document. implements the data model defined in this document.
skipping to change at page 31, line 5 skipping to change at page 31, line 5
<interfaces <interfaces
xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces" xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"
xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type" xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type"
xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin"> xmlns:or="urn:ietf:params:xml:ns:yang:ietf-origin">
<interface or:origin="or:intended"> <interface or:origin="or:intended">
<name>eth0</name> <name>eth0</name>
<type>ianaift:ethernetCsmacd</type> <type>ianaift:ethernetCsmacd</type>
<!-- other parameters from ietf-interfaces omitted --> <!-- other parameters from ietf-interfaces omitted -->
<ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<forwarding>false</forwarding> <enabled or:origin="or:default">true</enabled>
<mtu>1500</mtu> <forwarding or:origin="or:default">false</forwarding>
<mtu or:origin="or:system">1500</mtu>
<address> <address>
<ip>192.0.2.1</ip> <ip>192.0.2.1</ip>
<prefix-length>24</prefix-length> <prefix-length>24</prefix-length>
<origin>static</origin> <origin>static</origin>
</address> </address>
<neighbor> <neighbor or:origin="or:learned">
<ip>192.0.2.2</ip> <ip>192.0.2.2</ip>
<link-layer-address> <link-layer-address>
00:01:02:03:04:05 00:01:02:03:04:05
</link-layer-address> </link-layer-address>
</neighbor> </neighbor>
</ipv4> </ipv4>
<ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<forwarding>false</forwarding> <enabled or:origin="or:default">true</enabled>
<forwarding or:origin="or:default">false</forwarding>
<mtu>1280</mtu> <mtu>1280</mtu>
<address> <address>
<ip>2001:db8::10</ip> <ip>2001:db8::10</ip>
<prefix-length>32</prefix-length> <prefix-length>32</prefix-length>
<origin>static</origin> <origin>static</origin>
<status>preferred</status> <status>preferred</status>
</address> </address>
<address or:origin="or:learned"> <address or:origin="or:learned">
<ip>2001:db8::1:100</ip> <ip>2001:db8::1:100</ip>
<prefix-length>32</prefix-length> <prefix-length>32</prefix-length>
 End of changes. 26 change blocks. 
111 lines changed or deleted 86 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/