> Yes this is true - any mapping can be used to express much more then > topological information. See LISP as example :)
With respect to the data-plane, the ELP (Explicit Locator Path, defined in RFC8060 and use-cases in draft-ietf-lisp-te) RLOC-record: The L-bit, when set, means that Reencap Hop is routable by the underlay (an RLOC). When 0, a mapping system lookup can be performed to get the RLOC. Hence, doing what Tom commented on. Note this format above is in the *control-plane* and each node along the segment-route(LOL)/reencapsulation path has the ELP stored apriori. My demo of SR using the LISP mapping system, these ELP formatted records are used and registered in the mapping system. They are registered with L-bit set to 1 and the AFI=2 (an IPv6 RLOC). But note, if you used this in the control-plane, there would be no packet overhead because the destination address used to find these ELP paths. The authors of SR already know this. FYI, Dino
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
