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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 19 April 2019 23:52 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 A1698120479 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 16:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 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, 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 a10nVCjAcReI for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 16:52:23 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 0134E1201AC for <ietf@ietf.org>; Fri, 19 Apr 2019 16:52:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JNqHWM039597; Sat, 20 Apr 2019 01:52:17 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 79528206AAB; Sat, 20 Apr 2019 01:52:17 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 68FD32069C1; Sat, 20 Apr 2019 01:52:17 +0200 (CEST)
Received: from [10.8.68.1] ([10.8.68.1]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JNqETI022913; Sat, 20 Apr 2019 01:52:14 +0200
Subject: Re: exploring the process of self retiring one's name from an RFC
To: John C Klensin <john-ietf@jck.com>
Cc: Aaron Falk <aafalk@akamai.com>, IETF Discussion <ietf@ietf.org>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com> <DF65DF27-5E66-472B-9888-0D123B63D1E8@akamai.com> <15F35C17031A81BC457ED366@PSB>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <0c36fc88-34c9-0131-8e84-620650183f13@gmail.com>
Date: Sat, 20 Apr 2019 01:52:14 +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: <15F35C17031A81BC457ED366@PSB>
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/R4EKJYj-oOTHKdIx92gQAeZ4D0M>
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 23:52:26 -0000


Le 19/04/2019 à 18:57, John C Klensin a écrit :
> Alex,
> 
> With all respect to the other suggestions, Aaron has it right.
> Interestingly, he is proposing a solution that has was on the
> radar for 30 or 40 years (and I presume is still).   The
> solution to a problem with an RFC, _any_ problem, is another
> RFC.  Publishing the same document without your name on it is
> probably a non-starter, not only because all of your co-authors
> would need to agreed, but because the new document would need to
> go through the same review, Last Call, and IESG decision process
> the first one did and find it hard to imagine that would not end
> up requiring some rewriting as well as taking up a lot of time.
> But writing a critique and trying to get it published is always
> in order.
> 
> I would suggest one variation on Aaron's suggestion: rather than
> going directly to the Independent Submission Editor, have a
> discussion with one of the relevant ADs about a commentary,
> revised analysis, or other explanation about possible
> sponsorship for publication in the IETF Stream.  If you can get
> agreement to do that (and you are willing to put in the work),
> you could structure the new document to update with existing one
> (not by removing your name but by providing new information to
> the community).  Upon publication, that would result in "updated
> by" information in the metadata of the original and make your
> position much more obvious than simply publishing a critique.
> That would be much harder to accomplish with an Independent
> Submission because cross-stream updates have historically been
> contentious for various good reasons and possibly a few bad
> ones.  If the AD(s) are not receptive, the Independent Stream is
> an obvious second choice but, as Aaron hints, such a submission
> would almost certainly have to be about "why that was a bad
> idea" or "why you are more convinced it is a bad idea now than
> you concluded at the time".
> 
> Just to get your name removed, or even getting a subsequent
> document published to remove it, is likely to be impossible; the
> price of the nearest approximations is that you will need to do
> some substantive and informative writing.

John,

Thank you for the suggestion of a separate document.  It makes sense as 
you describe it.  I would be the only author of that new document and, 
if approved, it would express better what  I wanted to say in the first 
place.

I will see whether an opportunity may arise.

Alex
> 
>      john
> 
> 
> --On Friday, April 19, 2019 11:59 -0400 Aaron Falk
> <aafalk@akamai.com> wrote:
> 
>> On 19 Apr 2019, at 6:00, Alexandre Petrescu wrote:
>>
>>> I consider using such process to retire my name from the RFC
>>> that analyses the 64bit boundary analysis.
>>>
>>> For some reason I got in that group, then participated
>>> positively to  the
>>> discussion, and I let myself tempted to have my name up on
>>> the first page of a published RFC; but finally, after much
>>> time and reflexion, I think I do not agree with the effects
>>> of this RFC.
>>
>>
>> Sounds like you may want to write an independent submission
>> RFC on why you now think RFC7608 is a bad idea.
>>
>> --aaron
> 
> 
> 
> 
>