Re: [v6tc] v6tc Protocol Exploration
Alain Durand <Alain.Durand@Sun.COM> Fri, 17 December 2004 09: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 EAA28925;
Fri, 17 Dec 2004 04:48:39 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
by ietf-mx.ietf.org with esmtp (Exim 4.33)
id 1CfErf-0006ef-80; Fri, 17 Dec 2004 04:57:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1CfEh7-0000yA-RF; Fri, 17 Dec 2004 04:46:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1CfEaA-0008TU-D9
for v6tc@megatron.ietf.org; Fri, 17 Dec 2004 04:39:30 -0500
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 EAA28362
for <v6tc@ietf.org>; Fri, 17 Dec 2004 04:39:28 -0500 (EST)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfEik-0006RI-2G
for v6tc@ietf.org; Fri, 17 Dec 2004 04:48:24 -0500
Received: from esunmail ([129.147.156.34])
by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id iBH9dQVu020009
for <v6tc@ietf.org>; Fri, 17 Dec 2004 02:39:26 -0700 (MST)
Received: from fe7 (esunmail [129.147.156.34]) by edgemail1.Central.Sun.COM
(iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21 2004))
with ESMTP id <0I8V001YG1HPYI@edgemail1.Central.Sun.COM> for
v6tc@ietf.org; Fri, 17 Dec 2004 02:39:26 -0700 (MST)
Received: from [192.168.1.4] ([83.113.218.143])
by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 2.02 (built Oct 21
2004))
with ESMTPSA id <0I8V005ID1HNUK@mail.sun.net> for v6tc@ietf.org; Fri,
17 Dec 2004 02:39:25 -0700 (MST)
Date: Fri, 17 Dec 2004 01:39:25 -0800
From: Alain Durand <Alain.Durand@Sun.COM>
Subject: Re: [v6tc] v6tc Protocol Exploration
In-reply-to: <796972EB7CA1D55BD8D2967E@[192.168.31.2]>
To: Florent Parent <Florent.Parent@hexago.com>
Message-id: <89CDF53C-500F-11D9-81E4-00039358A080@sun.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
References: <796972EB7CA1D55BD8D2967E@[192.168.31.2]>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7BIT
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: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7BIT
Thank you Florent for sending this, it will help framing the next discussion. Back to a message I sent a while ago, some of the key issues we need to discuss are: Issue 1: - Could we live with UDP encapsulation always on? Issue 2: - Do we need mutual authentication? How strong should this be? Issue 3: Should some of this authentication mechanism "follow-on" atfer the tunnel set-up phase as finished? Issue 4: - Should we embed some kind of signaling in the tunnel? I will start email threads for each one of them. Please fell free to add other issues to this list. ps: I'll ask our ADs to be if we can use some of the issue tracker tools to help here. - Alain. _______________________________________________ v6tc mailing list v6tc@ietf.org https://www1.ietf.org/mailman/listinfo/v6tc
- [v6tc] v6tc Protocol Exploration Florent Parent
- Re: [v6tc] v6tc Protocol Exploration Alain Durand