Re: [precis] Ben Campbell's Yes on draft-ietf-precis-nickname-18: (with COMMENT)

"Ben Campbell" <ben@nostrum.com> Tue, 01 September 2015 20:22 UTC

Return-Path: <ben@nostrum.com>
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 520311B4234 for <precis@ietfa.amsl.com>; Tue, 1 Sep 2015 13:22:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 vk6DA1UOvKYe for <precis@ietfa.amsl.com>; Tue, 1 Sep 2015 13:22:35 -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 BDB7D1B2E91 for <precis@ietf.org>; Tue, 1 Sep 2015 13:22:35 -0700 (PDT)
Received: from [10.0.1.23] (cpe-70-119-203-4.tx.res.rr.com [70.119.203.4]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t81KMNZV078272 (version=TLSv1 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 1 Sep 2015 15:22:34 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-119-203-4.tx.res.rr.com [70.119.203.4] claimed to be [10.0.1.23]
From: Ben Campbell <ben@nostrum.com>
To: Peter Saint-Andre - &yet <peter@andyet.net>
Date: Tue, 01 Sep 2015 15:22:23 -0500
Message-ID: <DB798CF6-C9E7-4DC4-9184-1CEE4EF9534B@nostrum.com>
In-Reply-To: <55E6002F.8050408@andyet.net>
References: <20150901045033.18104.5426.idtracker@ietfa.amsl.com> <55E5E6D0.1000307@andyet.net> <55E6002F.8050408@andyet.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.2r5107)
Archived-At: <http://mailarchive.ietf.org/arch/msg/precis/bkKYXPl8Y1bDhiGCdSA4iPbIcFg>
Cc: draft-ietf-precis-nickname@ietf.org, draft-ietf-precis-nickname.ad@ietf.org, precis@ietf.org, draft-ietf-precis-nickname.shepherd@ietf.org, The IESG <iesg@ietf.org>, joe-ietf@cursive.net, precis-chairs@ietf.org
Subject: Re: [precis] Ben Campbell's Yes on draft-ietf-precis-nickname-18: (with COMMENT)
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: Tue, 01 Sep 2015 20:22:37 -0000

On 1 Sep 2015, at 14:44, Peter Saint-Andre - &yet wrote:

[...]

>>>
>>> -- Abstract:
>>> The abstract could be beefed up against? Maybe say what a nickname 
>>> is in
>>> this context?
>>> [Edit: "Against"?  I meant "a bit".]
>>
>> Good idea.
>
> I suggest:
>
> This document describes methods for handling Unicode strings
> representing memorable, human-friendly names (variously called
> "nicknames", "display names", or "petnames") for people, devices,
> accounts, websites, and other entities.
>

That WFM.

[...]
>>
>>> -- 1.1, 2nd paragraph:
>>> People really use "petname" for this? Who knew?
>>
>> Yes. Perhaps a pointer to
>> http://www.skyhunter.com/marcs/petnames/IntroPetNames.html would be
>> helpful?
>
> I think Section 1.1 could use a bit of clarification through regarding 
> terminology, something like the following...
>
> ###
>
> A number of technologies and applications provide the ability for a
> person to choose a memorable, human-friendly name in a communications
> context, or to set such a name for another entity entity such as a
> device, account, contact, or website.  Such names are variously
> called "nicknames" (e.g., in chatroom applications), "display names"
> (e.g., in Internet mail), or "petnames" (see [1]); for consistency,
> these are all called "nicknames" in this document.
>
> Nicknames are commonly supported in technologies for textual
> chatrooms, e.g., Internet Relay Chat [RFC2811] and multi-party chat
> technologies based on the Extensible Messaging and Presence Protocol
> (XMPP) [RFC6120] [XEP-0045], the Message Session Relay Protocol
> (MSRP) [RFC4975] [I-D.ietf-simple-chat], and Centralized Conferencing
> (XCON) [RFC5239] [I-D.boulton-xcon-session-chat].  Recent chatroom
> technologies also allow internationalized nicknames because they
> support characters from outside the ASCII range [RFC20], typically by
> means of the Unicode character set [Unicode].  Although such
> nicknames tend to be used primarily for display purposes, they are
> sometimes used for programmatic purposes as well (e.g., kicking users
> or avoiding nickname conflicts).
>
> A similar usage enables a person to set their own preferred display
> name or to set a preferred display name for another user (e.g., the
> "display-name" construct in the Internet message format [RFC5322] and
> [XEP-0172] in XMPP).
>
> Memorable, human-friendly names are also used in contexts other than
> personal messaging, such as names for devices (e.g., in a network
> visualization application), websites (e.g., for bookmarks in a web
> browser), accounts (e.g., in a web interface for a list of payees in
> a bank account), people (e.g., in a contact list application), and
> the like.
>
> The rules specified in this document can be applied in all of the
> foregoing contexts.
>
> To increase the likelihood that memorable, human-friendly names will
> work in ways that make sense for typical users throughout the world,
> this document defines rules for preparing, enforcing, and comparing
> internationalized nicknames.

That also WFM. (And for the record, I really didn't expect my "petname" 
observation to be actionable. But I like the proposed text.)


>
> ...
>
> [1] http://www.skyhunter.com/marcs/petnames/IntroPetNames.html
>
> ###
>
> Peter
>
> -- 
> Peter Saint-Andre
> https://andyet.com/