But don’t forget LCAFs can be used for non encapsulation purposes so there are cases where neither v4 or v6 AFIs would be used - meaning all other AFIs “could” be used.
For example you could have an AFI list of LCAFs, where each item in the list is a line in a json file. That is, each item in the list is a JSON LCAF. Or in the more “raw form”, each item is a DN to describe/encode a list of character strings. Dino > On May 28, 2026, at 1:19 AM, Alberto Rodriguez-Natal (natal) > <[email protected]> wrote: > > > >>In this case, do you think we should allow all AFIs as well? > > >For this one accepting MACs for example seems a bit odd. Even DNs. > >The usage of this LCAF seems very oriented to defining a route. If we could > >find an easy way to >describe v4, v6 and only those LCAFs that can > >complement v4 and v6 hops. > >Not sure how to be precise here. > > [AR] How about something along the lines of “If LCAF is used, the most inner > address within the LCAF (or nested LCAFs) must be v4 or v6" > > _______________________________________________ > 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]
