draft-ietf-netmod-ip-cfg-07.txt   draft-ietf-netmod-ip-cfg-08.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 November 15, 2012 Intended status: Standards Track February 6, 2013
Expires: May 19, 2013 Expires: August 10, 2013
A YANG Data Model for IP Management A YANG Data Model for IP Management
draft-ietf-netmod-ip-cfg-07 draft-ietf-netmod-ip-cfg-08
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 May 19, 2013. This Internet-Draft will expire on August 10, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 7, line 7 skipping to change at page 7, line 7
| ipv6/forwarding | ipv6InterfaceForwarding | | ipv6/forwarding | ipv6InterfaceForwarding |
| ipv6/address | ipAddressEntry | | ipv6/address | ipAddressEntry |
| ipv6/address/ip | ipAddressAddrType / ipAddressAddr | | ipv6/address/ip | ipAddressAddrType / ipAddressAddr |
| ipv6/neighbor | ipNetToPhysicalTable | | ipv6/neighbor | ipNetToPhysicalTable |
+-----------------+-----------------------------------+ +-----------------+-----------------------------------+
Mapping of YANG data nodes to IP-MIB objects Mapping of YANG data nodes to IP-MIB objects
4. IP configuration YANG Module 4. IP configuration YANG Module
This module imports typedefs from [RFC6021] 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@2012-11-15.yang" <CODE BEGINS> file "ietf-ip@2013-02-06.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 8, line 20 skipping to change at page 8, line 20
(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 2012-11-15 { revision 2013-02-06 {
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 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.";
} }
skipping to change at page 9, line 47 skipping to change at page 9, line 47
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 IPv4 addresses on the interface.";
leaf ip { leaf ip {
type inet:ipv4-address; type inet:ipv4-address-no-zone;
description description
"The IPv4 address on the interface."; "The IPv4 address on the interface.";
} }
choice subnet { choice subnet {
default prefix-length; default prefix-length;
description description
"The subnet can be specified as a prefix-length, or, "The subnet can be specified as a prefix-length, or,
if the server supports non-contiguous netmasks, as if the server supports non-contiguous netmasks, as
a netmask. a netmask.
skipping to change at page 10, line 20 skipping to change at page 10, line 20
leaf prefix-length { leaf prefix-length {
type uint8 { type uint8 {
range "0..32"; range "0..32";
} }
default 32; default 32;
description description
"The length of the subnet prefix."; "The length of the subnet prefix.";
} }
leaf netmask { leaf netmask {
if-feature ipv4-non-contiguous-netmasks; if-feature ipv4-non-contiguous-netmasks;
type inet:ipv4-address; 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 physical addresses. addresses to physical 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; type inet:ipv4-address-no-zone;
description description
"The IPv4 address of a neighbor node."; "The IPv4 address of a neighbor node.";
} }
leaf phys-address { leaf phys-address {
type yang:phys-address; type yang:phys-address;
description description
"The physical level address of the neihgbor node."; "The physical level address of the neihgbor node.";
} }
} }
skipping to change at page 11, line 48 skipping to change at page 11, line 48
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 IPv6 addresses on the interface.";
leaf ip { leaf ip {
type inet:ipv6-address; 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";
} }
default 128; default 128;
description description
"The length of the subnet prefix."; "The length of the subnet prefix.";
skipping to change at page 12, line 25 skipping to change at page 12, line 25
description description
"A list of mappings from IPv6 "A list of mappings from IPv6
addresses to physical addresses. addresses to physical 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; type inet:ipv6-address-no-zone;
description description
"The IPv6 address of a neighbor node."; "The IPv6 address of a neighbor node.";
} }
leaf phys-address { leaf phys-address {
type yang:phys-address; type yang:phys-address;
description description
"The physical level address of the neighbor node."; "The physical level address of the neighbor node.";
} }
} }
leaf dup-addr-detect-transmits { leaf dup-addr-detect-transmits {
skipping to change at page 19, line 11 skipping to change at page 19, line 11
The author wishes to thank Ladislav Lhotka, Juergen Schoenwaelder, The author wishes to thank Ladislav Lhotka, Juergen Schoenwaelder,
and Dave Thaler for their helpful comments. 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] [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-05 (work Configuration", draft-ietf-netmod-interfaces-cfg-09 (work
in progress), July 2012. 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 [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.
[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,
skipping to change at page 19, line 41 skipping to change at page 19, line 46
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.
[RFC6021] Schoenwaelder, J., "Common YANG Data Types", RFC 6021,
October 2010.
8.2. Informative References 8.2. Informative References
[I-D.ietf-netmod-routing-cfg] [I-D.ietf-netmod-routing-cfg]
Lhotka, L., "A YANG Data Model for Routing Configuration", Lhotka, L., "A YANG Data Model for Routing Configuration",
draft-ietf-netmod-routing-cfg-04 (work in progress), draft-ietf-netmod-routing-cfg-04 (work in progress),
July 2012. July 2012.
[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,
 End of changes. 16 change blocks. 
18 lines changed or deleted 20 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/