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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 26 January 2020 20:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 6371B120072 for <ipv6@ietfa.amsl.com>; Sun, 26 Jan 2020 12:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Y1YjX8FqaY4F for <ipv6@ietfa.amsl.com>; Sun, 26 Jan 2020 12:47:12 -0800 (PST)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0696D120052 for <ipv6@ietf.org>; Sun, 26 Jan 2020 12:47:11 -0800 (PST)
Received: by mail-pj1-x1030.google.com with SMTP id a6so2144937pjh.2 for <ipv6@ietf.org>; Sun, 26 Jan 2020 12:47:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=wF1H/Hggni5orwCBcRCcdofRHSFEhPUEPsZKLYEhWcY=; b=ZWHquYsTdh4+aDeDzRI/w8TGDYQwIX/lOp6IA5J5kcVswNXG94bFqWebU5FKvrM37w ptdsKbOIOm58Y+A4DYEuqDUAFOBGL/QBYhbRn3biX9a2UGZmMAy3bxYOtk+apFssPhL5 3NI1YCHfCYexZlwzM2RQzmFtJlDhi9QF91KqeI2YQ5YGASW2gaEJSMeIsy0gauEALL4W zCGsFrbCxv2h+yYjJWwlcpcUQ4bPj20Pikp6axVCQ86ZIEeast8FBgG9ZlSQePl6WeGz xD58Jprnn7EUmbMVUNfa5KQYQZYLJf9s2HTUS9cFdTkM7x56asreVi724bCeFzsai51C TRzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=wF1H/Hggni5orwCBcRCcdofRHSFEhPUEPsZKLYEhWcY=; b=VL9cgEw8HNCD+ECs9r5e0mnZ8rHPrNA0vhl6z4g3N2j0u+yGGaF93FsCyZMHQR4b7U WqorD7pl+zkoLXX7/2QpgkzAUWEJsYWgb3kDSvlO2z4YsPoQnKWbny/jsSU0QIpmfQnH B86vxnbsi9p7u7HqUHeCOlWBbdvX0Aoah8IYKV5Rn2IQOUkRqFtS2zwfLXU/BaHJHqkj qYc/hrfBsV2U8L1yRpxs9HZg0NdVVT7sd19bY8ldCN5fo6+VuOC6DB34y7n11DzPxCDr iYS2rb3OGeqeycz1yMdWdFOqJrqoJq5XzXoxabkcQqTtxhXKNJnizYxtrsmrUEbHoXbL tbSA==
X-Gm-Message-State: APjAAAXyb5+p1chPC3p0cud9ulWJ7uxKeqqP0KqQPXU6se6U+rA58r5c cqLcVVMosKJco42KQPIpzYHBf6oJ
X-Google-Smtp-Source: APXvYqxRbObvh0XDW7KS8+YXivI6nUCFYFruuM8rAO4d9YEl6vc7VK/nm+Nkx0djiPXcd3zYFBHvNQ==
X-Received: by 2002:a17:90a:a115:: with SMTP id s21mr10729487pjp.23.1580071630803; Sun, 26 Jan 2020 12:47:10 -0800 (PST)
Received: from [192.168.178.30] (88.161.69.111.dynamic.snap.net.nz. [111.69.161.88]) by smtp.gmail.com with ESMTPSA id d14sm12976688pjz.12.2020.01.26.12.47.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Jan 2020 12:47:09 -0800 (PST)
Subject: Re: SLAAC vs DHCPv6 (Re: RFC4941bis: consequences of many addresses for the network)
To: Simon Hobson <linux@thehobsons.co.uk>, 6man WG <ipv6@ietf.org>
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> <F7F5B682-918B-4190-BEE6-A86B5CCD8530@puck.nether.net> <CABNhwV1a+o-D-YDck-Ad42DNbHfPPOfXbbCBCift-=2Jb201og@mail.gmail.com> <4ACE9ABB-C5DA-4A76-8DF9-02D6350B4E9C@thehobsons.co.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <cad6f8df-c3c8-b7d3-9f32-cebec4539594@gmail.com>
Date: Mon, 27 Jan 2020 09:47:07 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <4ACE9ABB-C5DA-4A76-8DF9-02D6350B4E9C@thehobsons.co.uk>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6V5bbkjPJ598gmT5PCaHfYkvAgY>
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 20:47:13 -0000

On 27-Jan-20 09:22, Simon Hobson wrote:
> Gyan Mishra <hayabusagsm@gmail.com> wrote:
> 
>> The beauty behind SLAAC is that it works “out of the box” PNP like features makes it very user friendly to initiatally deploy.
> 
> Remember that DHCP for IPv4 generally works "out of the box" for most users. Certainly in the SOHO market, the presence of a built in, auto-configured, and enabled DHCP server in the route means that the user just "plugs it in and it works". By the time you get to a level of network complexity where that isn't the case, then there is normally a network admin either on the staff or hired n as needed.
> 
> If that isn't working reliably for users in the IPv6 world then that suggests the various components needed haven't reached the same level of completeness & correctness "mostly" available in the IPv4 world. It isn't an argument that DHCPv6 "doesn't work".

It's actually a historical accident. At the time that SLAAC was designed, DHCP(v4) wasn't mature and the state of the art in autoconfiguration was Appletalk, Novell IPX, and DECnet Phase IV. It really doesn't matter now. We can't roll the clock back.

   Brian