draft-ietf-xmpp-nodeprep-02.txt   draft-ietf-xmpp-nodeprep-03.txt 
Network Working Group P. Saint-Andre Network Working Group P. Saint-Andre
Internet-Draft Jabber Software Foundation Internet-Draft Jabber Software Foundation
Expires: October 19, 2003 J. Hildebrand Expires: December 3, 2003 J. Hildebrand
Jabber, Inc. Jabber, Inc.
April 20, 2003 June 04, 2003
Nodeprep: A Stringprep Profile for Node Identifiers in XMPP Nodeprep: A Stringprep Profile for Node Identifiers in XMPP
draft-ietf-xmpp-nodeprep-02 draft-ietf-xmpp-nodeprep-03
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
other groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-Drafts.
Drafts.
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."
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 October 19, 2003. This Internet-Draft will expire on December 3, 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).
skipping to change at page 2, line 21 skipping to change at page 2, line 21
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
Normative 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-01 . . . . . . . . . . . 13 A.1 Changes from draft-ietf-xmpp-nodeprep-02 . . . . . . . . . . . 13
A.2 Changes from draft-ietf-xmpp-nodeprep-00 . . . . . . . . . . . 13 A.2 Changes from draft-ietf-xmpp-nodeprep-01 . . . . . . . . . . . 13
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 14 A.3 Changes from draft-ietf-xmpp-nodeprep-00 . . . . . . . . . . . 13
Intellectual Property and Copyright Statements . . . . . . . . 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 only for XMPP node correct. These processing rules are intended only for XMPP node
identifiers (which are often associated with usernames), and not identifiers (which are often associated with usernames), and are not
intended for arbitrary text. 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
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 entities A node identifier can be employed as one part of an entity's address
that connect to XMPP/Jabber servers for instant messaging and in XMPP. One common usage is as the username of an instant messaging
presence services. The security of such services could be user; another is as the name of a multi-user chat room; and many
compromised if a user entering a single internationalized node other kinds of entities could use node identifiers as part of their
identifier could access another user's account information based on addresses. The security of such services could be compromised based
different interpretations of the internationalized node identifier. on different interpretations of the internationalized node
identifier; for example, a user entering a single internationalized
node identifier could access another user's account information, or a
user could gain access to an otherwise restricted chat room or
service.
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
skipping to change at page 12, line 10 skipping to change at page 12, line 10
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
Normative 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",
10, work in progress)", April 2003. draft-ietf-xmpp-core-13 (work in progress), June 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 10 skipping to change at page 13, line 10
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-01 A.1 Changes from draft-ietf-xmpp-nodeprep-02
o Provided additional examples of node identifier usage.
o Made several small editorial changes.
A.2 Changes from draft-ietf-xmpp-nodeprep-01
o Made small editorial changes to address RFC Editor requirements. o Made small editorial changes to address RFC Editor requirements.
A.2 Changes from draft-ietf-xmpp-nodeprep-00 A.3 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.
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
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
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement Acknowledgement
 End of changes. 13 change blocks. 
22 lines changed or deleted 54 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/