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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 24 October 2019 19:38 UTC

Return-Path: <brian.e.carpenter@gmail.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 6EDFB120025 for <v6ops@ietfa.amsl.com>; Thu, 24 Oct 2019 12:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 JhRJO93xflRt for <v6ops@ietfa.amsl.com>; Thu, 24 Oct 2019 12:38:46 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 808B2120020 for <v6ops@ietf.org>; Thu, 24 Oct 2019 12:38:46 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id c184so6250566pfb.0 for <v6ops@ietf.org>; Thu, 24 Oct 2019 12:38:46 -0700 (PDT)
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=+rzi9MPPi9+i02DYcyG4NqFS0tfLN2O/Z/SOx/Yei/Y=; b=ILpmEl8v8QmtQeX/vL9DHJwEaIRT7is0XiBvvDt9Id9fZSTblLSKynIpsVdGyAqczp nDWrTdoiEJ4XnmUwy//jcaaGlSEIvf8FlMgo7kW4sPze7T3Xlc6JZmmBDcWHFep1TVXH MLv4E3AwJqRzy+AgX1+XO09edogmx34VgpP13PKBsv1EQFYIpE9HmiXr6qI+nBVRJpFy 7LNtn5YuHqyaOIhOZXw3aaJp7LghU3VOWQORADdp55kmCvCETROIsOVs+z98F1+1K6iy mPibnM4w3xh6aRm7iTWK6blnimOYwR5rB4gusqAhMCZkL4/xTaQnK6gO7y1LLacr98co zyRA==
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=+rzi9MPPi9+i02DYcyG4NqFS0tfLN2O/Z/SOx/Yei/Y=; b=r+vn7yhNAGaLs9L3B3ftUndAeqwvEL8zJDPu0Me5GDU5/4hwHJFBvAbuXOGk1GAYv1 XVWbZcHfjezutggzkGW7NrF2xz5R6WK6b3XsrRerBMmpvZthLbABYbVmzXzXDcZZdXUp 5/lm2HaHjgg1vMKrtmZS/2amUxGw/myDuESeQcMYOUrI59pPfZ45AWH+g44ZyJrjY2jy yclCReVPsF0MCWiq9RYQYH/fa9RFrBMJ6R33y0Qeszu5mFC5Y3lqs8oeGGqlfCLC2lXY fKYVYb5uC5zkjn7cQRIw6FC4on5WMTaq2H0M+ZdWErqnncJ+Nsh/Azq5eMvdbU+hXN79 e7wA==
X-Gm-Message-State: APjAAAXg9Ssw/58BFLaEae94MRwgVxKCZDVHx1uWpA4xKUS8krZ43WQu M588wIEhd+IFUvHBO25T9bd5uBLM
X-Google-Smtp-Source: APXvYqxX7v6tjcRtQwX5ZIx8Sw+L8fZCJZeyiZxgdlGFLtDp9BhPmwj7d7hJ8YRi+DsmP5Ty3g4ROA==
X-Received: by 2002:a17:90a:35a5:: with SMTP id r34mr8782872pjb.40.1571945925525; Thu, 24 Oct 2019 12:38:45 -0700 (PDT)
Received: from [192.168.178.30] (98.145.69.111.dynamic.snap.net.nz. [111.69.145.98]) by smtp.gmail.com with ESMTPSA id b3sm27804749pfd.125.2019.10.24.12.38.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Oct 2019 12:38:44 -0700 (PDT)
To: Ole Troan <otroan@employees.org>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: v6ops list <v6ops@ietf.org>
References: <m1iNIFE-0000IwC@stereo.hq.phicoh.net> <d1b6855d-bde9-7b53-4809-0846bb9772e4@si6networks.com> <CAO42Z2x7vudujw5t++obry56g=VNjQXXTHFK8pBPk0jmk78Bcg@mail.gmail.com> <CAJoHkZ8pTjszP0vw4BjX0HUhmPa6wJONzdy2JEm5iqAfBUvjRg@mail.gmail.com> <CAO42Z2wCYi4KWTEz1hUSPVr9+hu8GaHRkPuvQQ2P00knvnPaaQ@mail.gmail.com> <848BA3B3-36B4-4C42-86D0-88759BC45D5A@employees.org> <A61279DA-4678-4A10-9117-6CA227AE2FA5@cisco.com> <A90AD47E-00E2-4EAB-8BD8-142CC10A6B6F@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <71100bce-f332-5805-e94a-9ce6ac7b110d@gmail.com>
Date: Fri, 25 Oct 2019 08:38:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <A90AD47E-00E2-4EAB-8BD8-142CC10A6B6F@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/M-kgpUXfg6a5XLAg_43tSXR_LYE>
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: Thu, 24 Oct 2019 19:38:48 -0000

On 25-Oct-19 02:38, Ole Troan wrote:
> Eric,
> 
>> What about a "IPv6 renumbering considered harmful" or "Unstable DHCP-PD prefix considered harmful" ?
> 
> Perhaps, but isn't there a long list of documents the IETF has produced on IPV6 renumbering already?
> Would a new document say anything new and more useful?

I doubt it, although we did leave many dangling problems in
https://tools.ietf.org/html/rfc7010

     Brian

> 
> And it's not like DHCPv6 PD (RFC3633) isn't clear either. From the abstract:
> 
>    The Prefix Delegation options provide a mechanism for automated
>    delegation of IPv6 prefixes using the Dynamic Host Configuration
>    Protocol (DHCP).  This mechanism is intended for delegating a long-
>    lived prefix from a delegating router to a requesting router, across
>    an administrative boundary, where the delegating router does not
>    require knowledge about the topology of the links in the network to
>    which the prefixes will be assigned.
> 
> 
> That said, if people want to write a "IPv6 networks need stable prefixes" document, go ahead.
> I'm skeptical that playing with prefix timers and protocol mechanisms will do more than put lipstick on the pig. Iff we wanted to solve ephemeral addressing / connectivity, that's would require something else.
> 
> Best regards,
> Ole
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> .
>