Hi Dino, Thank you for the follow-up and the new revision draft-ietf-lisp-geo-15.
Please see inline. Cheers, Med > -----Message d'origine----- > De : Dino Farinacci <[email protected]> > Envoyé : dimanche 25 mai 2025 00:38 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]> > Cc : The IESG <[email protected]>; [email protected]; lisp- > [email protected]; [email protected]; Kiran Makhijani > <[email protected]> > Objet : Re: Mohamed Boucadair's Discuss on draft-ietf-lisp-geo-14: > (with DISCUSS and COMMENT) > > > > ----------------------------------------------------------------- > > 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. [Med] I don't see this addressed in draft-ietf-lisp-geo-15. > > > > # 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. [Med] ACK. What about consistency with RFC9179? > > > ----------------------------------------------------------------- > > 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. [Med] I understand that was the deal at that time but these efforts were abandoned. 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. [Med] My concern is more about this claim: "which is compatible with the Global Positioning Satellite (GPS) encodings used by other routing protocols" > > > 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. [Med] Thanks. > > > > > ## Introduction > > > > (1) > > > > OLD: > > The LISP architecture and protocols [RFC9300] introduce two new > > > > NEW: > > The Locator/ID Separation Protocol (LISP) [RFC9300] introduces > two > > new > > Changed. [Med] Thanks. > > > > > (2) > > > > OLD: This document proposes a new LCAF > > > > NEW: This document defines a new LCAF > > > > Cheers, > > Med > > Changed. [Med] Thanks. > > Thanks again, > Dino > ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
