The low order 24 bits of the 32 bits in the control plane is used in the data plane. It’s a feature and implemented. Do not remove this. You break implementations.
This has been brought up several times before (by you) and I have made the same comment. Dino > On Mar 24, 2025, at 6:41 AM, Luigi Iannone <g...@gigix.net> wrote: > > Hi Dino, > > > >> On 18 Mar 2025, at 22:04, Dino Farinacci <farina...@gmail.com> wrote: >> >> Regarding what you said here Luigi, creating a 32-bit IID was intentiional >> so you can have more than 2^24 VPNs per instance of a data-plane. That is >> you can duplicate IIDs if different mapping systems were used for the same >> underlay. > > Yes, but RFC 9300 specifies IID as a 24 bits field. There is no > inter-operable description in how to convert a 32-bit field in a 24-bit and > vice versa. Hence we should just stick to 24 bits. > >> >> Also there was something you said that was incorrect. You said "on the wire >> the IID is 24-bits”. > > You are right on this. I did remeber the 8060 type 2 LCAF wrongly. > > >> Well when control plane messages are sent on the wire they are 32-bits. So >> in data packets its 24 and in control packets its 32. > > Which is an inconsistency and we should fix this now. > > Luigi > >> >> Dino >> >> <PastedGraphic-1.png>_______________________________________________ >> lisp mailing list -- lisp@ietf.org >> To unsubscribe send an email to lisp-le...@ietf.org > _______________________________________________ lisp mailing list -- lisp@ietf.org To unsubscribe send an email to lisp-le...@ietf.org
