rfc9868v4.txt		rfc9868.txt
	skipping to change at line 808 ¶		skipping to change at line 808 ¶
	11. SAFE UDP Options		11. SAFE UDP Options
	SAFE UDP Options can be silently ignored by legacy receivers without		SAFE UDP Options can be silently ignored by legacy receivers without
	affecting the meaning of the UDP user data. They stand in contrast		affecting the meaning of the UDP user data. They stand in contrast
	to UNSAFE Options, which modify UDP user data in ways that render it		to UNSAFE Options, which modify UDP user data in ways that render it
	unusable by legacy receivers (Section 12). The following subsections		unusable by legacy receivers (Section 12). The following subsections
	describe SAFE Options defined in this document.		describe SAFE Options defined in this document.
	11.1. End of Options List (EOL)		11.1. End of Options List (EOL)
	The End of Options List (EOL, Kind=0) option indicates that there are		The End of Options List (EOL, Kind=0) Option indicates that there are
	no more options. It is used to indicate the end of the list of		no more options. It is used to indicate the end of the list of
	options without needing to use NOP Options (see the following		options without needing to use NOP Options (see the following
	section) as padding to fill all available option space.		section) as padding to fill all available option space.
	+--------+		+--------+
	| Kind=0 |		| Kind=0 |
	+--------+		+--------+
	Figure 7: UDP EOL Option Format		Figure 7: UDP EOL Option Format
	skipping to change at line 845 ¶		skipping to change at line 845 ¶
	options area. In this case, the UDP user data MUST be delivered to		options area. In this case, the UDP user data MUST be delivered to
	the application layer, unless the socket has been explicitly		the application layer, unless the socket has been explicitly
	configured to do otherwise, as decided by the upper layer or		configured to do otherwise, as decided by the upper layer or
	negotiated with the other endpoint.		negotiated with the other endpoint.
	Requiring the post-option surplus area to be zero prevents side-		Requiring the post-option surplus area to be zero prevents side-
	channel uses of this area, instead requiring that all use of the		channel uses of this area, instead requiring that all use of the
	surplus area be UDP Options supported by both endpoints. It is		surplus area be UDP Options supported by both endpoints. It is
	useful to allow this area to be used for zero padding to increase the		useful to allow this area to be used for zero padding to increase the
	UDP datagram length without affecting the UDP user data length, e.g.,		UDP datagram length without affecting the UDP user data length, e.g.,
	for UDP DPLPMTUD (Section 4.1 of [RFC9869]).		for UDP DPLPMTUD (Section 4.4 of [RFC9869]).
	11.2. No Operation (NOP)		11.2. No Operation (NOP)
	The No Operation (NOP, Kind=1) option is a one-byte placeholder,		The No Operation (NOP, Kind=1) Option is a one-byte placeholder,
	intended to be used as padding, e.g., to align multi-byte options		intended to be used as padding, e.g., to align multi-byte options
	along 16-bit, 32-bit, or 64-bit boundaries.		along 16-bit, 32-bit, or 64-bit boundaries.
	+--------+		+--------+
	| Kind=1 |		| Kind=1 |
	+--------+		+--------+
	Figure 8: UDP NOP Option Format		Figure 8: UDP NOP Option Format
	>> UDP packets SHOULD NOT use more than seven consecutive NOPs, i.e.,		>> UDP packets SHOULD NOT use more than seven consecutive NOPs, i.e.,
End of changes. 3 change blocks.
	3 lines changed or deleted		3 lines changed or added
This html diff was produced by rfcdiff 1.48.