rfc9653v2.txt		rfc9653.txt
	skipping to change at line 204 ¶		skipping to change at line 204 ¶
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type = 0x8001 | Length = 8 |		| Type = 0x8001 | Length = 8 |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Error Detection Method Identifier (EDMID) |		| Error Detection Method Identifier (EDMID) |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2: Zero Checksum Acceptable Chunk Parameter		Figure 2: Zero Checksum Acceptable Chunk Parameter
	Type: 16 bits (unsigned integer).		Type: 16 bits (unsigned integer)
	This field holds the IANA-defined parameter type for the "Zero		This field holds the IANA-defined parameter type for the "Zero
	Checksum Acceptable" chunk parameter. IANA has assigned the value		Checksum Acceptable" chunk parameter. IANA has assigned the value
	32769 (0x8001) for this parameter type.		32769 (0x8001) for this parameter type.
	Length: 16 bits (unsigned integer).		Length: 16 bits (unsigned integer)
	This field holds the length in bytes of the chunk parameter; the		This field holds the length in bytes of the chunk parameter; the
	value MUST be 8.		value MUST be 8.
	Error Detection Method Identifier (EDMID): 32 bits (unsigned		Error Detection Method Identifier (EDMID): 32 bits (unsigned
	integer).		integer)
	An IANA-registered value specifying the alternate error detection		An IANA-registered value specifying the alternate error detection
	method the sender of this parameter is willing to use for received		method the sender of this parameter is willing to use for received
	packets.		packets.
	All transported integer numbers are in network byte order, a.k.a. big		All transported integer numbers are in network byte order, a.k.a. big
	endian.		endian.
	The Zero Checksum Acceptable Chunk Parameter MAY appear in INIT and		The Zero Checksum Acceptable Chunk Parameter MAY appear in INIT and
	INIT ACK chunks and MUST NOT appear in any other chunk. The		INIT ACK chunks and MUST NOT appear in any other chunk. The
	Parameter MUST NOT appear more than once in any chunk.		Parameter MUST NOT appear more than once in any chunk.
	skipping to change at line 299 ¶		skipping to change at line 296 ¶
	the alternate error detection method that was announced by the peer		the alternate error detection method that was announced by the peer
	before sending packets with an incorrect checksum of zero.		before sending packets with an incorrect checksum of zero.
	If none of the above restrictions apply, an endpoint SHOULD use zero		If none of the above restrictions apply, an endpoint SHOULD use zero
	as the checksum when sending an SCTP packet.		as the checksum when sending an SCTP packet.
	5.3. Receiver-Side Considerations		5.3. Receiver-Side Considerations
	If an endpoint has sent the Zero Checksum Acceptable Chunk Parameter		If an endpoint has sent the Zero Checksum Acceptable Chunk Parameter
	indicating the support of an alternate error detection method in an		indicating the support of an alternate error detection method in an
	INIT or INIT ACK chunk, it MUST accept SCTP packets fulfilling the		INIT or INIT ACK chunk, in addition to SCTP packets containing the
	requirements of the announced alternate error detection method using		correct CRC32c checksum value it MUST accept SCTP packets that have
	an incorrect checksum value of zero in addition to SCTP packets		an incorrect checksum value of zero and that fulfill the requirements
	containing the correct CRC32c checksum value for this association.		of the announced alternate error detection method used for this
	Otherwise, the endpoint MUST drop all SCTP packets with an incorrect		association. Otherwise, the endpoint MUST drop all SCTP packets with
	CRC32c checksum.		an incorrect CRC32c checksum.
	In addition to processing OOTB packets with a correct CRC32c checksum		In addition to processing OOTB packets with a correct CRC32c checksum
	as specified in [RFC9260], an SCTP implementation MAY also process		as specified in [RFC9260], an SCTP implementation MAY also process
	OOTB packets having an incorrect zero checksum. Doing so might		OOTB packets having an incorrect zero checksum. Doing so might
	result in faster SCTP association failure detection.		result in faster SCTP association failure detection.
	6. Error Detection via SCTP over DTLS		6. Error Detection via SCTP over DTLS
	Using SCTP over DTLS as specified in [RFC8261] provides a stronger		Using SCTP over DTLS as specified in [RFC8261] provides a stronger
	error detection method than using the CRC32c checksum algorithm.		error detection method than using the CRC32c checksum algorithm.
End of changes. 4 change blocks.
	13 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.48.