Re: [arch-d] [I18n-discuss] Closing the list

Jared Mauch <jared@puck.nether.net> Wed, 13 May 2020 18:20 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549F43A07BC; Wed, 13 May 2020 11:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-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 w6C3lyrD2slV; Wed, 13 May 2020 11:20:53 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6653A07C3; Wed, 13 May 2020 11:20:53 -0700 (PDT)
Received: from [10.0.0.129] (c-68-49-104-93.hsd1.mi.comcast.net [68.49.104.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 38E5154012D; Wed, 13 May 2020 14:20:52 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <000A12D4443F2DC47E555650@PSB>
Date: Wed, 13 May 2020 14:20:51 -0400
Cc: i18n-discuss@iab.org, architecture-discuss@ietf.org, art-ads@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D8E5CED-FAA5-423B-899C-EDD0D7ED970E@puck.nether.net>
References: <0114D1C5-49AE-46C8-9AD9-AF30C9D13E91@puck.nether.net> <000A12D4443F2DC47E555650@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/rBQaYK7yQeQI1NY3fJoyq2Wauk0>
Subject: Re: [arch-d] [I18n-discuss] Closing the list
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2020 18:20:57 -0000


> On May 13, 2020, at 2:13 PM, John C Klensin <john-ietf@jck.com> wrote:
> 
> Jared,
> 
> Re: i18n-discuss@iab.org
> 
> There have been multiple comments about that list, the
> observation that it is the _only_ IAB or IETF list available for
> general internationalization discussions (and, for the portion
> of the community that is interested in that work, a good place
> to copy announcements of i18n work and Last Calls), and the
> occasional but important bursts of traffic on it.    AFAIK, the
> first response from the IAB on the subject was this new
> "shutdown in 7 days" announcement.
> 
> Consistent with those comments, if the IAB wants to further
> indicate to the community that either it is uninterested in a
> fully international Internet and the technical and protocol work
> needed to get there or that it does not believe that such work
> is part of the architecture, you should definitely do that.  But
> the result should not be shutting down the list but moving
> responsibility for it to @ietf.org (noting that it is already on
> the IETF's Non-WG list and that the IETF holds the archives),
> creating whatever aliases, and moving over subscribers, as
> needed.
> 
> regards (and from an i18n perspective although with no hats on),
>   Sisyphus

(No hat)

I understand your concern and will ask this list not be touched given your response.  I previously worked for a company that used non-roman characters as their native language, and the prevailing thoughts that English as the the native language and cultural norms of American English sometimes caused a clash in understanding.

It would be good to hear this from others as well.  I will let you know that the list required manual intervention for my subscription to go through so I could post, so if the list is intended to be active, we should also look to understand why and correct that behavior if this is the best venue to discuss internationalization issues with the IAB as well as the broader community.

(I’ll find the details of that and at least let you know in private).

Thanks for your note!

- jared