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

Hi,

As I am afraid of the consequences to have 2 different solutions to solve
the same problem (management from the operator and the client point of view,
cost to implement them), I prefer to vote :

    Yes	     [ ]
    No	     [X]

Regards.

JMC.

France Telecom - R&D Division - MAPS/NSS   
Jean-Michel COMBES, Internet/Intranet Security
E-Mail: jeanmichel.combes@francetelecom.com
Phone: +33 (0)1 45 29 45 94
Fax: +33 (0)1 45 29 65 19
Mobile: +33 (0)6 07 29 30 16 

> -----Original Message-----
> From: mip6-bounces@ietf.org [mailto:mip6-bounces@ietf.org] On 
> Behalf Of Basavaraj.Patil@nokia.com
> Sent: Thursday, October 07, 2004 12:03 AM
> 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