IETF Logo Mail Archive

Re: [rfc-i] Fixing names in references to old RFCs

Martin Thomson <mt@lowentropy.net> Thu, 18 February 2021 10:25 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2E623A0FB0; Thu, 18 Feb 2021 02:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=lowentropy.net header.b=FP0XF4C3; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=ByChNfzr
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 Ci2aEDPZxizj; Thu, 18 Feb 2021 02:25:02 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46A603A0FAD; Thu, 18 Feb 2021 02:25:02 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E8F9AF40720; Thu, 18 Feb 2021 02:24:57 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id B8E28F40720 for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 02:24:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=FP0XF4C3; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ByChNfzr
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbmbwPi-lfRS for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 02:24:55 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by rfc-editor.org (Postfix) with ESMTPS id A9BFAF40716 for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 02:24:55 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0169F5C0045; Thu, 18 Feb 2021 05:24:59 -0500 (EST)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Thu, 18 Feb 2021 05:24:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type:content-transfer-encoding; s=fm1; bh=sz GpBI6NxuypWK8QZOWPeLOEo+4rMDzucwgcAs5oXps=; b=FP0XF4C3chbB76/ici uwiq8tYJ++GmkGyKehdTvb3qmBaI376cISK5vlh3Vdjo/LW0FVURMFQcPnuc0CXF w1GXPI5lcxYVUsLHZobxHEdFzgVz4F+RBKTgiszZs0+nlLGVMpgVCNEspAatJ6Yd KaVZfQRRRJu2HpJCG49ywBkWgU+aD2inznSJYABXydaBnsLpZCHkW1IyBOm9n4lO /pjrQYeqpPbXna+bprli5NW2jBwvGkcCtUnPUs2cfPgh6xiwqd2YDVCn/mA3EUm7 ufZswoK28AmtU17OZ5W5xvjaCP+0Ejc9uf4CVk2/cwt/bk6H7n/t1NMwb57QPaYz mi2A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=szGpBI6NxuypWK8QZOWPeLOEo+4rMDzucwgcAs5oX ps=; b=ByChNfzrL8rN5qVkpR0EeJg1dd3/700iFY6Id8Uv2j3ysVuvOPFu/r8re nLlQShilEvz3XydK6KC9+jFUqoa6ZmUGeb8hMzkHBMveUjU8GHOEm6dOvDHzwByq Q4bC2lAARNGDn6wWn4x6O7hWKMiDATuRLZyBlFL9V4v3roiIBY/C/6IjX6KlHjlY McXxOArmNL3YTb02NKGey6tyRvEDwGkjNU70RmQ8IRF2ixPP/CezUeEaQ6sYzdth dejhaLWTiTsGcybHvwJ5MjL4djBRZu8DIdzWE9Fh85oMuXEqOpVWmkYN/2AL8uwW rTlO98qQfXLclKq38G4isI+J1MYrQ==
X-ME-Sender: <xms:eEAuYMbsRQxHuLhagJvhhDgG8L0NFVEG0ryRcz78P1MjPQvf6JJoKA> <xme:eEAuYHbQ_U63HBFQkgOXJRdYiyk0vMXh3pUG4VJ9KIHkiO-nKekTaYXEa_XoEn5Nt HBZDgSegG7SQIa3WWQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjeeggddugecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecugg ftrfgrthhtvghrnhepgfejueduieffledtgeelheejvdettdejudduhefggeefgfekgfeu ieetgefftddtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrh homhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:eEAuYG8ehCMikb983rnzunxaHbMjyZXBWZW7DsrobaQNKG2g6BqKdg> <xmx:eEAuYGob0GcFb68-948H91eq0kaCnfQ61EeSJkt4Bm8PB147QXrwIA> <xmx:eEAuYHqsOJr_wsvolBP4pyXr5c_YIzub3QfuPafjA9OZSk6ZSpNY2Q> <xmx:ekAuYBFcA67cHYDi83_qFRpD2-coduPgmD5iMUDRkSi0gJ77HsinRg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id A6C0B4E0080; Thu, 18 Feb 2021 05:24:56 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-141-gf094924a34-fm-20210210.001-gf094924a
Mime-Version: 1.0
Message-Id: <f005f1f1-4b2a-4839-bb09-c143c5ee6b18@www.fastmail.com>
In-Reply-To: <FD1B0C71-87D1-4C1A-8DEB-2A72852F77F3@tzi.org>
References: <c6acbb0e-e96a-4b88-9b41-8cc5e03773bc@www.fastmail.com> <1ca206fd-dfe0-4c23-4161-b5cbd65dd841@gmx.de> <9070FA66-ECC7-4C82-8DEF-30CAEE473894@tzi.org> <9578884e-8437-239f-5dc2-cb4c153a9e4e@gmx.de> <6a08f9e7-00e3-4c21-8619-400890b8ef98@www.fastmail.com> <FD1B0C71-87D1-4C1A-8DEB-2A72852F77F3@tzi.org>
Date: Thu, 18 Feb 2021 21:24:36 +1100
From: Martin Thomson <mt@lowentropy.net>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: [rfc-i] Fixing names in references to old RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On Thu, Feb 18, 2021, at 20:11, Carsten Bormann wrote:
> > For the moment however, I just want to know if manually rewriting oe to ö would be a reasonable thing to do.  I think that it would.
> 
> Hmm.  Some people are actually changing their names for various 
> reasons; what do you do with that?

Well, this wasn't a name change.  It was the RFC format being unable to represent this person's actual name at the time the document was published.

> In academics, we generally keep the names as they were published in the 
> referenced document (which is really bad for the citation counts of 
> people who change their names).

I did almost have a name change in references too, for which I would probably have had a discussion with that person, but I think we're removing that particular reference.  I expect that the academic standard here you talk about is the right one, but I would still want to ask because I am uncomfortable with deadnaming in that way, at least without seeking permission (or maybe at least forgiveness).
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email