Re: [EAI] [Idna-update] [precis] [I18n-discuss] draft-faltstrom-unicode11, i18n "directorate", and related issues

John C Klensin <john-ietf@jck.com> Wed, 05 December 2018 21:37 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63C71130E95; Wed, 5 Dec 2018 13:37:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 lzi70Ib2VLKT; Wed, 5 Dec 2018 13:37:44 -0800 (PST)
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 46C9012D4E7; Wed, 5 Dec 2018 13:37:44 -0800 (PST)
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 1gUerR-0004Fd-Q3; Wed, 05 Dec 2018 16:37:37 -0500
Date: Wed, 05 Dec 2018 16:37:30 -0500
From: John C Klensin <john-ietf@jck.com>
To: Vint Cerf <vint@google.com>, ben@nostrum.com
cc: resnick@episteme.net, Ted Hardie <ted.ietf@gmail.com>, i18n-discuss@iab.org, precis@ietf.org, ima@ietf.org, idna-update@ietf.org
Message-ID: <D2B358AAD54EE0F95707FD31@PSB>
In-Reply-To: <CAHxHggc20G1NTMs8iEVYDc6R0W12sk6uLESRBhOd2UmsfXzt_Q@mail.gmail.com>
References: <3079F05172A384D8987A2338@PSB> <CA+9kkMAoGT-bnEk0bxieQBwd=yM+bvFfV4yyGf9gdyjm=zOtBw@mail.gmail.com> <8458F480-52CB-4DD4-9C52-6ED9F2860DFD@nostrum.com> <CA+9kkMBRP3Aj0w9LfiuOqnzL0JK2OgWA9iDKhH6f9eGrDzbmPg@mail.gmail.com> <680E50F3-3881-416F-A11A-22563F44A732@episteme.net> <CA+9kkMC0ioSoRP-7gZ6uEz77vASKoTW476gJef5jJieWr7Gipg@mail.gmail.com> <E8C57B36-17DA-4ED2-9E74-6740B979702F@episteme.net> <921E77FB-64DA-4A09-95BB-7307099F0B43@nostrum.com> <CAHxHggc20G1NTMs8iEVYDc6R0W12sk6uLESRBhOd2UmsfXzt_Q@mail.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/ima/kZQawwujwoeG080UJET9xSxTTBI>
Subject: Re: [EAI] [Idna-update] [precis] [I18n-discuss] draft-faltstrom-unicode11, i18n "directorate", and related issues
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ima/>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2018 21:37:47 -0000

But, with two qualifications, that is all that has ever been
proposed.  Those are:

(1) Because the root of the problems in this topic area is (or
appears to be) that the IETF community doesn't know nearly as
much about the topic as it would in a more ideal world and
because i18n work spans traditional and current Areas, I hope
the advice would be public rather than delivered in secret to
the AD and I would hope that the group would make an extra
effort to explain its reasoning in ways that the community (not
just the ADs) could understand and learn from.  I would hope
that the group members would want to do those things and that
the relevant AD(s) would insist on them.  (I don't think you
intended advice delivered in secret and kept that way, but your
suggestion could be read that way).  I think that is consistent
with your interpretation of "educating..." but can be see how
that could be interpreted differently, just as my initial
suggestion was.

(2) Not unlike our "Doctors" model (and consistent with the very
informal consultations about some LAMPS documents which I
believe were successful), I'd expect WGs and
document-developers, including those in other Areas, to want to
consult this group for advice and even help with text in
documents.   I'd hope that could be handled informally,
directly, and efficiently, with a focus on getting quality work
done.   I think it would be very unfortunate if the same sort of
procedure-lawyering that has gotten involved in this thread
would turn those efforts into requirements for a process that
would go something like:

   (OtherWG (or AD in other Area)): Dear ART ADs, would you
please ask the Directorate to review XYZ and help with text.
   (ART AD to OtherWG): Sure
   (ART AD to Directorate): Please see this request from
OtherWG, deal with it, and tell me.
   (Directorate to ART AD (because they are expected to advise
that AD and no one else): ART AD, we think ABCDE
   (ART AT to Other WG): Directorate says "we think ABCDE"

Possibly followed by additional iterations of this waste of the
time of ADs and Directorate members, especially if specific text
were asked for and/or suggested.

I think that would be seriously dumb and hope my example shows
that and why.  But it would be consistent with efforts to draw
narrow lines around supposed principles such as "the only thing
a directorate is allowed to do is to advise ADs in that area).

best,
   john


--On Tuesday, December 4, 2018 19:21 -0500 Vint Cerf
<vint@google.com>; wrote:

> suggestion:
> 
> set up the advisory group and allow it to offer advice to the
> appropriate AD.
> This same advisory group can reasonably share its findings
> more generally, thereby "educating...." the rest of the
> community. No power to block should either explicitly or
> implicitly be inferred by the creation of the advisory body.