Re: exploring the process of self retiring one's name from an RFC

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 19 April 2019 15:09 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15767120159 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 08:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 ShvLYRAlLw_0 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 08:09:19 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D2A1202F1 for <ietf@ietf.org>; Fri, 19 Apr 2019 08:09:18 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JF9CM5146960; Fri, 19 Apr 2019 17:09:12 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9E030200DE7; Fri, 19 Apr 2019 17:09:12 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8E2A62069E9; Fri, 19 Apr 2019 17:09:12 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JF9CLQ026323; Fri, 19 Apr 2019 17:09:12 +0200
Subject: Re: exploring the process of self retiring one's name from an RFC
To: Christian Huitema <huitema@huitema.net>
Cc: Jared Mauch <jared@puck.nether.net>, IETF Discussion <ietf@ietf.org>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com> <00fde7c6-c8a4-508e-5735-056647cdfb52@gmail.com> <9E3D5C77-C1C8-4D22-97BF-B97324C7DFCC@puck.nether.net> <13a585d3-ff7c-757d-3f5d-d60be289e0d1@gmail.com> <FE3CDAA5-CF0E-4D19-8985-76BAEEEC9E36@huitema.net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b94d0cd7-0ca2-4072-3f2a-ef387406c2b0@gmail.com>
Date: Fri, 19 Apr 2019 17:09:12 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <FE3CDAA5-CF0E-4D19-8985-76BAEEEC9E36@huitema.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rWRnhNCAfdEF3I8ZXdJ1g_v9Afc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Apr 2019 15:09:22 -0000

Christian,

Le 19/04/2019 à 16:09, Christian Huitema a écrit :
> 
> 
> 
>> On Apr 19, 2019, at 5:18 AM, Alexandre Petrescu 
>> <alexandre.petrescu@gmail.com> wrote:
>> 
>> With respect to questioning the kinds of comments that could be 
>> put:
>> 
>> - it's not because the technology has changed that I need my way 
>> removed from it.
>> 
>> - there is no new risk profiles.
>> 
>> - the reality has bent in the sense that the 64bit boundary seems 
>> to be imposed now in all new IPv6-over-foo RFCs.  It was so in the
>>  past (before the RFC), and I was hoping the RFC to change that 
>> tendency.  The reality is that since that RFC many other 
>> IP-over-foo documents have been written, and each time the 
>> recommendation is still to use 64bit IID.  That was not my 
>> intention when co-authoring that RFC.  I got into it to falsely 
>> believe the recommendation would happen in - what was at the time -
>> the future.
>> 
>> With respect to improved usefulness of a perpetual archive to 
>> insert up to date feedback (comments answering the Request for 
>> Comments): I think it sounds natural and it makes sense.  That can
>>  not be the email list of the WG having developed the RFC, because
>>  it gets shut down.
>> 
>> That perpetual archive can not be a new Internet Draft because that
>> expires if not adopted by a WG, which is itself subject to come and
>> go of people.
> 
> In short, you are asking to remove your name of the authorship of and
> RFC because if you knew then what you know now, you would not have
> written the paper that way, nor signed it.

YEs.

> Think about it.
> 
> People change opinion all the time, for lots of reasons.

But I did not change my mind!  I always wanted the 64bit boundary
removed - then and now and in the future.  I was in the hope that that
RFC would help.

The events happened in such a way that that RFC hurts instead of
helping.  People read it as if it is a recommendation to use 64bit
boundaries.

> Everybody makes what they think are mistakes. But the record is the 
> record, and you don't get to change it.

I agree.

> You filed an errata to remove your authorship. That errata should be
>  rejected, because the document is not actually erroneous. It states
>  that you were one of the authors at the time of publication, and 
> there is no doubt about that. There is no error.

I tend to agree.  Another person told me in private the same thing.

All I can do now, and I did, is to request an errata.  I agree if it is
rejected. I will take greater care next time when opportunities to
author documents arise - they may be worth considering, others should
rather be avoided.

Alex
> 
> -- Christian Huitema
>