rfc9292v2.txt		rfc9292.txt
	skipping to change at line 350 ¶		skipping to change at line 350 ¶
	Final Response Control Data {		Final Response Control Data {
	Status Code (i) = 200..599,		Status Code (i) = 200..599,
	}		}
	Figure 4: Format of Final Response Control Data		Figure 4: Format of Final Response Control Data
	3.5.1. Informational Status Codes		3.5.1. Informational Status Codes
	Responses that include informational status codes (see Section 15.2		Responses that include informational status codes (see Section 15.2
	of [HTTP]) are encoded by repeating the response control data and		of [HTTP]) are encoded by repeating the response control data and
	associated header section until a final Status Code is encoded; that		associated header section until a final status code is encoded; that
	is, a Status Code field with a value from 200 to 599 (inclusive).		is, a Status Code field with a value from 200 to 599 (inclusive).
	The status code distinguishes between informational and final		The status code distinguishes between informational and final
	responses.		responses.
	The format of the informational response control data is shown in		The format of the informational response control data is shown in
	Figure 5.		Figure 5.
	Informational Response Control Data {		Informational Response Control Data {
	Status Code (i) = 100..199,		Status Code (i) = 100..199,
	}		}
	skipping to change at line 674 ¶		skipping to change at line 674 ¶
	Type name: message		Type name: message
	Subtype name: bhttp		Subtype name: bhttp
	Required parameters: N/A		Required parameters: N/A
	Optional parameters: N/A		Optional parameters: N/A
	Encoding considerations: Only "8bit" or "binary" is permitted.		Encoding considerations: Only "8bit" or "binary" is permitted.
	Security considerations: See Section 8.		Security considerations: See Section 8.
	Interoperability considerations: N/A		Interoperability considerations: N/A
	Published specification: RFC 9292		Published specification: RFC 9292
	Applications that use this media type: Applications seeking to		Applications that use this media type: Applications seeking to
	convey HTTP request semantics that are independent of a specific		convey HTTP semantics that are independent of a specific protocol.
	protocol.
	Fragment identifier considerations: N/A		Fragment identifier considerations: N/A
	Additional information: Deprecated alias names for this type: N/A		Additional information: Deprecated alias names for this type: N/A
	Magic number(s): N/A		Magic number(s): N/A
	File extension(s): N/A		File extension(s): N/A
	Macintosh file type code(s): N/A		Macintosh file type code(s): N/A
	Person & email address to contact for further information: See the		Person & email address to contact for further information: See the
	Authors' Addresses section.		Authors' Addresses section.
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: N/A		Restrictions on usage: N/A
	Author: See the Authors' Addresses section.		Author: See the Authors' Addresses section.
End of changes. 2 change blocks.
	3 lines changed or deleted		2 lines changed or added
This html diff was produced by rfcdiff 1.48.