< draft-ietf-rtgwg-routing-types-12.txt		draft-ietf-rtgwg-routing-types-13.txt >
	skipping to change at page 1, line 16 ¶		skipping to change at page 1, line 16 ¶
	Expires: March 22, 2018 Futurewei Technologies, Inc.		Expires: March 22, 2018 Futurewei Technologies, Inc.
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	C. Hopps		C. Hopps
	Deutsche Telekom		Deutsche Telekom
	L. Berger		L. Berger
	LabN Consulting, L.L.C.		LabN Consulting, L.L.C.
	September 18, 2017		September 18, 2017
	Routing Area Common YANG Data Types		Routing Area Common YANG Data Types
	draft-ietf-rtgwg-routing-types-12		draft-ietf-rtgwg-routing-types-13
	Abstract		Abstract
	This document defines a collection of common data types using the		This document defines a collection of common data types using the
	YANG data modeling language. These derived common types are designed		YANG data modeling language. These derived common types are designed
	to be imported by other modules defined in the routing area.		to be imported by other modules defined in the routing area.
	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
	skipping to change at page 7, line 44 ¶		skipping to change at page 7, line 44 ¶
	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
	set forth in Section 4.c of the IETF Trust's Legal Provisions		set forth in Section 4.c of the IETF Trust's Legal Provisions
	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.";
	reference "RFC XXXX";		reference "RFC XXXX";
	revision 2017-09-11 {		revision 2017-09-18 {
	description "Initial revision.";		description "Initial revision.";
	reference "RFC TBD: Routing YANG Data Types";		reference "RFC TBD: Routing YANG Data Types";
	}		}
	/*** Identities related to MPLS/GMPLS ***/		/*** Identities related to MPLS/GMPLS ***/
	identity mpls-label-special-purpose-value {		identity mpls-label-special-purpose-value {
	description		description
	"Base identity for deriving identities describing		"Base identity for deriving identities describing
	special-purpose Multiprotocol Label Switching (MPLS) label		special-purpose Multiprotocol Label Switching (MPLS) label
	skipping to change at page 13, line 8 ¶		skipping to change at page 13, line 8 ¶
	+ '[0-5]?[0-9]{0,3}[0-9]))|'		+ '[0-5]?[0-9]{0,3}[0-9]))|'
	+ '(6(:[a-fA-F0-9]{2}){6})|'		+ '(6(:[a-fA-F0-9]{2}){6})|'
	+ '(([3-57-9a-fA-F]|[1-9a-fA-F][0-9a-fA-F]{1,3}):'		+ '(([3-57-9a-fA-F]|[1-9a-fA-F][0-9a-fA-F]{1,3}):'
	+ '[0-9a-fA-F]{1,12})';		+ '[0-9a-fA-F]{1,12})';
	}		}
	description		description
	"A route distinguisher is an 8-octet value used to		"A route distinguisher is an 8-octet value used to
	distinguish routes from different BGP VPNs (RFC 4364).		distinguish routes from different BGP VPNs (RFC 4364).
	As per RFC 4360, a route distinguisher will have the same		As per RFC 4360, a route distinguisher will have the same
	format as a route target and will consist of two or three		format as a route target and will consist of two or three
	fields including a 2-octet type field, an administrator		fields including a 2-octet type field, an administrator
	field, and, optionally, an assigned number field.		field, and, optionally, an assigned number field.
	According to the data formats for type 0, 1, 2, and 6		According to the data formats for type 0, 1, 2, and 6
	defined in RFC4360, RFC5668, and RFC7432, the encoding		defined in RFC4360, RFC5668, and RFC7432, the encoding
	pattern is defined as:		pattern is defined as:
	0:2-octet-asn:4-octet-number		0:2-octet-asn:4-octet-number
	1:4-octet-ipv4addr:2-octet-number		1:4-octet-ipv4addr:2-octet-number
	2:4-octet-asn:2-octet-number.		2:4-octet-asn:2-octet-number.
	6:6-octet-mac-address.		6:6-octet-mac-address.
End of changes. 3 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/