Re: RFC4941bis implementations
Fernando Gont <fgont@si6networks.com> Thu, 02 April 2020 20:56 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 2CE8D3A19E2 for <ipv6@ietfa.amsl.com>; Thu, 2 Apr 2020 13:56:58 -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=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 bzxRSOeLoF_G for <ipv6@ietfa.amsl.com>; Thu, 2 Apr 2020 13:56:55 -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 31EC03A19DA for <ipv6@ietf.org>; Thu, 2 Apr 2020 13:56:55 -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 A8ADF893AD; Thu, 2 Apr 2020 22:56:49 +0200 (CEST)
Subject: Re: RFC4941bis implementations
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Fernando Gont <fernando@gont.com.ar>, ipv6@ietf.org
References: <7d65f86a-7a82-6139-b455-a27046496c52@si6networks.com> <af621915-ad9d-eb89-01d7-6ec7c5dfdd5e@gmail.com> <20c47838-8c66-8380-d3b2-5f48a787c8a9@gont.com.ar> <0b79c6ad-d045-700f-3907-445966493f41@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <4985af67-a59e-0521-d7f4-cc317181335d@si6networks.com>
Date: Thu, 02 Apr 2020 17:50:15 -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: <0b79c6ad-d045-700f-3907-445966493f41@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/ipv6/S9PEjmPsBotgYw1Vna08Go0JC_Q>
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: Thu, 02 Apr 2020 20:57:04 -0000
On 2/4/20 17:20, Alexandre Petrescu wrote: > Le 02/04/2020 à 21:21, Fernando Gont a écrit : >> On 2/4/20 16:09, Alexandre Petrescu wrote: >>> Le 02/04/2020 à 19:26, Fernando Gont a écrit : >>>> Folks, >>>> >>>> FWIW, I produce a patch for Linux kernel (net-next) that implements >>>> rfc4941bis: >>>> https://www.gont.com.ar/code/fgont-patch-linux-net-next-rfc4941bis.txt >>>> (up & running here). >>> >>> Does it work with a plen 65 in RA? >> >> No. Why would that matter in this context? > > That is another way to tell me to shut up in this context, which I will. > > Not before I tell that this patch is another way to write new software > propagating further in the future that limit. 1) Typically, you address one issue in each patch. This patch didn't remove support for non-64 prefixes. The support wasn't there. Since the patch needs to be reviewed, it is better for the patch to do one thing, that's clearly defined somewhere (rfc4941bis). One this gets solved, it is possible, if deemed appropriate, to improve on this patch and relax the requirement on the prefix length. 2) I'm not sure how winning solves problems. You haven't wrote a patch to implement rfc4941bis, and you haven't implemented a patch to relax the requirement on the prefix length, either. Still, you even have the idea of obstructing progress of rfc4941 out of frustration that rfc4941bis does not boil the ocean you'd like to boil. Thanks, -- Fernando Gont SI6 Networks e-mail: fgont@si6networks.com PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
- RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Alexandre Petrescu
- Re: RFC4941bis implementations Suresh Krishnan
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Florian Obser
- Re: RFC4941bis implementations Alexandre Petrescu
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Fernando Gont
- RE: RFC4941bis implementations Manfredi (US), Albert E
- Re: RFC4941bis implementations Mark Smith
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations otroan
- Re: RFC4941bis implementations Lorenzo Colitti
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Mark Smith
- Re: RFC4941bis implementations Fernando Gont
- Re: RFC4941bis implementations Bob Hinden
- Re: RFC4941bis implementations Tim Chown
- Re: RFC4941bis implementations Gyan Mishra