IETF Logo Mail Archive

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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 19 April 2019 10:00 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 D7619120122 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 03:00:47 -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 4vMMbnBPNRYh for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 03:00:46 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 722E7120041 for <ietf@ietf.org>; Fri, 19 Apr 2019 03:00:46 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3JA0hIf008119 for <ietf@ietf.org>; Fri, 19 Apr 2019 12:00:43 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A0225205F8D for <ietf@ietf.org>; Fri, 19 Apr 2019 12:00:43 +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 89DB7205CFB for <ietf@ietf.org>; Fri, 19 Apr 2019 12:00:43 +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 x3JA0g4U017846 for <ietf@ietf.org>; Fri, 19 Apr 2019 12:00:42 +0200
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: exploring the process of self retiring one's name from an RFC
To: IETF Discussion <ietf@ietf.org>
Message-ID: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com>
Date: Fri, 19 Apr 2019 12:00:42 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MfhTpsB38lJUo26njWw7HLJTmww>
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 10:00:48 -0000

Hi IETFers,

I would like to ask whether there is process steps to retire one's name
from a published RFC.

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.

(I know there is common practice to retire one's name from a Work in
Progress Internet Draft - suffices it to ask - but I dont know whether
the same can be done with a published RFC).

Alex

v2.23.0 | Report a Bug | By Email