draft-ietf-netmod-ip-cfg-01.txt   draft-ietf-netmod-ip-cfg-02.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 October 28, 2011 Intended status: Standards Track February 8, 2012
Expires: April 30, 2012 Expires: August 11, 2012
A YANG Data Model for IP Configuration A YANG Data Model for IP Configuration
draft-ietf-netmod-ip-cfg-01 draft-ietf-netmod-ip-cfg-02
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 April 30, 2012. This Internet-Draft will expire on August 11, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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
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 . . . . . . . . . . . . . . . . . . . . . 9 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11
6. Normative References . . . . . . . . . . . . . . . . . . . . . 11 6. Normative References . . . . . . . . . . . . . . . . . . . . . 12
Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 12 Appendix A. Example: NETCONF <get> reply . . . . . . . . . . . . 13
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 13 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14
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].
2. IP Data Model 2. IP Data Model
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, where square brackets are used to enclose a list's
keys, and "?" means that the node is optional. Choice and case nodes
are enclosed in parenthesis, and a case node is marked with a colon
(":").
+--rw if:interfaces +--rw if:interfaces
+--rw if:interface [name] +--rw if:interface [name]
... ...
+--rw ipv4 +--rw ipv4
| +--rw enabled? boolean
| +--rw address [ip] | +--rw address [ip]
| +--rw ip inet:ipv4-address | +--rw ip inet:ipv4-address
| +--rw (subnet)? | +--rw (subnet)?
| +--:(prefix-length) | +--:(prefix-length)
| | +--rw ip:prefix-length? uint8 | | +--rw ip:prefix-length? uint8
| +--:(netmask) | +--:(netmask)
| +--rw ip:netmask? inet:ipv4-address | +--rw ip:netmask? inet:ipv4-address
+--rw ipv6 +--rw ipv6
+--rw enabled? boolean
+--rw address [ip] +--rw address [ip]
+--rw ip inet:ipv6-address | +--rw ip inet:ipv6-address
+--rw prefix-length? uint8 | +--rw prefix-length? uint8
+--rw autoconf
+--rw create-global-addresses? boolean
+--rw dup-addr-detect-transmits? uint32
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 leaf "enabled" that controls if the address familiy is
enabled on that interface. In each container, there is also 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], and references [RFC4862].
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-10-28.yang" <CODE BEGINS> file "ietf-ip@2012-02-08.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-10-28 { revision 2012-02-08 {
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 */ /* Features */
feature non-contiguous-netmasks { feature non-contiguous-netmasks {
description description
"Indicates support for configuring non-contiguous "Indicates support for configuring non-contiguous
subnet masks."; subnet masks.";
} }
/* Data nodes */ /* Data nodes */
augment "/if:interfaces/if:interface" { augment "/if:interfaces/if:interface" {
description description
"Parameters for configuring IP addresses on interfaces."; "Parameters for configuring IP addresses on interfaces.
If an interface is not capable of running IP, the server
must not allow the client to configure these parameters.";
container ipv4 { container ipv4 {
description description
"Parameters for the IPv4 address familiy."; "Parameters for the IPv4 address family.";
leaf enabled {
type boolean;
default true;
description
"Controls if IPv4 is enabled or disabled on this
interface.";
}
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 description
"The IPv4 address on the interface."; "The IPv4 address on the interface.";
skipping to change at page 7, line 30 skipping to change at page 7, line 40
if-feature non-contiguous-netmasks; if-feature non-contiguous-netmasks;
type inet:ipv4-address; type inet:ipv4-address;
description description
"The subnet specified as a netmask."; "The subnet specified as a netmask.";
} }
} }
} }
} }
container ipv6 { container ipv6 {
description description
"Parameters for the IPv6 address familiy."; "Parameters for the IPv6 address family.";
leaf enabled {
type boolean;
default true;
description
"Controls if IPv6 is enabled or disabled on this
interface.";
}
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 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";
} }
default 128; default 128;
description description
"The length of the subnet prefix."; "The length of the subnet prefix.";
} }
} }
} container autoconf {
description
"Parameters to control the autoconfiguration of IPv6
addresses, as described in RFC 4862.";
reference
"RFC 4862: IPv6 Stateless Address Autoconfiguration";
// Open Issue #ip-02: should we have a leaf to control
// the creation of a link-local address?
//leaf create-link-local-address { ... default true; ... }
leaf create-global-addresses {
// Open Issue #ip-06: should we have a feature here?
//if-feature ipv6-host;
type boolean;
default true;
description
"If enabled, the host creates global addresses as
described in section 5.5 of RFC 4862.";
reference
"RFC 4862: IPv6 Stateless Address Autoconfiguration";
}
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";
}
}
}
} }
} }
<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.
skipping to change at page 10, line 20 skipping to change at page 11, line 20
transport is SSH [RFC6242]. transport is SSH [RFC6242].
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:
<list subtrees and data nodes and state why they are sensitive> ipv4/enabled and ipv6/enabled: These nodes are used to enable or
disable IPv4 and IPv6 on a specific interface. By enabling a
Some of the readable data nodes in the YANG module may be considered protocol on an interface, an attacker might be able to create an
sensitive or vulnerable in some network environments. It is thus unsecured path into a node (or through it if routing is also
important to control read access (e.g., via get, get-config, or enabled). By disabling a protocol on an interface, an attacker
notification) to these data nodes. These are the subtrees and data might be able to force packets to be routed through some other
nodes and their sensitivity/vulnerability: interface or deny access to some or all of the network via that
protocol.
<list subtrees and data nodes and state why they are sensitive> ipv4/address and ipv6/address: These lists specify the configured IP
addresses on an interface. By modifying this information, an
attacker can cause a node to either ignore messages destined to it
or accept (at least at the IP layer) messages it would otherwise
ignore. The use of filtering or security associations may reduce
the potential damage in the latter case.
6. Normative References 6. Normative References
[I-D.ietf-netmod-interfaces-cfg] [I-D.ietf-netmod-interfaces-cfg]
Bjorklund, M., "A YANG Data Model for Interface Bjorklund, M., "A YANG Data Model for Interface
Configuration", draft-ietf-netmod-interfaces-cfg-01 (work Configuration", draft-ietf-netmod-interfaces-cfg-01 (work
in progress), May 2011. in progress), May 2011.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[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.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, 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.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021, [RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010. October 2010.
[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.
 End of changes. 21 change blocks. 
29 lines changed or deleted 101 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/