draft-ietf-idr-capabilities-registry-change-04.txt		draft-ietf-idr-capabilities-registry-change-05.txt
	Network Working Group J. Scudder		Network Working Group J. Scudder
	Internet-Draft Juniper Networks		Internet-Draft Juniper Networks
	Updates: 5492 (if approved) May 23, 2019		Updates: 5492 (if approved) May 28, 2019
	Intended status: Standards Track		Intended status: Standards Track
	Expires: November 24, 2019		Expires: November 29, 2019
	Revision to Capability Codes Registration Procedures		Revision to Capability Codes Registration Procedures
	draft-ietf-idr-capabilities-registry-change-04.txt		draft-ietf-idr-capabilities-registry-change-05.txt
	Abstract		Abstract
	This document updates RFC 5492 by making a change to the registration		This document updates RFC 5492 by making a change to the registration
	procedures for BGP Capability Codes. Specifically, the range		procedures for BGP Capability Codes. Specifically, the range
	formerly designated "Reserved for Private Use" is divided into three		formerly designated "Reserved for Private Use" is divided into three
	new ranges, respectively designated as "First Come First Served",		new ranges, respectively designated as "First Come First Served",
	"Experimental" and "Reserved".		"Experimental" and "Reserved".
	Status of This Memo		Status of This Memo
	skipping to change at page 1, line 35 ¶		skipping to change at page 1, line 35 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 November 24, 2019.		This Internet-Draft will expire on November 29, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2019 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 3, line 34 ¶		skipping to change at page 3, line 34 ¶
	Reference: [RFC5492] and this document.		Reference: [RFC5492] and this document.
	Registry Owner/Change Controller: IESG		Registry Owner/Change Controller: IESG
	Registration procedures:		Registration procedures:
	+---------+-------------------------+		+---------+-------------------------+
	| Range | Registration Procedures |		| Range | Registration Procedures |
	+---------+-------------------------+		+---------+-------------------------+
	| 0 | Reserved |
	| 1-63 | IETF Review |		| 1-63 | IETF Review |
	| 64-238 | First Come First Served |		| 64-238 | First Come First Served |
	| 239-254 | Experimental |		| 239-254 | Experimental |
	| 255 | Reserved |		| 255 | Reserved |
	+---------+-------------------------+		+---------+-------------------------+
	Note: a separate "owner" column is not provided because the owner of		Note: a separate "owner" column is not provided because the owner of
	all registrations, once made, is "IESG".		all registrations, once made, is "IESG".
	IANA is requested to perform the following new allocations within the		IANA is requested to perform the following new allocations within the
	"Capability Codes" registry:		"Capability Codes" registry:
	+-------+-------------------------------------------+---------------+		+-------+-----------------------------------------------+-----------+
	| Value | Description | Reference |		| Value | Description | Reference |
	+-------+-------------------------------------------+---------------+		+-------+-----------------------------------------------+-----------+
	| 128 | Prestandard Route Refresh (deprecated) | (this |		| 128 | Prestandard Route Refresh (deprecated) | (this |
	| | | document) |		| | | document) |
	| 129 | Prestandard Outbound Route Filtering | (this |		+-------+-----------------------------------------------+-----------+
	| | (deprecated) | document) |		| 129 | Prestandard Outbound Route Filtering | (this |
	| 130 | Prestandard Outbound Route Filtering | (this |		| | (deprecated), prestandard draft-li-idr- | document) |
	| | (deprecated) | document) |		| | flowspec-rpd-04 (deprecated) | |
	| 255 | Reserved | (this |		+-------+-----------------------------------------------+-----------+
	| | | document) |		| 130 | Prestandard Outbound Route Filtering | (this |
	+-------+-------------------------------------------+---------------+		| | (deprecated) | document) |
			+-------+-----------------------------------------------+-----------+
			| 255 | Reserved | (this |
			| | | document) |
			+-------+-----------------------------------------------+-----------+
	4. Security Considerations		4. Security Considerations
	This revision to registration procedures does not change the		This revision to registration procedures does not change the
	underlying security issues inherent in the existing [RFC5492] and		underlying security issues inherent in the existing [RFC5492] and
	[RFC4271].		[RFC4271].
	5. Acknowledgements		5. Acknowledgements
	Thanks to Alia Atlas, Bruno Decraene, Martin Djernaes, Jeff Haas, Sue		Thanks to Alia Atlas, Bruno Decraene, Martin Djernaes, Jie Dong, Jeff
	Hares, Acee Lindem, Thomas Mangin, and Tom Petch for review and		Haas, Sue Hares, Acee Lindem, Thomas Mangin, and Tom Petch for review
	comments.		and comments.
	6. References		6. References
	6.1. Normative References		6.1. Normative References
	[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement		[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
	with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February		with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
	2009, <https://www.rfc-editor.org/info/rfc5492>.		2009, <https://www.rfc-editor.org/info/rfc5492>.
	[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for		[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
End of changes. 7 change blocks.
	20 lines changed or deleted		23 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/