RE: [Mip6] Consensus Call: Standardizing the auth protocol[I-D:draft-ietf-mip6-auth-protocol-00.txt]
"Jahanzeb Faizan" <jfaizan@smu.edu> Thu, 07 October 2004 19:16 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 PAA13587 for <mip6-web-archive@ietf.org>; Thu, 7 Oct 2004 15:16:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFdty-0003YW-3F for mip6-web-archive@ietf.org; Thu, 07 Oct 2004 15:26:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFdXx-0006fU-NO; Thu, 07 Oct 2004 15:03:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CFdUx-0003dT-6K for mip6@megatron.ietf.org; Thu, 07 Oct 2004 15:00:19 -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 PAA11479 for <mip6@ietf.org>; Thu, 7 Oct 2004 15:00:17 -0400 (EDT)
Received: from email.seas.smu.edu ([129.119.113.35]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CFdeh-0002Qe-2b for mip6@ietf.org; Thu, 07 Oct 2004 15:10:24 -0400
Received: from sic300dpc1 (sic-300d-pc1.seas.smu.edu [129.119.101.37]) by email.engr.smu.edu (Postfix) with ESMTP id 411F426B76; Thu, 7 Oct 2004 14:00:11 -0500 (CDT)
From: Jahanzeb Faizan <jfaizan@smu.edu>
To: Basavaraj.Patil@nokia.com, mip6@ietf.org
Subject: RE: [Mip6] Consensus Call: Standardizing the auth protocol[I-D:draft-ietf-mip6-auth-protocol-00.txt]
Date: Thu, 07 Oct 2004 14:00:11 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Thread-Index: AcSr8DqS6Ympo/12TUmUacaxgh/VgAAnuH5AAAQn+LA=
In-Reply-To: <7892795E1A87F04CADFCCF41FADD00FC2BFC19@xmb-ams-337.emea.cisco.com>
Message-Id: <20041007190011.411F426B76@email.engr.smu.edu>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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: f60d0f7806b0c40781eee6b9cd0b2135
Content-Transfer-Encoding: 7bit
I vote YES. Jahanzeb Faizan > -----Original Message----- > From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On Behalf Of > Basavaraj.Patil@nokia.com > Sent: jeudi 7 octobre 2004 00:03 > 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.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 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