On 19.12.2024 15:28, Eric Rescorla wrote:


    Your list omits enabling discussion of RFC text prior to reporting
    something as an erratum, so that we end up with better/fewer-but-real
    errata, and are nicer to readers and approvers than currently.


I would also add some mechanism for allowing people (either reporters
or authors) to supply specific changes which can then be mechanically
applied to the RFC, as well as a mechanism for refining those changes.

FWIW, I know that there are many WGs that don't use GitHub but
what we are talking about here really is very much like GitHub issues
and pull requests. Rather than trying to reinvent everything from some
set of relatively broad principles, it seems like the IETF should instead
try to imitate mechanisms we know work, even if we can't directly
adopt them.

Ok, so what needs to be in this draft, versus left to implementation?

Eliot

Attachment: OpenPGP_0x87B66B46D9D27A33.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
rswg mailing list -- rswg@rfc-editor.org
To unsubscribe send an email to rswg-le...@rfc-editor.org

Reply via email to