Re: RFC793#ietf.org (was: Re: Proposed ietf.org email address policy)

John Levine <johnl@taugh.com> Sat, 12 June 2021 02:34 UTC

Return-Path: <johnl@iecc.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 17CFC3A191D for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 19:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=i/GKkJ2S; dkim=pass (2048-bit key) header.d=taugh.com header.b=opzztWKv
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 AVzu5Acl_ifv for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 19:34:17 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2DCE83A191C for <ietf@ietf.org>; Fri, 11 Jun 2021 19:34:16 -0700 (PDT)
Received: (qmail 29227 invoked from network); 12 Jun 2021 02:34:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=7229.60c41d26.k2106; bh=2hrxjPN/r3pSHrmLhzHYI24R9CKnO3AqZguxO7npYUk=; b=i/GKkJ2S9LQliiZcTGUF8ARjLzyqoPPpYR3Ta17URnp1VYh27Pi/rPjp9hxM29etUERyGi7Ve+4kIMDq4KzZ0JuYGASPKuetWK+jY9ZxDkkCuzGHAGV2NrlQS8QoiuGzlbQdiLtKgbL9+qedyTDoY6v3lzjL8X66Ghy7RxlvtiObI/Uf3yKwNHDcaBJenRdESkCj3NkwtFeNrQQUfU3AgjdEMvOrl/jQ7FV0pouquqkdCtPodTr0Jon2sW5dKGe9FQJn3q+9RZbkZ+hvLgXlMewZrXq9Ba4YhU/61mg7oosPvF9X3x4YbvB5tbPzbwtvHPfl/ybXbHY60knXtXYcGA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=7229.60c41d26.k2106; bh=2hrxjPN/r3pSHrmLhzHYI24R9CKnO3AqZguxO7npYUk=; b=opzztWKvhcF6qtz9eBiy+xo2XMtF330Yx1w6dWpHLHzWOhDWAFRoCKFkYuJXCFbOyQ/6jDMNWIYE7qyc366mEwvaEzKVZzkFfslyAKONlhN7QGN/701xHL9zPDI86Y4XS7sgOqa74iqJUqrl6xZu7jlQf7eHftmsdAzs8rqmnYgfpp4vl0pMTZUrD0/+4y8+2BFnfth0RrWnXRkMbmNgWNrlNUpkY03tGwt55NvuGcygHLaWlnM0xbDHJKOIQv5s+5daUqfUXtLXh7KHfS/nGA3SMmvdPuzq7VD6AAXmVG1aBJzoTQuvpHtP5/fHKhZ7jSKfYwauecFugNbns4R7kA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 12 Jun 2021 02:34:14 -0000
Received: by ary.qy (Postfix, from userid 501) id E5745F704B5; Fri, 11 Jun 2021 22:34:12 -0400 (EDT)
Date: Fri, 11 Jun 2021 22:34:12 -0400
Message-Id: <20210612023413.E5745F704B5@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Cc: john-ietf@jck.com
Subject: Re: RFC793#ietf.org (was: Re: Proposed ietf.org email address policy)
In-Reply-To: <151B3820DCC0A23EA1C58063@PSB>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nybGj0hxdGwR3bjpu6rfpQ8YzQw>
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: Sat, 12 Jun 2021 02:34:23 -0000

It appears that John C Klensin  <john-ietf@jck.com> said:
>For whatever it is worth and IIR, the RFC Editor made an effort
>to keep an up-to-date list of contact addresses for RFC authors
>25 or 30 years ago.  It was a complete failure, at least in the
>sense that it became clear that it would have required a large
>amount of ongoing outreach and tracking-down effort on the RFC
>Editor's part to even have hope of keeping things up to date.
>And that was when we were published far fewer RFCs -- for
>example, only around 135 in CY 1995; harder to guess for recent
>years because of the number of documents being published out of
>chronological order, but I'd guess much larger.  And, again
>subjectively the number of authors of whom one would need to
>keep track has also grown significantly.   I assume John Levine
>has much more exact figures if anyone cared, but I really
>suspect this is a dead end without a commitment of significantly
>more energy and resources than it is worth.

Since we switched to XML in Oct 2019, there have been 687 unique
author addresses. Below is the unsurprising list of all of the domains
with more than two addresses.

We've managed for 50 years without a system to track contact info and at this
point it would be a frustrating full time job to try and do so.  We are already
seeing a lot of authors using gmail for stable addresses and I don't see any
reaspon to try to duplicate that.

R's,
John

('gmail.com', 100)
('cisco.com', 65)
('huawei.com', 24)
('juniper.net', 20)
('google.com', 20)
('ericsson.com', 18)
('nokia.com', 9)
('verisign.com', 8)
('orange.com', 7)
('isc.org', 6)
('att.com', 6)
('apple.com', 5)
('intel.com', 5)
('chinamobile.com', 5)
('ieee.org', 4)
('interdigital.com', 4)
('microsoft.com', 4)
('telekom.de', 4)
('chinatelecom.cn', 4)
('zte.com.cn', 4)
('telefonica.com', 4)
('icann.org', 3)
('ifi.uio.no', 3)
('sinodun.com', 3)
('fb.com', 3)
('bupt.edu.cn', 3)
('cloudflare.com', 3)
('yahoo.com', 3)
('telecom-paris.fr', 3)
('alibaba-inc.com', 3)
('arm.com', 3)
('amazon.com', 3)
('vocal.com', 3)
('nist.gov', 3)
('fh-muenster.de', 3)
('nlnetlabs.nl', 3)
('inria.fr', 3)
('futurewei.com', 3)