< draft-ietf-rtgwg-routing-types-14.txt		draft-ietf-rtgwg-routing-types-15.txt >
	Network Working Group X. Liu		Network Working Group X. Liu
	Internet-Draft Jabil		Internet-Draft Jabil
	Intended status: Standards Track Y. Qu		Intended status: Standards Track Y. Qu
	Expires: March 23, 2018 Futurewei Technologies, Inc.		Expires: April 2, 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 19, 2017		September 29, 2017
	Routing Area Common YANG Data Types		Routing Area Common YANG Data Types
	draft-ietf-rtgwg-routing-types-14		draft-ietf-rtgwg-routing-types-15
	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 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 23, 2018.		This Internet-Draft will expire on April 2, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 33, line 5 ¶		skipping to change at page 33, line 5 ¶
	When an Address Family or Subsequent Address Family is respectively		When an Address Family or Subsequent Address Family is respectively
	added to the "Address Family Numbers" registry or the "Subsequent		added to the "Address Family Numbers" registry or the "Subsequent
	Address Family Identifiers (SAFI) Parameters" registry, a new "enum"		Address Family Identifiers (SAFI) Parameters" registry, a new "enum"
	statement must be added to the iana-routing-types YANG module. The		statement must be added to the iana-routing-types YANG module. The
	name of the "enum" is the same as the corresponding address family or		name of the "enum" is the same as the corresponding address family or
	SAFI only it will be a valid YANG identifier in all lowercase and		SAFI only it will be a valid YANG identifier in all lowercase and
	with hyphens separating individual words in compound identifiers.		with hyphens separating individual words in compound identifiers.
	The following substatements to the "enum" statement should be		The following substatements to the "enum" statement should be
	defined:		defined:
	"val": Contains the IANA assigned value corresponding to the		"enum": Contains the YANG enum identifier for the address-family
	address-family or "bgp-safi" for subsequent address		or "bgp-safi" for subsequent address families. This may
	families.		be the same as the address-family or "bgp-safi" or it may
			be a shorter version to faciliate YANG identifier usage.
			"value": Contains the IANA assigned value corresponding to the
			address-family or "bgp-safi" for subsequent address
			families.
	"status": Include only if a registration has been deprecated (use		"status": Include only if a registration has been deprecated (use
	the value "deprecated") or obsoleted (use the value		the value "deprecated") or obsoleted (use the value
	"obsolete").		"obsolete").
	"description": Replicate the description from the registry,		"description": Replicate the description from the registry,
	if any. Insert line breaks as needed so that the		if any. Insert line breaks as needed so that the
	line does not exceed 72 characters.		line does not exceed 72 characters.
	"reference": Replicate the reference from the registry, if any,		"reference": Replicate the reference from the registry, if any,
End of changes. 5 change blocks.
	7 lines changed or deleted		12 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/