On Thu, Oct 31, 2013 at 5:07 PM, Rene Bartsch <[email protected]> wrote: > Am 2013-10-31 16:32, schrieb [email protected]: >> I am fairly sure that this is outside the scope of this WG. I'm not sure >> where >> is; perhaps someone who's more familiar with the current broad scope of >> IETF >> efforts can point out the appropriate place for that. >> >> Obviously, if personal PI blocks happen, they will need some sort of >> identity/location suppport to make them work, but LISP is only one >> possibility >> for that. > > > I see the scope of this experiment to create an OSI-layer 3.5 which inserts > an identity-location abstraction between OSI-layer 3 and 4 - which just > means it creates end-to-end connectivity using roamable identities. And if > improving communication and boosting the economy by consumer roaming is a > by-product, we should jump at the chance. > > And experimenting with a dedicated EID-prefix will help us to find ways to > aggregate routing(-tables) to run a infrastructure with so much expected > endpoints smoothly.
I must admit I wrote the outline of the mgmt-draft on purpose in a quite generic way so it is possible to use it without LISP.... it would be really stupid (I think) to lock it to LISP use only. Does any of you know what the future might bring? This might be the best idea in quite some years for all we know. However, as pointed out by Dino and Noel, the point with this experiment is quite well defined, the text in the draft might not be perfect so good have this feedback:-) And about Sander Steffann's problem: "I understand what the technical idea is. There are already EIDs out there (including my own network) that are not in any special prefix. Therefore "address is in special prefix" != "address is an EID". Unless you break LISP for already existing sites I don't see how having a special prefix is going to help in (correctly) determining whether an address is an EID." The _big_ difference between EID's out there today, and the one from this new netblock are that any system should _know_ by matching the IP that this is EID space, and by that know how to handle it. If traffic grow as everyone predict, and continue todo so, optimizing the handling of LISP EID's is probably a very good idea. -- Roger Jorgensen | ROJO9-RIPE [email protected] | - IPv6 is The Key! http://www.jorgensen.no | [email protected] _______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
