IETF Logo Mail Archive

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

"John R. Levine" <johnl@iecc.com> Wed, 11 March 2020 21:51 UTC

Return-Path: <johnl@iecc.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 83FDE3A0101 for <tools-development@ietfa.amsl.com>; Wed, 11 Mar 2020 14:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.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 uxXQ0CZnkVA8 for <tools-development@ietfa.amsl.com>; Wed, 11 Mar 2020 14:51:10 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0C3B3A00E1 for <tools-development@ietf.org>; Wed, 11 Mar 2020 14:51:10 -0700 (PDT)
Received: (qmail 38992 invoked from network); 11 Mar 2020 21:51:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=984e.5e695d4d.k2003; i=johnl-iecc.com@submit.iecc.com; bh=DRQA9C6ZLqyvimKpJ5end1kNOyP4malueNmhPhTn42w=; b=ShLr5qlAmh6cLM163SRxDwV10Ul37ZkkxhiKj9HzBR9D0snD16HSSl2f0O0V24EQU+yfpciVFrYB5zBnts4ndah1eCjxhboinYBYajee6kc4XryKe6xVz9kUHcEYxiiL6kVviMpWiMP6Bjnn3WmiGyeBc/l56la+jvJvP9/+mXierNRjTOARK0XvBmQOEirqLkDcL37iavTDRLP1fmb1jM8p7j7noUv8bcKXWhrIFnfxHWs38AX0sCxwBzlnFidr
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.3 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP6; 11 Mar 2020 21:51:09 -0000
Date: Wed, 11 Mar 2020 17:51:08 -0400
Message-ID: <alpine.OSX.2.22.407.2003111749030.56130@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Russ Housley <housley@vigilsec.com>, Jay Daley <jay@ietf.org>
Cc: IETF Tools Development <tools-development@ietf.org>
In-Reply-To: <2BCF4712-1F62-459F-9720-110F93E63779@vigilsec.com>
References: <8E423183-E029-4C74-BEA4-D04212DF77D5@ietf.org> <2BCF4712-1F62-459F-9720-110F93E63779@vigilsec.com>
User-Agent: Alpine 2.22 (OSX 407 2020-02-09)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-development/FuilEZFDfJSoto-nGJKPICTyxh8>
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: Wed, 11 Mar 2020 21:51:13 -0000

> 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.

R's,
John

>> On Mar 11, 2020, at 5:24 PM, Jay Daley <jay@ietf.org> wrote:
>>
>> Glen
>>
>> When you have some time it would be useful if you could identify the top 5 problems that you experience with open source software (in running our services).  I will then look at the feasibility of issuing RFPs for people to fix them.
>>
>> thanks
>> Jay
>>
>> --
>> Jay Daley
>> IETF Executive Director
>> jay@ietf.org
>> +64 21 678840
>>
>> _______________________________________________
>> TOOLS-DEVELOPMENT mailing list
>> TOOLS-DEVELOPMENT@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-development
>
>

Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email