12. IANA Considerations
This section preserves the RFC text for UDPSTP, including One-Way IP Capacity metrics, Control and Data phases, Load and Status Feedback PDUs, KDF/HMAC authentication, optional checksum handling, IANA registries, and security considerations.
Original RFC Text
12. IANA Considerations
Per this document, IANA has assigned a UDP port number for the Test
Setup exchange in the Control phase of protocol operation and has
created a new registry group for the UDPSTP.
12.1. New User Port Number Assignment
IANA has registered the following service name in the "Service Name
and Transport Protocol Port Number Registry":
Service Name: udpstp
Port Number: 24601
Transport Protocol: udp
Description: UDP-based IP-Layer Capacity and Performance Measurement
protocol
Assignee: IESG <[email protected]>
Contact: IETF Chair <[email protected]>
Reference: RFC 9946
The protocol uses IP-Layer Unicast. A single port number was
assigned to help configure firewalls and other port-based systems for
access control prior to negotiating dynamic ports between client and
server.
12.2. New KeyTable KDF
IANA has added the following KDF entry to the "KeyTable KDFs"
registry (see <https://www.iana.org/assignments/keytable>):
+==============+=============================+===========+
| KDF | Description | Reference |
+==============+=============================+===========+
| HMAC-SHA-256 | HMAC using the SHA-256 hash | [RFC6234] |
+--------------+-----------------------------+-----------+
Table 1: KeyTable KDFs Registry
12.3. New UDPSTP Registry Group
IANA has created the registries in the subsections that follow under
a new registry group called "UDP Speed Test Protocol (UDPSTP)".
IANA has added the following note under the "UDP Speed Test Protocol
(UDPSTP)" registry group:
| Note: Values reserved for Experimental Use are not expected to be
| used on the Internet but are expected to be used for experiments
| that are confined to closed environments.
12.3.1. PDU Identifier Registry
IANA has created the "PDU Identifier" registry under the "UDP Speed
Test Protocol (UDPSTP)" registry group. Every UDPSTP PDU contains a
two-octet pduId field identifying the role and format of the PDU that
follows. The code points in this registry are allocated according to
the registration procedures [RFC8126] described in Table 2.
+===============+=========================+
| Range | Registration Procedures |
+===============+=========================+
| 0x0000 | Reserved |
+---------------+-------------------------+
| 0x0001-0x7F00 | Specification Required |
+---------------+-------------------------+
| 0x7F01-0x7FE0 | Experimental Use |
+---------------+-------------------------+
| 0x7FE1-0x7FFF | Private Use |
+---------------+-------------------------+
| 0x8000-0xFFFE | IETF Review |
+---------------+-------------------------+
| 0xFFFF | Reserved |
+---------------+-------------------------+
Table 2: Registration Procedures for
the PDU Identifier Registry
IANA has assigned values in the "PDU Identifier" registry as follows:
+===============+===============================+===========+
| Value | Description | Reference |
+===============+===============================+===========+
| 0x0000 | Reserved | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0x7F01-0x7FE0 | Reserved for Experimental Use | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0x7FE1-0x7FFF | Reserved for Private Use | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0xACE1 | Test Setup PDU | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0xACE2 | Test Activation PDU | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0xBEEF | Load PDU | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0xDEAD | Null PDU | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0xFEED | Status Feedback PDU | RFC 9946 |
+---------------+-------------------------------+-----------+
| 0xFFFF | Reserved | RFC 9946 |
+---------------+-------------------------------+-----------+
Table 3: Initial Values of the PDU Identifier Registry
12.3.2. Protocol Version Registry
IANA has created the "Protocol Version" registry under the "UDP Speed
Test Protocol (UDPSTP)" registry group. UDPSTP Test Setup Request,
Test Setup Response, and Test Activation Request PDUs contain a two-
octet protocolVer field, identifying the version of the protocol in
use. The code points in this registry are allocated according to the
registration procedures [RFC8126] described in Table 4.
+=============+=========================+
| Range | Registration Procedures |
+=============+=========================+
| 0-19 | Reserved |
+-------------+-------------------------+
| 20-40960 | IETF Review |
+-------------+-------------------------+
| 40961-53248 | Specification Required |
+-------------+-------------------------+
| 53249-65534 | Experimental Use |
+-------------+-------------------------+
| 65535 | Reserved |
+-------------+-------------------------+
Table 4: Registration Procedures for
the Protocol Version Registry
IANA has assigned decimal value 20 in the "Protocol Version" registry
as follows:
+=======+===========+
| Value | Reference |
+=======+===========+
| 20 | RFC 9946 |
+-------+-----------+
Table 5: Initial Value
of the Protocol
Version Registry
12.3.3. Test Setup PDU Modifier Bitmap Registry
IANA has created the "Test Setup PDU Modifier Bitmap" registry under
the "UDP Speed Test Protocol (UDPSTP)" registry group. The Test
Setup PDU layout contains a modifierBitmap field. The bitmaps in
this registry are allocated according to the registration procedures
[RFC8126] described in Table 6.
+===================+=========================+
| Range | Registration Procedures |
+===================+=========================+
| 00000000-01111111 | IETF Review |
+-------------------+-------------------------+
| 10000000 | Reserved |
+-------------------+-------------------------+
Table 6: Registration Procedures for the
Test Setup PDU Modifier Bitmap Registry
IANA has assigned bitmap values in the "Test Setup PDU Modifier
Bitmap" registry as follows:
+=======+===============================+===========+
| Value | Description | Reference |
+=======+===============================+===========+
| 0x00 | No modifications | RFC 9946 |
+-------+-------------------------------+-----------+
| 0x01 | Allow Jumbo datagram sizes | RFC 9946 |
| | above sending rates of 1 Gbps | |
+-------+-------------------------------+-----------+
| 0x02 | Use Traditional MTU (1500 | RFC 9946 |
| | bytes with an IP header) | |
+-------+-------------------------------+-----------+
Table 7: Initial Values of the Test Setup PDU
Modifier Bitmap Registry
12.3.4. Test Setup PDU Authentication Mode Registry
IANA has created the "Test Setup PDU Authentication Mode" registry
under the "UDP Speed Test Protocol (UDPSTP)" registry group. The
Test Setup PDU layout contains an authMode field. The code points in
this registry are allocated according to the registration procedures
[RFC8126] described in Table 8.
+========+=========================+
| Range | Registration Procedures |
+========+=========================+
| 0-59 | IETF Review |
+--------+-------------------------+
| 60-63 | Experimental Use |
+--------+-------------------------+
| 64-255 | Reserved |
+--------+-------------------------+
Table 8: Registration Procedures
for the Test Setup PDU
Authentication Mode Registry
IANA has assigned decimal values in the "Test Setup PDU
Authentication Mode" registry as follows:
+=======+===============================================+===========+
| Value | Description | Reference |
+=======+===============================================+===========+
| 0 | Not used | RFC 9946 |
+-------+-----------------------------------------------+-----------+
| 1 | Required authentication for | RFC 9946 |
| | the Control phase | |
+-------+-----------------------------------------------+-----------+
| 2 | Required authentication for | RFC 9946 |
| | the Control and Data phases | |
+-------+-----------------------------------------------+-----------+
Table 9: Initial Values of the Test Setup PDU Authentication Mode
Registry
12.3.5. 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
Test Setup PDU layout contains a cmdResponse field. The code points
in this registry are allocated according to the registration
procedures [RFC8126] described in Table 10.
+=========+=========================+
| Range | Registration Procedures |
+=========+=========================+
| 0-127 | IETF Review |
+---------+-------------------------+
| 128-239 | Specification Required |
+---------+-------------------------+
| 240-249 | Experimental Use |
+---------+-------------------------+
| 250-254 | Private Use |
+---------+-------------------------+
| 255 | Reserved |
+---------+-------------------------+
Table 10: Registration Procedures
for the Test Setup PDU Command
Response Field Registry
IANA has assigned decimal values in the "Test Setup PDU Command
Response Field" registry as follows:
+=========+============================================+===========+
| Value | Description | Reference |
+=========+============================================+===========+
| 0 | None (used by client in Request) | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 1 | Acknowledgment | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 2 | Bad protocol version | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 3 | Invalid Jumbo datagram option | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 4 | Unexpected authentication in Setup Request | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 5 | Authentication missing in Setup Request | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 6 | Invalid authentication method | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 7 | Authentication failure | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 8 | Authentication time is invalid in Setup | RFC 9946 |
| | Request | |
+---------+--------------------------------------------+-----------+
| 9 | No maximum test bit rate specified | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 10 | Server maximum bit rate exceeded | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 11 | MTU option does not match server | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 12 | Multi-connection parameters rejected by | RFC 9946 |
| | server | |
+---------+--------------------------------------------+-----------+
| 13 | Connection allocation failure on server | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 240-249 | Reserved for Experimental Use | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 250-254 | Reserved for Private Use | RFC 9946 |
+---------+--------------------------------------------+-----------+
| 255 | Reserved | RFC 9946 |
+---------+--------------------------------------------+-----------+
Table 11: Initial Values of the Test Setup PDU Command Response
Field Registry
Note that value 4 is required for backward compatibility with
previous experimental versions of software already in use. Further,
value 6 signals that a client erroneously used an authMode that
hasn't been standardized yet (i.e., authMode is greater than 1 or 2).
12.3.6. Test Activation PDU Command Request Registry
IANA has created the "Test Activation PDU Command Request" registry
under the "UDP Speed Test Protocol (UDPSTP)" registry group. The
Test Setup PDU layout contains a cmdRequest field. The code points
in this registry are allocated according to the registration
procedures [RFC8126] described in Table 12.
+=========+=========================+
| Range | Registration Procedures |
+=========+=========================+
| 0-127 | IETF Review |
+---------+-------------------------+
| 128-239 | Specification Required |
+---------+-------------------------+
| 240-249 | Experimental Use |
+---------+-------------------------+
| 250-254 | Private Use |
+---------+-------------------------+
| 255 | Reserved |
+---------+-------------------------+
Table 12: Registration Procedures
for the Test Activation PDU
Command Request Registry
IANA has assigned decimal values in the "Test Activation PDU Command
Request" registry as follows:
+=========+==============================+===========+
| Value | Description | Reference |
+=========+==============================+===========+
| 0 | No Request | RFC 9946 |
+---------+------------------------------+-----------+
| 1 | Request test in upstream | RFC 9946 |
| | direction (client to server) | |
+---------+------------------------------+-----------+
| 2 | Request test in downstream | RFC 9946 |
| | direction (server to client) | |
+---------+------------------------------+-----------+
| 240-249 | Reserved for Experimental | RFC 9946 |
| | Use | |
+---------+------------------------------+-----------+
| 250-254 | Reserved for Private Use | RFC 9946 |
+---------+------------------------------+-----------+
| 255 | Reserved | RFC 9946 |
+---------+------------------------------+-----------+
Table 13: Initial Values of the Test Activation
PDU Command Request Registry
12.3.7. Test Activation PDU Modifier Bitmap Registry
IANA has created the "Test Activation PDU Modifier Bitmap" registry
under the "UDP Speed Test Protocol (UDPSTP)" registry group. The
Test Activation PDU layout (also) contains a modifierBitmap field.
The bitmaps in this registry are allocated according to the
registration procedures [RFC8126] described in Table 14.
+===================+=========================+
| Range | Registration Procedures |
+===================+=========================+
| 00000000-01111111 | IETF Review |
+-------------------+-------------------------+
| 10000000 | Reserved |
+-------------------+-------------------------+
Table 14: Registration Procedures for the
Test Activation PDU Modifier Bitmap
Registry
IANA has assigned bitmap values in the "Test Activation PDU Modifier
Bitmap" registry as follows:
+=======+===============================================+===========+
| Value | Description | Reference |
+=======+===============================================+===========+
| 0x00 | No modifications | RFC 9946 |
+-------+-----------------------------------------------+-----------+
| 0x01 | Set when srIndexConf is | RFC 9946 |
| | start rate for search | |
+-------+-----------------------------------------------+-----------+
| 0x02 | Set for randomized UDP | RFC 9946 |
| | payload | |
+-------+-----------------------------------------------+-----------+
Table 15: Initial Values of the Test Activation PDU Modifier
Bitmap Registry
12.3.8. Test Activation PDU Rate Adjustment Algo Registry
IANA has created the "Test Activation PDU Rate Adjustment Algo"
registry under the "UDP Speed Test Protocol (UDPSTP)" registry group.
The Test Activation PDU layout contains a rateAdjAlgo field. The
code points in this registry are allocated according to the
registration procedures [RFC8126] described in Table 16.
+=======+=========================+
| Range | Registration Procedures |
+=======+=========================+
| A-Y | IETF Review |
+-------+-------------------------+
| Z | Reserved |
+-------+-------------------------+
Table 16: Registration
Procedures for the Test
Activation PDU Rate Adjustment
Algo Registry
IANA has added the following note under the "Test Activation PDU Rate
Adjustment Algo" registry:
| Note: The algorithm identifier is a capitalized alphabetic UTF-8
| value (A-Z), specified by the corresponding incremental numeric.
IANA has assigned capitalized alphabetic UTF-8 values, as well as the
corresponding incremental numeric values, in the "Test Activation PDU
Rate Adjustment Algo" registry as follows:
+================+=======================+==============+
| Value(Numeric) | Description | Reference |
+================+=======================+==============+
| A(n/a) | Not used | RFC 9946 |
+----------------+-----------------------+--------------+
| B(0) | Rate algorithm Type B | [Y.1540Amd2] |
+----------------+-----------------------+--------------+
| C(1) | Rate algorithm Type C | [TR-471] |
+----------------+-----------------------+--------------+
Table 17: Initial Values of the Test Activation PDU
Rate Adjustment Algo Registry
12.3.9. Test Activation PDU Command Response Field Registry
IANA has created the "Test Activation PDU Command Response Field"
registry under the "UDP Speed Test Protocol (UDPSTP)" registry group.
The Test Activation PDU layout (also) contains a cmdResponse field.
The code points in this registry are allocated according to the
registration procedures [RFC8126] described in Table 18.
+=========+=========================+
| Range | Registration Procedures |
+=========+=========================+
| 0-127 | IETF Review |
+---------+-------------------------+
| 128-239 | Specification Required |
+---------+-------------------------+
| 240-249 | Experimental Use |
+---------+-------------------------+
| 250-254 | Private Use |
+---------+-------------------------+
| 255 | Reserved |
+---------+-------------------------+
Table 18: Registration Procedures
for the Test Activation PDU
Command Response Field Registry
IANA has assigned decimal values in the "Test Activation PDU Command
Response Field" registry as follows:
+=========+==================================+===========+
| Value | Description | Reference |
+=========+==================================+===========+
| 0 | None (used by client in Request) | RFC 9946 |
+---------+----------------------------------+-----------+
| 1 | Server acknowledgment | RFC 9946 |
+---------+----------------------------------+-----------+
| 2 | Server indicates an error | RFC 9946 |
+---------+----------------------------------+-----------+
| 240-249 | Reserved for Experimental Use | RFC 9946 |
+---------+----------------------------------+-----------+
| 250-254 | Reserved for Private Use | RFC 9946 |
+---------+----------------------------------+-----------+
| 255 | Reserved | RFC 9946 |
+---------+----------------------------------+-----------+
Table 19: Initial Values of the Test Activation PDU
Command Response Field Registry
12.4. Guidelines for Designated Experts
It is suggested that multiple designated experts be appointed for
registry change requests.
Criteria that should be applied by the designated experts include
determining whether the proposed registration duplicates existing
entries and whether the registration description is clear and fits
the purpose of this registry.
Registration requests are evaluated within a two-week review period
on the advice of one or more designated experts. Within the review
period, the designated experts will either approve or deny the
registration request, communicating this decision to IANA. Denials
should include an explanation and, if applicable, suggestions as to
how to make the request successful.