[Mip6] [issue41] Ted Hardie's comment

Basavaraj Patil <tracker-mip6@mip4.org> Fri, 09 September 2005 20:20 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDpMg-0001md-Vk; Fri, 09 Sep 2005 16:20:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EDpMf-0001mN-E1 for mip6@megatron.ietf.org; Fri, 09 Sep 2005 16:20:49 -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 QAA06238 for <mip6@ietf.org>; Fri, 9 Sep 2005 16:20:46 -0400 (EDT)
Received: from av8-1-sn3.vrr.skanova.net ([81.228.9.183]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EDpQG-0008Ej-DT for mip6@ietf.org; Fri, 09 Sep 2005 16:24:34 -0400
Received: by av8-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 838FE37EE7; Fri, 9 Sep 2005 22:20:36 +0200 (CEST)
Received: from smtp3-2-sn3.vrr.skanova.net (smtp3-2-sn3.vrr.skanova.net [81.228.9.102]) by av8-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 45C4F37ED2 for <mip6@ietf.org>; Fri, 9 Sep 2005 22:20:36 +0200 (CEST)
Received: from shiraz.levkowetz.com (81-224-201-50-no45.tbcn.telia.com [81.224.201.50]) by smtp3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 2E31937E46 for <mip6@ietf.org>; Fri, 9 Sep 2005 22:20:36 +0200 (CEST)
Received: from shiraz.local.levkowetz.com ([192.168.3.14] helo=81-224-201-50-no45.tbcn.telia.com) by shiraz.levkowetz.com with esmtp (Exim 4.52) id 1EDpMQ-0001kV-W6 for mip6@ietf.org; Fri, 09 Sep 2005 22:20:36 +0200
Content-Type: text/plain; charset="utf-8"
To: mip6@ietf.org
From: Basavaraj Patil <tracker-mip6@mip4.org>
Date: Fri, 09 Sep 2005 20:20:34 +0000
MIME-Version: 1.0
Message-Id: <1126297234.44.0.877798908506.issue41@mip4.org>
X-Roundup-Name: Mip6 issue tracker
X-Roundup-Loop: hello
Content-Transfer-Encoding: quoted-printable
X-Helo-Check-Failed: Verification failed for HELO 81-224-201-50-no45.tbcn.telia.com
X-SA-Exim-Connect-IP: 192.168.3.14
X-SA-Exim-Mail-From: roundup-admin@mip4.org
X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on shiraz.levkowetz.com
X-Spam-Status: No, score=-103.8 required=2.5 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST,X_HELO_CHECK_FAILED autolearn=ham version=3.0.4
X-SA-Exim-Version: 4.2 (built Thu, 03 Mar 2005 10:44:12 +0100)
X-SA-Exim-Scanned: Yes (on shiraz.levkowetz.com)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable
Subject: [Mip6] [issue41] Ted Hardie's comment
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mip6 issue tracker <tracker-mip6@mip4.org>
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

New submission from Basavaraj Patil <basavaraj.patil@nokia.com>:

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