BTW - the ability to take a piece of IPv4 PA space, and start
announcing it as if it were PI space, is an example of the kind of
thing that needs to be supported.
Changing the role of a "piece" of the Internet, without renumbering.
So Brian, the decoupling that Loc/ID split gives you is attractive.
And if a site decides to use PA space as an EID-prefix, let's say
while it is still connected to the provider that owns it. If the site
decides to discontinue contract with the provider, gives back, say the
locator the CE box has assigned to it, what do you think should happen
to the PA block?
That is:
1) Do you lose EID address portability in this case because a site
decided to use PA space? And therefore doesn't get the renumbering-
avoidance benefit of Loc/ID split.
2) The service provider is willing to give up the space, which means
it routes only for a small part of this space (the locator space) and
not the entire larger space where EID-prefixes would be allocated out
of?
Some of the struggles that can make LISP much more efficient is to
look at an address and tell from an allocation bits, if it's EID
versus RLOC space. Then you can interwork LISP sites with non-LISP
sites much more efficiently. Easier to do with IPv6 but we may
struggle with IPv4 because EID-prefixes could come out of all kinds of
allocations including PA space.
I would be interested to hear what SPs have to say about this.
Dino
--
to unsubscribe send a message to [EMAIL PROTECTED] with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
