RE: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:d raft-ietf-mip6-auth-protocol-00.txt]
"Kuntal Chowdhury" <chowdury@nortelnetworks.com> Thu, 07 October 2004 15:43 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 LAA28074 for <mip6-web-archive@ietf.org>; Thu, 7 Oct 2004 11:43:25 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFaaB-0004gS-R5 for mip6-web-archive@ietf.org; Thu, 07 Oct 2004 11:53:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFaMR-0003tD-3Q; Thu, 07 Oct 2004 11:39:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFa3K-0008Hl-UR for mip6@megatron.ietf.org; Thu, 07 Oct 2004 11:19:34 -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 LAA26211 for <mip6@ietf.org>; Thu, 7 Oct 2004 11:19:32 -0400 (EDT)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFaD4-0003Wj-2v for mip6@ietf.org; Thu, 07 Oct 2004 11:29:38 -0400
Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i97FIxu12075; Thu, 7 Oct 2004 11:18:59 -0400 (EDT)
Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id <TS11HWCN>; Thu, 7 Oct 2004 11:18:59 -0400
Message-ID: <591B780D9676844E8A704B5B013FFE92032F194F@zrc2hxm1.corp.nortel.com>
From: Kuntal Chowdhury <chowdury@nortelnetworks.com>
To: Basavaraj.Patil@nokia.com, mip6@ietf.org
Subject: RE: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:d raft-ietf-mip6-auth-protocol-00.txt]
Date: Thu, 07 Oct 2004 11:18:45 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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: 02ec665d00de228c50c93ed6b5e4fc1a
I vote YES. -Kuntal >-----Original Message----- >From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On >Behalf Of Basavaraj.Patil@nokia.com >Sent: Wednesday, October 06, 2004 5:03 PM >To: mip6@ietf.org >Subject: [Mip6] Consensus Call: Standardizing the auth >protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt] > > > >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.htm l 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
- RE: [Mip6] Consensus Call: Standardizing the auth… Mohamed Khalil
- RE: [Mip6] Consensus Call: Standardizing the auth… Kuntal Chowdhury