[Slim] Adam Roach's No Objection on draft-ietf-slim-multilangcontent-13: (with COMMENT)

Adam Roach <adam@nostrum.com> Wed, 16 August 2017 23:50 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: slim@ietf.org
Delivered-To: slim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 517B2132143; Wed, 16 Aug 2017 16:50:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach <adam@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-slim-multilangcontent@ietf.org, Bernard Aboba <bernard.aboba@gmail.com>, slim-chairs@ietf.org, bernard.aboba@gmail.com, slim@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150292740024.12316.10186295594648032334.idtracker@ietfa.amsl.com>
Date: Wed, 16 Aug 2017 16:50:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/8483FrVXKOpL66yGpd6lL9QrTXw>
Subject: [Slim] Adam Roach's No Objection on draft-ietf-slim-multilangcontent-13: (with COMMENT)
X-BeenThere: slim@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Selection of Language for Internet Media <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Aug 2017 23:50:00 -0000

Adam Roach has entered the following ballot position for
draft-ietf-slim-multilangcontent-13: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I note that this mechanism uses only language tags and implicitly leaves aside
any discussion of script or region tags. I'm going to assume this was a
intentional decision that was considered by the group with the end result being
that there was no perceived need to distinguish between (e.g.) Latin and Jawi
scripts for Malay, or (e.g.) Brazilian and Portuguese variations of 'pt'. (If
this was not an explicit decision made by the WG, I would ask that it be posed
to the WG for an explicit decision -- the current mechanism seems somewhat
deficient in this regard from my admittedly brief analysis of the situation.)

I'm a little worried that an imprecise reading by implementors of the citation
to RFC5646 may lead them to believe that script and region tags may be included
in the Content-Language header fields. If the assumptions I discuss above are
true, please add text making it clear that script and region tags are forbidden.