rfc9209v8.txt		rfc9209.txt
	skipping to change at line 334 ¶		skipping to change at line 334 ¶
	2.1.3. next-protocol		2.1.3. next-protocol
	The next-protocol parameter's value indicates the Application-Layer		The next-protocol parameter's value indicates the Application-Layer
	Protocol Negotiation (ALPN) protocol identifier [RFC7301] of the		Protocol Negotiation (ALPN) protocol identifier [RFC7301] of the
	protocol used by the intermediary to connect to the next hop when		protocol used by the intermediary to connect to the next hop when
	obtaining this response.		obtaining this response.
	The value MUST be either a Token or Byte Sequence representing a TLS		The value MUST be either a Token or Byte Sequence representing a TLS
	ALPN Protocol ID (see <https://www.iana.org/assignments/tls-		ALPN Protocol ID (see <https://www.iana.org/assignments/tls-
	extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-		extensiontype-values#alpn-protocol-ids>). If the protocol identifier
	ids>). If the protocol identifier is able to be expressed as a Token		is able to be expressed as a Token using ASCII encoding, that form
	using ASCII encoding, that form MUST be used.		MUST be used.
	For example:		For example:
	Proxy-Status: "proxy.example.org"; next-protocol=h2		Proxy-Status: "proxy.example.org"; next-protocol=h2
	Note that the ALPN identifier is being used here to identify the		Note that the ALPN identifier is being used here to identify the
	protocol in use; it may or may not have been actually used in the		protocol in use; it may or may not have been actually used in the
	protocol negotiation.		protocol negotiation.
	2.1.4. received-status		2.1.4. received-status
End of changes. 1 change blocks.
	3 lines changed or deleted		3 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/