[rfc-i] Feedback solicited: Update tags draft

ekr at rtfm.com (Eric Rescorla) Sat, 29 February 2020 14:29 UTC

From: ekr at rtfm.com (Eric Rescorla)
Date: Sat, 29 Feb 2020 06:29:24 -0800
Subject: [rfc-i] Feedback solicited: Update tags draft
In-Reply-To: <BB6B7103-0A99-43E5-A423-82658CD08327@tzi.org>
References: <447718E1-D2EF-41B1-94DD-AB121EAA79BB@gmail.com> <179BB23D-825A-4177-B656-1B396903C7D8@gmail.com> <CABcZeBODoQTd+fdgqpLwXWhE5P35gTN5S-3zN5+_+7Mcb4PbzQ@mail.gmail.com> <AB0B3305-FCEC-48E6-A916-B86245CD1C3E@gmail.com> <CABcZeBMCZfSxTXUj0+Kuy2QJi+vJHcPpWjydobTD4ztuzTR2rQ@mail.gmail.com> <49F70083-5388-49CA-8A5D-54324C04538C@tzi.org> <CABcZeBP5M2feGVT5e+NhP_UtUaRxJMd_PxuEDTSmrWGr2PjtTg@mail.gmail.com> <BB6B7103-0A99-43E5-A423-82658CD08327@tzi.org>
Message-ID: <CABcZeBPvisrWZNPd8zhw5XQMEh=sxiqVN0=V1B1eQmxfzwGJ=w@mail.gmail.com>

My initial comment about the first rule of holes seems to apply doubly to
this idea


On Sat, Feb 29, 2020 at 6:27 AM Carsten Bormann <cabo at tzi.org> wrote:

> >> We would need boilerplate in each RFC that includes potential future
> amendments.
> >
> > I don't understand how that would work, and it's hard to see how you
> could reason about it.
> RFCs are textually immutable.  We solve the problem by adding references
> to mutable information the RFC, e.g. to IANA registries: this keeps the
> text immutable, but allows us to add to the content later.
> Obviously, a claim to conformance to any RFC could not include future
> values from that registry.
> By adding to each RFC a reference to (a ?registry?, except that it would
> not be an IANA registry) of documents that must be read with the that
> document, we could extend this mechanism to other changes.  We would need
> to make it explicit that any claim to conformance would need to include a
> date, and would imply adding amendments published at that date to the
> document conformance to which is claimed to.
> (I?m not advocating this, I?m just saying how this could be done.
> Disadvantage: Can not be done with RFCs published before this change.)
> Gr??e, Carsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20200229/7daad961/attachment.html>