draft-ietf-xmpp-address-03.txt   draft-ietf-xmpp-address-04.txt 
Network Working Group P. Saint-Andre Network Working Group P. Saint-Andre
Internet-Draft Cisco Internet-Draft Cisco
Intended status: Standards Track July 26, 2010 Intended status: Standards Track September 24, 2010
Expires: January 27, 2011 Expires: March 28, 2011
Extensible Messaging and Presence Protocol (XMPP): Address Format Extensible Messaging and Presence Protocol (XMPP): Address Format
draft-ietf-xmpp-address-03 draft-ietf-xmpp-address-04
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. ASCII characters.
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 32 skipping to change at page 1, line 32
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 January 27, 2011. This Internet-Draft will expire on March 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 29 skipping to change at page 2, line 29
4.4.1. Address Forging . . . . . . . . . . . . . . . . . . . 9 4.4.1. Address Forging . . . . . . . . . . . . . . . . . . . 9
4.4.2. Address Mimicking . . . . . . . . . . . . . . . . . . 9 4.4.2. Address Mimicking . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. Nodeprep Profile of Stringprep . . . . . . . . . . . . . . 11 5.1. Nodeprep Profile of Stringprep . . . . . . . . . . . . . . 11
5.2. Resourceprep Profile of Stringprep . . . . . . . . . . . . 11 5.2. Resourceprep Profile of Stringprep . . . . . . . . . . . . 11
6. Conformance Requirements . . . . . . . . . . . . . . . . . . . 11 6. Conformance Requirements . . . . . . . . . . . . . . . . . . . 11
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . . 13
7.2. Informative References . . . . . . . . . . . . . . . . . . 14 7.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Nodeprep . . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Nodeprep . . . . . . . . . . . . . . . . . . . . . . 15
A.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 16 A.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 15
A.2. Character Repertoire . . . . . . . . . . . . . . . . . . . 16 A.2. Character Repertoire . . . . . . . . . . . . . . . . . . . 16
A.3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 16 A.3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 16
A.4. Normalization . . . . . . . . . . . . . . . . . . . . . . 16 A.4. Normalization . . . . . . . . . . . . . . . . . . . . . . 16
A.5. Prohibited Output . . . . . . . . . . . . . . . . . . . . 16 A.5. Prohibited Output . . . . . . . . . . . . . . . . . . . . 16
A.6. Bidirectional Characters . . . . . . . . . . . . . . . . . 17 A.6. Bidirectional Characters . . . . . . . . . . . . . . . . . 17
A.7. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 17 A.7. Notes . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Appendix B. Resourceprep . . . . . . . . . . . . . . . . . . . . 18 Appendix B. Resourceprep . . . . . . . . . . . . . . . . . . . . 18
B.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 18 B.1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 18
B.2. Character Repertoire . . . . . . . . . . . . . . . . . . . 18 B.2. Character Repertoire . . . . . . . . . . . . . . . . . . . 18
B.3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 19 B.3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . 18
B.4. Normalization . . . . . . . . . . . . . . . . . . . . . . 19 B.4. Normalization . . . . . . . . . . . . . . . . . . . . . . 19
B.5. Prohibited Output . . . . . . . . . . . . . . . . . . . . 19 B.5. Prohibited Output . . . . . . . . . . . . . . . . . . . . 19
B.6. Bidirectional Characters . . . . . . . . . . . . . . . . . 19 B.6. Bidirectional Characters . . . . . . . . . . . . . . . . . 19
Appendix C. Differences From RFC 3920 . . . . . . . . . . . . . . 19 Appendix C. Differences From RFC 3920 . . . . . . . . . . . . . . 19
Appendix D. Copying Conditions . . . . . . . . . . . . . . . . . 20
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
The Extensible Messaging and Presence Protocol [XMPP] is an The Extensible Messaging and Presence Protocol [XMPP] is an
application profile of the Extensible Markup Language [XML] for application profile of the Extensible Markup Language [XML] for
streaming XML data in close to real time between any two or more streaming XML data in close to real time between any two or more
network-aware entities. The address format for XMPP entities was network-aware entities. The address format for XMPP entities was
originally developed in the Jabber open-source community in 1999, originally developed in the Jabber open-source community in 1999,
first described by [XEP-0029] in 2002, and defined canonically by first described by [XEP-0029] in 2002, and defined canonically by
skipping to change at page 14, line 16 skipping to change at page 14, line 16
(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-10 (work Protocol (XMPP): Core", draft-ietf-xmpp-3920bis-16 (work
in progress), July 2010. in progress), September 2010.
7.2. Informative References 7.2. Informative References
[DNS] Mockapetris, P., "Domain names - implementation and [DNS] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, November 1987.
[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
Applications (IDNA): Definitions and Document Framework", Applications (IDNA): Definitions and Document Framework",
draft-ietf-idnabis-defs-13 (work in progress), RFC 5890, August 2010.
January 2010.
[IDNA-PROTO] [IDNA-PROTO]
Klensin, J., "Internationalized Domain Names in Klensin, J., "Internationalized Domain Names in
Applications (IDNA): Protocol", Applications (IDNA): Protocol", RFC 5891, August 2010.
draft-ietf-idnabis-protocol-18 (work in progress),
January 2010.
[INTEROP] Masinter, L., "Formalizing IETF Interoperability [INTEROP] Masinter, L., "Formalizing IETF Interoperability
Reporting", draft-ietf-newtrk-interop-reports-00 (work in Reporting", draft-ietf-newtrk-interop-reports-00 (work in
progress), October 2005. progress), October 2005.
[IRI] Duerst, M. and M. Suignard, "Internationalized Resource [IRI] Duerst, M. and M. Suignard, "Internationalized Resource
Identifiers (IRIs)", RFC 3987, January 2005. Identifiers (IRIs)", RFC 3987, January 2005.
[PROCESS] Bradner, S., "The Internet Standards Process -- Revision [PROCESS] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
skipping to change at page 20, line 4 skipping to change at page 19, line 45
Based on consensus derived from implementation and deployment Based on consensus derived from implementation and deployment
experience as well as formal interoperability testing, the following experience as well as formal interoperability testing, the following
substantive modifications were made from RFC 3920. substantive modifications were made from RFC 3920.
o Corrected the ABNF syntax to (1) ensure consistency with [URI] and o Corrected the ABNF syntax to (1) ensure consistency with [URI] and
[IRI], and (2) prevent zero-length localparts, domainparts, and [IRI], and (2) prevent zero-length localparts, domainparts, and
resourceparts. resourceparts.
o To avoid confusion with the term "node" as used in [XEP-0030] and o To avoid confusion with the term "node" as used in [XEP-0030] and
[XEP-0060], changed the term "node identifier" to "localpart" (but [XEP-0060], changed the term "node identifier" to "localpart" (but
retained the name "Nodeprep" for backward compatibility). retained the name "Nodeprep" for backward compatibility).
o To avoid confusion with the terms "resource" and "identifier" as o To avoid confusion with the terms "resource" and "identifier" as
used in [URI], changed the term "resource identifier" to used in [URI], changed the term "resource identifier" to
"resourcepart". "resourcepart".
o Corrected the nameprep processing rules to require use of the o Corrected the nameprep processing rules to require use of the
UseSTD3ASCIIRules flag. UseSTD3ASCIIRules flag.
Appendix D. Copying Conditions
Regarding this entire document or any portion of it, the author makes
no guarantees and is not responsible for any damage resulting from
its use. The author grants irrevocable permission to anyone to use,
modify, and distribute it in any way that does not diminish the
rights of anyone else to use, modify, and distribute it, provided
that redistributed derivative works do not contain misleading author
or version information. Derivative works need not be licensed under
similar terms.
Author's Address Author's Address
Peter Saint-Andre Peter Saint-Andre
Cisco Cisco
1899 Wyknoop Street, Suite 600 1899 Wyknoop Street, Suite 600
Denver, CO 80202 Denver, CO 80202
USA USA
Phone: +1-303-308-3282 Phone: +1-303-308-3282
Email: psaintan@cisco.com Email: psaintan@cisco.com
 End of changes. 11 change blocks. 
26 lines changed or deleted 10 lines changed or added

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