Last Call Review of draft-iab-rfcefdp-rfced-model-11
review-iab-rfcefdp-rfced-model-11-opsdir-lc-romascanu-2022-02-22-00
| Request | Review of | draft-iab-rfcefdp-rfced-model |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | IETF Last Call Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2022-02-25 | |
| Requested | 2022-02-09 | |
| Requested by | Mirja Kühlewind | |
| Authors | Peter Saint-Andre | |
| I-D last updated | 2022-06-30 (Latest revision 2022-03-17) | |
| Completed reviews |
Rtgdir IETF Last Call review of -11
by Stig Venaas
(diff)
Secdir IETF Last Call review of -11 by Russ Mundy (diff) Genart IETF Last Call review of -11 by Christer Holmberg (diff) Intdir IETF Last Call review of -11 by Sheng Jiang (diff) Opsdir IETF Last Call review of -11 by Dan Romascanu (diff) Tsvart IETF Last Call review of -11 by Wesley Eddy (diff) Artart IETF Last Call review of -11 by Thomas Fossati (diff) I18ndir IETF Last Call review of -11 by Martin J. Dürst (diff) |
|
| Comments |
We're aiming to maximize the reviews for all documents associated with the change in the RFC Editor model. This document is the main deliverable from the RFC future editor model program and describes the new RFC editor model. The more eyes we get on this, the better! |
|
| Assignment | Reviewer | Dan Romascanu |
| State | Completed | |
| Request | IETF Last Call review on draft-iab-rfcefdp-rfced-model by Ops Directorate Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/y31onn8OQQ1W0LYtc8D3VFsDLIg | |
| Reviewed revision | 11 (document currently at 13) | |
| Result | Ready | |
| Completed | 2022-02-22 |
review-iab-rfcefdp-rfced-model-11-opsdir-lc-romascanu-2022-02-22-00
This Informational document specifies version 3 of the RFC Editor Model. The document does not define or extend any Internet related protocol. There are no implications related to the operation or management of the Internet. It would be useful for the operators to be aware about some of the aspects described in this document and in the related documents, especially in what concerns understanding the status of the RFCs (e.g. which RFC documents represent Internet Standards). I do not see any problem with the publication of this document from the OPS-DIR perspective.