
From nobody Tue Jul 12 19:43:21 2016
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 (PDT)
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


From nobody Wed Jul 13 07:56:44 2016
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 (PDT)
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


From nobody Thu Jul 21 07:49:13 2016
Return-Path: <ralphm@ik.nu>
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 94AFC12D0B7 for <xmpp@ietfa.amsl.com>; Thu, 21 Jul 2016 07:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.189
X-Spam-Level: 
X-Spam-Status: No, score=-3.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-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 g9emrOfiwILC for <xmpp@ietfa.amsl.com>; Thu, 21 Jul 2016 07:49:10 -0700 (PDT)
Received: from mag.ik.nu (mag.ik.nu [IPv6:2001:16f8:4::61]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BE6512D675 for <xmpp@ietf.org>; Thu, 21 Jul 2016 07:49:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mag.ik.nu (Postfix) with ESMTP id 641CB1600A0; Thu, 21 Jul 2016 16:49:07 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mag.ik.nu
Received: from mag.ik.nu ([IPv6:::1]) by localhost (mag.ik.nu [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Jr-Bjnv0-Dhw; Thu, 21 Jul 2016 16:49:03 +0200 (CEST)
Received: from [IPv6:2001:985:2560:1:c85b:8b90:6578:2acb] (unknown [IPv6:2001:985:2560:1:c85b:8b90:6578:2acb]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ralphm) by mag.ik.nu (Postfix) with ESMTPSA id AA563160096; Thu, 21 Jul 2016 16:49:03 +0200 (CEST)
To: XMPP Summit <summit@xmpp.org>, XSF Members <members@xmpp.org>, Jabber/XMPP software development list <jdev@jabber.org>, xmpp@ietf.org
From: Ralph Meijer <ralphm@ik.nu>
Message-ID: <5790E0DE.40408@ik.nu>
Date: Thu, 21 Jul 2016 16:49:02 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xmpp/T8D-u8nacRNfYi7SFHauX-Tl0WE>
Subject: [xmpp] FOSDEM 2017 and XMPP Summit 21 dates
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: Thu, 21 Jul 2016 14:49:12 -0000

Hi all,

The FOSDEM organization has announced the dates for the 2017 edition:
Saturday 4 and Sunday 5 February. As usual, we will try to arrange for
having another Realtime Lounge, as well as a devroom, as soon as the
Call for Participation happens. Of course, you can already start
thinking about:

 * Your demo for the Realtime Lounge (if allocated). Anything related to
XMPP or other open realtime protocols or technology goes. IoT stuff is
always a great thing to show off something as abstract as protocols.

 * Your talk, presentation, etc., for the devroom (if allocated).

 * Your main track or lightning talk.


Additionally, I am proud to announce that the XSF is once again
organizing an XMPP Summit, for the 21st time. The dates are Thursday 2
and Friday 3 February.

Usually, we spend these days talking about XMPP protocols in plenary
sessions. However, this year, we wanted to settle on the dates as soon
as possible to have plenty of time to do other things. We could have
parallel sessions, BoFs, (invited?) talks from people outside our
community, coding or interop sessions, you name it. In fact:

  You name it!

If you have any suggestions for things we could do at the XMPP Summit,
let me know, or write them down on our shiny new wiki page:

  https://wiki.xmpp.org/web/Summit_21

Please also consider sponsoring the traditional XMPP Dinner, most likely
on Thursday evening, or the XSF in general. You can contact me or any
other Board member on this.

So, jot down the dates for FOSDEM and the XMPP Summit in your calendar,
and sign up as participant at this wiki page, so we can look into Hotel
discounts and generally prepare for another great Summit.

I hope to see a lot of you in Brussels, again.

-- 
Cheers,

ralphm

