Re: [I18nrp] Was there ever a formal I18N directorate?

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 08 June 2018 02:10 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B2D130E0D for <i18nrp@ietfa.amsl.com>; Thu, 7 Jun 2018 19:10:50 -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 x4f4u_i8q_sO for <i18nrp@ietfa.amsl.com>; Thu, 7 Jun 2018 19:10:48 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::231]) (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 6612C12F1A6 for <i18nrp@ietf.org>; Thu, 7 Jun 2018 19:10:48 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id q62-v6so3906136ybg.5 for <i18nrp@ietf.org>; Thu, 07 Jun 2018 19:10:48 -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=MOW0fkQv9j3HvITjHqLBNoErQWoGx523gXTDyEainJM=; b=pVHTbSPuQm59dXiCxofGUz2qrWhR3xpNm96C2yaDJmEQxTrDFPiGU9ah6TjdB2ZPJo 9DWgbLmjlpBJPeeeyu5hZPjPe0mpIB3AtY4SmX4PaPlsiVLPW0XLV//jeiOBl0gj9/5X 7IAsH+IL0pS2XJqMU53FtlrPlTPsd1lljEe411pJcI4fC+oZNpYxKsmVO/TFPDYzx2co kpCooCze8AgJfr3L15yISQspU/zb3uVg8fE/Ur+Y8xIVhHRGkt6hpb1kOf85syoZhhnH E0qaLfMtGecEDVoIVW8sLqdf/MEfxmEXOgNSNh+9wAk5QIv0cfS/ALeyxy2e1E/XuNX4 fAcw==
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=MOW0fkQv9j3HvITjHqLBNoErQWoGx523gXTDyEainJM=; b=KPeXiL/NyhXXXg90ROBsN1Zru1F1GPLGHcl4bmO5TaZ1brXw4p2VxLaYfQVCHtqqPu P7l0c6Z9AOrFmpe4bUJYIjY3VRu/5SL0tnkLl2GAplRSS9gRANvGmW0AnFWkbGTwxWIe 4Av+w8ala4BQqFG8vmdmexBFqtxuWMROPQHO8OJKK7XdISDk9F5Z+fIAefiD5I5uDvNY yjO0ifysEDqrpkWfqIwM5pKNYm+NFfReChMbhJeoXRlFaYN3C1HfMb0KrIk81QSh0Efz XEWSYu7j61ukiPRNxNXjv/Y5X45wGHYVGrvkf59m8qwTV0R5OQkoC4KSciemUl16H/j9 OWag==
X-Gm-Message-State: APt69E2ufHaDwXZP0kn96SoRA1effV0rqCK3Fy1KKNGwxAXtdnNgaOFx I8nZwZbmI4pxxKKnYWMwtTFXGfur/Xhcu3tfvkA=
X-Google-Smtp-Source: ADUXVKKfdXHq+/9bkH4ZGwMsrmrRtBKswEbPC6gR8SZpRK39RFBvCfAYdKQU9PpOJko90Ow5V7ChV1c/gbm2d5S/09o=
X-Received: by 2002:a25:4d57:: with SMTP id a84-v6mr2554308ybb.286.1528423847385; Thu, 07 Jun 2018 19:10:47 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-cx+MOWL4Xiunph7ZS2q+OsJWzR25h3dtSgpSqBWSWXGQ@mail.gmail.com> <ABD8993CE02BD081471E5BFE@PSB>
In-Reply-To: <ABD8993CE02BD081471E5BFE@PSB>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 7 Jun 2018 21:10:35 -0500
Message-ID: <CAKKJt-d5ME_Z2faZ02qNRcf2FgdSD8tQYNeFJSeLeaRhweN3tw@mail.gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: i18nrp@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007d5f6d056e17e87c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/Irq7w1B34lDIfmNtw4X_-y5hX-Y>
Subject: Re: [I18nrp] Was there ever a formal I18N directorate?
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jun 2018 02:10:50 -0000

Also top posting and uncharacteristically short :-) ...

On Thu, Jun 7, 2018 at 2:29 PM John C Klensin <john-ietf@jck.com> wrote:

> Spencer,
>
> Top post and uncharacteristically short message:
>
> I don't think so although it was discussed a few times.
>
> The reason, IIR, is that, during the times when it was
> discussed, we typically had an active or very recently concluded
> WG (and only one) focused on core i18n issues and rarely more
> than one such WG at the time.   If the IESG needed advice, they
> could refer the questions to that WG (something they have always
> been able to do) and be reasonably sure that they could get a
> competent response.  Only in recent years have there been signs
> of so little energy that such a referral would have low odds of
> producing useful results.
>

I'm not surprised by that - I just wanted to understand the history of what
the IETF has done.

Thanks much.

Spencer

    john
>
>
>
>
> --On Thursday, June 7, 2018 12:49 -0500 Spencer Dawkins at IETF
> <spencerdawkins.ietf@gmail.com> wrote:
>
> > Dear I18Ners,
> >
> > We're running off the edge of history for most of the IESG,
> > but you folks would know the answer to this.
> >
> > There have been a few references to an Internationalization
> > Directorate, as if one existed in the past.
> >
> > I know about the IAB's (now-concluded) Internationalization
> > Program, mostly because I was on the IAB when we created it,
> > but I don't remember an actual IETF Internationalization
> > Directorate.
> >
> > That's not surprising - I've done a lot of work on binary
> > protocols, and much less on anything that would be
> > internationalized - but no one on the BOF coordination call(*)
> > this week could remember if the IETF ever having that specific
> > thing.
> >
> > Have we?
> >
> > Thanks in advance for clues ...
> >
> > Spencer
> >
> > (*) to be fair, not all the IESG and IAB were able to
> > participate in the BOF coordination call, but most of us were
> > present.
>
>
>
>
>