[Gendispatch] FW: New Version Notification for draft-kuehlewind-update-tag-04.txt

[Mirja Kuehlewind <[e-mail]>]

Hi all,

as promised we revived draft-kuehlewind-update-tag and submitted a new version yesterday. There are no substantial changes but there are some editorial changes and a bit more text in the security consideration section:

- One part is about the need to have the same "kind" of consensus for amendments as the original RFC had. This question came recently up for me in another context and I added some thoughts.

- I tried to reflect some of the discussion about risks of failure. I personally believe that the worst thing that can happens is that this change will not improve the situation but I don't think it will make it worse. Therefore I would like to see this published as BCP. However, if people would be more comfortable to run this as an experiment that would be doable as well and we can discuss the parameters of that (duration and criteria for success/failure). More input on that point is definitely welcome!

Also we will update you in the next days with data on the analysis Suresh did about the usage of the Updates tag so far. So if that is of interest for you, please stay tuned and wait for another mail from us!

Mirja and Suresh




On 12.07.21, 16:23, "[e-mail]" <[e-mail]> wrote:


    A new version of I-D, draft-kuehlewind-update-tag-04.txt
    has been successfully submitted by Mirja Kuehlewind and posted to the
    IETF repository.

    Name:		draft-kuehlewind-update-tag
    Revision:	04
    Title:		Definition of new tags for relations between RFCs
    Document date:	2021-07-12
    Group:		Individual Submission
    Pages:		9
    URL:            https://www.ietf.org/archive/id/draft-kuehlewind-update-tag-04.txt
    Status:         https://datatracker.ietf.org/doc/draft-kuehlewind-update-tag/
    Html:           https://www.ietf.org/archive/id/draft-kuehlewind-update-tag-04.html
    Htmlized:       https://datatracker.ietf.org/doc/html/draft-kuehlewind-update-tag
    Diff:           https://www.ietf.org/rfcdiff?url2=draft-kuehlewind-update-tag-04

    Abstract:
       An RFC can include a tag called "Updates" which can be used to link a
       new RFC to an existing RFC.  On publication of such an RFC, the
       existing RFC will include an additional metadata tag called "Updated
       by" which provides a link to the new RFC.  However, this tag pair is
       not well-defined and therefore it is currently used for multiple
       different purposes, which leads to confusion about the actual meaning
       of this tag and inconsistency in its use.

       This document recommends the discontinuation of the use of the
       updates/updated by tag pair, and instead proposes three new tag pairs
       that have well-defined meanings and use cases.




    The IETF Secretariat