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

 
Document Type Active Internet-Draft (precis WG)
Last updated 2015-04-14 (latest revision 2015-04-13)
Replaces draft-saintandre-precis-nickname
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream WG state Submitted to IESG for Publication Nov 2010
Document shepherd Joe Hildebrand
IESG IESG state AD Evaluation::Point Raised - writeup needed
Telechat date
Responsible AD Barry Leiba
Send notices 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

Email authors IPR References Referenced by Nits Search lists

PRECIS                                                    P. Saint-Andre
Internet-Draft                                                      &yet
Intended status: Standards Track                          April 13, 2015
Expires: October 15, 2015

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

Abstract

   This document describes methods for handling Unicode strings
   representing nicknames.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 15, 2015.

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Saint-Andre             Expires October 15, 2015                [Page 1]
Internet-Draft              PRECIS: Nickname                  April 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Nickname Profile  . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Preparation . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Enforcement . . . . . . . . . . . . . . . . . . . . . . .   3
     2.3.  Comparison  . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Use in Application Protocols  . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
     6.1.  Reuse of PRECIS . . . . . . . . . . . . . . . . . . . . .   7
     6.2.  Reuse of Unicode  . . . . . . . . . . . . . . . . . . . .   7
     6.3.  Visually Similar Characters . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

1.1.  Overview

   Technologies for textual chatrooms customarily enable participants to
   specify a nickname for use in the room; e.g., this is true of
   Internet Relay Chat [RFC2811] as well as 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).  Note too that nicknames can be used
   not only in chatrooms but also more generally as a user's preferred
   display name (see for instance [XEP-0172]).

   Nicknames (sometimes called "petnames") are also used in contexts
   other than messaging, such as petnames 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
Show full document text