--- 1/draft-ietf-netmod-iana-if-type-09.txt 2014-01-15 01:14:33.909267906 -0800 +++ 2/draft-ietf-netmod-iana-if-type-10.txt 2014-01-15 01:14:33.965269298 -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 January 15, 2014 +Expires: July 19, 2014 IANA Interface Type YANG Module - draft-ietf-netmod-iana-if-type-09 + draft-ietf-netmod-iana-if-type-10 Abstract This document defines the initial version of the iana-if-type YANG module. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -20,56 +20,56 @@ 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 July 19, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + Copyright (c) 2014 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 described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. IANA Maintained Interface Type YANG Module . . . . . . . . . . 4 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 - 3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 36 + 3.1. URI Registrations . . . . . . . . . . . . . . . . . . . . 37 3.2. YANG Module Registrations . . . . . . . . . . . . . . . . 37 4. Security Considerations . . . . . . . . . . . . . . . . . . . 38 5. Normative References . . . . . . . . . . . . . . . . . . . . . 39 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 40 1. Introduction This document defines the initial version of the iana-if-type YANG module for interface type definitions. The iana-if-type module reflects IANA's existing "ifType definitions" - registry. The latest revision of the module can be obtained from the - IANA web site. + registry [IFTYPE-IANA-REGISTRY]. The latest revision of the module + can be obtained from the IANA web site. Whenever a new interface type is added to the "ifType definitions" registry, the IANAifType-MIB and the iana-if-type YANG module are updated by IANA. 2. IANA Maintained Interface Type YANG Module This YANG module imports the "interface-type" identity from [I-D.ietf-netmod-interfaces-cfg]. @@ -108,31 +108,31 @@ Copyright (c) 2013 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions 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."; + The initial 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. reference "IANA ifType definitions registry. "; // RFC Ed.: update the date below with the date of RFC publication // and remove this note. - revision 2013-12-07 { + revision 2014-01-15 { description "Initial revision."; reference "RFC XXXX: IANA Interface Type YANG Module"; } identity iana-interface-type { base if:interface-type; description "This identity is used as a base for all interface types @@ -229,24 +229,28 @@ status obsolete; description "Obsolete see DS1-MIB"; reference "RFC 4805 - Definitions of Managed Objects for the DS1, J1, E1, DS2, and E2 Interface Types"; } identity basicISDN { base iana-interface-type; description - "see also RFC2127"; + "no longer used. + see also RFC2127"; } identity primaryISDN { base iana-interface-type; + description + "no longer used. + see also RFC2127"; } identity propPointToPointSerial { base iana-interface-type; description "proprietary serial"; } identity ppp { base iana-interface-type; } identity softwareLoopback { @@ -1592,42 +1593,55 @@ } 3. IANA Considerations This document defines the initial version of the IANA-maintained iana-if-type YANG module. - The iana-if-type module is intended to reflect the "ifType - definitions" registry. When an interface type is added to this - registry, a new "identity" statement must be added to the module. - The name of the "identity" is the same as the corresponding + The iana-if-type YANG module is intended to reflect the "ifType + definitions" registry [IFTYPE-IANA-REGISTRY], exactly like the + IANAifType-MIB MIB module [IANAifType-MIB] reflects the "ifType + definitions" registry. + + IANA is requested to add this new Note to the iana-if-type YANG + module registry: + + Interface types must not be directly added to the iana-if-type YANG + module, they must instead be added to the "ifType definitions" + registry. + + When an interface type is added to the "ifType definitions" registry, + a new "identity" statement must be added to the iana-if-type YANG + module. The name of the "identity" is the same as the corresponding enumeration in the IANAifType-MIB. The following substatements to the "identity" statement should be defined: "base": Contains the value "iana-interface-type". "status": Include only if a registration has been deprecated (use the value "deprecated") or obsoleted (use the value "obsolete"). "description": Replicate the description from the registry, if any. + Insert line breaks as needed so that the line does + not exceed 72 characters. "reference": Replicate the reference from the registry, if any, and add the title of the document. Unassigned or reserved values are not present in the module. When the iana-if-type YANG module is updated, a new "revision" - statement must be added. + statement must be added in front of the existing revision statements. IANA is requested to add this new Note to the "ifType definitions" registry: When this registry is modified, the YANG module iana-if-type must be updated as defined in RFC XXXX. The Reference text in the "ifType definitions" registry needs to be updated as: @@ -1665,20 +1679,30 @@ there are no security issues to be considered for this document itself. 5. Normative References [I-D.ietf-netmod-interfaces-cfg] Bjorklund, M., "A YANG Data Model for Interface Management", draft-ietf-netmod-interfaces-cfg-14 (work in progress), December 2013. + [IANAifType-MIB] + Internet Assigned Numbers Authority, "IANAifType Textual + Convention definitions", + . + + [IFTYPE-IANA-REGISTRY] + Internet Assigned Numbers Authority, "ifType Definitions", + . + [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. [RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, October 2010. Author's Address Martin Bjorklund