Re: [v6ops] Flash renumbering

Fernando Gont <fernando@gont.com.ar> Sat, 19 September 2020 05:43 UTC

Return-Path: <fernando@gont.com.ar>
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 629843A0BEF for <v6ops@ietfa.amsl.com>; Fri, 18 Sep 2020 22:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.096
X-Spam-Level:
X-Spam-Status: No, score=-1.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 s4aCb0lZk8Kv for <v6ops@ietfa.amsl.com>; Fri, 18 Sep 2020 22:43:40 -0700 (PDT)
Received: from skynet.si6networks.com (unknown [83.247.7.195]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 233DB3A0BDE for <v6ops@ietf.org>; Fri, 18 Sep 2020 22:43:39 -0700 (PDT)
Received: from [IPv6:2800:810:464:1088:8aa:4c05:95c5:912] (unknown [IPv6:2800:810:464:1088:8aa:4c05:95c5:912]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by skynet.si6networks.com (Postfix) with ESMTPSA id 3F8DB1F4B; Sat, 19 Sep 2020 02:43:36 -0300 (-03)
To: Gyan Mishra <hayabusagsm@gmail.com>, Richard Patterson <richard@helix.net.nz>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
References: <8f964b8650cd4b619ff47aed5b07bc67@huawei.com> <7ef6cbcc-164f-383c-658b-b3c0df859535@go6.si> <1af87e24-1410-8f89-b50d-9c61694e4644@foobar.org> <f97b7ac2-0b36-2fae-58fd-eddee6f8b408@gmail.com> <76f10fa7030044c4a0b71443fde92f24@huawei.com> <CAHL_VyC7u7bNJD9pUzbFTrBtifbCVmQtPn4YHHs5g7T6omKwLQ@mail.gmail.com> <CABNhwV17OQsfPoxz-xfyuv7wQMq3LRye8GJC95vUyV8cnkQ-Jg@mail.gmail.com>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <aff76ed9-3ec7-db76-48d5-db3ab51a1af1@gont.com.ar>
Date: Sat, 19 Sep 2020 02:39:41 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CABNhwV17OQsfPoxz-xfyuv7wQMq3LRye8GJC95vUyV8cnkQ-Jg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wmfqOkLGJs5Zooj6gAYUq1yHul4>
Subject: Re: [v6ops] Flash renumbering
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: Sat, 19 Sep 2020 05:43:44 -0000

Gyan,

On 18/9/20 14:11, Gyan Mishra wrote:
> 
> All
> 
> I really still feel this use case being Broadband provider PD related 
> stale prefix issue  is really a corner case for SOHO users as it does 
> not impact enterprises with manually configured stable prefix which is 
> 100% of the enterprise dual stack use case.

We have authored an entire I-D on the operational aspecs of 
flsh-renumbering (draft-ietf-v6ops-slaac-renum), which lists the SOHO 
scenario as one of *many* possible scenarios. I wonder why people keep 
insisting on that scenario as the only one, even after we have 
repeatedly pointed to the multiple scenarios listed in 
draft-ietf-v6ops-slaac-renum.


> 
>  From an operations impact there is considerable monetary impact to 
> enterprises if the IPv6 standards change proposed by flash renumbering 
>   does not take into account the  enterprise stable prefix scenario that 
> does not fall into this one size fits all bucket being proposed.
> 
> I am worried about adverse effects of the changes being proposed to 
> SLAAC standard that could impact enterprises.  We just need to be very 
> careful that every used case out there is accounted for.

We *are* being very careful. Could you please point at the sceneario 
where any of what we have been proposing introduces breakage? Otherwise, 
without concrete comments, it's hard to have a meaningful converstion.

Thanks!

Regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1