Re: A common problem with SLAAC in "renumbering" scenarios

Jen Linkova <furry13@gmail.com> Wed, 20 February 2019 09:16 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC47C1276D0 for <ipv6@ietfa.amsl.com>; Wed, 20 Feb 2019 01:16:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 jUGEkv94_WNI for <ipv6@ietfa.amsl.com>; Wed, 20 Feb 2019 01:16:23 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 3BBC1124B0C for <ipv6@ietf.org>; Wed, 20 Feb 2019 01:16:23 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id r21so1531447qkl.11 for <ipv6@ietf.org>; Wed, 20 Feb 2019 01:16:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EUx/gu3gXgG4RZlk537Ku8mlxKiY6vchZRU+Z1Rl2Gc=; b=hBTaK1VRoyraROBvGvyAX40OYc1cuZYTvFcZ/9q0LTUu5xFHJCCCdrpx9h1mCMwkKC qvgYHZp0b+RMJ7m//BiWXZSkuH+7vmCKzuWhQ4sSzyBqEONrkHahDYrPpuZgIJR0kC2g O3N5cslrotECzgf7/gftewwONQOmvnfz7BhXxMxeLup/YcB4OhnJ08N2JdqbUZgMEdiu x8JH5z/lYaNgUpR1oa6zowSP198woPMwnXsd3Cw2b3H15soqccnDi4tQ5k6Bdv1ec4N2 YhKDziyQgAIBZmCROLRKs0dayQo+tz0xsAAeN1DfSy4syGMLQQnK+qCiHN8+hf8Bp3BF +oag==
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=EUx/gu3gXgG4RZlk537Ku8mlxKiY6vchZRU+Z1Rl2Gc=; b=Crg4kVO7Cl/XAdMBbb9/wdqZO8oPZ2ZC7LuDlvsZ+tPiVQOBypLwnl6mLFqh+0yyQJ JMvrNEyQxo8Dc0sSI+bWw0xJib8aE4SQzvrt7SVSEA3KQsQHsH5Frs2DJ0J6rsBhsaJx okIalDx4qnu5epkohEAvCbvkuqBcfY9MQwz3RL85qiBCDs08mQuKUU0LSaRO0h8Nle2m Egof0TD3Pvh2hU1Zp1yquAV0g8bL2d3Zusu4luRvmT2pdy3fA7PUDiQNvw3OxUu2xdmp FLEZElYDEwJLm4YdxbGQ49RWZ2JdPs9wzzlYGvza9/rbYgoHPHRszgviJOjcH0kvxvbV 9bUQ==
X-Gm-Message-State: AHQUAubs6MWbkTr9oDnI0SUh7g51YHi3rvHWsUSKGdTs5w23i657yyoB fEjHyIkXTtauuC3gjtSmnl1AWT+HngpSxaAvMfWNR7ng
X-Google-Smtp-Source: AHgI3IaGUv3GnmGbSLsiK3r2mrm1MHkiRvyqScEgmKFWm5JiBOGYsMx5s14P2sM6D9GDMWyyiOUewXzlxjIZ+YQRk88=
X-Received: by 2002:a37:d4d1:: with SMTP id s78mr23717618qks.139.1550654182116; Wed, 20 Feb 2019 01:16:22 -0800 (PST)
MIME-Version: 1.0
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <alpine.DEB.2.20.1901311236320.5601@uplift.swm.pp.se> <35adea8e-704a-76f2-857f-a83a9ad689ef@si6networks.com> <CAFU7BAS1_veTu-ZXAF0MF4niJwz149nGipx3ep_6fh1bewOzgg@mail.gmail.com> <d9503983-6524-a13a-2cb0-cdcb95f76ea6@si6networks.com> <CAFU7BAQfg712UfgW9wi9pd3eVeZP9cqJEXd6=FDmchuSdauv+g@mail.gmail.com> <66687354-5ee1-80f7-2a32-78631530dfb3@go6.si>
In-Reply-To: <66687354-5ee1-80f7-2a32-78631530dfb3@go6.si>
From: Jen Linkova <furry13@gmail.com>
Date: Wed, 20 Feb 2019 20:16:09 +1100
Message-ID: <CAFU7BASbotMqVSRH3P0p2sn8mAX+gL8==tBdNYoR_75XUE918w@mail.gmail.com>
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
To: Jan Zorz - Go6 <jan@go6.si>
Cc: 6man <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ZpCoTCZAQ2AoQethCm2wJT_j66o>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2019 09:16:25 -0000

On Tue, Feb 19, 2019 at 8:38 PM Jan Zorz - Go6 <jan@go6.si> wrote:
> In theory you are correct.
>
> In practice - at residential home or SOHO environment we rarely see a
> corner case that you described. I'm not saying it's incorrect, but I
> would say - very very rare.

Sorry if I did not make it clear - what I'm trying to say is that the
proposed changes seem to affect not just residential home or SOHO
environment but all hosts in all environments.
So it would be nice to think about other scenarios and potential impact.

> We really need to address the big elephant in the room first and enable
> operators to deploy IPv6 on a massive scale in architectural way that
> they choose.

I think we all agree on this (well, unless what they choose does not
hurt users and IPv6 deployment ;-P)

>We ignored it for too long now. :)

Now all my personalities (one is an operator who has spent a lot of
time recently trying to deploy DHCPv6-PD and another one keeps sending
emails to IETF mailing lists) are equally confused ;)

> P.S: I hope that we can have this discussion at IPv6 WG meeting at RIPE
> in Reykyavik in May and bring some additional operational feedback to
> this mailing list ;)

We've just requested the second slot so hopefully we can have that
discussion in Reykyavik...I hope it's not too late to ask RIPE NCC
for popcorn machines in the hotel lobby ;))

-- 
SY, Jen Linkova aka Furry