draft-ietf-netmod-ip-cfg-00.txt   draft-ietf-netmod-ip-cfg-01.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 September 7, 2011 Intended status: Standards Track October 28, 2011
Expires: March 10, 2012 Expires: April 30, 2012
A YANG Data Model for IP Configuration A YANG Data Model for IP Configuration
draft-ietf-netmod-ip-cfg-00 draft-ietf-netmod-ip-cfg-01
Abstract Abstract
This document defines a YANG data model for configuration of IP This document defines a YANG data model for configuration of IP
addresses on network interfaces. addresses on network interfaces.
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 March 10, 2012. This Internet-Draft will expire on April 30, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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
2. IP Data Model . . . . . . . . . . . . . . . . . . . . . . . . 4 2. IP Data Model . . . . . . . . . . . . . . . . . . . . . . . . 4
3. IP Address YANG Module . . . . . . . . . . . . . . . . . . . . 5 3. IP Address YANG Module . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10
6. Normative References . . . . . . . . . . . . . . . . . . . . . 10 6. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 11 Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction 1. Introduction
This document defines a YANG [RFC6020] data model for configuration This document defines a YANG [RFC6020] data model for configuration
of IP addresses on network interfaces. of IP addresses on network interfaces.
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 17 skipping to change at page 4, line 17
The module "ietf-ip" augments the "interface" list defined in the The module "ietf-ip" augments the "interface" list defined in the
"ietf-interfaces" module [I-D.ietf-netmod-interfaces-cfg] with the "ietf-interfaces" module [I-D.ietf-netmod-interfaces-cfg] with the
following nodes: following nodes:
+--rw if:interfaces +--rw if:interfaces
+--rw if:interface [name] +--rw if:interface [name]
... ...
+--rw ipv4 +--rw ipv4
| +--rw address [ip] | +--rw address [ip]
| +--rw ip inet:ipv4-address | +--rw ip inet:ipv4-address
| +--rw prefix-length? uint8 | +--rw (subnet)?
| +--:(prefix-length)
| | +--rw ip:prefix-length? uint8
| +--:(netmask)
| +--rw ip:netmask? inet:ipv4-address
+--rw ipv6 +--rw ipv6
+--rw address [ip] +--rw address [ip]
+--rw ip inet:ipv6-address +--rw ip inet:ipv6-address
+--rw prefix-length? uint8 +--rw prefix-length? uint8
The data model defines two containers, "ipv4" and "ipv6", The data model defines two containers, "ipv4" and "ipv6",
representing the IPv4 and IPv6 address families. In each container, representing the IPv4 and IPv6 address families. In each container,
there is a list of manually configured addresses. there is a list of manually configured addresses.
3. IP Address YANG Module 3. IP Address YANG Module
This module imports typedefs from [RFC6021] and This module imports typedefs from [RFC6021] and
[I-D.ietf-netmod-interfaces-cfg]. [I-D.ietf-netmod-interfaces-cfg].
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@2011-09-07.yang" <CODE BEGINS> file "ietf-ip@2011-10-28.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 6, line 16 skipping to change at page 6, line 16
(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 2011-09-07 { revision 2011-10-28 {
description description
"Initial revision."; "Initial revision.";
reference reference
"RFC XXXX: A YANG Data Model for IP Configuration"; "RFC XXXX: A YANG Data Model for IP Configuration";
} }
/* Features */
feature non-contiguous-netmasks {
description
"Indicates support for configuring non-contiguous
subnet masks.";
}
/* Data nodes */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
description
"Parameters for configuring IP addresses on interfaces.";
container ipv4 { container ipv4 {
description description
"Parameters for the IPv4 address familiy."; "Parameters for the IPv4 address familiy.";
list address { list address {
key "ip"; key "ip";
description description
"The list of manually configured IPv4 addresses "The list of manually configured IPv4 addresses
on the interface."; on the interface.";
leaf ip { leaf ip {
type inet:ipv4-address; type inet:ipv4-address;
description
"The IPv4 address on the interface.";
} }
leaf prefix-length { choice subnet {
type uint8 { default prefix-length;
range "0..32"; description
"The subnet can be specified as a prefix-length, or,
if the server supports non-contiguous netmasks, as
a netmask.
The default subnet is a prefix-length of 32.";
leaf prefix-length {
type uint8 {
range "0..32";
}
default 32;
description
"The length of the subnet prefix.";
}
leaf netmask {
if-feature non-contiguous-netmasks;
type inet:ipv4-address;
description
"The subnet specified as a netmask.";
} }
} }
} }
} }
container ipv6 { container ipv6 {
description description
"Parameters for the IPv6 address familiy."; "Parameters for the IPv6 address familiy.";
list address { list address {
key "ip"; key "ip";
description description
"The list of manually configured IPv6 addresses "The list of manually configured IPv6 addresses
on the interface."; on the interface.";
leaf ip { leaf ip {
type inet:ipv6-address; type inet:ipv6-address;
description
"The IPv6 address on the interface.";
} }
leaf prefix-length { leaf prefix-length {
type uint8 { type uint8 {
range "0..128"; range "0..128";
} }
default 128;
description
"The length of the subnet prefix.";
} }
} }
} }
} }
} }
<CODE ENDS> <CODE ENDS>
4. IANA Considerations 4. 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.
 End of changes. 14 change blocks. 
15 lines changed or deleted 58 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/