Re: [Mip6] [issue41] Ted Hardie's comment

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Sat, 10 September 2005 09:28 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE1er-0005fK-Ld; Sat, 10 Sep 2005 05:28:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE1ep-0005eI-PI for mip6@megatron.ietf.org; Sat, 10 Sep 2005 05:28:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24716 for <mip6@ietf.org>; Sat, 10 Sep 2005 05:28:05 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EE1iJ-0002G3-SG for mip6@ietf.org; Sat, 10 Sep 2005 05:32:01 -0400
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 j8A9Rc315591; Sat, 10 Sep 2005 11:27:38 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id j8A9RbMV015736; Sat, 10 Sep 2005 11:27:38 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200509100927.j8A9RbMV015736@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Charles Perkins <charles.perkins@nokia.com>
Subject: Re: [Mip6] [issue41] Ted Hardie's comment
In-reply-to: Your message of Fri, 09 Sep 2005 20:20:34 -0000. <1126297234.44.0.877798908506.issue41@mip4.org>
Date: Sat, 10 Sep 2005 11:27:37 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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

 In your previous mail Ted Hardie wrote:

=> I wrote the draft-dupont-mipv6-rrcookie-01.txt exactly as an
answer to this kind of objection. So don't hesitate to use it
and if you're afraid it can introduce too long delay (REF in
the RFC editor process) I am open to suggestion, including
co-authoring.

Regards

Francis.Dupont@enst-bretagne.fr

   I think I'm confused. The document says in the Introduction:
   
     This mechanism is also limited to use only in
     scenarios where mobile nodes can be trusted to not misbehave, as the
     validity of the claimed care-of addresses is not verified.
   
   In the applicability statement, it goes on to say:
   
     -  The correspondent node has good reason to trust the actions of
         the mobile node.  In particular, the correspondent node needs to
         be certain that the mobile node will not launch flooding attacks
         against a third party as described in [2].
   
   But the Security Considerations don't contain any details about what happens
   if this trust is misplaced.  draft-ietf-mip6-ro-sec-03 has quite a taxonomy
   of potential issues; I would have thought that a basic run-through of those
   would be useful.  Not that it needs to go through the whole document, but
   a statement about whether any existing consideration (one of the flooding
   attacks?)  are worsened by this approach or that none are would seem
   like a valuable addition.
   
   ----------
   category: Editorial
   draft: draft-ietf-mip6-precfgkbm
   messages: 141
   nosy: bpatil
   priority: Should fix
   status: Pending
   title: Ted Hardie's comment
   
   _________________________________________________
   Mip6 issue tracker <tracker-mip6@mip4.org>
   <http://www.mip4.org/issues/tracker/mip6/issue41>
   _________________________________________________
   
   _______________________________________________
   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