Re: [Edm] [arch-d] Call for Comment: <draft-iab-use-it-or-lose-it-02> (Long-term Viability of Protocol Extension Mechanisms)

I find the ending of the introcution:

    It is possible
    that these conclusions are less applicable to protocol deployments
    that have less scale and diversity, or operate under different
    constraints.

to seriously understate the limitations of this work.  The most 
important different cases I can see are the extremely widely deployed 
protocols at the Internet and Routing layers.  These protocols share the 
problems that are identified.  But the proposed approaches to improving 
the situation are likely to be problematic at best.  I think a much 
stronger disclaimer is needed.

Yours,
Joel

On 8/25/2021 2:43 PM, IAB Executive Administrative Manager wrote:
> This is an announcement of an IETF-wide Call for Comment on
> draft-iab-use-it-or-lose-it-02.
> 
> 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-iab-use-it-or-lose-it/>
> 
> The Call for Comment will last until 2021-09-22. Please send comments to
> architecture-discuss@ietf.org and iab@iab.org.
> 
> Abstract:
> 
>     The ability to change protocols depends on exercising the extension
>     and version negotiation mechanisms that support change.  This
>     document explores how regular use of new protocol features can ensure
>     that it remains possible to deploy changes to a protocol.  Examples
>     are given where lack of use caused changes to be more difficult or
>     costly.
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
> 