Re: Proposed ietf.org email address policy

Toerless Eckert <tte@cs.fau.de> Fri, 11 June 2021 18:26 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 C5DBB3A0E04 for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 11:26:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 G1uhmdnfH-4N for <ietf@ietfa.amsl.com>; Fri, 11 Jun 2021 11:26:09 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29063A0E03 for <ietf@ietf.org>; Fri, 11 Jun 2021 11:26:09 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 8E8BB54802F; Fri, 11 Jun 2021 20:26:04 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 83B754E7728; Fri, 11 Jun 2021 20:26:04 +0200 (CEST)
Date: Fri, 11 Jun 2021 20:26:04 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org, lloyd.wood@yahoo.co.uk
Subject: Re: Proposed ietf.org email address policy
Message-ID: <20210611182604.GA36947@faui48e.informatik.uni-erlangen.de>
References: <2BF6EC60-8B32-4171-B236-D9D038B3135B@yahoo.co.uk> <20210611174521.CD568F22E4A@ary.qy>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20210611174521.CD568F22E4A@ary.qy>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mKqX7DIpZQgfs6PxDWrLwsmyS0c>
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 18:26:14 -0000

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

Cheers
    toerless

On Fri, Jun 11, 2021 at 01:45:21PM -0400, John Levine wrote:
> It appears that Lloyd W  <lloyd.wood@yahoo.co.uk> said:
> >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.
> 
> Having some familiarity with the mail business, there is no chance
> that something like this could break even, much less make any money,
> even if it was supposed to just forward mail to other addresses. I
> forward mail for some of my users and it is a huge pain between the
> legit mail that gets bounced by the target systems, the stuff my spam
> filters catch that the recipients actually want, and the spam that
> leaks through, they hit the junk button, and I get the complaint.
> 
> We're a standards organization.  Let's work on standards development.
> 
> R's,
> John