Hi!
I took a quick look and have some comments:
(1) The header should contain the "Updates: 8060" tag.
(2) The IANA Considerations section should explicitly request that LCAF
type 5 be deprecated so the registry can be updated.
(3) It seems to me that the title of the document ("LISP Geo-Coordinate
Use-Cases") can be misleading because its primary purpose is to define the
new encoding, not just describe use cases. "LISP Geo-Coordinates" or "Use
of Geo-Coordinates in LISP" may reflect the contents better.
Thanks!
Alvaro.
On February 12, 2025 at 4:15:45 AM, Luigi Iannone ([email protected]) wrote:
Dear WG
This message starts a two-week WG Last Call for draft-ietf-lisp-geo ending
on February 26th 2025.
https://datatracker.ietf.org/doc/draft-ietf-lisp-geo/
This document describes how Geo-Coordinates can be used in the LISP
Architecture and Protocols. The functionality proposes a new LISP
Canonical Address Format (LCAF) encoding for such Geo-Coordinates,
which is compatible with the Global Positioning Satellite (GPS)
encodings used by other routing protocols.
Please review this WG document and let the WG know if you agree that it is
ready to be handed over to the AD. If you have objections, please state your
reasons why, and explain what it would take to address your concerns.
Note: silence IS NOT consensus.
Thanks
Padma and Luigi
_______________________________________________
lisp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
lisp mailing list -- [email protected]
To unsubscribe send an email to [email protected]
