
From rjsparks@nostrum.com  Mon Dec  6 13:28:35 2010
Return-Path: <rjsparks@nostrum.com>
X-Original-To: sixpac@core3.amsl.com
Delivered-To: sixpac@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27E163A68B1 for <sixpac@core3.amsl.com>; Mon,  6 Dec 2010 13:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qvu3A566vbq3 for <sixpac@core3.amsl.com>; Mon,  6 Dec 2010 13:28:33 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id D92883A68AF for <sixpac@ietf.org>; Mon,  6 Dec 2010 13:28:32 -0800 (PST)
Received: from [192.168.2.105] (pool-173-71-48-4.dllstx.fios.verizon.net [173.71.48.4]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id oB6LTs0Y046806 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 Dec 2010 15:29:55 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <B3F72E5548B10A4A8E6F4795430F841840CEE9EC2F@NOK-EUMSG-02.mgdnok.nokia.com>
Date: Mon, 6 Dec 2010 15:29:54 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com>
References: <4CDB9E64.6070704@stpeter.im> <B3F72E5548B10A4A8E6F4795430F841840CEE9EC2F@NOK-EUMSG-02.mgdnok.nokia.com>
To: "<Markus.Isomaki@nokia.com>" <Markus.Isomaki@nokia.com>
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 173.71.48.4 is authenticated by a trusted mechanism)
Cc: sixpac@ietf.org
Subject: Re: [sixpac] charter proposal - correlation between SIP and XMPP
X-BeenThere: sixpac@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "The SIXPAC \(SIP Interworking with XMPP in Presence Aware Clients\) list is dedicated to discussion of dual-stack SIP/XMPP user agents." <sixpac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sixpac>
List-Post: <mailto:sixpac@ietf.org>
List-Help: <mailto:sixpac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2010 21:28:35 -0000

Discussion on this and the other threads appears to be stalling. Can we =
draw some conclusions?

For this thread, I think Markus was trying to soften (maybe remove?) =
this goal:
>> - Correlating an XMPP IM session with a SIP voice/video session, and
>> vice-versa
>=20

This is a place I think a group could get really stuck - as markus hints =
at below, how is this not going
to run into the same set of issues (and run into the same set of =
problems trying to specify a solution for)
that Hadriel's SIPSCOTCH proposal is having?


RjS


On Nov 11, 2010, at 11:06 AM, <Markus.Isomaki@nokia.com> =
<Markus.Isomaki@nokia.com> wrote:

> Hi,
>=20
> The charter says:
>=20
>> - There is no correlation between an XMPP IM session and a SIP voice
>> or video session, thus preventing a dual-stack endpoint from =
providing
>> integrated user interfaces and communications history
>=20
> It has been pointed out that in SIP we may have practical challenges =
to achieve this with a high likelihood. This means that if our solution =
is based on some kind of token that is exchanged between the two SIXPAC =
clients over SIP (so that they can replay it later on over XMPP for =
correlation), and if we put that token in some kind of a new header, it =
is possible that B2BUA's on the path will "eat" such headers out. So as =
a practical consideration we have to think about what happens if that =
kind of exchange fails.
>=20
> As a matter of fact, I don't think that such a correlation token is =
absolutely necessary for a good user experience. But we do need this:
>=20
>> - Advertising a SIP account address over XMPP and an XMPP account
>> address over SIP
>=20
> I don't think there is a reason to change our charter at all because =
of this, but this is perhaps something that we could cover in the use =
cases and requirements document.
>=20
> Markus
>=20
>=20
>> -----Original Message-----
>> From: sixpac-bounces@ietf.org [mailto:sixpac-bounces@ietf.org] On =
Behalf
>> Of ext Peter Saint-Andre
>> Sent: 11 November, 2010 09:42
>> To: sixpac@ietf.org
>> Subject: [sixpac] charter proposal
>>=20
>> To kick off discussion, here is the charter as I sent it to the
>> dispath@ietf.org list a while back, with removal of a clause about
>> working on user configuration, which I think is a large rathole.
>>=20
>> Let's discuss and get busy!
>>=20
>> /psa
>>=20
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> =3D
>> SIXPAC (SIP Integration with XMPP in Presence Aware Clients)
>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> =3D
>>=20
>> Problem Statement
>>=20
>> Both the Session Initiation Protocol (SIP) and the Extensible =
Messaging
>> and Presence Protocol (XMPP) are widely deployed technologies for =
real-
>> time communication over the Internet.  In order to offer a complete
>> suite of features as well as communication across multiple networks,
>> several user-oriented software applications support both SIP and =
XMPP,
>> and more software developers have expressed interest in building such
>> "dual-stack" solutions.  Unfortunately, it is difficult to provide a
>> good end-user experience in such applications because SIP and XMPP =
are
>> not "aware" of each other.  For example:
>>=20
>> - XMPP presence does not include availability states related to a SIP
>> voice call or video call (e.g., "on the phone"), thus preventing an
>> a dual-stack endpoint from showing presence-based communication hints
>>=20
>> - There is no correlation between an XMPP IM session and a SIP voice
>> or video session, thus preventing a dual-stack endpoint from =
providing
>> integrated user interfaces and communications history
>>=20
>> - SIP accounts and XMPP accounts are not directly correlated in =
contact
>> lists or vCards (and not all deployed services support storage of =
such
>> information), thus preventing a dual-stack endpoint from knowing that
>> a contact has both SIP and XMPP capabilities
>>=20
>> Although some proprietary solutions exist to the foregoing problems, =
it
>> would be preferable to define standardized solutions for the sake of
>> improved interoperability.
>>=20
>> Objectives
>>=20
>> Because both SIP and XMPP are easily extended through new SIP headers
>> and XMPP elements, it should be possible to provide tighter =
integration
>> within dual-stack SIP/XMPP user agents to improve the user =
experience.
>>=20
>> Any such extensions should meet the following criteria:
>>=20
>> - Be completely optional and backwards-compatible for all endpoints
>>=20
>> - Work without changes to deployed infrastructure such as existing
>> SIP and XMPP servers, B2BUAs, firewalls, etc.
>>=20
>> The SIXPAC WG will define a small number of SIP and XMPP extensions =
to
>> solve the following use cases in dual-stack endpoints:
>>=20
>> - Including SIP-based availability states in XMPP presence (limited =
to
>> basic presence and availability states only, not the full range of
>> PIDF extensions)
>>=20
>> - Correlating an XMPP IM session with a SIP voice/video session, and
>> vice-versa
>>=20
>> - Advertising a SIP account address over XMPP and an XMPP account
>> address over SIP
>>=20
>> Additional use cases are out of scope, including anything related to =
or
>> requiring server integration, multiparty communication, SIP-based IM =
and
>> presence, XMPP-based voice and video, file transfer, generalized =
service
>> discovery and capabilities exchange, full protocol translation in
>> communication gateways, shared credentials across both SIP and XMPP
>> accounts, rich presence extensions for features such as geolocation,
>> etc. Although such topics are important and interesting, they are out =
of
>> scope for this group.
>>=20
>> However, in addition to the protocol extensions explicitly mentioned
>> above, the group may also define best practices related to the
>> implementation and deployment of dual-stack SIP/XMPP endpoints.
>>=20
>> Deliverables
>>=20
>> - Use cases and protocol requirements
>>=20
>> - XMPP presence extension for SIP-based availability states
>>=20
>> - Media session correlation extensions for SIP and XMPP
>>=20
>> - Contact address advertisement extensions for SIP and XMPP
>>=20
>> - Best practices for implementation and deployment of dual-stack
>> endpoints
>>=20
>> Milestones
>>=20
>> Feb 2011  Submit use cases and protocol requirements document to IESG
>> (Informational)
>>=20
>> Oct 2011  Submit XMPP presence extension document to IESG (Standards
>> Track)
>>=20
>> Oct 2011  Submit media session correlation extensions document to =
IESG
>> (Standards Track)
>>=20
>> Oct 2011  Submit contact address advertisement extension document to
>> IESG (Standards Track)
>>=20
>> Oct 2011  Submit best practices document to IESG (Informational)
>>=20
>=20
> _______________________________________________
> sixpac mailing list
> sixpac@ietf.org
> https://www.ietf.org/mailman/listinfo/sixpac


