Hi Dino, I'm fully supportive of the consistency argument (this is actually a reason of my second DISCUSS point :-)). However, I'm still not comfortable to include claims such the one raised in my ballot for the simple reason that we don't have any IETF-endorsed solution. I don't think maintaining this claim adds much, but if you prefer cite these expired drafts, you may reword, e.g.,
DELETE this part from the abstract: which is compatible with the Global Positioning Satellite (GPS) encodings used by other routing protocols. + make this change OLD: This document defines 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 NEW: This document defines a new LCAF encoding for Geo-Coordinates, which is compatible with the one proposed for 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. + DELETE this part: 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]. Thank you. Cheers, Med > -----Message d'origine----- > De : Dino Farinacci <farina...@gmail.com> > Envoyé : lundi 26 mai 2025 22:49 > À : BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com> > Cc : The IESG <i...@ietf.org>; draft-ietf-lisp-...@ietf.org; lisp- > cha...@ietf.org; lisp@ietf.org; Kiran Makhijani > <kiran.i...@gmail.com> > Objet : Re: Mohamed Boucadair's Discuss on draft-ietf-lisp-geo-14: > (with DISCUSS and COMMENT) > > > >> 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" > > And is true if implmentations used the draft. Its a specific > working group issue. And if the working groups decide this is a > needed feature, then they will resurect the drafts. > > Its better to document, that we were in coorindation versus > designing in silos. > > 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 -- lisp@ietf.org To unsubscribe send an email to lisp-le...@ietf.org
