IETF Logo Mail Archive

Re: [I18nrp] Additional input needed for i18nRP BOF

Nico Williams <nico@cryptonector.com> Thu, 07 June 2018 03:30 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: i18nrp@ietfa.amsl.com
Delivered-To: i18nrp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF8B130E29 for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 20:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.795] 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 CbWjdXeCHcls for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 20:30:09 -0700 (PDT)
Received: from homiemail-a27.g.dreamhost.com (homie-sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD545130DEF for <i18nrp@ietf.org>; Wed, 6 Jun 2018 20:30:09 -0700 (PDT)
Received: from homiemail-a27.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a27.g.dreamhost.com (Postfix) with ESMTP id 3CC15A009A82; Wed, 6 Jun 2018 20:30:09 -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=zbNOwaQKlXPQeO 7WvNqZfVlAwHs=; b=LVdNbT5KHx1Oty81MeqvtZ1dQ/JUgMYhQghhYqTeKlt1mr TDM854S9/+1YBeJbYndKHwpz3bk1BzSI0WyTh+hQe/bYQmbkl5ASKKdTTXb3uZyz BAv1HHbZ8edp/RQpjDwUMbGreWHhh2E1ABLID1oJO/Vsw2B42q4Gxzw8vDFEI=
Received: from localhost (unknown [8.2.105.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a27.g.dreamhost.com (Postfix) with ESMTPSA id 9C6C2A009A81; Wed, 6 Jun 2018 20:30:08 -0700 (PDT)
Date: Wed, 6 Jun 2018 22:30:07 -0500
From: Nico Williams <nico@cryptonector.com>
To: Peter Saint-Andre <stpeter@mozilla.com>
Cc: Adam Roach <adam@nostrum.com>, John C Klensin <john-ietf@jck.com>, i18nrp@ietf.org
Message-ID: <20180607033006.GT14446@localhost>
References: <CE6F76BB323F1555D6B217A5@PSB> <9ecf8b7a-d086-1c56-03fb-6773aed332c6@nostrum.com> <4DA478C4C99396556E1B3EF1@PSB> <a31e91ff-c78c-6a7c-fe8c-70b9563312f7@nostrum.com> <8774afa2-4d3f-bc08-69af-f88e229f547a@mozilla.com> <07356789-b93f-b1a2-21d6-bef704b7c0b0@nostrum.com> <a6b7bf5c-3f37-e97b-7e44-c9e648bdbcef@mozilla.com> <ba6339f3-eb5f-4d14-51fb-256d6682f37e@nostrum.com> <c6d2a8d7-301b-c017-34ac-44da954c0b46@mozilla.com> <20180607031752.GS14446@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180607031752.GS14446@localhost>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/6A8puJ_-hKZhKIR9fXIXKwruamY>
Subject: Re: [I18nrp] Additional input needed for i18nRP BOF
X-BeenThere: i18nrp@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Internationalization Review Procedures <i18nrp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i18nrp/>
List-Post: <mailto:i18nrp@ietf.org>
List-Help: <mailto:i18nrp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i18nrp>, <mailto:i18nrp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Jun 2018 03:30:13 -0000

An initial, rough, incomplete questionnaire for triaging:

 - does the document deal with a protocol?

   No?  -> no I18NDIR review

 - does the protocol carry error and other messages for users?

   Yes? -> I18NDIR review necessary; the protocol should support
           language negotiation for localization (L10N), and it should
           use UTF-8.

 - does the protocol carry identifier strings (e.g., usernames,
   filenames, ...) or passwords?

   Yes? -> I18NDIR review necessary; the protocol should specify some
           sort of stringprep, whether to normalize or allow
           form-insensitivity, etc..

 - does the protocol have domainname slots?

   Yes? -> I18NDIR review necessary; must indicate which slots are
           IDNA-aware and so on.

 - does the protocol carry "shell" session data?

   Yes? -> I18NDIR review necessary; the protocol should support locale
           negotiation, or at least negotiation of language and codeset.

Note that the use of constant strings in protocol elements does not imply
I18N considerations if they are not to be displayed to users, or if
localization of them is a local problem.

If "no" to all of these questions, then no I18NDIR review should be
needed.

Nico
--

v2.8.7 | Report a Bug | By Email