Re: [precis] I-D Action: draft-ietf-precis-mappings-11.txt

Peter Saint-Andre <peter@andyet.net> Wed, 08 July 2015 13:18 UTC

Return-Path: <peter@andyet.net>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9861B34E0 for <precis@ietfa.amsl.com>; Wed, 8 Jul 2015 06:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 FTC2A6m3FrB4 for <precis@ietfa.amsl.com>; Wed, 8 Jul 2015 06:18:13 -0700 (PDT)
Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) (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 A5B841A92E7 for <precis@ietf.org>; Wed, 8 Jul 2015 06:18:13 -0700 (PDT)
Received: by oiyy130 with SMTP id y130so165267738oiy.0 for <precis@ietf.org>; Wed, 08 Jul 2015 06:18:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=ctV7MH5JGcKL4CRm3sWOcOyMYut6+v4UkCMKU3GDhfo=; b=RFCBI5GxUwxR39vEh+bC00DObupGoRgHKhnfJmkJUC8Ybun01CNHQwpX44BaVzLFeK 90FK4JvkgVMgYwiHT32/mOVZnXXbE+YCtClaKQPsX0Fquhfn8GiMKkz5Xc03velk7Cek yR7s8QWISuJP8VCW65gwt8XmKCynZLuwwLv1nV1Hz+dv9GoCuHGWP5JaCN5kiWSsNiRg kIK/krWJoEWZft29PUEf5mLUAH8GvJSDhYuCOzhbVBcl167UwiP08S4QORnI3IaTfo1S AcAF8uK1Dfhmd5webMTtGeCS1XUdirwilO1VMpoxjGxuVQeH26UeQWUTyo+uBxsP4+FK tuqg==
X-Gm-Message-State: ALoCoQm7yFyuba4y81Cix+ELnkQJS0k0Y38tSaNViEnfYyMFCZ6DvIlKZSS12epc9G+mpRQ9o0Zt
X-Received: by 10.182.142.202 with SMTP id ry10mr9481506obb.27.1436361493094; Wed, 08 Jul 2015 06:18:13 -0700 (PDT)
Received: from [10.173.228.54] (mobile-166-173-184-003.mycingular.net. [166.173.184.3]) by smtp.gmail.com with ESMTPSA id s3sm1208167obt.27.2015.07.08.06.18.10 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jul 2015 06:18:11 -0700 (PDT)
References: <20150706100706.11575.52853.idtracker@ietfa.amsl.com> <10EE3CE0-71D4-4058-9810-F46D34AD1A5F@kmd.keio.ac.jp> <559BEFEC.9030807@andyet.net> <26D92CAC-C987-435B-B649-CE78F49789A1@kmd.keio.ac.jp>
Mime-Version: 1.0 (1.0)
In-Reply-To: <26D92CAC-C987-435B-B649-CE78F49789A1@kmd.keio.ac.jp>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <4297FED3-4F3D-422B-82C7-72DDBECDB77F@andyet.net>
X-Mailer: iPhone Mail (12F70)
From: Peter Saint-Andre <peter@andyet.net>
Date: Wed, 08 Jul 2015 07:18:11 -0600
To: Takahiro Nemoto <t.nemo10@kmd.keio.ac.jp>
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/3YvKx3wz8-9__Ob1N5vV1oEBPRY>
Cc: "precis@ietf.org" <precis@ietf.org>
Subject: Re: [precis] I-D Action: draft-ietf-precis-mappings-11.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/precis/>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2015 13:18:15 -0000

Ah, you are right. Thus I think it is better not to change the name. 

Peter

Sent from mobile, might be terse 

> On Jul 8, 2015, at 2:46 AM, Takahiro Nemoto <t.nemo10@kmd.keio.ac.jp> wrote:
> 
> Hi Peter-san,
> 
> Thank you for taking your time to review the mappings document.
> We, co-authors, are thinking the name change is fine, but our concern 
> is that the name change will cause influence to RFC 7564 (framework) 
> wording because it uses "local case mapping" already.
> 
> If we change the name, is it helpful to append remarks such as:
> 
> alternative case mapping (note that this mapping was formerly 
> called "local case mapping", but changed to avoid confusion)
> 
> Regards,
> 
> Nemo
> 
>> 2015/07/08 0:27、Peter Saint-Andre - &yet <peter@andyet.net> のメール:
>> 
>> Thanks, Nemo!
>> 
>> Your changes look good to me.
>> 
>> What do you think about my suggestion to change "local case mapping" to "alternative case mapping"? See here:
>> 
>> https://mailarchive.ietf.org/arch/msg/precis/t0NsOdHCp_V_zfgMamOqEW6vBMY
>> 
>> I still feel that the word "local" might be confusing in several ways.
>> 
>> Peter
>> 
>>> On 7/7/15 1:23 AM, Takahiro Nemoto wrote:
>>> Dear all,
>>> 
>>> Yoneya-san and I submitted the latest version of precis mappings document.
>>> We modified the document to address feedback from Peter-san. Thank you very much, Peter-san.
>>> Please let me know if you have any questions and comments.
>>> Your feedbacks will be greatly appreciated.
>>> 
>>> Regards,
>>> 
>>> Nemo
>>> 
>>>> 転送されたメッセージ:
>>>> 
>>>> 差出人: internet-drafts@ietf.org
>>>> 件名: [precis] I-D Action: draft-ietf-precis-mappings-11.txt
>>>> 日付: 2015年7月6日 19:07:06 JST
>>>> 宛先: <i-d-announce@ietf.org>
>>>> CC: precis@ietf.org
>>>> 
>>>> 
>>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>> This draft is a work item of the Preparation and Comparison of Internationalized Strings Working Group of the IETF.
>>>> 
>>>>       Title           : Mapping characters for PRECIS classes
>>>>       Authors         : Yoshiro YONEYA
>>>>                         Takahiro Nemoto
>>>>    Filename        : draft-ietf-precis-mappings-11.txt
>>>>    Pages           : 12
>>>>    Date            : 2015-07-06
>>>> 
>>>> Abstract:
>>>>  The framework for preparation, enforcement, and comparison of
>>>>  internationalized strings ("PRECIS") defines several classes of
>>>>  strings for use in application protocols.  Because many protocols
>>>>  perform case-sensitive or case-insensitive string comparison, it
>>>>  necessary to define methods for case mapping.  In addition, both the
>>>>  Internationalized Domain Names in Applications (IDNA) and the PRECIS
>>>>  problem statement describe mappings for internationalized strings
>>>>  that are not limited to case, but include width mapping and mapping
>>>>  of delimiters and other special characters that can be taken into
>>>>  consideration.  This document provides guidelines for designers of
>>>>  PRECIS profiles and describes several mappings that can be applied
>>>>  between receiving user input and passing permitted code points to
>>>>  internationalized protocols.  In particular, this document describes
>>>>  both locale-dependent and context-depending case mappings as well as
>>>>  additional mappings for delimiters and special characters.
>>>> 
>>>> 
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-precis-mappings/
>>>> 
>>>> There's also a htmlized version available at:
>>>> https://tools.ietf.org/html/draft-ietf-precis-mappings-11
>>>> 
>>>> A diff from the previous version is available at:
>>>> https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-mappings-11
>>>> 
>>>> 
>>>> Please note that it may take a couple of minutes from the time of submission
>>>> until the htmlized version and diff are available at tools.ietf.org.
>>>> 
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>> 
>> _______________________________________________
>> precis mailing list
>> precis@ietf.org
>> https://www.ietf.org/mailman/listinfo/precis
>