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 §2: Scope, Goals, and Applicability

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

StateRequirements
Tested3
Operational3

RFC9097-2-1

Operational

It is RECOMMENDED to discontinue non-measurement traffic that shares a subscriber’s dedicated resources while testing: measurements may not be accurate, and throughput of competing elastic traffic may be greatly reduced.

Note: Advice to the user running a Test.

RFC9097-2-2

Operational

It MUST only be used in the application of diagnostic and operations measurements as described in this memo.

Note: “It” is the Load Rate Adjustment Algorithm; RFC 9946 section 5.1 item 2 says the same.

RFC9097-2-3

Operational

It MUST only be used in circumstances consistent with Section 10 (“Security Considerations”).

Note: RFC 9946 section 5.1 item 11 says the same.

RFC9097-2-4

Tested

If a network operator is certain of the IP-Layer Capacity to be validated, then testing MAY start with a fixed-rate test at the IP-Layer Capacity and avoid activating the load adjustment algorithm.

Note: Fixed-Rate Test, Operator Key only; RFC 9946 section 5.1 item 10.

Proving tests:

RFC9097-2-5

Tested

However, the stimulus for a diagnostic test (such as a subscriber request) strongly implies that there is no certainty, and the load adjustment algorithm is RECOMMENDED.

Note: A Search Test is the default.

Proving tests:

RFC9097-2-6

Tested

Finally, the measurement system’s load rate adjustment algorithm SHALL NOT be provided with the exact capacity value to be validated a priori.

Note: A Search Test starts at the default row or a requested srIndexConf row, never at a known capacity.

Proving tests: