--- 1/draft-ietf-netmod-interfaces-cfg-14.txt 2013-12-23 02:14:34.698173271 -0800 +++ 2/draft-ietf-netmod-interfaces-cfg-15.txt 2013-12-23 02:14:34.766174959 -0800 @@ -1,18 +1,18 @@ Network Working Group M. Bjorklund Internet-Draft Tail-f Systems -Intended status: Standards Track December 7, 2013 -Expires: June 10, 2014 +Intended status: Standards Track December 23, 2013 +Expires: June 26, 2014 A YANG Data Model for Interface Management - draft-ietf-netmod-interfaces-cfg-14 + draft-ietf-netmod-interfaces-cfg-15 Abstract This document defines a YANG data model for the management of network interfaces. It is expected that interface type specific data models augment the generic interfaces data model defined in this document. The data model includes configuration data and state data (status information and counters for the collection of statistics). Status of this Memo @@ -23,21 +23,21 @@ Internet-Drafts are working documents of the Internet Engineering 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on June 10, 2014. + This Internet-Draft will expire on June 26, 2014. Copyright Notice Copyright (c) 2013 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -353,30 +353,25 @@ "lower-layer-if", represent a read-only view of the interface layering hierarchy. 4. Relationship to the IF-MIB If the device implements IF-MIB [RFC2863], each entry in the "/interfaces-state/interface" list is typically mapped to one ifEntry. The "if-index" leaf MUST contain the value of the corresponding ifEntry's ifIndex. - In most cases, the "name" of an "interface" entry is mapped to - ifName. ifName is defined as a DisplayString [RFC2579] which uses a - 7-bit ASCII character set. An implementation that performs this - mapping MUST restrict the allowed values for "name" to match the - restrictions of ifName. - - The IF-MIB allows two different ifEntries to have the same ifName. - Devices that support this feature, and also support the data model - defined in this document, cannot have a 1-1 mapping between the - "name" leaf and ifName. + In most cases, the "name" of an "/interfaces-state/interface" entry + is mapped to ifName. The IF-MIB allows two different ifEntries to + have the same ifName. Devices that support this feature, and also + support the data model defined in this document, cannot have a 1-1 + mapping between the "name" leaf and ifName. The configured "description" of an "interface" has traditionally been mapped to ifAlias in some implementations. This document allows this mapping, but implementers should be aware of the differences in the value space and persistence for these objects. See the YANG module definition of the leaf "description" in Section 5 for details. The IF-MIB also defines the writable object ifPromiscuousMode. Since this object typically is not a configuration object, it is not mapped to the "ietf-interfaces" module. @@ -433,21 +428,21 @@ YANG config data nodes and related IF-MIB objects 5. Interfaces YANG Module This YANG module imports typedefs from [RFC6991]. RFC Ed.: update the date below with the date of RFC publication and remove this note. - file "ietf-interfaces@2013-12-06.yang" + file "ietf-interfaces@2013-12-23.yang" module ietf-interfaces { namespace "urn:ietf:params:xml:ns:yang:ietf-interfaces"; prefix if; import ietf-yang-types { prefix yang; } @@ -481,21 +476,21 @@ Relating to IETF Documents (http://trustee.ietf.org/license-info). This version of this YANG module is part of RFC XXXX; see the RFC itself for full legal notices."; // RFC Ed.: replace XXXX with actual RFC number and remove this // note. // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision 2013-12-06 { + revision 2013-12-23 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Interface Management"; } /* * Typedefs */ @@ -601,46 +596,33 @@ If the device supports pre-provisioning of interface configuration, the feature 'pre-provisioning' is advertised. If the device allows arbitrarily named user-controlled interfaces, the feature 'arbitrary-names' is advertised. When a configured user-controlled interface is created by the system, it is instantiated with the same name in the - /interface-state/interface list. Since the name in that - list MAY be mapped to ifName by an implementation, such an - implementation MUST restrict the allowed values for this - leaf so that it matches the restrictions of ifName. - - If a NETCONF server that implements this restriction is - sent a value that doesn't match the restriction, it MUST - reply with an rpc-error with the error-tag - 'invalid-value'."; + /interface-state/interface list."; } leaf description { type string; description "A textual description of the interface. - This leaf MAY be mapped to ifAlias by an implementation. - - Such an implementation MUST restrict the allowed values - for this leaf so that it matches the restrictions of - ifAlias. - - If a NETCONF server that implements this restriction is - sent a value that doesn't match the restriction, it MUST - reply with an rpc-error with the error-tag - 'invalid-value'. + A server implementation MAY map this leaf to the ifAlias + MIB object. Such an implementation needs to use some + mechanism to handle the differences in size and characters + allowed between this leaf and ifAlias. The definition of + such a mechanism is outside the scope of this document. Since ifAlias is defined to be stored in non-volatile storage, the MIB implementation MUST map ifAlias to the value of 'description' in the persistently stored datastore. Specifically, if the device supports ':startup', when ifAlias is read the device MUST return the value of 'description' in the 'startup' datastore, and when it is written, it MUST be written to the 'running' and 'startup' @@ -739,21 +721,25 @@ System-controlled interfaces created by the system are always present in this list, whether they are configured or not."; leaf name { type string; description "The name of the interface. - This leaf MAY be mapped to ifName by an implementation."; + A server implementation MAY map this leaf to the ifName + MIB object. Such an implementation needs to use some + mechanism to handle the differences in size and characters + allowed between this leaf and ifName. The definition of + such a mechanism is outside the scope of this document."; reference "RFC 2863: The Interfaces Group MIB - ifName"; } leaf type { type identityref { base interface-type; } mandatory true; description @@ -1210,24 +1197,20 @@ [RFC6991] Schoenwaelder, J., "Common YANG Data Types", RFC 6991, July 2013. 9.2. Informative References [I-D.ietf-netmod-iana-if-type] Bjorklund, M., "IANA Interface Type YANG Module", draft-ietf-netmod-iana-if-type-08 (work in progress), November 2013. - [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. - Schoenwaelder, Ed., "Textual Conventions for SMIv2", - STD 58, RFC 2579, April 1999. - [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 Shell (SSH)", RFC 6242, June 2011. [RFC6536] Bierman, A. and M. Bjorklund, "Network Configuration Protocol (NETCONF) Access Control Model", RFC 6536, March 2012. @@ -1248,21 +1231,21 @@ import ietf-interfaces { prefix if; } import iana-if-type { prefix ianaift; } // configuration parameters for ethernet interfaces augment "/if:interfaces/if:interface" { - when "if:type = 'ianaift:ethernet'"; + when "if:type = 'ianaift:ethernetCsmacd'"; container ethernet { choice transmission-params { case auto { leaf auto-negotiate { type empty; } } case manual { leaf duplex { @@ -1281,21 +1264,21 @@ } } } // other ethernet specific params... } } // operational state parameters for ethernet interfaces augment "/if:interfaces-state/if:interface" { - when "if:type = 'ethernetCsmacd'"; + when "if:type = 'ianaift:ethernetCsmacd'"; container ethernet { leaf duplex { type enumeration { enum "half"; enum "full"; } } // other ethernet specific params... }