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

Martin Thomson <mt@lowentropy.net> Thu, 18 February 2021 08:57 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 D70B53A0E1E; Thu, 18 Feb 2021 00:57:32 -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=AHFO2YpU; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=B89AKcNS
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 fC5oPHg8pGsz; Thu, 18 Feb 2021 00:57:31 -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 198F63A0E1B; Thu, 18 Feb 2021 00:57:31 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 982E5F4070A; Thu, 18 Feb 2021 00:57:26 -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 D099FF4070A for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 00:57:24 -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=AHFO2YpU; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=B89AKcNS
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 RWv24fiPJGpH for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 00:57:23 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by rfc-editor.org (Postfix) with ESMTPS id 0109BF40709 for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 00:57:22 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3EA135C0172 for <rfc-interest@rfc-editor.org>; Thu, 18 Feb 2021 03:57:26 -0500 (EST)
Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Thu, 18 Feb 2021 03:57:26 -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 :subject:content-type:content-transfer-encoding; s=fm1; bh=oS8Ep UFk3eOqd8M0b8d9r8AFrvkTaEbGr2o0aaMgCMY=; b=AHFO2YpUl+7w1aRZnwu94 GoJjHMMmG4CyjeZTjYkBkPytAnKvHUdupYiRVRLWsX3mlfSV7Zqkr4mXCqu6j5tZ l5megqUKXUCFe5pc5rVPxQSOidulH0SuIjdhG5qiZUnTYvJS8R2UeqW+kwNlnfYg FN7lJb+lunTRrf9G8+LFymjfs+R+b8093s2Oh4iTI9BfUjAwSgQhT/roU6lVvve1 QcPq51aFJgriOLSQcoQHlv8+h0yycB0kJcVcuaaw8PaOB50oW1/SVfPd1vZPoeAw 4AsHKuAsX5v3CT9ZPROJ7XSzg2HsJQpIBecV7gyPbjh6JGSQX3a1d7NbcINqKsMW Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=oS8EpUFk3eOqd8M0b8d9r8AFrvkTaEbGr2o0aaMgC MY=; b=B89AKcNSyHY+aMtpAWgT5zyIQOJs6mWBO7ga/Pdrexl2J7GQVtvGWPPTW zXALg4mvikyLMIcoTZ5/PLfZAyJdT72qvsvdzB65Ya/svnYsbcorcaxjpzo7dKfF NtG8uv4bIZ3phfqjqS7J89dLGEMiwn6hkVGmcyuaKGuSwU9U569+RK3NUHc1f61Z fZ9P/qojklDDC5V2wV2hjTnZCTcCsaEtaFpto2xVjOBdfVDVhqcrT26Ng3l4RBK4 hZOxNE4UXAY1qHX6ZK5qWzxaD1G+Sm164n/r45r+KJecTN0xgmJVdMNH5TRFZG68 4t6ZxuKlG8BuWQkGQkeGziMELA7jQ==
X-ME-Sender: <xms:9SsuYLVmWpRa26RpUQJgMcvWXK9A-JrIdQst6tm_UlHc6dN_RL0Efg> <xme:9SsuYDl1lk_I87i7PAj7zyn9wPr1jHcpO3myBjuV9iE4_0ZffAPZ7gdLd6VYo917o S9v6mQlDYZm701g3eY>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrjeefgdduvdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfejueduieffledtge elheejvdettdejudduhefggeefgfekgfeuieetgefftddtnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnh gvth
X-ME-Proxy: <xmx:9SsuYHZ3TYZBQG53I6tagHIZX45FcejjpVIHcM7LiY4hX83nSzspRg> <xmx:9SsuYGVN-4GR_Cc8p521XJZ-5B2q_Pl1RMWpZEkFTl2RDBEhvPAIJw> <xmx:9SsuYFl26ErnOpqFO_YvU0OVGfFVE8NszBrj_xb0nWv89nX200VPGA> <xmx:9isuYBwT6xT7OcQMBDVbMDReXEP_CzF_sv7fRoEgCnrh2dIpYalEBw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 14CAF4E0080; Thu, 18 Feb 2021 03:57:25 -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: <6a08f9e7-00e3-4c21-8619-400890b8ef98@www.fastmail.com>
In-Reply-To: <9578884e-8437-239f-5dc2-cb4c153a9e4e@gmx.de>
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>
Date: Thu, 18 Feb 2021 19:57:04 +1100
From: Martin Thomson <mt@lowentropy.net>
To: rfc-interest@rfc-editor.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>
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 19:06, Julian Reschke wrote:
> There are two questions here:
> 
> 1) Should we "fix" references to contain something that actually is not
> in the referenced document (such as a non-ASCII character in an author
> name)?

This was the only question I was asking, but you are right to ask the second as well, as it informs how we might manage the answer to this best.

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.
 
> 2) Should we change the published reference files to use v3 features
> (such as extensions to the content model and support for non-latin
> characters in names and titles)?

I see a few options:

1. Declare end of life for the v2 format and work toward getting fixed references.
   (with or without the first question being answered)
2. Make a new location for references in the v3 format.
  2a. Stop adding new references to the old location after a fixed date.
3. Let the tools manage the transition.

Option 2a is where I would try to go.  It's a little more costly, but it provides a clear upgrade path and a bit of incentive to follow.  I understand that people will want some notice, but we're far enough along with the v3 format that a little nudge is probably good.
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest