IETF Logo Mail Archive

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

Richard Patterson <richard@helix.net.nz> Thu, 31 January 2019 17:49 UTC

Return-Path: <richard@helix.net.nz>
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 8B34A12D4F2 for <ipv6@ietfa.amsl.com>; Thu, 31 Jan 2019 09:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.043
X-Spam-Level:
X-Spam-Status: No, score=-2.043 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.142, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 4K0qCaI9ouz3 for <ipv6@ietfa.amsl.com>; Thu, 31 Jan 2019 09:49:55 -0800 (PST)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 6CB641277D2 for <6man@ietf.org>; Thu, 31 Jan 2019 09:49:55 -0800 (PST)
Received: by mail-yb1-xb30.google.com with SMTP id k9so1672743ybg.1 for <6man@ietf.org>; Thu, 31 Jan 2019 09:49:55 -0800 (PST)
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=Fh74kfq8y6S39OY3+mp0fcXtmQ9CL6tWLsUFy+fzFYA=; b=iNRaocaXneGKJkfe/D/dCPvMHxc8cUwJ8UQIaNc7I8JGcmnHuIn5PtSf+2Ke60sBTY HfrllW30BOp2v/iWk0kUTD/WRXYa2uNqy/4S4Ep/7gxsou51BhnBALUnf0AYaTnLnz/B DHPTfSIo9jHnc4p1SHx7q3WYoe8hZjDnz9noTAvlNve9L9tpn76+GwKi04TT/aHbjIug qjQddPgLx0O2qyHJ3Q7g/rljnuyikVtE3Y+66h5AlQtcndkIbwqqGeUL60eSRBnlZWZC 4UiIBqV1rHxfuoDG0jjVCqi7Sy3+blbAkxJnd75qHD+4fThB3rFsCz1PkQmmmuqfYpb7 Ei3w==
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=Fh74kfq8y6S39OY3+mp0fcXtmQ9CL6tWLsUFy+fzFYA=; b=furDYEfyPTjHgdQZDjv7p2JT7t3IjULTrtGHkwqZDE3Q+6QFzhJ0l39cunWpF8msKj 7ZHd4sAGmoQ/eMiQHcPBEGeolA8htNDKzojkrMeC1f/fgM3Gs0MJycHDE7JlZ+NZ88ht a0S88dR5bnDZ0ou9vvU8U+wlCQAe1QksarqMC1VCcABm+EjmCWHhRyrdoTU5kehOSav1 Yxi9UpijyaS/6tmHExg+PC1Sy9YBNNSrJHcWJV5p+Z/5n7h8iJgi2f0mRFSREe3kSTjr C59ZljQP5JAmFNvQ7Jeva0dCE8bME/3GXBH4J0bVSPEFzKz2iJWVwlYo1YGpsh55lR3U ubsQ==
X-Gm-Message-State: AJcUukdldtaU25uYTYnXUydvMO96C/TsSTGhiyBsX7R+9g85RqFWSWkK uw1oU1mLYcmnF3NvgyjsWlBF5Q==
X-Google-Smtp-Source: ALg8bN7OJuzMSQB2hQX+sUkHztvIF84N8MjRSfsA41/CbDaxqsdjnWKYPaqABRnwxERWILPTMVJHnA==
X-Received: by 2002:a25:ca86:: with SMTP id a128mr34761747ybg.244.1548956994624; Thu, 31 Jan 2019 09:49:54 -0800 (PST)
Received: from mail-yw1-f48.google.com (mail-yw1-f48.google.com. [209.85.161.48]) by smtp.gmail.com with ESMTPSA id g84sm5806886ywg.9.2019.01.31.09.49.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 Jan 2019 09:49:53 -0800 (PST)
Received: by mail-yw1-f48.google.com with SMTP id h193so1617432ywc.4; Thu, 31 Jan 2019 09:49:53 -0800 (PST)
X-Received: by 2002:a81:350f:: with SMTP id c15mr34613209ywa.232.1548956993614; Thu, 31 Jan 2019 09:49:53 -0800 (PST)
MIME-Version: 1.0
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <7b77cbfe-2bee-fda0-9751-44f9fb95a553@forthnet.gr> <76ea7b13-888c-a978-9fd7-cc8387169215@si6networks.com> <CAHL_VyAji4RKJmgxpYBgaMAoQn=Ey2BrgFrkvcesYZHLSncpnw@mail.gmail.com> <alpine.DEB.2.20.1901311522080.5601@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1901311522080.5601@uplift.swm.pp.se>
From: Richard Patterson <richard@helix.net.nz>
Date: Thu, 31 Jan 2019 17:49:40 +0000
X-Gmail-Original-Message-ID: <CAHL_VyCp8Eoc2qKA+zJuVAJpHJCsmPGuiJBuSv3j5rOS3medEQ@mail.gmail.com>
Message-ID: <CAHL_VyCp8Eoc2qKA+zJuVAJpHJCsmPGuiJBuSv3j5rOS3medEQ@mail.gmail.com>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Fernando Gont <fgont@si6networks.com>, IPv6 Operations <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/F8DPxHeFfjnjI1NMHGH3dhm55jE>
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: Thu, 31 Jan 2019 17:49:58 -0000

On Thu, 31 Jan 2019 at 14:23, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> This is a good point. On our HGWs we disabled ever sending release just to
> try to always give the same prefix to the customer.

Likewise for soft reboots, but we still send a Release if the user
specifically clicks the "Disconnect" button in the UI, just in case
they do wish to change prefixes.

v2.23.0 | Report a Bug | By Email