From peter.musgrave@magorcorp.com  Mon Dec  6 13:43:06 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: sixpac@core3.amsl.com
Delivered-To: sixpac@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E30A93A68BE for <sixpac@core3.amsl.com>; Mon,  6 Dec 2010 13:43:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.39
X-Spam-Level: 
X-Spam-Status: No, score=-103.39 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9KRBERB8H93 for <sixpac@core3.amsl.com>; Mon,  6 Dec 2010 13:43:05 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 64D203A6882 for <sixpac@ietf.org>; Mon,  6 Dec 2010 13:43:05 -0800 (PST)
Received: by yxt33 with SMTP id 33so2945949yxt.31 for <sixpac@ietf.org>; Mon, 06 Dec 2010 13:44:29 -0800 (PST)
Received: by 10.147.41.5 with SMTP id t5mr7634558yaj.38.1291671869295; Mon, 06 Dec 2010 13:44:29 -0800 (PST)
Received: from petermac.magor.local ([72.1.217.106]) by mx.google.com with ESMTPS id y11sm3376271yhc.8.2010.12.06.13.44.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 06 Dec 2010 13:44:28 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com>
Date: Mon, 6 Dec 2010 16:44:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5FEE60E-D70A-46C7-9B2E-E5493A9872F7@magorcorp.com>
References: <4CDB9E64.6070704@stpeter.im> <B3F72E5548B10A4A8E6F4795430F841840CEE9EC2F@NOK-EUMSG-02.mgdnok.nokia.com> <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1082)
Cc: sixpac@ietf.org
Subject: Re: [sixpac] charter proposal - correlation between SIP and XMPP
X-BeenThere: sixpac@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "The SIXPAC \(SIP Interworking with XMPP in Presence Aware Clients\) list is dedicated to discussion of dual-stack SIP/XMPP user agents." <sixpac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sixpac>
List-Post: <mailto:sixpac@ietf.org>
List-Help: <mailto:sixpac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2010 21:43:07 -0000

Hi Robert,=20

I agree that session correlation is a snake pit. (Since we can't even =
get to agreeing on it as it traverses a B2BUA I think correlation with =
XMPP is going to be ugly^2 or maybe even e^(ugly) ).=20

I continue to be interested in the work here primarily from an XMPP =
identity/SIP identity correlation perspective - I will find some time to =
read the appropriate background material...

Peter Musgrave

On 2010-12-06, at 4:29 PM, Robert Sparks wrote:

