Re: [Idna-update] [precis] [I18n-discuss] draft-faltstrom-unicode11, i18n "directorate", and related issues
"Marc Blanchet" <marc.blanchet@viagenie.ca> Wed, 05 December 2018 22:08 UTC
Return-Path: <marc.blanchet@viagenie.ca>
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 41148130E89 for <idna-update@ietfa.amsl.com>; Wed, 5 Dec 2018 14:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.36
X-Spam-Level:
X-Spam-Status: No, score=-3.36 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=viagenie-ca.20150623.gappssmtp.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 kwiuNJg-8k5M for <idna-update@ietfa.amsl.com>; Wed, 5 Dec 2018 14:08:50 -0800 (PST)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 5448D130F11 for <idna-update@ietf.org>; Wed, 5 Dec 2018 14:08:47 -0800 (PST)
Received: by mail-qt1-x834.google.com with SMTP id n21so24159431qtl.6 for <idna-update@ietf.org>; Wed, 05 Dec 2018 14:08:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=viagenie-ca.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Ixohzz4uQmIoHImCOsgFiOuGUUCE05hkQLOtWIaRkeQ=; b=OOXK6Eryntfe9UO4/zxmiCjJAlAa1ygcnvKMNaTYzYWWAm1eTYjffI4JreAa6HvJSM /mvKlko5zMAgLUGcUc4gD8VVRLiO0338h1+w+FORB8k/NWOwcsuGzvkE/TKndOuZWBji zX71mDYcS0OR8ERkeH2G70xg1NaQdidn25qMDPWmy4aZCEYvHdv6Xc0RujGXRBeoJ2qA yIU2tanhNqPo0yPozsuNi9hTBawghq9HgQxKZWJTLvTtyt9ISTuQ5jteh+wt+1Q2DC4D nfqcCdcRfT66I9hToKLrk5i7GdveT34IEMn/pPYDQID8iCjYlz+CWCkIq4bsG4QOxRKM 4WaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Ixohzz4uQmIoHImCOsgFiOuGUUCE05hkQLOtWIaRkeQ=; b=MJUUqk/d7gZVI77ph35ou0Bkz23NFBOGdxV4lj9xhvrmaKEQEtEa5x+zp1b+UItXOr scrPEKoSjFXDnFWT2HeFdzLR0z796Tltp1Pc8qZCubWqKEKXirfTcUBobHrGXRTj89zk tcVOAmSJXUblDzhLKEklNs5uLsaHBqq83zt3X3lXbX0MprgrNa3TEDdbN1PFTAcFHVco GoIaliwdx0YiS47aVnsskbfVrw0fT0XgAXD7miTvLHtnY2crr9ImCIVkauFE89B1a+T3 BOamUllv4LStrwC21EM6Sl5M8t/p8Is+CspPlqlUoSJcLaqRI9VCfzjkJzQwZWfZ0bGN 1nTQ==
X-Gm-Message-State: AA+aEWYU2gpjnjnJg6sWgcl3SyyRwvXC5ku8Ud+YEUyGnCoX86hVoR9Q fzXHUKTCJifMdhg0gbivzcb2PA==
X-Google-Smtp-Source: AFSGD/WOnRmYP5boMhtaNJoHsrMKFYjg+OMBHrpSLDKqOa4kgQDMzvYcwS2RQzE3UeruKfwyXL68SA==
X-Received: by 2002:ac8:6b18:: with SMTP id w24mr25485920qts.144.1544047726260; Wed, 05 Dec 2018 14:08:46 -0800 (PST)
Received: from [192.168.1.60] (modemcable138.218-70-69.static.videotron.ca. [69.70.218.138]) by smtp.gmail.com with ESMTPSA id v42sm13725513qth.32.2018.12.05.14.08.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Dec 2018 14:08:45 -0800 (PST)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
To: John C Klensin <john-ietf@jck.com>
Cc: Vint Cerf <vint@google.com>, ben@nostrum.com, Ted Hardie <ted.ietf@gmail.com>, i18n-discuss@iab.org, precis@ietf.org, ima@ietf.org, idna-update@ietf.org, resnick@episteme.net
Date: Wed, 05 Dec 2018 17:08:43 -0500
X-Mailer: MailMate (1.12.2r5568)
Message-ID: <A4C29B36-FAC6-4EB1-BD6D-F8CA05E6194E@viagenie.ca>
In-Reply-To: <D2B358AAD54EE0F95707FD31@PSB>
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> <D2B358AAD54EE0F95707FD31@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idna-update/Kg--dvaE-gR5XPDWY-4YeVgKGbc>
Subject: Re: [Idna-update] [precis] [I18n-discuss] draft-faltstrom-unicode11, i18n "directorate", and related issues
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: Wed, 05 Dec 2018 22:08:54 -0000
On 5 Dec 2018, at 16:37, John C Klensin wrote: > 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. it has been « by design » that Stringprep [RFC3454] and its replacement Precis[RFC8264] that there will be « requests » on how to do « the precis profile for my protocol » from the community. This happened for Stringprep quite a lot after the release of Stringprep. With Precis, we updated many of those to use Precis instead, but when the precis working group was closed, there was still many profiles-to-update left and obviously others will come. Therefore, for Precis at least, there will be some community—i18ndirectorate exchanges similar to yang doctors. Marc. > > (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. > > > > > _______________________________________________ > IDNA-UPDATE mailing list > IDNA-UPDATE@ietf.org > https://www.ietf.org/mailman/listinfo/idna-update
- [Idna-update] draft-faltstrom-unicode11, i18n "di… John C Klensin
- Re: [Idna-update] [I18n-discuss] draft-faltstrom-… Ted Hardie
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Ben Campbell
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Ted Hardie
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Pete Resnick
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Ted Hardie
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Pete Resnick
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Ben Campbell
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Vint Cerf
- Re: [Idna-update] [EAI] [precis] [I18n-discuss] d… Ajay Data
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… John C Klensin
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… John C Klensin
- Re: [Idna-update] [precis] [I18n-discuss] draft-f… Marc Blanchet