Re: [Int-area] Continuing the addressing discussion: what is an address anyway?

[Dino Farinacci <[e-mail]>]

> On Mar 7, 2022, at 4:18 AM, Jens Finkhaeuser <[e-mail]> wrote:
> 
> Different sections of the draft claim different things; some claim EIDs never change, others talk about multiple EIDs used in different scenarios. I find section 5.1 interesting: "It is anticipated that these EIDs will change infrequently if at all, since the assignment of a LISP-MN's EID is envisioned to be a subscription time event."
> 
> Subscription is an undefined term that also appears in LISP+ALT. In the context of drones (not to bombard you with terminology from that area), one could imagine that subscription occurs when loading a mission plan onto a drone prior to departure. But by definition, this then only entails anticipated scenarios, not emergency response situations.

"Subscription time" means the mobile-node manufacture assigns an EID like it would a IMEI. Then it never changes.

> A completely static drone identifier is one thing; EIDs changing rarely is another. Drones may require communications with isolated, private networks, which are outside the scope of LISP+ALT - how subscription should be interpreted here is an interesting topic!

EIDs need to be unique *within* a mapping system. So you can have multiple mapping systems that use, say 240.0.0.0/4 (for IPv4 EIDs), for static assignment, where the low-order 3 bytes is a random number generated and verify from the mapping system the node uses to be unique.

Dino