Re: [Ietf-languages] Errors in Registry

"Phillips, Addison" <addison@lab126.com> Wed, 09 January 2019 22:03 UTC

Return-Path: <prvs=9055b4a44=addison@lab126.com>
X-Original-To: ietf-languages@ietfa.amsl.com
Delivered-To: ietf-languages@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB32A126DBF for <ietf-languages@ietfa.amsl.com>; Wed, 9 Jan 2019 14:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 VQprzHhQtw6Y for <ietf-languages@ietfa.amsl.com>; Wed, 9 Jan 2019 14:03:01 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [IPv6:2001:700:1:2::117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBB0C124D68 for <ietf-languages@ietf.org>; Wed, 9 Jan 2019 14:03:00 -0800 (PST)
Received: by mork.alvestrand.no (Postfix) id 1A43D7C583E; Wed, 9 Jan 2019 23:02:59 +0100 (CET)
Delivered-To: ietf-languages@alvestrand.no
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 014EA7C5414 for <ietf-languages@alvestrand.no>; Wed, 9 Jan 2019 23:02:59 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dCodVaBuQWG6 for <ietf-languages@alvestrand.no>; Wed, 9 Jan 2019 23:02:56 +0100 (CET)
X-Greylist: delayed 03:47:37 by SQLgrey-1.8.0
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
X-Comment: SPF skipped for whitelisted relay - client-ip=192.0.33.71; helo=pechora1.lax.icann.org; envelope-from=prvs=9055b4a44=addison@lab126.com; receiver=ietf-languages@alvestrand.no
Received: from pechora1.lax.icann.org (pechora1.icann.org [192.0.33.71]) by mork.alvestrand.no (Postfix) with ESMTPS id A55477C3FEA for <ietf-languages@alvestrand.no>; Wed, 9 Jan 2019 23:02:55 +0100 (CET)
Received: from smtp-fw-33001.amazon.com (smtp-fw-33001.amazon.com [207.171.190.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora1.lax.icann.org (Postfix) with ESMTPS id 0DDF21E03B1 for <ietf-languages@iana.org>; Wed, 9 Jan 2019 22:02:54 +0000 (UTC)
X-IronPort-AV: E=Sophos;i="5.56,253,1539648000"; d="scan'208";a="775584655"
Received: from sea3-co-svc-lb6-vlan2.sea.amazon.com (HELO email-inbound-relay-1a-16acd5e0.us-east-1.amazon.com) ([10.47.22.34]) by smtp-border-fw-out-33001.sea14.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Jan 2019 22:02:30 +0000
Received: from EX13MTAUWB001.ant.amazon.com (iad55-ws-svc-p15-lb9-vlan3.iad.amazon.com [10.40.159.166]) by email-inbound-relay-1a-16acd5e0.us-east-1.amazon.com (8.14.7/8.14.7) with ESMTP id x09M2L0m069306 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 9 Jan 2019 22:02:28 GMT
Received: from EX13D08UWB003.ant.amazon.com (10.43.161.186) by EX13MTAUWB001.ant.amazon.com (10.43.161.249) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 9 Jan 2019 22:02:27 +0000
Received: from EX13D08UWB002.ant.amazon.com (10.43.161.168) by EX13D08UWB003.ant.amazon.com (10.43.161.186) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 9 Jan 2019 22:02:27 +0000
Received: from EX13D08UWB002.ant.amazon.com ([10.43.161.168]) by EX13D08UWB002.ant.amazon.com ([10.43.161.168]) with mapi id 15.00.1367.000; Wed, 9 Jan 2019 22:02:27 +0000
From: "Phillips, Addison" <addison@lab126.com>
To: Doug Ewell <doug@ewellic.org>, Mark Davis ☕️ <mark@macchiato.com>, Martin Duerst <duerst@it.aoyama.ac.jp>, Arthur Reutenauer <arthur.reutenauer@normalesup.org>
CC: "ietf-languages@iana.org" <ietf-languages@iana.org>
Thread-Topic: [Ietf-languages] Errors in Registry
Thread-Index: AQHUqGUdlm79gFZuukCg1zY2jNk8eqWne4pg
Date: Wed, 09 Jan 2019 22:02:27 +0000
Message-ID: <fd43fa9c583a4ad6bf71a419aba0c58a@EX13D08UWB002.ant.amazon.com>
References: <20190109144854.665a7a7059d7ee80bb4d670165c8327d.8c10a9215e.wbe@email03.godaddy.com>
In-Reply-To: <20190109144854.665a7a7059d7ee80bb4d670165c8327d.8c10a9215e.wbe@email03.godaddy.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.161.178]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (pechora1.lax.icann.org [192.0.33.71]); Wed, 09 Jan 2019 22:02:54 +0000 (UTC)
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-languages/tVHoPbF7WmyWlP43BiqZKs1p7bk>
Subject: Re: [Ietf-languages] Errors in Registry
X-BeenThere: ietf-languages@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ietf-languages.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-languages/>
List-Post: <mailto:ietf-languages@ietf.org>
List-Help: <mailto:ietf-languages-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-languages>, <mailto:ietf-languages-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jan 2019 22:03:03 -0000

Hi Doug,

I'm not seeing the requirement in 3.1.7 that you refer to? There are lots of cases in that section, so it may be simply that I'm overlooking the provision, but most of the cases are for specific record types. The extlang ones are consistent with the 2.2.2 requirement.

In this case we're making an errata correction, so I don't think there is any difficulty involved. The rules are slightly permissive for this reason. See for example 3.4 bullet 2, where we use SHOULD instead of MUST (for example):

   2.   Values in the fields 'Preferred-Value' and 'Deprecated' MAY be
        added, altered, or removed via the registration process.  These
        changes SHOULD be limited to changes necessary to mirror changes
        in one of the underlying standards (ISO 639, ISO 15924, ISO
        3166-1, or UN M.49) and typically alteration or removal of a
        'Preferred-Value' is limited specifically to region codes.

Addison

Addison Phillips
Sr. Principal SDE – I18N (Amazon)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.



> -----Original Message-----
> From: Doug Ewell [mailto:doug@ewellic.org]
> Sent: Wednesday, January 09, 2019 1:49 PM
> To: Phillips, Addison <addison@lab126.com>; Mark Davis ☕️
> <mark@macchiato.com>; Martin Duerst <duerst@it.aoyama.ac.jp>; Arthur
> Reutenauer <arthur.reutenauer@normalesup.org>
> Cc: ietf-languages@iana.org
> Subject: RE: [Ietf-languages] Errors in Registry
> 
> Thanks to all for the support. Forms will be coming later this week.
> 
> I wondered if there was a conflict between Section 2.2.2, which says extlangs
> MUST have a P-V identical to the Subtag field, and Section 3.1.7, which says
> P-Vs MUST be changed so as to avoid chaining.
> 
> I think we can litigate our way out of this: 3.1.7 describes what happens when
> a P-V *changes*, but technically doesn't cover the case where the P-V field is
> *removed*. If there is ever a revision to RFC
> 5646 (I'm not holding my breath), we need to make sure this possible conflict
> is resolved.
> 
> --
> Doug Ewell | Thornton, CO, US | ewellic.org