RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (1)

RFC 8912, "Initial Performance Metrics Registry Entries", November 2021

Source of RFC: ippm (ops)

Errata ID: 6758
Status: Verified
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML

Reported By: Nikolai Malykh
Date Reported: 2021-11-28
Verifier Name: Martin Duke
Date Verified: 2021-12-01

Section 4.4.2 says:

   Percent_LossRatio:  The numeric value of the result is expressed in
      units of lost packets to total packets times 100%, as a positive
      value of type decimal64 with fraction digits = 9 (see Section 9.3
      of [RFC6020]) with a resolution of 0.0000000001.


It should say:

   Percent_LossRatio:  The numeric value of the result is expressed in
      units of lost packets to total packets times 100%, as a positive
      value of type decimal64 with fraction digits = 9 (see Section 9.3
      of [RFC6020]) with a resolution of 0.000000001.


Notes:

An extra 0 in the value of the resolution of the loss ratio.

The error is repeated in sections 7.4.2.6, 8.4.2.6, 9.4.2.4

Status: Held for Document Update (1)

RFC 8912, "Initial Performance Metrics Registry Entries", November 2021

Source of RFC: ippm (ops)

Errata ID: 6755
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT, PDF, HTML

Reported By: Nikolai Malykh
Date Reported: 2021-11-27
Held for Document Update by: Martin Duke
Date Held: 2022-05-13

Section 5.3.5 says:

5.3.5.  Runtime Parameters and Data Format

   Src:  The IP address of the host in the Src Role (format
      ipv4-address-no-zone value for IPv4 or ipv6-address-no-zone value
      for IPv6; see Section 4 of [RFC6991]).

It should say:

5.3.5.  Runtime Parameters and Data Format

   Runtime Parameters are input factors that must be determined,
   configured into the measurement system, and reported with the results
   for the context to be complete.

   Src:  The IP address of the host in the Src Role (format
      ipv4-address-no-zone value for IPv4 or ipv6-address-no-zone value
      for IPv6; see Section 4 of [RFC6991]).

Notes:

Skipped paragraph.

=======
01/24/22: RFC Editor changed type to technical and asked the TSV ADs to review - nope this is editorial; this explanatory paragraph is in all the counterpart sections, but just missed here.

Status: Rejected (1)

RFC 8912, "Initial Performance Metrics Registry Entries", November 2021

Source of RFC: ippm (ops)

Errata ID: 6762
Status: Rejected
Type: Technical
Publication Format(s) : TEXT, PDF, HTML

Reported By: Nikolai Malykh
Date Reported: 2021-11-30
Rejected by: Martin Duke
Date Rejected: 2021-11-30

Section 10.1.4 says:

   RTLoss:  This metric assesses the estimated loss count for TCP
      packets constituting a single connection, exchanged between two
      hosts.  We consider the measurement of round-trip delay based on a
      single OP [RFC7011] somewhere in the network.  The output is the
      estimated loss count for the measurement interval.

It should say:

   RTLoss:  This metric assesses the estimated loss count for TCP
      packets constituting a single connection, exchanged between two
      hosts.  We consider the measurement of loss count based on a
      single OP [RFC7011] somewhere in the network.  The output is the
      estimated loss count for the measurement interval.

Notes:

This is where loss count is measured, not round-trip delay.
--VERIFIER NOTES--
From Al Morton: Sorry, but the original text is correct. In this case we have a RT loss *estimate* conducted in the context of (and using the same packets as) the RT Delay measurements described for TCP. We considered this text carefully before publication.

Report New Errata



Advanced Search