RE: [RRG] loc/id split and LISP

[Sheng Jiang <shengjiang@huawei.com>]

Catching up from the national holiday...

In my opinion, the most important point should not be whether LISP or DNS/IP
is nature identifier/locator split solution. It should be what benefit LISP
can bring us. For me, LISP partly solves the routing convergence issue with
the minimum modification on the current Internet architecture. Of course,
LISP could introduce another namespace in order to be a real
identifier/locator split solution, actually there are such approaches, but
that would be too expensive to be deployed. LISP is not the best solution,
but it is the most realistic in a short term. It is a result of compromise.

Best regards,

Dr. Sheng JIANG

IP Research Department, Networking Research Department, Network Product
Line, Huawei Technologies Co. Ltd.

*-----Original Message-----
*From: owner-rrg@psg.com [mailto:owner-rrg@psg.com] On Behalf Of Eliot Lear
*Sent: Monday, October 01, 2007 9:05 PM
*To: HeinerHummel@aol.com
*Cc: xuxh@huawei.com; rrg@psg.com
*Subject: Re: [RRG] loc/id split and LISP
*
*>
*Hi,
*> Thanks for responding, but this is not what I wanted to say. LISP may
*> even have been triggered due to the identifier/locator dual nature
*> discussion. But in the end it is (imho) a two loose hops forwarding
*> where the EID is also used like a locator - well, for the second loose
*> hop.
*
*Everyone has a slightly different view of this, and I think yours as as
*good as any.  Dino and crew set out to tackle a very specific and well
*scoped problem, which really had very little to do with what many people
*believe is the IP/loc split.  They were out to change the nature of the
*performance curve by adding an additional tier of routing that is
*bilateral in nature rather than multilateral.  To me that's the
*fundamental challenge.  IDs and locators are not a central them in LISP,
*IMHO.  And for that matter, neither is whether you tunnel or map
*(although each has its advantages).
*
*Eliot
*
*--
*to unsubscribe send a message to rrg-request@psg.com 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



--
to unsubscribe send a message to rrg-request@psg.com 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