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 §9: Reporting Formats

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

StateRequirements
Tested9
Deviation6

RFC9097-9-1

Tested

The Singleton IP-Layer Capacity results SHOULD be accompanied by the context under which they were measured. * Timestamp (especially the time when the maximum was observed in dtn). * Source and Destination (by IP or other meaningful ID). * Other inner Parameters of the test case (Section 4). * Outer Parameters, such as “test conducted in motion” or other factors belonging to the context of the measurement. * Result validity (indicating cases where the process was somehow interrupted or the attempt failed). * A field where unusual circumstances could be documented, and another one for “ignore / mask out” purposes in further processing.

Proving tests:

RFC9097-9-2

Deviation

The Maximum IP-Layer Capacity results SHOULD be reported in tabular format.

Recorded in compact-human-final-metrics.

Proving tests:

RFC9097-9-3

Deviation

There SHOULD be a column that identifies the test Phase.

Note: Maximum IP-Layer Capacity table.

Recorded in compact-human-final-metrics.

Conformance Records: results-name-the-phase-and-f.

Proving tests:

RFC9097-9-4

Deviation

There SHOULD be a column listing the number of flows used in that Phase.

Recorded in compact-human-final-metrics.

Conformance Records: results-name-the-phase-and-f.

Proving tests:

RFC9097-9-5

Deviation

The remaining columns SHOULD report the following results for the aggregate of all flows, including the Maximum IP-Layer Capacity, the Loss Ratio, the RTT minimum, RTT maximum, and other metrics tested having similar relevance.

Recorded in compact-human-final-metrics.

Proving tests:

RFC9097-9-6

Tested

As mentioned in Section 6.6, bimodal (or multi-modal) maxima SHALL be reported for each mode separately.

Note: Capacity Modes; restates RFC9097-6.6-3.

Proving tests:

RFC9097-9-7

Tested

The sub-interval time, dt, MUST accompany a report of Maximum IP- Layer Capacity results, as well as the remaining Parameters from Section 4 (“General Parameters and Definitions”).

Proving tests:

RFC9097-9-8

Tested

The PM list metrics corresponding to the sub-interval where the Maximum Capacity occurred MUST accompany a report of Maximum IP-Layer Capacity results, for each test Phase.

Proving tests:

RFC9097-9-9

Tested

The IP-Layer Sender Bit Rate results SHOULD be reported in tabular format.

Proving tests:

RFC9097-9-10

Tested

There SHOULD be a column that identifies the test Phase.

Note: The table of IP-Layer Sender Bit Rates.

Conformance Records: results-name-the-phase-and-f.

Proving tests:

RFC9097-9-11

Deviation

There SHOULD be a column listing each individual (numbered) flow used in that Phase, or the aggregate of flows in that Phase.

Recorded in sender-bit-rate-per-sub-interval.

RFC9097-9-12

Deviation

A corresponding column SHOULD identify the specific sending rate sub- interval, stn, for each flow and aggregate.

Recorded in sender-bit-rate-per-sub-interval.

RFC9097-9-13

Tested

A final column SHOULD report the IP-Layer Sender Bit Rate results for each flow used, or the aggregate of all flows.

Proving tests:

RFC9097-9-14

Tested

The sub-interval duration, st, MUST accompany a report of Sender IP- Layer Bit Rate results.

Proving tests:

RFC9097-9-15

Tested

Also, the values of the remaining Parameters from Section 4 (“General Parameters and Definitions”) MUST be reported.

Proving tests: