> ---------------------------------------------------------------------- > DISCUSS: > ----------------------------------------------------------------------
Thanks for the comments Med. Revision -15 has been submitted with changes to reflect your comments. See resposnes inline to your commentsd. > > Hi Dino, > > Thanks for the effort put into this specification. > > Please find below two DISCUSS points: > > # We need to define the experiment, goals, and criteria to declare > failure/success. > > # How the encoding articulates with the various management pieces out there? The yang model draft needs to be updated to reflect the protocol message definition. It should be the authoritative source. I will let the chairs ping the LISP yang authors. > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > # Compatibility with the GPS use in routing > > The document says in several places: > > Abstract: > which is compatible with the Global Positioning Satellite (GPS) > encodings used by other routing protocols. > > Intro: > This document proposes a new LCAF encoding for Geo-Coordinates, which > is compatible with the one used in other routing protocols, namely > OSPF [I-D.acee-ospf-geo-location], IS-IS > [I-D.shen-isis-geo-coordinates], and BGP > [I-D.chen-idr-geo-coordinates] protocols > > Section 4.1: > The encoding format is consistent with the encoding used in other > routing protocols, namely OSPF [I-D.acee-ospf-geo-location], IS-IS > [I-D.shen-isis-geo-coordinates], and BGP > [I-D.chen-idr-geo-coordinates]. > > > However, and unless I’m mistaken, all those were expired since 2016/2017. At the time the 4 efforts were creating GPS encodings for the 4 protocols, we decided to say coordinated and in sync. I can not commit why or why not the working groups have expired the drafts. But the intent still stands and I don't want to remove the references. > Unless we have fresh data to back this claim, I would simply delete this > sentence. > > # Compatibility with the GPS use in routing > > # nits > > ## abstract > > OLD: > 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, > > > NEW: > This document describes how Geo-Coordinates can be used in the > Locator/ID Separation Protocol (LISP). Specifically, the document defines a > new LISP Changed. > > ## Introduction > > (1) > > OLD: > The LISP architecture and protocols [RFC9300] introduce two new > > NEW: > The Locator/ID Separation Protocol (LISP) [RFC9300] introduces two new Changed. > > (2) > > OLD: This document proposes a new LCAF > > NEW: This document defines a new LCAF > > Cheers, > Med Changed. Thanks again, Dino _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
