IETF Logo Mail Archive

Re: [I18ndir] Will there be an I18N directorate meeting at IETF 108?

Nico Williams <nico@cryptonector.com> Wed, 24 June 2020 15:13 UTC

Return-Path: <nico@cryptonector.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 A7ACD3A0EED for <i18ndir@ietfa.amsl.com>; Wed, 24 Jun 2020 08:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 4hdmEAhshka1 for <i18ndir@ietfa.amsl.com>; Wed, 24 Jun 2020 08:13:40 -0700 (PDT)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D0703A0EFB for <i18ndir@ietf.org>; Wed, 24 Jun 2020 08:13:38 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 3FA441E1041; Wed, 24 Jun 2020 15:13:37 +0000 (UTC)
Received: from pdx1-sub0-mail-a31.g.dreamhost.com (100-96-27-16.trex.outbound.svc.cluster.local [100.96.27.16]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 883371E156F; Wed, 24 Jun 2020 15:13:36 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a31.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Wed, 24 Jun 2020 15:13:37 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Whistle-Plucky: 026679e75ac092fb_1593011617000_3670131248
X-MC-Loop-Signature: 1593011617000:688533322
X-MC-Ingress-Time: 1593011617000
Received: from pdx1-sub0-mail-a31.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a31.g.dreamhost.com (Postfix) with ESMTP id 4010F7E63A; Wed, 24 Jun 2020 08:13:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=QHHqhBm5AdlujU eBD/ETG7XQJHs=; b=nODMhOoiy73do8UsR9lUo+K0JC0AYOxiEBhGNWWde7Lr0z uaarcbz0vz8N/hWHRWXKDbj33UICnb5mUiHwppvNZmKTUN/XV3Lrja8g0xahczKx lSX4LERYBFwLtdfWa74fgy34inp7oKL78qEl35+sYpR6/pstJagWfwIOWqe7Q=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 385937E637; Wed, 24 Jun 2020 08:13:33 -0700 (PDT)
Date: Wed, 24 Jun 2020 10:13:30 -0500
X-DH-BACKEND: pdx1-sub0-mail-a31
From: Nico Williams <nico@cryptonector.com>
To: John C Klensin <john-ietf@jck.com>
Cc: i18ndir@ietf.org
Message-ID: <20200624151328.GT3100@localhost>
References: <20200623160021.GO3100@localhost> <723F92393735E684C75471FA@PSB> <20200623191501.GP3100@localhost> <C2D29B21FB339FE6B5820D39@PSB> <20200624052654.GS3100@localhost> <B439664D0432EDABFEB98988@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B439664D0432EDABFEB98988@PSB>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrudekjedgjeelucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujggfsehttdertddtredvnecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecuggftrfgrthhtvghrnhepffdtkeethfeuteeviefgfeegjeetjedvhfehgfdvtdefueejheelgeeuhffghffgnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/T5WuBYlbeukMDD5x-KM1Ick6DGI>
Subject: Re: [I18ndir] Will there be an I18N directorate meeting at IETF 108?
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: Wed, 24 Jun 2020 15:13:42 -0000

On Wed, Jun 24, 2020 at 02:13:13AM -0400, John C Klensin wrote:
> --On Wednesday, June 24, 2020 00:26 -0500 Nico Williams
> <nico@cryptonector.com> wrote:
> > Surely that is sufficient evidence that this group is a
> > directorate.
> 
> Except that "directorate" in the sense above is not (absent one
> hypothesis) what is actually happening; [...]

This group is too -officially!- a directorate.  If you think it doesn't
act as one, therefore it is not or should not be one, fine, ask that it
be officially downgraded to a review team, or that it be disbanded.  But
for the moment it is officially a directorate even if you don't like it
being so.

I await a response from the chairs.  If the chairs would like to test
consensus for having or not having meetings, that's great, and since we
know where you and I stand on that, maybe we can let other participants
weigh in.

Nico

PS: Oh, and in regards to IDNA updates, perhaps a meeting would help you
    sell your proposal.  I don't understand your urge to give up on IDNA
    updates without a fight when you -apparently- feel so strongly about
    it.  Sell us on it, and we might furnish the additional interest/
    energy that you need that you think is absent.

v2.23.0 | Report a Bug | By Email