On Tue, Mar 01, 2022 at 11:54:35AM -0800, Dino Farinacci wrote:
> > For example: The use of locator/identifier in RFC6830 (LISP) i think is,
> > to use the White Knight's terminology, only what an address is
> > called by an xTR (or the LISP instance) but nothing more: It does not
> > defining what the nature of the locator or identifier addresses are.
>
> An identifier (i.e. EID) typically is static (can be dynamcially assigned)
> and is used by the transport layer and not routable by the underlay. A
> locator (i.e. RLOC) is an address, according to the definition that everyone
> understands today, is used in the outer header encapsulation and is routable
> by the underlay.
>
> It is that simple, even though I made the description lengthy to be a bit
> more complete on their usage.
Thanks. Not contradicting what i claimed... I think.
My point was specifically that the LISP locator helps LISP to "locate" another
xTR, but that is different from whether or not the locator by the nature
of its address structure helps the underlay to locate the entity (xTR) that the
address is assigned to (xTR). So the name 'locator' is 'just' a good
name for what LISP calls/uses the address for, not for how the under
itself would maybe call the address or use the address for.
Cheers
Toerless
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
