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))

Mark Smith <> Tue, 12 November 2019 22:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E61161200B9 for <>; Tue, 12 Nov 2019 14:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.497
X-Spam-Status: No, score=-0.497 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dnzaACrro_6F for <>; Tue, 12 Nov 2019 14:29:18 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2F62D120018 for <>; Tue, 12 Nov 2019 14:29:18 -0800 (PST)
Received: by with SMTP id 14so10404093oir.12 for <>; Tue, 12 Nov 2019 14:29:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TijewTMMh40ZlbPDx075DZAeoG3EFJx6bZskP8OxhVc=; b=lwXPbMVg1d3ahw9EYwLVuJ+E9kFPhn5OPopae3bBoppjQke1+G7qpIWSgFvrxF0lQt eqiz7Uj8yLkXECb+C/wZ1tnkH5TvmlhsvqbPrTC/loH4RDQzofwiTqMio8Y1vm+Wy2n7 9nwDfrUx5JNeb60bjKP2IpikZKeukTl7lQTAfpovTh9+cuJPCCkh2emeA+xkU5k2E4Ml HgeNjx0G/6YeFiJZbVZAdMJgVklhg/gh47mNTqeh+evBP+G7EudV9M4W19iOPTsNSNBp ewEpWNcFpY8xkNwLL5Ny0q8tUKZdg2situ60ZjT2DIjt054dcBAwDRpkOMZKzxshZDXY VIqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TijewTMMh40ZlbPDx075DZAeoG3EFJx6bZskP8OxhVc=; b=L/6tnTt8yDdi5dz/QqxAlhbTJSq8GaP2Xbs9Z/FNMRmIKU03w9RWWCWF+ZaR25YfLT 6UwNEuA3yHmA57osYCAt8j++oRMzg9JSCkoiGEIToOQQlC9gVxprkv9URYedsogJm4b7 +WotcF8WQLmEw/quYd6IrtFj0emPBj2cKEsycbCRHnoLUqksG126PUCUT5C7ydHdjA6W 10ufeGykaqnvoEWp2yNJUokgK8WbVeWYbBpImPxoTzcLLSARw9d/S0OWyKA5wJudJkYh 8xyjYT5ofOhbHbBfd534dySoar478gGWWfdbPWfKPzWTWpLSGU0Z+ao7NzViPeHlenH/ R5IA==
X-Gm-Message-State: APjAAAW5Q0IsSkP/LRbecvxkvg6Prwntg35/CWO9R5F++6XWVDOL5vRn e57sRVUiDRk9+JdlauDl9y03yMee649FNRphGFMrHH+i
X-Google-Smtp-Source: APXvYqwLZJritdiSEPRUmiwhvHnltnxk+la1sPEa91mn4COebbUkr2jt3BkZmylBDX1EeGn9TR1BpBuYI9E9FqgW1Ps=
X-Received: by 2002:aca:f553:: with SMTP id t80mr70813oih.60.1573597757402; Tue, 12 Nov 2019 14:29:17 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Mark Smith <>
Date: Wed, 13 Nov 2019 09:28:49 +1100
Message-ID: <>
To: Tassos Chatzithomaoglou <>
Cc: Fernando Gont <>, v6ops list <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
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-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Nov 2019 22:29:20 -0000

On Wed, 13 Nov 2019 at 08:20, Tassos Chatzithomaoglou
<> wrote:
> 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).

"like in IPv4"

Why are you giving customers delegated IPv6 prefixes - that's not like IPv4?

Other than "like in IPv4", why are you making the PD prefix change
upon reconnect when you don't have to?

What if your competitors provide stable prefixes, and their customers
get a better service experience than your customers do, without having
to wait possibly years for CPE and/or host upgrades per this ID's

What is stopping them doing that? If they already have stable prefix
supporting infrastructure, why wouldn't they switch it on when they
can, when it could mean stealing customers from you and reducing their
numbers of helpdesk calls?

>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
> _______________________________________________
> v6ops mailing list