Re: [Mip6] MIP6 WG meeting at IETF61

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Wed, 20 October 2004 02:19 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 WAA16836 for <mip6-web-archive@ietf.org>; Tue, 19 Oct 2004 22:19:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CK6Gh-0003WQ-0i for mip6-web-archive@ietf.org; Tue, 19 Oct 2004 22:32:04 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CK4Cg-0003x2-UQ; Tue, 19 Oct 2004 20:19:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJvvx-0002e9-Uz for mip6@megatron.ietf.org; Tue, 19 Oct 2004 11:29:58 -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 LAA07155 for <mip6@ietf.org>; Tue, 19 Oct 2004 11:29:55 -0400 (EDT)
Received: from laposte.enst-bretagne.fr ([192.108.115.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJw8A-0000aL-IF for mip6@ietf.org; Tue, 19 Oct 2004 11:42:36 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id i9JFTI210552; Tue, 19 Oct 2004 17:29:18 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id i9JFTJSj086505; Tue, 19 Oct 2004 17:29:19 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200410191529.i9JFTJSj086505@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Basavaraj.Patil@nokia.com
Subject: Re: [Mip6] MIP6 WG meeting at IETF61
In-reply-to: Your message of Wed, 13 Oct 2004 10:47:00 CDT. <697DAA22C5004B4596E033803A7CEF4403B1BF5D@daebe007.americas.nokia.com>
Date: Tue, 19 Oct 2004 17:29:19 +0200
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745

 In your previous mail you wrote:
   
   If you would like a timeslot on the MIP6 WG agenda, please send
   a request to the chairs. Include in the request:
   
=> I have two requests (already presented but not discussed enough
so no decission was taken):

-------------------------------- FIRST --------------------------------

   1. Discussion Topic

=> use of IPsec to protect signaling between MN and CN

   2. Draft Name

=> draft-dupont-mipv6-cn-ipsec-01.txt

   3. Slot Duration

=> 5 minutes (1 minute presentation, 4 minutes discussion)

   4. Is this in the scope of the Charter? (if not explain the relation)

=> quoting the charter: "Mechanisms using a shared secret Key/Security
Association will be considered."

   5. What do you want to accomplish by this presentation
      (e.g resolve the following issues)

=> make the draft a WG item and/or what is missing in it.

   6. Was this draft discussed in the mailing list

=> not enough!

   7. Are there any open issues?
   
=> none (note I implemented it)

-------------------------------- SECOND --------------------------------

   1. Discussion Topic

=> care-of address test procedure using a state cookie

   2. Draft Name

=> Annex of draft-dupont-mipv6-cn-ipsec-01.txt
(note I am extracting it to make a stand-alone document, an XML version
should be available soon)

   3. Slot Duration

=> 5 minutes (3 minutes presentation, 2 minutes to find someone else
who needs it)

   4. Is this in the scope of the Charter? (if not explain the relation)

=> same argument (Mechanisms using a shared secret Key/Security
Association will be considered): these mechanisms don't provide
a built-in care-of address test.

   5. What do you want to accomplish by this presentation
      (e.g resolve the following issues)

=> find someone else (i.e., another alternative to the RR procedure)
who (which) needs it and very shortly discussed if the solution is good
or can be improved.

   6. Was this draft discussed in the mailing list

=> not enough, in particular I don't know who share my feeling
that to initiate the care-of address test by the CN is good.

   7. Are there any open issues?
   
=> IANA considerations (so a WG document status should be fine)

Regard

Francis.Dupont@enst-bretagne.fr

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