RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared
"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 18 July 2007 15:13 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 1IBBDe-0002DX-5f; Wed, 18 Jul 2007 11:13:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1IBBDZ-0002D7-Cz
for ram@iab.org; Wed, 18 Jul 2007 11:13:33 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBBDY-0003ml-3Y
for ram@iab.org; Wed, 18 Jul 2007 11:13:33 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
ESMTP id l6IFDKcl021092
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
Wed, 18 Jul 2007 08:13:20 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
l6IFDKKT023854; Wed, 18 Jul 2007 08:13:20 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
[130.247.55.84])
by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
l6IFDFXg023702; Wed, 18 Jul 2007 08:13:20 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 18 Jul 2007 08:13:18 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared
Date: Wed, 18 Jul 2007 08:13:18 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED91C@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <469DEB91.1000805@firstpr.com.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared
Thread-Index: AcfJJpNstuBmMKBSTDuvhfo51w1qRQAJCuAQ
References: <469C962B.1090600@firstpr.com.au> <469DBFA0.7010103@cisco.com>
<469DEB91.1000805@firstpr.com.au>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Robin Whittle" <rw@firstpr.com.au>, <ram@iab.org>
X-OriginalArrivalTime: 18 Jul 2007 15:13:18.0371 (UTC)
FILETIME=[2BDA5730:01C7C94E]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc:
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 Robin, Thanks for looking. Just as clarification, IPvLX does not require changes to host software; it requires changes to router software. If the host and router occur on the same physical platform (which is *not* a requirement), then it may appear that host software changes are needed - but, it is really only router software that is being changed. About similarities to other proposals, I think if there were to be a LISP 2 it would probably look a lot like IPvLX. But, there is no reason IPvLX can't be extended to support other mapping mechanisms than just DNS, too. About IPv6, IPvLX accomplishes the ID/loc split by using IPv6 addresses as EIDs and IPv4 addresses as RLOCs. Thanks - Fred fred.l.templin@boeing.com > -----Original Message----- > From: Robin Whittle [mailto:rw@firstpr.com.au] > Sent: Wednesday, July 18, 2007 3:30 AM > To: ram@iab.org > Cc: Eliot Lear; Templin, Fred L > Subject: Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared > > 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
- [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Templin, Fred L
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Eliot Lear
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Templin, Fred L
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Templin, Fred L
- RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Templin, Fred L
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Dino Farinacci
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- RE: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Templin, Fred L
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Dino Farinacci
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Dino Farinacci
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Dino Farinacci
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Dan Jen
- Re: [RAM] LISP NERD/CONS, eFIT-APT & Ivip compared Robin Whittle