Re: [v6tc] Let the market decide or not: L2TP and/or TSP

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Fri, 08 April 2005 19:48 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02752; Fri, 8 Apr 2005 15:48:51 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJzc8-0001OO-G4; Fri, 08 Apr 2005 15:58:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJzST-0007Qy-8I; Fri, 08 Apr 2005 15:48:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJzSS-0007Qg-9p for v6tc@megatron.ietf.org; Fri, 08 Apr 2005 15:48:00 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02432 for <v6tc@ietf.org>; Fri, 8 Apr 2005 15:47:58 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJzbG-00019p-PO for v6tc@ietf.org; Fri, 08 Apr 2005 15:57:07 -0400
Received: from [10.10.10.100] ([217.126.187.160]) by consulintel.es (consulintel.es [127.0.0.1]) (MDaemon.PRO.v7.2.3.R) with ESMTP id md50000904802.msg for <v6tc@ietf.org>; Fri, 08 Apr 2005 21:49:21 +0200
User-Agent: Microsoft-Entourage/11.1.0.040913
Date: Fri, 08 Apr 2005 21:13:54 +0200
Subject: Re: [v6tc] Let the market decide or not: L2TP and/or TSP
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6tc@ietf.org" <v6tc@ietf.org>
Message-ID: <BE7CA492.F2D04%jordi.palet@consulintel.es>
In-Reply-To: <2ebbfb91d40e6f9790ef7c1db0abc78e@tycool.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-MDRemoteIP: 217.126.187.160
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6tc@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail.consulintel.es
X-Spam-Status: No, hits=-4.1 required=5.0 tests=BAYES_00,TO_ADDRESS_EQ_REAL autolearn=ham version=2.64
X-Spam-Processed: consulintel.es, Fri, 08 Apr 2005 21:49:34 +0200
X-MDAV-Processed: consulintel.es, Fri, 08 Apr 2005 21:49:36 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Content-Transfer-Encoding: 7bit
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: v6tc.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/v6tc>
List-Post: <mailto:v6tc@ietf.org>
List-Help: <mailto:v6tc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/v6tc>, <mailto:v6tc-request@ietf.org?subject=subscribe>
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: 7bit

Hi Alain,

My comments below, in-line.

Regards,
Jordi




> De: Alain Durand <alain@tycool.net>
> Responder a: <v6tc-bounces@ietf.org>
> Fecha: Fri, 8 Apr 2005 11:49:23 -0700
> Para: "v6tc@ietf.org" <v6tc@ietf.org>
> Asunto: [v6tc] Let the market decide or not: L2TP and/or TSP
> 
> BOF chair hat still on, I'm going to try to summarize the discussion so
> far.
> 
> - Time to market is critical.
> - TSP & L2TP are the two natural candidates

Or something better if we can make it quickly.

> - The end point discovery is a difficult but orthogonal issue that
> should not
>     clout the discussion on tunnel configuration. I'm not going to
> address
>     it in this email.
> 
> Back to TSP & L2TP.
> 
> - L2TP is standardized, but a document explaining how to use it
>  in the IPv6 transition phase might be needed.
> 
> - 3 issues have been raised with L2TP:
> - large number of RTT. This is only on issue in low latency networks
>   such as 3G. If we are NOT looking for a combined solution for
> fixed/wireless 3G
>   this is a non issue, if we are, this is a show stopper.
> - Lack of a supported implementation of IPv6 over PPP on a very
> critical OS.
>  IMHO, this is issue for the company that makes this OS, not for the
> IETF...
>  ... on the other hand, time to market is critical.
> - Lack of a complete non authenticated mode.
>  This needs to be investigate further, as it is not absolutely clear
> to me
>   it can't be done.
> 
> - Issues with TSP:
> - not been through community review (i.e. no RFC to point to)
> - re-opening TSP might sounds like duplicating L2TP

The other issue with TSP that was commented was the unnecessary overhead
because the usage of XML, this could be improved very easily, I guess.

> 
> Now, here are the questions I would like this group to try to answer:
> 
> 1) is a combined mechanism for fixed/wireless 3G network still
> important?

Somehow I could say yes, because we don't want to have in the small devices
(such as cellular phones, both protocols, for example when they have both 3G
and WLAN interfaces).

But an alternative is a self adaptative protocol which is actually like both
well integrated.

> 
> 2) Is it the case that we have to define BOTH an L2TP based mechanism
> AND TSP
>       with all the operational/implementation headaches of having to
> support 2 things
>       in order to "let the market decide" or do people think we need one
> and only one
>       mechanism?

Yes, I will say so, if possible. But I'm still not excluding the option of
something else. I mean, if we do it quickly, why not choose among L2TP, TSP
or a new protocol which integrates the good things that we learned from
several of the available protocols (I explained this in my first email on
this thread).

> 
> 
> Please focus your answers on those two questions.
> 
> - Alain.
> 
> 
> _______________________________________________
> v6tc mailing list
> v6tc@ietf.org
> https://www1.ietf.org/mailman/listinfo/v6tc




************************************
Barcelona 2005 Global IPv6 Summit
Registration open. Information available at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




_______________________________________________
v6tc mailing list
v6tc@ietf.org
https://www1.ietf.org/mailman/listinfo/v6tc