>From my understanding of the use-case, I believe there are no changes to the >base protocol to support this use-case. Regarding EID assignment and >allocation, that is an admin/configuration function.
H3-EIDs makes sense for assigning to nodes that provide services. But I forget if you wanted to allocate an H3-EID to a moving vehicle. Because as the EID moves, the H3 hexagon can change even the H3-ID is from resolution 16. Unless you want to scope the mobility and when the vehicle moves, you assign a new H3-EID. I hope you don't do thw latter or you lose the EID-mobility features LISP has (or maybe don't need it in this case). Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
