Re: [sixpac] Drafts on SIP-XMPP combined use

<Simo.Veikkolainen@nokia.com> Fri, 19 November 2010 08:26 UTC

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 0EC0C28B23E for <sixpac@core3.amsl.com>; Fri, 19 Nov 2010 00:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.799
X-Spam-Level:
X-Spam-Status: No, score=-6.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 fB16-2US3sDt for <sixpac@core3.amsl.com>; Fri, 19 Nov 2010 00:26:12 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 14D6D28C0CF for <sixpac@ietf.org>; Fri, 19 Nov 2010 00:26:11 -0800 (PST)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id oAJ8QM7k008210; Fri, 19 Nov 2010 02:26:59 -0600
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 19 Nov 2010 10:26:46 +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); Fri, 19 Nov 2010 10:26:45 +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; Fri, 19 Nov 2010 09:26:45 +0100
From: <Simo.Veikkolainen@nokia.com>
To: <peter.musgrave@magorcorp.com>
Date: Fri, 19 Nov 2010 09:26:43 +0100
Thread-Topic: [sixpac] Drafts on SIP-XMPP combined use
Thread-Index: AcuG3aOzIyTdD8OLRR2FQvMYctmufgA5PW7g
Message-ID: <B23B311878A0B4438F5F09F47E01AAE051393A6AF7@NOK-EUMSG-01.mgdnok.nokia.com>
References: <B23B311878A0B4438F5F09F47E01AAE05103C096C7@NOK-EUMSG-01.mgdnok.nokia.com> <3B319CDD-C6D5-4CCC-B177-1D63C9996D96@magorcorp.com>
In-Reply-To: <3B319CDD-C6D5-4CCC-B177-1D63C9996D96@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: 19 Nov 2010 08:26:45.0908 (UTC) FILETIME=[80C6DD40:01CB87C3]
X-Nokia-AV: Clean
Cc: sixpac@ietf.org
Subject: Re: [sixpac] Drafts on SIP-XMPP combined use
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: Fri, 19 Nov 2010 08:26:13 -0000

>-----Original Message-----
>From: ext Peter Musgrave [mailto:peter.musgrave@magorcorp.com]
>Sent: 18 November, 2010 07:01
>To: Veikkolainen Simo (Nokia-MS/Helsinki)
>Cc: sixpac@ietf.org
>Subject: Re: [sixpac] Drafts on SIP-XMPP combined use
>
>Hi Simo,
>
>A question about REQ-1:
>When it says "SIP Contact" information - does this mean literally the
>value in the SIP Contact: header?

No, what is meant here is the information by which a SIP request can be routed to the endpoint, meaning basically an AOR or GRUU.

>I think it might need to be the AOR - since that is required to be a
>FQDN and publicly reachable, whereas a contact header value might not
>be. However, in the case where the AOR has multiple contacts registered,
>would we require GRUU to specify which one is to be called?
>
>Is the requirement that the information provided allow for the specific
>UA instance to be contacted when this identity information is conveyed
>over XMPP?

Yes.

>REQ-3: Can you elaborate on "real time media contact and status" ? I am
>not sure what the requirement is asking for. An indication that an audio
>or video session simply exists - or details down to the port, CODEC etc.
>???

The wording is indeed a bit confusing. What we would like is to be able to indicate via XMPP presence that I'm available for voice or video calls on SIP, and if you want to contact me, here is my SIP AOR. Also, if I happen to be off-line, on the phone or otherwise not available for SIP calls, that should be indicated in the XMPP presence as well.

Simo

>Regards,
>
>Peter Musgrave
>
>
>
>On 2010-11-11, at 4:05 PM, <Simo.Veikkolainen@nokia.com>;
><Simo.Veikkolainen@nokia.com>; wrote:
>
>> Thanks Peter for setting up this list!
>>
>> Just as a reminder, the relevant I-D for this work is
>> http://tools.ietf.org/html/draft-veikkolainen-sip-xmpp-coex-reqs-01
>>
>> We had an earlier draft containing also the protocol extensions, but
>that one has been expired. However, you can find it at
>> http://tools.ietf.org/html/draft-veikkolainen-sip-voip-xmpp-im
>>
>> For our first target, I think we should concentrate on getting a set
>of requirements which is agreeable for all.
>>
>> Regards,
>> Simo
>>
>> _______________________________________________
>> sixpac mailing list
>> sixpac@ietf.org
>> https://www.ietf.org/mailman/listinfo/sixpac