Re: [v6ops] Implementation Status of PREF64

Gert Doering <gert@space.net> Tue, 28 September 2021 20:28 UTC

Return-Path: <gert@space.net>
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 424463A1078 for <v6ops@ietfa.amsl.com>; Tue, 28 Sep 2021 13:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (2048-bit key) header.d=space.net
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 o7VnL3q6e1aQ for <v6ops@ietfa.amsl.com>; Tue, 28 Sep 2021 13:28:51 -0700 (PDT)
Received: from gatekeeper1-relay.space.net (gatekeeper1-relay.space.net [IPv6:2001:608:3:85::38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5D133A107E for <v6ops@ietf.org>; Tue, 28 Sep 2021 13:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=space.net; i=@space.net; q=dns/txt; s=esa; t=1632860931; x=1664396931; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=1WJdbjg0TQ0lGq1DCjVOIjwquFwA+YEUnK6DCsGGtWE=; b=IFA4yT7jNj0H+dzPF59PkjvM6G1cN8U2omcLSsv8jQz2tIv8Vi8rB7OB PWwxuGQsRjw/xDvXOZF78pL5TUaCEVQOhsO+UEXTs2SfSbb0XeLV32cw4 OPrJK73QS/Y1ue7Tkj+qIq6viYzaMMCIpTKdso6s7R2WrSrJzhU0ocqX8 vYRaJQrIL9wGMiCXONDN2ZAx79jmwU+vnaUit1FzThPRCnhdJR4KeoEVQ i0H+eTjVnq6UNwDUtxU5UlhgTdeb1Z/Gllwkm31/13QYkQZjPWzbuLe3/ wEeADwk5deI8EktVkNFpyeeHPmq8v6a60t90gbgfSViLndH3gDNlO2BkA Q==;
X-SpaceNet-SBRS: None
Received: from mobil.space.net ([195.30.115.67]) by gatekeeper1-relay.space.net with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Sep 2021 22:28:46 +0200
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 56C4A41264 for <v6ops@ietf.org>; Tue, 28 Sep 2021 22:28:46 +0200 (CEST)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id E12EF40AD6; Tue, 28 Sep 2021 22:28:45 +0200 (CEST)
Received: by moebius4.space.net (Postfix, from userid 1007) id DA6B010FB59; Tue, 28 Sep 2021 22:28:45 +0200 (CEST)
Date: Tue, 28 Sep 2021 22:28:45 +0200
From: Gert Doering <gert@space.net>
To: Philip Homburg <pch-v6ops-10@u-1.phicoh.com>
Cc: v6ops@ietf.org
Message-ID: <YVN6/cA6Ob3vLJQH@Space.Net>
References: <DDA36020-90CC-471B-83AD-3D98950F1164@delong.com> <CAO42Z2wdoSdJDOB2Zo0=ZK0ecOARRsdg2nbHZGSDOhryPbLfDw@mail.gmail.com> <F2BD0A42-E9AD-45DD-999A-638E73BE1177@delong.com> <CAKD1Yr2K3Gd3JD=NJFOoH6GYgs-8ACxRQB9-sKJ7cbF4_hxsow@mail.gmail.com> <0B533C71-5DB0-410D-A5A3-7E8FD559F214@delong.com> <CAKD1Yr3NoYfNT7+OVJoCCdgdif6AHHw29tNCPttS=-NuRZKv3w@mail.gmail.com> <5FAD5290-3616-4194-B783-D473DB38A89A@delong.com> <m1mVGC6-0000HSC@stereo.hq.phicoh.net> <D6620D7C-8FE8-4294-8014-AB18A230C9C7@delong.com> <m1mVItl-0000GuC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <m1mVItl-0000GuC@stereo.hq.phicoh.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/s6tH07z2T9tf0FAWLNhb0eD0wUU>
Subject: Re: [v6ops] Implementation Status of PREF64
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: Tue, 28 Sep 2021 20:28:57 -0000

Hi,

On Tue, Sep 28, 2021 at 09:36:16PM +0200, Philip Homburg wrote:
> > With SLAAC, you can begin advertising an additional prefix right
> > now.
> > 
> > You cant get rid of the old one so fast, you have to wait for the
> > timers to expire.
> 
> Indeed I was sloppy. In addition to adding a prefix right now, you can 
> also deprecate the old prefix without waiting for timers to expire.
> 
> The net effect is that new flows use the new prefix right away, but the old
> prefix can be used for 2 hours longer. So timers are limited to 2 hours.

Indeed, this can be done with SLAAC.

But - the folks asking for proper DHCPv6 support in Android are not
deploying SoHo networks where ISPs tend to change prefixes every now
and then, but managed enterprise networks.  Prefixes change when the
admin says so, and they know how to deal with DHCP lease timers, 
change prefixes at times when nobody is at work, and so on.

So the standard argument from the "DHCPv6 sucks, because!" camp is
really totally ignoring reality.

(Now: supporting a DHCPv6 *server* on an Android device running as
mobile hotspot with frequently changing uplink connectivity - here I
totally agree that DHCPv6 is not the right tool for such a network
setup.  But nobody is asking for it, and refusing DHCPv6 client support
because DHCPv6 server support on the same device is not a useful
thing sounds a bit... "painted myself into a corner" -ish)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279