Re: exploring the process of self retiring one's name from an RFC
John C Klensin <john-ietf@jck.com> Fri, 19 April 2019 16:57 UTC
Return-Path: <john-ietf@jck.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 64572120185 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 09:57:14 -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, 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 MyrjIbgq9rfj for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 09:57:12 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9E1E12014E for <ietf@ietf.org>; Fri, 19 Apr 2019 09:57:11 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1hHWp3-000OhP-4H; Fri, 19 Apr 2019 12:57:09 -0400
Date: Fri, 19 Apr 2019 12:57:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Aaron Falk <aafalk@akamai.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
cc: IETF Discussion <ietf@ietf.org>
Subject: Re: exploring the process of self retiring one's name from an RFC
Message-ID: <15F35C17031A81BC457ED366@PSB>
In-Reply-To: <DF65DF27-5E66-472B-9888-0D123B63D1E8@akamai.com>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com> <DF65DF27-5E66-472B-9888-0D123B63D1E8@akamai.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QWhuAJBSJolQDNmdnIJclrpVaro>
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 16:57:14 -0000
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 --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
- exploring the process of self retiring one's name… Alexandre Petrescu
- Re: exploring the process of self retiring one's … Scott O. Bradner
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Jared Mauch
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Christian Huitema
- Re: exploring the process of self retiring one's … Behcet Sarikaya
- Re: exploring the process of self retiring one's … Keith Moore
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Eric Rescorla
- Re: exploring the process of self retiring one's … Paul Wouters
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Aaron Falk
- Re: exploring the process of self retiring one's … Paul Wouters
- Re: exploring the process of self retiring one's … John C Klensin
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … John Levine
- Re: exploring the process of self retiring one's … ned+ietf
- Re: exploring the process of self retiring one's … Marco Davids
- Re: exploring the process of self retiring one's … Brian E Carpenter
- Re: exploring the process of self retiring one's … Brian E Carpenter
- Re: exploring the process of self retiring one's … Brian E Carpenter
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Randy Bush
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Alexandre Petrescu
- Re: exploring the process of self retiring one's … Tim Chown
- Re: exploring the process of self retiring one's … Alexandre Petrescu