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

Ole Troan <otroan@employees.org> Mon, 28 October 2019 09:58 UTC

Return-Path: <otroan@employees.org>
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 ED113120071 for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2019 02:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 JjbNh931zHPB for <v6ops@ietfa.amsl.com>; Mon, 28 Oct 2019 02:58:35 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 764E6120018 for <v6ops@ietf.org>; Mon, 28 Oct 2019 02:58:35 -0700 (PDT)
Received: from astfgl.hanazo.no (246.51-175-81.customer.lyse.net [51.175.81.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id A06AF4E11B18; Mon, 28 Oct 2019 09:58:32 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 09D1A2038ED8; Mon, 28 Oct 2019 10:58:30 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3594.4.19\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <m1iP1fa-0000GYC@stereo.hq.phicoh.net>
Date: Mon, 28 Oct 2019 10:58:29 +0100
Cc: v6ops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E99599F-0A56-4A53-AD7C-499BC87AA7D3@employees.org>
References: <m1iOinq-0000J3C@stereo.hq.phicoh.net> <44F39DE2-E142-4ED0-853E-2F3AAC6F4ADE@employees.org> <m1iOnqN-0000EpC@stereo.hq.phicoh.net> <ADCF08FD-1366-4CCB-984E-695D8E2AC2F8@employees.org> <m1iP0kt-0000GkC@stereo.hq.phicoh.net> <21E28E8F-8E91-47D6-8337-9FF0359D67B8@employees.org> <m1iP1fa-0000GYC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3594.4.19)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/IrxI_QdDrB7JUiqhlkL27AOZDaM>
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: Mon, 28 Oct 2019 09:58:37 -0000

Philip,

>> I didn't see your answer to:  "I dont know of a single server which
>> operates that way currently. Can you point to a working example?"
>> 
>> I take it the answer is: "currently none"?
> 
> Is the question whether people are running services on home networks where
> the ISP uses flash renumbering?
> 
> If so, the answer is yes. There are a number of 'dynamic DNS' providers.
> People use those to keep DNS up-to-date when their public IPv4 address changes.
> 
> All of this is small scale hobbyist usage (and most likely only IPv4) but
> it does exist.

No, the question is if there is any host stack + server software that deals with flash renumbering deployed.
And that is deployable without coding.

It's the same question Owen posed for the ISP side, when challenged with how DHCP behaves.
The point here is that we as the IETF must also consider the end-user here. Not that I don't think ISPs do that too, but so far this debate has largely been on the premise of the opertor with little concern of the consequences for the user.

Cheers,
Ole