rfc9736v1.txt		rfc9736.txt
	skipping to change at line 60 ¶		skipping to change at line 60 ¶
	include Revised BSD License text as described in Section 4.e of the		include Revised BSD License text as described in Section 4.e of the
	Trust Legal Provisions and are provided without warranty as described		Trust Legal Provisions and are provided without warranty as described
	in the Revised BSD License.		in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction		1. Introduction
	1.1. Requirements Language		1.1. Requirements Language
	2. String Definition		2. String Definition
	3. Changes to Existing RFCs		3. Changes to Existing RFCs
	3.1. Revision to the Information TLV, Renamed as Initiation		3.1. Revision to the Information TLV
	Information TLV
	3.2. Revision to the Peer Up Notification		3.2. Revision to the Peer Up Notification
	3.3. Definition of Peer Up Information TLV		3.3. Definition of Peer Up Information TLV
	4. IANA Considerations		4. IANA Considerations
	5. Security Considerations		5. Security Considerations
	6. Normative References		6. Normative References
	Acknowledgements		Acknowledgements
	Authors' Addresses		Authors' Addresses
	1. Introduction		1. Introduction
	[RFC7854] defines a number of different BMP message types. With the		[RFC7854] defines a number of different BMP message types. With the
	exception of the Route Monitoring message type, these messages are		exception of the Route Monitoring message type, these messages are
	TLV-structured. Most message types have distinct namespaces and IANA		TLV-structured. Most message types have distinct namespaces and IANA
	registries. However, the namespace of the Peer Up message overlaps		registries. However, the namespace of the Peer Up message overlaps
	that of the Initiation message. As the BGP Monitoring Protocol has		that of the Initiation message. As the BGP Monitoring Protocol has
	been extended, this oversight has become problematic. In this		been extended, this overlap has become problematic. In this
	document, we create a distinct namespace for the Peer Up message to		document, we create distinct namespaces for the Peer Up and
	eliminate this overlap, and create the corresponding missing		Initiation messages to eliminate the overlap.
	registry.
	Compliant implementations of [RFC7854], [RFC8671], and [RFC9069] also		Compliant implementations of [RFC7854], [RFC8671], and [RFC9069] also
	comply with this specification.		comply with this specification.
	1.1. Requirements Language		1.1. Requirements Language
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in		"OPTIONAL" in this document are to be interpreted as described in
	BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all		BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
	skipping to change at line 104 ¶		skipping to change at line 102 ¶
	A string TLV is a free-form sequence of UTF-8 characters whose length		A string TLV is a free-form sequence of UTF-8 characters whose length
	in bytes is given by the TLV's Length field. There is no requirement		in bytes is given by the TLV's Length field. There is no requirement
	to terminate the string with a null (or any other particular)		to terminate the string with a null (or any other particular)
	character -- the Length field gives its termination.		character -- the Length field gives its termination.
	3. Changes to Existing RFCs		3. Changes to Existing RFCs
	[RFC7854] is updated as detailed in the following subsections.		[RFC7854] is updated as detailed in the following subsections.
	3.1. Revision to the Information TLV, Renamed as Initiation Information		3.1. Revision to the Information TLV
	TLV
	The Information TLV defined in Section 4.4 of [RFC7854] is renamed		The Information TLV defined in Section 4.4 of [RFC7854] is renamed
	"Initiation Information TLV". It is used only by the Initiation		"Initiation Information TLV". It is used only by the Initiation
	message, not by the Peer Up message.		message, not by the Peer Up message.
	The definition of Type = 0 is revised to be:		The definition of Type = 0 is revised as shown below. Type = 1 and
			Type = 2 are unchanged; they are provided for here for completeness.
	* Type = 0: String. The Information field contains a string		* Type = 0: String. The Information field contains a string
	(Section 2). The value is administratively assigned. If multiple		(Section 2). The value is administratively assigned. If multiple
	string TLVs are included, their ordering MUST be preserved when		string TLVs are included, their ordering MUST be preserved when
	they are reported.		they are reported.
	* Type = 1: sysDescr. The Information field contains an ASCII		* Type = 1: sysDescr. The Information field contains an ASCII
	string whose value MUST be set to be equal to the value of the		string whose value MUST be set to be equal to the value of the
	sysDescr MIB-II [RFC1213] object.		sysDescr MIB-II [RFC1213] object.
End of changes. 4 change blocks.
	9 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.48.