Re: [I18nrp] Additional input needed for i18nRP BOF

Adam Roach <adam@nostrum.com> Thu, 07 June 2018 03:38 UTC

Return-Path: <adam@nostrum.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 1FC37130E2A for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 20:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level:
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 4b-fOVOyVofV for <i18nrp@ietfa.amsl.com>; Wed, 6 Jun 2018 20:38:38 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32D0130E2D for <i18nrp@ietf.org>; Wed, 6 Jun 2018 20:38:37 -0700 (PDT)
Received: from Svantevit.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w573cZdc096967 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 6 Jun 2018 22:38:35 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.local
To: Nico Williams <nico@cryptonector.com>, Peter Saint-Andre <stpeter@mozilla.com>
Cc: John C Klensin <john-ietf@jck.com>, i18nrp@ietf.org
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> <20180607033006.GT14446@localhost>
From: Adam Roach <adam@nostrum.com>
Message-ID: <cff5d71d-d47f-d8b2-4c93-41b2c0c603c5@nostrum.com>
Date: Wed, 6 Jun 2018 22:38:30 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <20180607033006.GT14446@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/i18nrp/V9gRJCqkoRCt-FGOtu-LAbwaeU0>
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:38:40 -0000

Thanks for taking a first stab at this. I think one of these criteria 
needs a bit of expansion:

On 6/6/18 10:30 PM, Nico Williams wrote:
>   - 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..


This will also be the answer if you have any protocol that compares 
UTF-8 strings, regardless of whether they are identifiers or passwords. 
For example, if one were to define a SIP header field whose value can 
contain characters greater than U+007F, and defined semantics for 
comparison of that value to another string, then such considerations 
would apply.

/a