IETF Logo Mail Archive

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

"Scott O. Bradner" <sob@sobco.com> Fri, 19 April 2019 10:14 UTC

Return-Path: <sob@sobco.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 A758D1202D0 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 03:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level:
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no 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 FriKwklefc0t for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 03:14:18 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id D6E201202C2 for <ietf@ietf.org>; Fri, 19 Apr 2019 03:14:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id CA9E0F33B8A; Fri, 19 Apr 2019 06:14:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GB-qds2kXdA; Fri, 19 Apr 2019 06:14:16 -0400 (EDT)
Received: from [192.168.50.224] (173-166-5-67-newengland.hfc.comcastbusiness.net [173.166.5.67]) by sobco.sobco.com (Postfix) with ESMTPSA id AC75FF33B64; Fri, 19 Apr 2019 06:14:16 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: exploring the process of self retiring one's name from an RFC
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com>
Date: Fri, 19 Apr 2019 06:14:15 -0400
Cc: IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2757BCB3-0390-46DE-BD04-CF252DE6E1BC@sobco.com>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xs627rmvphkt2svDnPovYHHVMVk>
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:14:29 -0000

RFCs are not changed after they are published so removing one’s name from a existing RFC cannot be done.

Scott

> On Apr 19, 2019, at 6:00 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> 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