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 9946 §11: Security Considerations

The 8 Requirements of RFC 9946 §11, each quoted from the RFC with its state and the tests that prove it. Conformance explains the states.

StateRequirements
Tested6
Deviation1
Operational1

RFC9946-11-1

Operational

Cooperating client and server hosts and agreements to test the path between the hosts are REQUIRED.

Note: Agreements between the parties; authentication (Section 5.3) is one way to assure them.

RFC9946-11-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 or ephemeral ports that are only created as needed.

Note: Test Setup exchange (Section 6); Ephemeral Ports opened per Test Connection.

Proving tests:

RFC9946-11-3

Tested

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

Note: authMode 2 (Section 5.3.2).

Proving tests:

RFC9946-11-4

Tested

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

Note: Server limits on Tests and Test Connections.

Conformance Records: per-test-cap-over-the-tests-life, admitted-rate-reserved-at-activation, max-test-share-of-the-rate-cap, unactivated-test-connection-share.

Proving tests:

RFC9946-11-5

Tested

Senders MUST be rate-limited.

Note: The Sending Rate Table bounds every rate.

Conformance Records: search-capped-at-stated-max-bandwidth, consumer-start-row-capped.

Proving tests:

RFC9946-11-6

Deviation

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 test interval duration values should be limited).

Recorded in no-frequency-or-volume-quotas.

Proving tests:

RFC9946-11-L1

Tested

This can be accomplished using a pre-built table defining all the offered sending rates that will be supported.

Note: The Sending Rate Table.

Proving tests:

RFC9946-11-L2

Tested

Optionally, the server could utilize the maxBandwidth field (and the CHSR_USDIR_BIT bit) in the Setup Request from the client to limit the maximum that it will attempt to achieve.

Note: maxBandwidth field (Section 6.1).

Conformance Records: search-capped-at-stated-max-bandwidth.

Proving tests: