Re: A common problem with SLAAC in "renumbering" scenarios

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Wed, 20 February 2019 06:02 UTC

Return-Path: <prvs=1954f3d980=jordi.palet@consulintel.es>
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 86DA712E036 for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 22:02:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 xS7gR9NOOSju for <ipv6@ietfa.amsl.com>; Tue, 19 Feb 2019 22:02:23 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EC431277CC for <ipv6@ietf.org>; Tue, 19 Feb 2019 22:02:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1550642539; x=1551247339; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:CC:Message-ID:Thread-Topic:References: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; bh=GB71z7w9ii9Cbbw+V+YEmCSyHc6zXhI+bVkGsEO1kZ4=; b=crWLwwSJ6KTDr JpC1PL3jo0p5Ci9sQTIiEZHJcu4s54Yq45aib3BEPp6dyusna2oMO55yYwmSMnDs haltBvOeh3StAjLGMZgDTWE7MF0fNKe9huPMsRH0dRPH8z1nH1bFwUxeyOlQ/0WX dim5LhOtO8FmxZc/+1aPPcgQ4u5wnw=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Wed, 20 Feb 2019 07:02:19 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 20 Feb 2019 07:02:19 +0100
Received: from [10.10.10.160] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50006161161.msg for <ipv6@ietf.org>; Wed, 20 Feb 2019 07:02:18 +0100
X-MDRemoteIP: 10.8.10.10
X-MDHelo: [10.10.10.160]
X-MDArrival-Date: Wed, 20 Feb 2019 07:02:18 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1954f3d980=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ipv6@ietf.org
User-Agent: Microsoft-MacOutlook/10.10.7.190210
Date: Wed, 20 Feb 2019 15:02:02 +0900
Subject: Re: A common problem with SLAAC in "renumbering" scenarios
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: Fernando Gont <fgont@si6networks.com>, Ole Troan <otroan@employees.org>
CC: 6man WG <ipv6@ietf.org>
Message-ID: <57EDE606-0E8A-41AB-AC05-A60C2412FAF6@consulintel.es>
Thread-Topic: A common problem with SLAAC in "renumbering" scenarios
References: <60fabe4b-fd76-4b35-08d3-09adce43dd71@si6networks.com> <65DB4854-97D2-4C31-A691-2CD93812EF93@consulintel.es> <CAHL_VyCMpCcGkEQu+RV1GRf2QLB-HD0+AOOBV0YhfQ5sbydVzQ@mail.gmail.com> <8CE7A0CD-97D9-46A0-814D-CAF8788F9964@consulintel.es> <e3e0bf2273e04f15b792665d0f66dfe5@boeing.com> <4c5fab33-2bff-e5b5-fc1d-8f60a01a146d@go6.si> <b4525832-9151-20bf-7136-31d87ba6c88d@huitema.net> <463f15cf-2754-e2e8-609d-dc0f33448c6c@go6.si> <ff649810-7242-7bc2-d36f-3f998f7bdd71@asgard.org> <9CDF41CA-83B4-4FC4-B995-EF79727C5458@steffann.nl> <CAO42Z2wA+vLmU7+sU6xLK7TO6pWfNQA5shs9zp=PqANCihLmBQ@mail.gmail.com> <BAB3061A-1808-4C0E-AA1B-2D7DD5BA63FC@employees.org> <bbd8b761-403a-5b3f-3f04-dc3bfdea116e@foobar.org> <6F3036C6-50A1-43C6-B554-31293B69E59D@employees.org> <433607c1-dbc6-a42e-cb17-dc209e33bdaa@si6networks.com> <12EA4FAE-BE3D-4CFE-9837-DF052F79A998@employees.org> <5bc3eaf0-3ef0-d954-b228-00a7faac7f4c@si6networks.com> <D7311FE6-27C9-4EC3-97A9-810BEF77D1D9@consulintel.es> <5a2165ec-0f7d-2158-1ee4-6ea87e68de3f@si6networks.com>
In-Reply-To: <5a2165ec-0f7d-2158-1ee4-6ea87e68de3f@si6networks.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rVCCDWFWwJnK_oN62raJSVd51ho>
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, 20 Feb 2019 06:02:25 -0000

Of course, not acceptable. I'm not saying that is not a problem to be solved, just tried to make the data more precise. My reading of your text was like "dynamic is over static".

Saludos,
Jordi
 
 

-----Mensaje original-----
De: Fernando Gont <fgont@si6networks.com>
Fecha: miércoles, 20 de febrero de 2019, 14:38
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, Ole Troan <otroan@employees.org>
CC: 6man WG <ipv6@ietf.org>
Asunto: Re: A common problem with SLAAC in "renumbering" scenarios

    On 20/2/19 01:56, JORDI PALET MARTINEZ wrote:
    > Well, significant ... 37% dynamic, vs. 63% static.
    
    Of course it's significant. Would you consider 37% failure rate acceptable?
    
    
    
    > And from the dynamic ones, 40% allows to be static. From that 38% charge extra cost for it (on top of stable IPv4, if provided).
    
    I don't care about "allows". Either it works by default, or it doesn't.
    If you expect a normal user to enter an ISP's web site and make
    decisions about prefixes or pay more to workaround the lack of
    robustness of what we ship, you are doing very bad engineering.
    
    
    It puzzles me that instead of trying to improve things, some seem to
    apply this problem-solving methodology:
    https://images-na.ssl-images-amazon.com/images/I/416cjJcmM-L.jpg
    
    Thanks,
    -- 
    Fernando Gont
    SI6 Networks
    e-mail: fgont@si6networks.com
    PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
    
    
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.