Re: [Idna-update] [art] Comments on draft-faltstrom-unicode11-02

Ted Hardie <ted.ietf@gmail.com> Mon, 08 October 2018 20:27 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: idna-update@ietfa.amsl.com
Delivered-To: idna-update@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9008313101B; Mon, 8 Oct 2018 13:27:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 CnNPgoeofU13; Mon, 8 Oct 2018 13:27:25 -0700 (PDT)
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 B61A1131007; Mon, 8 Oct 2018 13:27:25 -0700 (PDT)
Received: by mail-ot1-x32a.google.com with SMTP id u22so21202028ota.12; Mon, 08 Oct 2018 13:27:25 -0700 (PDT)
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=RDoSaEtt0JsbKNcw4FFeA2kyK6tM06sgH1uhHcwdiiM=; b=gJ+BC9D/AYK4IFQZcZa28B8MAjamx6aIaVAu0cQ86sW9n9F+mua/txct0BtJDi1iPh 0xFVMGWuZyTwzzduz6Vb6TP9j4IksKfVNClFjdWMzHoQgSKFY/vIq/huJT6bAJZLwSd0 PR8Rd2205jatyBNRnuP+vKFaaDZ2YBuaWYQzehapMcjKokOvPF5lA5o85AyrFy+Afww7 rveWVE80QzIgbx9UC8vKpkd59BgLGAI9hbkfEWkih3+kUaHPgw5ZgNyr1s4/ltHwBLkr YVN8HoG+H+YW/bMDLBrxdw6Z5Nna6ePa92NhTWtb+kUCnamP8nem5dZOIpmoXfHyoENu uzMA==
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=RDoSaEtt0JsbKNcw4FFeA2kyK6tM06sgH1uhHcwdiiM=; b=eSK/n9DJuR7XwVZAAhd1oUMdEH+y3u4yZKT/9CLTe+SCw62oC6JjOXXOfIb8Ro7ZHc s+Zoj8A8kpf0+XNAt3lyKTmgFsyHI1kGeVLtVuY+Hp7EEwRf/eZ0sxhsICzLs4QhaCcn MUDYcf0MUKNcHg8kYZMZhjLXhT+pLfhRq/aVIXiAM7Q3VrQN9p10RvtL9Qqz5eswwvrG ZvRUd8QWkGZN5r/iVLlFA2yOpTuokXllU6p9GscNWiqoENWq1ktnkWE+TPD/cp5xhcpC YkiqduPQAEZ/KJiOI3Cn1DQGCgL7KQbDidvbRw+wPan94yAZevN0/GY+qPPd/gWXZfMu uChw==
X-Gm-Message-State: ABuFfohGz9G2aXYkqWtkxW1qoZr30mSSk1POaLrQvkmD3zJnHbdFxSim Gamm7pczukErLSIrtun57Ykn5sRFWekAqpjDgxQ=
X-Google-Smtp-Source: ACcGV60eOdc64H+y81TnOrtx14z0dkRbSNZldZKzGrOKcKIzRwCJI1soEHygT82GIrcbmFtmr8fRTk8lxkAHVcox1Dw=
X-Received: by 2002:a9d:992:: with SMTP id q18mr7624777otd.351.1539030444793; Mon, 08 Oct 2018 13:27:24 -0700 (PDT)
MIME-Version: 1.0
References: <ac2f439d-bed2-11e1-dcc7-34ee2d11fc1b@acm.org> <EEBE6FD4-A75C-4BB7-92BF-BD5F5AD7E171@netnod.se> <CA+9kkMB1AcJD9v6EggN3Hx2Wqv0VHwwhbR3P18a7O+OGkf7Odw@mail.gmail.com> <B0BA40527CB85EC369DD812D@PSB>
In-Reply-To: <B0BA40527CB85EC369DD812D@PSB>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 08 Oct 2018 13:26:58 -0700
Message-ID: <CA+9kkMC836d20ZCHETUJ_njYCO6b=V72YYpVufquXkH4F23gsA@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Patrik Fältström <paf@netnod.se>, nordmark@acm.org, Applications and Real-Time Area Discussion <art@ietf.org>, idna-update@ietf.org
Content-Type: multipart/alternative; boundary="000000000000f5e5300577bd7237"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/qgV47pDFq5esq3VaEBDrPRtyRhQ>
Subject: Re: [Idna-update] [art] Comments on draft-faltstrom-unicode11-02
X-BeenThere: idna-update@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Internationalized Domain Names in Applications \(IDNA\) implementation and update discussions" <idna-update.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idna-update>, <mailto:idna-update-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idna-update/>
List-Post: <mailto:idna-update@ietf.org>
List-Help: <mailto:idna-update-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idna-update>, <mailto:idna-update-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2018 20:27:28 -0000

Howdy,

On Mon, Oct 8, 2018 at 12:58 PM John C Klensin <john-ietf@jck.com> wrote:

> --On Monday, October 8, 2018 09:06 -0700 Ted Hardie
> <ted.ietf@gmail.com> wrote:
>
> > Modulo Erik's comments, I think this is ready for publication.
> > The instructions to IANA are clear and the rationale behind
> > those instructions is laid out.
> >
> > I think we could ask for AD-sponsorship for this, but I also
> > believe that the instructions could go to IANA now; at the
> > very least, we could ask them to review.
>
> Ted,
>
> I'm sorry, but I disagree.  Patrik has, as far as I can tell,
> done the job that the IAB asked him to do in his liaison
> capacity to Unicode, but that job involves a number of
> assumptions about how to proceed that interact with i18n
> documents that the IETF has been unable to process.  If we
> follow the precedent of RFC 6452, this document should be
> processed as standards track even if it changes nothing.  It
> would be wildly inappropriate for it to constrain the
> conclusions the IETF could reach about those other documents.
>
> I infer that you are disagreeing with my suggestion that this get
AD-sponsorship, not with my suggestion that it get at minimum IANA review.
If you disagree with that as well, perhaps you'd care to say why.  My
personal take is that it is useful to get confirmation from IANA that the
instructions are clear as soon as possible.

My understanding coming out of the BOF at IETF 102 was that the
> ART ADs were going to establish a directorate to determine how
> i18n documents were to be handled and to start processing those
> documents.  This document would make an entirely reasonable
> addition to that directorate's queue.   However, if an progress
> has been made on creating that directorate, much less having it
> convene and discuss processing of documents, I seem to have
> missed the announcement(s).
>
> As you know doubt recall from RFC 2418, the purpose of a directorate is to
advise an Area Director or a set of Area Directors:

In many areas, the Area Directors have formed an advisory group or
> directorate. These comprise experienced members of the IETF and the
> technical community represented by the area. The specific name and the
> details of the role for each group differ from area to area, but the
> primary intent is that these groups assist the Area Director(s), e.g., with
> the review of specifications produced in the area.
>

I certainly agree that the presence of a fully functional i18n directorate
would be a boon, but I believe that any AD considering sponsorship of this
would do so by consulting, informally, many of the same folks who might
serve on that directorate were it in place.  So I do not, personally, see
any reason to gate on the formality when the ADs can get the same advice
for this one without it.

regards,

Ted Hardie


> best,
>    john
>
>