[Edm] Please review draft-iab-use-it-or-lose-it-01

[Tommy Pauly <[e-mail]>]

Hello EDM,

We’ve posted a new version of the use-it-or-lose-it draft, which has been discussed in several of our past calls.

The IAB would like to get this document progressed to be published as an RFC between IETF 111 and IETF 112. Please take a look at the current version, and provide your reviews either here by email, or on the GitHub (https://github.com/intarchboard/draft-use-it-or-lose-it/issues <https://github.com/intarchboard/draft-use-it-or-lose-it/issues>).

Best,
Tommy

> On Jul 14, 2021, at 6:21 AM, [e-mail] wrote:
> 
> 
> A new version of I-D, draft-iab-use-it-or-lose-it-01.txt
> has been successfully submitted by Cindy Morgan and posted to the
> IETF repository.
> 
> Name:		draft-iab-use-it-or-lose-it
> Revision:	01
> Title:		Long-term Viability of Protocol Extension Mechanisms
> Document date:	2021-07-14
> Group:		iab
> Pages:		19
> URL:            https://www.ietf.org/archive/id/draft-iab-use-it-or-lose-it-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-iab-use-it-or-lose-it/
> Html:           https://www.ietf.org/archive/id/draft-iab-use-it-or-lose-it-01.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-iab-use-it-or-lose-it
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-iab-use-it-or-lose-it-01
> 
> Abstract:
>   The ability to change protocols depends on exercising the extension
>   and version negotiation mechanisms that support change.  Protocols
>   that don't use these mechanisms can find it difficult and costly to
>   deploy changes.
> 
> 
> 
> 
> The IETF Secretariat
> 
>