Re: Flooding Attacks and MIP6 (was RE: [Mipshop] Review of draft-arkko-mipshop-cga-cba-04)

Vijay Devarapalli <vijay.devarapalli@azairenet.com> Mon, 14 August 2006 23:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCm8c-0002zc-En; Mon, 14 Aug 2006 19:46:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GCm8b-0002xG-Qs for mipshop@ietf.org; Mon, 14 Aug 2006 19:46:29 -0400
Received: from mail1.azairenet.com ([66.92.223.4] helo=bart.corp.azairenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GCm8a-0007hT-Hk for mipshop@ietf.org; Mon, 14 Aug 2006 19:46:29 -0400
Received: from [10.1.201.3] ([10.1.201.3]) by bart.corp.azairenet.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 14 Aug 2006 16:46:26 -0700
Message-ID: <44E10B4F.6060907@azairenet.com>
Date: Mon, 14 Aug 2006 16:46:23 -0700
From: Vijay Devarapalli <vijay.devarapalli@azairenet.com>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@kolumbus.fi>
Subject: Re: Flooding Attacks and MIP6 (was RE: [Mipshop] Review of draft-arkko-mipshop-cga-cba-04)
References: <C24CB51D5AA800449982D9BCB903251311A5E9@NAEX13.na.qualcomm.com> <44E0D802.5090307@kolumbus.fi>
In-Reply-To: <44E0D802.5090307@kolumbus.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Aug 2006 23:46:26.0780 (UTC) FILETIME=[DB8D39C0:01C6BFFB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: mipshop@ietf.org
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Errors-To: mipshop-bounces@ietf.org

Jari Arkko wrote:

>> 3. Using MIP6 home subscription to redirect traffic to the victim. Of
>> course, the risk here is that of authenticated nodes registering the
>> victim's IP address as its CoA. 

> Let me first state that if I could redesign RFC 3775 today, I would probably
> NOT include an administrative security association relationship for the
> MN - HA. This would have made deployment much easier (e.g. DHCP
> assigned home agents without any of the bootstrapping complexity).
> And it would have gotten us rid of problem #3.

we could add a return routability check for the home agent
to check if the mobile node is at the CoA it is claiming in
the BU. but AFAIK, it has not been seen as an issue so far.

regarding the "administrative security association
relationship", things are no longer so rigid (RFC 3775 ties
an SA to the home address) with the bootstrapping specs. the
mobile node can be assigned any random home agent as long as
there is a way to authenticate each other.

Vijay

_______________________________________________
Mipshop mailing list
Mipshop@ietf.org
https://www1.ietf.org/mailman/listinfo/mipshop