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

Re: [GROW] LISP at GROW



 

| > If a site wants to change its
|> EIDs, it's forced to renumber.  
|
|That's a tautology.


So the implication is that LISP doesn't really protect the end user site
from having to renumber.

Per Lixia's presentation in RRG, she's asserting that protection from
renumbering is a hard requirement, as there has been no forward progress on
getting anyone to renumber in at least 13 years.


|> If it changes its ISP but doesn't
|> change its EIDs, then it's still locked into a 'mapping provider'.
|
|I'm guessing you're concerned about business relationships.  
|Locked in? 
|  First, you are already "locked in", for example to your DNS 
|provider, 
|and somehow you survive.  Second, the possibilities for business 
|relationships are wide open.  For example the lowest levels of the ALT 
|could be provided by small enterprises (like DNS names), and the key 
|higher levels by non-profits.  So I think it's wildly premature to 
|assume the worst.


There are numerous DNS providers, and changing your DNS server is a far less
costly proposition than renumbering by several orders of magnitude.  The
fact of the matter is that today, folks do not feel that DNS creates a
lock-in (there are plenty of registrars), but that addressing is a lock-in,
so they go get PI.

FWIW, I'm not assuming anything, I'm just trying to understand how things
will work if LISP is deployed.  So far, I see a few issues.

Tony

_______________________________________________
GROW mailing list
GROW at ietf.org
https://www.ietf.org/mailman/listinfo/grow