draft-ietf-netmod-ip-cfg-09.txt   rfc7277.txt 
Network Working Group M. Bjorklund Internet Engineering Task Force (IETF) M. Bjorklund
Internet-Draft Tail-f Systems Request for Comments: 7277 Tail-f Systems
Intended status: Standards Track February 11, 2013 Category: Standards Track June 2014
Expires: August 15, 2013 ISSN: 2070-1721
A YANG Data Model for IP Management A YANG Data Model for IP Management
draft-ietf-netmod-ip-cfg-09
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. implementations. The data model includes configuration data and
state data.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This is an Internet Standards Track document.
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on August 15, 2013. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7277.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology ................................................2
2. IP Data Model . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Diagrams ..............................................3
3. Relationship to IP-MIB . . . . . . . . . . . . . . . . . . . . 6 2. IP Data Model ...................................................3
4. IP configuration YANG Module . . . . . . . . . . . . . . . . . 7 3. Relationship to the IP-MIB ......................................6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 4. IP Management YANG Module .......................................8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations ............................................24
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations ........................................24
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. Acknowledgments ................................................25
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8. References .....................................................25
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.1. Normative References ......................................25
Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 21 8.2. Informative References ....................................26
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Example: NETCONF <get> Reply ..........................28
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for management of This document defines a YANG [RFC6020] data model for management of
IP implementations. IP implementations.
The initial version of this data model focuses on configuration The data model covers configuration of per-interface IPv4 and IPv6
parameters for interfaces. Future revisions of this data model might parameters, and mappings of IP addresses to link-layer addresses. It
add other kinds of IP parameters. also provides information about which IP addresses are operationally
used, and which link-layer mappings exist. Per-interface parameters
Parameters to manage IP routing are defined in are added through augmentation of the interface data model defined in
[I-D.ietf-netmod-routing-cfg]. [RFC7223].
1.1. Terminology 1.1. 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].
The following terms are defined in [RFC6241] and are not redefined The following terms are defined in [RFC6241] and are not redefined
here: here:
o client o client
o configuration data
o server o server
o state data
The following terms are defined in [RFC6020] and are not redefined The following terms are defined in [RFC6020] and are not redefined
here: here:
o augment o augment
o data model o data model
o data node o data node
The terminology for describing YANG data models is found in
[RFC6020].
1.2. Tree Diagrams
A simplified graphical representation of the data model is used in
this document. The meaning of the symbols in these diagrams is as
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
The module "ietf-ip" augments the "interface" list defined in the This document defines the YANG module "ietf-ip", which augments the
"ietf-interfaces" module [I-D.ietf-netmod-interfaces-cfg] with the "interface" and "interface-state" lists defined in the
following data nodes, where square brackets are used to enclose a "ietf-interfaces" module [RFC7223] with IP-specific data nodes, and
list's keys, and "?" means that the node is optional. Choice and also adds IP-specific state data.
case nodes are enclosed in parenthesis, and a case node is marked
with a colon (":").
+--rw if:interfaces The data model has the following structure for IP configuration per
+--rw if:interface [name] interface:
...
+--rw ipv4?
| +--rw enabled? boolean
| +--rw forwarding? boolean
| +--rw mtu? uint16
| +--rw address [ip]
| | +--rw ip inet:ipv4-address-no-zone
| | +--rw (subnet)
| | +--:(prefix-length)
| | | +--rw ip:prefix-length? uint8
| | +--:(netmask)
| | +--rw ip:netmask? yang:dotted-quad
| +--rw neighbor [ip]
| +--rw ip inet:ipv4-address-no-zone
| +--rw phys-address? yang:phys-address
+--rw ipv6?
+--rw enabled? boolean
+--rw forwarding? boolean
+--rw mtu? uint32
+--rw address [ip]
| +--rw ip inet:ipv6-address-no-zone
| +--rw prefix-length uint8
+--rw neighbor [ip]
| +--rw ip inet:ipv6-address-no-zone
| +--rw phys-address? yang:phys-address
+--rw dup-addr-detect-transmits? uint32
+--rw autoconf
+--rw create-global-addresses? boolean
+--rw create-temporary-addresses? boolean
+--rw temporary-valid-lifetime? uint32
+--rw temporary-preferred-lifetime? uint32
The data model defines two containers, "ipv4" and "ipv6", +--rw if:interfaces
representing the IPv4 and IPv6 address families. In each container, +--rw if:interface* [name]
there is a leaf "enabled" that controls if the address family is ...
enabled on that interface, and a leaf "forwarding" that controls if +--rw ipv4!
ip packet forwarding for the address family is enabled on the | +--rw enabled? boolean
interface. In each container, there is also a list of addresses, and | +--rw forwarding? boolean
a list of mappings from ip addresses to physical addresses. | +--rw mtu? uint16
| +--rw address* [ip]
| | +--rw ip inet:ipv4-address-no-zone
| | +--rw (subnet)
| | +--:(prefix-length)
| | | +--rw ip:prefix-length? uint8
| | +--:(netmask)
| | +--rw ip:netmask? yang:dotted-quad
| +--rw neighbor* [ip]
| +--rw ip inet:ipv4-address-no-zone
| +--rw link-layer-address yang:phys-address
+--rw ipv6!
+--rw enabled? boolean
+--rw forwarding? boolean
+--rw mtu? uint32
+--rw address* [ip]
| +--rw ip inet:ipv6-address-no-zone
| +--rw prefix-length uint8
+--rw neighbor* [ip]
| +--rw ip inet:ipv6-address-no-zone
| +--rw link-layer-address yang:phys-address
+--rw dup-addr-detect-transmits? uint32
+--rw autoconf
+--rw create-global-addresses? boolean
+--rw create-temporary-addresses? boolean
+--rw temporary-valid-lifetime? uint32
+--rw temporary-preferred-lifetime? uint32
3. Relationship to IP-MIB The data model defines two configuration containers per interface --
"ipv4" and "ipv6", representing the IPv4 and IPv6 address families.
In each container, there is a leaf "enabled" that controls whether or
not the address family is enabled on that interface, and a leaf
"forwarding" that controls whether or not IP packet forwarding for
the address family is enabled on the interface. In each container,
there is also a list of configured addresses, and a list of
configured mappings from IP addresses to link-layer addresses.
If the device implements IP-MIB [RFC4293], each entry in the "ipv4/ The data model has the following structure for IP state per
address" and "ipv6/address" lists is mapped to one ipAddressEntry, interface:
where the ipAddressIfIndex refers to the "address" entry's interface.
The IP-MIB defines objects to control IPv6 Router Advertisement. The +--ro if:interfaces-state
corresponding YANG data nodes are defined in +--ro if:interface* [name]
[I-D.ietf-netmod-routing-cfg]. ...
+--ro ipv4!
| +--ro forwarding? boolean
| +--ro mtu? uint16
| +--ro address* [ip]
| | +--ro ip inet:ipv4-address-no-zone
| | +--ro (subnet)?
| | | +--:(prefix-length)
| | | | +--ro prefix-length? uint8
| | | +--:(netmask)
| | | +--ro netmask? yang:dotted-quad
| | +--ro origin? ip-address-origin
| +--ro neighbor* [ip]
| +--ro ip inet:ipv4-address-no-zone
| +--ro link-layer-address? yang:phys-address
| +--ro origin? neighbor-origin
+--ro ipv6!
+--ro forwarding? boolean
+--ro mtu? uint32
+--ro address* [ip]
| +--ro ip inet:ipv6-address-no-zone
| +--ro prefix-length uint8
| +--ro origin? ip-address-origin
| +--ro status? enumeration
+--ro neighbor* [ip]
+--ro ip inet:ipv6-address-no-zone
+--ro link-layer-address? yang:phys-address
+--ro origin? neighbor-origin
+--ro is-router? empty
+--ro state? enumeration
The data model defines two state containers per interface -- "ipv4"
and "ipv6", representing the IPv4 and IPv6 address families. In each
container, there is a leaf "forwarding" that indicates whether or not
IP packet forwarding is enabled on that interface. In each
container, there is also a list of all addresses in use and a list of
known mappings from IP addresses to link-layer addresses.
3. Relationship to the IP-MIB
If the device implements the IP-MIB [RFC4293], each entry in the
"ipv4/address" and "ipv6/address" lists is mapped to one
ipAddressEntry, where the ipAddressIfIndex refers to the "address"
entry's interface.
The IP-MIB defines objects to control IPv6 Router Advertisement
messages. The corresponding YANG data nodes are defined in
[ROUTING-MGMT].
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 object ipAddressStatus is writable in the IP-MIB but does not The following tables list the YANG data nodes with corresponding
represent configuration, and is thus not mapped to the YANG module.
The following table lists the YANG data nodes with corresponding
objects in the IP-MIB. objects in the IP-MIB.
+-----------------+-----------------------------------+ +----------------------------------+--------------------------------+
| YANG data node | IP-MIB object | | YANG data node in | IP-MIB object |
+-----------------+-----------------------------------+ | /if:interfaces/if:interface | |
| ipv4/enabled | ipv4InterfaceEnableStatus | +----------------------------------+--------------------------------+
| ipv4/address | ipAddressEntry | | ipv4/enabled | ipv4InterfaceEnableStatus |
| ipv4/address/ip | ipAddressAddrType / ipAddressAddr | | ipv4/address | ipAddressEntry |
| ipv4/neighbor | ipNetToPhysicalTable | | ipv4/address/ip | ipAddressAddrType |
| ipv6/enabled | ipv6InterfaceEnableStatus | | | ipAddressAddr |
| ipv6/forwarding | ipv6InterfaceForwarding | | ipv4/neighbor | ipNetToPhysicalEntry |
| ipv6/address | ipAddressEntry | | ipv4/neighbor/ip | ipNetToPhysicalNetAddressType |
| ipv6/address/ip | ipAddressAddrType / ipAddressAddr | | | ipNetToPhysicalNetAddress |
| ipv6/neighbor | ipNetToPhysicalTable | | ipv4/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
+-----------------+-----------------------------------+ | | |
| ipv6/enabled | ipv6InterfaceEnableStatus |
| ipv6/forwarding | ipv6InterfaceForwarding |
| ipv6/address | ipAddressEntry |
| ipv6/address/ip | ipAddressAddrType |
| | ipAddressAddr |
| ipv6/neighbor | ipNetToPhysicalEntry |
| ipv6/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| ipv6/neighbor/origin | ipNetToPhysicalType |
+----------------------------------+--------------------------------+
Mapping of YANG data nodes to IP-MIB objects YANG Interface Configuration Data Nodes and Related IP-MIB Objects
4. IP configuration YANG Module +-----------------------------------+-------------------------------+
| YANG data node in | IP-MIB object |
| /if:interfaces-state/if:interface | |
+-----------------------------------+-------------------------------+
| ipv4 | ipv4InterfaceEnableStatus |
| ipv4/address | ipAddressEntry |
| ipv4/address/ip | ipAddressAddrType |
| | ipAddressAddr |
| ipv4/address/origin | ipAddressOrigin |
| ipv4/neighbor | ipNetToPhysicalEntry |
| ipv4/neighbor/ip | ipNetToPhysicalNetAddressType |
| | ipNetToPhysicalNetAddress |
| ipv4/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| ipv4/neighbor/origin | ipNetToPhysicalType |
| | |
| ipv6 | ipv6InterfaceEnableStatus |
| ipv6/forwarding | ipv6InterfaceForwarding |
| ipv6/address | ipAddressEntry |
| ipv6/address/ip | ipAddressAddrType |
| | ipAddressAddr |
| ipv6/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 |
+-----------------------------------+-------------------------------+
This module imports typedefs from [I-D.ietf-netmod-rfc6021-bis] and YANG Interface State Data Nodes and Related IP-MIB Objects
[I-D.ietf-netmod-interfaces-cfg], and references [RFC0791],
[RFC0826], [RFC2460], [RFC4861], [RFC4862], and [RFC4941].
RFC Ed.: update the date below with the date of RFC publication and 4. IP Management YANG Module
remove this note.
<CODE BEGINS> file "ietf-ip@2013-02-11.yang" This module imports typedefs from [RFC6991] and [RFC7223], and it
references [RFC0791], [RFC0826], [RFC2460], [RFC4861], [RFC4862],
[RFC4941], and [RFC7217].
<CODE BEGINS> file "ietf-ip@2014-06-16.yang"
module ietf-ip { module ietf-ip {
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 (NETCONF Data Modeling Language) 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>
WG Chair: David Kessens WG Chair: Thomas Nadeau
<mailto:david.kessens@nsn.com> <mailto:tnadeau@lucidvision.com>
WG Chair: Juergen Schoenwaelder WG Chair: Juergen Schoenwaelder
<mailto:j.schoenwaelder@jacobs-university.de> <mailto:j.schoenwaelder@jacobs-university.de>
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
configuring IP implementations. configuring IP implementations.
Copyright (c) 2012 IETF Trust and the persons identified as Copyright (c) 2014 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 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 7277; see
the RFC itself for full legal notices."; the RFC itself for full legal notices.";
// RFC Ed.: replace XXXX with actual RFC number and remove this revision 2014-06-16 {
// note. description
"Initial revision.";
reference
"RFC 7277: A YANG Data Model for IP Management";
}
// RFC Ed.: update the date below with the date of RFC publication /*
// and remove this note.
revision 2013-02-11 {
description
"Initial revision.";
reference
"RFC XXXX: A YANG Data Model for IP Management";
}
/* Features */ * Features
*/
feature ipv4-non-contiguous-netmasks { feature ipv4-non-contiguous-netmasks {
description description
"Indicates support for configuring non-contiguous "Indicates support for configuring non-contiguous
subnet masks."; subnet masks.";
} }
feature ipv6-privacy-autoconf { feature ipv6-privacy-autoconf {
description description
"Indicates support for Privacy Extensions for Stateless Address "Indicates support for Privacy Extensions for Stateless Address
Autoconfiguration in IPv6."; Autoconfiguration in IPv6.";
reference reference
"RFC 4941: Privacy Extensions for Stateless Address "RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6"; Autoconfiguration in IPv6";
} }
/*
* Typedefs
*/
/* Data nodes */ typedef ip-address-origin {
type enumeration {
enum other {
description
"None of the following.";
}
enum static {
description
"Indicates that the address has been statically
configured - for example, using NETCONF or a Command Line
Interface.";
}
enum dhcp {
description
"Indicates an address that has been assigned to this
system by a DHCP server.";
}
enum link-layer {
description
"Indicates an address created by IPv6 stateless
autoconfiguration that embeds a link-layer address in its
interface identifier.";
}
enum random {
description
"Indicates an address chosen by the system at
augment "/if:interfaces/if:interface" { random, e.g., an IPv4 address within 169.254/16, an
description RFC 4941 temporary address, or an RFC 7217 semantically
"Parameters for configuring IP on interfaces. opaque address.";
reference
"RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6
RFC 7217: A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless
Address Autoconfiguration (SLAAC)";
}
}
description
"The origin of an address.";
}
typedef neighbor-origin {
type enumeration {
enum other {
description
"None of the following.";
}
enum static {
description
"Indicates that the mapping has been statically
configured - for example, using NETCONF or a Command Line
Interface.";
}
enum dynamic {
description
"Indicates that the mapping has been dynamically resolved
using, e.g., IPv4 ARP or the IPv6 Neighbor Discovery
protocol.";
}
}
description
"The origin of a neighbor entry.";
}
If an interface is not capable of running IP, the server /*
must not allow the client to configure these parameters."; * Configuration data nodes
*/
container ipv4 { augment "/if:interfaces/if:interface" {
presence "Configure IPv4 on this interface."; description
description "Parameters for configuring IP on interfaces.
"Parameters for the IPv4 address family.";
leaf enabled { If an interface is not capable of running IP, the server
type boolean; must not allow the client to configure these parameters.";
default true;
description
"Controls if IPv4 is enabled or disabled on this
interface.";
}
leaf forwarding {
type boolean;
default false;
description
"Controls if IPv4 packet forwarding is enabled or disabled
on this interface.";
}
leaf mtu {
type uint16 {
range "68..max";
}
units octets;
description
"The size, in octets, of the largest IPv4 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf container ipv4 {
depending on the interface's type. presence
"Enables IPv4 unless the 'enabled' leaf
(which defaults to 'true') is set to 'false'";
description
"Parameters for the IPv4 address family.";
If this leaf is not configured, the operationally used mtu leaf enabled {
depends on the interface's type."; type boolean;
reference default true;
"RFC 791: Internet Protocol"; description
} "Controls whether IPv4 is enabled or disabled on this
list address { interface. When IPv4 is enabled, this interface is
key "ip"; connected to an IPv4 stack, and the interface can send
description and receive IPv4 packets.";
"The list of IPv4 addresses on the interface."; }
leaf forwarding {
type boolean;
default false;
description
"Controls IPv4 packet forwarding of datagrams received by,
but not addressed to, this interface. IPv4 routers
forward datagrams. IPv4 hosts do not (except those
source-routed via the host).";
}
leaf mtu {
type uint16 {
range "68..max";
}
units octets;
description
"The size, in octets, of the largest IPv4 packet that the
interface will send and receive.
leaf ip { The server may restrict the allowed values for this leaf,
type inet:ipv4-address-no-zone; depending on the interface's type.
description
"The IPv4 address on the interface.";
}
choice subnet {
mandatory true;
description
"The subnet can be specified as a prefix-length, or,
if the server supports non-contiguous netmasks, as
a netmask.";
leaf prefix-length {
type uint8 {
range "0..32";
}
description
"The length of the subnet prefix.";
}
leaf netmask {
if-feature ipv4-non-contiguous-netmasks;
type yang:dotted-quad;
description
"The subnet specified as a netmask.";
}
}
}
list neighbor {
key "ip";
description
"A list of mappings from IPv4
addresses to physical addresses.
Entries in this list are used as static entries in the If this leaf is not configured, the operationally used MTU
ARP cache."; depends on the interface's type.";
reference reference
"RFC 826: An Ethernet Address Resolution Protocol"; "RFC 791: Internet Protocol";
}
list address {
key "ip";
description
"The list of configured IPv4 addresses on the interface.";
leaf ip { leaf ip {
type inet:ipv4-address-no-zone; type inet:ipv4-address-no-zone;
description description
"The IPv4 address of a neighbor node."; "The IPv4 address on the interface.";
} }
leaf phys-address { choice subnet {
type yang:phys-address; mandatory true;
description description
"The physical level address of the neihgbor node."; "The subnet can be specified as a prefix-length, or,
} if the server supports non-contiguous netmasks, as
} a netmask.";
leaf prefix-length {
type uint8 {
range "0..32";
}
description
"The length of the subnet prefix.";
}
leaf netmask {
if-feature ipv4-non-contiguous-netmasks;
type yang:dotted-quad;
description
"The subnet specified as a netmask.";
}
}
}
list neighbor {
key "ip";
description
"A list of mappings from IPv4 addresses to
link-layer addresses.
} Entries in this list are used as static entries in the
container ipv6 { ARP Cache.";
presence "Configure IPv6 on this interface."; reference
description "RFC 826: An Ethernet Address Resolution Protocol";
"Parameters for the IPv6 address family.";
leaf enabled { leaf ip {
type boolean; type inet:ipv4-address-no-zone;
default true; description
description "The IPv4 address of the neighbor node.";
"Controls if IPv6 is enabled or disabled on this }
interface."; leaf link-layer-address {
} type yang:phys-address;
leaf forwarding { mandatory true;
type boolean; description
default false; "The link-layer address of the neighbor node.";
description }
"Controls if IPv6 packet forwarding is enabled or disabled }
on this interface.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Section 6.2.1, IsRouter";
}
leaf mtu {
type uint32 {
range "1280..max";
}
units octets;
description
"The size, in octets, of the largest IPv6 packet that the
interface will send and receive.
The server may restrict the allowed values for this leaf }
depending on the interface's type. container ipv6 {
presence
"Enables IPv6 unless the 'enabled' leaf
(which defaults to 'true') is set to 'false'";
description
"Parameters for the IPv6 address family.";
If this leaf is not configured, the operationally used mtu leaf enabled {
depends on the interface's type."; type boolean;
reference default true;
"RFC 2460: IPv6 Specification description
Section 5"; "Controls whether IPv6 is enabled or disabled on this
} interface. When IPv6 is enabled, this interface is
list address { connected to an IPv6 stack, and the interface can send
key "ip"; and receive IPv6 packets.";
description }
"The list of IPv6 addresses on the interface."; leaf forwarding {
type boolean;
default false;
description
"Controls IPv6 packet forwarding of datagrams received by,
but not addressed to, this interface. IPv6 routers
forward datagrams. IPv6 hosts do not (except those
source-routed via the host).";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Section 6.2.1, IsRouter";
}
leaf mtu {
type uint32 {
range "1280..max";
}
units octets;
description
"The size, in octets, of the largest IPv6 packet that the
interface will send and receive.
leaf ip { The server may restrict the allowed values for this leaf,
type inet:ipv6-address-no-zone; depending on the interface's type.
description
"The IPv6 address on the interface.";
}
leaf prefix-length {
type uint8 {
range "0..128";
} If this leaf is not configured, the operationally used MTU
mandatory true; depends on the interface's type.";
description reference
"The length of the subnet prefix."; "RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
} Section 5";
} }
list neighbor { list address {
key "ip"; key "ip";
description description
"A list of mappings from IPv6 "The list of configured IPv6 addresses on the interface.";
addresses to physical addresses.
Entries in this list are used as static entries in the leaf ip {
Neighbor Cache."; type inet:ipv6-address-no-zone;
reference description
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)"; "The IPv6 address on the interface.";
}
leaf prefix-length {
type uint8 {
range "0..128";
}
mandatory true;
description
"The length of the subnet prefix.";
}
}
list neighbor {
key "ip";
description
"A list of mappings from IPv6 addresses to
link-layer addresses.
leaf ip { Entries in this list are used as static entries in the
type inet:ipv6-address-no-zone; Neighbor Cache.";
description reference
"The IPv6 address of a neighbor node."; "RFC 4861: Neighbor Discovery for IP version 6 (IPv6)";
}
leaf phys-address {
type yang:phys-address;
description
"The physical level address of the neighbor node.";
}
}
leaf dup-addr-detect-transmits {
type uint32;
default 1;
description
"The number of consecutive Neighbor Solicitation messages
sent while performing Duplicate Address Detection on a
tentative address. A value of zero indicates that
Duplicate Address Detection is not performed on
tentative addresses. A value of one indicates a single
transmission with no follow-up retransmissions.";
reference
"RFC 4862: IPv6 Stateless Address Autoconfiguration";
}
container autoconf {
description
"Parameters to control the autoconfiguration of IPv6
addresses, as described in RFC 4862.";
reference
"RFC 4862: IPv6 Stateless Address Autoconfiguration";
leaf create-global-addresses { leaf ip {
type boolean; type inet:ipv6-address-no-zone;
default true; description
description "The IPv6 address of the neighbor node.";
"If enabled, the host creates global addresses as }
described in section 5.5 of RFC 4862."; leaf link-layer-address {
reference type yang:phys-address;
"RFC 4862: IPv6 Stateless Address Autoconfiguration"; mandatory true;
} description
leaf create-temporary-addresses { "The link-layer address of the neighbor node.";
if-feature ipv6-privacy-autoconf; }
type boolean; }
default false; leaf dup-addr-detect-transmits {
description type uint32;
"If enabled, the host creates temporary addresses as default 1;
described in RFC 4941."; description
reference "The number of consecutive Neighbor Solicitation messages
"RFC 4941: Privacy Extensions for Stateless Address sent while performing Duplicate Address Detection on a
Autoconfiguration in IPv6"; tentative address. A value of zero indicates that
} Duplicate Address Detection is not performed on
leaf temporary-valid-lifetime { tentative addresses. A value of one indicates a single
if-feature ipv6-privacy-autoconf; transmission with no follow-up retransmissions.";
type uint32; reference
units "seconds"; "RFC 4862: IPv6 Stateless Address Autoconfiguration";
default 604800; }
description container autoconf {
"The time period during which the temporary address description
is valid."; "Parameters to control the autoconfiguration of IPv6
reference addresses, as described in RFC 4862.";
"RFC 4941: Privacy Extensions for Stateless Address reference
Autoconfiguration in IPv6 "RFC 4862: IPv6 Stateless Address Autoconfiguration";
- TEMP_VALID_LIFETIME";
}
leaf temporary-preferred-lifetime {
if-feature ipv6-privacy-autoconf;
type uint32;
units "seconds";
default 86400;
description
"The time period during which the temporary address is
preferred.";
reference
"RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6
- TEMP_PREFERED_LIFETIME";
}
}
}
} leaf create-global-addresses {
type boolean;
default true;
description
"If enabled, the host creates global addresses as
described in RFC 4862.";
reference
"RFC 4862: IPv6 Stateless Address Autoconfiguration
Section 5.5";
}
leaf create-temporary-addresses {
if-feature ipv6-privacy-autoconf;
type boolean;
default false;
description
"If enabled, the host creates temporary addresses as
described in RFC 4941.";
reference
"RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6";
}
leaf temporary-valid-lifetime {
if-feature ipv6-privacy-autoconf;
type uint32;
units "seconds";
default 604800;
description
"The time period during which the temporary address
is valid.";
reference
"RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6
- TEMP_VALID_LIFETIME";
}
leaf temporary-preferred-lifetime {
if-feature ipv6-privacy-autoconf;
type uint32;
units "seconds";
default 86400;
description
"The time period during which the temporary address is
preferred.";
reference
"RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6
- TEMP_PREFERRED_LIFETIME";
}
}
}
}
/*
* Operational state data nodes
*/
augment "/if:interfaces-state/if:interface" {
description
"Data nodes for the operational state of IP on interfaces.";
container ipv4 {
presence "Present if IPv4 is enabled on this interface";
config false;
description
"Interface-specific parameters for the IPv4 address family.";
leaf forwarding {
type boolean;
description
"Indicates whether IPv4 packet forwarding is enabled or
disabled on this interface.";
}
leaf mtu {
type uint16 {
range "68..max";
}
units octets;
description
"The size, in octets, of the largest IPv4 packet that the
interface will send and receive.";
reference
"RFC 791: Internet Protocol";
}
list address {
key "ip";
description
"The list of IPv4 addresses on the interface.";
leaf ip {
type inet:ipv4-address-no-zone;
description
"The IPv4 address on the interface.";
}
choice subnet {
description
"The subnet can be specified as a prefix-length, or,
if the server supports non-contiguous netmasks, as
a netmask.";
leaf prefix-length {
type uint8 {
range "0..32";
}
description
"The length of the subnet prefix.";
}
leaf netmask {
if-feature ipv4-non-contiguous-netmasks;
type yang:dotted-quad;
description
"The subnet specified as a netmask.";
}
}
leaf origin {
type ip-address-origin;
description
"The origin of this address.";
}
}
list neighbor {
key "ip";
description
"A list of mappings from IPv4 addresses to
link-layer addresses.
This list represents the ARP Cache.";
reference
"RFC 826: An Ethernet Address Resolution Protocol";
leaf ip {
type inet:ipv4-address-no-zone;
description
"The IPv4 address of the neighbor node.";
}
leaf link-layer-address {
type yang:phys-address;
description
"The link-layer address of the neighbor node.";
}
leaf origin {
type neighbor-origin;
description
"The origin of this neighbor entry.";
}
}
}
container ipv6 {
presence "Present if IPv6 is enabled on this interface";
config false;
description
"Parameters for the IPv6 address family.";
leaf forwarding {
type boolean;
default false;
description
"Indicates whether IPv6 packet forwarding is enabled or
disabled on this interface.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Section 6.2.1, IsRouter";
}
leaf mtu {
type uint32 {
range "1280..max";
}
units octets;
description
"The size, in octets, of the largest IPv6 packet that the
interface will send and receive.";
reference
"RFC 2460: Internet Protocol, Version 6 (IPv6) Specification
Section 5";
}
list address {
key "ip";
description
"The list of IPv6 addresses on the interface.";
leaf ip {
type inet:ipv6-address-no-zone;
description
"The IPv6 address on the interface.";
}
leaf prefix-length {
type uint8 {
range "0..128";
}
mandatory true;
description
"The length of the subnet prefix.";
}
leaf origin {
type ip-address-origin;
description
"The origin of this address.";
}
leaf status {
type enumeration {
enum preferred {
description
"This is a valid address that can appear as the
destination or source address of a packet.";
}
enum deprecated {
description
"This is a valid but deprecated address that should
no longer be used as a source address in new
communications, but packets addressed to such an
address are processed as expected.";
}
enum invalid {
description
"This isn't a valid address, and it shouldn't appear
as the destination or source address of a packet.";
}
enum inaccessible {
description
"The address is not accessible because the interface
to which this address is assigned is not
operational.";
}
enum unknown {
description
"The status cannot be determined for some reason.";
}
enum tentative {
description
"The uniqueness of the address on the link is being
verified. Addresses in this state should not be
used for general communication and should only be
used to determine the uniqueness of the address.";
}
enum duplicate {
description
"The address has been determined to be non-unique on
the link and so must not be used.";
}
enum optimistic {
description
"The address is available for use, subject to
restrictions, while its uniqueness on a link is
being verified.";
}
}
description
"The status of an address. Most of the states correspond
to states from the IPv6 Stateless Address
Autoconfiguration protocol.";
reference
"RFC 4293: Management Information Base for the
Internet Protocol (IP)
- IpAddressStatusTC
RFC 4862: IPv6 Stateless Address Autoconfiguration";
}
}
list neighbor {
key "ip";
description
"A list of mappings from IPv6 addresses to
link-layer addresses.
This list represents the Neighbor Cache.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)";
leaf ip {
type inet:ipv6-address-no-zone;
description
"The IPv6 address of the neighbor node.";
}
leaf link-layer-address {
type yang:phys-address;
description
"The link-layer address of the neighbor node.";
}
leaf origin {
type neighbor-origin;
description
"The origin of this neighbor entry.";
}
leaf is-router {
type empty;
description
"Indicates that the neighbor node acts as a router.";
}
leaf state {
type enumeration {
enum incomplete {
description
"Address resolution is in progress, and the link-layer
address of the neighbor has not yet been
determined.";
}
enum reachable {
description
"Roughly speaking, the neighbor is known to have been
reachable recently (within tens of seconds ago).";
}
enum stale {
description
"The neighbor is no longer known to be reachable, but
until traffic is sent to the neighbor no attempt
should be made to verify its reachability.";
}
enum delay {
description
"The neighbor is no longer known to be reachable, and
traffic has recently been sent to the neighbor.
Rather than probe the neighbor immediately, however,
delay sending probes for a short while in order to
give upper-layer protocols a chance to provide
reachability confirmation.";
}
enum probe {
description
"The neighbor is no longer known to be reachable, and
unicast Neighbor Solicitation probes are being sent
to verify reachability.";
}
}
description
"The Neighbor Unreachability Detection state of this
entry.";
reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)
Section 7.3.2";
}
}
}
}
} }
<CODE ENDS> <CODE ENDS>
5. IANA Considerations 5. IANA Considerations
This document registers a URI in the IETF XML registry [RFC3688]. This document registers a URI in the "IETF XML Registry" [RFC3688].
Following the format in RFC 3688, the following registration is Following the format in RFC 3688, the following registration has been
requested to be made. made.
URI: urn:ietf:params:xml:ns:yang:ietf-ip URI: urn:ietf:params:xml:ns:yang:ietf-ip
Registrant Contact: The NETMOD WG of the IETF. Registrant Contact: The NETMOD WG of the IETF.
XML: N/A, the requested URI is an XML namespace. XML: N/A; the requested URI is an XML namespace.
This document registers a YANG module in the YANG Module Names This document registers a YANG module in the "YANG Module Names"
registry [RFC6020]. registry [RFC6020].
name: ietf-ip Name: ietf-ip
namespace: urn:ietf:params:xml:ns:yang:ietf-ip Namespace: urn:ietf:params:xml:ns:yang:ietf-ip
prefix: ip Prefix: ip
reference: RFC XXXX Reference: RFC 7277
6. Security Considerations 6. Security Considerations
The YANG module defined in this memo is designed to be accessed via The YANG module defined in this memo is designed to be accessed via
the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the the NETCONF protocol [RFC6241]. The lowest NETCONF layer is the
secure transport layer and the mandatory-to-implement secure secure transport layer and the mandatory-to-implement secure
transport is SSH [RFC6242]. transport is SSH [RFC6242]. The NETCONF access control model
[RFC6536] provides the means to restrict access for particular
NETCONF users to a pre-configured subset of all available NETCONF
protocol operations and content.
There are a number of data nodes defined in the YANG module which are There are a number of data nodes defined in the YANG module which are
writable/creatable/deletable (i.e., config true, which is the writable/creatable/deletable (i.e., config true, which is the
default). These data nodes may be considered sensitive or vulnerable default). These data nodes may be considered sensitive or vulnerable
in some network environments. Write operations (e.g., edit-config) in some network environments. Write operations (e.g., edit-config)
to these data nodes without proper protection can have a negative to these data nodes without proper protection can have a negative
effect on network operations. These are the subtrees and data nodes effect on network operations. These are the subtrees and data nodes
and their sensitivity/vulnerability: and their sensitivity/vulnerability:
ipv4/enabled and ipv6/enabled: These leafs are used to enable or ipv4/enabled and ipv6/enabled: These leafs are used to enable or
skipping to change at page 16, line 42 skipping to change at page 25, line 18
or accept (at least at the IP layer) messages it would otherwise or accept (at least at the IP layer) messages it would otherwise
ignore. The use of filtering or security associations may reduce ignore. The use of filtering or security associations may reduce
the potential damage in the latter case. the potential damage in the latter case.
ipv4/forwarding and ipv6/forwarding: These leafs allow a client to ipv4/forwarding and ipv6/forwarding: These leafs allow a client to
enable or disable the forwarding functions on the entity. By enable or disable the forwarding functions on the entity. By
disabling the forwarding functions, an attacker would possibly be disabling the forwarding functions, an attacker would possibly be
able to deny service to users. By enabling the forwarding able to deny service to users. By enabling the forwarding
functions, an attacker could open a conduit into an area. This functions, an attacker could open a conduit into an area. This
might result in the area providing transit for packets it might result in the area providing transit for packets it
shouldn't or might allow the attacker access to the area bypassing shouldn't, or it might allow the attacker access to the area,
security safeguards. bypassing security safeguards.
ipv6/autoconf: The leafs in this branch control the ipv6/autoconf: The leafs in this branch control the
autoconfiguration of IPv6 addresses and in particular whether autoconfiguration of IPv6 addresses and, in particular, whether or
temporary addresses are used or not. By modifying the not temporary addresses are used. By modifying the corresponding
corresponding leafs, an attacker might impact the addresses used leafs, an attacker might impact the addresses used by a node and
by a node and thus indirectly the privacy of the users using the thus indirectly the privacy of the users using the node.
node.
ipv4/mtu and ipv6/mtu: Setting these leafs to very small values can ipv4/mtu and ipv6/mtu: Setting these leafs to very small values can
be used to slow down interfaces. be used to slow down interfaces.
7. Acknowledgments 7. Acknowledgments
The author wishes to thank Ladislav Lhotka, Juergen Schoenwaelder, The author wishes to thank Jeffrey Lange, Ladislav Lhotka, Juergen
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.ietf-netmod-interfaces-cfg]
Bjorklund, M., "A YANG Data Model for Interface
Configuration", draft-ietf-netmod-interfaces-cfg-09 (work
in progress), July 2012.
[I-D.ietf-netmod-rfc6021-bis]
Schoenwaelder, J., "Common YANG Data Types",
draft-ietf-netmod-rfc6021-bis-00 (work in progress),
Feb 2013.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
September 1981. September 1981.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[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,
September 2007. September 2007.
skipping to change at page 19, line 46 skipping to change at page 26, line 16
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[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, September 2007. IPv6", RFC 4941, September 2007.
[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
Network Configuration Protocol (NETCONF)", RFC 6020, Network Configuration Protocol (NETCONF)", RFC 6020,
October 2010. October 2010.
8.2. Informative References [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)",
RFC 6241, June 2011.
[I-D.ietf-netmod-routing-cfg] [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991,
Lhotka, L., "A YANG Data Model for Routing Configuration", July 2013.
draft-ietf-netmod-routing-cfg-04 (work in progress),
July 2012. [RFC7223] Bjorklund, M., "A YANG Data Model for Interface
Management", RFC 7223, May 2014.
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and
F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth
Edition)", W3C Recommendation, November 2008,
<http://www.w3.org/TR/xml/>.
8.2. Informative References
[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, November 1982. RFC 826, November 1982.
[RFC4293] Routhier, S., "Management Information Base for the [RFC4293] Routhier, S., "Management Information Base for the
Internet Protocol (IP)", RFC 4293, April 2006. Internet Protocol (IP)", RFC 4293, April 2006.
[RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)",
RFC 6241, June 2011.
[RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, June 2011. Shell (SSH)", RFC 6242, June 2011.
Appendix A. Example: NETCONF <get> reply [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
March 2012.
[RFC7217] Gont, F., "A Method for Generating Semantically Opaque
Interface Identifiers with IPv6 Stateless Address
Autoconfiguration (SLAAC)", RFC 7217, April 2014.
[ROUTING-MGMT]
Lhotka, L., "A YANG Data Model for Routing Management",
Work in Progress, May 2014.
Appendix A. Example: NETCONF <get> Reply
This section gives an example of a reply to the NETCONF <get> request This section gives an example of a reply to the NETCONF <get> request
for a device that implements the data model defined in this document. for a device that implements the data model defined in this document.
The example is written in XML [XML].
<rpc-reply <rpc-reply
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"
message-id="101"> message-id="101">
<data> <data>
<interfaces <interfaces
xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"> xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"
<interface> xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">
<name>eth0</name> <interface>
<type>ethernetCsmacd</type> <name>eth0</name>
<location>0</location> <type>ianaift:ethernetCsmacd</type>
<if-index>2</if-index> <ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <address>
<address> <ip>192.0.2.1</ip>
<ip>192.0.2.1</ip> <prefix-length>24</prefix-length>
<prefix-length>24</prefix-length> </address>
</address> </ipv4>
</ipv4> <ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip"> <mtu>1280</mtu>
<mtu>1280</mtu> <address>
<address> <ip>2001:db8::10</ip>
<ip>2001:DB8::1</ip> <prefix-length>32</prefix-length>
<prefix-length>32</prefix-length> </address>
</address> <dup-addr-detect-transmits>0</dup-addr-detect-transmits>
<dup-addr-detect-transmits>0</dup-addr-detect-transmits> </ipv6>
</ipv6> </interface>
</interface> </interfaces>
</interfaces>
</data> <interfaces-state
xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces"
xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">
<interface>
<name>eth0</name>
<type>ianaift:ethernetCsmacd</type>
<!-- other parameters from ietf-interfaces omitted -->
<ipv4 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<forwarding>false</forwarding>
<mtu>1500</mtu>
<address>
<ip>192.0.2.1</ip>
<prefix-length>24</prefix-length>
<origin>static</origin>
</address>
<neighbor>
<ip>192.0.2.2</ip>
<link-layer-address>00:01:02:03:04:05</link-layer-address>
</neighbor>
</ipv4>
<ipv6 xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<forwarding>false</forwarding>
<mtu>1500</mtu>
<address>
<ip>2001:db8::10</ip>
<prefix-length>32</prefix-length>
<origin>static</origin>
<status>preferred</status>
</address>
<address>
<ip>2001:db8::1:100</ip>
<prefix-length>32</prefix-length>
<origin>dhcp</origin>
<status>preferred</status>
</address>
<neighbor>
<ip>2001:db8::1</ip>
<link-layer-address>00:01:02:03:04:05</link-layer-address>
<origin>dynamic</origin>
<is-router/>
<state>reachable</state>
</neighbor>
<neighbor>
<ip>2001:db8::4</ip>
<origin>dynamic</origin>
<state>incomplete</state>
</neighbor>
</ipv6>
</interface>
</interfaces-state>
</data>
</rpc-reply> </rpc-reply>
Author's Address Author's Address
Martin Bjorklund Martin Bjorklund
Tail-f Systems Tail-f Systems
Email: mbj@tail-f.com EMail: mbj@tail-f.com
 End of changes. 82 change blocks. 
485 lines changed or deleted 1003 lines changed or added

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