IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 03 February 2019 19:41 UTC

Return-Path: <brian.e.carpenter@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 94A9F12D4EA; Sun, 3 Feb 2019 11:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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=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 4128YXybmswH; Sun, 3 Feb 2019 11:41:36 -0800 (PST)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 395461277D2; Sun, 3 Feb 2019 11:41:36 -0800 (PST)
Received: by mail-pf1-x42a.google.com with SMTP id b7so5745373pfi.8; Sun, 03 Feb 2019 11:41:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=lYHH6JI1fM9hsvdkMG4igQvx7IyAnFUJR9lChxoaYgY=; b=f5rsQFn26T618pjceHcxFSS+B8TL4I6NGBQe3gC+Du1OReIJO6E+jstWPFnLcWSrhZ p7rwOeCeB3+GMdO+NYjd7WO4xjJUJv1tFFOZrOsNKNiLhMhMGN569X2VJtzJcegey7mN JwmYV6MSEuc5x/6m3TP+z58JurNUvrKkm1S0DO0ybmD9YG+BrZpmRYg5L3JgnYfE+xHP AsOijO0Jdr2JKhIY2wMIMDwQef6QT2tKz+fqGX+weBYLeiQzUycicxBhkLggA5ZcdBxg DxaqAATDi4JMIzsZj0aosxc0D6NDXXY5hBvt4BXdoKhYfef+UqfXbz66sEYCfs5QghSk 9l6w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=lYHH6JI1fM9hsvdkMG4igQvx7IyAnFUJR9lChxoaYgY=; b=hGDIcWLYbhhtyH0uyudADGlDhrXcs5D/TkI2RCcHgYJXzDa/o1gTHepCxKQUVJtdPs NOe7+pPbFCbQ31eJpcgyC+PiSOtheGGbNRDya28wSGLIGve+nJqVyBRBcVqVPx2DB85k lo28P7mn0wTL1MmMDaNqAOnqRslF6DuZ2iPbJtyCwWP8kTZPqtuFYh5xpdxAkOCMCd1B Oa67+TIcj1y8XnprYNwU5BkLBVCQnWOap/ASHT9jaQGqLB2I8KKF48GVzUj72xsSsdRI LDPj8d3tmcBvRa1UddUnaUPV7EWQBRN41TXs4tb+cvjcE5autBVjtDHyqeH1LOPayIcI 6SAw==
X-Gm-Message-State: AHQUAuZoZnHTV25juME/2CqtSz2yf++Jc+FMMs34lhV1LO3SaTDFJJi0 ho7qZC6qeVURYXbrCPIGgTRE8S0q
X-Google-Smtp-Source: AHgI3IZUjMX8j8xVKXUAjYNDIzZp193Q3WEF3jU0/esTM7/f2L+lM0XU9uVjxpF2qjb0kE3SE3tQkg==
X-Received: by 2002:a63:330c:: with SMTP id z12mr9692108pgz.10.1549222895355; Sun, 03 Feb 2019 11:41:35 -0800 (PST)
Received: from [192.168.178.30] ([118.148.79.176]) by smtp.gmail.com with ESMTPSA id g28sm19608394pfd.100.2019.02.03.11.41.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 03 Feb 2019 11:41:34 -0800 (PST)
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
To: JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>, Fernando Gont <fgont@si6networks.com>, Ole Troan <otroan@employees.org>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <alpine.DEB.2.20.1901311236320.5601@uplift.swm.pp.se> <m1gpCcz-0000FlC@stereo.hq.phicoh.net> <ddd28787-8905-bafd-3546-2ceef436c8b0@si6networks.com> <m1gptWx-0000G3C@stereo.hq.phicoh.net> <69609C58-7205-4519-B17A-4FBC8AE2EA16@employees.org> <ac773bb5-0da8-064b-d46b-3a218b8c9e7a@si6networks.com> <CFAEACC4-BA78-4DF9-AD8A-3EB0790B8000@employees.org> <a4f6742e-f18e-3384-d4cc-06bfab49101f@si6networks.com> <FEFA99C2-4F09-4D8F-8D51-C9D9D7090637@employees.org> <a484d5de-0dce-a41a-928e-785d8d80d05d@si6networks.com> <A40C5116-9474-4F2B-BD94-F57D155ECD4C@employees.org> <b05e3872-d63b-108c-6c00-21b951dad263@si6networks.com> <A9FBBED3-A858-4BB1-A02A-2A06CBEB7662@consulintel.es>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <010b2c6d-9c79-9309-aad8-32530c9dab94@gmail.com>
Date: Mon, 04 Feb 2019 08:41:28 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <A9FBBED3-A858-4BB1-A02A-2A06CBEB7662@consulintel.es>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KB6OY0yzEY9wF2ZMTE8Ljlzv9mU>
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: Sun, 03 Feb 2019 19:41:38 -0000

On 2019-02-04 06:46, JORDI PALET MARTINEZ wrote:
>     The RIPE document does not recommend it. In Germany, that's the expected
>     default.
>     
> ---->  This is not correct, in the context of another mailing list, a few day ago, some people (including people from Germany) confirmed that this is not true for Germany, neither there is any law or anything similar that requires dynamic prefixes.

It doesn't matter. The objective fact is that getting a new prefix after a CPE reboot, or after a DSL disconnect/reconnect, or every 24 hours, is common, and not just in Germany.

Not that I've ever had any stale address problems as a result, even at a time when I was getting multiple ADSL disconnects per day due to a line fault. So with a FritzBox and Windows hosts, the "common problem" simply wasn't a problem.

   Brian

v2.23.0 | Report a Bug | By Email