> Discussion on this and the other threads appears to be stalling. Can =
we draw some conclusions?
>=20
> For this thread, I think Markus was trying to soften (maybe remove?) =
this goal:
>>> - Correlating an XMPP IM session with a SIP voice/video session, and
>>> vice-versa
>>=20
>=20
> This is a place I think a group could get really stuck - as markus =
hints at below, how is this not going
> to run into the same set of issues (and run into the same set of =
problems trying to specify a solution for)
> that Hadriel's SIPSCOTCH proposal is having?
>=20
>=20
> RjS
>=20
>=20
> On Nov 11, 2010, at 11:06 AM, <Markus.Isomaki@nokia.com> =
<Markus.Isomaki@nokia.com> wrote:
>=20
>> Hi,
>>=20
>> The charter says:
>>=20
>>> - There is no correlation between an XMPP IM session and a SIP voice
>>> or video session, thus preventing a dual-stack endpoint from =
providing
>>> integrated user interfaces and communications history
>>=20
>> It has been pointed out that in SIP we may have practical challenges =
to achieve this with a high likelihood. This means that if our solution =
is based on some kind of token that is exchanged between the two SIXPAC =
clients over SIP (so that they can replay it later on over XMPP for =
correlation), and if we put that token in some kind of a new header, it =
is possible that B2BUA's on the path will "eat" such headers out. So as =
a practical consideration we have to think about what happens if that =
kind of exchange fails.
>>=20
>> As a matter of fact, I don't think that such a correlation token is =
absolutely necessary for a good user experience. But we do need this:
>>=20
>>> - Advertising a SIP account address over XMPP and an XMPP account
>>> address over SIP
>>=20
>> I don't think there is a reason to change our charter at all because =
of this, but this is perhaps something that we could cover in the use =
cases and requirements document.
>>=20
>> Markus
>>=20
>>=20
>>> -----Original Message-----
>>> From: sixpac-bounces@ietf.org [mailto:sixpac-bounces@ietf.org] On =
Behalf
>>> Of ext Peter Saint-Andre
>>> Sent: 11 November, 2010 09:42
>>> To: sixpac@ietf.org
>>> Subject: [sixpac] charter proposal
>>>=20
>>> To kick off discussion, here is the charter as I sent it to the
>>> dispath@ietf.org list a while back, with removal of a clause about
>>> working on user configuration, which I think is a large rathole.
>>>=20
>>> Let's discuss and get busy!
>>>=20
>>> /psa
>>>=20
>>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> =3D
>>> SIXPAC (SIP Integration with XMPP in Presence Aware Clients)
>>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> =3D
>>>=20
>>> Problem Statement
>>>=20
>>> Both the Session Initiation Protocol (SIP) and the Extensible =
Messaging
>>> and Presence Protocol (XMPP) are widely deployed technologies for =
real-
>>> time communication over the Internet.  In order to offer a complete
>>> suite of features as well as communication across multiple networks,
>>> several user-oriented software applications support both SIP and =
XMPP,
>>> and more software developers have expressed interest in building =
such
>>> "dual-stack" solutions.  Unfortunately, it is difficult to provide a
>>> good end-user experience in such applications because SIP and XMPP =
are
>>> not "aware" of each other.  For example:
>>>=20
>>> - XMPP presence does not include availability states related to a =
SIP
>>> voice call or video call (e.g., "on the phone"), thus preventing an
>>> a dual-stack endpoint from showing presence-based communication =
hints
>>>=20
>>> - There is no correlation between an XMPP IM session and a SIP voice
>>> or video session, thus preventing a dual-stack endpoint from =
providing
>>> integrated user interfaces and communications history
>>>=20
>>> - SIP accounts and XMPP accounts are not directly correlated in =
contact
>>> lists or vCards (and not all deployed services support storage of =
such
>>> information), thus preventing a dual-stack endpoint from knowing =
that
>>> a contact has both SIP and XMPP capabilities
>>>=20
>>> Although some proprietary solutions exist to the foregoing problems, =
it
>>> would be preferable to define standardized solutions for the sake of
>>> improved interoperability.
>>>=20
>>> Objectives
>>>=20
>>> Because both SIP and XMPP are easily extended through new SIP =
headers
>>> and XMPP elements, it should be possible to provide tighter =
integration
>>> within dual-stack SIP/XMPP user agents to improve the user =
experience.
>>>=20
>>> Any such extensions should meet the following criteria:
>>>=20
>>> - Be completely optional and backwards-compatible for all endpoints
>>>=20
>>> - Work without changes to deployed infrastructure such as existing
>>> SIP and XMPP servers, B2BUAs, firewalls, etc.
>>>=20
>>> The SIXPAC WG will define a small number of SIP and XMPP extensions =
to
>>> solve the following use cases in dual-stack endpoints:
>>>=20
>>> - Including SIP-based availability states in XMPP presence (limited =
to
>>> basic presence and availability states only, not the full range of
>>> PIDF extensions)
>>>=20
>>> - Correlating an XMPP IM session with a SIP voice/video session, and
>>> vice-versa
>>>=20
>>> - Advertising a SIP account address over XMPP and an XMPP account
>>> address over SIP
>>>=20
>>> Additional use cases are out of scope, including anything related to =
or
>>> requiring server integration, multiparty communication, SIP-based IM =
and
>>> presence, XMPP-based voice and video, file transfer, generalized =
service
>>> discovery and capabilities exchange, full protocol translation in
>>> communication gateways, shared credentials across both SIP and XMPP
>>> accounts, rich presence extensions for features such as geolocation,
>>> etc. Although such topics are important and interesting, they are =
out of
>>> scope for this group.
>>>=20
>>> However, in addition to the protocol extensions explicitly mentioned
>>> above, the group may also define best practices related to the
>>> implementation and deployment of dual-stack SIP/XMPP endpoints.
>>>=20
>>> Deliverables
>>>=20
>>> - Use cases and protocol requirements
>>>=20
>>> - XMPP presence extension for SIP-based availability states
>>>=20
>>> - Media session correlation extensions for SIP and XMPP
>>>=20
>>> - Contact address advertisement extensions for SIP and XMPP
>>>=20
>>> - Best practices for implementation and deployment of dual-stack
>>> endpoints
>>>=20
>>> Milestones
>>>=20
>>> Feb 2011  Submit use cases and protocol requirements document to =
IESG
>>> (Informational)
>>>=20
>>> Oct 2011  Submit XMPP presence extension document to IESG (Standards
>>> Track)
>>>=20
>>> Oct 2011  Submit media session correlation extensions document to =
IESG
>>> (Standards Track)
>>>=20
>>> Oct 2011  Submit contact address advertisement extension document to
>>> IESG (Standards Track)
>>>=20
>>> Oct 2011  Submit best practices document to IESG (Informational)
>>>=20
>>=20
>> _______________________________________________
>> sixpac mailing list
>> sixpac@ietf.org
>> https://www.ietf.org/mailman/listinfo/sixpac
>=20
> _______________________________________________
> sixpac mailing list
> sixpac@ietf.org
> https://www.ietf.org/mailman/listinfo/sixpac


