Re: [arch-d] Call for Comment: <draft-ietf-iasa2-rfc6220bis-03> (Defining the Role and Function of IETF Protocol Parameter Registry Operators)

[Bob Hinden <[e-mail]>]

Hi,

Overall this looks good.   Here is a link to a diff between the RFC and current draft:

https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=https://tools.ietf.org/rfc/rfc6220.txt&url2=https://tools.ietf.org/id/draft-ietf-iasa2-rfc6220bis-03.txt

A few comments:

This draft says it obsoletes RFC6220, but that is not mentioned in the abstract or in the Introduction.  It should be.  This was called out in Idnits.  Idnits also mentions some old references.

After the abstract there is a [Cover Note]:

   [The IASA2 WG asks the IAB to publish this replacement for RFC 6220.
    This document is changed for alignment with the new structure for the
    IETF Administrative Support Activity (IASA). ]

Later in the document it asks the RFC Editor to remove this.

I think the Abstract needs to include text that says this draft makes changes relating to the IASA 2.0 model.  For example something like this:

   This document obsoletes RFC 6220 to replace all references to the IASA and
   related structures with those defined by the IASA 2.0 Model.

The something similar in the Introduction.  This was done in the other IASA 2.0 bis documents.

Thanks
Bob




> On Aug 21, 2019, at 11:19 AM, IAB Executive Administrative Manager <[e-mail]> wrote:
> 
> This is an announcement of an IETF-wide Call for Comment on
> draft-ietf-iasa2-rfc6220bis-03.
> 
> The document is being considered for publication as an Informational RFC
> within the IAB stream, and is available for inspection at:
> <https://datatracker.ietf.org/doc/draft-ietf-iasa2-rfc6220bis/>
> 
> The Call for Comment will last until 2019-09-18. Please send comments to
> [e-mail] and [e-mail].
> 
> Abstract
> 
>   Many Internet Engineering Task Force (IETF) protocols make use of
>   commonly defined values that are passed in messages or packets.  To
>   ensure consistent interpretation of these values between independent
>   implementations, there is a need to ensure that the values and
>   associated semantic intent are uniquely defined.  The IETF uses
>   registry functions to record assigned protocol parameter values and
>   their associated semantic intentions.  For each IETF protocol
>   parameter, it is current practice for the IETF to delegate the role
>   of Protocol Parameter Registry Operator to a nominated entity.  This
>   document provides a description of, and the requirements for, these
>   delegated functions.
> 
> [Cover Note]
> 
>   [The IASA2 WG asks the IAB to publish this replacement for RFC 6220.
>   This document is changed for alignment with the new structure for the
>   IETF Administrative Support Activity (IASA). ]
> 
> _______________________________________________
> IETF-Announce mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ietf-announce