--- 1/draft-ietf-netmod-interfaces-cfg-08.txt 2013-02-06 16:41:38.235708575 +0100 +++ 2/draft-ietf-netmod-interfaces-cfg-09.txt 2013-02-06 16:41:38.287708297 +0100 @@ -1,18 +1,18 @@ Network Working Group M. Bjorklund Internet-Draft Tail-f Systems -Intended status: Standards Track November 15, 2012 -Expires: May 19, 2013 +Intended status: Standards Track February 6, 2013 +Expires: August 10, 2013 A YANG Data Model for Interface Management - draft-ietf-netmod-interfaces-cfg-08 + draft-ietf-netmod-interfaces-cfg-09 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. Status of this Memo This Internet-Draft is submitted in full conformance with the @@ -21,25 +21,25 @@ 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 May 19, 2013. + This Internet-Draft will expire on August 10, 2013. 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. 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -257,23 +257,22 @@ type if:interface-ref; must "/if:interfaces/if:interface[if:name = current()]" + "/if:type = 'ethernetCsmacd'" { description "The type of a slave interface must be ethernet"; } } // other bonding config params, failover times etc. } - There are two state data leaf-list nodes "higher-layer-if" and - "lower-layer-if" defined, that contains a read-only view of the - interface layering hierarchy. + Two state data leaf-lists, "higher-layer-if" and "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 "interface" list is typically mapped to one ifEntry. The "if-index" leaf contains 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 an DisplayString [RFC2579] which uses a 7-bit ASCII character set. An implementation MAY restrict the @@ -324,21 +323,21 @@ Mapping of YANG data nodes to IF-MIB objects 5. Interfaces YANG Module This YANG module imports a typedef from [I-D.ietf-netmod-iana-if-type]. RFC Ed.: update the date below with the date of RFC publication and remove this note. - file "ietf-interfaces@2012-11-15.yang" + file "ietf-interfaces@2013-02-06.yang" module ietf-interfaces { namespace "urn:ietf:params:xml:ns:yang:ietf-interfaces"; prefix if; import ietf-yang-types { prefix yang; } import iana-if-type { @@ -376,21 +375,21 @@ (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 2012-11-15 { + revision 2013-02-06 { description "Initial revision."; reference "RFC XXXX: A YANG Data Model for Interface Management"; } /* Typedefs */ typedef interface-ref { type leafref { @@ -478,21 +477,24 @@ interface."; reference "RFC 2863: The Interfaces Group MIB - ifType"; } leaf location { type string; description "The device-specific location of the interface of a particular type. The format of the location string - depends on the interface type and the device. + depends on the interface type and the device. If a + NETCONF server is sent a value that doesn't match this + format, it MUST reply with an rpc-error with the error-tag + 'invalid-value'. If the interface's type represents a physical interface, this leaf MUST be set. When an interface entry is created, a server MAY initialize the location leaf with a valid value, e.g., if it is possible to derive the location from the name of the interface."; } @@ -535,21 +536,21 @@ "Status cannot be determined for some reason."; } enum dormant { value 5; description "Waiting for some external event."; } enum not-present { value 6; description - "Some component is missing."; + "Some component (typically hardware) is missing."; } enum lower-layer-down { value 7; description "Down due to state of lower-layer interface(s)."; } } config false; description "The current operational state of the interface.