draft-ietf-netmod-ip-cfg-09.txt   draft-ietf-netmod-ip-cfg-10.txt 
Network Working Group M. Bjorklund Network Working Group M. Bjorklund
Internet-Draft Tail-f Systems Internet-Draft Tail-f Systems
Intended status: Standards Track February 11, 2013 Intended status: Standards Track August 25, 2013
Expires: August 15, 2013 Expires: February 26, 2014
A YANG Data Model for IP Management A YANG Data Model for IP Management
draft-ietf-netmod-ip-cfg-09 draft-ietf-netmod-ip-cfg-10
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.
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.
skipping to change at page 1, line 31 skipping to change at page 1, line 31
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 15, 2013. This Internet-Draft will expire on February 26, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. IP Data Model . . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . 3
3. Relationship to IP-MIB . . . . . . . . . . . . . . . . . . . . 6 2. IP Data Model . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IP configuration YANG Module . . . . . . . . . . . . . . . . . 7 3. Relationship to IP-MIB . . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 4. IP management YANG Module . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28
8.1. Normative References . . . . . . . . . . . . . . . . . . . 19 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
8.2. Informative References . . . . . . . . . . . . . . . . . . 19 8.1. Normative References . . . . . . . . . . . . . . . . . . . 29
Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 21 8.2. Informative References . . . . . . . . . . . . . . . . . . 29
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 31
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 33
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 includes configuration and state data.
parameters for interfaces. Future revisions of this data model might
add other kinds of IP parameters.
Parameters to manage IP routing are defined in Parameters to manage IP routing are defined in
[I-D.ietf-netmod-routing-cfg]. [I-D.ietf-netmod-routing-cfg].
1.1. Terminology 1.1. Terminology
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14, [RFC2119]. 14, [RFC2119].
skipping to change at page 4, line 5 skipping to change at page 3, line 38
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
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
(read-write) and "ro" state data (read-only).
o Symbols after data node names: "?" means an optional node 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 [I-D.ietf-netmod-interfaces-cfg] with IP
list's keys, and "?" means that the node is optional. Choice and specific nodes, and adds IP specific state data.
case nodes are enclosed in parenthesis, and a case node is marked
with a colon (":"). The data model has the following structure for IP configuration per
interface:
+--rw if:interfaces +--rw if:interfaces
+--rw if:interface [name] +--rw if:interface* [name]
... ...
+--rw ipv4? +--rw ipv4?
| +--rw enabled? boolean | +--rw enabled? boolean
| +--rw forwarding? boolean | +--rw forwarding? boolean
| +--rw mtu? uint16 | +--rw mtu? uint16
| +--rw address [ip] | +--rw address* [ip]
| | +--rw ip inet:ipv4-address-no-zone | | +--rw ip inet:ipv4-address-no-zone
| | +--rw (subnet) | | +--rw (subnet)
| | +--:(prefix-length) | | +--:(prefix-length)
| | | +--rw ip:prefix-length? uint8 | | | +--rw ip:prefix-length? uint8
| | +--:(netmask) | | +--:(netmask)
| | +--rw ip:netmask? yang:dotted-quad | | +--rw ip:netmask? yang:dotted-quad
| +--rw neighbor [ip] | +--rw neighbor* [ip]
| +--rw ip inet:ipv4-address-no-zone | +--rw ip inet:ipv4-address-no-zone
| +--rw phys-address? yang:phys-address | +--rw link-layer-address? yang:phys-address
+--rw ipv6? +--rw ipv6?
+--rw enabled? boolean +--rw enabled? boolean
+--rw forwarding? boolean +--rw forwarding? boolean
+--rw mtu? uint32 +--rw mtu? uint32
+--rw address [ip] +--rw address* [ip]
| +--rw ip inet:ipv6-address-no-zone | +--rw ip inet:ipv6-address-no-zone
| +--rw prefix-length uint8 | +--rw prefix-length uint8
+--rw neighbor [ip] +--rw neighbor* [ip]
| +--rw ip inet:ipv6-address-no-zone | +--rw ip inet:ipv6-address-no-zone
| +--rw phys-address? yang:phys-address | +--rw link-layer-address? yang:phys-address
+--rw dup-addr-detect-transmits? uint32 +--rw dup-addr-detect-transmits? uint32
+--rw autoconf +--rw autoconf
+--rw create-global-addresses? boolean +--rw create-global-addresses? boolean
+--rw create-temporary-addresses? boolean +--rw create-temporary-addresses? boolean
+--rw temporary-valid-lifetime? uint32 +--rw temporary-valid-lifetime? uint32
+--rw temporary-preferred-lifetime? uint32 +--rw temporary-preferred-lifetime? uint32
The data model defines two containers, "ipv4" and "ipv6", The data model defines two configuration containers per interface,
representing the IPv4 and IPv6 address families. In each container, "ipv4" and "ipv6", representing the IPv4 and IPv6 address families.
there is a leaf "enabled" that controls if the address family is In each container, there is a leaf "enabled" that controls if the
enabled on that interface, and a leaf "forwarding" that controls if address family is enabled on that interface, and a leaf "forwarding"
ip packet forwarding for the address family is enabled on the that controls if IP packet forwarding for the address family is
interface. In each container, there is also a list of addresses, and enabled on the interface. In each container, there is also a list of
a list of mappings from ip addresses to physical addresses. configured addresses, and a list of configured mappings from IP
addresses to link-layer addresses.
The data model has the following structure for IP state per
interface:
+--ro if:interfaces-state
+--ro if:interface* [name]
...
+--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 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
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 if IP packet
forwarding is enabled on that interface. In each container there is
also a list of all addresses in use.
The data model has the following structure for global IP state:
+--ro ip-state
+--ro ipv4?
| +--ro neighbor* [interface ip]
| +--ro interface if:interface-state-ref
| +--ro ip inet:ipv4-address-no-zone
| +--ro link-layer-address? yang:phys-address
| +--ro origin? neighbor-origin
+--ro ipv6?
+--ro neighbor* [interface ip]
+--ro interface if:interface-state-ref
+--ro ip inet:ipv6-address-no-zone
+--ro link-layer-address? yang:phys-address
+--ro origin? neighbor-origin
+--ro is-router? boolean
+--ro state? enumeration
The data model defines a top-level container "ip-state" that contains
containers for ipv4 and ipv6 state. For each address family, there
is a list of known mappings from IP addresses to link-layer
addresses.
3. Relationship to IP-MIB 3. Relationship to IP-MIB
If the device implements IP-MIB [RFC4293], each entry in the "ipv4/ If the device implements IP-MIB [RFC4293], each entry in the "ipv4/
address" and "ipv6/address" lists is mapped to one ipAddressEntry, address" and "ipv6/address" lists is mapped to one ipAddressEntry,
where the ipAddressIfIndex refers to the "address" entry's interface. where the ipAddressIfIndex refers to the "address" entry's interface.
The IP-MIB defines objects to control IPv6 Router Advertisement. The The IP-MIB defines objects to control IPv6 Router Advertisement. The
corresponding YANG data nodes are defined in corresponding YANG data nodes are defined in
[I-D.ietf-netmod-routing-cfg]. [I-D.ietf-netmod-routing-cfg].
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 | | | ipNetToPhysicalNetAddressAddr |
| 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 |
| ipv6 | ipv6InterfaceEnableStatus |
| ipv6/forwarding | ipv6InterfaceForwarding |
| ipv6/address | ipAddressEntry |
| ipv6/address/ip | ipAddressAddrType |
| | ipAddressAddr |
| ipv6/address/origin | ipAddressOrigin |
| ipv6/address/status | ipAddressStatus |
+---------------------------------------+---------------------------+
YANG interface state data nodes and related IP-MIB objects
+----------------------------------+--------------------------------+
| YANG data node in /ip-state | IP-MIB object |
+----------------------------------+--------------------------------+
| ipv4/neighbor | ipNetToPhysicalEntry |
| ipv4/neighbor/interface | ipNetToPhysicalIfIndex |
| ipv4/neighbor/ip | ipNetToPhysicalNetAddressType |
| | ipNetToPhysicalNetAddressAddr |
| ipv4/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| ipv4/neighbor/origin | ipNetToPhysicalType |
| ipv6/neighbor | ipNetToPhysicalEntry |
| ipv6/neighbor/interface | ipNetToPhysicalIfIndex |
| ipv6/neighbor/ip | ipNetToPhysicalNetAddressType |
| | ipNetToPhysicalNetAddressAddr |
| ipv6/neighbor/link-layer-address | ipNetToPhysicalPhysAddress |
| ipv6/neighbor/origin | ipNetToPhysicalType |
| ipv6/neighbor/state | ipNetToPhysicalState |
+----------------------------------+--------------------------------+
YANG state data nodes and related IP-MIB objects
4. IP management YANG Module
This module imports typedefs from [I-D.ietf-netmod-rfc6021-bis] and This module imports typedefs from [I-D.ietf-netmod-rfc6021-bis] and
[I-D.ietf-netmod-interfaces-cfg], and references [RFC0791], [I-D.ietf-netmod-interfaces-cfg], and references [RFC0791],
[RFC0826], [RFC2460], [RFC4861], [RFC4862], and [RFC4941]. [RFC0826], [RFC2460], [RFC4861], [RFC4862], and [RFC4941].
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@2013-02-11.yang" <CODE BEGINS> file "ietf-ip@2013-08-25.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 {
skipping to change at page 7, line 51 skipping to change at page 10, line 51
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) 2013 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 XXXX; 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 // RFC Ed.: replace XXXX with actual RFC number and remove this
// note. // note.
// RFC Ed.: update the date below with the date of RFC publication // RFC Ed.: update the date below with the date of RFC publication
// and remove this note. // and remove this note.
revision 2013-02-11 { revision 2013-08-25 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for IP Management"; "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";
} }
/* Data nodes */ /*
* Typedefs
*/
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
auto-configuration.";
}
enum random {
description
"Indicates an address chosen by the system at
random, e.g., an IPv4 address within 169.254/16, or an
RFC 4941 privacy address.";
}
}
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.";
}
/*
* Configuration data nodes
*/
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
description description
"Parameters for configuring IP on interfaces. "Parameters for configuring IP on interfaces.
If an interface is not capable of running IP, the server If an interface is not capable of running IP, the server
must not allow the client to configure these parameters."; must not allow the client to configure these parameters.";
container ipv4 { container ipv4 {
presence "Configure IPv4 on this interface."; presence "Configure IPv4 on this interface.";
skipping to change at page 9, line 44 skipping to change at page 14, line 11
depending on the interface's type. depending on the interface's type.
If this leaf is not configured, the operationally used mtu If this leaf is not configured, the operationally used mtu
depends on the interface's type."; depends on the interface's type.";
reference reference
"RFC 791: Internet Protocol"; "RFC 791: Internet Protocol";
} }
list address { list address {
key "ip"; key "ip";
description description
"The list of IPv4 addresses on the interface."; "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 on the interface."; "The IPv4 address on the interface.";
} }
choice subnet { choice subnet {
mandatory true; mandatory true;
description description
"The subnet can be specified as a prefix-length, or, "The subnet can be specified as a prefix-length, or,
skipping to change at page 10, line 26 skipping to change at page 14, line 42
if-feature ipv4-non-contiguous-netmasks; if-feature ipv4-non-contiguous-netmasks;
type yang:dotted-quad; type yang:dotted-quad;
description description
"The subnet specified as a netmask."; "The subnet specified as a netmask.";
} }
} }
} }
list neighbor { list neighbor {
key "ip"; key "ip";
description description
"A list of mappings from IPv4 "A list of mappings from IPv4 addresses to
addresses to physical addresses. link-layer addresses.
Entries in this list are used as static entries in the Entries in this list are used as static entries in the
ARP cache."; ARP cache.";
reference reference
"RFC 826: An Ethernet Address Resolution Protocol"; "RFC 826: An Ethernet Address Resolution Protocol";
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 of the neighbor node.";
} }
leaf phys-address { leaf link-layer-address {
type yang:phys-address; type yang:phys-address;
description description
"The physical level address of the neihgbor node."; "The link-layer address of the neighbor node.";
} }
} }
} }
container ipv6 { container ipv6 {
presence "Configure IPv6 on this interface."; presence "Configure IPv6 on this interface.";
description description
"Parameters for the IPv6 address family."; "Parameters for the IPv6 address family.";
leaf enabled { leaf enabled {
skipping to change at page 11, line 43 skipping to change at page 16, line 10
If this leaf is not configured, the operationally used mtu If this leaf is not configured, the operationally used mtu
depends on the interface's type."; depends on the interface's type.";
reference reference
"RFC 2460: IPv6 Specification "RFC 2460: IPv6 Specification
Section 5"; Section 5";
} }
list address { list address {
key "ip"; key "ip";
description description
"The list of IPv6 addresses on the interface."; "The list of configured IPv6 addresses on the interface.";
leaf ip { leaf ip {
type inet:ipv6-address-no-zone; type inet:ipv6-address-no-zone;
description description
"The IPv6 address on the interface."; "The IPv6 address on the interface.";
} }
leaf prefix-length { leaf prefix-length {
type uint8 { type uint8 {
range "0..128"; range "0..128";
} }
mandatory true; mandatory true;
description description
"The length of the subnet prefix."; "The length of the subnet prefix.";
} }
} }
list neighbor { list neighbor {
key "ip"; key "ip";
description description
"A list of mappings from IPv6 "A list of mappings from IPv6 addresses to
addresses to physical addresses. link-layer addresses.
Entries in this list are used as static entries in the Entries in this list are used as static entries in the
Neighbor Cache."; Neighbor Cache.";
reference reference
"RFC 4861: Neighbor Discovery for IP version 6 (IPv6)"; "RFC 4861: Neighbor Discovery for IP version 6 (IPv6)";
leaf ip { leaf ip {
type inet:ipv6-address-no-zone; type inet:ipv6-address-no-zone;
description description
"The IPv6 address of a neighbor node."; "The IPv6 address of the neighbor node.";
} }
leaf phys-address { leaf link-layer-address {
type yang:phys-address; type yang:phys-address;
description description
"The physical level address of the neighbor node."; "The link-layer address of the neighbor node.";
} }
} }
leaf dup-addr-detect-transmits { leaf dup-addr-detect-transmits {
type uint32; type uint32;
default 1; default 1;
description description
"The number of consecutive Neighbor Solicitation messages "The number of consecutive Neighbor Solicitation messages
sent while performing Duplicate Address Detection on a sent while performing Duplicate Address Detection on a
tentative address. A value of zero indicates that tentative address. A value of zero indicates that
Duplicate Address Detection is not performed on Duplicate Address Detection is not performed on
skipping to change at page 13, line 49 skipping to change at page 18, line 17
if-feature ipv6-privacy-autoconf; if-feature ipv6-privacy-autoconf;
type uint32; type uint32;
units "seconds"; units "seconds";
default 86400; default 86400;
description description
"The time period during which the temporary address is "The time period during which the temporary address is
preferred."; preferred.";
reference reference
"RFC 4941: Privacy Extensions for Stateless Address "RFC 4941: Privacy Extensions for Stateless Address
Autoconfiguration in IPv6 Autoconfiguration in IPv6
- TEMP_PREFERED_LIFETIME"; - 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 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.";
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.";
} }
} }
} }
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 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.";
reference
"RFC 2460: 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";
}
}
}
}
container ip-state {
config false;
description
"Data nodes for the operational state of IP.";
container ipv4 {
presence "Present if IPv4 is enabled";
description
"Parameters for the IPv4 address family.";
list neighbor {
key "interface 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 interface {
type if:interface-state-ref;
description
"The name of the interface for this neighbor.";
}
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";
description
"Parameters for the IPv6 address family.";
list neighbor {
key "interface 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 interface {
type if:interface-state-ref;
description
"The name of the interface for this neighbor.";
}
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 is
requested to be made. requested to be made.
skipping to change at page 16, line 10 skipping to change at page 26, line 10
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 XXXX
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 21, line 5 skipping to change at page 30, line 20
[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. [RFC6241] Enns, R., Bjorklund, M., Schoenwaelder, J., and A.
Bierman, "Network Configuration Protocol (NETCONF)", Bierman, "Network Configuration Protocol (NETCONF)",
RFC 6241, June 2011. 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.
[RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration
Protocol (NETCONF) Access Control Model", RFC 6536,
March 2012.
Appendix A. Example: NETCONF <get> reply 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.
<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> <interface>
<name>eth0</name> <name>eth0</name>
<type>ethernetCsmacd</type> <type>ethernetCsmacd</type>
<location>0</location>
<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::1</ip> <ip>2001:DB8::10</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>
<interfaces-state
xmlns="urn:ietf:params:xml:ns:yang:ietf-interfaces">
<interface>
<name>eth0</name>
<type>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>
</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>
</ipv6>
</interface>
</interfaces-state>
<ip-state xmlns="urn:ietf:params:xml:ns:yang:ietf-ip">
<ipv6>
<neighbor>
<interface>eth0</interface>
<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>
<interface>eth0</interface>
<ip>2001:DB8::4</ip>
<origin>dynamic</origin>
<state>incomplete</state>
</neighbor>
</ipv6>
</ip-state>
</data> </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. 40 change blocks. 
82 lines changed or deleted 635 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/