From peter.musgrave@magorcorp.com  Mon Dec  6 15:39:14 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: sixpac@core3.amsl.com
Delivered-To: sixpac@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D24513A68B1 for <sixpac@core3.amsl.com>; Mon,  6 Dec 2010 15:39:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.284
X-Spam-Level: 
X-Spam-Status: No, score=-103.284 tagged_above=-999 required=5 tests=[AWL=0.315, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iiCnBTma8pG4 for <sixpac@core3.amsl.com>; Mon,  6 Dec 2010 15:39:12 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 1EDE93A68D5 for <sixpac@ietf.org>; Mon,  6 Dec 2010 15:39:11 -0800 (PST)
Received: by gyb13 with SMTP id 13so7067965gyb.31 for <sixpac@ietf.org>; Mon, 06 Dec 2010 15:40:35 -0800 (PST)
Received: by 10.147.168.5 with SMTP id v5mr7841516yao.21.1291678833940; Mon, 06 Dec 2010 15:40:33 -0800 (PST)
Received: from [192.168.1.105] ([204.237.32.134]) by mx.google.com with ESMTPS id y73sm3435759yhc.36.2010.12.06.15.40.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 06 Dec 2010 15:40:32 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Peter Musgrave <peter.musgrave@magorcorp.com>
In-Reply-To: <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com>
Date: Mon, 6 Dec 2010 18:40:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E942205-7EDC-47CF-81C5-D8AFD163C0E8@magorcorp.com>
References: <4CDB9E64.6070704@stpeter.im> <B3F72E5548B10A4A8E6F4795430F841840CEE9EC2F@NOK-EUMSG-02.mgdnok.nokia.com> <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.1082)
Cc: sixpac@ietf.org
Subject: Re: [sixpac] charter proposal - correlation between SIP and XMPP
X-BeenThere: sixpac@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "The SIXPAC \(SIP Interworking with XMPP in Presence Aware Clients\) list is dedicated to discussion of dual-stack SIP/XMPP user agents." <sixpac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sixpac>
List-Post: <mailto:sixpac@ietf.org>
List-Help: <mailto:sixpac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Dec 2010 23:39:15 -0000

Hi all,

I have returned to =
http://tools.ietf.org/html/draft-veikkolainen-sip-xmpp-coex-reqs-01 (now =
expired).=20

The use cases make sense to me. I think to make them crisper it would be =
useful to extend it to consider the cases where I have two SIP devices =
registered to the same AOR and two XMPP clients (one each on the same =
two devices) logged in. I think this encompasses the potential corner =
cases.=20

If the charter decides to forgo session correlation then REQ-2 will need =
to reflect this (It speaks to XMPP carrying SIP session information).=20

Other than that I think the identity correlation requirements it =
describes are useful.=20

Regards,=20

Peter Musgrave


On 2010-12-06, at 4:29 PM, Robert Sparks wrote:

