Re: Proposed ietf.org email address policy
John C Klensin <john-ietf@jck.com> Thu, 10 June 2021 18:54 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 5DD983A1439; Thu, 10 Jun 2021 11:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 jkXomq-yqRKX; Thu, 10 Jun 2021 11:54:04 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AEE23A142D; Thu, 10 Jun 2021 11:54:03 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lrPoX-0003Ac-AW; Thu, 10 Jun 2021 14:54:01 -0400
Date: Thu, 10 Jun 2021 14:53:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Fred Baker <fredbaker.ietf@gmail.com>, admin-discuss@ietf.org
cc: IETF <ietf@ietf.org>
Subject: Re: Proposed ietf.org email address policy
Message-ID: <71FFEE6A5354E4D51039A99D@PSB>
In-Reply-To: <021D5577-9DB1-4FA9-8D09-2683CC32BCB7@gmail.com>
References: <59562F9B-8DDE-408C-ACCD-BC087FE86E1A@ietf.org> <021D5577-9DB1-4FA9-8D09-2683CC32BCB7@gmail.com>
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
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dRe2PxTTO3FXr7v6364Rd-ZBh7I>
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: Thu, 10 Jun 2021 18:54:09 -0000
Fred, I think that is already in the proposal -- see the last bullet point ("* existing individual email addresses under ietf.org...") Lars and Jason, Seems completely sensible to me and is fairly similar to what I would have proposed if asked (probably just a happy coincidence). One tiny suggestion and a question: * At least for the benefit of those of us with fat fingers, have you considered a subdomain shorter than "staff". "llc.ietf.org" or even "co.ietf.org" or "ad.ietf.org" would seem to have small advantages if done at the beginning? * Several people who are not employees of the LLC, particularly Secretariat Staff working for AMS, already have ietf.org role accounts. As I understand the proposal, that does not change. They are now using AMSL.COM addresses when those role account are inappropriate (or they don't have role accounts). I assume that does not change. Correct? Again, seems like a very good proposal and plan. thanks, john --On Thursday, June 10, 2021 11:16 -0700 Fred Baker <fredbaker.ietf@gmail.com> wrote: > Thanks for this. Your proposed rule makes sense. I might have > one suggestion. > > Where you have allocated an email address in IETF.org for an > individual, duplicate that with an address in staff.IETF.org. > That will allow you, at some point in the future, to remove > the first set of addresses and continue communication with the > second. I might suggest that those individuals start using the > @staff email addresses so reduce any possible impact when that > is done. > > JUst a thought.
- Re: Proposed ietf.org email address policy Salz, Rich
- Proposed ietf.org email address policy IETF Chair
- Re: Proposed ietf.org email address policy Fred Baker
- Re: Proposed ietf.org email address policy John C Klensin
- Re: Proposed ietf.org email address policy Keith Moore
- Re: Proposed ietf.org email address policy Lloyd W
- Re: Proposed ietf.org email address policy John C Klensin
- Re: Proposed ietf.org email address policy Michael Richardson
- Re: Proposed ietf.org email address policy John Levine
- Re: Proposed ietf.org email address policy Toerless Eckert
- Re: Proposed ietf.org email address policy Bron Gondwana
- Re: Proposed ietf.org email address policy Spencer Dawkins at IETF
- Re: Proposed ietf.org email address policy Michael Richardson
- Re: Proposed ietf.org email address policy John C Klensin
- Re: Proposed ietf.org email address policy Michael Richardson
- Re: Proposed ietf.org email address policy Brian E Carpenter
- Re: Proposed ietf.org email address policy Stephen Farrell
- Re: Proposed ietf.org email address policy Carsten Bormann
- Re: Proposed ietf.org email address policy John C Klensin
- Re: Proposed ietf.org email address policy Aqua Q Glass
- Re: Proposed ietf.org email address policy ned+ietf
- Re: Proposed ietf.org email address policy John C Klensin
- Re: Proposed ietf.org email address policy John C Klensin
- Re: Proposed ietf.org email address policy Adam Roach
- Re: Proposed ietf.org email address policy Carsten Bormann
- RE: Proposed ietf.org email address policy Larry Masinter
- Re: Proposed ietf.org email address policy Phillip Hallam-Baker
- Re: Proposed ietf.org email address policy Scott Bradner
- Re: Proposed ietf.org email address policy Spencer Dawkins at IETF