IETF Logo Mail Archive

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

Gert Doering <gert@space.net> Sun, 03 February 2019 19:05 UTC

Return-Path: <gert@space.net>
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 F101712870E for <v6ops@ietfa.amsl.com>; Sun, 3 Feb 2019 11:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 OEShtqpjWTMB for <v6ops@ietfa.amsl.com>; Sun, 3 Feb 2019 11:05:21 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B7E21277D2 for <v6ops@ietf.org>; Sun, 3 Feb 2019 11:05:21 -0800 (PST)
X-Original-To: v6ops@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 42A6D418F7 for <v6ops@ietf.org>; Sun, 3 Feb 2019 20:05:19 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 3034640D75; Sun, 3 Feb 2019 20:05:19 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 1FBF983C8; Sun, 3 Feb 2019 20:05:19 +0100 (CET)
Date: Sun, 03 Feb 2019 20:05:19 +0100
From: Gert Doering <gert@space.net>
To: Nick Hilliard <nick@foobar.org>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, v6ops list <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>
Message-ID: <20190203190519.GY1543@Space.Net>
References: <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> <CAO42Z2xzYQESqqsz4AEE89vx=AhvBEf8Yzyae9o7z1U1XYyarw@mail.gmail.com> <alpine.DEB.2.20.1902031813310.23912@uplift.swm.pp.se> <23b3ffc3-7f01-6d15-ae93-c0e6932d53a6@si6networks.com> <857eef9b-e37d-1e3e-cf7f-ce2122f4d645@joelhalpern.com> <ff42613e-30a6-1e11-f512-6e78bcf7ead5@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <ff42613e-30a6-1e11-f512-6e78bcf7ead5@foobar.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/09XTAnJv1oOfpBys0B4dK2cFt-o>
Subject: Re: [v6ops] A common problem with SLAAC in "renumbering" scenarios
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: Sun, 03 Feb 2019 19:05:24 -0000

Hi,

On Sun, Feb 03, 2019 at 06:53:38PM +0000, Nick Hilliard wrote:
> The IETF may well be able to offer reasonable guidance here.

But isn't much more fun to quarrel about semantics of some sentence in
a long-dead RFC instead?

Real world problems, experienced by real people out there, how uninteresting.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

v2.23.0 | Report a Bug | By Email