[xmpp] [Technical Errata Reported] RFC6120 (4741)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 13 July 2016 02:43 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 760F212DA4A for <xmpp@ietfa.amsl.com>; Tue, 12 Jul 2016 19:43:20 -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 hc3G-ZgIdMTY for <xmpp@ietfa.amsl.com>; Tue, 12 Jul 2016 19:43:19 -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 6F95812D93F for <xmpp@ietf.org>; Tue, 12 Jul 2016 19:43:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E8F7B80E8E; Tue, 12 Jul 2016 19:43:19 -0700 (PDT)
To: ietf@stpeter.im, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, jhildebr@cisco.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160713024319.5E8F7B80E8E@rfc-editor.org>
Date: Tue, 12 Jul 2016 19:43:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/xmpp/9EGERVK0vUeIej0HbOLTgO6HR0g>
Cc: xmpp@ietf.org, rfc-editor@rfc-editor.org
Subject: [xmpp] [Technical Errata Reported] 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 02:43:20 -0000
The following errata report has been submitted 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 -------------------------------------- Type: Technical Reported by: Sam Whited <sam@samwhited.com> 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. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- 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
- [xmpp] [Errata Held for Document Update] RFC6120 … RFC Errata System
- [xmpp] [Technical Errata Reported] RFC6120 (4741) RFC Errata System