IETF Logo Mail Archive

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

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Mon, 20 December 2004 15:22 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 KAA06072 for <mip6-web-archive@ietf.org>; Mon, 20 Dec 2004 10:22:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgPVt-000343-8p for mip6-web-archive@ietf.org; Mon, 20 Dec 2004 10:31:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgPFs-0004dg-TQ; Mon, 20 Dec 2004 10:15:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgP9U-0001yw-Ds for mip6@megatron.ietf.org; Mon, 20 Dec 2004 10:08:48 -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 KAA04728 for <mip6@ietf.org>; Mon, 20 Dec 2004 10:08:46 -0500 (EST)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgPIl-0002gI-Dn for mip6@ietf.org; Mon, 20 Dec 2004 10:18:23 -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 iBKF89I30583; Mon, 20 Dec 2004 16:08:09 +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 iBKF88Sj081344; Mon, 20 Dec 2004 16:08:09 +0100 (CET) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200412201508.iBKF88Sj081344@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [Mip6] WG LC (Deadline Dec 18th, 04) for I-Ds: draft-ietf-mip6-auth-protocol-01.txt and draft-ietf-mip6-mn-ident-option-00.txt
In-reply-to: Your message of Tue, 14 Dec 2004 11:08:17 PST. <41BF3A21.9000102@iprg.nokia.com>
Date: Mon, 20 Dec 2004 16:08:08 +0100
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: mip6@ietf.org, 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: 2409bba43e9c8d580670fda8b695204a

 In your previous mail you wrote:

   >  - 6 message indent: anti-replay is important, IMHO at least SHOULD is
   >    required.
   
   in most cases, the sequence number in the Binding Update is
   enough for replay protection when the authentication option
   protocol is used. if in a particular deployment, (which uses
   the authentication option protocol), the sequence number is
   not sufficient, the message identification option should be
   used. that why it is a MAY in the document.
   
=> I have no concern to get the function from the "deployment
environment" but in this case the constraints for the "deployment
environment" must be explicited (currently we can only assume
that the "deployment environment" provides authentication and
authorization). Note it is possible the "deployment environment"
needs the sequence number...

Regards

Francis.Dupont@enst-bretagne.fr

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

v2.23.0 | Report a Bug | By Email