Re: draft-gont-6man-slaac-renum

Fernando Gont <fgont@si6networks.com> Wed, 08 April 2020 21:02 UTC

Return-Path: <fgont@si6networks.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 D89613A1031 for <ipv6@ietfa.amsl.com>; Wed, 8 Apr 2020 14:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 4PwgLq-vsO3D for <ipv6@ietfa.amsl.com>; Wed, 8 Apr 2020 14:02:03 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E0653A1030 for <6man@ietf.org>; Wed, 8 Apr 2020 14:02:01 -0700 (PDT)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 3E789801CC; Wed, 8 Apr 2020 23:01:57 +0200 (CEST)
Subject: Re: draft-gont-6man-slaac-renum
From: Fernando Gont <fgont@si6networks.com>
To: otroan@employees.org, Ted Lemon <mellon@fugue.com>
Cc: "6man@ietf.org" <6man@ietf.org>
References: <E65F7C97-0188-4BF9-98C7-F2924CDE0EC5@employees.org> <91E3C450-57C9-4809-B4F3-B6210F27E09C@fugue.com> <B80BE229-21B6-4589-8B94-F8B66367615F@employees.org> <737b84c7-cb63-52ef-ae91-a8190804b5c6@si6networks.com>
Message-ID: <1a9df9c9-3fd2-8c4b-caf4-afaffc5cfd3a@si6networks.com>
Date: Wed, 08 Apr 2020 18:01:52 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <737b84c7-cb63-52ef-ae91-a8190804b5c6@si6networks.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/J_-_DCG-LWHRiIe8bwIX0CVu6fA>
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: Wed, 08 Apr 2020 21:02:05 -0000

On 8/4/20 17:57, Fernando Gont wrote:
> On 8/4/20 17:46, otroan@employees.org wrote:
>>>> Sorry, I don't see the gap.
>>>> All deployments I am aware of use the remote-id / option-82 
>>>> equivalent option to identify subscribers.
>>>> Most operators are a lot more clueful about this than us here.
>>>>
>>>> Think of PD as a contract. The ISP promises to lease the prefix to 
>>>> the subscriber for the time stated.
>>>> The ISP can still do flash renumbering (although that's likely to 
>>>> induce a customer call) in two ways.
>>>> One, just ignore it's earlier promise and give the subscriber a new 
>>>> prefix (which introduces all the problems Fernado wants to use 
>>>> prefix lifetimes to solve), or it can include the old prefix with 
>>>> lifetimes 0 (violating it's earlier promise, but at least being 
>>>> explicit) and advertise a new prefix.
>>>
>>> I’m trying to figure out why this is such an utterly unsatisfying 
>>> response.  Yes, I get that in the ideal case, which is what you are 
>>> describing here, there is no problem.  But you are missing _all_ of 
>>> the edge cases.  And you’re assuming that things on a home network 
>>> are a lot cleaner than I think is safe to assume.
>>>
>>> So yes, in the case you describe, where everything is done correctly, 
>>> there is no problem.  I would not expect to see the persistent prefix 
>>> problem routinely.  But I think it’s worth designing for—there are a 
>>> lot of reasons why renumbering might happen in a way that is not as 
>>> clean as you’re saying it should be, and we ought to handle it 
>>> gracefully when it happens.
>>
>> s/ideal/typical/
>>
>> This small problem has a couple of simple solutions:
>>   - change to an ISP that operate better
> 
> Seriously? Please think twice. (Hint: in many countries there's only one 
> ISP -- welcome to the real world).

To add to that, in many countries, as soon as you get away from major 
cities, the same is true.

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492