> Discussion on this and the other threads appears to be stalling. Can =
we draw some conclusions?
>=20
> For this thread, I think Markus was trying to soften (maybe remove?) =
this goal:
>>> - Correlating an XMPP IM session with a SIP voice/video session, and
>>> vice-versa
>>=20
>=20
> This is a place I think a group could get really stuck - as markus =
hints at below, how is this not going
> to run into the same set of issues (and run into the same set of =
problems trying to specify a solution for)
> that Hadriel's SIPSCOTCH proposal is having?
>=20
>=20
> RjS
>=20
>=20
> On Nov 11, 2010, at 11:06 AM, <Markus.Isomaki@nokia.com> =
<Markus.Isomaki@nokia.com> wrote:
>=20
>> Hi,
>>=20
>> The charter says:
>>=20
>>> - There is no correlation between an XMPP IM session and a SIP voice
>>> or video session, thus preventing a dual-stack endpoint from =
providing
>>> integrated user interfaces and communications history
>>=20
>> It has been pointed out that in SIP we may have practical challenges =
to achieve this with a high likelihood. This means that if our solution =
is based on some kind of token that is exchanged between the two SIXPAC =
clients over SIP (so that they can replay it later on over XMPP for =
correlation), and if we put that token in some kind of a new header, it =
is possible that B2BUA's on the path will "eat" such headers out. So as =
a practical consideration we have to think about what happens if that =
kind of exchange fails.
>>=20
>> As a matter of fact, I don't think that such a correlation token is =
absolutely necessary for a good user experience. But we do need this:
>>=20
>>> - Advertising a SIP account address over XMPP and an XMPP account
>>> address over SIP
>>=20
>> I don't think there is a reason to change our charter at all because =
of this, but this is perhaps something that we could cover in the use =
cases and requirements document.
>>=20
>> Markus
>>=20
>>=20
>>> -----Original Message-----
>>> From: sixpac-bounces@ietf.org [mailto:sixpac-bounces@ietf.org] On =
Behalf
>>> Of ext Peter Saint-Andre
>>> Sent: 11 November, 2010 09:42
>>> To: sixpac@ietf.org
>>> Subject: [sixpac] charter proposal
>>>=20
>>> To kick off discussion, here is the charter as I sent it to the
>>> dispath@ietf.org list a while back, with removal of a clause about
>>> working on user configuration, which I think is a large rathole.
>>>=20
>>> Let's discuss and get busy!
>>>=20
>>> /psa
>>>=20
>>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> =3D
>>> SIXPAC (SIP Integration with XMPP in Presence Aware Clients)
>>> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> =3D
>>>=20
>>> Problem Statement
>>>=20
>>> Both the Session Initiation Protocol (SIP) and the Extensible =
Messaging
>>> and Presence Protocol (XMPP) are widely deployed technologies for =
real-
>>> time communication over the Internet.  In order to offer a complete
>>> suite of features as well as communication across multiple networks,
>>> several user-oriented software applications support both SIP and =
XMPP,
>>> and more software developers have expressed interest in building =
such
>>> "dual-stack" solutions.  Unfortunately, it is difficult to provide a
>>> good end-user experience in such applications because SIP and XMPP =
are
>>> not "aware" of each other.  For example:
>>>=20
>>> - XMPP presence does not include availability states related to a =
SIP
>>> voice call or video call (e.g., "on the phone"), thus preventing an
>>> a dual-stack endpoint from showing presence-based communication =
hints
>>>=20
>>> - There is no correlation between an XMPP IM session and a SIP voice
>>> or video session, thus preventing a dual-stack endpoint from =
providing
>>> integrated user interfaces and communications history
>>>=20
>>> - SIP accounts and XMPP accounts are not directly correlated in =
contact
>>> lists or vCards (and not all deployed services support storage of =
such
>>> information), thus preventing a dual-stack endpoint from knowing =
that
>>> a contact has both SIP and XMPP capabilities
>>>=20
>>> Although some proprietary solutions exist to the foregoing problems, =
it
>>> would be preferable to define standardized solutions for the sake of
>>> improved interoperability.
>>>=20
>>> Objectives
>>>=20
>>> Because both SIP and XMPP are easily extended through new SIP =
headers
>>> and XMPP elements, it should be possible to provide tighter =
integration
>>> within dual-stack SIP/XMPP user agents to improve the user =
experience.
>>>=20
>>> Any such extensions should meet the following criteria:
>>>=20
>>> - Be completely optional and backwards-compatible for all endpoints
>>>=20
>>> - Work without changes to deployed infrastructure such as existing
>>> SIP and XMPP servers, B2BUAs, firewalls, etc.
>>>=20
>>> The SIXPAC WG will define a small number of SIP and XMPP extensions =
to
>>> solve the following use cases in dual-stack endpoints:
>>>=20
>>> - Including SIP-based availability states in XMPP presence (limited =
to
>>> basic presence and availability states only, not the full range of
>>> PIDF extensions)
>>>=20
>>> - Correlating an XMPP IM session with a SIP voice/video session, and
>>> vice-versa
>>>=20
>>> - Advertising a SIP account address over XMPP and an XMPP account
>>> address over SIP
>>>=20
>>> Additional use cases are out of scope, including anything related to =
or
>>> requiring server integration, multiparty communication, SIP-based IM =
and
>>> presence, XMPP-based voice and video, file transfer, generalized =
service
>>> discovery and capabilities exchange, full protocol translation in
>>> communication gateways, shared credentials across both SIP and XMPP
>>> accounts, rich presence extensions for features such as geolocation,
>>> etc. Although such topics are important and interesting, they are =
out of
>>> scope for this group.
>>>=20
>>> However, in addition to the protocol extensions explicitly mentioned
>>> above, the group may also define best practices related to the
>>> implementation and deployment of dual-stack SIP/XMPP endpoints.
>>>=20
>>> Deliverables
>>>=20
>>> - Use cases and protocol requirements
>>>=20
>>> - XMPP presence extension for SIP-based availability states
>>>=20
>>> - Media session correlation extensions for SIP and XMPP
>>>=20
>>> - Contact address advertisement extensions for SIP and XMPP
>>>=20
>>> - Best practices for implementation and deployment of dual-stack
>>> endpoints
>>>=20
>>> Milestones
>>>=20
>>> Feb 2011  Submit use cases and protocol requirements document to =
IESG
>>> (Informational)
>>>=20
>>> Oct 2011  Submit XMPP presence extension document to IESG (Standards
>>> Track)
>>>=20
>>> Oct 2011  Submit media session correlation extensions document to =
IESG
>>> (Standards Track)
>>>=20
>>> Oct 2011  Submit contact address advertisement extension document to
>>> IESG (Standards Track)
>>>=20
>>> Oct 2011  Submit best practices document to IESG (Informational)
>>>=20
>>=20
>> _______________________________________________
>> sixpac mailing list
>> sixpac@ietf.org
>> https://www.ietf.org/mailman/listinfo/sixpac
>=20
> _______________________________________________
> sixpac mailing list
> sixpac@ietf.org
> https://www.ietf.org/mailman/listinfo/sixpac


From Simo.Veikkolainen@nokia.com  Mon Dec 13 00:05:17 2010
Return-Path: <Simo.Veikkolainen@nokia.com>
X-Original-To: sixpac@core3.amsl.com
Delivered-To: sixpac@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F41143A6CDE for <sixpac@core3.amsl.com>; Mon, 13 Dec 2010 00:05:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.266
X-Spam-Level: 
X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=-1.667, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPRXJfPOhXfY for <sixpac@core3.amsl.com>; Mon, 13 Dec 2010 00:05:15 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by core3.amsl.com (Postfix) with ESMTP id 2EBC83A6900 for <sixpac@ietf.org>; Mon, 13 Dec 2010 00:05:15 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id oBD86oV2030296; Mon, 13 Dec 2010 10:06:51 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 10:06:39 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 13 Dec 2010 10:06:39 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.106]) by nok-am1mhub-03.mgdnok.nokia.com ([65.54.30.7]) with mapi; Mon, 13 Dec 2010 09:06:39 +0100
From: <Simo.Veikkolainen@nokia.com>
To: <peter.musgrave@magorcorp.com>, <rjsparks@nostrum.com>
Date: Mon, 13 Dec 2010 09:06:37 +0100
Thread-Topic: [sixpac] charter proposal - correlation between SIP and XMPP
Thread-Index: AcuVnwEOWIVNIQLpTbyFVTcvMfIc2QE+2rug
Message-ID: <B23B311878A0B4438F5F09F47E01AAE051397A5353@NOK-EUMSG-01.mgdnok.nokia.com>
References: <4CDB9E64.6070704@stpeter.im> <B3F72E5548B10A4A8E6F4795430F841840CEE9EC2F@NOK-EUMSG-02.mgdnok.nokia.com> <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com> <6E942205-7EDC-47CF-81C5-D8AFD163C0E8@magorcorp.com>
In-Reply-To: <6E942205-7EDC-47CF-81C5-D8AFD163C0E8@magorcorp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Dec 2010 08:06:39.0342 (UTC) FILETIME=[AB8580E0:01CB9A9C]
X-Nokia-AV: Clean
Cc: sixpac@ietf.org
Subject: Re: [sixpac] charter proposal - correlation between SIP and XMPP
X-BeenThere: sixpac@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "The SIXPAC \(SIP Interworking with XMPP in Presence Aware Clients\) list is dedicated to discussion of dual-stack SIP/XMPP user agents." <sixpac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sixpac>
List-Post: <mailto:sixpac@ietf.org>
List-Help: <mailto:sixpac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 08:05:17 -0000

-----Original Message-----
From: sixpac-bounces@ietf.org [mailto:sixpac-bounces@ietf.org] On Behalf Of=
 ext Peter Musgrave
Sent: 07 December, 2010 01:40
To: Robert Sparks
Cc: sixpac@ietf.org
Subject: Re: [sixpac] charter proposal - correlation between SIP and XMPP

Hi all,

I have returned to http://tools.ietf.org/html/draft-veikkolainen-sip-xmpp-c=
oex-reqs-01 (now expired).=20

[Simo] The -01 version expires Feb 23rd, 2011; maybe you took a look at the=
 previous version? (But even that's ok since there are few changes only in =
-01.)

The use cases make sense to me. I think to make them crisper it would be us=
eful to extend it to consider the cases where I have two SIP devices regist=
ered to the same AOR and two XMPP clients (one each on the same two devices=
) logged in. I think this encompasses the potential corner cases.=20

[Simo] You mean a case when I have two dual-stack endpoints registered at t=
he same time? I agree this might be something we want to say something on, =
since developers will be facing the issue anyway. The simplest way would pr=
obably be that everything works as they do currently: If the other party wa=
nts to extend the IM conversation we have with a SIP call, and he send a SI=
P INVITE to my AOR, all my registered UA instances ring. On the other hand,=
 he might choose to send the SIP INVITE to my GRUU only, and in this case o=
nly a specific UA instance gets the call. And the same way around with SIP =
call extended with XMPP IM. Would that be enough, or do we want to build so=
mething more elaborate?

-Simo

If the charter decides to forgo session correlation then REQ-2 will need to=
 reflect this (It speaks to XMPP carrying SIP session information).=20

Other than that I think the identity correlation requirements it describes =
are useful.=20

Regards,=20

Peter Musgrave


On 2010-12-06, at 4:29 PM, Robert Sparks wrote:

> Discussion on this and the other threads appears to be stalling. Can we d=
raw some conclusions?
>=20
> For this thread, I think Markus was trying to soften (maybe remove?) this=
 goal:
