Last Call Review of draft-leiba-cotton-iana-5226bis-08
review-leiba-cotton-iana-5226bis-08-genart-lc-even-2014-10-23-00
| Request | Review of | draft-leiba-cotton-iana-5226bis |
|---|---|---|
| Requested revision | No specific revision (document currently at 20) | |
| Type | IETF Last Call Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2014-10-30 | |
| Requested | 2014-10-02 | |
| Authors | Michelle Cotton , Barry Leiba , Dr. Thomas Narten | |
| I-D last updated | 2019-07-05 (Latest revision 2017-02-09) | |
| Completed reviews |
Genart IETF Last Call review of -08
by Roni Even
(diff)
Secdir IETF Last Call review of -08 by Donald E. Eastlake 3rd (diff) Secdir Telechat review of -11 by Donald E. Eastlake 3rd (diff) |
|
| Assignment | Reviewer | Roni Even |
| State | Completed | |
| Request | IETF Last Call review on draft-leiba-cotton-iana-5226bis by General Area Review Team (Gen-ART) Assigned | |
| Reviewed revision | 08 (document currently at 20) | |
| Result | Ready w/issues | |
| Completed | 2014-10-23 |
review-leiba-cotton-iana-5226bis-08-genart-lc-even-2014-10-23-00
I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>. Please resolve these comments along with any other Last Call comments you may receive. Document: draft-leiba-cotton-iana-5226bis-08 Reviewer: Roni Even Review Date:2014–10-23 IETF LC End Date: 2014–10-30 IESG Telechat date: Summary: This draft is ready for publication as a BCP RFC . Major issues: Minor issues: Section 2.3 discusses the issue of defining appropriate registration policy. I was wondering about consistency between the policies of similar registries, is it important and how to verify it. For example the policy for http://www.iana.org/assignments/sdp-security-descriptions/sdp-security-descriptions.xhtml#sdp-security-descriptions-3 is standard action and for http://www.iana.org/assignments/srtp-protection/srtp-protection.xhtml#srtp-protection-1 is specification required. I think that such cases should be discussed when defining the registration policy. Nits/editorial comments: In section 2.3 “judgement” should be “judgment”