Re: [Mip6] WG LC (Deadline Dec 18th, 04) for I-Ds: draft-ietf-mip6-auth-protocol-01.txt anddraft-ietf-mip6-mn-ident-option-00.txt

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Thu, 30 December 2004 14: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 JAA16372 for <mip6-web-archive@ietf.org>; Thu, 30 Dec 2004 09:43:47 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck1i7-0001e6-6F for mip6-web-archive@ietf.org; Thu, 30 Dec 2004 09:55:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck1Q4-00085G-Sy; Thu, 30 Dec 2004 09:36:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck1GS-0006IM-UT for mip6@megatron.ietf.org; Thu, 30 Dec 2004 09:26:57 -0500
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 JAA15307 for <mip6@ietf.org>; Thu, 30 Dec 2004 09:26:55 -0500 (EST)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck1Ro-0001E3-58 for mip6@ietf.org; Thu, 30 Dec 2004 09:38:40 -0500
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id iBUEQIr19559; Thu, 30 Dec 2004 15:26:18 +0100
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.12.3/8.12.3) with ESMTP id iBUEQISj021173; Thu, 30 Dec 2004 15:26:18 +0100 (CET) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200412301426.iBUEQISj021173@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: alpesh <alpesh@cisco.com>
Subject: Re: [Mip6] WG LC (Deadline Dec 18th, 04) for I-Ds: draft-ietf-mip6-auth-protocol-01.txt anddraft-ietf-mip6-mn-ident-option-00.txt
In-reply-to: Your message of Tue, 21 Dec 2004 13:19:16 PST. <200412212130.BAA10441@mira-sjc5-b.cisco.com>
Date: Thu, 30 Dec 2004 15:26:18 +0100
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: mip6@ietf.org, 'Vijay Devarapalli' <vijayd@iprg.nokia.com>, Basavaraj.Patil@nokia.com
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: 93238566e09e6e262849b4f805833007

 In your previous mail you wrote:

   The specific case is described in an appendix (B in the version you have).
   It is
   In appendix A (in version that will be submitted shortly).
   
=> appendixes are not "normative" so there is still a formal issue.
I am reading the new (02) version:
 - MN-HA has the anti-replay in its SA, even there is no detail I believe
   there will no problem with not totally stupid implementations.
 - MN-AAA has still the problem and in 5.2.1.1 no anti-replay stuff is
   sent to the AAA server. BTW there is no reference to the AAA application
   used in 5.2.1.1 so one can infer from the whole draft that the message
   identification option is highly recommended with MN-AAA.
   As it is not the case the text should be improved...

Regards

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6