> > Actually, that use case is only helped by the EID block if you can be sure > that ALL the destination EIDs it will see will come from the block.
I don't believe so. It could just an efficiency play for one versus the other. > Which seems to be impossible to ensure in the general case. And easy to > achieve without an allocated block in many of the special cases. Well the EID could mean it is behind a NAT and that ITRs should encapsulate to an RTR. Maybe one that is used by a default map-cache entry or a distinguished key on the mapping database. See there are sorts of things we could try. Again, "try" here means experimentation. Look how the pilot network was easier to debug since we had 153.16.0.0/16 generically donated by Andrew Partan and how cisco has been renting 2610:d0::/32. Dino _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
