Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds

Philip Homburg <pch-v6ops-9@u-1.phicoh.com> Fri, 25 October 2019 08:43 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.com>
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 B5D4612001E for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2019 01:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 G_UNC7vqTGD3 for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2019 01:43:03 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) (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 80FD912012D for <v6ops@ietf.org>; Fri, 25 Oct 2019 01:43:03 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1iNvBU-0000DpC; Fri, 25 Oct 2019 10:43:00 +0200
Message-Id: <m1iNvBU-0000DpC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
Cc: Fernando Gont <fgont@si6networks.com>
From: Philip Homburg <pch-v6ops-9@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
References: <m1iNIFE-0000IwC@stereo.hq.phicoh.net> <d1b6855d-bde9-7b53-4809-0846bb9772e4@si6networks.com> <m1iNXlr-0000GGC@stereo.hq.phicoh.net> <c52fda1d-9019-97e9-037c-c2c03c55df7d@si6networks.com>
In-reply-to: Your message of "Thu, 24 Oct 2019 08:17:48 -0300 ." <c52fda1d-9019-97e9-037c-c2c03c55df7d@si6networks.com>
Date: Fri, 25 Oct 2019 10:42:51 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/e0d_HaEwz0-9q2OAcjWEG8jzgC8>
Subject: Re: [v6ops] SLAAC renum: Problem Statement & Operational workarounds
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: Fri, 25 Oct 2019 08:43:05 -0000

>I fully agree with your assessment. That said, maybe the first step is
>to start with a problem statement, as with this document?

The current draft is not a problem statement. From Section 3 it describes
potential solutions.

I'm not sure a separate problem statement is needed. The relevant
documents can start with a description of what is happening today.
In perfect world, bad things do not happen, but we don't live in a 
perfect world. Most customers don't have the luxury position to change ISPs
just because their ISP does flash renumbering.