Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

RFC 9097 §10: Security Considerations

The 7 Requirements of RFC 9097 §10, each quoted from the RFC with its state and the tests that prove it. Conformance explains the states.

StateRequirements
Tested6
Operational1

RFC9097-10-1

Operational

Cooperating Source and Destination hosts and agreements to test the path between the hosts are REQUIRED.

Note: Agreements between the parties that run the hosts.

RFC9097-10-2

Tested

It is REQUIRED to have a user client-initiated setup handshake between cooperating hosts that allows firewalls to control inbound unsolicited UDP traffic that goes to either a control port (expected and with authentication) or ephemeral ports that are only created as needed.

Note: Setup exchange on the Standard Port; Test Connections on Ephemeral Ports.

Proving tests:

RFC9097-10-3

Tested

Client-server authentication and integrity protection for feedback messages conveying measurements are RECOMMENDED.

Note: Authentication Mode 2 (RFC 9946 section 5.3.2).

Proving tests:

RFC9097-10-4

Tested

Hosts MUST limit the number of simultaneous tests to avoid resource exhaustion and inaccurate results.

Note: Admission.

Proving tests:

RFC9097-10-5

Tested

Senders MUST be rate limited.

Note: Sending Rate Table; Admitted Rate Cap.

Proving tests:

RFC9097-10-L1

Tested

The recommended load control search algorithm results in “ramp-up” from the lowest rate in the table.

Note: A Search Test starts at row 0 unless srIndexConf asks otherwise.

Proving tests:

RFC9097-10-6

Tested

Testing with the Service Provider’s measurement hosts SHOULD be limited in frequency and/or overall volume of test traffic (for example, the range of duration values, I, SHOULD be limited).

Note: testIntTime’s maximum.

Proving tests: