Last Call Review of draft-eastlake-rfc6931bis-xmlsec-uris-19
review-eastlake-rfc6931bis-xmlsec-uris-19-opsdir-lc-morton-2021-11-23-00
Request | Review of | draft-eastlake-rfc6931bis-xmlsec-uris |
---|---|---|
Requested revision | No specific revision (document currently at 27) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2021-12-15 | |
Requested | 2021-11-17 | |
Authors | Donald E. Eastlake 3rd | |
I-D last updated | 2021-11-23 | |
Completed reviews |
Genart Last Call review of -19
by Peter E. Yee
(diff)
Secdir Last Call review of -19 by Rifaat Shekh-Yusef (diff) Opsdir Last Call review of -19 by Al Morton (diff) |
|
Assignment | Reviewer | Al Morton |
State | Completed | |
Request | Last Call review on draft-eastlake-rfc6931bis-xmlsec-uris by Ops Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/ops-dir/zlAH3kksP6CXAlvlwaYyZYnvxWE | |
Reviewed revision | 19 (document currently at 27) | |
Result | Ready | |
Completed | 2021-11-23 |
review-eastlake-rfc6931bis-xmlsec-uris-19-opsdir-lc-morton-2021-11-23-00
Thanks to Don for taking-up this extensive update. Accurate information in the IANA "XML Security URIs" Registry can only have a positive operational impact. The abstract indicates that document also updates, corrects three errata against, and obsoletes RFC 6931. I scanned the doc, and the diffs: https://www.ietf.org/rfcdiff?url1=rfc6931&url2=draft-eastlake-rfc6931bis-xmlsec-uris-19 appear to do exactly that. The updates have been prepared over 7 years - and it seems that the doc is ready to go.