IETF Logo Mail Archive

Re: [v6tc] Re: Tunneling and Transition Drafts

Jeroen Massar <jeroen@unfix.org> Fri, 08 April 2005 11:17 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 HAA04180; Fri, 8 Apr 2005 07:17:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJrcy-0006lz-Oj; Fri, 08 Apr 2005 07:26:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJrSh-0002Vj-QL; Fri, 08 Apr 2005 07:15:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DJrSf-0002Ve-Qf for v6tc@megatron.ietf.org; Fri, 08 Apr 2005 07:15:41 -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 HAA04136 for <v6tc@ietf.org>; Fri, 8 Apr 2005 07:15:38 -0400 (EDT)
Received: from 213-136-24-43.adsl.bit.nl ([213.136.24.43] helo=purgatory.unfix.org ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJrbO-0006kb-Uc for v6tc@ietf.org; Fri, 08 Apr 2005 07:24:44 -0400
Received: from firenze.zurich.ibm.com (pat.zurich.ibm.com [195.176.20.45]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by purgatory.unfix.org (Postfix) with ESMTP id 55A5A8880; Fri, 8 Apr 2005 13:15:35 +0200 (CEST)
Subject: Re: [v6tc] Re: Tunneling and Transition Drafts
From: Jeroen Massar <jeroen@unfix.org>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <Pine.LNX.4.61.0504081311420.2531@netcore.fi>
References: <200504071854.j37IseAs006430@rotala.raleigh.ibm.com> <4256390A.5000808@renater.fr> <Pine.LNX.4.61.0504081311420.2531@netcore.fi>
Organization: Unfix
Date: Fri, 08 Apr 2005 13:15:32 +0200
Message-Id: <1112958932.26936.37.camel@firenze.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.1.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: "v6tc@ietf.org" <v6tc@ietf.org>, Jerome Durand <jdurand@renater.fr>
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>
Content-Type: multipart/mixed; boundary="===============0656075092=="
Sender: v6tc-bounces@ietf.org
Errors-To: v6tc-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab

On Fri, 2005-04-08 at 13:12 +0300, Pekka Savola wrote:
> On Fri, 8 Apr 2005, Jerome Durand wrote:
> > The point here is that as an ISP, I'd prefer to work with a standard, 
> > manageable and available solution. Is one already available? If yes that is 
> > worth documenting how to use/deploy it (in v6ops WG). If not, then we have to 
> > adopt a new standard (in v6tc as v6ops is not made for it).
> 
> L2TP ?

Client for all OS's that support it doing IPv6 ?

Greets,
 Jeroen


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

v2.23.0 | Report a Bug | By Email