IETF Logo Mail Archive

Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Fernando Gont <fgont@si6networks.com> Fri, 25 October 2019 18:05 UTC

Return-Path: <fgont@si6networks.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 E932B120088 for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2019 11:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 YmjUCbEv8fkf for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2019 11:05:09 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB752120043 for <v6ops@ietf.org>; Fri, 25 Oct 2019 11:05:09 -0700 (PDT)
Received: from [IPv6:2804:431:c7f3:bff2:b8b3:4400:3123:ecb7] (unknown [IPv6:2804:431:c7f3:bff2:b8b3:4400:3123:ecb7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 795B78681C; Fri, 25 Oct 2019 20:05:06 +0200 (CEST)
To: Ole Troan <otroan@employees.org>, Philip Homburg <pch-v6ops-9@u-1.phicoh.com>
Cc: v6ops@ietf.org
References: <m1iNIFE-0000IwC@stereo.hq.phicoh.net> <d1b6855d-bde9-7b53-4809-0846bb9772e4@si6networks.com> <CAO42Z2x7vudujw5t++obry56g=VNjQXXTHFK8pBPk0jmk78Bcg@mail.gmail.com> <CAJoHkZ8pTjszP0vw4BjX0HUhmPa6wJONzdy2JEm5iqAfBUvjRg@mail.gmail.com> <CAO42Z2wCYi4KWTEz1hUSPVr9+hu8GaHRkPuvQQ2P00knvnPaaQ@mail.gmail.com> <848BA3B3-36B4-4C42-86D0-88759BC45D5A@employees.org> <A61279DA-4678-4A10-9117-6CA227AE2FA5@cisco.com> <A90AD47E-00E2-4EAB-8BD8-142CC10A6B6F@employees.org> <m1iNv5U-0000KUC@stereo.hq.phicoh.net> <E273241D-9C35-4E07-9525-DF7FA786F419@employees.org> <m1iNywd-0000KmC@stereo.hq.phicoh.net> <49A6064C-3AA0-4AA6-B78E-ED8404D35B97@employees.org> <m1iNzQi-0000KmC@stereo.hq.phicoh.net> <C630FEB8-550D-47D1-BEEE-55134DDDEDD9@employees.org>
From: Fernando Gont <fgont@si6networks.com>
Openpgp: preference=signencrypt
Message-ID: <71621d5f-1525-98c0-aa94-281ac72a15cb@si6networks.com>
Date: Fri, 25 Oct 2019 15:04:23 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <C630FEB8-550D-47D1-BEEE-55134DDDEDD9@employees.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/zgToSZw1dEQc3KNu7CjgnYTIiA8>
Subject: Re: [v6ops] 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: Fri, 25 Oct 2019 18:05:11 -0000

On 25/10/19 10:25, Ole Troan wrote:
>>> The changes in the transport and application layers are already 
>>> happening (e.g. QUIC).
>>
>> If QUIC can deal with this flash renumbering problem then it would be nice
>> to see a report on that. I'm very curious how to would work.
>>
>> In any case, there will continue to be a lot of TCP and non-QUIC UDP in
>> the coming years. Are you saying that it will be cheaper to modify all
>> transport protocols than to fix it in the IPv6 stack?
> 
> It can't be fixed in the IPv6 stack.

When what you call "flash-renumbering" happens, hosts continue employing
addresses and network configuration that is stale incorrect. That's the
problem. As soon as you are able to detect that and unprefer/remove such
addresses/configuration, you've solved the problem.

That's what we're trying to do here.


> My argument is that if you do that, as in add support for ephemeral addressing / flash renumbering at the network layer, without doing anything at upper layers, then for an end-user, IPv6 will provide no value or more likely negative value compared to IPv4 + NAT.

The two are orthogonal. Upper-layers can/should do better. That doesn't
mean that we shouldn't improve robustness at the network layer.


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

v2.23.0 | Report a Bug | By Email