Search RFCs

RFC Editor

Found 2 records.

Status:Verified (1)

RFC 6122, "Extensible Messaging and Presence Protocol (XMPP): Address Format", March 2011

Note: This RFC has been obsoleted byRFC 7622

Errata ID:2765
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Nico Roeser
Date Reported: 2011-04-03
Verifier Name: Robert Sparks
Date Verified: 2011-05-12

Section 7.2 says:

   [XEP-0165]        Saint-Andre, P., "Best Practices to Discourage JID                     Mimicking", XSF XEP 0045, December 2007.

It should say:

   [XEP-0165]        Saint-Andre, P., "Best Practices to Discourage JID                     Mimicking", XSF XEP 0165, December 2007.

Notes:

Seems to be a problem caused by copy-and-paste: forgot to update the XEP number.

Status:Held for Document Update (1)

RFC 6122, "Extensible Messaging and Presence Protocol (XMPP): Address Format", March 2011

Note: This RFC has been obsoleted byRFC 7622

Errata ID:2801
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Florian Zeitz
Date Reported: 2011-05-07
Held for Document Update by: Robert Sparks

Section 2.2 says:

When preparing a text label (consisting of a sequence of UTF-8 encodedUnicode code points) for representation as an internationalized labelin the process of constructing an XMPP domainpart or comparing twoXMPP domainparts, an application MUST ensure that for each text labelit is possible to apply without failing the ToASCII operationspecified in [IDNA2003] with the UseSTD3ASCIIRules flag set (thusforbidding ASCII code points other than letters, digits, andhyphens).

It should say:

When preparing a text label (consisting of a sequence of UTF-8 encodedUnicode code points) for representation as an internationalized labelin the process of constructing an XMPP domainpart, an application MUSTensure that for each text label it is possible to apply without failing theToASCII 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-wisecomparison 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.

Report New Errata