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
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
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.