Re: [I18ndir] Getting restarted and triage

John C Klensin <> Sat, 22 June 2019 00:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 29E2C120230 for <>; Fri, 21 Jun 2019 17:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4G548O7VRRQ2 for <>; Fri, 21 Jun 2019 17:47:00 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 693D412017F for <>; Fri, 21 Jun 2019 17:47:00 -0700 (PDT)
Received: from [] (helo=PSB) by with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <>) id 1heUBG-000DZT-J1; Fri, 21 Jun 2019 20:46:58 -0400
Date: Fri, 21 Jun 2019 20:46:51 -0400
From: John C Klensin <>
To: John Levine <>,
Message-ID: <AF49257619901A2694737684@PSB>
In-Reply-To: <20190621224209.5A2B820162CB0E@ary.qy>
References: <20190621224209.5A2B820162CB0E@ary.qy>
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-Scanned: No (on; SAEximRunCond expanded to false
Archived-At: <>
Subject: Re: [I18ndir] Getting restarted and triage
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 22 Jun 2019 00:47:02 -0000

--On Friday, June 21, 2019 18:42 -0400 John Levine
<> wrote:

> In article <F2A317B2420BA48FC2A23176@PSB> you write:
>> I've read Barry's note, which seems entirely reasonable.  As
>> you (and I trust most other's here) have noticed, while
>> waiting I did post a note to the IDNAbis list asking for
>> review and feedback on the theory that, if anyone on that
>> list but not on this one had something to say / contribute,
>> we should listen. So far the silence has been deafening which
>> I can interpret either as ...
> It's on my List of Things to Do Immediately.  You know how it
> is.

Oh, yes. 

But one guess as to what is causing Pete's difficulties in
getting responses to his triage question is that I18N issues
generally, and perhaps IDNA-related ones in particular, have
gotten into that state and that List for everyone here
(including Pete's and Peter's and, probably given the progress
on draft-faltstrom-unicode12-00 since March 11th, Alexey's).
While we've been saying things in terms of "insufficient
expertise" for i18n issues, it may be equally true that is just
has not been high enough priority for anyone with expertise or
otherwise in the critical path.  

If that is the case, then the question --and, again, the
question since Patrik and I requested the BoF over a year ago --
is whether we have a plan about changing that (maybe easier than
finding more expertise and maybe not) or whether should be
making another plan entirely, presumably one that gets the IETF
out of the critical path.