Telechat Review of draft-ietf-geopriv-dhcp-lbyr-uri-option-17
review-ietf-geopriv-dhcp-lbyr-uri-option-17-genart-telechat-melnikov-2013-02-07-00
| Request | Review of | draft-ietf-geopriv-dhcp-lbyr-uri-option |
|---|---|---|
| Requested revision | No specific revision (document currently at 19) | |
| Type | Telechat Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2013-02-05 | |
| Requested | 2013-01-31 | |
| Authors | James Polk | |
| I-D last updated | 2015-10-14 (Latest revision 2013-02-24) | |
| Completed reviews |
Genart IETF Last Call review of -??
by Alexey Melnikov
Genart Telechat review of -17 by Alexey Melnikov (diff) Secdir Early review of -?? by Chris M. Lonvick Secdir Telechat review of -17 by Chris M. Lonvick (diff) |
|
| Assignment | Reviewer | Alexey Melnikov |
| State | Completed | |
| Request | Telechat review on draft-ietf-geopriv-dhcp-lbyr-uri-option by General Area Review Team (Gen-ART) Assigned | |
| Reviewed revision | 17 (document currently at 19) | |
| Result | Ready w/issues | |
| Completed | 2013-02-07 |
review-ietf-geopriv-dhcp-lbyr-uri-option-17-genart-telechat-melnikov-2013-02-07-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-ietf-geopriv-dhcp-lbyr-uri-option-18 Reviewer: Alexey Melnikov Review Date: 2013-02-07 IETF LC End Date: 2013-02-07 IESG Telechat date: (if known) Summary: This document is nearly ready for publication as a Proposed Standard. Major issues: None Minor issues: In Section 1: the first reference to URI needs a Normative reference. The whole document is about passing URIs and they are not defined anywhere. In Section 3.2: "data:" URI needs an Informative reference (RFC 2397). In the same section I see: o Section 3.3 IANA registers acceptable location URI schemes (or types) for use by this specification. Clients MUST reject URI schemes not currently registered in IANA. The last sentence looks wrong. Firstly, you already restrict the list of acceptable URIs to the list specified in Section 3.3. Secondly, what does this requirement mean exactly? Is the client required to fetch the list of registered URIs from iana.org (I hope not)? I suggest just deleting the last sentence. In Section 3.3: all media types mentioned (two?) need Normative references.