I was reminded in recent discussion that the LCAF AFI is allowed both
for RLOCs and for EIDs.
For RLOCs, I have raised the concern that when an ETR injects RLOCs
using various LCAFs, it has no way to know whether the receiving ITRs
will be able to understand the LCAF. For some cases, this is actually a
benefit. But particularly if the structure within the LCAF gets more
diverse, it seems to get difficult. I do see the argument for
flexibility here.
But then my naive participant head exploded when I tried to apply this
to an EID. Are all mapping systems required to handle all LCAFs? At
first, this seems reasonable. As long as you are just doing pure prefix
matching, it is just a variable length "address".
But then we see things which have internal mask lengths. Or might need
prefixing on multiple fields. Or might have even more complex match
criteria.
If the mapping system can always treat and LCAF EID as a prefix-matched
bit string, I get it. But if not, how is this supposed to work?
Sorry for a basic question,
Joel
_______________________________________________
lisp mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lisp
