draft-ietf-netmod-iana-if-type-05.txt		draft-ietf-netmod-iana-if-type-06.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 April 17, 2013		Intended status: Standards Track April 19, 2013
	Expires: October 19, 2013		Expires: October 21, 2013
	IANA Interface Type and Address Family YANG Modules		IANA Interface Type and Address Family YANG Modules
	draft-ietf-netmod-iana-if-type-05		draft-ietf-netmod-iana-if-type-06
	Abstract		Abstract
	This document defines the initial versions of the iana-if-type and		This document defines the initial versions of the iana-if-type and
	iana-afn-safi YANG modules.		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.
	skipping to change at page 1, line 31		skipping to change at page 1, line 31
	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 October 19, 2013.		This Internet-Draft will expire on October 21, 2013.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 IETF Trust and the persons identified as the		Copyright (c) 2013 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
	skipping to change at page 2, line 10		skipping to change at page 2, line 10
	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 Maintained AFN and SAFI YANG Module . . . . . . . . . . . 36		3. IANA Maintained AFN and SAFI YANG Module . . . . . . . . . . . 36
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46
	5. Security Considerations . . . . . . . . . . . . . . . . . . . 47		5. Security Considerations . . . . . . . . . . . . . . . . . . . 48
	6. Normative References . . . . . . . . . . . . . . . . . . . . . 48		6. Normative References . . . . . . . . . . . . . . . . . . . . . 49
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 49		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 50
	1. Introduction		1. Introduction
	This document defines the initial version of the iana-if-type and		This document defines the initial version of the iana-if-type and
	iana-afn-safi YANG modules, for interface type definitions, and		iana-afn-safi YANG modules, for interface type definitions, and
	Address Family Numbers (AFN) and Subsequent Address Family		Address Family Numbers (AFN) and Subsequent Address Family
	Identifiers (SAFI), respectively.		Identifiers (SAFI), respectively.
	The iana-if-type module reflects IANA's existing "ifType definitions"		The iana-if-type module reflects IANA's existing "ifType definitions"
	registry. The latest revision of the module can be obtained from the		registry. The latest revision of the module can be obtained from the
	skipping to change at page 4, line 50		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 2013-04-17 {		revision 2013-04-18 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: TITLE";		"RFC XXXX: TITLE";
	}		}
	typedef iana-if-type {		typedef iana-if-type {
	type enumeration {		type enumeration {
	enum "other" {		enum "other" {
	skipping to change at page 35, line 15		skipping to change at page 35, line 15
	description		description
	"GPON physical User to Network interface";		"GPON physical User to Network interface";
	reference		reference
	"ITU-T G.984.2";		"ITU-T G.984.2";
	}		}
	enum "vmwareNicTeam" {		enum "vmwareNicTeam" {
	value 272;		value 272;
	description		description
	"VMware NIC Team";		"VMware NIC Team";
	}		}
			// value 273 reserved by IANA
	}		}
	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		reference
	"ifType definitions registry.		"IANA ifType definitions registry.
	<http://www.iana.org/assignments/smi-numbers>";		<http://www.iana.org/assignments/smi-numbers>";
	}		}
	}		}
	<CODE ENDS>		<CODE ENDS>
	3. IANA Maintained AFN and SAFI YANG Module		3. IANA Maintained AFN and SAFI YANG Module
	<CODE BEGINS> file "iana-afn-safi.yang"		<CODE BEGINS> file "iana-afn-safi.yang"
	skipping to change at page 36, line 52		skipping to change at page 36, line 52
	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 the		This version of this YANG module is part of RFC XXXX; see the
	RFC itself for full legal notices.";		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 2013-04-17 {		revision 2013-04-18 {
	description		description
	"Initial revision.";		"Initial revision.";
	reference		reference
	"RFC XXXX: TITLE";		"RFC XXXX: TITLE";
	}		}
	typedef address-family {		typedef address-family {
	type enumeration {		type enumeration {
	enum other {		// value 0 is reserved by IANA
	value "0";
	description
	"none of the following";
	}
	enum ipv4 {		enum ipv4 {
	value "1";		value "1";
	description		description
	"IP version 4";		"IP version 4";
	}		}
	enum ipv6 {		enum ipv6 {
	value "2";		value "2";
	description		description
	"IP version 6";		"IP version 6";
	}		}
	skipping to change at page 40, line 4		skipping to change at page 39, line 48
	description		description
	"Gateway Identifier";		"Gateway Identifier";
	}		}
	enum l2vpn {		enum l2vpn {
	value "25";		value "25";
	description		description
	"AFI for L2VPN information";		"AFI for L2VPN information";
	reference		reference
	"RFC 4761: Virtual Private LAN Service (VPLS): Using BGP		"RFC 4761: Virtual Private LAN Service (VPLS): Using BGP
	for Auto-Discovery and Signaling		for Auto-Discovery and Signaling
	RFC 6074: Provisioning, Auto-Discovery, and Signaling in		RFC 6074: Provisioning, Auto-Discovery, and Signaling in
	Layer 2 Virtual Private Networks (L2VPNs)		Layer 2 Virtual Private Networks (L2VPNs)";
	";
	}		}
	enum eigrpCommon {		enum eigrpCommon {
	value "16384";		value "16384";
	description		description
	"EIGRP Common Service Family";		"EIGRP Common Service Family";
	}		}
	enum eigrpIPv4 {		enum eigrpIPv4 {
	value "16385";		value "16385";
	description		description
	"EIGRP IPv4 Service Family";		"EIGRP IPv4 Service Family";
	skipping to change at page 40, line 28		skipping to change at page 40, line 23
	enum eigrpIPv6 {		enum eigrpIPv6 {
	value "16386";		value "16386";
	description		description
	"EIGRP IPv6 Service Family";		"EIGRP IPv6 Service Family";
	}		}
	enum lcaf {		enum lcaf {
	value "16387";		value "16387";
	description		description
	"LISP Canonical Address Format";		"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		description
	"This typedef is a YANG enumeration of IANA-registered address		"This typedef is a YANG enumeration of IANA-registered address
	family numbers (AFN).";		family numbers (AFN).";
	reference		reference
	"Address Family Numbers. IANA, 2011-01-20.		"IANA Address Family Numbers registry.
	<http://www.iana.org/assignments/address-family-numbers/		<http://www.iana.org/assignments/address-family-numbers>";
	address-family-numbers.xml>
	";
	}		}
	typedef subsequent-address-family {		typedef subsequent-address-family {
	type enumeration {		type enumeration {
			// value 0 is reserved by IANA
	enum nlri-unicast {		enum nlri-unicast {
	value "1";		value "1";
	description		description
	"Network Layer Reachability Information used for unicast		"Network Layer Reachability Information used for unicast
	forwarding";		forwarding";
	reference		reference
	"RFC 4760: Multiprotocol Extensions for BGP-4";		"RFC 4760: Multiprotocol Extensions for BGP-4";
	}		}
	enum nlri-multicast {		enum nlri-multicast {
	value "2";		value "2";
	description		description
	"Network Layer Reachability Information used for multicast		"Network Layer Reachability Information used for multicast
	forwarding";		forwarding";
	reference		reference
	"RFC 4760: Multiprotocol Extensions for BGP-4";		"RFC 4760: Multiprotocol Extensions for BGP-4";
	}		}
			// value 3 is reserved by IANA
	enum nlri-mpls {		enum nlri-mpls {
	value "4";		value "4";
	description		description
	"Network Layer Reachability Information (NLRI) with MPLS		"Network Layer Reachability Information (NLRI) with MPLS
	Labels";		Labels";
	reference		reference
	"RFC 3107: Carrying Label Information in BGP-4";		"RFC 3107: Carrying Label Information in BGP-4";
	}		}
	enum mcast-vpn {		enum mcast-vpn {
	value "5";		value "5";
	skipping to change at page 42, line 15		skipping to change at page 42, line 17
	}		}
	enum vpls {		enum vpls {
	value "65";		value "65";
	description		description
	"Virtual Private LAN Service (VPLS)";		"Virtual Private LAN Service (VPLS)";
	reference		reference
	"RFC 4761: Virtual Private LAN Service (VPLS): Using BGP		"RFC 4761: Virtual Private LAN Service (VPLS): Using BGP
	for Auto-Discovery and Signaling		for Auto-Discovery and Signaling
	RFC 6074: Provisioning, Auto-Discovery, and Signaling in		RFC 6074: Provisioning, Auto-Discovery, and Signaling in
	Layer 2 Virtual Private Networks (L2VPNs)		Layer 2 Virtual Private Networks (L2VPNs)";
	";
	}		}
	enum bgp-mdt {		enum bgp-mdt {
	value "66";		value "66";
	description		description
	"BGP MDT SAFI";		"BGP MDT SAFI";
	reference		reference
	"RFC 6037: Cisco Systems' Solution for Multicast in		"RFC 6037: Cisco Systems' Solution for Multicast in
	BGP/MPLS IP VPNs";		BGP/MPLS IP VPNs";
	}		}
	enum bgp-4over6 {		enum bgp-4over6 {
	skipping to change at page 43, line 13		skipping to change at page 43, line 15
	}		}
	enum multicast-bgp-mpls-vpn {		enum multicast-bgp-mpls-vpn {
	value "129";		value "129";
	description		description
	"Multicast for BGP/MPLS IP Virtual Private Networks		"Multicast for BGP/MPLS IP Virtual Private Networks
	(VPNs)";		(VPNs)";
	reference		reference
	"RFC 6513: Multicast in MPLS/BGP IP VPNs		"RFC 6513: Multicast in MPLS/BGP IP VPNs
	RFC 6514: BGP Encodings and Procedures for Multicast in		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 {		enum route-target-constraints {
	value "132";		value "132";
	description		description
	"Route Target constraints";		"Route Target constraints";
	reference		reference
	"RFC 4684: Constrained Route Distribution for Border		"RFC 4684: Constrained Route Distribution for Border
	Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)		Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)
	Internet Protocol (IP) Virtual Private Networks (VPNs)";		Internet Protocol (IP) Virtual Private Networks (VPNs)";
	}		}
	enum ipv4-diss-flow {		enum ipv4-diss-flow {
	skipping to change at page 43, line 39		skipping to change at page 43, line 41
	reference		reference
	"RFC 5575: Dissemination of Flow Specification Rules";		"RFC 5575: Dissemination of Flow Specification Rules";
	}		}
	enum vpnv4-diss-flow {		enum vpnv4-diss-flow {
	value "134";		value "134";
	description		description
	"IPv4 dissemination of flow specification rules";		"IPv4 dissemination of flow specification rules";
	reference		reference
	"RFC 5575: Dissemination of Flow Specification Rules";		"RFC 5575: Dissemination of Flow Specification Rules";
	}		}
			// values 135-139 are reserved by IANA
	enum vpn-auto-discovery {		enum vpn-auto-discovery {
	value "140";		value "140";
	status "obsolete";		status "obsolete";
	description		description
	"VPN auto-discovery";		"VPN auto-discovery";
	reference		reference
	"draft-ietf-l3vpn-bgpvpn-auto: Using BGP as an		"draft-ietf-l3vpn-bgpvpn-auto: Using BGP as an
	Auto-Discovery Mechanism for VR-based Layer-3 VPNs";		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		description
	"This typedef is a YANG enumeration of IANA-registered		"This typedef is a YANG enumeration of IANA-registered
	subsequent address family identifiers (SAFI).";		subsequent address family identifiers (SAFI).";
	reference		reference
	"Subsequent Address Family Identifiers (SAFI) Parameters. IANA,		"IANA Subsequent Address Family Identifiers (SAFI) Parameters
	2012-02-22. <http://www.iana.org/assignments/safi-namespace/		registry.
	safi-namespace.xml>		<http://www.iana.org/assignments/safi-namespace>";
	";
	}		}
	}		}
	<CODE ENDS>		<CODE ENDS>
	4. 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 and iana-afn-safi YANG modules.		iana-if-type and iana-afn-safi YANG modules.
	skipping to change at page 45, line 21		skipping to change at page 46, line 21
	definitions" registry. When an interface type is added to this		definitions" registry. When an interface type is added to this
	registry, a new "enum" statement must be added to the "iana-if-type"		registry, a new "enum" statement must be added to the "iana-if-type"
	typedef, with the same name and value as the corresponding		typedef, with the same name and value as the corresponding
	enumeration in IANAifType-MIB. If the new interface type has a		enumeration in IANAifType-MIB. If the new interface type has a
	reference, a new "reference" statement should be added to the new		reference, a new "reference" statement should be added to the new
	"enum" statement. If an interface type is deprecated in the "ifType		"enum" statement. If an interface type is deprecated in the "ifType
	definitions" registry, the corresponding "enum" statement must be		definitions" registry, the corresponding "enum" statement must be
	updated with a "status" statement with the value "deprecated". If an		updated with a "status" statement with the value "deprecated". If an
	interface type is marked as "reserved" in the "ifType definitions"		interface type is marked as "reserved" in the "ifType definitions"
	registry, no "enum" statement is added to the "iana-if-type" typedef.		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"		When the iana-if-type YANG module is updated, a new "revision"
	statement must be added.		statement must be added.
	The iana-afn-safi module is intended to reflect the "Address Family		The iana-afn-safi module is intended to reflect the "Address Family
	Numbers" and "Subsequent Address Family Identifiers" registries.		Numbers" and "Subsequent Address Family Identifiers" registries.
	When an AFN or SAFI is added to these registries, a new "enum"		When an AFN or SAFI is added to these registries, a new "enum"
	statement must be added to the "address-family" or		statement must be added to the "address-family" or
	"subsequent-address-family" typedefs. If the new parameter has a		"subsequent-address-family" typedefs. If the new parameter has a
	reference, a new "reference" statement should be added to the new		reference, a new "reference" statement should be added to the new
	"enum" statement. If a parameter gets deprecated in these		"enum" statement. If a parameter gets deprecated in these
	registries, the corresponding "enum" statement must be updated with a		registries, the corresponding "enum" statement must be updated with a
	"status" statement with the value "deprecated". If a parameter is		"status" statement with the value "deprecated". If a parameter is
	marked as "reserved" in these registries, no "enum" statement 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"		When the iana-afn-safi YANG module is updated, a new "revision"
	statement must be added.		statement must be added.
	This document registers two URIs in the IETF XML registry [RFC3688].		This document registers two URIs in the IETF XML registry [RFC3688].
	Following the format in RFC 3688, the following registrations are		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
End of changes. 24 change blocks.
	32 lines changed or deleted		113 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/