Re: Proposed ietf.org email address policy

Bron Gondwana <brong@fastmailteam.com> Sat, 12 June 2021 13:51 UTC

Return-Path: <brong@fastmailteam.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 86E023A13AE for <ietf@ietfa.amsl.com>; Sat, 12 Jun 2021 06:51:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, HTML_MESSAGE=0.001, 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=pass (2048-bit key) header.d=fastmailteam.com header.b=MiPqGNyD; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Qr2AZreZ
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 VJuRtTUq8ZEm for <ietf@ietfa.amsl.com>; Sat, 12 Jun 2021 06:51:03 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D64183A13A4 for <ietf@ietf.org>; Sat, 12 Jun 2021 06:51:03 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 60876163C for <ietf@ietf.org>; Sat, 12 Jun 2021 09:51:02 -0400 (EDT)
Received: from imap42 ([10.202.2.92]) by compute2.internal (MEProxy); Sat, 12 Jun 2021 09:51:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:subject:content-type; s=fm2; bh=o8b12kK eGQq4+al4UsjcLzgIzryILZtXol5ZKxxcsD4=; b=MiPqGNyDB41TRX1UPLYzpSP iacn8ngX9ykqrQeWhbzTMng7VjWKt4IMZKAFVIpbyHRwsMt4Vvja5mrcTGenibKr AqV6OiErHCztfkADdvoR8eFV7/ixksc5YmwKR6wf7W498dD+rT3lkAf+1droawPA rNFIse7ftxaGhVt8aSsZjL3pkeO2CSuwA7HGdsfUE1Bkyb2M3mzfi0ZT7OvUg/bK tvNaa5twDd/uP0jMurhts7aRxDM4MREbgGGZMD0Ck3RynsgyrnRI+KDAla4kMeWL NSDQf0n6cqWcc3WweC4xH7Asy+p2sLoP2Zl8leFbG78UiOHGKJya7QYRTFtP0Cw= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm3; bh=o8b12k KeGQq4+al4UsjcLzgIzryILZtXol5ZKxxcsD4=; b=Qr2AZreZKH3g4lwhVrjDko xUxlleVEI6WjWS8+PVvv0WhBgCYKbh4yQAcnM4x1H2n+GyRCy/0Pb6qh7BN9x+MW atXw2zDwbk/vV2+HdhwJMlVmlxRAWEV71lyGDqPzaw1uIdznlwUCngRzy9bhoNM5 DpVzXHkidG7HU7QqCkRezNBuR8Fz8ipHDccIuwAK+pFpN4vb9MEnSrucD1obVL2/ E+KX8Ep3RpbG085wdChxOI5YBDhT3tj6/C+cf1zkZ0vOk6bXiTh7QgDakdgSiF6q iKRqw/yhx105f2CR02eeJkvJ70mY+OvADZL1N3X31cO/k5xaCtHZfUsVZqqiFskQ ==
X-ME-Sender: <xms:xbvEYCrAWNP8mqmymkz4ZwrJctGg9osSsRSs1XBvdkipQ4m6enczqA> <xme:xbvEYAqqHZSeGVLsYUQ0PiRRVoLvUYR5eRmNCuTDbXQ14xgUn8fnY5JcLSU6itxxw qzizRNB-gQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedvtddgjeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsegrtd erreerredtnecuhfhrohhmpedfuehrohhnucfiohhnugifrghnrgdfuceosghrohhnghes fhgrshhtmhgrihhlthgvrghmrdgtohhmqeenucggtffrrghtthgvrhhnpeffveefiefgje evteehheelgeetleetveeguedthfehgffhtdejhfdvhefhtdekgfenucffohhmrghinhep ihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomhepsghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:xbvEYHO6_huMyK7kH5uqUsWnaJIH04HERzlVdzEFM3sR8XUnmNaQNQ> <xmx:xbvEYB4h4KeWHdQqxvfpR2TNajHJAMsRtaJ48RQcktfaC0-TmhWv1Q> <xmx:xbvEYB7SGqAfPQV7V1pyfy0pv_aMeHgOUNXBGQI1OBecoYsJSbJKOg> <xmx:xrvEYDFGLcZczMUjc8O6W857IBYLRRI2RSAPUbqSA14PA20OKjfvqw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4DD123100062; Sat, 12 Jun 2021 09:51:01 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-808-g1bcb13b751-fm-ubox-20210609.006-g1bcb13b7
Mime-Version: 1.0
Message-Id: <ff6d912d-b0c6-4550-8d16-a79348e45699@dogfood.fastmail.com>
In-Reply-To: <20210611182604.GA36947@faui48e.informatik.uni-erlangen.de>
References: <2BF6EC60-8B32-4171-B236-D9D038B3135B@yahoo.co.uk> <20210611174521.CD568F22E4A@ary.qy> <20210611182604.GA36947@faui48e.informatik.uni-erlangen.de>
Date: Sat, 12 Jun 2021 23:50:40 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: ietf@ietf.org
Subject: Re: Proposed ietf.org email address policy
Content-Type: multipart/alternative; boundary="3eb14172f9b94f928b0b7bfbd610c3b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sqI5S3l9t54TnoX-m7uphZhQHEw>
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 13:51:11 -0000

On Sat, Jun 12, 2021, at 04:26, Toerless Eckert wrote:
> I guess whoever is in support of such email adresses could
> write an RFC, and i think it should include proposals how
> to create such a service.
> 
> I am not on top of the email business these days, but i would
> be surprised if there where no commercial email providers where
> some operationalizing option could be made to work if there was interest:
> 
> Something like:
> 
>   a) members.ietf.org Is handed over to that company (SOA, MX, whatever is needed)
>   b) provider comes up with charging model, IETF is not involved in anything.
>   c) Upon opening account, some authentication with datracker is done,
>      e.g.: open a <whatever>@members.ietf.org email account you need
>      to prove to be owner of a datatracker account.
> 
> Just one option. Maybe more interesting to IETF:
> 
>   a) During registration for IETF, one is offered to pay extra
>      for an N-month (renewal) of email-forwarding for some $XXX.
>   b) The email forard is set up via cloudflare email forwarding app,
>      given how IETF is already using cloudflare.
>   c) some good amount of $XXX is kept by IETF

I am in that business, and I expect that the small subset of IETF participants that would be willing to pay for such a service wouldn't justify a reasonable price.  I'm not sure what "some $XXX" you're imagining here, or what uptake you would expect, but the headache of setting this up and maintaining it would be unlikely to leave "some good amount" for the IETF.

Anyways, the IETF already has mail forwarding infrastructure, per the alias expanders for all the drafts.  The difference is between "a static contact address" (which I see some value in having for every RFC that can be updated or directed to the most relevant working group if the RFC is abandoned by its original authors), and an address which people might start signing up as the target for significant volumes of non-person-to-person traffic.

Bron.


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com