IETF Logo Mail Archive

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

Jared Mauch <jared@puck.nether.net> Fri, 19 April 2019 11:55 UTC

Return-Path: <jared@puck.nether.net>
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 D04371201AB for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 04:55:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 F7SC95SzAbF2 for <ietf@ietfa.amsl.com>; Fri, 19 Apr 2019 04:55:39 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9246812016D for <ietf@ietf.org>; Fri, 19 Apr 2019 04:55:39 -0700 (PDT)
Received: from [IPv6:2603:3015:3606:cbe1:b4c4:32f9:e9f:7c15] (unknown [IPv6:2603:3015:3606:cbe1:b4c4:32f9:e9f:7c15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id BE87D5407B0; Fri, 19 Apr 2019 07:55:37 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: exploring the process of self retiring one's name from an RFC
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <00fde7c6-c8a4-508e-5735-056647cdfb52@gmail.com>
Date: Fri, 19 Apr 2019 07:55:37 -0400
Cc: IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E3D5C77-C1C8-4D22-97BF-B97324C7DFCC@puck.nether.net>
References: <1a0ba1ad-9e32-4663-208c-f94f4f0306de@gmail.com> <00fde7c6-c8a4-508e-5735-056647cdfb52@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fRdizditSB8XxLQbtSLYzjeBsa0>
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 11:55:41 -0000


> On Apr 19, 2019, at 7:28 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> Hi Scott,
> 
> Thank you for the reply.
> 
>> 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 UTCShow
>> header
>> RFCs are not changed after they are published so removing one’s name
>> from a existing RFC cannot be done.
> 
> Errata?

Perhaps.  They are requests for comments.  One of the comments may be that technology has changed, or risk profiles (or any number of other assumptions or realities have been bent).  I think retiring authorship isn’t really a useful way, but is the perpetual archive of comments just the e-mail archives or should there be a more prominent way for an author to submit comments for the historical record?

- Jared

v2.23.0 | Report a Bug | By Email