draft-ietf-netmod-iana-if-type-01.txt		draft-ietf-netmod-iana-if-type-02.txt
	Network Working Group M. Bjorklund		Network Working Group M. Bjorklund
	Internet-Draft Tail-f Systems		Internet-Draft Tail-f Systems
	Intended status: Standards Track September 7, 2011		Intended status: Standards Track April 29, 2012
	Expires: March 10, 2012		Expires: October 31, 2012
	IANA Interface Type YANG Module		IANA Interface Type and Address Family YANG Modules
	draft-ietf-netmod-iana-if-type-01		draft-ietf-netmod-iana-if-type-02
	Abstract		Abstract
	This document defines the initial version of the iana-if-type YANG		This document defines the initial versions of the iana-if-type and
	module.		iana-afn-safi YANG modules.
	Status of this Memo		Status of this Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on March 10, 2012.		This Internet-Draft will expire on October 31, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2012 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. IANA Maintained Interface Type YANG Module . . . . . . . . . . 4		2. IANA Maintained Interface Type YANG Module . . . . . . . . . . 4
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 35		3. IANA Maintained AFN and SAFI YANG Module . . . . . . . . . . . 36
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 36		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
	5. Normative References . . . . . . . . . . . . . . . . . . . . . 37		5. Security Considerations . . . . . . . . . . . . . . . . . . . 46
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 38		6. Normative References . . . . . . . . . . . . . . . . . . . . . 47
			Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 48
	1. Introduction		1. Introduction
	This document defines the initial version of the iana-if-type YANG		This document defines the initial version of the iana-if-type and
	module. This module reflects IANA's "ifType definitions" registry.		iana-afn-safi YANG modules, for interface type definitions, and
	The latest revision of the module can be obtained from the IANA web		Address Family Numbers (AFN) and Subsequent Address Family
	site.		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
			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		2. IANA Maintained Interface Type YANG Module
	<CODE BEGINS> file "iana-if-type.yang"		<CODE BEGINS> file "iana-if-type.yang"
	module iana-if-type {		module iana-if-type {
	namespace "urn:ietf:params:xml:ns:yang:iana-if-type";		namespace "urn:ietf:params:xml:ns:yang:iana-if-type";
	prefix ianaift;		prefix ianaift;
	organization "IANA";		organization "IANA";
	skipping to change at page 4, line 25		skipping to change at page 4, line 25
	" Internet Assigned Numbers Authority		" Internet Assigned Numbers Authority
	Postal: ICANN		Postal: ICANN
	4676 Admiralty Way, Suite 330		4676 Admiralty Way, Suite 330
	Marina del Rey, CA 90292		Marina del Rey, CA 90292
	Tel: +1 310 823 9358		Tel: +1 310 823 9358
	E-Mail: iana&iana.org";		E-Mail: iana&iana.org";
	description		description
	"This YANG module defines the iana-if-type typedef, which		"This YANG module defines the iana-if-type typedef, which
	contains YANG definitions for IANA-registrered interface types.		contains YANG definitions for IANA-registered interface types.
			This YANG module is maintained by IANA, and reflects the
			'ifType definitions' registry.
	The latest revision of this YANG module can be obtained from		The latest revision of this YANG module can be obtained from
	the IANA web site.		the IANA web site.
	Copyright (c) 2011 IETF Trust and the persons identified as		Copyright (c) 2011 IETF Trust and the persons identified as
	authors of the code. All rights reserved.		authors of the code. All rights reserved.
	Redistribution and use in source and binary forms, with or		Redistribution and use in source and binary forms, with or
	without modification, is permitted pursuant to, and subject		without modification, is permitted pursuant to, and subject
	to the license terms contained in, the Simplified BSD License		to the license terms contained in, the Simplified BSD License
	skipping to change at page 4, line 47		skipping to change at page 4, line 50
	Relating to IETF Documents		Relating to IETF Documents
	(http://trustee.ietf.org/license-info).		(http://trustee.ietf.org/license-info).
	This version of this YANG module is part of RFC XXXX; see		This version of this YANG module is part of RFC XXXX; see
	the RFC itself for full legal notices.";		the RFC itself for full legal notices.";
	// RFC Ed.: replace XXXX with actual RFC number and remove this		// RFC Ed.: replace XXXX with actual RFC number and remove this
	// note.		// note.
	// RFC Ed.: update the date below with the date of RFC publication		// RFC Ed.: update the date below with the date of RFC publication
	// and remove this note.		// and remove this note.
	revision 2011-09-07 {		revision 2012-04-24 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: IANA Interface Type YANG Module";		"RFC XXXX: TITLE";
	}		}
	typedef iana-if-type {		typedef iana-if-type {
	type enumeration {		type enumeration {
	enum "other" {		enum "other" {
	value 1;		value 1;
	description		description
	"None of the following";		"None of the following";
	}		}
	enum "regular1822" {		enum "regular1822" {
	value 2;		value 2;
	}		}
	skipping to change at page 33, line 34		skipping to change at page 33, line 38
	}		}
	enum "vmwareVirtualNic" {		enum "vmwareVirtualNic" {
	value 258;		value 258;
	description		description
	"VMware Virtual Network Interface";		"VMware Virtual Network Interface";
	}		}
	enum "ieee802154" {		enum "ieee802154" {
	value 259;		value 259;
	description		description
	"IEEE 802.15.4 WPAN interface";		"IEEE 802.15.4 WPAN interface";
			reference
			"IEEE 802.15.4-2006";
			}
			enum "otnOdu" {
			value 260;
			description
			"OTN Optical Data Unit";
			}
			enum "otnOtu" {
			value 261;
			description
			"OTN Optical channel Transport Unit";
			}
			enum "ifVfiType" {
			value 262;
			description
			"VPLS Forwarding Instance Interface Type";
			}
			enum "g9981" {
			value 263;
			description
			"G.998.1 bonded interface";
			}
			enum "g9982" {
			value 264;
			description
			"G.998.2 bonded interface";
			}
			enum "g9983" {
			value 265;
			description
			"G.998.3 bonded interface";
			}
			enum "aluEpon" {
			value 266;
			description
			"Ethernet Passive Optical Networks (E-PON)";
			}
			enum "aluEponOnu" {
			value 267;
			description
			"EPON Optical Network Unit";
			}
			enum "aluEponPhysicalUni" {
			value 268;
			description
			"EPON physical User to Network interface";
			}
			enum "aluEponLogicalLink" {
			value 269;
			description
			"The emulation of a point-to-point link over the EPON
			layer";
			}
			enum "aluGponOnu" {
			value 270;
			description
			"GPON Optical Network Unit";
			reference
			"ITU-T G.984.2";
			}
			enum "aluGponPhysicalUni" {
			value 271;
			description
			"GPON physical User to Network interface";
			reference
			"ITU-T G.984.2";
	}		}
	}		}
	description		description
	"This data type is used as the syntax of the 'type'		"This data type is used as the syntax of the 'type'
	leaf in the 'interface' list in the YANG module		leaf in the 'interface' list in the YANG module
	ietf-interface.		ietf-interface.
	The definition of this typedef with the		The definition of this typedef with the
	addition of newly assigned values is published		addition of newly assigned values is published
	periodically by the IANA, in either the Assigned		periodically by the IANA, in either the Assigned
	Numbers RFC, or some derivative of it specific to		Numbers RFC, or some derivative of it specific to
	Internet Network Management number assignments. (The		Internet Network Management number assignments. (The
	latest arrangements can be obtained by contacting the		latest arrangements can be obtained by contacting the
	IANA.)		IANA.)
	Requests for new values should be made to IANA via		Requests for new values should be made to IANA via
	email (iana&iana.org).";		email (iana&iana.org).";
			reference
			"ifType definitions registry.
			<http://www.iana.org/assignments/smi-numbers>";
			}
			}
			<CODE ENDS>
			3. IANA Maintained AFN and SAFI YANG Module
			<CODE BEGINS> 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.
			// RFC Ed.: update the date below with the date of RFC publication
			// and remove this note.
			revision 2012-04-24 {
			description
			"Initial revision.";
			reference
			"RFC XXXX: TITLE";
			}
			typedef address-family {
			type enumeration {
			enum other {
			value "0";
			description
			"none of the following";
			}
			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
			"(8-bit multidrop)";
			}
			enum bbn1822 {
			value "5";
			description
			"BBN Report 1822";
			}
			enum all802 {
			value "6";
			description
			"(includes all 802 media plus Ethernet 'canonical
			format')";
			}
			enum e163 {
			value "7";
			description
			"E.163";
			}
			enum e164 {
			value "8";
			description
			"(SMDS, FrameRelay, ATM)";
			}
			enum f69 {
			value "9";
			description
			"(Telex)";
			}
			enum x121 {
			value "10";
			description
			"(X.25, Frame Relay)";
			}
			enum ipx {
			value "11";
			description
			"IPX (Internet Protocol Exchange)";
			}
			enum appleTalk {
			value "12";
			description
			"Apple Talk";
			}
			enum decnetIV {
			value "13";
			description
			"DEC Net Phase IV";
			}
			enum banyanVines {
			value "14";
			description
			"Banyan Vines";
			}
			enum e164withNsap {
			value "15";
			description
			"(E.164 with NSAP format subaddress)";
			}
			enum dns {
			value "16";
			description
			"(Domain Name System)";
			}
			enum distinguishedName {
			value "17";
			description
			"(Distinguished Name, per X.500)";
			}
			enum asNumber {
			value "18";
			description
			"(16-bit quantity, per the AS number space)";
			}
			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 afi {
			value "25";
			description
			"AFI for L2VPN";
			}
			}
			description
			"This typedef is a YANG enumeration of IANA-registered address
			family numbers (AFN).";
			reference
			"Address Family Numbers. IANA, 2011-01-20.
			<http://www.iana.org/assignments/address-family-numbers/
			address-family-numbers.xml>
			IANA-ADDRESS-FAMILY-NUMBERS-MIB DEFINITIONS
			<http://www.iana.org/assignments/ianaaddressfamilynumbers-mib>
			";
	}		}
			typedef subsequent-address-family {
			type enumeration {
			enum nlri-unicast {
			value "1";
			description
			"Network Layer Reachability Information used for unicast
			forwarding";
			reference
			"RFC4760";
			}
			enum nlri-multicast {
			value "2";
			description
			"Network Layer Reachability Information used for multicast
			forwarding";
			reference
			"RFC4760";
			}
			enum nlri-mpls {
			value "4";
			description
			"Network Layer Reachability Information (NLRI) with MPLS
			Labels";
			reference
			"RFC3107";
			}
			enum mcast-vpn {
			value "5";
			description
			"MCAST-VPN";
			reference
			"draft-ietf-l3vpn-2547bis-mcast-bgp-08";
			}
			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-13";
			}
			enum tunnel-safi {
			value "64";
			description
			"Tunnel SAFI";
			reference
			"draft-nalawade-kapoor-tunnel-safi-05";
			}
			enum vpls {
			value "65";
			description
			"Virtual Private LAN Service (VPLS)";
			reference
			"RFC4761, RFC6074";
			}
			enum bgp-mdt {
			value "66";
			description
			"BGP MDT SAFI";
			reference
			"RFC6037";
			}
			enum bgp-4over6 {
			value "67";
			description
			"BGP 4over6 SAFI";
			reference
			"RFC5747";
			}
			enum bgp-6over4 {
			value "68";
			description
			"BGP 6over4 SAFI";
			reference
			"mailto:cuiyong&tsinghua.edu.cn";
			}
			enum l1vpn-auto-discovery {
			value "69";
			description
			"Layer-1 VPN auto-discovery information";
			reference
			"draft-ietf-l1vpn-bgp-auto-discovery-05";
			}
			enum mpls-vpn {
			value "128";
			description
			"MPLS-labeled VPN address";
			reference
			"RFC4364";
			}
			enum multicast-bgp-mpls-vpn {
			value "129";
			description
			"Multicast for BGP/MPLS IP Virtual Private Networks
			(VPNs)";
			reference
			"draft-ietf-l3vpn-2547bis-mcast-10,
			draft-ietf-l3vpn-2547bis-mcast-10";
			}
			enum route-target-constraints {
			value "132";
			description
			"Route Target constraints";
			reference
			"RFC4684";
			}
			enum ipv4-diss-flow {
			value "133";
			description
			"IPv4 dissemination of flow specification rules";
			reference
			"RFC5575";
			}
			enum vpnv4-diss-flow {
			value "134";
			description
			"IPv4 dissemination of flow specification rules";
			reference
			"RFC5575";
			}
			enum vpn-auto-discovery {
			value "140";
			description
			"VPN auto-discovery";
			reference
			"draft-ietf-l3vpn-bgpvpn-auto-09";
			}
			}
			description
			"This typedef is a YANG enumeration of IANA-registered
			subsequent address family identifiers (SAFI).";
			reference
			"Subsequent Address Family Identifiers (SAFI) Parameters. IANA,
			2011-03-04. <http://www.iana.org/assignments/safi-namespace/
			safi-namespace.xml>
			";
			}
	}		}
	<CODE ENDS>		<CODE ENDS>
	3. IANA Considerations		4. IANA Considerations
	This document defines the initial version of the IANA-maintained		This document defines the initial version of the IANA-maintained
	iana-if-type YANG module. The iana-if-type module is intended to		iana-if-type and iana-afn-safi YANG modules.
	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".
	This document registers a URI in the IETF XML registry [RFC3688].		The iana-if-type module is intended to reflect the "ifType
	Following the format in RFC 3688, the following registration is		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".
			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 Familiy
			Numbers" and "Subsequent Address Familiy 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 the registry,
			the corresponding "enum" statement must be updated with a "status"
			statement with the value "deprecated".
			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.		requested to be made.
	URI: urn:ietf:params:xml:ns:yang:iana-if-types		URI: urn:ietf:params:xml:ns:yang:iana-if-types
	Registrant Contact: The NETMOD WG of the IETF.		Registrant Contact: IANA.
	XML: N/A, the requested URI is an XML namespace.		XML: N/A, the requested URI is an XML namespace.
	This document registers one YANG module in the YANG Module Names		URI: urn:ietf:params:xml:ns:yang:iana-afn-safi
			Registrant Contact: IANA.
			XML: N/A, the requested URI is an XML namespace.
			This document registers two YANG modules in the YANG Module Names
	registry [RFC6020].		registry [RFC6020].
	name: iana-if-type		name: iana-if-type
	namespace: urn:ietf:params:xml:ns:yang:iana-if-type		namespace: urn:ietf:params:xml:ns:yang:iana-if-type
	prefix: ianaift		prefix: ianaift
	reference: RFC XXXX		reference: RFC XXXX
	4. Security Considerations		name: iana-afn-safi
			namespace: urn:ietf:params:xml:ns:yang:iana-afn-safi
			prefix: ianaaf
			reference: RFC XXXX
			5. Security Considerations
	Since this document does not introduce any technology or protocol,		Since this document does not introduce any technology or protocol,
	there are no security issues to be considered for this document		there are no security issues to be considered for this document
	itself.		itself.
	5. Normative References		6. Normative References
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,		[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
	January 2004.		January 2004.
	[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the		[RFC6020] Bjorklund, M., "YANG - A Data Modeling Language for the
	Network Configuration Protocol (NETCONF)", RFC 6020,		Network Configuration Protocol (NETCONF)", RFC 6020,
	October 2010.		October 2010.
	Author's Address		Author's Address
End of changes. 22 change blocks.
	36 lines changed or deleted		503 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/