Re: [v6ops] What problem are we trying to solve? (Re: A broken promise - "You said PD Prefix Valid Lifetime is going to be X" (Re: SLAAC renum: Problem Statement & Operational workarounds))

Tassos Chatzithomaoglou <achatz@forthnet.gr> Tue, 12 November 2019 21:20 UTC

Return-Path: <achatz@forthnet.gr>
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 115401200EB for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2019 13:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forthnet.gr
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 9g-F73MVvhj8 for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2019 13:20:28 -0800 (PST)
Received: from zm-out-01.forthnet.gr (zm-out-01.forthnet.gr [194.219.0.13]) (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 1687B120019 for <v6ops@ietf.org>; Tue, 12 Nov 2019 13:20:27 -0800 (PST)
Received: from zm-in-01.cloud.forthnet.prv (zm-in-01.cloud.forthnet.prv [10.24.31.15]) by zm-out-01.forthnet.gr (Postfix) with ESMTP id 13DDB121C85; Tue, 12 Nov 2019 23:20:22 +0200 (EET)
Received: from localhost (localhost6.localdomain6 [IPv6:::1]) by zm-in-01.cloud.forthnet.prv (Postfix) with ESMTP id 053C7120831; Tue, 12 Nov 2019 23:20:22 +0200 (EET)
X-DSPAM-Result: Spam
Authentication-Results: zm-in-01.cloud.forthnet.prv (amavisd-new); dkim=pass (1024-bit key) header.d=forthnet.gr
Received: from zm-in-01.cloud.forthnet.prv ([IPv6:::1]) by localhost (zm-in-01.cloud.forthnet.prv [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 84GAs5iWmEup; Tue, 12 Nov 2019 23:20:21 +0200 (EET)
Received: from localhost (localhost6.localdomain6 [IPv6:::1]) by zm-in-01.cloud.forthnet.prv (Postfix) with ESMTP id 2BFCD12082C; Tue, 12 Nov 2019 23:20:21 +0200 (EET)
DKIM-Filter: OpenDKIM Filter v2.9.2 zm-in-01.cloud.forthnet.prv 2BFCD12082C
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forthnet.gr; s=zm; t=1573593621; bh=fm7NhFY7AWETCmxP51uacZwsncCVDtrb3Z2pSwhiheU=; h=Subject:To:From:Message-ID:Date:MIME-Version:Content-Type: Content-Transfer-Encoding; b=hLaSqMVh9Hlk2R1r+vg3ljD2RdjqdLeBy6x2tFhdHv9VZURWx3+wyefDWvIOOwj2e GVWzmZh+oD9RCUULRpySvCpoOkKxoAlumO4/YeAEHvX9D1ctDW7oZuFQOHNijTCR2m F/pTUJWdT6RulTWAvACwKcD8SS0dqPv5PdHJl4hQ=
X-Virus-Scanned: amavisd-new at zm-in-01.cloud.forthnet.prv
Received: from zm-in-01.cloud.forthnet.prv ([IPv6:::1]) by localhost (zm-in-01.cloud.forthnet.prv [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id BeZMJbxvTZWP; Tue, 12 Nov 2019 23:20:21 +0200 (EET)
Received: from [IPv6:2a02:2149:8769:2d00:602c:f317:7805:8d7e] (unknown [IPv6:2a02:2149:8769:2d00:602c:f317:7805:8d7e]) by zm-in-01.cloud.forthnet.prv (Postfix) with ESMTPA id D9FD511FE73; Tue, 12 Nov 2019 23:20:20 +0200 (EET)
To: Fernando Gont <fgont@si6networks.com>
Cc: v6ops list <v6ops@ietf.org>
References: <CAHL_VyBC3NbT4b-mnacU+ZmzyXus4HXcKx9ykdWJ3_a2uJCi4g@mail.gmail.com> <903CD569-A1A6-4BEC-A1FE-69706D04CF88@fugue.com> <CAO42Z2zWTediRkaF_pfot_QT9Hsf5Wdu9_77BQZjEEG5wY1jdQ@mail.gmail.com> <5a479b19-bf77-4c06-123f-87ed67fb5e09@si6networks.com> <CAO42Z2zTBXCA7HVBYfXsZFC91-Ac5h6m4fAvgBFPHz8xTfNZTA@mail.gmail.com> <6aca00b4-2502-0c64-cf9a-78184f32ddcc@forthnet.gr> <2c95e214-7a64-311a-e856-d5891dda260d@si6networks.com>
From: Tassos Chatzithomaoglou <achatz@forthnet.gr>
Openpgp: preference=signencrypt
Autocrypt: addr=achatz@forthnet.gr; keydata= mQENBFPWrY4BCADa9txOlMMGA1PvelU2qfkJ3cIoF+M9wXhSvZTI63FfgZAMWVM/NryJQ74q kiaWFyprgqo2BBk6vWkCw0N8pVwx0Z0sbPisB1fo/zB29cyM0HeB8lnu+Z5AvkfjwekMtGJd 3+tsRwOqdAJpCpJNhS0cVAkk1lIe3i8pdBbbKYJ5VNpBTyi0zL18WRvz9qf8nnP50rQOF8Oc LNCyKrT5S02SonWH5fQDTMVaSDVRvzRLU34pL0WEsIfTQciwg9LhjRpGj6mHxX1OdRHBpHmH WAI05lg7xRwYZq2/X/9Xizd0j9hbr6Ph7oiW7u6e4zAndvPSxXaBVCzpVI0hhaJl11yVABEB AAG0G1Rhc3NvcyA8Y2hhdGFzb3NAeWFob28uY29tPokBPwQTAQIAKQUCU9atjgIbIwUJCWYB gAcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEG9JgN4loaV7D0kIAKfyVLWFzOfYM0uT m78iJsh9nAaxYiM0t40oF+HY7Cri35FDAzrRjbB0os/KehCz6uuBqDe+3swkVX9bwE9/GsHc Tb5C1IOdvgb2Rp3MfSF1+Ju/3uGtiktQIqZ5YrIZhIjGiwUCVC6ewpC3VRiFVo/HvE23p16y 6Ws9y4xoRNuxs0952twZjT9jwVub8TWm/uES6RERZ68FGA1jVFXtAgMXljP29KcL8zRw9xiY VNI1MgUIRhOKENzpChS+7jZSDWKKD9fwPUNDNPG9kNuXoinRX1g2wlgWKmaBNVBOZMunR20P eVewZ2v35uaiHyzzHw92vjjfxOtpXoW0QFlT5cg=
Message-ID: <d01e7f5c-2415-6271-f6ac-1775f2bbf900@forthnet.gr>
Date: Tue, 12 Nov 2019 23:20:16 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.5
MIME-Version: 1.0
In-Reply-To: <2c95e214-7a64-311a-e856-d5891dda260d@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/kQkyvXHRffYR9FztEenYiTbGK8I>
Subject: Re: [v6ops] What problem are we trying to solve? (Re: A broken promise - "You said PD Prefix Valid Lifetime is going to be X" (Re: 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: Tue, 12 Nov 2019 21:20:31 -0000

Fernando Gont wrote on 12/11/19 16:33:
> On 12/11/19 04:11, Tassos Chatzithomaoglou wrote:
>
>> The subscriber should have the choice to decide and the technology should give the means to support his/her choices.
>> We're building a page inside our subscriber portal, where the subscriber chooses how frequently the LAN IPv6 assigned prefix should change.
>> Default is to change at every PPP reconnect, but the subscriber can choose specific periods (x weeks/months) or action (once at next reconnect).
> So, upon a CPE crash and reboot, the subscriber would get a different
> prefix. Right?
>
> Thanks!
>
> Cheers,
Yes, the current default is for the subscriber to get a different prefix after a CPE crash and reboot (like in IPv4). But a CPE crash is not a common case. The most common case for prefix change is a DSL disconnect (due to line issues) or a PPP disconnect (due to network issues).
Also, many of our CPEs store internally the prefix, so after a PPP reconnect they inform the LAN hosts about its release.

--
Tassos