Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Owen DeLong <owen@delong.com> Thu, 31 October 2019 23:18 UTC

Return-Path: <owen@delong.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 553AA12086F for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2019 16:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=delong.com
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 boAwbRBKTHWd for <v6ops@ietfa.amsl.com>; Thu, 31 Oct 2019 16:17:57 -0700 (PDT)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id B840412026E for <v6ops@ietf.org>; Thu, 31 Oct 2019 16:17:57 -0700 (PDT)
Received: from [199.187.216.130] ([199.187.216.130]) (authenticated bits=0) by owen.delong.com (8.15.2/8.15.2) with ESMTPSA id x9VJsmgM029622 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 31 Oct 2019 12:54:48 -0700
DKIM-Filter: OpenDKIM Filter v2.11.0 owen.delong.com x9VJsmgM029622
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delong.com; s=mail; t=1572551689; bh=ioaUTNQL7UgFlcxN0J6WNb59gPrqvur7We87rsCrPzw=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=SbdbZm00W1FnVRAGumw3dqhAZi6wCdweTJqtYQDRNbhd+ZQnIl3IFmfoHvGaHddgH PY9Dwef/3ghM9Nh6IWPhBCOJWtqFOvyIMQTQEAVzIRdS2nUggmv9FWJ+ECa3V10qIv 8csNHmcfqqVlP9tN/QPiwBShx1Jm/Umd+SkPwuJ8=
From: Owen DeLong <owen@delong.com>
Message-Id: <8ACF5015-B390-4722-801C-B49E8F80E1C4@delong.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E7484BCD-E5A5-44AB-AEC8-03451C724F5C"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Thu, 31 Oct 2019 12:54:47 -0700
In-Reply-To: <D07DEFDF-1442-4793-AF21-E75D8D0D616A@fugue.com>
Cc: Fernando Gont <fgont@si6networks.com>, v6ops@ietf.org
To: Ted Lemon <mellon@fugue.com>
References: <CAO42Z2yQ_6PT3nQrXGD-mKO1bjsW6V3jZ_2kNGC2x586EMiNZg@mail.gmail.com> <B53CE471-C6E8-4DC1-8A72-C6E23154544F@fugue.com> <m1iOk6q-0000IyC@stereo.hq.phicoh.net> <855496CB-BF7E-41E6-B273-41C4AA771E41@fugue.com> <5e0d1da1-4933-069c-68f6-9aa360106582@si6networks.com> <D07DEFDF-1442-4793-AF21-E75D8D0D616A@fugue.com>
X-Mailer: Apple Mail (2.3445.104.8)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (owen.delong.com [192.159.10.2]); Thu, 31 Oct 2019 12:54:49 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LWjuhgxe77zhQrGmZi73vYi6a5Y>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 31 Oct 2019 23:18:11 -0000


> On Oct 31, 2019, at 12:47 PM, Ted Lemon <mellon@fugue.com> wrote:
> 
> On Oct 31, 2019, at 3:41 PM, Fernando Gont <fgont@si6networks.com <mailto:fgont@si6networks.com>> wrote:
>> As someone that has played a lot with ND-based DoS vectors, I should say
>> that you trust RAs, or you don't. If you do, all bets are off. ("sudo
>> apt-get install ipv6toolkit;man ra6" and you'll get examples of a bunch
>> of other DoS attacks that an attacker can perform).
> 
> As an end user, I don’t have this experience.   If someone is spamming my network with RAs, I can find out who and disconnect them.   A DoS attack based on massive quantities of RAs is a lot different than an attack that shuts my network off with one multicast. 

There are a variety of attacks in Fernando’s documentation which do not require large numbers of Gas.

A few multicast RAs well timed can, for example, change everyone’s default gateway for MITM games.

Another thing you often seem to miss, Ted, is that not everyone’s environment is necessarily similar to yours.

When developing I-Ds and RFCs, care must be taken to consider that the internet is an extremely diverse set of networks in an even more diverse set of environments.

Owen