Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers

Jari Arkko <jari.arkko@piuha.net> Thu, 24 September 2009 19:26 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A9263A6922 for <lisp@core3.amsl.com>; Thu, 24 Sep 2009 12:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.625
X-Spam-Level:
X-Spam-Status: No, score=-2.625 tagged_above=-999 required=5 tests=[AWL=-0.026, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9m-uhM1usHI6 for <lisp@core3.amsl.com>; Thu, 24 Sep 2009 12:26:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 8D80C3A68C9 for <lisp@ietf.org>; Thu, 24 Sep 2009 12:26:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 50D58D4943; Thu, 24 Sep 2009 22:27:41 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nr1AF8ZlgY1Y; Thu, 24 Sep 2009 22:27:40 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id D411DD4922; Thu, 24 Sep 2009 22:27:39 +0300 (EEST)
Message-ID: <4ABBC82A.7030106@piuha.net>
Date: Thu, 24 Sep 2009 22:27:38 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
References: <20090919171820.746426BE628@mercury.lcs.mit.edu> <4AB5AA3C.5090805@firstpr.com.au> <C0ACCB7B60E6F14B9AC46D742C1009A15D0AAD@xmb-sjc-213.amer.cisco.com> <tsl8wg8cgmx.fsf@mit.edu> <20090921204855.GA7205@1-4-5.net> <tslskegat2z.fsf@mit.edu>
In-Reply-To: <tslskegat2z.fsf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: lisp@ietf.org, Robin Whittle <rw@firstpr.com.au>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 19:26:33 -0000

This working group is not chartered to develop solutions to the 
IPv4-IPv6 transition problem. We have plenty of other working groups in 
that space already.

Of course, I understand that pretty much any tunneling or translation 
technique can be used for IPv6 deployment as well. I do not mind if such 
use case gets mentioned in a list of other potential uses of Lisp. 
However, the main use case, deployment rationale, etc. needs to stand on 
its own and talk about routing scalability, traffic engineering, and 
other things central to Lisp. I also understand that what we develop 
technology X for may not be what it eventually gets used for; we've been 
surprised before. Lets see what happens with Lisp. But for the RFCs that 
come out of this working group, lets focus on the initial main reason 
why Lisp was developed.

Jari