On Tue, Sep 1, 2020 at 8:58 AM Timothy Mcsweeney <tim@xxxxxxxxxxxxxx> wrote:
>While it's certainly possible to add such guidance now, this update is
>very narrowly targeted to fix a serious problem, and I would not want
>debate about additional text to get in the way of that.And doesn't using this draft as an update of the entire IANA considerations section effectively remove any means of registration through the mailing lists provided in that same section??
This draft doesn't replace the entire IANA Considerations section of RFC 3405, but rather amends it. That is, after this is published, to get the full IANA Considerations for BCP 65, you would read RFC 3405 and then apply this document as a sort of "patch". That's what we mean when we say "RFC Y updates RFC X", which will be the end result here.
The specific effect of this document when published is to amend Section 3.1.1 of RFC 3405 such that instead of saying "registered under the IETF URI tree", it becomes "a registered permanent URI scheme", and then take "tree" out of the next sentence, and rename the section to something more appropriate. This draft could spell out each of those edits precisely, or just replace all of Section 3.1.1 with a new set of text, but it's such a small change that what's here seems equivalent and unambiguous to me.
-MSK
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
