draft-ietf-xmpp-nodeprep-01.txt   draft-ietf-xmpp-nodeprep-02.txt 
Network Working Group P. Saint-Andre Network Working Group P. Saint-Andre
Internet-Draft Jabber Software Foundation Internet-Draft Jabber Software Foundation
Expires: August 22, 2003 J. Hildebrand Expires: October 19, 2003 J. Hildebrand
Jabber, Inc. Jabber, Inc.
February 21, 2003 April 20, 2003
Nodeprep: A Stringprep Profile for Node Identifiers in XMPP Nodeprep: A Stringprep Profile for Node Identifiers in XMPP
draft-ietf-xmpp-nodeprep-01 draft-ietf-xmpp-nodeprep-02
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 22, 2003. This Internet-Draft will expire on October 19, 2003.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This document defines a stringprep profile for node identifiers in This document defines a stringprep profile for node identifiers in
the eXtensible Messaging and Presence Protocol (XMPP). the Extensible Messaging and Presence Protocol (XMPP).
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Discussion Venue . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 Discussion Venue . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 Intellectual Property Notice . . . . . . . . . . . . . . . . . 3 1.3 Intellectual Property Notice . . . . . . . . . . . . . . . . . 3
2. Character Repertoire . . . . . . . . . . . . . . . . . . . . . 5 2. Character Repertoire . . . . . . . . . . . . . . . . . . . . . 5
3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4. Normalization . . . . . . . . . . . . . . . . . . . . . . . . 7 4. Normalization . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Prohibited Output . . . . . . . . . . . . . . . . . . . . . . 8 5. Prohibited Output . . . . . . . . . . . . . . . . . . . . . . 8
6. Bidirectional Characters . . . . . . . . . . . . . . . . . . . 9 6. Bidirectional Characters . . . . . . . . . . . . . . . . . . . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Normative References . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 12
A. Revision History . . . . . . . . . . . . . . . . . . . . . . . 13 A. Revision History . . . . . . . . . . . . . . . . . . . . . . . 13
A.1 Changes from draft-ietf-xmpp-nodeprep-00 . . . . . . . . . . . 13 A.1 Changes from draft-ietf-xmpp-nodeprep-01 . . . . . . . . . . . 13
A.2 Changes from draft-ietf-xmpp-nodeprep-00 . . . . . . . . . . . 13
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 14 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
This document, which defines a profile of stringprep (RFC 3454 [1]), This document, which defines a profile of stringprep (RFC 3454 [1]),
specifies processing rules that will enable users to enter specifies processing rules that will enable users to enter
internationalized node identifiers in XMPP (see XMPP Core [2]) and internationalized node identifiers in XMPP (see XMPP Core [2]) and
have the highest chance of getting the content of the strings have the highest chance of getting the content of the strings
correct. These processing rules are intended for XMPP node correct. These processing rules are intended only for XMPP node
identifiers only, and not for arbitrary text. identifiers (which are often associated with usernames), and not
intended for arbitrary text.
This profile defines the following, as required by RFC 3454 [1]: This profile defines the following, as required by RFC 3454 [1]:
o The intended applicability of the profile: internationalized node o The intended applicability of the profile: internationalized node
identifiers within XMPP identifiers within XMPP
o The character repertoire that is the input and output to o The character repertoire that is the input and output to
stringprep: Unicode 3.2, specified in section 2 stringprep: Unicode 3.2, specified in section 2
o The mappings used: specified in section 3 o The mappings used: specified in section 3
skipping to change at page 10, line 15 skipping to change at page 10, line 15
7. Security Considerations 7. Security Considerations
The Unicode and ISO/IEC 10646 repertoires have many characters that The Unicode and ISO/IEC 10646 repertoires have many characters that
look similar. In many cases, users of security protocols might do look similar. In many cases, users of security protocols might do
visual matching, such as when comparing the names of trusted third visual matching, such as when comparing the names of trusted third
parties. Because it is impossible to map similar-looking characters parties. Because it is impossible to map similar-looking characters
without a great deal of context such as knowing the fonts used, without a great deal of context such as knowing the fonts used,
stringprep does nothing to map similar-looking characters together stringprep does nothing to map similar-looking characters together
nor to prohibit some characters because they look like others. nor to prohibit some characters because they look like others.
Node identifiers are commonly employed as the username of users who Node identifiers are commonly employed as the username of entities
connect to XMPP servers for instant messaging and presence services. that connect to XMPP/Jabber servers for instant messaging and
The security of such services could be compromised if a user entering presence services. The security of such services could be
a single internationalized node identifier could access another compromised if a user entering a single internationalized node
user's account information based on different interpretations of the identifier could access another user's account information based on
internationalized node identifier. different interpretations of the internationalized node identifier.
8. IANA Considerations 8. IANA Considerations
This is a profile of stringprep. If and when it becomes an RFC, it This is a profile of stringprep. If and when it becomes an RFC, it
should be registered in the stringprep profile registry maintained by should be registered in the stringprep profile registry maintained by
the IANA [4]. the IANA [4].
Name of this profile: Name of this profile:
Nodeprep Nodeprep
RFC in which the profile is defined: RFC in which the profile is defined:
This document This document
Indicator whether or not this is the newest version of the profile: Indicator whether or not this is the newest version of the profile:
This is the first version of Nodeprep This is the first version of Nodeprep
References Normative References
[1] Hoffman, P. and M. Blanchet, "Preparation of Internationalized [1] Hoffman, P. and M. Blanchet, "Preparation of Internationalized
Strings ("stringprep")", RFC 3454, December 2002. Strings ("stringprep")", RFC 3454, December 2002.
[2] Saint-Andre, P. and J. Miller, "XMPP Core (draft-ietf-xmpp-core- [2] Saint-Andre, P. and J. Miller, "XMPP Core (draft-ietf-xmpp-core-
03, work in progress)", February 2003. 10, work in progress)", April 2003.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[4] Internet Assigned Numbers Authority, "Internet Assigned Numbers [4] Internet Assigned Numbers Authority, "Internet Assigned Numbers
Authority", January 1998, <http://www.iana.org/>. Authority", January 1998, <http://www.iana.org/>.
Authors' Addresses Authors' Addresses
Peter Saint-Andre Peter Saint-Andre
skipping to change at page 13, line 7 skipping to change at page 13, line 7
URI: http://www.jabber.org/people/stpeter.php URI: http://www.jabber.org/people/stpeter.php
Joe Hildebrand Joe Hildebrand
Jabber, Inc. Jabber, Inc.
EMail: jhildebrand@jabber.com EMail: jhildebrand@jabber.com
URI: http://www.jabber.org/people/hildjj.php URI: http://www.jabber.org/people/hildjj.php
Appendix A. Revision History Appendix A. Revision History
Note to RFC editor: please remove this entire appendix, and the Note to RFC Editor: please remove this entire appendix, and the
corresponding entries in the table of contents, prior to publication. corresponding entries in the table of contents, prior to publication.
A.1 Changes from draft-ietf-xmpp-nodeprep-00 A.1 Changes from draft-ietf-xmpp-nodeprep-01
o Made small editorial changes to address RFC Editor requirements.
A.2 Changes from draft-ietf-xmpp-nodeprep-00
o Clarified references to Unicode 3.2 and unassigned code points. o Clarified references to Unicode 3.2 and unassigned code points.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
 End of changes. 13 change blocks. 
19 lines changed or deleted 25 lines changed or added

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