Re: [I18ndir] Directorate procedural question (was: Re: draft-faltstrom-unicode11-07)

Ben Campbell <ben@nostrum.com> Mon, 18 February 2019 18:52 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: i18ndir@ietfa.amsl.com
Delivered-To: i18ndir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BCD8130E68 for <i18ndir@ietfa.amsl.com>; Mon, 18 Feb 2019 10:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level:
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.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 zIj7X6YsmcyO for <i18ndir@ietfa.amsl.com>; Mon, 18 Feb 2019 10:52:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 C2E96129508 for <i18ndir@ietf.org>; Mon, 18 Feb 2019 10:52:30 -0800 (PST)
Received: from [10.0.1.29] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x1IIqE1D004839 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 18 Feb 2019 12:52:15 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1550515936; bh=v8IrSttymWIqao3g+sgNWLeu+NcZ5TZDI8PUe9HA4WE=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=HCe8BKql51/DXSkxYApeRG5DZaZP94oAhP9FaSlIc1CVLIBFKMHBus1DdHPcxds9m /iBqH2LR//BhyZ4DrVfgT3FsvLEJIp1msK4VCTE+vJlIfn1Cp/6fWbfUk0Jc+cMCZm gHwL961wVYhF1/KjF1wWAp2JBJL+cjEwwK/af/tA=
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.29]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <B8906218-09AA-406A-8797-8EE1FF5351A9@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BECFCDB9-517C-456D-80A0-959BC77C6979"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 18 Feb 2019 12:52:13 -0600
In-Reply-To: <35bc4d3e-9a72-4c9a-a2bf-dbc1b5acf28d@www.fastmail.com>
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <resnick@episteme.net>, Peter Saint-Andre <stpeter@mozilla.com>, i18ndir@ietf.org
To: Alexey Melnikov <aamelnikov@fastmail.fm>
References: <37939676-2D8A-4329-B6A0-A854F9530016@episteme.net> <341F4A75-30B9-4958-BBA1-DF6073BB6BE8@episteme.net> <CACA4C3C-007E-4370-B36C-0F9D3DD547D1@episteme.net> <c794f99e-c4b0-714d-f33f-67beee5daf6c@it.aoyama.ac.jp> <E5650F1C-CD61-4DD6-AF22-721877D1B60B@episteme.net> <079ab44b-2dcd-a730-d555-36ef75f1e101@mozilla.com> <F07414156FE01B008AA6A856@PSB> <248D3495-D429-4E73-836A-E1D9BBC3FF9E@episteme.net> <35bc4d3e-9a72-4c9a-a2bf-dbc1b5acf28d@www.fastmail.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/NTGaN_axVMG1hi1fYK9Q3YYpmdM>
Subject: Re: [I18ndir] Directorate procedural question (was: Re: draft-faltstrom-unicode11-07)
X-BeenThere: i18ndir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Internationalization Directorate <i18ndir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18ndir/>
List-Post: <mailto:i18ndir@ietf.org>
List-Help: <mailto:i18ndir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18ndir>, <mailto:i18ndir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2019 18:52:32 -0000

Do I understand correctly that Harald plans to send a summary of any conclusions?

Thanks,

Ben.

> On Feb 18, 2019, at 12:37 PM, Alexey Melnikov <aamelnikov@fastmail.fm> wrote:
> 
> John/Pete,
> 
> On Mon, Feb 18, 2019, at 5:37 PM, Pete Resnick wrote:
>> The ART ADs (who are monitoring this list and will hopefully notice
>> this) are in a better position to answer this query, but from my
>> perspective:
>> 
>> This list is likely to have a more in-depth discussion of the document
>> than any more general LC discussion on the main IETF list. I think it is
>> more valuable to have your input here.
> 
> Agreed.
> 
>> I also expect the ART ADs at the very least to take the input of this
>> review very seriously, and I expect the sponsoring AD of this document
>> would be unlikely to let issues raised by this review to go unaddressed.
> 
> Indeed, ART ADs will be watching both mailing lists. At the moment I don't see any email on ietf@ietf.org other than the one from Suzanne Woolf.
> 
> Best Regards,
> Alexey
> 
>> pr
>> 
>> On 16 Feb 2019, at 15:03, John C Klensin wrote:
>> 
>>> Gentlemen,
>>> 
>>> In addition to the issues identified below (on which, AFAICT,
>>> only the two of you and Asmus have commented in the week and a
>>> half since it was posted), I note that the Last Call on the I-D
>>> has been issued and discussion (albeit limited) has started on
>>> the IETF list.   I have every confidence in Harald's ability to
>>> write a good summary but, if it written in the usual style of
>>> directorate-as-review-team documents, I'd expect that at least
>>> some IESG members who would prefer to not be bothered by these
>>> issues would more or less ignore it.
>>> 
>>> I don't have time -- and I assume few others on this list have
>>> time -- to participate in parallel discussions on the two lists
>>> (this one and the IETF one).  I also believe that reasoned
>>> comments on the IETF list that disagree with the conclusions of
>>> some of us should be responded to there so that their authors
>>> (as well as the whole IESG) see the responses and might even be
>>> educated by whatever discussion follows.  So I now have a
>>> dilemma as to whether to keep reading and responding here or to
>>> put this list aside and start paying attention to the IETF one.
>>> 
>>> Please advise.
>>> 
>>>   john
>>> 
>>> 
>>> 
>>> --On Thursday, February 14, 2019 19:52 -0700 Peter Saint-Andre
>>> <stpeter@mozilla.com> wrote:
>>> 
>>>> On 2/14/19 8:52 AM, Pete Resnick wrote:
>>>> 
>>>>> I do want to point you and everyone at John's review
>>>>> https://mailarchive.ietf.org/arch/msg/i18ndir/vFddEKMIN0DR55Q
>>>>> ALal16H_1WYw to see if you have any comments on it. In
>>>>> particular:
>>>>> 
>>>>> |TL;DR summary of this note: It is extremely unwise for the
>>>>> IETF to process draft-faltstrom-unicode11-07 before a number
>>>>> of other issues (and associated documents) are carefully
>>>>> considered and resolved.|
>>>> 
>>>> I think John raises valid concerns, which I understand as:
>>>> 
>>>> 1. We really do need to figure out what to do about the issues
>>>> described in draft-klensin-idna-5892upd-unicode70,
>>>> draft-klensin-idna-rfc5891bis, and
>>>> draft-freytag-troublesome-characters.
>>>> 
>>>> 2. Advancing draft-faltstrom-unicode11 as-is could be
>>>> perceived as ignoring those issues.
>>>> 
>>>> 3. We now have a proper venue in which to address those
>>>> issues, so perhaps we should give ourselves a chance to
>>>> succeed.
>>>> 
>>>> 4. At the least, we might want to include more explicit
>>>> warnings in draft-faltstrom-unicode11 about the risks of
>>>> allowing "troublesome" characters.
>> 
>> 
>> --
>> Pete Resnick http://www.episteme.net/
>> All connections to the world are tenuous at best
>> 
>> --
>> I18ndir mailing list
>> I18ndir@ietf.org
>> https://www.ietf.org/mailman/listinfo/i18ndir
>> 
> 
> --
> I18ndir mailing list
> I18ndir@ietf.org
> https://www.ietf.org/mailman/listinfo/i18ndir