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

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Sat, 09 April 2005 09:31 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 FAA21715; Sat, 9 Apr 2005 05:31:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKCSG-0006FI-Jf; Sat, 09 Apr 2005 05:40:40 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKCHn-0004D5-CG; Sat, 09 Apr 2005 05:29:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DKCHl-0004Al-By for v6tc@megatron.ietf.org; Sat, 09 Apr 2005 05:29:49 -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 FAA21667 for <v6tc@ietf.org>; Sat, 9 Apr 2005 05:29:47 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DKCQh-000684-3n for v6tc@ietf.org; Sat, 09 Apr 2005 05:39:03 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id j399TTg22483; Sat, 9 Apr 2005 11:29:29 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id j399TT8h017348; Sat, 9 Apr 2005 11:29:29 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200504090929.j399TT8h017348@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Alain Durand <alain@tycool.net>
Subject: Re: [v6tc] Let the market decide or not: L2TP and/or TSP
In-reply-to: Your message of Fri, 08 Apr 2005 11:49:23 PDT. <2ebbfb91d40e6f9790ef7c1db0abc78e@tycool.net>
Date: Sat, 09 Apr 2005 11:29:29 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: v6tc@ietf.org
X-BeenThere: v6tc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

 In your previous mail you wrote:

   L2TP:
	- Lack of a complete non authenticated mode.

=> this is not true but L2TP security is a bit complex. I'll try
to summarize it here for L2TP v2 over an IPv4 network:
 * the basic way to use L2TP is over UDP, i.e., with
   IPv4 - UDP - L2TP - PPP - IPv6 - etc
 * the highest security is provided by IPsec ESP in transport mode:
   IPv4 - ESP - UDP - L2TP - PPP - IPv6 - etc
 * as the previous solution kill the NAT traversal, it is possible to
   use IPsec in NAT traversal with L2TP directly over IP:
   IPv4 - UDP - ESP - L2TP - PPP - IPv6 - etc
 * without IPsec which can be too hard to use (no anonymous tunnel with it),
   L2TP can be protected using a shared secret (shared between the server
   and its clients) and a CHAP-like mechanism. The idea is to protect
   the L2TP control against unauthenticated access.
 * PPP itself can (should!) be protected using PAP, CHAP, ..., and
   things like MPPE. Perhaps not very good from the security point of
   view but easy to use and often already deployed.
 * last point: most L2TP servers can be configured in function of the
   client addresses so it is possible to use a fully unauthenticated
   L2TP in a closed (by anyway) network. BTW the IPsec solutions are
   a special case of this.

Regards

Francis.Dupont@enst-bretagne.fr

PS: in conclusion there is a complete non authenticated mode in L2TP
but as one should expect it must not be used in an open network...

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