[rfc-i] Feedback solicited: Update tags draft
cabo at tzi.org (Carsten Bormann) Sat, 29 February 2020 14:27 UTC
From: "cabo at tzi.org"
Date: Sat, 29 Feb 2020 15:27:55 +0100
Subject: [rfc-i] Feedback solicited: Update tags draft
In-Reply-To: <CABcZeBP5M2feGVT5e+NhP_UtUaRxJMd_PxuEDTSmrWGr2PjtTg@mail.gmail.com>
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>
Message-ID: <BB6B7103-0A99-43E5-A423-82658CD08327@tzi.org>
>> 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
- [rfc-i] Feedback solicited: Update tags draft Suresh Krishnan
- [rfc-i] Feedback solicited: Update tags draft Suresh Krishnan
- [rfc-i] Feedback solicited: Update tags draft Stephen Farrell
- [rfc-i] Feedback solicited: Update tags draft Paul Kyzivat
- [rfc-i] Feedback solicited: Update tags draft Julian Reschke
- [rfc-i] Feedback solicited: Update tags draft Robert Sparks
- [rfc-i] Feedback solicited: Update tags draft Stephen Farrell
- [rfc-i] Feedback solicited: Update tags draft Mirja Kuehlewind
- [rfc-i] Feedback solicited: Update tags draft Mirja Kuehlewind
- [rfc-i] Feedback solicited: Update tags draft Eric Rescorla
- [rfc-i] Feedback solicited: Update tags draft Donald Eastlake
- [rfc-i] Feedback solicited: Update tags draft Suresh Krishnan
- [rfc-i] Feedback solicited: Update tags draft Suresh Krishnan
- [rfc-i] Feedback solicited: Update tags draft Eric Rescorla
- [rfc-i] Feedback solicited: Update tags draft Carsten Bormann
- [rfc-i] Feedback solicited: Update tags draft Eric Rescorla
- [rfc-i] Feedback solicited: Update tags draft Ekkarat Wareesing
- [rfc-i] Feedback solicited: Update tags draft Carsten Bormann
- [rfc-i] Feedback solicited: Update tags draft Eric Rescorla
- Re: [rfc-i] Feedback solicited: Update tags draft Mirja Kuehlewind
- Re: [rfc-i] Feedback solicited: Update tags draft Mirja Kuehlewind
- Re: [rfc-i] Feedback solicited: Update tags draft Eric Rescorla