--- 1/draft-ietf-netmod-iana-if-type-06.txt 2013-07-04 15:14:38.327024630 -0700 +++ 2/draft-ietf-netmod-iana-if-type-07.txt 2013-07-04 15:14:38.387026242 -0700 @@ -1,92 +1,80 @@ Network Working Group M. Bjorklund Internet-Draft Tail-f Systems -Intended status: Standards Track April 19, 2013 -Expires: October 21, 2013 +Intended status: Standards Track July 4, 2013 +Expires: January 5, 2014 - IANA Interface Type and Address Family YANG Modules - draft-ietf-netmod-iana-if-type-06 + IANA Interface Type YANG Module + draft-ietf-netmod-iana-if-type-07 Abstract - This document defines the initial versions of the iana-if-type and - iana-afn-safi YANG modules. + 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. 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 21, 2013. + This Internet-Draft will expire on January 5, 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 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 Maintained AFN and SAFI YANG Module . . . . . . . . . . . 36 - 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46 - 5. Security Considerations . . . . . . . . . . . . . . . . . . . 48 - 6. Normative References . . . . . . . . . . . . . . . . . . . . . 49 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 50 + 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 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 and - iana-afn-safi YANG modules, for interface type definitions, and - Address Family Numbers (AFN) and Subsequent Address Family - Identifiers (SAFI), respectively. + 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. 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. - The iana-afn-safi module reflects IANA's existing "Address Family - Numbers" and "Subsequent Address Family Identifiers" registries. - - Whenever a new address family number is added to the "Address Family - Numbers" registry, the IANA-ADDRESS-FAMILY-NUMBERS-MIB and the iana- - afn-safi YANG module are updated by IANA. - - Whenever a new subsequent address family identifier is added to the - "Subsequent Address Family Identifiers" registry, the iana-afn-safi - YANG module is updated by IANA. - 2. IANA Maintained Interface Type YANG Module file "iana-if-type.yang" module iana-if-type { namespace "urn:ietf:params:xml:ns:yang:iana-if-type"; prefix ianaift; organization "IANA"; contact @@ -118,26 +106,26 @@ 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-18 { + revision 2013-07-04 { description "Initial revision."; reference - "RFC XXXX: TITLE"; + "RFC XXXX: IANA Interface Type YANG Module"; } typedef iana-if-type { type enumeration { enum "other" { value 1; description "None of the following"; } enum "regular1822" { @@ -1601,566 +1589,98 @@ Requests for new values should be made to IANA via email (iana&iana.org)."; reference "IANA ifType definitions registry. "; } } -3. IANA Maintained AFN and SAFI YANG Module - - file "iana-afn-safi.yang" - - module iana-afn-safi { - namespace "urn:ietf:params:xml:ns:yang:iana-afn-safi"; - prefix "ianaaf"; - - organization - "IANA"; - contact - " Internet Assigned Numbers Authority - - Postal: ICANN - 4676 Admiralty Way, Suite 330 - Marina del Rey, CA 90292 - - Tel: +1 310 823 9358 - E-Mail: iana&iana.org"; - description - "This YANG module provides two typedefs containing YANG - definitions for the following IANA-registered enumerations: - - - Address Family Numbers (AFN) - - - Subsequent Address Family Identifiers (SAFI) - - The latest revision of this YANG module can be obtained from the - IANA web site. - - Copyright (c) 2012 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."; - // RFC Ed.: replace XXXX with actual RFC number and remove this - // note. +3. IANA Considerations - // RFC Ed.: update the date below with the date of RFC publication - // and remove this note. - revision 2013-04-18 { - description - "Initial revision."; - reference - "RFC XXXX: TITLE"; - } + This document defines the initial version of the IANA-maintained + iana-if-type YANG module. - typedef address-family { - type enumeration { - // value 0 is reserved by IANA - enum ipv4 { - value "1"; - description - "IP version 4"; - } - enum ipv6 { - value "2"; - description - "IP version 6"; - } - enum nsap { - value "3"; - description - "NSAP"; - } - enum hdlc { - value "4"; - description - "HDLC (8-bit multidrop)"; - } - enum bbn1822 { - value "5"; - description - "BBN 1822"; - } - enum all802 { - value "6"; - description - "802 (includes all 802 media plus Ethernet 'canonical - format')"; - } - enum e163 { - value "7"; - description - "E.163"; - } - enum e164 { - value "8"; - description - "E.164 (SMDS, FrameRelay, ATM)"; - } - enum f69 { - value "9"; - description - "F.69 (Telex)"; - } - enum x121 { - value "10"; - description - "X.121 (X.25, Frame Relay)"; - } - enum ipx { - value "11"; - description - "IPX (Internetwork Packet Exchange)"; - } - enum appletalk { - value "12"; - description - "Appletalk"; - } - enum decnetIV { - value "13"; - description - "DECnet IV"; - } - enum banyanVines { - value "14"; - description - "Banyan Vines"; - } - enum e164withNsap { - value "15"; - description - "E.164 with NSAP format subaddress"; - reference - "ATM Forum UNI 3.1"; - } - enum dns { - value "16"; - description - "DNS (Domain Name System)"; - } - enum distinguishedName { - value "17"; - description - "Distinguished Name (per X.500)"; + The iana-if-type module is intended to reflect the "ifType + definitions" registry. When an interface type is added to this + registry, a new "enum" statement must be added to the "iana-if-type" + typedef. The name of the "enum" is the same as the corresponding + enumeration in the IANAifType-MIB. The following substatements to + the "enum" statement should be defined: - } - enum asNumber { - value "18"; - description - "Autonomous System Number"; - } - enum xtpOverIPv4 { - value "19"; - description - "XTP over IP version 4"; - } - enum xtpOverIpv6 { - value "20"; - description - "XTP over IP version 6"; - } - enum xtpNativeModeXTP { - value "21"; - description - "XTP native mode XTP"; - } - enum fibreChannelWWPN { - value "22"; - description - "Fibre Channel World-Wide Port Name"; - } - enum fibreChannelWWNN { - value "23"; - description - "Fibre Channel World-Wide Node Name"; - } - enum gwid { - value "24"; - 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 + "value": Replicate the value from the registry. - RFC 6074: Provisioning, Auto-Discovery, and Signaling in - Layer 2 Virtual Private Networks (L2VPNs)"; - } - enum eigrpCommon { - value "16384"; - description - "EIGRP Common Service Family"; - } - enum eigrpIPv4 { - value "16385"; - description - "EIGRP IPv4 Service Family"; - } - 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 - "IANA Address Family Numbers registry. - "; - } + "status": Include only if a registration has been deprecated (use + the value "deprecated") or obsoleted (use the value + "obsolete"). - 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"; - description - "MCAST-VPN"; - reference - "RFC 6514: BGP Encodings and Procedures for Multicast in - MPLS/BGP IP VPNs"; - } - enum nlri-dynamic-ms-pw { - value "6"; - status "obsolete"; - description - "Network Layer Reachability Information used for Dynamic - Placement of Multi-Segment Pseudowires (TEMPORARY - - Expires 2008-08-23)"; - reference - "draft-ietf-pwe3-dynamic-ms-pw: Dynamic Placement of Multi - Segment Pseudowires"; - } - enum encapsulation { - value "7"; - description - "Encapsulation SAFI"; - reference - "RFC 5512: The BGP Encapsulation Subsequent Address Family - Identifier (SAFI) and the BGP Tunnel Encapsulation - Attribute"; - } - enum tunnel-safi { - value "64"; - status "obsolete"; - description - "Tunnel SAFI"; - reference - "draft-nalawade-kapoor-tunnel-safi: BGP Tunnel SAFI"; - } - 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 + "description": Replicate the description from the registry, if any. - RFC 6074: Provisioning, Auto-Discovery, and Signaling in - 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 { - value "67"; - description - "BGP 4over6 SAFI"; - reference - "RFC 5747: 4over6 Transit Solution Using IP Encapsulation - and MP-BGP Extensions"; - } - enum bgp-6over4 { - value "68"; - description - "BGP 6over4 SAFI"; - } - enum l1vpn-auto-discovery { - value "69"; - description - "Layer-1 VPN auto-discovery information"; - reference - "RFC 5195: BGP-Based Auto-Discovery for Layer-1 VPNs"; - } - enum mpls-vpn { - value "128"; - description - "MPLS-labeled VPN address"; - reference - "RFC 4364: BGP/MPLS IP Virtual Private Networks (VPNs)"; - } - 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 + "reference": Replicate the reference from the registry, if any, and + add the title of the document. - RFC 6514: BGP Encodings and Procedures for Multicast in - 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 { - value "133"; - description - "IPv4 dissemination of flow specification rules"; - 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 - "IANA Subsequent Address Family Identifiers (SAFI) Parameters - registry. - "; - } - } + 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 XX -4. IANA Considerations + Unassigned values are not present in the module. - This document defines the initial version of the IANA-maintained - iana-if-type and iana-afn-safi YANG modules. + When the iana-if-type YANG module is updated, a new "revision" + statement must be added. - The iana-if-type module is intended to reflect the "ifType - 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: + IANA is requested to add this new Note to the "ifType definitions" + registry: - // value NN is reserved by IANA + When this registry is modified, the YANG module iana-if-type + must be updated as defined in RFC XXXX. - When the iana-if-type YANG module is updated, a new "revision" - statement must be added. + The Reference text in the "ifType definitions" registry needs to be + updated as: - 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. Instead a comment is added, on - the form: + OLD: + [RFC1213][RFC2863] - // value NN is reserved by IANA + NEW: + [RFC1213][RFC2863][RFCXXXX] - When the iana-afn-safi YANG module is updated, a new "revision" - statement must be added. +3.1. URI Registrations - This document registers two URIs in the IETF XML registry [RFC3688]. - Following the format in RFC 3688, the following registrations are + This document registers a URIs in the IETF XML registry [RFC3688]. + Following the format in RFC 3688, the following registration is requested to be made. URI: urn:ietf:params:xml:ns:yang:iana-if-types Registrant Contact: IANA. XML: N/A, the requested URI is an XML namespace. - URI: urn:ietf:params:xml:ns:yang:iana-afn-safi - - Registrant Contact: IANA. - - XML: N/A, the requested URI is an XML namespace. +3.2. YANG Module Registrations - This document registers two YANG modules in the YANG Module Names + This document registers a YANG module in the YANG Module Names registry [RFC6020]. name: iana-if-type namespace: urn:ietf:params:xml:ns:yang:iana-if-type prefix: ianaift reference: RFC XXXX - name: iana-afn-safi - namespace: urn:ietf:params:xml:ns:yang:iana-afn-safi - prefix: ianaaf - reference: RFC XXXX - -5. Security Considerations +4. Security Considerations Since this document does not introduce any technology or protocol, there are no security issues to be considered for this document itself. -6. Normative References +5. Normative References [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