Re: [I18ndir] I18NDIR advice and process (was: Re: I18ndir last call review of draft-ietf-regext-dnrd-objects-mapping-06)
John C Klensin <john-ietf@jck.com> Fri, 06 March 2020 23:49 UTC
Return-Path: <john-ietf@jck.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 DC7293A0DC4 for <i18ndir@ietfa.amsl.com>; Fri, 6 Mar 2020 15:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 pixc2RHU55pn for <i18ndir@ietfa.amsl.com>; Fri, 6 Mar 2020 15:49:08 -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 6316E3A0DC5 for <i18ndir@ietf.org>; Fri, 6 Mar 2020 15:49:08 -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 1jAMiH-00074h-1g; Fri, 06 Mar 2020 18:49:05 -0500
Date: Fri, 06 Mar 2020 18:48:58 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <resnick@episteme.net>
cc: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>, asmusf@ix.netcom.com, i18ndir@ietf.org
Message-ID: <EB335C051EA7DE49C299FD7B@PSB>
In-Reply-To: <ED9F0940-EEEB-4ABF-934B-DB5AF2EC7640@episteme.net>
References: <158343520135.15044.10991712449156105132@ietfa.amsl.com> <9CD56DEFBC9108D9620ED61E@PSB> <2cb9e78f-32dc-3e2f-ba1a-6ae0218f3ef9@ix.netcom.com> <78B490AE833098E23541E672@PSB> <b10e418c-aa00-669d-68cf-03bb0ef0920b@ix.netcom.com> <19196892ADC7F5919DA7CE7A@PSB> <3e6d3b2bf0f241dfb161a0497e762bf3@verisign.com> <e54f23f8-aee5-e0f0-5acd-ebb86ddcc181@ix.netcom.com> <364f4ce4ca0d4ed7a95446169655e1cd@verisign.com> <4AA3DB653204B1B1EBB8B1E7@PSB> <6c6a5a378d56464c979f9313cc140a45@verisign.com> <8ADAC03F462A7EFF214505F6@PSB> <E63DA12D-5A83-4E34-98A1-53CE08B06917@episteme.net> <9AE8DC12A1D6D851BA8B4EC3@PSB> <ED9F0940-EEEB-4ABF-934B-DB5AF2EC7640@episteme.net>
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/i18ndir/-fytPyRKfFMeDbEBDOV6M81Hywc>
Subject: Re: [I18ndir] I18NDIR advice and process (was: Re: I18ndir last call review of draft-ietf-regext-dnrd-objects-mapping-06)
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: Fri, 06 Mar 2020 23:49:10 -0000
Pete, Skipping to the bottom... --On Friday, March 6, 2020 16:34 -0600 Pete Resnick <resnick@episteme.net> wrote: >... > I think "forbidden" is a bit dramatic. All that I was > suggesting is that we (as a directorate) not try to tell ADs > how they ought to run the Last Call process, or any other > aspect of the process, unless that advice is solicited. (We > are not an exceedingly shy bunch about privately telling ADs > how to do their job, and I would not presume to tell anyone > what they should or should not say to an AD in private, at > least not in my capacity as cat-herder of this directorate.) I don't think I was telling Barry, or Scott, or anyone else, how to do their jobs. I was making a suggestion about how, in my personal but probably not adequately humble opinion, how things could be expedited with this document. Barry is free to do with that advice whatever he likes, a range of options that certainly includes either ignoring it or telling me in vivid detail where I would put it. I have more than enough confidence in him to be sure that he is aware of both opinions and hope that his relationship with me is such that he knows that I would not be particularly offended if he selected the second. And, in that context, _if_ he decides he wants to move forward by bouncing the document back to the WG, "the WG is going to have to consult us further" might be presumptuous but it is also a statement of fact. Unless you make the distinction between "us" as the directorate and "us" as a bunch of individuals, the reality is that substantially all of the expertise on these matters, at a level deep enough to have participated usefully in the discussion of the last 24 hours, and among people active in the IETF ("active" as measured by participation in the WGs concerned with these topics) are on this mailing list (or were a year ago). If you have other candidates, why haven't we recruited them? As you know, I did have a few from outside who were ready to be brought in, but you know what happened to that idea. So, assuming the WG doesn't have the needed expertise and perspective internally (if they did, we wouldn't be finding these issues after IETF LC started) where else are you (or Barry) going to send them? I assume the answer isn't to someone who thinks that all of the issues come down to the implications of diacritical marks in two closely-related languages that both use Latin script The answer feels to me a whole lot like "us". best, john
- [I18ndir] I18ndir last call review of draft-ietf-… Marc Blanchet via Datatracker
- Re: [I18ndir] I18ndir last call review of draft-i… Barry Leiba
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Marc Blanchet
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Patrik Fältström
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag (c)
- Re: [I18ndir] I18ndir last call review of draft-i… Marc Blanchet
- Re: [I18ndir] I18ndir last call review of draft-i… Marc Blanchet
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Hollenbeck, Scott
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag (c)
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag
- Re: [I18ndir] I18ndir last call review of draft-i… Hollenbeck, Scott
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Pete Resnick
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag (c)
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Asmus Freytag (c)
- Re: [I18ndir] I18ndir last call review of draft-i… Hollenbeck, Scott
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Pete Resnick
- Re: [I18ndir] I18ndir last call review of draft-i… John C Klensin
- Re: [I18ndir] I18ndir last call review of draft-i… Marc Blanchet
- [I18ndir] I18NDIR advice and process (was: Re: I1… John C Klensin
- Re: [I18ndir] I18NDIR advice and process (was: Re… Pete Resnick
- Re: [I18ndir] I18NDIR advice and process Asmus Freytag
- Re: [I18ndir] I18NDIR advice and process (was: Re… John C Klensin
- Re: [I18ndir] I18NDIR advice and process (was: Re… Pete Resnick