Hi, This seems reasonable. I'm not even sure it needs to be a BCP, since as far as I can see it doesn't introduce any new process rules. I'm also not sure it should be treated as mandatory, because each case is special. However... It doesn't help to clarify what the "Updates:" tag means (it only mentions "Obsoletes:") and it doesn't discuss how protocol extensions should be labelled. Should they carry the "Updates:" tag? Or should we ask the RFC Editor for a new "Extends:" tag, and "Extended by:"? Regards Brian On 08-May-19 12:18, internet-drafts@xxxxxxxx wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title : Process for Handling Non-Major Revisions to Existing RFCs > Author : Adam Roach > Filename : draft-roach-bis-documents-00.txt > Pages : 8 > Date : 2019-05-07 > > Abstract: > This document discusses mechanisms the IETF has historically used for > updating RFCs subsequent to their publication, and outlines an > updated procedure for publishing newer versions (colloquially known > as "bis versions") that is appropriate in certain circumstances. > This procedure is expected to be easier for both authors and > consumers of RFCs. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-roach-bis-documents/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-roach-bis-documents-00 > https://datatracker.ietf.org/doc/html/draft-roach-bis-documents-00 > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@xxxxxxxx > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt >
