Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames
draft-ietf-precis-nickname-19

[Ballot comment]
Yay! Just a few nits:

-- Abstract:
The abstract could be beefed up against? Maybe say what a nickname is in this context?
[Edit: "Against"?  I meant "a bit".]

-- 1.1, first paragraph: "...participants to specify a nickname ..."
Plural agreement mismatch.

-- 1.1, 2nd paragraph:
People really use "petname" for this? Who knew?

[Ballot comment]
Yay! Just a few nits:

-- Abstract:
The abstract could be beefed up against? Maybe say what a nickname is in this context?

-- 1.1, first paragraph: "...participants to specify a nickname ..."
Plural agreement mismatch.

-- 1.1, 2nd paragraph:
People really use "petname" for this? Who knew?

[Ballot comment]
Thanks for another well-written draft!

I just have one question and could be wrong, but in table 1, should the output for #9 have <>  around it?

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-precis-nickname-17.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

We received the following comments/questions from the IANA's reviewer:

IANA understands that, upon approval of this document, there is a single action which IANA must complete.

In the PRECIS Profiles subregistry of the Preparation and Comparison of Internationalized Strings (PRECIS) Parameters registry located at:

http://www.iana.org/assignments/precis-parameters/

a single, new profile is to be registered as follows:

Name: Nickname
Base Class: FreeformClass
Replaces: None
Template: [ TBD-at-registration ]
Reference: [ RFC-to-be ]

As this document requests registrations in an Expert Review or Specification Required (see RFC 5226) registry, we will initiate the required Expert Review via a separate request. Expert review will need to be completed before your document can be approved for publication as an RFC.

IANA understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Preparation, Enforcement, and Comparison of Internationalized Strings Representing Nicknames) to Proposed Standard


The IESG has received a request from the Preparation and Comparison of
Internationalized Strings WG (precis) to consider the following document:
- 'Preparation, Enforcement, and Comparison of Internationalized Strings
  Representing Nicknames'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-07-10. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document describes methods for handling Unicode strings
  representing nicknames.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-precis-nickname/ballot/


No IPR declarations have been submitted directly on this I-D.

1. Summary

Matthew Miller is the document shepherd, and Barry Leiba is the
responsible AD.  The document type is expected to be Proposed Standard
upon publication.  This document does not obsolete any other documents.

This document describes methods for handling internationalized
nicknames (or petnames).  Such uses are common in XMPP Multi-User Chat
(MUC), Message Session Relay Protocol (MSRP), and Centralized
Conferencing (XCON), but can also be encountered in other contexts,
such as contact lists, device names, and bookmarks.  This document
provides rules for preparing strings that represent an
internationalized nickname, as well as for comparing two
internationalized nicknames.  Also provided is guidance for using these
rules in application protocols.

2. Review and Consensus

This document received review both from participants active in the
PRECIS Working Group as well as individuals from the XMPP and SIP
communities.  The consensus of the PRECIS Working Group is to publish
this document.

A major topic of discussion in the Working Group was in regard to
"confusables", characters that often visually appear very similar to
(if not indistinguishable from) other characters.  While there was
desire to further combat confusables (e.g., rules and/or guidelines on
incorporating a "confusables" table), ultimately the consensus of the
Working Group was to warn implementers of their existence, use NFKC
normalization to mitigate a large degree of confusables, and note there
might be more rules or guidelines implementers and deployers could
follow (UTS39).

3. Intellectual Property

The document is submitted in full compliance with BCPs 78 and 79.
There are no IPR disclosures referencing this document.

4. Other Points

This document does not create any new IANA registries.  It does
register a new profile to the PRECIS Profiles Registry: Nickname.

There are two nits about possible downref to non-RFC documents (UNICODE
and UTS39).  The downref reported against UNICODE is a limitation of
the tooling; UNICODE is an external specification that is recognized to
have with a status equivalent to IETF Standards Track documents.  The
reference to UTS39 is correct and meets with the Working Group's
consensus.  Other nits are in regard to updated I-Ds this document
references; there is no concern that this document is substantively
outdated with regards to the references, and it is expected the
appropriate reference updates will be made before publication.

1. Summary

Matthew Miller is the document shepherd, and Barry Leiba is the
responsible AD.  The document type is expected to be Proposed Standard
upon publication.  This document does not obsolete any other documents.

This document describes methods for handling internationalized
nicknames (or petnames).  Such uses are common in XMPP Multi-User Chat
(MUC), Message Session Relay Protocol (MSRP), and Centralized
Conferencing (XCON), but can also be encountered in other contexts,
such as contact lists, device names, and bookmarks.  This document
provides rules for preparing strings that represent an
internationalized nickname, as well as for comparing two
internationalized nicknames.  Also provided is guidance for using these
rules in application protocols.

2. Review and Consensus

This document received review both from participants active in the
PRECIS Working Group as well as individuals from the XMPP and SIP
communities.  The consensus of the PRECIS Working Group is to publish
this document.

A major topic of discussion in the Working Group was in regard to
"confusables", characters that often visually appear very similar to
(if not indistinguishable from) other characters.  While there was
desire to further combat confusables (e.g., rules and/or guidelines on
incorporating a "confusables" table), ultimately the consensus of the
Working Group was to warn implementers of their existence, use NFKC
normalization to mitigate a large degree of confusables, and note there
might be more rules or guidelines implementers and deployers could
follow (UTS39).

3. Intellectual Property

The document is submitted in full compliance with BCPs 78 and 79.
There are no IPR disclosures referencing this document.

4. Other Points

This document does not create any new IANA registries.  It does
register a new profile to the PRECIS Profiles Registry: Nickname.

There are two nits about possible downref to non-RFC documents (UNICODE
and UTS39).  The references are correct and meet with the Working
Group's consensus.  Other nits are in regard to updated I-Ds this
document references; there is no concern that this document is
substantively outdated with regards to the references, and it is
expected the appropriate reference updates will be made before
publication.

Notification list changed to draft-ietf-precis-nickname@ietf.org, draft-ietf-precis-nickname.ad@ietf.org, draft-ietf-precis-nickname.shepherd@ietf.org, joe-ietf@cursive.net, precis-chairs@ietf.org, "Matthew Miller" <mamille2@cisco.com> from draft-ietf-precis-nickname@ietf.org, draft-ietf-precis-nickname.ad@ietf.org, draft-ietf-precis-nickname.shepherd@ietf.org, joe-ietf@cursive.net, precis-chairs@ietf.org