draft-ietf-idr-capabilities-registry-change-07.txt		draft-ietf-idr-capabilities-registry-change-08.txt
	Network Working Group J. Scudder		Network Working Group J. Scudder
	Internet-Draft Juniper Networks		Internet-Draft Juniper Networks
	Updates: 5492 (if approved) April 15, 2020		Updates: 5492 (if approved) April 30, 2020
	Intended status: Standards Track		Intended status: Standards Track
	Expires: October 17, 2020		Expires: November 1, 2020
	Revision to Capability Codes Registration Procedures		Revision to Capability Codes Registration Procedures
	draft-ietf-idr-capabilities-registry-change-07		draft-ietf-idr-capabilities-registry-change-08
	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 Use" and "Reserved".		"Experimental Use" 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 October 17, 2020.		This Internet-Draft will expire on November 1, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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 2, line 14 ¶		skipping to change at page 2, line 14 ¶
	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 . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 2		2. Discussion . . . . . . . . . . . . . . . . . . . . . . . . . 2
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 4		4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
	6.1. Normative References . . . . . . . . . . . . . . . . . . 5		6.1. Normative References . . . . . . . . . . . . . . . . . . 5
	6.2. Informative References . . . . . . . . . . . . . . . . . 5		6.2. Informative References . . . . . . . . . . . . . . . . . 5
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
			The Border Gateway Protocol uses a mechanism called "Capability
			Advertisement" [RFC5492] to enable BGP peers to tell one another
			about their optional protocol extensions. These so-called
			"Capabilities" are signaled using code points called "Capability
			Codes".
	[RFC5492] designates the range of Capability Codes 128-255 as		[RFC5492] designates the range of Capability Codes 128-255 as
	"Reserved for Private Use". Subsequent experience has shown this to		"Reserved for Private Use". Subsequent experience has shown this to
	be not only useless, but actively confusing to implementors.		be not only useless, but actively confusing to implementors.
	Accordingly, this document revises the registration procedures for		Accordingly, this document revises the registration procedures for
	the range 128-255, as follows, using the terminology defined in		the range 128-255, as follows, using the terminology defined in
	[RFC8126]:		[RFC8126]:
	o 128-238: First Come First Served		o 128-238: First Come First Served
	o 239-254: Experimental Use		o 239-254: Experimental Use
	skipping to change at page 4, line 5 ¶		skipping to change at page 4, line 5 ¶
	+---------+-------------------------+		+---------+-------------------------+
	Table 1		Table 1
	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:
	+------+-------------------------+----------------------------------+		+-------+--------------------------------------------+--------------+
	| Valu | Description | Reference / Change Controller |		| Value | Description | Reference / |
	| e | | |		| | | Change |
	+------+-------------------------+----------------------------------+		| | | Controller |
	| 128 | Prestandard Route | (this document) |		+-------+--------------------------------------------+--------------+
	| | Refresh (deprecated) | |		| 128 | Prestandard Route Refresh (deprecated) | (this |
	+------+-------------------------+----------------------------------+		| | | document) |
	| 129 | Prestandard Outbound | (this document) |		+-------+--------------------------------------------+--------------+
	| | Route Filtering | |		| 129 | Prestandard Outbound Route Filtering | (this |
	| | (deprecated), | |		| | (deprecated), prestandard Routing | document) |
	| | prestandard draft-li- | |		| | Policy Distribution (deprecated) | |
	| | idr-flowspec-rpd-04 | |		+-------+--------------------------------------------+--------------+
	| | (deprecated) | |		| 130 | Prestandard Outbound Route Filtering | (this |
	+------+-------------------------+----------------------------------+		| | (deprecated) | document) |
	| 130 | Prestandard Outbound | (this document) |		+-------+--------------------------------------------+--------------+
	| | Route Filtering | |		| 131 | Prestandard Multisession (deprecated) | (this |
	| | (deprecated) | |		| | | document) |
	+------+-------------------------+----------------------------------+		+-------+--------------------------------------------+--------------+
	| 131 | Prestandard | (this document) |		| 184 | Prestandard FQDN (deprecated) | (this |
	| | Multisession | |		| | | document) |
	| | (deprecated) | |		+-------+--------------------------------------------+--------------+
	+------+-------------------------+----------------------------------+		| 185 | Prestandard OPERATIONAL message | (this |
	| 184 | Prestandard FQDN | (this document) |		| | (deprecated) | document) |
	| | (deprecated) | |		+-------+--------------------------------------------+--------------+
	+------+-------------------------+----------------------------------+		| 255 | Reserved | (this |
	| 185 | OPERATIONAL message | (this document, draft-ietf-idr- |		| | | document) |
	| | (deprecated) | operational-message-00) |		+-------+--------------------------------------------+--------------+
	+------+-------------------------+----------------------------------+
	| 255 | Reserved | (this document) |
	+------+-------------------------+----------------------------------+
	Table 2		Table 2
	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
End of changes. 7 change blocks.
	35 lines changed or deleted		38 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/