Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared

Robin Whittle <rw@firstpr.com.au> Wed, 18 July 2007 10:29 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IB6n9-0006u8-Jx; Wed, 18 Jul 2007 06:29:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IB6n2-0006tp-UZ for ram@iab.org; Wed, 18 Jul 2007 06:29:53 -0400
Received: from gair.firstpr.com.au ([150.101.162.123]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IB6n0-00049i-TP for ram@iab.org; Wed, 18 Jul 2007 06:29:52 -0400
Received: from [10.0.0.8] (zita.firstpr.com.au [10.0.0.8]) by gair.firstpr.com.au (Postfix) with ESMTP id 4280F59E3C; Wed, 18 Jul 2007 20:29:49 +1000 (EST)
Message-ID: <469DEB91.1000805@firstpr.com.au>
Date: Wed, 18 Jul 2007 20:29:37 +1000
From: Robin Whittle <rw@firstpr.com.au>
Organization: First Principles
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: ram@iab.org
Subject: Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared
References: <469C962B.1090600@firstpr.com.au> <469DBFA0.7010103@cisco.com>
In-Reply-To: <469DBFA0.7010103@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

Hi Fred and Eliot,

Fred, I didn't try to compare IPvLX (http://ipvlx.com) with the
others because I think it is very different from these.  Firstly,
I understand that IPvLX requires changes in host software.
Secondly, it involves IPv6, although as best I understand it I
think you want it to help with IPv4 communications, and doesn't
actually require IPv6 connectivity.  Thirdly, I don't understand
it anywhere near enough to evaluate it.

The first point is the most important to me.  As long as a
proposal to solve what I call the "crisis in routing and
addressing" involves changes to host software, I am convinced it
will never actually be deployed.  I am am wrong about any of this,
please correct me.


Thanks, Eliot, for your appreciative response and for clarifying
some points about the state maintained in a LISP-NERD ITR.  I
understand that "ifstate" and the timer will exist for every RLOC
address the ITR has recently been attempting to send packets to,
and that the database could have one or more likely many EID
addresses and prefixes mapped to this RLOC address.

I re-read the proposals and got enough of the material in my brain
at once to be able to compare them.  There may well be
inadequacies in what I wrote.  I have a version of the comparison at:

  http://www.firstpr.com.au/ip/ivip/comp/

with a note about how the proposals will no-doubt change rapidly.
 I won't try to keep this comparison up-to-date forever, but if
there are any things I should change I will do so.  I point to
this mailing list discussion from that page.

  - Robin


_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram