SLAAC vs DHCPv6 (Re: RFC4941bis: consequences of many addresses for the network)

Jared Mauch <jared@puck.nether.net> Sun, 26 January 2020 13:40 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32D9B12006B for <ipv6@ietfa.amsl.com>; Sun, 26 Jan 2020 05:40:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 4wElh0ig_E4O for <ipv6@ietfa.amsl.com>; Sun, 26 Jan 2020 05:40:57 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [IPv6:2001:418:3f4::5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E494F120043 for <ipv6@ietf.org>; Sun, 26 Jan 2020 05:40:56 -0800 (PST)
Received: from [10.0.0.129] (c-68-32-79-179.hsd1.mi.comcast.net [68.32.79.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id A331454024E; Sun, 26 Jan 2020 08:40:54 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\))
Subject: SLAAC vs DHCPv6 (Re: RFC4941bis: consequences of many addresses for the network)
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <d607cc77-0a98-8319-9f0e-3f8d4a86e6c2@si6networks.com>
Date: Sun, 26 Jan 2020 08:40:54 -0500
Cc: Tim Chown <Tim.Chown@jisc.ac.uk>, 6man WG <ipv6@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7F5B682-918B-4190-BEE6-A86B5CCD8530@puck.nether.net>
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <MN2PR11MB3565330989D411525D30B90DD80F0@MN2PR11MB3565.namprd11.prod.outlook.com> <80207E17-AE8E-4D19-B516-D2E6AB70721E@employees.org> <8D5610EA-49D3-483E-BB7A-67D67BC89346@jisc.ac.uk> <DE7B0688-230F-4A5C-8E24-9EAED9FD9FEB@puck.nether.net> <d607cc77-0a98-8319-9f0e-3f8d4a86e6c2@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3608.40.2.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/J9BwpnPl_-yeRicKmb3dX0-O51s>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2020 13:40:58 -0000


> On Jan 23, 2020, at 9:08 AM, Fernando Gont <fgont@si6networks.com> wrote:
> 
> * DHCPv6 support is not required, and in fact we seem to do our best to
>  trash DHCPv6 and borrow cool DHCPv6 features into slaac as much as
>  possible -- which doesn't help the situation.

This for me is an example of one of the problems around IPv6.

The IPv6 solution space includes things like:

* Don’t do DHCPv6, do SLAAC
** We forgot to include DNS, so RDNSS
* Do DHCPv6, don’t do SLAAC
** Some hosts won’t do DHCPv6
** Not all hardware does DHCPv6-PD properly
** Not all software does DHCPv6-PD properly
** Not all networks can support DHCPv6-PD

The general discussion for me here is we need to ensure we’re not violating rfc1925[1] 2.1 which at times seems to be blame shifted to operators or vendors.  While everyone has their weaknesses we need to ensure the ecosystem we specify is robust enough.

- Jared

[1] - Yes I know, doesn’t make it any less true though.