rfc9946v7.txt		rfc9946.txt
	Internet Engineering Task Force (IETF) A. Morton		Internet Engineering Task Force (IETF) A. Morton
	Request for Comments: 9946 L. Ciavattone		Request for Comments: 9946 L. Ciavattone
	Category: Standards Track AT&T Labs		Category: Standards Track AT&T Labs
	ISSN: 2070-1721 R. Geib, Ed.		ISSN: 2070-1721 R. Geib, Ed.
	Deutsche Telekom		Deutsche Telekom
	March 2026		April 2026
	The UDP Speed Test Protocol (UDPSTP) for One-Way IP Capacity Metric		The UDP Speed Test Protocol (UDPSTP) for One-Way IP Capacity Metric
	Measurement		Measurement
	Abstract		Abstract
	This document addresses the problem of protocol support for measuring		This document addresses the problem of protocol support for measuring
	One-Way IP Capacity metrics specified by RFC 9097. The Method of		One-Way IP Capacity metrics specified by RFC 9097. The Method of
	Measurement discussed in that RFC requires a feedback channel from		Measurement discussed in that RFC requires a feedback channel from
	the receiver to control the sender's transmission rate in near real-		the receiver to control the sender's transmission rate in near real-
	skipping to change at line 478 ¶		skipping to change at line 478 ¶
	load rate adjustment algorithm requirements listed below reflect		load rate adjustment algorithm requirements listed below reflect
	feedback from performance measurement experts, as well as changes		feedback from performance measurement experts, as well as changes
	resulting from the standardization of [RFC9097] (reflected also in		resulting from the standardization of [RFC9097] (reflected also in
	algorithm B [Y.1540Amd2], which updates a prior version of this		algorithm B [Y.1540Amd2], which updates a prior version of this
	algorithm).		algorithm).
	Load rate adjustment algorithms for capacity measurement MUST comply		Load rate adjustment algorithms for capacity measurement MUST comply
	with the requirements specified by this section. New standard load		with the requirements specified by this section. New standard load
	rate adjustment algorithms for capacity measurement MUST be reviewed		rate adjustment algorithms for capacity measurement MUST be reviewed
	by IETF designated experts prior to assignment of a code point in the		by IETF designated experts prior to assignment of a code point in the
	"Test Activation PDU Rate Adjustment Algorithm" registry.		"Test Activation PDU Rate Adjustment Algo" registry.
	The load rate adjustment algorithm for capacity measurement		The load rate adjustment algorithm for capacity measurement
	requirements are as follows:		requirements are as follows:
	1. The measurement load rate adjustment algorithm described in this		1. The measurement load rate adjustment algorithm described in this
	section MUST NOT be used as a general CCA.		section MUST NOT be used as a general CCA.
	2. This specification MUST only be used in the application of		2. This specification MUST only be used in the application of
	diagnostic and operations measurements.		diagnostic and operations measurements.
	skipping to change at line 978 ¶		skipping to change at line 978 ¶
	testPort: A two-octet field set to zero in the Test Setup Request		testPort: A two-octet field set to zero in the Test Setup Request
	and populated by the server in the Test Setup Response. It		and populated by the server in the Test Setup Response. It
	contains the UDP ephemeral port number on the server that the		contains the UDP ephemeral port number on the server that the
	client has to use for the Test Activation Request and subsequent		client has to use for the Test Activation Request and subsequent
	Load or Status PDUs.		Load or Status PDUs.
	modifierBitmap: A one-octet field. This document only assigns two		modifierBitmap: A one-octet field. This document only assigns two
	bits in this bitmap; see Section 12.3.3:		bits in this bitmap; see Section 12.3.3:
	CHSR_JUMBO_STATUS: This bit SHALL be set by default. By default,		CHSR_JUMBO_STATUS (0x01): This bit SHALL be set by default. By
	sending rates up to 1 Gbps SHALL NOT produce IP packet sizes		default, sending rates up to 1 Gbps SHALL NOT produce IP packet
	greater than 1250 bytes (unless CHSR_TRADITIONAL_MTU is set),		sizes greater than 1250 bytes (unless CHSR_TRADITIONAL_MTU is
	while rates above 1 Gbps MAY produce IP packet sizes up to 9000		set), while rates above 1 Gbps MAY produce IP packet sizes up
	bytes. When CHSR_JUMBO_STATUS is not set, all sending rates		to 9000 bytes. When CHSR_JUMBO_STATUS is not set, all sending
	SHALL NOT produce IP packet sizes greater than 1250 bytes		rates SHALL NOT produce IP packet sizes greater than 1250 bytes
	(unless CHSR_TRADITIONAL_MTU is set).		(unless CHSR_TRADITIONAL_MTU is set).
	CHSR_TRADITIONAL_MTU: This bit SHALL NOT be set by default. If		CHSR_TRADITIONAL_MTU (0x02): This bit SHALL NOT be set by
	set, sending rates up to 1 Gbps MAY produce IP packets up to		default. If set, sending rates up to 1 Gbps MAY produce IP
	the traditional size of 1500 bytes. If CHSR_JUMBO_STATUS is		packets up to the traditional size of 1500 bytes. If
	simultaneously not set, all sending rates SHALL NOT produce IP		CHSR_JUMBO_STATUS is simultaneously not set, all sending rates
	packets greater than the traditional size of 1500 bytes.		SHALL NOT produce IP packets greater than the traditional size
			of 1500 bytes.
	Other bit positions are left unassigned per this document.		Other bit positions are left unassigned per this document.
	authMode: A one-octet field. The authMode field currently has two		authMode: A one-octet field. The authMode field currently has two
	values assigned (see Section 12.3.4). One of the following has to		values assigned (see Section 12.3.4). One of the following has to
	be set (see Section 5.3 for requirements and details of		be set (see Section 5.3 for requirements and details of
	operation):		operation):
	AUTHMODE_1: Required Authentication for Control phase.		AUTHMODE_1: Required authentication for the Control phase.
	AUTHMODE_2: Optional Authentication for Control and Data phase		AUTHMODE_2: Required authentication for the Control and Data
	(Status Feedback PDU only).		phases (Status Feedback PDU only).
	A range of 60 through 63 is reserved for experimentation. IANA has		A range of 60 through 63 is reserved for experimentation. IANA has
	created a registry for the assigned values; see the IANA		created the "Test Setup PDU Authentication Mode” registry for the
	Considerations section.		assigned values; see Section 12.3.4.
	authUnixTime: A 32-bit timestamp of the current system (wall-clock)		authUnixTime: A 32-bit timestamp of the current system (wall-clock)
	time since the Unix Epoch on January 1, 1970 at 00:00:00 UTC.		time since the Unix Epoch on January 1, 1970 at 00:00:00 UTC.
	authDigest: This field contains the 32-octet HMAC-SHA-256 hash that		authDigest: This field contains the 32-octet HMAC-SHA-256 hash that
	covers the entire PDU. Normally, the calculation is done as the		covers the entire PDU. Normally, the calculation is done as the
	last step of building the PDU. However, if the optional checkSum		last step of building the PDU. However, if the optional checkSum
	field is being utilized, it becomes the penultimate step and is		field is being utilized, it becomes the penultimate step and is
	done just prior to the checksum calculation (with the checkSum		done just prior to the checksum calculation (with the checkSum
	field set to zero).		field set to zero).
	skipping to change at line 1466 ¶		skipping to change at line 1467 ¶
	ignoreOooDup: A one-octet field. Ignore out-of-order duplicates,		ignoreOooDup: A one-octet field. Ignore out-of-order duplicates,
	Boolean. When True, only loss counts toward received packet		Boolean. When True, only loss counts toward received packet
	sequence number errors. When False, loss, out-of-order, and		sequence number errors. When False, loss, out-of-order, and
	duplicate totals are all counted as sequence number errors.		duplicate totals are all counted as sequence number errors.
	Default is True (see also Table 3 of [TR-471]).		Default is True (see also Table 3 of [TR-471]).
	modifierBitmap: A one-octet field. This document only assigns two		modifierBitmap: A one-octet field. This document only assigns two
	bits in this bitmap; see Section 12.3.7:		bits in this bitmap; see Section 12.3.7:
	CHTA_SRIDX_ISSTART: Treat srIndexConf as the starting sending		CHTA_SRIDX_ISSTART (0x01): Treat srIndexConf as the starting
	rate to be used by the load rate adjustment algorithm.		sending rate to be used by the load rate adjustment algorithm.
	CHTA_RAND_PAYLOAD: Randomize the payload content beyond the Load		CHTA_RAND_PAYLOAD (0x02): Randomize the payload content beyond
	PDU header.		the Load PDU header.
	Other bit positions are left unassigned per this document.		Other bit positions are left unassigned per this document.
	rateAdjAlgo: A one-octet field. The applied load rate adjustment		rateAdjAlgo: A one-octet field. The applied load rate adjustment
	algorithm; see Section 12.3.8.		algorithm; see Section 12.3.8.
	srStruct: Sending Rate structure. Used by the server in a Test		srStruct: Sending Rate structure. Used by the server in a Test
	Activation Response for an upstream test to communicate the		Activation Response for an upstream test to communicate the
	(initial) Load PDU transmission parameters the client SHALL use.		(initial) Load PDU transmission parameters the client SHALL use.
	For a Test Activation Request or a downstream test, this structure		For a Test Activation Request or a downstream test, this structure
	skipping to change at line 2662 ¶		skipping to change at line 2663 ¶
	Authentication Mode Registry		Authentication Mode Registry
	IANA has assigned decimal values in the "Test Setup PDU		IANA has assigned decimal values in the "Test Setup PDU
	Authentication Mode" registry as follows:		Authentication Mode" registry as follows:
	+=======+===============================================+===========+		+=======+===============================================+===========+
	| Value | Description | Reference |		| Value | Description | Reference |
	+=======+===============================================+===========+		+=======+===============================================+===========+
	| 0 | Not used | RFC 9946 |		| 0 | Not used | RFC 9946 |
	+-------+-----------------------------------------------+-----------+		+-------+-----------------------------------------------+-----------+
	| 1 | Required authentication for the Control | RFC 9946 |		| 1 | Required authentication for | RFC 9946 |
	| | phase | |		| | the Control phase | |
	+-------+-----------------------------------------------+-----------+		+-------+-----------------------------------------------+-----------+
	| 2 | Optional authentication for the Data | RFC 9946 |		| 2 | Required authentication for | RFC 9946 |
	| | phase, in addition to the Control phase | |		| | the Control and Data phases | |
	+-------+-----------------------------------------------+-----------+		+-------+-----------------------------------------------+-----------+
	Table 9: Initial Values of the Test Setup PDU Authentication Mode		Table 9: Initial Values of the Test Setup PDU Authentication Mode
	Registry		Registry
	12.3.5. Test Setup PDU Command Response Field Registry		12.3.5. Test Setup PDU Command Response Field Registry
	IANA has created the "Test Setup PDU Command Response Field" registry		IANA has created the "Test Setup PDU Command Response Field" registry
	under the "UDP Speed Test Protocol (UDPSTP)" registry group. The		under the "UDP Speed Test Protocol (UDPSTP)" registry group. The
	Test Setup PDU layout contains a cmdResponse field. The code points		Test Setup PDU layout contains a cmdResponse field. The code points
End of changes. 11 change blocks.
	26 lines changed or deleted		27 lines changed or added
This html diff was produced by rfcdiff 1.48.