RE: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]
"Navali, Jay" <jnavali@starentnetworks.com> Thu, 07 October 2004 18:58 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 OAA11254 for <mip6-web-archive@ietf.org>; Thu, 7 Oct 2004 14:58:24 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFdct-0002Dq-V8 for mip6-web-archive@ietf.org; Thu, 07 Oct 2004 15:08:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFdDk-0006Ca-RU; Thu, 07 Oct 2004 14:42:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFct2-00019i-0T for mip6@megatron.ietf.org; Thu, 07 Oct 2004 14:21:08 -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 OAA08625 for <mip6@ietf.org>; Thu, 7 Oct 2004 14:21:01 -0400 (EDT)
Received: from ns.starentnetworks.com ([12.38.223.195] helo=starentnetworks.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CFcax-0004y4-Hc for mip6@ietf.org; Thu, 07 Oct 2004 14:02:28 -0400
Received: (qmail 5601 invoked from network); 7 Oct 2004 17:40:06 -0000
Received: from ames.starentnetworks.com (12.33.235.15) by mail.starentnetworks.com with SMTP; 7 Oct 2004 17:40:06 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
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: Thu, 07 Oct 2004 13:50:56 -0400
Message-ID: <8A16DAD84432534FBFC19FD92B50512F0D3049@ames.starentnetworks.com>
Thread-Topic: RE: [Mip6] Consensus Call: Standardizing the auth protocol [I-D:draft-ietf-mip6-auth-protocol-00.txt]
Thread-Index: AcSsljJCPexuDnVqSB6Zv2Uocmv22w==
From: "Navali, Jay" <jnavali@starentnetworks.com>
To: Basavaraj.Patil@nokia.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Thu, 07 Oct 2004 14:42:25 -0400
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: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable
Hi, I vote YES to standardize the draft-ietf-mip6-auth-protocol-00.txt. Thanks, Jay Navali Starent Networks >-----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… Pascal Thubert (pthubert)
- RE: [Mip6] Consensus Call: Standardizing the auth… Hirschman, Brent B [NTK]
- RE: [Mip6] Consensus Call: Standardizing the auth… Lipford, Mark A [NTK]
- RE: [Mip6] Consensus Call: Standardizing the auth… Navali, Jay
- RE: [Mip6] Consensus Call: Standardizing the auth… Jahanzeb Faizan
- RE: [Mip6] Consensus Call: Standardizing the auth… Soliman, Hesham
- RE: [Mip6] Consensus Call: Standardizing the auth… juha.wiljakka
- RE: [Mip6] Consensus Call: Standardizing the auth… Mika.Joutsenvirta
- RE: [Mip6] Consensus Call: Standardizing the auth… Franck.Le
- RE: [Mip6] Consensus Call: Standardizing the auth… Markku.Ala-Vannesluoma
- Re: [Mip6] Consensus Call: Standardizing the auth… Alexandru Petrescu
- RE: [Mip6] Consensus Call: Standardizing the auth… Manning, Serge M [NTK]
- FW: [Mip6] Consensus Call: Standardizing the auth… Basavaraj.Patil
- FW: [Mip6] Consensus Call: Standardizing the auth… Samita Chakrabarti