David Harrington has entered the following ballot position for draft-ietf-
geopriv-rfc3825bis-14.
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.
----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------
This document is well-written, with clear and unambiguous language.
When aType=2, numbering starts at ground level. How does one represent an
underground parking garage level?
Should 2.4.3 mention how to represent this? Should Appendix B include such
an example?
----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------
1) section 1, paragraph 4 says "The DHCP server could correlate the
Circuit-ID with the geographic location where the
identified circuit terminates (such as the location of the wall jack)."
Would it be the job of the DHCP server to do this correlation? I would
assume it was a NM application function to do such correlation.
2) In 2.2.1.2, s/same response. This is not useful since/same response,
since/
--
---------------------------------------+------------------------------------
Reporter: bernard_aboba@… | Owner: bernard_aboba@…
Type: defect | Status: new
Priority: major | Milestone: draft-ietf-geopriv-3825bis
Component: rfc3825bis | Version: 1.0
Severity: Submitted WG Document | Keywords:
---------------------------------------+------------------------------------
Ticket URL: <https://svn.tools.ietf.org/wg/geopriv/trac/ticket/41>
geopriv <http://tools.ietf.org/geopriv/>
_______________________________________________
Geopriv mailing list
Geopriv@ietf.org
https://www.ietf.org/mailman/listinfo/geopriv
