Re: [v6ops] Genart last call review of draft-ietf-v6ops-slaac-renum-03

Philip Homburg <pch-v6ops-9@u-1.phicoh.com> Thu, 01 October 2020 08:53 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 771B33A0E6D for <v6ops@ietfa.amsl.com>; Thu, 1 Oct 2020 01:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 MaYcFmGKCpyH for <v6ops@ietfa.amsl.com>; Thu, 1 Oct 2020 01:53:27 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747813A0E6B for <v6ops@ietf.org>; Thu, 1 Oct 2020 01:53:25 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-CHACHA20-POLY1305) (Smail #157) id m1kNuKz-0000JoC; Thu, 1 Oct 2020 10:53:17 +0200
Message-Id: <m1kNuKz-0000JoC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <159883647280.7294.15168668243468397592@ietfa.amsl.com> <3EB77F8F-C229-47CC-833D-C4B127701B10@delong.com> <m1kDnE7-0000MEC@stereo.hq.phicoh.net> <151D723E-D0A6-495D-B7F7-3CC25505107D@delong.com>
In-reply-to: Your message of "Wed, 30 Sep 2020 19:14:44 -0700 ." <151D723E-D0A6-495D-B7F7-3CC25505107D@delong.com>
Date: Thu, 01 Oct 2020 10:53:15 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/z_C6PALkfTR2BVVN_zorA5JlIJg>
Subject: Re: [v6ops] Genart last call review of draft-ietf-v6ops-slaac-renum-03
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, 01 Oct 2020 08:53:30 -0000

> Some routers send PIOs in RAs with a valid lifetime of 0 and some
> systems erroneously process that and invalidate said prefix. This
> violates RFC4862 and is a potential DOS vector. If you invalidate
> the prefix, you have weaponized RAs as discussed in RFC4862.

There is a proposal now in 6man to make this required host behavior.
The reasoning is that with RA-guard, this does not introduce a new attack
vector. Without RA-guard, there are already many DOS vectors, and the 
new behavior has benefits that outweigh the downside of one new vector when
there are already many.

> A deprecated valid prefix that actually should be invalid will
> cause less suffering than a non-deprecated prefix in the same
> circumstance, but the no-win situation I was describing remains.

If there is only one SLAAC prefix, then deprecating that prefix is not
an attack vector. If there are two (for example a global one and a ULA) then
deprecating is also an attack vector. However, there are plenty of other
ways to DOS hosts using RAs.