Last Call Review of draft-leiba-urnbis-ietf-namespace-01
review-leiba-urnbis-ietf-namespace-01-secdir-lc-orman-2013-02-14-00
Request | Review of | draft-leiba-urnbis-ietf-namespace |
---|---|---|
Requested revision | No specific revision (document currently at 02) | |
Type | IETF Last Call Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2013-02-11 | |
Requested | 2013-01-17 | |
Authors | Barry Leiba | |
I-D last updated | 2015-10-14 (Latest revision 2013-02-14) | |
Completed reviews |
Genart IETF Last Call review of -01
by Joel M. Halpern
(diff)
Genart Telechat review of -02 by Joel M. Halpern Secdir IETF Last Call review of -01 by Hilarie Orman (diff) |
|
Assignment | Reviewer | Hilarie Orman |
State | Completed | |
Request | IETF Last Call review on draft-leiba-urnbis-ietf-namespace by Security Area Directorate Assigned | |
Reviewed revision | 01 (document currently at 02) | |
Result | Ready | |
Completed | 2013-02-14 |
review-leiba-urnbis-ietf-namespace-01-secdir-lc-orman-2013-02-14-00
Secdir review of Registration of Second-Level URI Namespaces Under "ietf" draft-leiba-urnbis-ietf-namespace-01 Do not be alarmed. I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. From the Abstract: RFC 2648 defines the "ietf" URN namespace, and defines a number of sub-namespaces. RFC 3553 defines an additional sub-namespace, "params", and creates a registry to document allocations under that. But there is no registry that lists, in one place, all sub-namespaces of "ietf". This document creates and populates such a registry. I agree with the author's assessment that there are no security ramifications. Hilarie