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

Fred Baker <fredbaker.ietf@gmail.com> Wed, 13 November 2019 05:08 UTC

Return-Path: <fredbaker.ietf@gmail.com>
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 AA1411200E0 for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2019 21:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com
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 UW-Umn8fX6VO for <v6ops@ietfa.amsl.com>; Tue, 12 Nov 2019 21:08:16 -0800 (PST)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C36ED1200C4 for <v6ops@ietf.org>; Tue, 12 Nov 2019 21:08:16 -0800 (PST)
Received: by mail-pg1-x532.google.com with SMTP id q17so578160pgt.9 for <v6ops@ietf.org>; Tue, 12 Nov 2019 21:08:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zRLlqpILc4MJ7IZb0GnvTVvBxLfcqDO9FE1BaSsl9Z4=; b=uLviiKuY5JRuUOyyslZEEdnAUJUqzANmrONzKSve2j3306Tdipc2DBW5XnqsOEDHAk iHWRiuX2NldGeePgv1jrrDH85SP7tkuYwR0f+xmqWqk8zqgEf0TI7nbfZRDix99mi04y AQJ4MuP2DfDO2uP2HaxC0GCRik26TjMhPS/i4sXiha/W6tdXtFsAYcCgtqoBkmDkXNUU 29w92icbbXUtECqlwxmpCTTLy0X3HPZtRJDV7tbh8DAR2scYRkOdduKUBmXbMy/qUA1T c/rYP1e0OR3MIxAY4c8s8fI8vqTj6C/Z9e8Xek05x4Enk+UxgMaQ22nJ3jXICUqjim52 jiZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zRLlqpILc4MJ7IZb0GnvTVvBxLfcqDO9FE1BaSsl9Z4=; b=E83M4py9d3Ba4Ptkefrff08qYwaVXMQH0MEQbyoDWUrwvrQ7XweUVlbOulxbi6CyO7 bB5BRYFGEisBrCcmNO5+PEuGnTLcnz5/FGtPMJCXKxoxsT++2kk3diMzF35lfihZbWjX r+YsPpNtOCnidsHmy2EjEbUBMdO3M0ID0QQxxVIGfMq8E16iiFbdSEuOK3V4YIDwy/Yj G3PgOgqyRa0X2Hrit5ZKYNtIq6lKt3lzjUoGkszgT7UEzy6QlDZp2qaGxfTc5lGe68V5 i9CRunnoifHBNp1Qyfq03yf4e0y0Ln5wXYi+GluMudFvkVuqtO2k2TQ8IXfKqdL4GZLd yH4A==
X-Gm-Message-State: APjAAAV5IfNiwTuOzQC7StDo7C3qmmJC8+Y6+jFaWllRnM9qg5NvFiPn mqV20rNznAnBvqNhNnJUe0plv6cleuc=
X-Google-Smtp-Source: APXvYqyer0T41KLv31PKbp1yM0pvCxwV+oOR+Si6w9toV0GvswbMtbbpHSP7WkklT6XVRfDQaay6GA==
X-Received: by 2002:a63:7015:: with SMTP id l21mr1432587pgc.200.1573621695911; Tue, 12 Nov 2019 21:08:15 -0800 (PST)
Received: from 237.66.20.149.in-addr.arpa (237.66.20.149.in-addr.arpa. [149.20.66.237]) by smtp.gmail.com with ESMTPSA id s24sm768144pfm.144.2019.11.12.21.08.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Nov 2019 21:08:15 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.2\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <2c95e214-7a64-311a-e856-d5891dda260d@si6networks.com>
Date: Wed, 13 Nov 2019 10:38:11 +0530
Cc: Tassos Chatzithomaoglou <achatz@forthnet.gr>, v6ops list <v6ops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <33554C26-5007-483C-8C5E-6CC6DEB7724F@gmail.com>
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>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3608.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/SGJ6PVOzfDA0uq0nXghrxThVl-k>
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: Wed, 13 Nov 2019 05:08:18 -0000


> On Nov 12, 2019, at 8:03 PM, Fernando Gont <fgont@si6networks.com> wrote:
> 
> So, upon a CPE crash and reboot, the subscriber would get a different
> prefix. Right?

Change "would" to "could", and you're probably close. In general, I would expect ISPs to not want to randomly change their routing, and so it would not be deterministic - if the customer is no longer using a prefix (e.g., the CPE crashed and routing has changed anyway), when the CPE comes back up they might give it a different prefix. However, I'd be surprised if they did it "just because".