Re: Proposed ietf.org email address policy

John C Klensin <john-ietf@jck.com> Sun, 13 June 2021 23:57 UTC

Return-Path: <john-ietf@jck.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 CD3883A15B2 for <ietf@ietfa.amsl.com>; Sun, 13 Jun 2021 16:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 QGm9_zfI0J6A for <ietf@ietfa.amsl.com>; Sun, 13 Jun 2021 16:57:45 -0700 (PDT)
Received: from bsa3.jck.com (static-65-175-133-136.nh.cpe.atlanticbb.net [65.175.133.136]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479B33A15B1 for <ietf@ietf.org>; Sun, 13 Jun 2021 16:57:45 -0700 (PDT)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lsZxO-000HKQ-EI; Sun, 13 Jun 2021 19:55:58 -0400
Date: Sun, 13 Jun 2021 19:55:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Carsten Bormann <cabo@tzi.org>
cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF list <ietf@ietf.org>
Subject: Re: Proposed ietf.org email address policy
Message-ID: <CB9550F5FE92CCCC02B759F0@JcK-HP5>
In-Reply-To: <BFCE99A0-FB41-4B53-994E-AA7FFE1DEEE4@tzi.org>
References: <2BF6EC60-8B32-4171-B236-D9D038B3135B@yahoo.co.uk> <20210611174521.CD568F22E4A@ary.qy> <20210611182604.GA36947@faui48e.informatik.uni-erlangen.de> <ff6d912d-b0c6-4550-8d16-a79348e45699@dogfood.fastmail.com> <CAKKJt-enK4XmMuapke9LX-3TVuyg9j12zS9RyWXqvOT6Vbk5Mw@mail.gmail.com> <7606DFCE59EA95E72625E0FF@PSB> <26cf60f0-a007-a53f-f386-069526c31be4@cs.tcd.ie> <BB343401F7F2798A7EC7D196@JcK-HP5> <BFCE99A0-FB41-4B53-994E-AA7FFE1DEEE4@tzi.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rBTzwWZkZW3Lh4A2sVtmIt4tw48>
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: Sun, 13 Jun 2021 23:57:50 -0000


--On Sunday, 13 June, 2021 20:58 +0200 Carsten Bormann
<cabo@tzi.org> wrote:

> On 2021-06-13, at 19:47, John C Klensin <john-ietf@jck.com>
> wrote:
>> 
>> Would we really, really, want
>> questions about variations on SMTP addressed to me in 2021?
> 
> But would you have opted in?

That is where I might not be typical enough to make a good
example.  I seem to suffer from an odd, perhaps pathological,
sense of responsibility where the Internet is concerned.and sp
the answer to your question is "probably", especially if things
were set up so that the alternates to my signing up were people
tracking me down anyway (see Ned's note) or inquiries going to
somewhere other than a set or ADs who were enthused about the
mob.

> The only situation where easier access to the authors might be
> construed harmful is where the WG or IESG had to hamstring the
> author in order to obtain an acceptable outcome.  Private
> conversation with the author might not benefit from that
> influence.

This may be just a quibble, but there is a rather large
difference between "author puts something into a document on the
nistrutions of a WG with which they disagree" and "need to
hamstring or otherwise torture".  Depending on the circumstances
and personality of the author, "might not benefit" might set it
well before the authors needed to be subject to physical harm.

> But that is true for any kind of contact with the author, and
> a lot of people do find my email address in RFCs I have
> co-authored and manage to send email to that.
> 
> So with all the horror scenarios of people outside the IETF
> actually talking to authors, I still think this is a net win.

I agree with Ned and his explanation of why the balance we have
today is just about right.

best,
   john