IETF Logo Mail Archive

Re: [v6ops] Flash renumbering

Vasilenko Eduard <vasilenko.eduard@huawei.com> Wed, 23 September 2020 08:23 UTC

Return-Path: <vasilenko.eduard@huawei.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 1AB7C3A0E63 for <v6ops@ietfa.amsl.com>; Wed, 23 Sep 2020 01:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 vtaxgrI8nJUI for <v6ops@ietfa.amsl.com>; Wed, 23 Sep 2020 01:23:35 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 75A0C3A0E60 for <v6ops@ietf.org>; Wed, 23 Sep 2020 01:23:35 -0700 (PDT)
Received: from lhreml707-chm.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 0595C50A08738EFF6EDF; Wed, 23 Sep 2020 09:23:34 +0100 (IST)
Received: from msceml706-chm.china.huawei.com (10.219.141.145) by lhreml707-chm.china.huawei.com (10.201.108.56) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 23 Sep 2020 09:23:33 +0100
Received: from msceml703-chm.china.huawei.com (10.219.141.161) by msceml706-chm.china.huawei.com (10.219.141.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Wed, 23 Sep 2020 11:23:33 +0300
Received: from msceml703-chm.china.huawei.com ([10.219.141.161]) by msceml703-chm.china.huawei.com ([10.219.141.161]) with mapi id 15.01.1913.007; Wed, 23 Sep 2020 11:23:32 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Richard Patterson <richard@helix.net.nz>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Flash renumbering
Thread-Index: AdaLlIyewLCjExjqRk+nNQVH29wmCwAzUPGAABOUmgAAGqqFAAAbuXfAAAxRMoAADNTJAP//1BmA///IPECAAEoYgP/7tcFAgAiApID//6SnYABVlo0Y//9FjsA=
Date: Wed, 23 Sep 2020 08:23:32 +0000
Message-ID: <0cd5191bd0664c6f9d17f9a2d2e47671@huawei.com>
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> <CAHL_VyDhUO9mMTXEB1Z53-sA4KtHMu4-vdB0zb-oukanmEdARw@mail.gmail.com> <5b2f71a95a7944f0bcda368c11c6d7a2@huawei.com> <CAHL_VyDP-w9LzQTCkQM-tyjVo+T982aazFJTWeNPvGqHSHRtgQ@mail.gmail.com> <6f5fabd632fb4954adc13ea805be3c0b@huawei.com> <CAHL_VyDO_DTtE2Uj-T2f=a4wdJ2QtNrtO8YwMS88rZtcit5MrQ@mail.gmail.com> <2fec0984-2288-420b-5ca7-6504045b2d5d@gmail.com>
In-Reply-To: <2fec0984-2288-420b-5ca7-6504045b2d5d@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.202.158]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/SXiCwI9441diTVK9kdkBUlkYpRc>
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: Wed, 23 Sep 2020 08:23:37 -0000

Hi Brian,
It is too later to discuss 8028. But yes, it should discuss what if
1) uplink is down
2) all uplinks are down
Because multi-homing has been organized to improve resiliency. Then it was logical to analyze resiliency fully.
Eduard
> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
> Sent: 23 сентября 2020 г. 0:09
> To: Richard Patterson <richard@helix.net.nz>; Vasilenko Eduard
> <vasilenko.eduard@huawei.com>
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] Flash renumbering
> 
> On 22-Sep-20 21:45, Richard Patterson wrote:
> > That presumes the end-host is multihomed with different interfaces to
> different networks, rather than attached to a single network that is multihomed.
> >
> > On Mon, 21 Sep 2020 at 16:24, Vasilenko Eduard
> <vasilenko.eduard@huawei.com <mailto:vasilenko.eduard@huawei.com>>
> wrote:
> >>
> >>     Hi Richard,
> >>
> >>     Thanks. You have pointed to interesting case. I have investigated.
> >>
> >>     Unfortunately, RFC 8028 (1st hop router selection) has not considered
> what to do when router is up, but all uplinks are down.
> 
> As Richard says, a case with one router connected to the Internet is of no
> interest to RFC8028, whatever the state of the uplinks.
> 
> If you have uplinks from more than one router, RFC8028 is useful. If one of
> those uplinks gets flash-renumbered, RFC8028 will react when and only when
> the relevant RA/PIO is updated. If I'm not mistaken, that is exactly when SLAAC
> will react too.
> 
> When all uplinks are down, who cares? (That's when you would be happy to
> have a valid ULA prefix, of course. Using GRUAs for internal traffic is not robust
> in that case.)
> 
> (You could argue that RFC8028 should have mentioned renumbering
> consisderations and ULA considerations, but I think there is very little to say.)
> 
>    Brian

v2.23.0 | Report a Bug | By Email