[Errata Held for Document Update] RFC7622 (5769)

The following errata report has been held for document update 
for RFC7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid5769

--------------------------------------
Status: Held for Document Update
Type: Technical

Reported by: Florian Schmaus <[email protected]>
Date Reported: 2019-06-30
Held by: Barry Leiba (IESG)

Section: 3.2.1

Original Text
-------------
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].

Corrected Text
--------------
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], or the DNS label separator "dot" (U+002E, FULL STOP).

Notes
-----
The current specification forbids the inclusion of dots (".") in the domainpart, since they are not allowed in NR-LDH nor U-labels. But they should be allowed, as otherwise a DNS name could never be put into an XMPP domainpart (which is commonly done).

----- Verifier notes -----
This is correct as far as it goes, but there's more to the fix than this, so proper discussion, consensus, and document update are needed.  There are, for example, other dot characters that need to be allowed as well as U+002E.  The bottom line is that Florian is correct that DNS label separators need to be allowed, and the proper fix to the text is deferred to any future document update.

--------------------------------------
RFC7622 (draft-ietf-xmpp-6122bis-24)
--------------------------------------
Title               : Extensible Messaging and Presence Protocol (XMPP): Address Format
Publication Date    : September 2015
Author(s)           : P. Saint-Andre
Category            : PROPOSED STANDARD
Source              : Extensible Messaging and Presence Protocol
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG