[Stox] STOX WG status

<markus.isomaki@nokia.com> Sun, 08 June 2014 20:27 UTC

Return-Path: <prvs=229d99f18=markus.isomaki@nokia.com>
X-Original-To: stox@ietfa.amsl.com
Delivered-To: stox@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 568F91A0403 for <stox@ietfa.amsl.com>; Sun, 8 Jun 2014 13:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id yQ6P3LVvVbcx for <stox@ietfa.amsl.com>; Sun, 8 Jun 2014 13:27:29 -0700 (PDT)
Received: from nok-msg-2.service.capgemini.fi (nok-msg-2.service.capgemini.fi []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F71F1A0175 for <stox@ietf.org>; Sun, 8 Jun 2014 13:27:28 -0700 (PDT)
Received: from unknown (HELO NOKWDCFIEXCH01P.nnok.nokia.com) ([]) by noi-msg-2.service.capgemini.fi with ESMTP; 08 Jun 2014 23:27:25 +0300
Received: from NOKWDCFIEXCH02P.nnok.nokia.com ( by NOKWDCFIEXCH01P.nnok.nokia.com ( with Microsoft SMTP Server (TLS) id 15.0.775.38; Sun, 8 Jun 2014 23:27:25 +0300
Received: from NOKWDCFIEXCH02P.nnok.nokia.com ([fe80::99d1:400a:d939:3ebe]) by NOKWDCFIEXCH02P.nnok.nokia.com ([fe80::99d1:400a:d939:3ebe%17]) with mapi id 15.00.0775.031; Sun, 8 Jun 2014 23:27:06 +0300
From: <markus.isomaki@nokia.com>
To: <stox@ietf.org>
Thread-Topic: STOX WG status
Thread-Index: Ac+DUo3AQdK2vYOcREm/6H7x3tZgHw==
Date: Sun, 8 Jun 2014 20:27:06 +0000
Message-ID: <f48e141ae1854bcab5dfdc90c99eb2b1@NOKWDCFIEXCH02P.nnok.nokia.com>
Accept-Language: en-US, fi-FI
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/stox/mh8QZQLESNc23Tbh56oalQBKFGQ
Subject: [Stox] STOX WG status
X-BeenThere: stox@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP-TO-XMPP Working Group discussion list <stox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stox>, <mailto:stox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stox/>
List-Post: <mailto:stox@ietf.org>
List-Help: <mailto:stox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stox>, <mailto:stox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 20:27:31 -0000

Hi all,

Below you can find the chairs' view of the current status of the STOX WG documents. Comments and questions are welcome. 


  * draft-ietf-stox-core
     - Published as RFC 7247

  * draft-ietf-stox-presence
     - Published as RFC 7248
     - Will need an errata to address the FAIL [1] issue.

This documents are complete from STOX WG point of view.


  * draft-ietf-stox-im:
     - Initial WG last call already in December 2013
     - Latest update on March 11 
     - No issues, ready for AD review. Wait to move it together with -chat, though.
  * draft-ietf-stox-chat:
      - Initial WG last call already in December 2013
     - Latest update on March 11
     - Reviews received after the last update
     - New revision needed to address the review comments including FAIL. 

  * draft-ietf-stox-groupchat:
     - WG last call beginning of May
     - Reviews received during and after the last call
     - New version needed to address review comments including FAIL.

Target would be to get these above three documents to AD review within June/July timeframe. Peter, the main author in all of these, has been doing a good work with this set and has promised another round of updates in the next couple of weeks.


  * draft-ietf-stox-media:
    - Latest update on March 20
    - Still needs more work before considering WG last call

Target is to get this document to WG last call phase in August/September timeframe. The chairs have asked the co-authors about their plans and at least Peter and Saul have promised to get busy with this again still in June.


[1] stox-core defines separate gateways in SIP-to-XMPP and XMPP-to-SIP direction, respectively. However, only a single gateway entity is supposed to be used within one "instance" of communication: SIP-to-XMPP gateway is used when the communication is initiated from the SIP side, and vice versa. The message flow diagrams in stox-presecen, stox-chat and stox-groupchat however mistakenly always show two gateways being involved. See http://www.ietf.org/mail-archive/web/stox/current/msg00507.html for more details.

	Markus & Yana