RFC 7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format", September 2015

Errata ID: 5789
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Florian Schmaus
Date Reported: 2019-07-22
Held for Document Update by: Barry Leiba
Date Held: 2019-07-22

Section 3.2.1 says:

An entity that prepares a string for inclusion in an XMPP domainpart
slot MUST ensure that the string consists only of Unicode code points
that are allowed in NR-LDH labels or U-labels as defined in
[RFC5890].

It should say:

An entity that prepares a string for inclusion in an XMPP
domainpart slot MUST ensure that the string consists only of
- code points allowed in U-labels as defined in [RFC5890]
- % U+0025 PERCENT SIGN
- . U+002E (FULL STOP, DNS label separator "dot")
- : U+003A (COLON)
- ] U+005B (LEFT SQUARE BRACKET)
- [ U+005D (RIGHT SQUARE BRACKET)

Notes:

This is a follow up and update on Errata ID #5769. Besides allowing DNS label separators in the domainpart, this further allows codepoints not allowed in U-labels but required by the IP-literal rule of RFC6874, which is used by RFC7622 to allow IPv6 addresses in XMPP domainparts. As in the previous errata, this also drops the reference to NR-LDH labels, which I believe to be unnecessary.

===== Verifier Notes =====
As with the related errata report, this is held for document update because more discussion and consensus is needed. So this is on record for that discussion.

Report New Errata