--- 1/draft-ietf-netmod-iana-if-type-05.txt 2013-05-08 11:46:00.892413800 +0100 +++ 2/draft-ietf-netmod-iana-if-type-06.txt 2013-05-08 11:46:01.036417060 +0100 @@ -1,18 +1,18 @@ Network Working Group M. Bjorklund Internet-Draft Tail-f Systems -Intended status: Standards Track April 17, 2013 -Expires: October 19, 2013 +Intended status: Standards Track April 19, 2013 +Expires: October 21, 2013 IANA Interface Type and Address Family YANG Modules - draft-ietf-netmod-iana-if-type-05 + draft-ietf-netmod-iana-if-type-06 Abstract This document defines the initial versions of the iana-if-type and iana-afn-safi YANG modules. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -20,21 +20,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 October 19, 2013. + This Internet-Draft will expire on October 21, 2013. 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 @@ -42,24 +42,24 @@ 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 Maintained AFN and SAFI YANG Module . . . . . . . . . . . 36 - 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 47 - 6. Normative References . . . . . . . . . . . . . . . . . . . . . 48 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 49 + 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 + 5. Security Considerations . . . . . . . . . . . . . . . . . . . 48 + 6. Normative References . . . . . . . . . . . . . . . . . . . . . 49 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 50 1. Introduction This document defines the initial version of the iana-if-type and iana-afn-safi YANG modules, for interface type definitions, and Address Family Numbers (AFN) and Subsequent Address Family Identifiers (SAFI), respectively. The iana-if-type module reflects IANA's existing "ifType definitions" registry. The latest revision of the module can be obtained from the @@ -118,21 +118,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-04-17 { + revision 2013-04-18 { description "Initial revision."; reference "RFC XXXX: TITLE"; } typedef iana-if-type { type enumeration { enum "other" { @@ -1576,38 +1576,39 @@ description "GPON physical User to Network interface"; reference "ITU-T G.984.2"; } enum "vmwareNicTeam" { value 272; description "VMware NIC Team"; } + // value 273 reserved by IANA } description "This data type is used as the syntax of the 'type' leaf in the 'interface' list in the YANG module ietf-interface. The definition of this typedef with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.) Requests for new values should be made to IANA via email (iana&iana.org)."; reference - "ifType definitions registry. + "IANA ifType definitions registry. "; } } 3. IANA Maintained AFN and SAFI YANG Module file "iana-afn-safi.yang" @@ -1647,34 +1648,30 @@ 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-04-17 { + revision 2013-04-18 { description "Initial revision."; reference "RFC XXXX: TITLE"; } typedef address-family { type enumeration { - enum other { - value "0"; - description - "none of the following"; - } + // value 0 is reserved by IANA enum ipv4 { value "1"; description "IP version 4"; } enum ipv6 { value "2"; description "IP version 6"; } @@ -1792,23 +1789,23 @@ description "Gateway Identifier"; } enum l2vpn { value "25"; description "AFI for L2VPN information"; reference "RFC 4761: Virtual Private LAN Service (VPLS): Using BGP for Auto-Discovery and Signaling + RFC 6074: Provisioning, Auto-Discovery, and Signaling in - Layer 2 Virtual Private Networks (L2VPNs) - "; + Layer 2 Virtual Private Networks (L2VPNs)"; } enum eigrpCommon { value "16384"; description "EIGRP Common Service Family"; } enum eigrpIPv4 { value "16385"; description "EIGRP IPv4 Service Family"; @@ -1816,49 +1813,57 @@ enum eigrpIPv6 { value "16386"; description "EIGRP IPv6 Service Family"; } enum lcaf { value "16387"; description "LISP Canonical Address Format"; } + enum bgp-ls { + value "16388"; + description + "BGP-LS"; + reference + "draft-ietf-idr-ls-distribution"; + } + // value 65535 is reserved by IANA } description "This typedef is a YANG enumeration of IANA-registered address family numbers (AFN)."; reference - "Address Family Numbers. IANA, 2011-01-20. - - "; + "IANA Address Family Numbers registry. + "; } typedef subsequent-address-family { type enumeration { + // value 0 is reserved by IANA enum nlri-unicast { value "1"; description "Network Layer Reachability Information used for unicast forwarding"; reference "RFC 4760: Multiprotocol Extensions for BGP-4"; } enum nlri-multicast { value "2"; description "Network Layer Reachability Information used for multicast forwarding"; reference "RFC 4760: Multiprotocol Extensions for BGP-4"; } + // value 3 is reserved by IANA enum nlri-mpls { value "4"; description "Network Layer Reachability Information (NLRI) with MPLS Labels"; reference "RFC 3107: Carrying Label Information in BGP-4"; } enum mcast-vpn { value "5"; @@ -1899,22 +1903,21 @@ } enum vpls { value "65"; description "Virtual Private LAN Service (VPLS)"; reference "RFC 4761: Virtual Private LAN Service (VPLS): Using BGP for Auto-Discovery and Signaling RFC 6074: Provisioning, Auto-Discovery, and Signaling in - Layer 2 Virtual Private Networks (L2VPNs) - "; + Layer 2 Virtual Private Networks (L2VPNs)"; } enum bgp-mdt { value "66"; description "BGP MDT SAFI"; reference "RFC 6037: Cisco Systems' Solution for Multicast in BGP/MPLS IP VPNs"; } enum bgp-4over6 { @@ -1946,23 +1949,23 @@ } enum multicast-bgp-mpls-vpn { value "129"; description "Multicast for BGP/MPLS IP Virtual Private Networks (VPNs)"; reference "RFC 6513: Multicast in MPLS/BGP IP VPNs RFC 6514: BGP Encodings and Procedures for Multicast in - MPLS/BGP IP VPNs - "; + MPLS/BGP IP VPNs"; } + // values 130-131 are reserved by IANA enum route-target-constraints { value "132"; description "Route Target constraints"; reference "RFC 4684: Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)"; } enum ipv4-diss-flow { @@ -1972,39 +1975,110 @@ reference "RFC 5575: Dissemination of Flow Specification Rules"; } enum vpnv4-diss-flow { value "134"; description "IPv4 dissemination of flow specification rules"; reference "RFC 5575: Dissemination of Flow Specification Rules"; } + // values 135-139 are reserved by IANA enum vpn-auto-discovery { value "140"; status "obsolete"; description "VPN auto-discovery"; reference "draft-ietf-l3vpn-bgpvpn-auto: Using BGP as an Auto-Discovery Mechanism for VR-based Layer-3 VPNs"; } + // values 141-240 are reserved by IANA + enum private-241 { + value "241"; + description + "For private use."; + } + enum private-242 { + value "242"; + description + "For private use."; + } + enum private-243 { + value "243"; + description + "For private use."; + } + enum private-244 { + value "244"; + description + "For private use."; + } + enum private-245 { + value "245"; + description + "For private use."; + } + enum private-246 { + value "246"; + description + "For private use."; + } + enum private-247 { + value "247"; + description + "For private use."; + } + enum private-248 { + value "248"; + description + "For private use."; + } + enum private-249 { + value "249"; + description + "For private use."; + } + enum private-250 { + value "250"; + description + "For private use."; + } + enum private-251 { + value "251"; + description + "For private use."; + } + enum private-252 { + value "252"; + description + "For private use."; + } + enum private-253 { + value "253"; + description + "For private use."; + } + enum private-254 { + value "254"; + description + "For private use."; + } + // value 255 is reserved by IANA } description "This typedef is a YANG enumeration of IANA-registered subsequent address family identifiers (SAFI)."; - reference - "Subsequent Address Family Identifiers (SAFI) Parameters. IANA, - 2012-02-22. - "; + "IANA Subsequent Address Family Identifiers (SAFI) Parameters + registry. + "; } } 4. IANA Considerations This document defines the initial version of the IANA-maintained iana-if-type and iana-afn-safi YANG modules. @@ -2012,35 +2086,41 @@ definitions" registry. When an interface type is added to this registry, a new "enum" statement must be added to the "iana-if-type" typedef, with the same name and value as the corresponding enumeration in IANAifType-MIB. If the new interface type has a reference, a new "reference" statement should be added to the new "enum" statement. If an interface type is deprecated in the "ifType definitions" registry, the corresponding "enum" statement must be updated with a "status" statement with the value "deprecated". If an interface type is marked as "reserved" in the "ifType definitions" registry, no "enum" statement is added to the "iana-if-type" typedef. + Instead a comment is added, on the form: + + // value NN is reserved by IANA When the iana-if-type YANG module is updated, a new "revision" statement must be added. The iana-afn-safi module is intended to reflect the "Address Family Numbers" and "Subsequent Address Family Identifiers" registries. When an AFN or SAFI is added to these registries, a new "enum" statement must be added to the "address-family" or "subsequent-address-family" typedefs. If the new parameter has a reference, a new "reference" statement should be added to the new "enum" statement. If a parameter gets deprecated in these registries, the corresponding "enum" statement must be updated with a "status" statement with the value "deprecated". If a parameter is marked as "reserved" in these registries, no "enum" statement is - added to the corresponding typedef. + added to the corresponding typedef. Instead a comment is added, on + the form: + + // value NN is reserved by IANA When the iana-afn-safi YANG module is updated, a new "revision" statement must be added. This document registers two URIs in the IETF XML registry [RFC3688]. Following the format in RFC 3688, the following registrations are requested to be made. URI: urn:ietf:params:xml:ns:yang:iana-if-types