I had to IAAN request Type value 17 (and not 15 since RFC8060 had already spec'ed type values 15 and 16). And I wasn't sure if it was implied by Luigi's comments, but the name of this encoding needs to be different than the "Geo-Coordinates type 15" in RFC8060, so it is called "Geo-Location".
Dino > On Apr 30, 2024, at 12:11 PM, [email protected] wrote: > > Internet-Draft draft-ietf-lisp-geo-05.txt is now available. It is a work item > of the Locator/ID Separation Protocol (LISP) WG of the IETF. > > Title: LISP Geo-Coordinate Use-Cases > Author: Dino Farinacci > Name: draft-ietf-lisp-geo-05.txt > Pages: 15 > Dates: 2024-04-30 > > Abstract: > > This draft describes how Geo-Coordinates can be used in the LISP > Architecture and Protocols. Some use-cases can be geo-fencing and > physically locating objects. > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-lisp-geo/ > > There is also an HTMLized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-lisp-geo-05 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-geo-05 > > Internet-Drafts are also available by rsync at: > rsync.ietf.org::internet-drafts > > > _______________________________________________ > lisp mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lisp _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
