Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios

Mark Smith <markzzzsmith@gmail.com> Mon, 25 February 2019 12:57 UTC

Return-Path: <markzzzsmith@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 88E47130EF9; Mon, 25 Feb 2019 04:57:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.497
X-Spam-Level:
X-Spam-Status: No, score=-1.497 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 at8SvGGjPj83; Mon, 25 Feb 2019 04:57:10 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (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 97952130EF1; Mon, 25 Feb 2019 04:57:10 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id 32so7666738ota.12; Mon, 25 Feb 2019 04:57:10 -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=t91KmrOcShCiGNFxgeFZ+wgrsKlYcaky/UZBC49vHeQ=; b=DMaBJgDcA8hm86GvOBpcbC/Fx00ftxxtYmYMzDm9lHhhb/FhxsxOqDW7DKOE7hnK// hoHVk2I1kkiZI5/KVyq6AEKPkxOpODXTxYAwMkH9m3pFn2nffr76k92/45UpE/JsdU+b uI0FcprAwjfVtseKhFGkCU10dorVUQkwZv/2OCbHyTcwXEAc3cimfGAfdsaTCmu5DRsu cS6bUC/hOB31TQOBfZbumXW5QYMUj1i6JEsVUzh5DCWQrzh8POnPWWmm4tvlFNwTQbWi M05b9hkGzb24dAj63Af1uBJ6e1q5lh8IpXPvdvPkyYQfa/G7hVFq92OtqZE/3+2G34BO MbWA==
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=t91KmrOcShCiGNFxgeFZ+wgrsKlYcaky/UZBC49vHeQ=; b=ZIYgg6jNPI+VmEQL6QwcsKjPT1UI8aw5qgR/FU4R3m3/QbHCTwMSOdSCtxWCL9YMf9 6BLEpHSGZ4G32cIb5+NOtjc/md/xLmP9LbholImLvQEO5okyHxhjOwX+Ivf+Ukk/WpOI BWLAiLFy0hbW3hU66clOUJ8Px2ZI2EnBaoUgb+s3pzTXxELqRHvFFrx/Me/gNqBK+RH0 +d3Im3UjTFzvqw3unJKWirpmZig2vLlkuVU9iCrQklPlbAiZv+6FvPRWNrr9Oxhb+9BT jydi7dyJtkMWpSXgxsb+Hr2R/P3PQaDW8Vte8griBXU8Jd0wqjQ5zdwYn09bsCAmYVEN MXPA==
X-Gm-Message-State: AHQUAuYsmv2rCUtsXZQOvQkl2v9Jb6hYHUQtUV9rtephmgl4/F34WMmo LcxNzbd2WMA1SXZI24PeDLctWfwNtTKjDlVY+yoWPw==
X-Google-Smtp-Source: AHgI3Ia9DtpuvH2balubIFyEO/oh0SHtqUKIXcSSwm4LhXtqrhfM04F+ki2769veIBJ139FN2XfWbdfaDD9BUMQ9fEA=
X-Received: by 2002:a9d:6d98:: with SMTP id x24mr11813740otp.318.1551099429621; Mon, 25 Feb 2019 04:57:09 -0800 (PST)
MIME-Version: 1.0
References: <6D78F4B2-A30D-4562-AC21-E4D3DE019D90@consulintel.es> <B6E2EC33-EEAF-40D0-AFCC-BDAFA9134ACD@consulintel.es> <20190220113603.GK71606@Space.Net> <28fbc2c305c640c9afb3704050f6e8d7@boeing.com> <20190220213107.GS71606@Space.Net> <019c552eb1624d348641d6930829fd1f@boeing.com> <CAKD1Yr0HBG+rhyFWg9zh0t3mW486Mjx9umjn+CRqAZg4z9r0dg@mail.gmail.com> <20190221073530.GT71606@Space.Net> <CAO42Z2wmB2W52b4MZ2h9sW5E9cQKm-HRjyf--q8C26jezS7LXQ@mail.gmail.com> <a73818d31db7422b99a524bc431b00ed@boeing.com> <CAO42Z2z9-48Gbb_Exf+oWUqDO=axSLpZBtqeDcxkAoFq5OziGw@mail.gmail.com> <CALx6S3624hnGauG1HaSWPMvQw0t2Q5R3gb8W4R8w3kuK7dcrWQ@mail.gmail.com> <1F07F2BB-2F37-4D12-9731-7892DF4E3D88@consulintel.es> <0a582916-af14-bd82-a4cd-002a36f8830b@huitema.net> <67515a73-26a5-3ed0-da88-1a4ce64550d3@foobar.org> <360afa02-cf23-375c-4876-780d3c2aa5ac@gont.com.ar> <CAHL_VyD34V=TRcsCp0DOO9HJNHyy5xkiMQ_cZoBa7zTE4fe5OA@mail.gmail.com>
In-Reply-To: <CAHL_VyD34V=TRcsCp0DOO9HJNHyy5xkiMQ_cZoBa7zTE4fe5OA@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 25 Feb 2019 23:56:57 +1100
Message-ID: <CAO42Z2xZTQQj+2VNTQDv6P3HHvNxySppC64eAceXFizn35GbOQ@mail.gmail.com>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
To: Richard Patterson <richard@helix.net.nz>
Cc: Fernando Gont <fernando@gont.com.ar>, v6ops list <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000083978f0582b77aa0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/woOBBBTv72v968Qj8O0zTm7rxmE>
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: Mon, 25 Feb 2019 12:57:13 -0000

On Mon., 25 Feb. 2019, 21:33 Richard Patterson, <richard@helix.net.nz>
wrote:

> On Sat, 23 Feb 2019 at 05:22, Fernando Gont <fernando@gont.com.ar> wrote:
>
> > * As per RFC4862, it turns out that you cannot remove a stale prefix vy
> > sending an RA wiht a "Prefix Lifetime" of 0. SO, with current standards,
> > not even the CPEs can (even if they wanted to) do something to fix the
> > problem.
>
>
> The Valid Lifetime cannot be zeroed or shortened below 2 hours, but
> the Preferred Lifetime can.  So we can't invalidate the prefix, but we
> can deprecate it so it's not used for new outbound sessions.   This is
> what we've implemented in our CPEs, after an unavoidable change in
> prefix, and it seems to have mitigated (or reduced the impact of) the
> issue.
>

It seems the Ubiquity Networks community have discovered the
DeprecatePrefix option of 'radvd' and are suggesting its use to mitigate
this issue.

https://community.ubnt.com/t5/EdgeRouter/Solution-for-client-losing-IPv6-connectivity-after-PPPoE-re/td-p/2019416



> RFC4862 §5.5.3
>
> e)  If the advertised prefix is equal to the prefix of an address
>       configured by stateless autoconfiguration in the list, the
>       preferred lifetime of the address is reset to the Preferred
>       Lifetime in the received advertisement.
>
> ....
>
>       Note that the preferred lifetime of the corresponding address is
>       always reset to the Preferred Lifetime in the received Prefix
>       Information option, regardless of whether the valid lifetime is
>       also reset or ignored.  The difference comes from the fact that
>       the possible attack for the preferred lifetime is relatively
>       minor.  Additionally, it is even undesirable to ignore the
>       preferred lifetime when a valid administrator wants to deprecate a
>       particular address by sending a short preferred lifetime (and the
>       valid lifetime is ignored by accident).
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>