IETF Logo Mail Archive

RE: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]

juha.wiljakka@nokia.com Fri, 08 October 2004 07:02 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 DAA29043 for <mip6-web-archive@ietf.org>; Fri, 8 Oct 2004 03:02:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFovY-000837-6K for mip6-web-archive@ietf.org; Fri, 08 Oct 2004 03:12:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFoe7-0003fy-Ri; Fri, 08 Oct 2004 02:54:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFodE-0003UH-2g for mip6@megatron.ietf.org; Fri, 08 Oct 2004 02:53:36 -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 CAA28715 for <mip6@ietf.org>; Fri, 8 Oct 2004 02:53:34 -0400 (EDT)
From: juha.wiljakka@nokia.com
Received: from mgw-x4.nokia.com ([131.228.20.27]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFon4-0007uw-H6 for mip6@ietf.org; Fri, 08 Oct 2004 03:03:47 -0400
Received: from esdks004.ntc.nokia.com (esdks004.ntc.nokia.com [172.21.138.159]) by mgw-x4.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i986rVW15594 for <mip6@ietf.org>; Fri, 8 Oct 2004 09:53:32 +0300 (EET DST)
X-Scanned: Fri, 8 Oct 2004 09:52:31 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE
Received: (from root@localhost) by esdks004.ntc.nokia.com (8.12.9/8.12.9) id i986qVim012475 for <mip6@ietf.org>; Fri, 8 Oct 2004 09:52:31 +0300
Received: from mgw-int1.ntc.nokia.com (172.21.143.96) by esdks004.ntc.nokia.com 00r0Dvvq; Fri, 08 Oct 2004 09:52:29 EEST
Received: from esebh002.NOE.Nokia.com (esebh002.ntc.nokia.com [172.21.138.77]) by mgw-int1.ntc.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i986qMY03249 for <mip6@ietf.org>; Fri, 8 Oct 2004 09:52:23 +0300 (EET DST)
Received: from esebe005.NOE.Nokia.com ([172.21.138.45]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 8 Oct 2004 09:52:17 +0300
Received: from esebe054.NOE.Nokia.com ([172.21.143.44]) by esebe005.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 8 Oct 2004 09:52:16 +0300
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]
Date: Fri, 08 Oct 2004 09:52:16 +0300
Message-ID: <4255703385E781428653E1DEE230980D51B58E@esebe054.ntc.nokia.com>
Thread-Topic: Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]
Thread-Index: AcSr8DqS6Ympo/12TUmUacaxgh/VgABErRYQ
To: mip6@ietf.org
X-OriginalArrivalTime: 08 Oct 2004 06:52:16.0398 (UTC) FILETIME=[59108AE0:01C4AD03]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: quoted-printable
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.3 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable

Hi,

My vote is:

1. Should we standardize the authentication protocol specified in I-D
   draft-ietf-mip6-auth-protocol-00.txt as an alternative (to the
   IPSec mechanism specified in RFC3775/6) means to securing the BUs
   and BAcks between the MN and HA. Note that this solution is an
   additional mechanism for doing registration with an HA and does not
   deprecate the currently specified solution. 

   Yes	     [X]
   No	     [ ]

BR,
	Juha Wiljakka
 
-----Original Message-----
From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org]On Behalf Of
ext Basavaraj.Patil@nokia.com

This is a consensus call to the WG on the issue of standardizing the
authentication-data-suboption mechanism for performing a binding between the
MN and HA. The issue has been discussed on the WG mailing list over
the last few weeks. The I-D
(draft-patil-mip6-whyauthdataoption-00.txt) has captured some of the
arguments, but there are several others that have been made on the
list as well. A summary of the discussion was sent out earlier and is
captured in :
http://www1.ietf.org/mail-archive/web/mip6/current/msg01690.html

The proposal here (in brief) is to standardize a mechanism specified
in I-D draft-ietf-mip6-auth-protocol-00.txt for performing MIP6
registration with a home agent. RFC3775 specifies the use of IPsec to
secure the binding update/ACK messages between the MN and HA. The
auth-protocol mechanism relies on the use of an
authentication-data-suboption and does not require the MN-HA to
establish an IPsec SA.  
(For the discussion that has ensued so far, please refer to the MIP6
ML archives)

The question to the WG is:

1. Should we standardize the authentication protocol specified in I-D
   draft-ietf-mip6-auth-protocol-00.txt as an alternative (to the
   IPSec mechanism specified in RFC3775/6) means to securing the BUs
   and BAcks between the MN and HA. Note that this solution is an
   additional mechanism for doing registration with an HA and does not
   deprecate the currently specified solution. 

   Yes	     [ ]
   No	     [ ]


The consensus call will close on October 12th, 2004.

-Chairs

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

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

v2.23.0 | Report a Bug | By Email