Extensible Messaging and Presence Protocol (XMPP): Address Format
draft-ietf-xmpp-6122bis-24

Document Type Active Internet-Draft (xmpp WG)
Last updated 2015-06-18 (latest revision 2015-06-11)
Replaces draft-saintandre-xmpp-6122bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html
Stream WG state Submitted to IESG for Publication
Consensus Yes
Document shepherd Matthew Miller
Shepherd write-up Show (last changed 2015-04-30)
IESG IESG state RFC Ed Queue
Telechat date
Responsible AD Ben Campbell
Send notices to xmpp-chairs@ietf.org, draft-ietf-xmpp-6122bis.ad@ietf.org, draft-ietf-xmpp-6122bis@ietf.org, mamille2@cisco.com, draft-ietf-xmpp-6122bis.shepherd@ietf.org
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state RFC-EDITOR
XMPP                                                      P. Saint-Andre
Internet-Draft                                                      &yet
Obsoletes: 6122 (if approved)                              June 11, 2015
Intended status: Standards Track
Expires: December 13, 2015

   Extensible Messaging and Presence Protocol (XMPP): Address Format
                       draft-ietf-xmpp-6122bis-24

Abstract

   This document defines the address format for the Extensible Messaging
   and Presence Protocol (XMPP), including support for code points
   outside the ASCII range.  This document obsoletes RFC 6122.

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 December 13, 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 December 13, 2015               [Page 1]
Internet-Draft             XMPP Address Format                 June 2015

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Addresses . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Fundamentals  . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Domainpart  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Localpart . . . . . . . . . . . . . . . . . . . . . . . .   7
     3.4.  Resourcepart  . . . . . . . . . . . . . . . . . . . . . .   8
     3.5.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   9
   4.  Enforcement in JIDs and JID Parts . . . . . . . . . . . . . .  13
   5.  Internationalization Considerations . . . . . . . . . . . . .  15
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
     6.1.  Stringprep Profiles Registry  . . . . . . . . . . . . . .  15
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
     7.1.  Reuse of PRECIS . . . . . . . . . . . . . . . . . . . . .  16
     7.2.  Reuse of Unicode  . . . . . . . . . . . . . . . . . . . .  16
     7.3.  Address Spoofing  . . . . . . . . . . . . . . . . . . . .  16
   8.  Conformance Requirements  . . . . . . . . . . . . . . . . . .  18
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  21
   Appendix A.  Differences from RFC 6122  . . . . . . . . . . . . .  24
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .  25
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  25

1.  Introduction

   The Extensible Messaging and Presence Protocol (XMPP) [RFC6120] is an
   application profile of the Extensible Markup Language [XML] for
   streaming XML data in close to real time between any two or more
   network-aware entities.  The address format for XMPP entities was
   originally developed in the Jabber open-source community in 1999,
   first described by [XEP-0029] in 2002, and then defined canonically
   by [RFC3920] in 2004 and [RFC6122] in 2011.

   As specified in RFC 3920 and RFC 6122, the XMPP address format used
   the "stringprep" technology for preparation and comparison of non-
   ASCII characters [RFC3454].  Following the movement of
   internationalized domain names away from stringprep, this document
   defines the XMPP address format in a way that no longer depends on
   stringprep (see the PRECIS problem statement [RFC6885]).  Instead,
   this document builds upon the internationalization framework defined
Show full document text