Re: [tsvwg] [Editorial Errata Reported] RFC8311 (5399)

[Megan Ferguson <[e-mail]>]

Greetings,

We suggest updating the Type of this errata report from “Editorial” to “Technical”.

Please see https://www.rfc-editor.org/errata-definitions/ for further information.

If this update is agreeable, we would be happy to edit the report.

Thank you.

RFC Editor/mf


On Jun 19, 2018, at 2:37 PM, RFC Errata System <[e-mail]> wrote:

> The following errata report has been submitted for RFC8311,
> "Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5399
> 
> --------------------------------------
> Type: Editorial
> Reported by: David Black <[e-mail]>
> 
> Section: 7
> 
> Original Text
> -------------
> (n/a, this errata adds an additional IANA Consideration)
> 
> Corrected Text
> --------------
> To reflect the experimental use of ECT(1) envisioned by this memo,
> IANA has added the following footnote to the ECN Field registry
> <https://www.iana.org/assignments/dscp-registry/
> dscp-registry.xhtml#ecn-field)>:
> 
> ECT(1) is for experimental use only [RFC8311, Section 4.2]
> 
> 
> Notes
> -----
> The Corrected Text is written as if IANA has already added the footnote, which will be done upon approval of this errata, citing this approved errata as justification.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC8311 (draft-ietf-tsvwg-ecn-experimentation-08)
> --------------------------------------
> Title               : Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation
> Publication Date    : January 2018
> Author(s)           : D. Black
> Category            : PROPOSED STANDARD
> Source              : Transport Area Working Group
> Area                : Transport
> Stream              : IETF
> Verifying Party     : IESG
>