IETF Logo Mail Archive

Re: Proposed ietf.org email address policy

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 11 June 2021 17:30 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 4D9A73A07A4 for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 10:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.5
X-Spam-Level: **
X-Spam-Status: No, score=2.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.398, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 Ry6x0TZWZdri for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 10:30:12 -0700 (PDT)
Received: from relay.sandelman.ca (minerva.sandelman.ca [IPv6:2a01:7e00::3d:b000]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B59523A0789 for <ietf@ietf.org>; Fri, 11 Jun 2021 10:30:12 -0700 (PDT)
Received: from dooku.sandelman.ca (cpe788a207f397a-cmbc4dfb96bb50.sdns.net.rogers.com [174.116.121.43]) by relay.sandelman.ca (Postfix) with ESMTPS id 0B94A1F47B; Fri, 11 Jun 2021 17:30:06 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id B7F8F1A02D3; Fri, 11 Jun 2021 13:30:03 -0400 (EDT)
Received: from dooku (localhost [127.0.0.1]) by dooku.sandelman.ca (Postfix) with ESMTP id B68281A00D8; Fri, 11 Jun 2021 13:30:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John C Klensin <john-ietf@jck.com>, Lloyd W <lloyd.wood=40yahoo.co.uk@dmarc.ietf.org>, IETF <ietf@ietf.org>
Subject: Re: Proposed ietf.org email address policy
In-reply-to: <B1B01A33410EEFCB89C5679D@PSB>
References: <59562F9B-8DDE-408C-ACCD-BC087FE86E1A@ietf.org> <2BF6EC60-8B32-4171-B236-D9D038B3135B@yahoo.co.uk> <B1B01A33410EEFCB89C5679D@PSB>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Fri, 11 Jun 2021 10:40:55 -0400."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 11 Jun 2021 13:30:03 -0400
Message-ID: <113183.1623432603@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gWiw3dSADoa3saGW-Uv8JexYDw0>
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, 11 Jun 2021 17:30:17 -0000

John C Klensin <john-ietf@jck.com> wrote:
    > --On Friday, June 11, 2021 16:35 +1000 Lloyd W
    > <lloyd.wood=40yahoo.co.uk@dmarc.ietf.org> wrote:

    >> Has the IESG considered renting out @member.ietf.org or
    >> @supporter.ietf.org addresses as a potential revenue stream?  Throw in
    >> a free github account to sweeten the deal and so that access to
    >> discussion is not unnecessarily limited.

    > Lloyd,

    > Prior experience with people being allowed to set up IETF-provided
    > mailing lists for discussions that seemed rather far out on the edges
    > of IETF work, deliberate misrepresentations of Informational RFCs or
    > even I-Ds as IETF standards, etc., suggests that it would be a small
    > jump from troll@member.ietf.org (and what is a "Member" or the IETF
    > anyway?), disrupter@supporter.ietf.org, or even
    > nutcase@participant.ietf.org from even worse misrepresentations about
    > positions and authority.

I see your point, so I suggest maybe it be restricted to people with
published RFCs.
Being able to put a stable contact into an RFC seems like a good thing to me.

I know we have draft-xxx@ietf.org aliases, and those can get updated via the
DT, I'm unclear if I can email rfcxxxx@ietf.org to reach the authors, and
that's not what's listed in the RFC.

As for member, supporter, etc. I'd suggest "contributor.ietf.org".

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [






--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email