draft-ietf-xmpp-address-08.txt   draft-ietf-xmpp-address-09.txt 
XMPP P. Saint-Andre XMPP P. Saint-Andre
Internet-Draft Cisco Internet-Draft Cisco
Updates: 3920 (if approved) December 10, 2010 Updates: 3920 (if approved) January 6, 2011
Intended status: Standards Track Intended status: Standards Track
Expires: June 13, 2011 Expires: July 10, 2011
Extensible Messaging and Presence Protocol (XMPP): Address Format Extensible Messaging and Presence Protocol (XMPP): Address Format
draft-ietf-xmpp-address-08 draft-ietf-xmpp-address-09
Abstract Abstract
This document defines the format for addresses used in the Extensible This document defines the format for addresses used in the Extensible
Messaging and Presence Protocol (XMPP), including support for non- Messaging and Presence Protocol (XMPP), including support for non-
ASCII characters. This document updates RFC 3920. ASCII characters. This document updates RFC 3920.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 13, 2011. This Internet-Draft will expire on July 10, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 28 skipping to change at page 3, line 28
"stringprep" technology for preparation of non-ASCII characters "stringprep" technology for preparation of non-ASCII characters
[STRINGPREP], including the Nameprep profile for internationalized [STRINGPREP], including the Nameprep profile for internationalized
domain names as specified in [NAMEPREP] and [IDNA2003] along with two domain names as specified in [NAMEPREP] and [IDNA2003] along with two
XMPP-specific profiles for the localpart and resourcepart. XMPP-specific profiles for the localpart and resourcepart.
Since the publication of RFC 3920, IDNA2003 has been superseded by Since the publication of RFC 3920, IDNA2003 has been superseded by
IDNA2008 (see [IDNA-PROTO] and related documents), which is not based IDNA2008 (see [IDNA-PROTO] and related documents), which is not based
on stringprep. Following the lead of the IDNA community, other on stringprep. Following the lead of the IDNA community, other
technology communities that use stringprep have begun discussions technology communities that use stringprep have begun discussions
about migrating away from stringprep toward more "modern" approaches. about migrating away from stringprep toward more "modern" approaches.
The XMPP community is participating in those discussions in order to The XMPP community is participating in those discussions (mostly
find a replacement for the Nodeprep and Resourceprep profiles of within the PRECIS Working Group) in order to find a replacement for
stringprep defined in RFC 3920. However, work on updated handling of the Nodeprep and Resourceprep profiles of stringprep defined in RFC
internationalized addresses is currently in progress within the 3920. Because all other aspects of revised documentation for XMPP
PRECIS Working Group and at the time of this writing it seems that have been incorporated into [XMPP], the XMPP Working Group decided to
such work might take several years to complete. Because all other temporarily split the XMPP address format into a separate document so
aspects of revised documentation for XMPP have been incorporated into as not to significantly delay publication of improved documentation
[XMPP], the XMPP Working Group decided to split the XMPP address for XMPP. It is expected that this document will be obsoleted as
format into a separate specification so as not to significantly delay soon as work on a new approach to preparation and comparison of
publication of improved documentation for XMPP while awaiting the internationalized addresses has been completed.
conclusion of work on updated handling of internationalized
addresses.
Therefore, this specification provides corrected documentation of the Therefore, this specification provides corrected documentation of the
XMPP address format using the internationalization technologies XMPP address format using the internationalization technologies
available in 2004 (when RFC 3920 was published), with the intent that available in 2004 (when RFC 3920 was published). Although this
this specification will be superseded as soon as work on a new document normatively references [IDNA2003] and [NAMEPREP], XMPP
approach to preparation and comparison of internationalized strings software implementations are encouraged to begin migrating to
has been defined by the PRECIS Working Group and applied to the IDNA2008 (see [IDNA-PROTO] and related documents) because the
specific cases of XMPP localparts and resourceparts. In the specification that obsoletes this one will re-use IDNA2008 rather
meantime, this document normatively references [IDNA2003] and than IDNA2003.
[NAMEPREP]; XMPP software implementations are encouraged to begin
migrating to IDNA2008 (see [IDNA-PROTO] and related documents)
because it is nearly certain that the specification superseding this
one will re-use IDNA2008.
This document updates RFC 3920. This document updates RFC 3920.
1.2. Terminology 1.2. Terminology
Many important terms used in this document are defined in [IDNA2003], Many important terms used in this document are defined in [IDNA2003],
[STRINGPREP], [UNICODE], and [XMPP]. [STRINGPREP], [UNICODE], and [XMPP].
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in RFC
[KEYWORDS]. 2119 [KEYWORDS].
2. Addresses 2. Addresses
2.1. Fundamentals 2.1. Fundamentals
An XMPP entity is anything that is network-addressable and that can An XMPP entity is anything that is network-addressable and that can
communicate using XMPP. For historical reasons, the native address communicate using XMPP. For historical reasons, the native address
of an XMPP entity is called a Jabber Identifier or JID. A valid JID of an XMPP entity is called a Jabber Identifier or JID. A valid JID
is a string of [UNICODE] code points, encoded using [UTF-8], and is a string of [UNICODE] code points, encoded using [UTF-8], and
structured as an ordered sequence of localpart, domainpart, and structured as an ordered sequence of localpart, domainpart, and
skipping to change at page 16, line 44 skipping to change at page 16, line 44
(http://www.unicode.org/reports/tr28/). (http://www.unicode.org/reports/tr28/).
[UNICODE-SEC] [UNICODE-SEC]
The Unicode Consortium, "Unicode Technical Report #36: The Unicode Consortium, "Unicode Technical Report #36:
Unicode Security Considerations", 2008. Unicode Security Considerations", 2008.
[UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO [UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003. 10646", STD 63, RFC 3629, November 2003.
[XMPP] Saint-Andre, P., "Extensible Messaging and Presence [XMPP] Saint-Andre, P., "Extensible Messaging and Presence
Protocol (XMPP): Core", draft-ietf-xmpp-3920bis-20 (work Protocol (XMPP): Core", draft-ietf-xmpp-3920bis-22 (work
in progress), December 2010. in progress), December 2010.
7.2. Informative References 7.2. Informative References
[DNSSEC] Arends, R., Austein, R., Larson, M., Massey, D., and S. [DNSSEC] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements", Rose, "DNS Security Introduction and Requirements",
RFC 4033, March 2005. RFC 4033, March 2005.
[IDNA-DEFS] [IDNA-DEFS]
Klensin, J., "Internationalized Domain Names for Klensin, J., "Internationalized Domain Names for
 End of changes. 10 change blocks. 
31 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/