> 1. The Edge Geolocation Services EIDs have a 64bit H3-ID part of the location > of the Vehicle being served > > 2. This is how we eliminate the need for an actual geospatial network. These > are virtualized in the form of H3EIDs
Okay, so "Geolocation Services EID" equals an H3EID. > 3. The prefix of the service EID is the H3 location it serves, the suffix is > the specific Geolocation Service: collection, parking .. Right, thought so. > 4. The vehicle EID is not related to location (H3) because its moving. It is > however ephemeral to protect drivers geoprivacy Good. > 5. The only entity which knows the vehicle carrier assigned RLOC is its RTR. > We can host those at the carrier (UPF) or bring your own Great. > 6. Both lisp-nexagon and lisp-fix do not change the protocol. But you do have > to understand the map assisted overlay ucast/mcast I don't understand what you mean. Say more please. > 7. Maybe after more examples we can generalize how Compute First Networks use > LISP to aggregate and reduce data on a need to know basis.. > > ..so that non lispers can follow a cookbook, but for now we need to do it > example at a time i think. lisp-nexagon in publication lisp-fix-00 i think > work group response was good, so by next ietf?? Yes. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
