Subject: [xmpp] [Technical Errata Reported] RFC6122 (2801)

From: RFC Errata System <[email-masked]>
Date: Sat, 7 May 2011 10:59:18 -0700 (PDT)

The following errata report has been submitted for RFC6122,
"Extensible Messaging and Presence Protocol (XMPP): Address Format".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6122&eid=2801

--------------------------------------
Type: Technical
Reported by: Florian Zeitz <[email-masked]>

Section: 2.2

Original Text
-------------
When preparing a text label (consisting of a sequence of UTF-8 encoded
Unicode code points) for representation as an internationalized label
in the process of constructing an XMPP domainpart or comparing two
XMPP domainparts, an application MUST ensure that for each text label
it is possible to apply without failing the ToASCII operation
specified in [IDNA2003] with the UseSTD3ASCIIRules flag set (thus
forbidding ASCII code points other than letters, digits, and
hyphens).

Corrected Text
--------------
When preparing a text label (consisting of a sequence of UTF-8 encoded
Unicode code points) for representation as an internationalized label
in the process of constructing an XMPP domainpart, an application MUST
ensure that for each text label it is possible to apply without failing the
ToASCII operation specified in [IDNA2003] with the UseSTD3ASCIIRules flag set
(thus forbidding ASCII code points other than letters, digits, and hyphens).
When comparing two XMPP domainparts, an application MUST first apply the
[NAMEPREP] profile of [STRINGPREP] to both domainparts and perform a byte-wise
comparison afterwards.

Notes
-----
As is the RFC does not specify how to compare XMPP domainparts. It should have been pointed out that normalization is required and how to do that normalization.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6122 (draft-ietf-xmpp-address-09)
--------------------------------------
Title               : Extensible Messaging and Presence Protocol (XMPP): Address Format
Publication Date    : March 2011
Author(s)           : P. Saint-Andre
Category            : PROPOSED STANDARD
Source              : Extensible Messaging and Presence Protocol
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG