Re: [dispatch] Fwd: I-D Action: draft-christou-sip-xmpp-interop-00.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 14 March 2013 11:58 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10A9821F8D07 for <dispatch@ietfa.amsl.com>; Thu, 14 Mar 2013 04:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.162
X-Spam-Level: **
X-Spam-Status: No, score=2.162 tagged_above=-999 required=5 tests=[FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 m7f7R63FXimN for <dispatch@ietfa.amsl.com>; Thu, 14 Mar 2013 04:58:51 -0700 (PDT)
Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:227]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8EA21F8AD8 for <dispatch@ietf.org>; Thu, 14 Mar 2013 04:58:47 -0700 (PDT)
Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta12.emeryville.ca.mail.comcast.net with comcast id BPxx1l0041u4NiLACPynNm; Thu, 14 Mar 2013 11:58:47 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([IPv6:2001:df8:0:128:2006:56e9:cf8b:4ea7]) by omta21.emeryville.ca.mail.comcast.net with comcast id BPym1l00D2CH3Z58hPymeg; Thu, 14 Mar 2013 11:58:47 +0000
Message-ID: <5141BB76.7080200@alum.mit.edu>
Date: Thu, 14 Mar 2013 19:58:46 +0800
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: dispatch@ietf.org
References: <462D69106F82344E95BC83996D8039D259FCE5F4@ASHBDAG1M1.resource.ds.bah.com>
In-Reply-To: <462D69106F82344E95BC83996D8039D259FCE5F4@ASHBDAG1M1.resource.ds.bah.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1363262327; bh=lscU5/fGzkBgNI13ni7YIJoIFpZRBuROqHOL+QrMp8A=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=pd0UY5uZG3Zq5nFSMFhKTb31OHiCtzAhSUs6hWscW45UwREhjrOLYK0lciX7va53/ fKzL5ITzLYgJeGeFnkNnW1FxDsUUF/Q03exZtiQ3nj44lAKWBQoNAHA8+r4AyzrHQg JMdYY+vxJMmEPTadqRp7RGTGoBeYeAQ8sJC3fe6LukmofVLNw4R+ya/x0sfs7U98pp 2R4oD5ia7AalwqS6eOPeZruG/a+MIX7b5yfUYzYlMOyfneKPtKKVXFZ9QKmTGxr6Bn TBUNfk0feO5bc0selCCEWHF+Wez1tvpllyl2aBaD7zQeX48jSFWrhGeKrmPHFdDvru Q1n4I1GDfqdTg==
Subject: Re: [dispatch] Fwd: I-D Action: draft-christou-sip-xmpp-interop-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 11:58:52 -0000

Hi,

I think this document is good as an overview.

I have another case for you - a variant of both 2.2 and 2.3:

User Brings own Client(s): each user is free to bring his own client, 
with some constraints over which clients will work at all, or will 
provide an acceptable user experience. Here the guidance is mostly 
intended for the developers of "open" clients.

	Thanks,
	Paul

On 3/12/13 10:05 AM, Christou, Christos [USA] wrote:
> All,
>
> We have submitted a draft that describes the different types of SIP to XMPP interoperability use cases.  It primarily serves as an overview type of document to define the different SIP and XMPP use cases that might exist among Service Providers and implementers. In addition, it points to other documents (e.g., CUSAX, SIP-XMPP interworking documents) where the relevant interworking functions are defined.
>
> Please provide any feedback for this document, especially as we continue to finalize the SIP-XMPP Interworking and CUSAX docs.
>
>
>
> -------- Original Message --------
> Subject: I-D Action: draft-christou-sip-xmpp-interop-00.txt
> Date: Sun, 10 Mar 2013 18:50:12 -0700
> From: internet-drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
> 	Title           : Interoperability between the Session Initiation
> Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP)
> 	Author(s)       : Chris Christou
>                            Michael Lundberg
>                            Christopher Ross
>                            Peter Saint-Andre
> 	Filename        : draft-christou-sip-xmpp-interop-00.txt
> 	Pages           : 7
> 	Date            : 2013-03-10
>
> Abstract:
>     This document is intended to serve as a reference point for
>     developers and operators implementing the Session Initiation Protocol
>     (SIP) and the Extensible Messaging and Presence Protocol (XMPP)
>     within their networks.  This document does not define any new
>     protocols but does define the different reference models for
>     deployment of combined use of SIP and XMPP ("CUSAX") clients and SIP-
>     XMPP interworking to ensure consistency across the community.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-christou-sip-xmpp-interop
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-christou-sip-xmpp-interop-00
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>