Eliot, *:
Thanks for the historic reference to IEN19!
IEN19 defines that "an address indicates *where* it is". But in the
Internet, my rfc4291 subnet prefix is injected into Internet BGP,
so that (part of the IPv6) address does not tell me nada, zilch,zip
about *it*'s location. Only the routing system knows the location.
Maybe IEN19 was written with E.164 routing as its core reference, where
i guess (at least back then), the actual location of *it* was
indeed fixed by the physical point of attachment, and the dynamic
routing system only allowed to plot more than one path to *it*.
And of course, the other part of the rfc4291 address is already
called (interface) interface, so it too isn't indicating, where
*it* is. I am obviously using elecrtromagnetic broadcast via
a WiFi AP or a yellow ethernet to locate *it*, not the address.
Did we (e.g.: through locator/identifier split effort or other)
ever came up with some cross-technology consistent terminology for the
nature of an address, such as whether or how we decide if/what is
a locator and/or identifier (or any other name-calling for addresses) ?
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.
So maybe there is no such thing as "are" unless we start having self-aware
addresses. Maybe we should only think about what (the parts of)
addresses "is called" by specific entities using them such as the network
routing subsystems address registries or APIs into the forwarding layer.
Cheers
Toerless
On Tue, Jan 25, 2022 at 08:46:13AM +0100, Eliot Lear wrote:
> The orthodoxy here is the seminal work of Shoch[1]. And of course there's
> Saltzer et al.[2] The assumptions being made today by different players are
> indeed all over the map. Routing is a function of the network. Or is it?
> Privacy is something the endpoint must manage. Or is it? So I like your
> approach for discussion.
>
> Eliot
>
> [1] http://www.postel.org/ien/txt/ien19.txt
> [2] http://web.mit.edu/Saltzer/www/publications/endtoend/endtoendA4.pdf
_______________________________________________
Int-area mailing list
Int-area@ietf.org
https://www.ietf.org/mailman/listinfo/int-area
