[xmpp] [Errata Held for Document Update] RFC6120 (4741)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 13 July 2016 14:56 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 0F5E512D8C8; Wed, 13 Jul 2016 07:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 rYr5PVhDrQMp; Wed, 13 Jul 2016 07:56:41 -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 BD84D12D17A; Wed, 13 Jul 2016 07:56:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B1E9CB80A95; Wed, 13 Jul 2016 07:56:41 -0700 (PDT)
To: sam@samwhited.com, ietf@stpeter.im
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160713145641.B1E9CB80A95@rfc-editor.org>
Date: Wed, 13 Jul 2016 07:56:41 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/xmpp/3HxanDPOV3fLx60JzEcXjGpN3SI>
Cc: ben@nostrum.com, iesg@ietf.org, xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] [Errata Held for Document Update] RFC6120 (4741)
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 13 Jul 2016 14:56:43 -0000

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

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

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

Reported by: Sam Whited <sam@samwhited.com>
Date Reported: 2016-07-13
Held by: Ben Campbell (IESG)

Section: 8.2.3

Original Text
-------------
1.  The 'id' attribute is REQUIRED for IQ stanzas.

…

3.  An entity that receives a stanza of type "get" or "set" MUST
    reply with an IQ respones of type "result" or "error".  The
    response MUST preserve the 'id' attribute of the request (or be
    empty if the generated stanza did not include an 'id' attribute).

Corrected Text
--------------
1.  The 'id' attribute is REQUIRED for IQ stanzas.

…

3.  An entity that receives a stanza of type "get" or "set" MUST
    reply with an IQ respones of type "result" or "error".  The
    response MUST preserve the 'id' attribute of the request, or
    send an appropriate error if the generated stanza did not
    include an 'id' attribute.

Notes
-----
If the received IQ had an empty ID then it was not valid per point 1 and clients and servers cannot key on the ID (eg. for key mapped lists of IQs pending receipt or dispatch of a reply). An appropriate error or other behavior should be defined if the 'id' is meant to be REQUIRED, otherwise, if point 3 is correct, then 'id' should not be REQUIRED.

--------------------------------------
RFC6120 (draft-ietf-xmpp-3920bis-22)
--------------------------------------
Title               : Extensible Messaging and Presence Protocol (XMPP): Core
Publication Date    : March 2011
Author(s)           : P. Saint-Andre
Category            : PROPOSED STANDARD
Source              : Extensible Messaging and Presence Protocol RAI
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG