Re: [Errata Held for Document Update] RFC8200 (5933)

Fernando Gont <fgont@si6networks.com> Wed, 04 March 2020 12:32 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 EE7BE3A0DE3 for <ipv6@ietfa.amsl.com>; Wed, 4 Mar 2020 04:32:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01, 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 LPPwEKBXINOt for <ipv6@ietfa.amsl.com>; Wed, 4 Mar 2020 04:31:53 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2125E3A0DDE for <ipv6@ietf.org>; Wed, 4 Mar 2020 04:31:53 -0800 (PST)
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 B4FE383425; Wed, 4 Mar 2020 13:31:46 +0100 (CET)
Subject: Re: [Errata Held for Document Update] RFC8200 (5933)
To: Ole Troan <otroan@employees.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, ipv6@ietf.org
References: <253810a2-bc07-5673-fb22-92d0f435888c@gmail.com> <24FB4746-5D9B-4A3C-A0A2-021AFFCC77FC@employees.org>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <f9939751-23f6-e15b-5e35-88a62ef1402b@si6networks.com>
Date: Wed, 04 Mar 2020 09:01:48 -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: <24FB4746-5D9B-4A3C-A0A2-021AFFCC77FC@employees.org>
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/VvIqteZdfp4oz6HRKUDTtvYCUI0>
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, 04 Mar 2020 12:32:04 -0000

On 4/3/20 04:21, Ole Troan wrote:
> 
>> On 3 Mar 2020, at 22:43, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> I didn't know what we meant to say, because I never thought for one
>> moment how the text applied to routing headers, where the destination
>> address essentially becomes a variable instead of a constant, and where
>> the Segments Left field is mutable by construction. So it isn't a "flea";
>> IMHO it's a major omission. (I feel a bit guilty, because we first missed
>> it in RFC7045.)
> 
> You should not feel guilty.
> Isn’t the IETF mantra to write specifications to ensure interoperability. The goal isn’t to write enough legalese to prohibit future uses (or abuses) of the specifications. 

Isn't there a procedure to update existing specs, when needed?  -- 
that's what some of us have been arguing about...

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492