Re: [RAM] New LISP draft available ...
Dino Farinacci <dino@cisco.com> Wed, 25 July 2007 05:31 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 1IDZSm-0007cp-Vb; Wed, 25 Jul 2007 01:31:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1IDZSm-0007cj-68
for ram@iab.org; Wed, 25 Jul 2007 01:31:08 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDZSl-000462-Ny
for ram@iab.org; Wed, 25 Jul 2007 01:31:08 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
by sj-iport-5.cisco.com with ESMTP; 24 Jul 2007 22:31:07 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAC59pkarR7O6/2dsb2JhbAA
X-IronPort-AV: i="4.16,578,1175497200";
d="scan'208"; a="168051148:sNHT56488851"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l6P5V6HR026140;
Tue, 24 Jul 2007 22:31:06 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
[64.102.31.102])
by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l6P5V1A2017072;
Wed, 25 Jul 2007 05:31:06 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 25 Jul 2007 01:31:01 -0400
Received: from [172.28.168.212] ([10.82.219.32]) by xfe-rtp-201.amer.cisco.com
with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 25 Jul 2007 01:31:01 -0400
In-Reply-To: <75A199C5D243C741BF3D3F1EBCEF9BA50132C128@E03MVZ1-UKDY.domain1.systemhost.net>
References: <1DFBAD55-CA28-4D44-9F96-218F5F281047@cisco.com>
<Pine.LNX.4.64.0707231019230.13685@chandra.student.uit.no>
<75A199C5D243C741BF3D3F1EBCEF9BA50132C128@E03MVZ1-UKDY.domain1.systemhost.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8168EC57-DF7E-4EC1-A32C-167EB955A34E@cisco.com>
Content-Transfer-Encoding: 7bit
From: Dino Farinacci <dino@cisco.com>
Subject: Re: [RAM] New LISP draft available ...
Date: Tue, 24 Jul 2007 22:30:54 -0700
To: "<philip.eardley@bt.com>" <philip.eardley@bt.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 25 Jul 2007 05:31:01.0119 (UTC)
FILETIME=[FC8500F0:01C7CE7C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1375; t=1185341466;
x=1186205466; c=relaxed/simple; s=sjdkim2002;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
d=cisco.com; i=dino@cisco.com;
z=From:=20Dino=20Farinacci=20<dino@cisco.com>
|Subject:=20Re=3A=20[RAM]=20New=20LISP=20draft=20available=20...
|Sender:=20; bh=agT8JLUymg3r+oRW+FS2bLLf9AkwUHspLyNfj6AcioM=;
b=pmdqYnKV7CvuIZWMKoxeKb72BZj36VDcF6w10NRc1xdqxxttLwgHXHC5Sp2Z0Y0ZqmWVm/Bu
c6jNqCZ9FKoXOKF/g5fP8QA/FhMWwKgB4MaGXN0g+24vbt8gfNJsNHHU;
Authentication-Results: sj-dkim-2; header.From=dino@cisco.com; dkim=pass (si
g from cisco.com/sjdkim2002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: ram@iab.org
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
> what's the relationship between the variants of lisp? Is it
> considered that an operator
They are implementation and deployment alternatives to experiment and
learn about the design. We have already learned quite a bit so we can
eliminate some of the variants before ever deploying them.
> would migrate through the 4 steps lisp 1 -> 1.5 -> 2 -> 3? Could
> the variants co-exist?
At this point we think we can do a scalable mapping infrastructure
with a LISP 1.5 variant that can go multiple ways. Or, a LISP 3
variant that proposes one of (or a hybrid of) CONS, NERD, or APT.
> Or are they really 4 independent proposals? ('independent' meaning
> you make a choice of which *one* to deploy)
The data-plane encapsulation is the same in all of them. The locator
reachability mechanism is the same in all of them.
What differs is the way you retrieve EID-to-RLOC mappings. In LISP
1.0 and 1.5, it is via data-triggered evens and in LISP 2 and LISP 3,
it is purely in the control-plane.
> since lisp 1 uses routable EIDs, will it get the benefits hoped for
> a locator/ID split approach (in terms of the design goals in draft-
> irtf-rrg-design-goals)?
LISP 1 and LISP 2 will probably never get deployed.
> sorry if questions have already been covered
They have, but it's okay to repeat for clarity.
Dino
_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram
- [RAM] New LISP draft available ... Dino Farinacci
- Re: [RAM] New LISP draft available ... Brian E Carpenter
- Re: [RAM] New LISP draft available ... Roger Jorgensen
- RE: [RAM] New LISP draft available ... philip.eardley
- Re: [RAM] New LISP draft available ... Dino Farinacci
- Re: [RAM] New LISP draft available ... Dino Farinacci
- Re: [RAM] New LISP draft available ... Scott Brim
- Re: [RAM] New LISP draft available ... Brian E Carpenter
- Re: [RAM] New LISP draft available ... Dino Farinacci
- Re: [RAM] New LISP draft available ... Brian E Carpenter
- Re: [RAM] New LISP draft available ... Dino Farinacci
- RE: [RAM] New LISP draft available ... Templin, Fred L
- Re: [RAM] New LISP draft available ... Brian E Carpenter
- Re: [RAM] New LISP draft available ... Dino Farinacci