Re: [arch-d] I-D Action: draft-iab-protocol-maintenance-12.txt

Dear Joe,

For clarification: This is an IAB document, providing guidance from the IAB. This text was added to the IAB approval section and talks about “broad […] approval within the IAB”. Effectively this text was specifically added to reflect that there were concern in the community.

Mirja

> On 2. Feb 2023, at 06:34, Joe Touch <touch@strayalpha.com> wrote:
> 
> And while we’re at it:
> 
> broad … approval != valid
> 
> At best, it could be claimed that the guidance might be “popular”.
> 
> Joe
> 
>> On Feb 1, 2023, at 9:13 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
>> 
>> 
>> I find the sentence "The document had broad but not unanimous approval within the IAB, reflecting that while the guidance is valid, concerns were expressed in the IETF community about how broadly it applies in all situations" to be somewhat odd.  Given that the document is an IAB statement and not an IETF consensus statement, it should not be making comments about the community view of the document.   I suspect that the statement is intended to imply something about the degree of IAB support for publication, but whatever it is intended to accomplish, I don't think it works.
>> 
>> Yours,
>> 
>> Joel
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On 2/1/2023 7:58 PM, internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>> This draft is a work item of the Internet Architecture Board IETF of the IETF.
>>> 
>>>         Title           : Maintaining Robust Protocols
>>>         Authors         : Martin Thomson
>>>                           David Schinazi
>>>   Filename        : draft-iab-protocol-maintenance-12.txt
>>>   Pages           : 17
>>>   Date            : 2023-02-01
>>> 
>>> Abstract:
>>>    The main goal of the networking standards process is to enable the
>>>    long term interoperability of protocols.  This document describes
>>>    active protocol maintenance, a means to accomplish that goal.  By
>>>    evolving specifications and implementations, it is possible to reduce
>>>    ambiguity over time and create a healthy ecosystem.
>>> 
>>>    The robustness principle, often phrased as "be conservative in what
>>>    you send, and liberal in what you accept", has long guided the design
>>>    and implementation of Internet protocols.  However, it has been
>>>    interpreted in a variety of ways.  While some interpretations help
>>>    ensure the health of the Internet, others can negatively affect
>>>    interoperability over time.  When a protocol is actively maintained,
>>>    protocol designers and implementers can avoid these pitfalls.
>>> 
>>> 
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-iab-protocol-maintenance/
>>> 
>>> There is also an HTML version available at:
>>> https://www.ietf.org/archive/id/draft-iab-protocol-maintenance-12.html
>>> 
>>> A diff from the previous version is available at:
>>> https://author-tools.ietf.org/iddiff?url2=draft-iab-protocol-maintenance-12
>>> 
>>> 
>>> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
>>> 
>>> 
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>> _______________________________________________
>> Architecture-discuss mailing list
>> Architecture-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/architecture-discuss
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss