This update reflects Luigi's comments. The only outstanding issue I think we have is if RFC8060 should be updated (I think it should) to reflect the packet format changes.
Dino > Begin forwarded message: > > From: internet-dra...@ietf.org > Subject: [lisp] I-D Action: draft-ietf-lisp-geo-01.txt > Date: December 12, 2022 at 12:26:39 PM PST > To: <i-d-annou...@ietf.org> > Cc: lisp@ietf.org > Reply-To: lisp@ietf.org > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Locator/ID Separation Protocol WG of the > IETF. > > Title : LISP Geo-Coordinate Use-Cases > Author : Dino Farinacci > Filename : draft-ietf-lisp-geo-01.txt > Pages : 14 > Date : 2022-12-12 > > 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 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-01 > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-lisp-geo-01 > > > Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp
_______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp