[Idr] [IANA #1183451] Protocol Action: 'Dissemination of Flow Specification Rules for IPv6' to Proposed Standard (draft-ietf-idr-flow-spec-v6-21.txt)

[Michelle Cotton via RT <[e-mail]>]

Hello,

The changes as requested in version 22 of the document have been completed.

We have capitalized "Flags" and "Length" for values 9 and 10 in the following registry:  https://www.iana.org/assignments/flow-spec

We removed the registration (0x0e) in the Generic Transitive Experimental Use Extended Community Sub-Types registry.

We have registered the following:

Transitive IPv6-Address-Specific Extended Community Types

0x000d	Flow spec rt-redirect-ipv6 format

See: https://www.iana.org/assignments/bgp-extended-communities

Please let us know if this document's revised actions have been completed correctly.

Thank you,

Michelle Cotton
Protocol Parameters Engagement Sr. Manager
IANA Services






On Mon Dec 14 09:58:27 2020, [e-mail] wrote:
> Hi Amanda,
> 
> CC also to IDR for reference.
> 
> Sorry for the delayed answers to your questions. During the review of
> the changes I noticed that the Action 2 requested a new codepoint from
> the Generic Extended Community registry but the document is clearly
> referencing a IPv6-Specific-Extended Community in sections 6., 6.1
> (the IANA section 8.2 was not aligned with the text above).
> 
> I updated and uploaded  a version -22 of the document to correct that
> defect. Alvaro reviewed the changes. I will also notify RFC-Editors
> about the changed document.
> 
> To answer your questions:
> 
> ACTION 1:
> 
> >> QUESTION: All words in the registry other than "flags" and "length"
> >> (at values 9 and 10) were capitalized by this document. We have no
> >> opinion, but should those words have been capitalized as well?
> 
> 
> Please capitalize those as well. The -22 document also addresses this
> nit.
> 
> ACTION 2:
> 
> Please revert the -21 changes and see the new -22 Section 8.2 for the
> correct registry that needs to be updated.
> 
> Sorry for that.
> 
> Cheers Christoph