Hi Dino, Med, I was preparing the refresh of LISP YANG and checking this discussion. Just so that we are all in the same page, as you know, currently the YANG model uses the geo encoding defined in RFC8060.
My understanding is that Alvaro’s plan for 8060bis [1] is to incorporate RFC-to-be-draft-ietf-lisp-geo in 8060bis. My opinion is that the YANG model should reflect whichever geo encoding ends up in 8060bis. We can discuss this further in Madrid. Alberto [1] https://datatracker.ietf.org/meeting/122/materials/slides-122-lisp-rfc8060bis-00 From: Dino Farinacci <[email protected]> Date: Tuesday, June 17, 2025 at 6:31 PM To: [email protected] <[email protected]> Cc: The IESG <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]>, Kiran Makhijani <[email protected]> Subject: [lisp] Re: Mohamed Boucadair's Discuss on draft-ietf-lisp-geo-14: (with DISCUSS and COMMENT) > On Jun 17, 2025, at 5:09 AM, [email protected] wrote: > > For the second point, the yang model will be following what is in the base > spec (i.e., draft-ietf-lisp-geo). The root issue should be discussed/fixed in > draft-ietf-lisp-geo. Thank you. I’m sorry but I don’t understand the root issue. The fields in the control packet are simply copied internally and set to the yang model according to the draft-ietf-lisp-yang document. Be specific in the issue bs pointing to an RFC. Because I can’t derive any issues or guess what your issue is. Dino _______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ lisp mailing list -- [email protected] To unsubscribe send an email to [email protected]
