Telechat Review of draft-ietf-regext-bundling-registration-11
review-ietf-regext-bundling-registration-11-secdir-telechat-housley-2019-10-10-00
Request | Review of | draft-ietf-regext-bundling-registration |
---|---|---|
Requested revision | No specific revision (document currently at 11) | |
Type | Telechat Review | |
Team | Security Area Directorate (secdir) | |
Deadline | 2019-10-15 | |
Requested | 2019-10-07 | |
Authors | Ning Kong , Jiankang Yao , Linlin Zhou , Wil Tan , Jiagui Xie | |
I-D last updated | 2019-10-10 | |
Completed reviews |
Secdir Last Call review of -09
by Russ Housley
(diff)
Genart Last Call review of -09 by Joel M. Halpern (diff) Secdir Telechat review of -11 by Russ Housley Genart Telechat review of -11 by Joel M. Halpern |
|
Assignment | Reviewer | Russ Housley |
State | Completed | |
Request | Telechat review on draft-ietf-regext-bundling-registration by Security Area Directorate Assigned | |
Posted at | https://mailarchive.ietf.org/arch/msg/secdir/3OHy4mmMBY-BpUoi_PBlmsxLW3U | |
Reviewed revision | 11 | |
Result | Has issues | |
Completed | 2019-10-10 |
review-ietf-regext-bundling-registration-11-secdir-telechat-housley-2019-10-10-00
I 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 authors, document editors, and WG chairs should treat these comments just like any other IETF Last Call comments. Document: draft-ietf-regext-bundling-registration-11 Reviewer: Russ Housley Review Date: 2019-10-10 IETF LC End Date: 2019-03-15 IESG Telechat date: 2019-10-17 Summary: Has Issues Major Concerns: The Abstract ans Section 1 say: "This is a non-standard proprietary extension." I understand that this is not a standards track document, so the "non-standard" part makes sense. However, what is the point of publishing a "proprietary" extension as an RFC. I would hope that interoperable implementations is the goal of publication. In Section 1, the use of "policy-wise" is unclear. Is this registration policy or something else? Minor Concerns: None. Nits: Section 1: s/label(LABEL)/label (LABEL)/ - s/(V-tld);/(V-tld)./ In addition, there are several places in the upper left corner of the title page: Internet Engineering Task Force