Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



And you do not want to tie addresses to topological entities. Or you will lose the mobility capabilities that Locator/ID separation can bring.

Dino

On Nov 15, 2012, at 12:21 PM, Paul Vinciguerra <pvinci@xxxxxxxxxxxxxxxxxxx> wrote:

>> 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.




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]