Re: [v6ops] DoS attacks (ICMPv6-based) resulting from IPv6 EH drops

Tore Anderson <tore@fud.no> Sat, 23 August 2014 07:48 UTC

Return-Path: <tore@fud.no>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB0E01A8719; Sat, 23 Aug 2014 00:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.868
X-Spam-Level:
X-Spam-Status: No, score=-0.868 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.668] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxFci4YwJN0R; Sat, 23 Aug 2014 00:48:49 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83EDF1A871A; Sat, 23 Aug 2014 00:48:49 -0700 (PDT)
Received: from [2a02:fe0:c411:a000::2] (port=60332 helo=envy.fud.no) by greed.fud.no with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tore@fud.no>) id 1XL643-0002OX-9d; Sat, 23 Aug 2014 09:48:43 +0200
Message-ID: <53F8475A.1090800@fud.no>
Date: Sat, 23 Aug 2014 09:48:42 +0200
From: Tore Anderson <tore@fud.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0
MIME-Version: 1.0
To: 神明達哉 <jinmei@wide.ad.jp>, Fernando Gont <fgont@si6networks.com>
References: <53F33C4F.2070807@si6networks.com> <CAJE_bqfb+v9p-PO8-7xzuYx3rs6Lpvob-Zh8ummgUEqsy764Tg@mail.gmail.com> <53F3931F.9050601@si6networks.com> <CAJE_bqeJBBghP=qXcYUOqQwTPky0uqoog=ifu0pqGi0zycu8kw@mail.gmail.com> <53F51269.8070506@si6networks.com> <CAJE_bqfgp-dpGnPFGKqYNGQK_TszZ8656AJbnQihenks=t9d1w@mail.gmail.com> <53F590A2.2090101@si6networks.com> <CAJE_bqdrN6K3z2JzYH2ArHdrTERfSS+UYDH-YO=sPKpp0K-tDA@mail.gmail.com>
In-Reply-To: <CAJE_bqdrN6K3z2JzYH2ArHdrTERfSS+UYDH-YO=sPKpp0K-tDA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/-GHxzGHy-t6Uf_zSrAAEuFKlEe0
Cc: IPv6 Operations <v6ops@ietf.org>, "opsec@ietf.org" <opsec@ietf.org>
Subject: Re: [v6ops] DoS attacks (ICMPv6-based) resulting from IPv6 EH drops
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Aug 2014 07:48:51 -0000

Hello 神明達哉,

> I assumed that stateless translation always uses the well-known
> prefix.  Maybe I was incorrect about that?

Yes, that is incorrect. Per RFC 6052 the operator can use either the
Well-Known Prefix and a Network-Specific Prefix. There are quite few
reasons why one would choose the latter; for example it allows for the
translating device to be reached across the public internet. Another
reason is that only a single WKP exists, so if the operator wants to
deploy both SIIT and NAT64, and/or multiple instances of either
technology, all of his deployments (except for one), must necessarily
use an NSP.

Tore