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

[Megan Ferguson <[e-mail]>]

Spencer, 

This erratum is awaiting your review; we understand that it potentially has an effect on an IANA registry. 
(IANA is CC'ed for awareness; our understanding is that no change will be made unless you change it to “Verified".)

Bob - Thanks for this note.  We have updated the nit you mentioned. 

RFC Editor/mf

On Nov 12, 2018, at 12:20 AM, Bob Briscoe <[e-mail]> wrote:

> Megan, David,
> 
> Completion of the process for this erratum seems to have stalled.
> 
> I just followed the link to this erratum from the tools page for RFC8311. Its status is still only 'Reported'.
> 
> The referenced IANA page for the ECN codepoints doesn't display the text requested by the erratum (probably unsurprising, given the erratum is not approved yet).
> 
> 
> A nitty comments about the erratum itself:
>     There's an extraneous ')' in the proposed replacement text before the '>' at the end of the URL.
> 
> 
> Bob
> 
> 
> 
> On 26/06/2018 18:03, Megan Ferguson wrote:
>> David,
>> 
>> Thanks for the reply.  This has been updated.
>> 
>> RFC Editor/mf
>> 
>> On Jun 26, 2018, at 8:42 AM, Black, David 
>> <[e-mail]>
>>  wrote:
>> 
>> 
>>> That's ok, given that this errata does result in a modification to an IANA registry.
>>> 
>>> Thanks, --David
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Megan Ferguson [
>>>> mailto:[e-mail]
>>>> ]
>>>> Sent: Tuesday, June 26, 2018 1:23 AM
>>>> To: Black, David; Black, David; Spencer Dawkins at IETF; Mirja Kuehlewind
>>>> (IETF); Gorry Fairhust; Wesley Eddy
>>>> Cc: RFC System; 
>>>> [e-mail]
>>>> 
>>>> Subject: Re: [Editorial Errata Reported] RFC8311 (5399)
>>>> 
>>>> 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
>>>>> 
>>>>> 
>> 
> 
> -- 
> ________________________________________________________________
> Bob Briscoe                               
> http://bobbriscoe.net/