draft-gont-6man-slaac-renum: Protocol-based improvements (Re: [v6ops] cpe-slaac-renum: Proposed text for prefix lifetimes)
Fernando Gont <fgont@si6networks.com> Wed, 08 April 2020 21:25 UTC
Return-Path: <fgont@si6networks.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 169AD3A1857 for <ipv6@ietfa.amsl.com>; Wed, 8 Apr 2020 14:25:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 IxqWnbj54ck0 for <ipv6@ietfa.amsl.com>; Wed, 8 Apr 2020 14:25:00 -0700 (PDT)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BF523A17FA for <6man@ietf.org>; Wed, 8 Apr 2020 14:24:56 -0700 (PDT)
Received: from [192.168.0.10] (unknown [181.45.84.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 60210893A0; Wed, 8 Apr 2020 23:24:53 +0200 (CEST)
From: Fernando Gont <fgont@si6networks.com>
Subject: draft-gont-6man-slaac-renum: Protocol-based improvements (Re: [v6ops] cpe-slaac-renum: Proposed text for prefix lifetimes)
To: "Bernie Volz (volz)" <volz=40cisco.com@dmarc.ietf.org>, "otroan@employees.org" <otroan@employees.org>
Cc: "6man@ietf.org" <6man@ietf.org>, Erik Kline <ek.ietf@gmail.com>
References: <A7402541-3A6E-474D-B4D9-1E1B4B3D50A9@employees.org> <4E01DB76-DBF4-4B6D-B054-2A011E0AC3A6@fugue.com> <E65F7C97-0188-4BF9-98C7-F2924CDE0EC5@employees.org> <BN7PR11MB25478E4B49DA3B5D7B966DB4CFC00@BN7PR11MB2547.namprd11.prod.outlook.com> <BN7PR11MB2547577B9EB428DDB3F2FB94CFC00@BN7PR11MB2547.namprd11.prod.outlook.com> <BN7PR11MB2547A8F72529CA4EFE3A110ACFC00@BN7PR11MB2547.namprd11.prod.outlook.com>
Message-ID: <e4f3260b-20f8-da1c-c8c5-798f2d410e56@si6networks.com>
Date: Wed, 08 Apr 2020 18:24:46 -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: <BN7PR11MB2547A8F72529CA4EFE3A110ACFC00@BN7PR11MB2547.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RIWfPPUgNdNvcvUHf7c9sNdpciw>
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: Wed, 08 Apr 2020 21:25:07 -0000
Hi, Bernie, On 8/4/20 16:44, Bernie Volz (volz) wrote: > > Ole, perhaps if there was a concrete proposal for an alternative approach, we would go there? So maybe this debate needs to be put on hold a bit to allow alternative approaches to come about. Though as stated earlier, some of this has been discussed for a while and I don't think there are any yet? We have discussed this for over a year now. Ole has repeatedly argued that this is not a problem, or that this is not a problem worth solving, because the networks that face these problems suffer from the incompetence/lack of knowledge of their admins/operators (even after multiple-statements from operators on why these scenarios take place). He deems these occurrences as rare, while concrete data and anecdotal evidence suggests 40% of deployments doing dynamic addresses. In such scenarios, he argues that the user should switch ISPs, when in so many different places I know of, there is no other ISP to switch to. Now, the topic has been debated for over a year now. Nobody prevented anybody to come up with something better.. and as you correctly note, nobody did. On our side, we kept working on this. A few folks (Jen and Philip to name a few) found flaws in our early proposal, and suggested improvements, which we did our best to incorporate. We also discussed this with as many operators (this was discussed, IIRC, in RIPE, UKNOF, LACNOG..) and developers as possible, and received very positive feedback. And we also took the time to produce implementations of some of the improvements we propose (please see: https://tools.ietf.org/html/draft-gont-6man-slaac-renum-06#section-6), or discuss this with developers that might want to improve SLAAC. Maybe in order to honor the motto of "we reject kings", it would be time for the working group to be polled for adoption of this document. Certainly not to rubber-stamp it, but to continue polishing and improving it where/as appropriate. Thanks, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- draft-gont-6man-slaac-renum: Protocol-based impro… Fernando Gont
- Re: draft-gont-6man-slaac-renum: Protocol-based i… Loganaden Velvindron
- Re: draft-gont-6man-slaac-renum: Protocol-based i… James R Cutler