Simon,
How about a "IETF48" review period? The to-be-published RFC is published again as a new I-D and the entire community can do final review of the changes introduced during the RFC editing process.
I fear that might turn the current 48 day review period into a 48 week review period :-)
In any case, the data about what drafts are in AUTH48 is public, and the URLs for the to-be-RFCs are guessable... there are a few people outside the authors who seem to be checking some drafts this way. I wouldn't mind if the latest version from the RFC editor was more conveniently accessible.
In short, I think having easier access to the drafts in their various states would always be welcome. And input would very much be appreciated if something is broken. But I don't think we need more formal periods or process after the draft has been approved. We already now have the RFC Editor, the authors, the chairs, and the ADs checking each change and attempting to catch mistakes and flag non-editorial changes. I know there are cases where these checks have failed, but in general, if we have more review power in the IETF community I think I would probably put it to work in earlier phases for bigger bang for the buck.
Jari _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf