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

Ted Hardie <ted.ietf@gmail.com> Tue, 04 December 2018 22:02 UTC

Return-Path: <ted.ietf@gmail.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 B4F97130E97; Tue, 4 Dec 2018 14:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 j6PWSDY1O8LV; Tue, 4 Dec 2018 14:02:56 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A9951200B3; Tue, 4 Dec 2018 14:02:56 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id u16so16734851otk.8; Tue, 04 Dec 2018 14:02:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=o56rKKMJZI41EcfZCKUuBWYBwkBIdX+iAGondqAeHxc=; b=NKZKMKBcqAL8QUJpD2x2W3JqZ/ZXuPw5GaiJ6maVTM6StJBB5oYirWSJsa++9qQQhn 8nyrD/HSUY4uPjjZpZzkLOVrvbGcWrB5pgwlnO0S7BXdeqHyvaHvZ/p0DTyC2i8kg1/B v8IMkZJGSmshiXgO1CQMF6Tq0slAwnJPQznELe7yl4+EOxCiFiUGRWekAgeQrfZNp4s4 4lSuiszbGWXmPNusmnszCiSQXE0lJAEq/FKSdOe0mb+vXwkq+FA79L7K0hSSmKzEFwJT 78rmLShJ79AQnJMDxZnObwoc1DHCaho+FdgvzLUU6h9JcXT4kMCEYQVm3cz5qwQImBYP RfIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=o56rKKMJZI41EcfZCKUuBWYBwkBIdX+iAGondqAeHxc=; b=YZl7UkFB9VzqNJV45QawPTyhnqr9/NC6QD7OX92Pa/aFqyuof0NeBSm8tr/oq/m50N p3Ws6UO9azGxej3ebvxfkzmXCbQmUncTdeAQcz/x6wnmh8XelygzrripXomnqxdtyPKx QA1awsNTjnZbccnoBcN/sKuCLMi2hE8Nc/BIOOV0qUXNndAdq1eUE3TtIVDDpjhA1d5l uSmS8+FowZi2aO2rqqFJ4Z8Oy7cLFXGKtOS9KhAhNgBjqepz4EbQZK6/n4Ofvgtpd0ph LOGzDKafwVKeKNd2ZEgA6nXk3CIpWSVhN1wopGJcGOkZrBiRCJrdnZB4LICGfnVwHn4I shTg==
X-Gm-Message-State: AA+aEWY8UCAn/u3N1AfnUI7H5KsCQkjazQC8pypr5yFDv0+29oksj50b WDbAPuPD70QMjIocyBikSQI5mpy4Y90LPtvJUQw=
X-Google-Smtp-Source: AFSGD/XGMB9GMZ/pB7tWG/8DPEdklC9Ne6Lz0EeMrYEsNJf+A1dBO3aWC1IkvspE5TioyfTFega6l3JF6Q2s5YIlxM8=
X-Received: by 2002:a9d:72a:: with SMTP id 39mr15031719ote.134.1543960975251; Tue, 04 Dec 2018 14:02:55 -0800 (PST)
MIME-Version: 1.0
References: <3079F05172A384D8987A2338@PSB> <CA+9kkMAoGT-bnEk0bxieQBwd=yM+bvFfV4yyGf9gdyjm=zOtBw@mail.gmail.com> <8458F480-52CB-4DD4-9C52-6ED9F2860DFD@nostrum.com>
In-Reply-To: <8458F480-52CB-4DD4-9C52-6ED9F2860DFD@nostrum.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 4 Dec 2018 14:02:27 -0800
Message-ID: <CA+9kkMBRP3Aj0w9LfiuOqnzL0JK2OgWA9iDKhH6f9eGrDzbmPg@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: John C Klensin <john-ietf@jck.com>, i18n-discuss@iab.org, idna-update@ietf.org, ima@ietf.org, precis@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007a1e70057c396d8f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/-050-eNRhkjXyivUKuwvYKQmb9k>
Subject: Re: [EAI] [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: Tue, 04 Dec 2018 22:03:00 -0000

Hi Ben,

On Tue, Dec 4, 2018 at 1:29 PM Ben Campbell <ben@nostrum.com>; wrote:

> Hi Ted,
>
> I’d like to understand your objection better. (Please don’t take this as
> disagreement. Or agreement, for that matter :-) )
>
> How do you see things like “advise”, “educate” and “inform” as being a
> grant of authority beyond that of a directorate?  Individual participants
> can and do those things regularly; so I’m confused as why doing it as part
> of a directorate would be different. Do you read those things as putting
> the directorate in the approval path? Or are you concerned such advice
> would be given greater weight because of the directorate?
>

Given that the first suggestion here was that a document could not go
through last call until it had been reviewed by the group and John's
message seemed to indicate that its authority was not simply to advise an
AD, I inferred that the intent was to set up a group with an independent
authority to foster work or block documents.  That seems to me to require
discussion.  Even the EDU team, which has a remit to educate the community
is defined as a directorate serving the GEN area, and why this cannot be
not an area director led activity is not clear to me.

If we need something beyond that, okay, but I believe that requires
community discussion about how such groups are chartered, how their
membership is selected, and what the limits of their authority should be.

regards,

Ted Hardie


>
>
> Thanks!
>
> Ben.
>
> On Dec 4, 2018, at 3:04 PM, Ted Hardie <ted.ietf@gmail.com>; wrote:
>
> John,
>
> This is to advise you that I have notified the IESG that I strongly
> disagree with this conclusion on the scope of an i18n directorate; I heard
> calls for a directorate, not for a body with different characteristics
> sharing the name.  I have also notified them that I object to the formation
> of a body with a different remit to the usual "advise the ADs" unless a
> community discussion, charter, and discussion of how membership is selected
> takes place.
>
> We charter directorates now as advisory bodies to the ADs, and the ADs
> bear the responsibility for the related decisions (taking or not taking the
> advice as they see fit).  Since the ADs are selected by the NomCom, how
> they derive that authority and its limits are well known.  What you
> describe below departs from that, and unless it is made clear what
> authority is being granted and how the community is being consulted, I
> think it is outside of our process.
>
> Since this amounts to the early stage of an appeal, I have recused myself
> from further discussion within the IESG on this topic.
>
> On the more technical topic of the appropriate status (Standards Track or
> Informational) for this document, I will follow up as you suggest.
>
> Ted
>
> On Tue, Dec 4, 2018 at 12:19 PM John C Klensin <john-ietf@jck.com>; wrote:
>
>>
>> Those who attended or watched the IETF 102 BOF in July will
>> probably recall that it concluded that a group should be formed
>> to provide a focus and expert advice on I18n issues to the
>> community.   It was described as a "directorate" because that
>> term and organizational arrangement is familiar in the IETF, but
>> it was quite clear (at least to many of us) that its mission was
>> to advise, inform, and perhaps even educate the community on
>> i18n issues, rather than merely advising the ART ADs and/or
>> designating people to perform reviews late in the Last Call
>> cycle.  Alexey (as the ART AD who is apparently taking lead
>> responsibility for this work) has indicated that the
>> "directorate" should be organized and announced very soon now.
>>
>>
>
>
>
>> Because (if nothing else) the document follows up on RFC 6452,
>> which was Standards Track, and because the directorate should
>> have a chance to come together and review this document and its
>> relationship to other pending work, the Last Call has now been
>> cancelled (or, I hope more accurately, deferred).
>>
>> However, people should be aware of that document, that there has
>> been a discussion on the I18Nrp list that is certainly relevant
>> to the IDNA list and effort, that includes details not covered
>> by the summary above, and may be relevant to the other lists
>> copied; that the directorate is expected to be announced soon;
>> and that draft-faltstrom-unicode11 and other relevant I-Ds,
>> including some expired ones, may soon [re-]appear and require
>> review and evaluation.
>>
>> At least until Patrik or the ADs suggest otherwise, the
>> discussion of draft-faltstrom-unicode11 is on I18Nrp
>> (subscription and archive information at
>> https://www.ietf.org/mailman/listinfo/i18nrp )
>>
>> Happy reading and reviewing.
>> And apologies for not getting this note out when the discussion
>> first started up.
>>
>>     john
>>     (no particular hats other than interested party although my
>> hats as ex-EAI Co-Chair and author or contributor to a number of
>> relevant RFCs and pending documents are around here somewhere)
>>
>> _______________________________________________
>> I18n-discuss mailing list
>> I18n-discuss@iab.org
>> https://www.iab.org/mailman/listinfo/i18n-discuss
>>
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis
>
>
>