Re: [TOOLS-DEVELOPMENT] Open source tools and their problems

Russ Housley <housley@vigilsec.com> Sat, 14 March 2020 13:54 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: tools-development@ietfa.amsl.com
Delivered-To: tools-development@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63073A1552 for <tools-development@ietfa.amsl.com>; Sat, 14 Mar 2020 06:54:48 -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=unavailable 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 tE4d85cxGPen for <tools-development@ietfa.amsl.com>; Sat, 14 Mar 2020 06:54:47 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05D7D3A1553 for <tools-development@ietf.org>; Sat, 14 Mar 2020 06:54:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6E2D2300B31 for <tools-development@ietf.org>; Sat, 14 Mar 2020 09:54:44 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DC2pzMLlSxD0 for <tools-development@ietf.org>; Sat, 14 Mar 2020 09:54:43 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id 16445300464; Sat, 14 Mar 2020 09:54:42 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <alpine.OSX.2.22.407.2003111749030.56130@ary.qy>
Date: Sat, 14 Mar 2020 09:54:44 -0400
Cc: Jay Daley <jay@ietf.org>, IETF Tools Development <tools-development@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <99DE8DE9-4481-4AE7-9D72-EDA5F7507F6C@vigilsec.com>
References: <8E423183-E029-4C74-BEA4-D04212DF77D5@ietf.org> <2BCF4712-1F62-459F-9720-110F93E63779@vigilsec.com> <alpine.OSX.2.22.407.2003111749030.56130@ary.qy>
To: John Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/tiTgXBj3PaG5MLqvFppc8mXAFQk>
Subject: Re: [TOOLS-DEVELOPMENT] Open source tools and their problems
X-BeenThere: tools-development@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <tools-development.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-development>, <mailto:tools-development-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-development/>
List-Post: <mailto:tools-development@ietf.org>
List-Help: <mailto:tools-development-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-development>, <mailto:tools-development-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Mar 2020 13:54:49 -0000


> On Mar 11, 2020, at 5:51 PM, John R. Levine <johnl@iecc.com> wrote:
> 
>> We do not allow people to register for IETF meetings with an EAI.  The reason is that the person will be added to the XXXall@ietf.org <mailto:XXXall@ietf.org> mail list, and that will cause Mailman to barf. The Mailman developers have publicly stated that EAI support is coming, but it was not part of the last release as expected.  Don Hollander at ICANN is also interested in solving this problem, and he has offered money in the past.  Maybe we can get the developers attention by both approaching them.
> 
> I'm probably the one to ask about EAI.
> 
> Realistically, it is vanishingly unlikely that there is anyone with an EAI address who would want to register or subscribe to an IETF thing who would not also have an ASCII address.  So long as our working language is English that is not likely to change.
> 
> There are communities of EAI-only users, but they exchange messages in the language of their address.

John:

We had someone try to do it a few meetings ago.  Fortunately they had another email address tey could use.

Russ