Last Call Review of draft-carpenter-rfced-iab-charter-08
review-carpenter-rfced-iab-charter-08-artart-lc-kyzivat-2022-03-29-00
| Request | Review of | draft-carpenter-rfced-iab-charter |
|---|---|---|
| Requested revision | No specific revision (document currently at 09) | |
| Type | IETF Last Call Review | |
| Team | ART Area Review Team (artart) | |
| Deadline | 2022-04-05 | |
| Requested | 2022-02-09 | |
| Requested by | Lars Eggert | |
| Authors | Brian E. Carpenter | |
| I-D last updated | 2022-06-30 (Latest revision 2022-04-01) | |
| Completed reviews |
Secdir IETF Last Call review of -05
by Yoav Nir
(diff)
Genart IETF Last Call review of -05 by Pete Resnick (diff) Intdir IETF Last Call review of -05 by Bob Halley (diff) Iotdir IETF Last Call review of -05 by Samita Chakrabarti (diff) Tsvart IETF Last Call review of -05 by Joerg Ott (diff) Artart IETF Last Call review of -08 by Paul Kyzivat (diff) I18ndir IETF Last Call review of -05 by Takahiro Nemoto (diff) |
|
| Comments |
We're trying to maximize the reviews for documents associated with the change in the RFC Editor model. Hence the request to review these pretty short documents, even though they may not need a review from a technical perspective. |
|
| Assignment | Reviewer | Paul Kyzivat |
| State | Completed | |
| Request | IETF Last Call review on draft-carpenter-rfced-iab-charter by ART Area Review Team Assigned | |
| Posted at | https://mailarchive.ietf.org/arch/msg/art/w8c6ThJ3wqShfjYbYPASaJg2W4k | |
| Reviewed revision | 08 (document currently at 09) | |
| Result | Ready | |
| Completed | 2022-03-29 |
review-carpenter-rfced-iab-charter-08-artart-lc-kyzivat-2022-03-29-00
I am the assigned Art-Art reviewer for this draft. The Art Area Review Team (Art-Art) reviews all Art Area IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. Document: draft-carpenter-rfced-iab-charter-08 Reviewer: Paul Kyzivat Review Date: 2022-03-29 IETF LC End Date: 2022-04-05 IESG Telechat date: ? Summary: This draft is ready for publication as a Best Current Practice RFC. Comment: The intended status of BCP gave some pause, but I trust this has been given due consideration by people better qualified to make that call.