rfc9221v1.txt		rfc9221.txt
	skipping to change at line 248 ¶		skipping to change at line 248 ¶
	5.1. Multiplexing Datagrams		5.1. Multiplexing Datagrams
	DATAGRAM frames belong to a QUIC connection as a whole and are not		DATAGRAM frames belong to a QUIC connection as a whole and are not
	associated with any stream ID at the QUIC layer. However, it is		associated with any stream ID at the QUIC layer. However, it is
	expected that applications will want to differentiate between		expected that applications will want to differentiate between
	specific DATAGRAM frames by using identifiers, such as for logical		specific DATAGRAM frames by using identifiers, such as for logical
	flows of datagrams or to distinguish between different kinds of		flows of datagrams or to distinguish between different kinds of
	datagrams.		datagrams.
	Identifiers used to multiplex different kinds of datagrams, or flows		Defining the identifiers used to multiplex different kinds of
	of datagrams, are the responsibility of the application protocol		datagrams or flows of datagrams is the responsibility of the
	running over QUIC to define. The application defines the semantics		application protocol running over QUIC. The application defines the
	of the Datagram Data field and how it is parsed.		semantics of the Datagram Data field and how it is parsed.
	If the application needs to support the coexistence of multiple flows		If the application needs to support the coexistence of multiple flows
	of datagrams, one recommended pattern is to use a variable-length		of datagrams, one recommended pattern is to use a variable-length
	integer at the beginning of the Datagram Data field. This is a		integer at the beginning of the Datagram Data field. This is a
	simple approach that allows a large number of flows to be encoded		simple approach that allows a large number of flows to be encoded
	using minimal space.		using minimal space.
	QUIC implementations SHOULD present an API to applications to assign		QUIC implementations SHOULD present an API to applications to assign
	relative priorities to DATAGRAM frames with respect to each other and		relative priorities to DATAGRAM frames with respect to each other and
	to QUIC streams.		to QUIC streams.
	skipping to change at line 355 ¶		skipping to change at line 355 ¶
	Parameters" registry maintained at <https://www.iana.org/assignments/		Parameters" registry maintained at <https://www.iana.org/assignments/
	quic>.		quic>.
	Value: 0x20		Value: 0x20
	Parameter Name: max_datagram_frame_size		Parameter Name: max_datagram_frame_size
	Status: permanent		Status: permanent
	Specification: RFC 9221		Specification: RFC 9221
	7.2. QUIC Frame Types		7.2. QUIC Frame Types
	This document registers two new values in the QUIC Frame Type		This document registers two new values in the "QUIC Frame Types"
	registry maintained at <https://www.iana.org/assignments/quic>.		registry maintained at <https://www.iana.org/assignments/quic>.
	Value: 0x30 and 0x31		Value: 0x30-0x31
	Frame Name: DATAGRAM		Frame Name: DATAGRAM
	Status: permanent		Status: permanent
	Specification: RFC 9221		Specification: RFC 9221
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
End of changes. 3 change blocks.
	6 lines changed or deleted		6 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/