Re: Proposed ietf.org email address policy

Adam Roach <adam@nostrum.com> Mon, 14 June 2021 01:40 UTC

Return-Path: <adam@nostrum.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 F0DFD3A19C2; Sun, 13 Jun 2021 18:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 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, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
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 CXIaqNz9Vq_Y; Sun, 13 Jun 2021 18:40:34 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D3633A19C1; Sun, 13 Jun 2021 18:40:34 -0700 (PDT)
Received: from [172.17.121.48] (76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 15E1eT7s018520 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 13 Jun 2021 20:40:31 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1623634831; bh=eXFdg4B0gKrauaTO3mBiTX76Oq1l7VNcXmerXnt1lkg=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=RAVuT7rzfvkzjlHyUOyS9O4lknsFTxZVBWoHlQmQAMgW0dR0DvUIiakjEaJtIiDWg 64Tgdv8dQKNTJRnjY7a/27L9qYkEBgaok7mExW/DHPHbKfn6nYq5Dk+O92Q31XNA11 6xccR7sgPpq2C2BnJ3DA4HzFF/ehqo6EaXwOe7m0=
X-Authentication-Warning: raven.nostrum.com: Host 76-218-40-253.lightspeed.dllstx.sbcglobal.net [76.218.40.253] claimed to be [172.17.121.48]
Subject: Re: Proposed ietf.org email address policy
To: admin-discuss@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Cc: IETF <ietf@ietf.org>
References: <59562F9B-8DDE-408C-ACCD-BC087FE86E1A@ietf.org>
From: Adam Roach <adam@nostrum.com>
Message-ID: <64453fad-ead9-8b36-51d6-8c4d650cb372@nostrum.com>
Date: Sun, 13 Jun 2021 20:40:24 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <59562F9B-8DDE-408C-ACCD-BC087FE86E1A@ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rXx-jfuY_VerJdWcSBIOilEr848>
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: Mon, 14 Jun 2021 01:40:40 -0000

I think this proposal takes things in the right direction. Thanks to 
everyone who worked to craft the policy.

/a

On 6/10/2021 12:52 PM, IETF Chair wrote:
> We are proposing a policy regarding the allocation of individual
> administrative email addresses in the ietf.org domain. The proposal
> was motivated by a few community members that raised the concern that
> continued allocation of individual email addresses under ietf.org
> could at some point create collisions for IETF mailing lists.
>
> Historically, the only email addresses created under the ietf.org
> domain were for IETF-associated mailing lists, e.g., for working
> groups, the IESG, directorates, etc., for aliases for certain roles,
> e.g., chair@ietf.org, or for administrative purposes, e.g.,
> support@ietf.org. This was not the result of following any explicit
> allocation policy, it just happened that way.
>
> This expanded slightly a number of years ago, on an ad hoc basis, and
> now a few individuals - all of them IETF LLC employees - have work
> email addresses under ietf.org.
>
> Therefore, the IESG and LLC Board are considering formalizing a policy
> concerning ietf.org email addresses:
>
> * new email addresses for general and administrative roles under
>    ietf.org must be chosen to avoid conflicts with potential IETF
>    mailing list names
>
> * the IESG must be consulted before any new email addresses under
>    ietf.org are created and will have the sole responsibility for
>    approving and managing addresses under ietf.org
>
> * new individual email addresses for LLC personnel will be allocated
>    under a new staff.ietf.org subdomain, with the LLC being solely
>    responsible for the approval and management of those addresses
>
> * existing individual email addresses under ietf.org at the time the
>    policy goes into effect will continue to receive email, which will
>    be forwarded to new staff.ietf.org subdomain addresses; and
>    outbound mail should be preferably be sent from staff.ietf.org
>    addresses or role-based ietf.org addresses
>
> We invite the community to send feedback on this proposed policy to
> admin-discuss@ietf.org by 24 June 2021.
>
> Lars Eggert
> IETF Chair
>
> Jason Livingood
> Chair, IETF LLC Board
>