Re: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]
"James Kempf" <kempf@docomolabs-usa.com> Wed, 06 October 2004 22:41 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 SAA26386 for <mip6-web-archive@ietf.org>; Wed, 6 Oct 2004 18:41:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFKdP-0000bX-8F for mip6-web-archive@ietf.org; Wed, 06 Oct 2004 18:51:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFKS3-0007lX-LA; Wed, 06 Oct 2004 18:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFKRB-0007Wp-Nc for mip6@megatron.ietf.org; Wed, 06 Oct 2004 18:39:09 -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 SAA26291 for <mip6@ietf.org>; Wed, 6 Oct 2004 18:39:05 -0400 (EDT)
Received: from key1.docomolabs-usa.com ([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFKaa-0000QM-3p for mip6@ietf.org; Wed, 06 Oct 2004 18:49:03 -0400
Message-ID: <028201c4abf5$602aa040$656115ac@dcml.docomolabsusa.com>
From: James Kempf <kempf@docomolabs-usa.com>
To: Basavaraj.Patil@nokia.com, mip6@ietf.org
References: <697DAA22C5004B4596E033803A7CEF4403B1BF01@daebe007.americas.nokia.com>
Subject: Re: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]
Date: Wed, 06 Oct 2004 15:39:36 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
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: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Lacking any Security Directorate review opinion on this, I must regrettably vote NO. I would, however, support pursuing the draft as an informational RFC for 3GPP2 use only. jak ----- Original Message ----- From: <Basavaraj.Patil@nokia.com> To: <mip6@ietf.org> Sent: Wednesday, October 06, 2004 3:02 PM 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.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
- [Mip6] Consensus Call: Standardizing the auth pro… Basavaraj.Patil
- Re: [Mip6] Consensus Call: Standardizing the auth… James Kempf
- Re: [Mip6] Consensus Call: Standardizing the auth… Erik Nordmark
- Re: [Mip6] Consensus Call: Standardizing the auth… gabriel montenegro
- Re: [Mip6] Consensus Call: Standardizing the auth… Francis Dupont
- Re: [Mip6] Consensus Call: Standardizing the auth… Alpesh
- Re: [Mip6] Consensus Call: Standardizing the auth… Charles E.Perkins
- Re: [Mip6] Consensus Call: Standardizing the auth… Jari Arkko
- RE: [Mip6] Consensus Call: Standardizing the auth… Tschofenig Hannes
- Re: [Mip6] Consensus Call: Standardizing the auth… Vijay Devarapalli
- Re: [Mip6] Consensus Call: Standardizing the auth… Gopal Dommety
- RE : [Mip6] Consensus Call: Standardizing the aut… Jean-Michel COMBES
- RE: [Mip6] Consensus Call: Standardizing the auth… AC Mahendran
- Re: [Mip6] Consensus Call: Standardizing the auth… Wing Cheong Lau
- Re: [Mip6] Consensus Call: Standardizing the auth… Brian Haley
- Re: [Mip6] Consensus Call: Standardizing the auth… Pekka Savola
- Re: [Mip6] Consensus Call: Standardizing the auth… Charles E. Perkins
- Re: [Mip6] Consensus Call: Standardizing the auth… Pekka Savola
- Re: [Mip6] Consensus Call: Standardizing the auth… Joe Lau
- Re: [Mip6] Consensus Call: Standardizing the auth… Yoshihiro Ohba
- Re: [Mip6] Consensus Call: Standardizing the auth… Mohan Parthasarathy
- Re: [Mip6] Consensus Call: Standardizing the auth… Rajeev Koodli