Re: [v6ops] Flash renumbering

Richard Patterson <richard@helix.net.nz> Fri, 18 September 2020 20:31 UTC

Return-Path: <richard@helix.net.nz>
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 6BEC83A118F for <v6ops@ietfa.amsl.com>; Fri, 18 Sep 2020 13:31:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=helix-net-nz.20150623.gappssmtp.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 suobtTWApmdT for <v6ops@ietfa.amsl.com>; Fri, 18 Sep 2020 13:31:32 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 0AE113A115D for <v6ops@ietf.org>; Fri, 18 Sep 2020 13:31:27 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id g7so8348000iov.13 for <v6ops@ietf.org>; Fri, 18 Sep 2020 13:31:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helix-net-nz.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=by5JUptTwfesMiZcc9uhHeBanvoLe2AeayMRSOg/oS0=; b=vl6L2lRfM6rKDwmC/EyIrDBbFd7kE4vH8cFMUqnCuI2um5O6ZcZaxt+81OoCSvnHOW AvoUhcl1P17MdOwZea3SH603GQD0eyUViWkf74yCX3zDVJoycFMnyCWviDW1Vzf48uWv +m2rsJIZyb3d0PXiXqYtwhbNDkzRrRt5MxLYFtYaxjHkhGBtl0ysZBXD6/rxQkoqjN60 18CFOL2v0Rs44NgfsQD959dSGcvs8NEhMy5QQMACQViNw2/MQa2LUOafRuY1GJeO71Dj rDqFixqi6QzuGgByMNZ0snVWTMloaEt222Kq1wuZSR0/NeXKHVlE1eyBjk4tW1PJzIqm a9+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=by5JUptTwfesMiZcc9uhHeBanvoLe2AeayMRSOg/oS0=; b=BBMGzA1FmZpvFj6h8l7QMa01c3vZFsOUaiEgXWAjErKdQP5eakZFB8kfTnxjEIUyMz vZU3DBcUA290noKyLxpkqAF3ts+3Hu/wvgq0pMiWa20LXq4/monxrUqq1NmVVoJ6OEwR KzU1dRtomOOWXgj7tZ0Ttdom0+uEdpHQ9SPtfqqPvTd1ptst1DRfDvgsUerKL+0JZeBV TYHP3k4/ai5tJiK1UCvCgfN+f2nhdesAsZakQdHdw/Td+9Skpdh2J6+NxYo73YGf48gM 3cm2AzcDzodolw/GLIyjzIpIqCQxfwrAYR5UGUVsO9s8XuHErm+p8eUglyMRye92P76n Q51A==
X-Gm-Message-State: AOAM532mB7rnziCQTEjGSVawarohFeLlW4uqC6h74YIYKuCaWFhO7fZz 58DkDzwiViv94ztPUavvrlpquPArIAHwUQ==
X-Google-Smtp-Source: ABdhPJykFKXtN9xBJ4hePONg8Y05Xc9YGCgv2k0Oh4RM3LIxwYO37b9PKxLkEYLkLOYNlNiwPEtIEg==
X-Received: by 2002:a05:6638:22ba:: with SMTP id z26mr32156790jas.55.1600461085949; Fri, 18 Sep 2020 13:31:25 -0700 (PDT)
Received: from mail-io1-f51.google.com (mail-io1-f51.google.com. [209.85.166.51]) by smtp.gmail.com with ESMTPSA id v20sm2171008ile.42.2020.09.18.13.31.25 for <v6ops@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 18 Sep 2020 13:31:25 -0700 (PDT)
Received: by mail-io1-f51.google.com with SMTP id y74so8346383iof.12 for <v6ops@ietf.org>; Fri, 18 Sep 2020 13:31:25 -0700 (PDT)
X-Received: by 2002:a05:6602:2e0e:: with SMTP id o14mr29771043iow.111.1600461085208; Fri, 18 Sep 2020 13:31:25 -0700 (PDT)
MIME-Version: 1.0
References: <8f964b8650cd4b619ff47aed5b07bc67@huawei.com> <7ef6cbcc-164f-383c-658b-b3c0df859535@go6.si> <1af87e24-1410-8f89-b50d-9c61694e4644@foobar.org> <f97b7ac2-0b36-2fae-58fd-eddee6f8b408@gmail.com> <76f10fa7030044c4a0b71443fde92f24@huawei.com> <CAHL_VyC7u7bNJD9pUzbFTrBtifbCVmQtPn4YHHs5g7T6omKwLQ@mail.gmail.com> <2e11a0315196499c81b72c171e014650@huawei.com> <EB3611C3-8849-4670-AFAD-4924AC79E26A@fugue.com> <93e01391b78b4c19be87f58f68281cbf@huawei.com>
In-Reply-To: <93e01391b78b4c19be87f58f68281cbf@huawei.com>
From: Richard Patterson <richard@helix.net.nz>
Date: Fri, 18 Sep 2020 21:31:13 +0100
X-Gmail-Original-Message-ID: <CAHL_VyDhUO9mMTXEB1Z53-sA4KtHMu4-vdB0zb-oukanmEdARw@mail.gmail.com>
Message-ID: <CAHL_VyDhUO9mMTXEB1Z53-sA4KtHMu4-vdB0zb-oukanmEdARw@mail.gmail.com>
To: Vasilenko Eduard <vasilenko.eduard@huawei.com>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000075f81505af9c6266"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/SoeqOhs68U0PoKJC5JygHLqCQCY>
Subject: Re: [v6ops] Flash renumbering
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: Fri, 18 Sep 2020 20:31:40 -0000

On Fri, 18 Sep 2020 at 20:47, Vasilenko Eduard <vasilenko.eduard@huawei.com>
wrote:

> From standard point of view
>
> local traffic should not stop after CPE would lose uplink,
>
> Because internal CPE switch should still switch traffic
>
> After internal CPE router would stop promoting itself a router for this
> link
>
>
>

In this scenario, when the WAN interface (native Ethernet or PPP) goes
down, would you expect the CPE router to:
a) continue sending RAs with the old prefix PIO as if nothing has happened.
b) send an RA with PIO prefered lifetime of 0
c) simply stop sending RAs with the PIO


a. messes up multihoming, and is a bit disingenuous of the CPE to continue
advertising
b. Helps deprecate the stale GUA prefix but means we lose local IPv6
connectivity
c. Prevents new devices from attaching and getting local IPv6 connectivity

ULA would help retain local IPv6 connectivity behind CPEs that implement b
& c.
I'm kinda wishing we included a recommendation for the use of ULA in
draft-ietf-v6ops-cpe-slaac-renum.  But I imagine that would be rather
contentious