>>> - Correlating an XMPP IM session with a SIP voice/video session, and
>>> vice-versa
>>=20
>=20
> This is a place I think a group could get really stuck - as markus hints =
at below, how is this not going
> to run into the same set of issues (and run into the same set of problems=
 trying to specify a solution for)
> that Hadriel's SIPSCOTCH proposal is having?
>=20
>=20
> RjS
>=20
>=20
> On Nov 11, 2010, at 11:06 AM, <Markus.Isomaki@nokia.com> <Markus.Isomaki@=
nokia.com> wrote:
>=20
>> Hi,
>>=20
>> The charter says:
>>=20
>>> - There is no correlation between an XMPP IM session and a SIP voice
>>> or video session, thus preventing a dual-stack endpoint from providing
>>> integrated user interfaces and communications history
>>=20
>> It has been pointed out that in SIP we may have practical challenges to =
achieve this with a high likelihood. This means that if our solution is bas=
ed on some kind of token that is exchanged between the two SIXPAC clients o=
ver SIP (so that they can replay it later on over XMPP for correlation), an=
d if we put that token in some kind of a new header, it is possible that B2=
BUA's on the path will "eat" such headers out. So as a practical considerat=
ion we have to think about what happens if that kind of exchange fails.
>>=20
>> As a matter of fact, I don't think that such a correlation token is abso=
lutely necessary for a good user experience. But we do need this:
>>=20
>>> - Advertising a SIP account address over XMPP and an XMPP account
>>> address over SIP
>>=20
>> I don't think there is a reason to change our charter at all because of =
this, but this is perhaps something that we could cover in the use cases an=
d requirements document.
>>=20
>> Markus
>>=20
>>=20
>>> -----Original Message-----
>>> From: sixpac-bounces@ietf.org [mailto:sixpac-bounces@ietf.org] On Behal=
f
>>> Of ext Peter Saint-Andre
>>> Sent: 11 November, 2010 09:42
>>> To: sixpac@ietf.org
>>> Subject: [sixpac] charter proposal
>>>=20
>>> To kick off discussion, here is the charter as I sent it to the
>>> dispath@ietf.org list a while back, with removal of a clause about
>>> working on user configuration, which I think is a large rathole.
>>>=20
>>> Let's discuss and get busy!
>>>=20
>>> /psa
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> =3D
>>> SIXPAC (SIP Integration with XMPP in Presence Aware Clients)
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> =3D
>>>=20
>>> Problem Statement
>>>=20
>>> Both the Session Initiation Protocol (SIP) and the Extensible Messaging
>>> and Presence Protocol (XMPP) are widely deployed technologies for real-
>>> time communication over the Internet.  In order to offer a complete
>>> suite of features as well as communication across multiple networks,
>>> several user-oriented software applications support both SIP and XMPP,
>>> and more software developers have expressed interest in building such
>>> "dual-stack" solutions.  Unfortunately, it is difficult to provide a
>>> good end-user experience in such applications because SIP and XMPP are
>>> not "aware" of each other.  For example:
>>>=20
>>> - XMPP presence does not include availability states related to a SIP
>>> voice call or video call (e.g., "on the phone"), thus preventing an
>>> a dual-stack endpoint from showing presence-based communication hints
>>>=20
>>> - There is no correlation between an XMPP IM session and a SIP voice
>>> or video session, thus preventing a dual-stack endpoint from providing
>>> integrated user interfaces and communications history
>>>=20
>>> - SIP accounts and XMPP accounts are not directly correlated in contact
>>> lists or vCards (and not all deployed services support storage of such
>>> information), thus preventing a dual-stack endpoint from knowing that
>>> a contact has both SIP and XMPP capabilities
>>>=20
>>> Although some proprietary solutions exist to the foregoing problems, it
>>> would be preferable to define standardized solutions for the sake of
>>> improved interoperability.
>>>=20
>>> Objectives
>>>=20
>>> Because both SIP and XMPP are easily extended through new SIP headers
>>> and XMPP elements, it should be possible to provide tighter integration
>>> within dual-stack SIP/XMPP user agents to improve the user experience.
>>>=20
>>> Any such extensions should meet the following criteria:
>>>=20
>>> - Be completely optional and backwards-compatible for all endpoints
>>>=20
>>> - Work without changes to deployed infrastructure such as existing
>>> SIP and XMPP servers, B2BUAs, firewalls, etc.
>>>=20
>>> The SIXPAC WG will define a small number of SIP and XMPP extensions to
>>> solve the following use cases in dual-stack endpoints:
>>>=20
>>> - Including SIP-based availability states in XMPP presence (limited to
>>> basic presence and availability states only, not the full range of
>>> PIDF extensions)
>>>=20
>>> - Correlating an XMPP IM session with a SIP voice/video session, and
>>> vice-versa
>>>=20
>>> - Advertising a SIP account address over XMPP and an XMPP account
>>> address over SIP
>>>=20
>>> Additional use cases are out of scope, including anything related to or
>>> requiring server integration, multiparty communication, SIP-based IM an=
d
>>> presence, XMPP-based voice and video, file transfer, generalized servic=
e
>>> discovery and capabilities exchange, full protocol translation in
>>> communication gateways, shared credentials across both SIP and XMPP
>>> accounts, rich presence extensions for features such as geolocation,
>>> etc. Although such topics are important and interesting, they are out o=
f
>>> scope for this group.
>>>=20
>>> However, in addition to the protocol extensions explicitly mentioned
>>> above, the group may also define best practices related to the
>>> implementation and deployment of dual-stack SIP/XMPP endpoints.
>>>=20
>>> Deliverables
>>>=20
>>> - Use cases and protocol requirements
>>>=20
>>> - XMPP presence extension for SIP-based availability states
>>>=20
>>> - Media session correlation extensions for SIP and XMPP
>>>=20
>>> - Contact address advertisement extensions for SIP and XMPP
>>>=20
>>> - Best practices for implementation and deployment of dual-stack
>>> endpoints
>>>=20
>>> Milestones
>>>=20
>>> Feb 2011  Submit use cases and protocol requirements document to IESG
>>> (Informational)
>>>=20
>>> Oct 2011  Submit XMPP presence extension document to IESG (Standards
>>> Track)
>>>=20
>>> Oct 2011  Submit media session correlation extensions document to IESG
>>> (Standards Track)
>>>=20
>>> Oct 2011  Submit contact address advertisement extension document to
>>> IESG (Standards Track)
>>>=20
>>> Oct 2011  Submit best practices document to IESG (Informational)
>>>=20
>>=20
>> _______________________________________________
>> sixpac mailing list
>> sixpac@ietf.org
>> https://www.ietf.org/mailman/listinfo/sixpac
>=20
> _______________________________________________
> sixpac mailing list
> sixpac@ietf.org
> https://www.ietf.org/mailman/listinfo/sixpac

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

From peter.musgrave@magorcorp.com  Mon Dec 13 06:22:21 2010
Return-Path: <peter.musgrave@magorcorp.com>
X-Original-To: sixpac@core3.amsl.com
Delivered-To: sixpac@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C17A03A6E96 for <sixpac@core3.amsl.com>; Mon, 13 Dec 2010 06:22:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.643
X-Spam-Level: 
X-Spam-Status: No, score=-102.643 tagged_above=-999 required=5 tests=[AWL=0.334, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELKBylmXNPX4 for <sixpac@core3.amsl.com>; Mon, 13 Dec 2010 06:22:21 -0800 (PST)
Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by core3.amsl.com (Postfix) with ESMTP id E0CDD3A6D99 for <sixpac@ietf.org>; Mon, 13 Dec 2010 06:22:20 -0800 (PST)
Received: by gxk8 with SMTP id 8so3073086gxk.27 for <sixpac@ietf.org>; Mon, 13 Dec 2010 06:23:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.90.136.14 with SMTP id j14mr5135116agd.17.1292250238391; Mon, 13 Dec 2010 06:23:58 -0800 (PST)
Received: by 10.91.1.2 with HTTP; Mon, 13 Dec 2010 06:23:58 -0800 (PST)
In-Reply-To: <B23B311878A0B4438F5F09F47E01AAE051397A5353@NOK-EUMSG-01.mgdnok.nokia.com>
References: <4CDB9E64.6070704@stpeter.im> <B3F72E5548B10A4A8E6F4795430F841840CEE9EC2F@NOK-EUMSG-02.mgdnok.nokia.com> <B2BBC4E3-F851-4190-AD33-6366E27ECE50@nostrum.com> <6E942205-7EDC-47CF-81C5-D8AFD163C0E8@magorcorp.com> <B23B311878A0B4438F5F09F47E01AAE051397A5353@NOK-EUMSG-01.mgdnok.nokia.com>
Date: Mon, 13 Dec 2010 09:23:58 -0500
Message-ID: <AANLkTinp87XjhyAPrYgBiwJeKY3Vb=cB=hSJLwQuSMEf@mail.gmail.com>
From: Peter Musgrave <peter.musgrave@magorcorp.com>
To: Simo.Veikkolainen@nokia.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: sixpac@ietf.org
Subject: Re: [sixpac] charter proposal - correlation between SIP and XMPP
X-BeenThere: sixpac@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "The SIXPAC \(SIP Interworking with XMPP in Presence Aware Clients\) list is dedicated to discussion of dual-stack SIP/XMPP user agents." <sixpac.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sixpac>
List-Post: <mailto:sixpac@ietf.org>
List-Help: <mailto:sixpac-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sixpac>, <mailto:sixpac-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 14:22:21 -0000

> The use cases make sense to me. I think to make them crisper it would be =
useful to extend it to consider the cases where I have two SIP devices regi=
stered to the same AOR and two XMPP clients (one each on the same two devic=
es) logged in. I think this encompasses the potential corner cases.
>
> [Simo] You mean a case when I have two dual-stack endpoints registered at=
 the same time? I agree this might be something we want to say something on=
, since developers will be facing the issue anyway. The simplest way would =
probably be that everything works as they do currently: If the other party =
wants to extend the IM conversation we have with a SIP call, and he send a =
SIP INVITE to my AOR, all my registered UA instances ring. On the other han=
d, he might choose to send the SIP INVITE to my GRUU only, and in this case=
 only a specific UA instance gets the call. And the same way around with SI=
P call extended with XMPP IM. Would that be enough, or do we want to build =
something more elaborate?

Hi,

Yes, the case you describe is one. The other would be one dual-stack
device and two other devices, one with a SIP reg and the other with an
XMPP reg.

I agree that the response could be to e.g ring the SIP device by AOR
or GRUU (and the converse would be send an IM to both clients).

I don't see a need for anything more than that - but I think thinking
about how what is prescribed works in this environment will be
helpful.

Peter Musgrave
