Subject: [Iasa20] Consolidated Update Draft vs. Individual Drafts

From: "Livingood, Jason" <[email-masked]>
Date: Mon, 10 Dec 2018 17:00:10 +0000

As you have certainly noticed, we have gotten varying feedback over time from the WG, the RFC editor, and some in the broader IETF community about whether to update individual drafts, to have a consolidated update draft, or a mix of the two approaches – or even to file errata. It seems the clearest path forward now is to employ a mix of the two approaches, with the recent consolidated update draft (https://datatracker.ietf.org/doc/draft-ietf-iasa2-consolidated-upd/) addressing a great many of these. But that won’t work in all cases so we will still have some individual drafts, as the circumstances and extent of updates necessary dictate.

As noted in the header of draft-ietf-iasa2-consolidated-upd, it would:
Update – RFC 2028, RFC 2418, RFC 3005, RFC 3710, RFC 5377 (see separate email in a moment), RFC 6702, RFC 7500
Obsolete – RFC 3716, RFC 3929, RFC 4633

Since no one can ever be 100% certain this will be acceptable with the IESG, general IETF community, and RFC Editor, last week we asked that some individual documents that would have addressed RFCs above be updated to reflect the change in reference from the structure I-D to RFC4071-bis. Our thinking was that this was a hedge against any possibility that we had challenges with the consolidated draft, so that we had a backup document plan at the ready just in case.

We appreciate the work of those volunteer document editors that assisted with the documents now covered by the consolidated update! And should some or all of these later be found to need individual updates, we’ll be prepared and can react quickly.

Regards
Jason