
From stpeter@stpeter.im  Tue Jun 18 09:07:21 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1E711E80E4 for <simple@ietfa.amsl.com>; Tue, 18 Jun 2013 09:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4AmJdVfVINw for <simple@ietfa.amsl.com>; Tue, 18 Jun 2013 09:07:21 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id DF71811E80DC for <simple@ietf.org>; Tue, 18 Jun 2013 09:07:20 -0700 (PDT)
Received: from sjc-vpn5-823.cisco.com (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9DB8C41189; Tue, 18 Jun 2013 10:21:14 -0600 (MDT)
Message-ID: <51C085B6.6080508@stpeter.im>
Date: Tue, 18 Jun 2013 10:07:18 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: simple@ietf.org
References: <20130618155949.923.24534.idtracker@ietfa.amsl.com>
In-Reply-To: <20130618155949.923.24534.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.1
X-Forwarded-Message-Id: <20130618155949.923.24534.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Simple] Fwd: Last Call: <draft-ivov-xmpp-cusax-06.txt> (CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)) to Informational RFC
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 16:07:21 -0000

FYI.


-------- Original Message --------
Subject: Last Call: <draft-ivov-xmpp-cusax-06.txt> (CUSAX: Combined Use
of the Session Initiation Protocol (SIP) and the Extensible Messaging
and Presence Protocol (XMPP)) to Informational RFC
Date: Tue, 18 Jun 2013 08:59:49 -0700
From: The IESG <iesg-secretary@ietf.org>
Reply-To: ietf@ietf.org
To: IETF-Announce <ietf-announce@ietf.org>


The IESG has received a request from an individual submitter to consider
the following document:
- 'CUSAX: Combined Use of the Session Initiation Protocol (SIP) and the
   Extensible Messaging and Presence Protocol (XMPP)'
  <draft-ivov-xmpp-cusax-06.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-07-16. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes suggested practices for combined use of the
   Session Initiation Protocol (SIP) and the Extensible Messaging and
   Presence Protocol (XMPP).  Such practices aim to provide a single
   fully featured real-time communication service by using complementary
   subsets of features from each of the protocols.  Typically such
   subsets would include telephony capabilities from SIP and instant
   messaging and presence capabilities from XMPP.  This specification
   does not define any new protocols or syntax for either SIP or XMPP.
   However, implementing the practices outlined in this document may
   require modifying or at least reconfiguring existing client and
   server-side software.  Also, it is not the purpose of this document
   to make recommendations as to whether or not such combined use should
   be preferred to the mechanisms provided natively by each protocol
   (for example, SIP's SIMPLE or XMPP's Jingle).  It merely aims to
   provide guidance to those who are interested in such a combined use.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ivov-xmpp-cusax/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ivov-xmpp-cusax/ballot/


No IPR declarations have been submitted directly on this I-D.





From stpeter@stpeter.im  Wed Jun 19 10:11:13 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: simple@ietfa.amsl.com
Delivered-To: simple@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6813621F9113 for <simple@ietfa.amsl.com>; Wed, 19 Jun 2013 10:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.126
X-Spam-Level: 
X-Spam-Status: No, score=-102.126 tagged_above=-999 required=5 tests=[AWL=-0.397, BAYES_00=-2.599, SARE_MLH_Stock1=0.87, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6zQqmuWgYFKv for <simple@ietfa.amsl.com>; Wed, 19 Jun 2013 10:11:13 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 60B0D21F8EAE for <simple@ietf.org>; Wed, 19 Jun 2013 10:10:52 -0700 (PDT)
Received: from ergon.local (unknown [64.101.72.59]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C4F7E41278; Wed, 19 Jun 2013 11:10:49 -0600 (MDT)
Message-ID: <51C1E617.4080907@stpeter.im>
Date: Wed, 19 Jun 2013 11:10:47 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: simple@ietf.org
References: <E44893DD4E290745BB608EB23FDDB7620A01C79D@008-AM1MPN1-042.mgdnok.nokia.com>
In-Reply-To: <E44893DD4E290745BB608EB23FDDB7620A01C79D@008-AM1MPN1-042.mgdnok.nokia.com>
X-Enigmail-Version: 1.5.1
X-Forwarded-Message-Id: <E44893DD4E290745BB608EB23FDDB7620A01C79D@008-AM1MPN1-042.mgdnok.nokia.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [Simple] Fwd: [Stox] STOX WG officially approved - charter and work plan
X-BeenThere: simple@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP for Instant Messaging and Presence Leveraging Extensions <simple.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/simple>, <mailto:simple-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/simple>
List-Post: <mailto:simple@ietf.org>
List-Help: <mailto:simple-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/simple>, <mailto:simple-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 17:11:13 -0000

FYI. Please join the stox@ietf.org list to participate:

https://www.ietf.org/mailman/listinfo/stox

Peter


-------- Original Message --------
Subject: [Stox] STOX WG officially approved - charter and work plan
Date: Wed, 19 Jun 2013 09:57:28 +0000
From: <Markus.Isomaki@nokia.com>
To: <stox@ietf.org>
CC: yana@jitsi.org

Hi all,

The SIP-to-XMPP (STOX) WG has now been officially approved by the IESG.
Our charter can be found at
<http://datatracker.ietf.org/wg/stox/charter/>. Myself
(markus.isomaki@nokia.com) and Yana Stamcheva (yana@jitsi.org) will act
as co-chairs.

The plan outlined in the charter is that this will be a focused and
relatively straight-forward effort that we aim to finish in just a few
months. The charter has these milestones:

Jun 2013  Accept starting-point mapping specifications as WG items
Aug 2013  Start Working Group Last Call on mapping specifications
Oct 2013  Submit mapping specifications to the IESG

Yana and I have additionally outlined a bit more detailed plan:

- June: One week consensus call on adopting the current drafts as WG items.
- Latest by July 8: Submit current drafts as -00 WG drafts.
- July: Ask people to comment and raise open issues about the drafts,
ask co-authors to prepare presentations about open issues for IETF 87.
Start recruiting reviewers and if needed, co-authors.
- IETF 87: Meet  for 1 hour. Discuss open issues. Agree on the deadline
for reviews and WG last call on the documents. Decide if all documents
can proceed in the same timeline, or whether some phasing will be needed.
- By end of August: Start the official WG last call.
- September - October: Process last call comments and finalize the
documents for the IESG review.
- IETF 88: Meet if there is interest and energy to discuss about
rechartering, i.e. adding new WG items.

Let us know if you have any feedback to this.

I will next send a few mails to the list about specific topics such as
our first milestone, i.e. the acceptance of the current drafts as WG items.

Markus


_______________________________________________
stox mailing list
stox@ietf.org
https://www.ietf.org/mailman/listinfo/stox


