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

Nico Williams <nico@cryptonector.com> Tue, 23 June 2020 22:31 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 86AB53A0C00 for <i18ndir@ietfa.amsl.com>; Tue, 23 Jun 2020 15:31:50 -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 ebR-UvA_e1kp for <i18ndir@ietfa.amsl.com>; Tue, 23 Jun 2020 15:31:48 -0700 (PDT)
Received: from eastern.birch.relay.mailchannels.net (eastern.birch.relay.mailchannels.net [23.83.209.55]) (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 8158E3A0BFF for <i18ndir@ietf.org>; Tue, 23 Jun 2020 15:31:47 -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 15AE3121587; Tue, 23 Jun 2020 22:31:45 +0000 (UTC)
Received: from pdx1-sub0-mail-a23.g.dreamhost.com (100-96-137-11.trex.outbound.svc.cluster.local [100.96.137.11]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 46C3D121E42; Tue, 23 Jun 2020 22:31:44 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a23.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); Tue, 23 Jun 2020 22:31:44 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Unite-Continue: 04be97f34f71c25e_1592951504512_3081610282
X-MC-Loop-Signature: 1592951504512:1884489582
X-MC-Ingress-Time: 1592951504512
Received: from pdx1-sub0-mail-a23.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a23.g.dreamhost.com (Postfix) with ESMTP id B99C2B84F3; Tue, 23 Jun 2020 15:31:43 -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=Ncybx2bL4JK0N1 stNddlottkJm0=; b=B9tBPctaeLN0YjpOhNqoW6CqckaarsVtQp8eHsz3ueCcXI q8F0akXuwgrFyYGAQOj26+yY7AZ7KK5lWR5Ikt3H6aExxGK8705UrYJeiyK14bse cFVetv/P6CxQp9ylYF/oo71SnyFAKmjU7gONUIOcQJhPVwOUi27fhynmAc47Y=
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-a23.g.dreamhost.com (Postfix) with ESMTPSA id BC2F1B84F2; Tue, 23 Jun 2020 15:31:40 -0700 (PDT)
Date: Tue, 23 Jun 2020 17:31:35 -0500
X-DH-BACKEND: pdx1-sub0-mail-a23
From: Nico Williams <nico@cryptonector.com>
To: Asmus Freytag <asmusf@ix.netcom.com>
Cc: i18ndir@ietf.org
Message-ID: <20200623223133.GR3100@localhost>
References: <20200623160021.GO3100@localhost> <723F92393735E684C75471FA@PSB> <20200623191501.GP3100@localhost> <20200623192230.GQ3100@localhost> <56481213-ac60-29e2-7393-ad2a10025911@ix.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <56481213-ac60-29e2-7393-ad2a10025911@ix.netcom.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrudekiedguddtucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjfgesthdtredttdervdenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucggtffrrghtthgvrhhnpefftdektefhueetveeigfefgeejteejvdfhhefgvddtfeeujeehleeguefhgffhgfenucfkphepvdegrddvkedruddtkedrudekfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhm
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18ndir/zenmGr_b7ocPCkDmDDgl1X5XT_Y>
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: Tue, 23 Jun 2020 22:31:51 -0000

On Tue, Jun 23, 2020 at 03:17:37PM -0700, Asmus Freytag wrote:
> On 6/23/2020 12:22 PM, Nico Williams wrote:
> > I should add that I would like to discuss the filesystem I18N matter,
> > and others might like to discuss updates to IDNA or whatever.  There's
> > plenty of fodder for an actual meeting of this group.
> 
> Are you talking about a remote meeting or an in-person meeting?

"Yes".  That is, IETF 108 is not in-person, but if it were, then I'd be
asking about an in-person meeting, and since it's not, I'm asking about
a remote meeting.

In the context of an IETF meeting that is all-remote, the question of
whether a WG or directorate would meet at that IETF really means whether
we'd have a remote meeting scheduled in the sort of time slots you'd
expect for that IETF meeting.  Since there is no published agenda yet,
I don't know what time slots would be involved, but I assume lunch-time
in CEST or something like that, on some day of the week.

Nico
--