Erik Kline has entered the following ballot position for draft-ietf-lisp-geo-14: No Objection
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 https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-lisp-geo/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Internet AD comments for draft-ietf-lisp-geo-14 CC @ekline * comment syntax: - https://github.com/mnot/ietf-comments/blob/main/format.md * "Handling Ballot Positions": - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/ ## Comments ### S3, S4.2 * Given that a Geo-Point includes an altitude, wouldn't a Geo-Point and a radius describe a sphere and not a circle? Should the altitude be ignored for "Geo-Point ∈ Geo-Prefix" evaluations? ### S4.2 * I don't quite follow the "longest prefix" analogy here. I would have expected "longest prefix" implies "greater specificity" ergo "smaller radius" rather than larger? Undoubtedly there's some LISP context here I'm lacking. RFC 9301 seems to talk about returning more specific when there are multiple overlapping prefixes. But again: I'm sure I must be missing something (well, many things, but... :-) ). ### S5 * You cite S2 the WGS84 as the source definition for a Geo-Point (Geo-Coordinate) but declare here the Altitude vertical datum is MSL. I think MSL is fine, and probably more intuitive, but AIUI it's not the same as the WGS84 geodetic height above the reference ellipsoid. Perhaps just note the specific change in the terminology summary in S2? _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
