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 s
Okay, we are synced.
Dino
> On Feb 28, 2022, at 10:35 PM, Joe Touch wrote:
>
> In the example I gave, I was equating GRE *to* UDP, not saying it ran over
> UDP, though it can (port 4754, per RFC 8086).
>
> Joe
>
>> On Feb 28, 2022, at 10:15 PM, Dino Farinacci wrote:
>>
>> There is no UDP
NAT IMHO has been vilified for a lot of bad instances of NAT from the past.
Now unfortunately, the term is identified with evil only, so maybe we should
find a better term for what IMHO are really useful/beneficial instances.
Maybe "address rewrite".
Non-evil address rewrite IMHO is per-flow-state
> 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 (
