[xmpp] [Errata Held for Document Update] RFC7622 (5769)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 02 July 2019 15:03 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF58120296; Tue, 2 Jul 2019 08:03:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r1PA3bsyi-fE; Tue, 2 Jul 2019 08:03:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E5B7120148; Tue, 2 Jul 2019 08:03:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D506EB81F34; Tue, 2 Jul 2019 08:03:25 -0700 (PDT)
To: flo@geekplace.eu, stpeter@mozilla.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: barryleiba@computer.org, iesg@ietf.org, xmpp@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20190702150325.D506EB81F34@rfc-editor.org>
Date: Tue, 02 Jul 2019 08:03:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/xmpp/fjl2b9kLL01eFpoTt083zqvRUUw>
Subject: [xmpp] [Errata Held for Document Update] RFC7622 (5769)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jul 2019 15:03:45 -0000

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 <flo@geekplace.eu>
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