[sixpac] Chartering...

<Markus.Isomaki@nokia.com> Tue, 01 February 2011 12:39 UTC

Return-Path: <Markus.Isomaki@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 B49573A6938 for <sixpac@core3.amsl.com>; Tue, 1 Feb 2011 04:39:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.523
X-Spam-Level:
X-Spam-Status: No, score=-3.523 tagged_above=-999 required=5 tests=[AWL=-0.924, BAYES_00=-2.599]
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 C7Ic6exqXvVT for <sixpac@core3.amsl.com>; Tue, 1 Feb 2011 04:39:12 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by core3.amsl.com (Postfix) with ESMTP id 30A413A6900 for <sixpac@ietf.org>; Tue, 1 Feb 2011 04:39:11 -0800 (PST)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-sa01.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p11CgPZr027170 for <sixpac@ietf.org>; Tue, 1 Feb 2011 14:42:25 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 1 Feb 2011 14:42:20 +0200
Received: from 008-AM1MMR1-004.mgdnok.nokia.com (65.54.30.59) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 1 Feb 2011 13:42:19 +0100
Received: from 008-AM1MPN1-004.mgdnok.nokia.com ([169.254.5.218]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi; Tue, 1 Feb 2011 13:42:18 +0100
From: <Markus.Isomaki@nokia.com>
To: <sixpac@ietf.org>
Thread-Topic: Chartering...
Thread-Index: AQHLwg12Ea6H6YfOHk+8HzA5r5+Idw==
Date: Tue, 1 Feb 2011 12:42:13 +0000
Message-ID: <DD8B10B86502AB488CB2D3DB4C546E38E67FFE@008-AM1MPN1-004.mgdnok.nokia.com>
References: <4CDB9E64.6070704@stpeter.im>
In-Reply-To: <4CDB9E64.6070704@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-puzzleid: {50790E06-92B4-4714-AC04-A77364C2DBF1}
x-cr-hashedpuzzle: AkJ9 A4yW A+vK BzcC Cb7/ DKmL DqoY D/v3 E0bO FpMO HVGU Hh9U H4rL IsgK Jc8f JiHv; 1; cwBpAHgAcABhAGMAQABpAGUAdABmAC4AbwByAGcA; Sosha1_v1; 7; {50790E06-92B4-4714-AC04-A77364C2DBF1}; bQBhAHIAawB1AHMALgBpAHMAbwBtAGEAawBpAEAAbgBvAGsAaQBhAC4AYwBvAG0A; Tue, 01 Feb 2011 12:42:13 GMT; QwBoAGEAcgB0AGUAcgBpAG4AZwAuAC4ALgA=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Feb 2011 12:42:20.0310 (UTC) FILETIME=[775C6B60:01CBC20D]
X-Nokia-AV: Clean
Subject: [sixpac] Chartering...
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: Tue, 01 Feb 2011 12:39:13 -0000

Hi all,

What comes to the SIXPAC charter proposal, the latest version (from November) is included below.

I think there was a pretty good agreement on this version, but I think there are three specific issues about it:

1. Is there enough energy to get the work done?

I don't know how many people are on this list (Peter, any estimate?), but there were enough people who *said* they want to get this done. I guess now the best way to show commitment and make progress is to review the Requirements and Use Cases draft (see my earlier mail) and send comments on it.

2. The client configuration part was dropped. Is that OK?

There was not really a common understanding on what the group would do, so the text was prone to misunderstandings. I don't think anyone's intention was to design something completely new just for SIXPAC clients. SIP has certain auto-config methods (such as the recent SIP Forum / IETF standard), and so does XMPP. If we see it useful to recommend something about their use by SIXPAC clients, I think we can do so along these lines (as included in the charter proposal now):

>the group may also define best practices related to the
>implementation and deployment of dual-stack SIP/XMPP endpoints.

3. Correlation and SIP deployment reality (B2BUAs, SBCs, ...)

Some people think that the "correlation between an XMPP IM session and a SIP voice or video session" is only going to work in "standards compliant" SIP networks, which may not exist due to the excessive deployment of SBCs and other types of B2BUA, who strip out or override end-to-end data between SIP UAs. This is certainly a risk, but fortunately I think in most cases the correlation is just an optimization/nice-to-have feature, and even if it fails on some or even most sessions, we will not ruin the user experience (it will be anyway better with SIXPAC than completely isolated SIP and XMPP clients). In the end I think we should here only worry about user experience, not get into the philosophical discussion about SBCs. We should also make sure our correlation method is straight-to-the-purpose (SIXPAC) and not some kind of generic framework a la session id or splices or something like that, that will open doors to all kinds of conspiracy theories what it can also be used for.

So, from my perspective the charter text is good (enough) as it is now, and we only need to worry about point 1 (track record so far has not been that impressive due to various reasons).

Any comments? Have I missed other issues/ratholes about the charter?

Markus 


>
>========================================================================
>=
>SIXPAC (SIP Integration with XMPP in Presence Aware Clients)
>========================================================================
>=
>
>Problem Statement
>
>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:
>
>- 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
>
>- 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
>
>- 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
>
>Although some proprietary solutions exist to the foregoing problems, it
>would be preferable to define standardized solutions for the sake of
>improved interoperability.
>
>Objectives
>
>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.
>
>Any such extensions should meet the following criteria:
>
>- Be completely optional and backwards-compatible for all endpoints
>
>- Work without changes to deployed infrastructure such as existing
>  SIP and XMPP servers, B2BUAs, firewalls, etc.
>
>The SIXPAC WG will define a small number of SIP and XMPP extensions to
>solve the following use cases in dual-stack endpoints:
>
>- Including SIP-based availability states in XMPP presence (limited to
>  basic presence and availability states only, not the full range of
>  PIDF extensions)
>
>- Correlating an XMPP IM session with a SIP voice/video session, and
>  vice-versa
>
>- Advertising a SIP account address over XMPP and an XMPP account
>  address over SIP
>
>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.
>
>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.
>
>Deliverables
>
>- Use cases and protocol requirements
>
>- XMPP presence extension for SIP-based availability states
>
>- Media session correlation extensions for SIP and XMPP
>
>- Contact address advertisement extensions for SIP and XMPP
>
>- Best practices for implementation and deployment of dual-stack
>  endpoints
>
>Milestones
>
>Feb 2011  Submit use cases and protocol requirements document to IESG
>(Informational)
>
>Oct 2011  Submit XMPP presence extension document to IESG (Standards
>Track)
>
>Oct 2011  Submit media session correlation extensions document to IESG
>(Standards Track)
>
>Oct 2011  Submit contact address advertisement extension document to
>IESG (Standards Track)
>
>Oct 2011  Submit best practices document to IESG (Informational)
>