Re: [sixpac] FW: New Version Notification for draft-veikkolainen-sip-xmpp-coex-reqs-02

<Markus.Isomaki@nokia.com> Tue, 01 February 2011 11:44 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 BB7C03A6CBF for <sixpac@core3.amsl.com>; Tue, 1 Feb 2011 03:44:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.518
X-Spam-Level:
X-Spam-Status: No, score=-3.518 tagged_above=-999 required=5 tests=[AWL=-1.146, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227]
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 oRRzdt8hWDn7 for <sixpac@core3.amsl.com>; Tue, 1 Feb 2011 03:44:47 -0800 (PST)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by core3.amsl.com (Postfix) with ESMTP id A42FC3A6914 for <sixpac@ietf.org>; Tue, 1 Feb 2011 03:44:47 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p11Blras000690 for <sixpac@ietf.org>; Tue, 1 Feb 2011 13:48:03 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 1 Feb 2011 13:47:54 +0200
Received: from 008-AM1MMR1-005.mgdnok.nokia.com (65.54.30.60) by NOK-am1MHUB-01.mgdnok.nokia.com (65.54.30.5) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 1 Feb 2011 12:47:54 +0100
Received: from 008-AM1MPN1-004.mgdnok.nokia.com ([169.254.5.218]) by 008-AM1MMR1-005.mgdnok.nokia.com ([65.54.30.60]) with mapi; Tue, 1 Feb 2011 12:47:53 +0100
From: <Markus.Isomaki@nokia.com>
To: <Simo.Veikkolainen@nokia.com>, <sixpac@ietf.org>
Thread-Topic: [sixpac] FW: New Version Notification for draft-veikkolainen-sip-xmpp-coex-reqs-02
Thread-Index: AQHLvZTBMsVG7EQwQ06Q+aXi3KtO9ZPjrp/wgAjfw/A=
Date: Tue, 1 Feb 2011 11:47:52 +0000
Message-ID: <DD8B10B86502AB488CB2D3DB4C546E38E67FA5@008-AM1MPN1-004.mgdnok.nokia.com>
References: <F9E2FDAF48D4544F874A56A3A8BD68B13BC79A@008-AM1MPN1-003.mgdnok.nokia.com>
In-Reply-To: <F9E2FDAF48D4544F874A56A3A8BD68B13BC79A@008-AM1MPN1-003.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Feb 2011 11:47:54.0696 (UTC) FILETIME=[DCE74480:01CBC205]
X-Nokia-AV: Clean
Subject: Re: [sixpac] FW: New Version Notification for draft-veikkolainen-sip-xmpp-coex-reqs-02
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 11:44:48 -0000

Hi all,

Simo Veikkolainen wrote:
>
>I have just uploaded a new version of draft-veikkolainen-sip-xmpp-coex-
>reqs, which can be found at http://www.ietf.org/internet-drafts/draft-
>veikkolainen-sip-xmpp-coex-reqs-02.txt
>
>The changes in this version address the comments made by Peter Musgrave
>(mainly clarifications):
>

It would be good if we got a few more reviews on this requirements and use cases draft to see that we agree on them. So far we have reviews done by Peter Musgrave and John Elwell (in addition to the authors), but in the IETF 79 ad hoc meeting, and on the DISPATCH list, there were quite a few other interested people as well.

So, please review the draft and send your comments. Based on those we can do a couple of revisions, and if after that there is a consensus on the requirements and use cases, we can move to the next phase and start the real work on protocol (extension) proposals.

Markus