Re: [precis] I-D Action: draft-ietf-precis-7700bis-01.txt

Sam Whited <sam@samwhited.com> Mon, 16 May 2016 21:53 UTC

Return-Path: <sam@samwhited.com>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D90312DAD1 for <precis@ietfa.amsl.com>; Mon, 16 May 2016 14:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=samwhited.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 BX9fM7shLYLs for <precis@ietfa.amsl.com>; Mon, 16 May 2016 14:53:04 -0700 (PDT)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (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 52A3112D539 for <precis@ietf.org>; Mon, 16 May 2016 14:53:04 -0700 (PDT)
Received: by mail-qg0-x235.google.com with SMTP id 90so96585864qgz.1 for <precis@ietf.org>; Mon, 16 May 2016 14:53:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samwhited.com; s=swgoo; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Eb7bg5rTPGgF+p3BKs2whBp2JJgajYWsOaFr1XQO8as=; b=pl/7GSZZQmWLp3hea7rdYpvkaFwqTBQldwn1xzk4HsyxB89QZHHmDyLHYFvNiPJNYB aUC7AtIU9fOaTcsKYff9TUfxKVTyyrL6XpcNc4pFRvpRAW6RPgYIuy72XS6k2O2xqYXN IaOLwuPPrxr4jAEEX95Vo5CEDzxr4QI016or4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Eb7bg5rTPGgF+p3BKs2whBp2JJgajYWsOaFr1XQO8as=; b=W31zxVkMiSU2Rf34xxNrBjOgaYRM5qgYgIEVujVSe/KHVhJVlHDM4HF1rqD/DN9Vx6 flVXqDNfZEDi/iUR558+chvMyFY0p2cGATxzADlENSm3DV1fI+idwpEbC47YEjt7zSjJ wpmk5kmVKzQf5yHxgBDS47qpwncqWUSksQpU2crHpiivN3sfWTuR5UgW4gSIaJSAJQuZ I5PV+MTJr8B6URjCliM6cbIwde26luviP7UGnF2JwYEeq84vcBcTwab8HE1aG3OEwWbo xt7PENg/XlatJdhIt7RG6nqoMMy3q5d3QHnxOqvO8wJu2aoB6t8rwh0hUfdWCmd4IwFw uO6g==
X-Gm-Message-State: AOPr4FWhBd05hzB/2L6Gg2G54fRkVmx/ElhKQ8Mo+NDds/i8kmgo+AJDK5oP1Q6ZYJ3NNvuGA8ciNsr9xszNiw==
X-Received: by 10.140.42.195 with SMTP id c61mr31084058qga.40.1463435583424; Mon, 16 May 2016 14:53:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.55.146.5 with HTTP; Mon, 16 May 2016 14:52:23 -0700 (PDT)
X-Originating-IP: [72.48.156.244]
In-Reply-To: <20160505174255.20595.13753.idtracker@ietfa.amsl.com>
References: <20160505174255.20595.13753.idtracker@ietfa.amsl.com>
From: Sam Whited <sam@samwhited.com>
Date: Mon, 16 May 2016 16:52:23 -0500
Message-ID: <CAHbk4RJVGUxrMYoOX6e7Z924C1Na-uhYsc8SKScBa3rc4j-1jQ@mail.gmail.com>
To: peter@filament.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/SlwQoSpWtXEL_NZ4nKyqg-VXeX8>
Cc: precis@ietf.org
Subject: Re: [precis] I-D Action: draft-ietf-precis-7700bis-01.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 16 May 2016 21:53:06 -0000

Hi Peter et al.

A few quick notes regarding your draft to replace RFC 7700:

* Nit: §1.1 ¶3 uses the term "display name" several times, but the
document otherwise uses the term "nickname"
* §2.1: "May any instances of non-ASCII space be mapped…" sounds odd,
should this just say "Instances of non-ASCII space should be mapped…"
* §2.2 Specifies that UTF-8 MUST be used as the encoding; do we really
want to limit this to UTF-8 only? Is this for comparison purposes?
Then again, 99.99% of the time UTF-8 is what you should be using
anyways, so I'm not sure that it matters.
* §2.3: "Normalization Rule" is listed twice for enforcement


Best,
Sam


On Thu, May 5, 2016 at 12:42 PM,  <internet-drafts@ietf.org>; wrote:
>
> 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 of the IETF.
>
>         Title           : Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames
>         Author          : Peter Saint-Andre
>         Filename        : draft-ietf-precis-7700bis-01.txt
>         Pages           : 11
>         Date            : 2016-05-05
>
> Abstract:
>    This document describes methods for handling Unicode strings
>    representing memorable, human-friendly names (called "nicknames",
>    "display names", or "petnames") for people, devices, accounts,
>    websites, and other entities.  This document obsoletes RFC 7700.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-precis-7700bis/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-precis-7700bis-01
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-7700bis-01
>
>
> 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



-- 
Sam Whited
pub 4096R/54083AE104EA7AD3
https://blog.samwhited.com