RFC 9946 §10: Operational Considerations for the Measurement Method

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

RFC9946-10-1

Tested

The nominal duration of a measurement interval at the Destination, parameter testIntTime, MUST be constrained in a production network, since this is an active test method and it will likely cause congestion on the Src to Dst host path during a test.

Note: The Server bounds testIntTime; a Consumer’s Test Interval is at most 60 s.

Proving tests:

• crates/udpstp-core/tests/test_interval_limits.rs::an_ordinary_key_gets_at_most_60_s

RFC9946-10-2

Operational

It is RECOMMENDED to locate test endpoints as close to the intended measured link(s) as practical.

Note: Where the operator places Clients and Servers.

RFC9946-10-3

Operational

The testing operator MUST set a value for the MaxHops parameter, based on the expected path length.

Note: The operator sets it; udpstp provides the MaxHops setting (max_hops).

Proving tests:

• crates/udpstp-runtime/src/ip_options.rs::test_traffic_carries_df_and_max_hops

RFC9946-10-4

Deviation

The number of concurrent, independent tests of a path SHALL be limited to one.

Note: Tests per source; see also Section 4.2.

Recorded in tests-per-source-above-one.

Proving tests:

• crates/udpstp-core/tests/tests_per_source.rs::a_second_test_from_the_same_source_is_refused_at_setup

RFC9946-10-5

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: What the Consumer does while testing.