Hi, >> One thing we have to be very careful with here is that EIDs are not directly >> allocated/assigned to end sites from this block. That will cause everyone to >> independently find (different) PITRs for their space, which will make a mess >> of the global IPv6 routing table... >> >> Thanks, >> Sander > > I don't think that (by definition) there is any way to cleanly aggregate PI > space. Legacy advertisements are going to be done by their LISP provider and > will have to match the endpoint's PI allocations.
Yeah, so RIR policy-making communities might want to allow for LISP-PA space for example. I don't think we can make assumptions about that here. The other side of this is then: why not use 'normal' address space? If it is going to be announced in the legacy global BGP table anyway by some LISP provider I can't see why an end-site would choose for the LISP block instead of the more flexible regular block (which can then also be used as EID space)... Thanks, Sander _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
