rfc9622v2.txt		rfc9622.txt
	skipping to change at line 681 ¶		skipping to change at line 681 ¶
	Namespace (e.g., a Connection that uses TCP could support a TCP-		Namespace (e.g., a Connection that uses TCP could support a TCP-
	specific Transport Property, such as the TCP User Timeout value,		specific Transport Property, such as the TCP User Timeout value,
	in a Protocol-specific Property called tcp.userTimeoutValue (see		in a Protocol-specific Property called tcp.userTimeoutValue (see
	Section 8.2)).		Section 8.2)).
	* Vendor-specific or implementation-specific properties MUST be		* Vendor-specific or implementation-specific properties MUST be
	placed in a Namespace starting with the underscore _ character and		placed in a Namespace starting with the underscore _ character and
	SHOULD use a string identifying the vendor or implementation.		SHOULD use a string identifying the vendor or implementation.
	* For IETF protocols, the name of a Protocol-specific Property MUST		* For IETF protocols, the name of a Protocol-specific Property MUST
	be specified in an RFC from the IETF Stream (after IETF review).		be specified in an RFC from the IETF Stream (after IETF Review
	An IETF protocol Namespace does not start with an underscore		[RFC8126]). An IETF protocol Namespace does not start with an
	character ("_").		underscore character ("_").
	Namespaces for each of the keywords provided in the "Protocol		Namespaces for each of the keywords provided in the "Protocol
	Numbers" registry (see <https://www.iana.org/assignments/protocol-		Numbers" registry (see <https://www.iana.org/assignments/protocol-
	numbers/>) are reserved for Protocol-specific Properties and MUST NOT		numbers/>) are reserved for Protocol-specific Properties and MUST NOT
	be used for vendor-specific or implementation-specific properties.		be used for vendor-specific or implementation-specific properties.
	Terms listed as keywords, as in the "Protocol Numbers" registry,		Terms listed as keywords, as in the "Protocol Numbers" registry,
	SHOULD be avoided as any part of a vendor-specific or implementation-		SHOULD be avoided as any part of a vendor-specific or implementation-
	specific property name.		specific property name.
	Though Transport Property Names are case insensitive, it is		Though Transport Property Names are case insensitive, it is
	skipping to change at line 4043 ¶		skipping to change at line 4043 ¶
	[RFC8085] Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage		[RFC8085] Eggert, L., Fairhurst, G., and G. Shepherd, "UDP Usage
	Guidelines", BCP 145, RFC 8085, DOI 10.17487/RFC8085,		Guidelines", BCP 145, RFC 8085, DOI 10.17487/RFC8085,
	March 2017, <https://www.rfc-editor.org/info/rfc8085>.		March 2017, <https://www.rfc-editor.org/info/rfc8085>.
	[RFC8095] Fairhurst, G., Ed., Trammell, B., Ed., and M. Kuehlewind,		[RFC8095] Fairhurst, G., Ed., Trammell, B., Ed., and M. Kuehlewind,
	Ed., "Services Provided by IETF Transport Protocols and		Ed., "Services Provided by IETF Transport Protocols and
	Congestion Control Mechanisms", RFC 8095,		Congestion Control Mechanisms", RFC 8095,
	DOI 10.17487/RFC8095, March 2017,		DOI 10.17487/RFC8095, March 2017,
	<https://www.rfc-editor.org/info/rfc8095>.		<https://www.rfc-editor.org/info/rfc8095>.
			[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
			Writing an IANA Considerations Section in RFCs", BCP 26,
			RFC 8126, DOI 10.17487/RFC8126, June 2017,
			<https://www.rfc-editor.org/info/rfc8126>.
	[RFC8260] Stewart, R., Tuexen, M., Loreto, S., and R. Seggelmann,		[RFC8260] Stewart, R., Tuexen, M., Loreto, S., and R. Seggelmann,
	"Stream Schedulers and User Message Interleaving for the		"Stream Schedulers and User Message Interleaving for the
	Stream Control Transmission Protocol", RFC 8260,		Stream Control Transmission Protocol", RFC 8260,
	DOI 10.17487/RFC8260, November 2017,		DOI 10.17487/RFC8260, November 2017,
	<https://www.rfc-editor.org/info/rfc8260>.		<https://www.rfc-editor.org/info/rfc8260>.
	[RFC8293] Ghanwani, A., Dunbar, L., McBride, M., Bannai, V., and R.		[RFC8293] Ghanwani, A., Dunbar, L., McBride, M., Bannai, V., and R.
	Krishnan, "A Framework for Multicast in Network		Krishnan, "A Framework for Multicast in Network
	Virtualization over Layer 3", RFC 8293,		Virtualization over Layer 3", RFC 8293,
	DOI 10.17487/RFC8293, January 2018,		DOI 10.17487/RFC8293, January 2018,
End of changes. 2 change blocks.
	3 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.48.