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

Peter Musgrave <peter.musgrave@magorcorp.com> Thu, 18 November 2010 05:00 UTC

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 C51E33A67AE for <sixpac@core3.amsl.com>; Wed, 17 Nov 2010 21:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 D-79Fa3vZ2bH for <sixpac@core3.amsl.com>; Wed, 17 Nov 2010 21:00:24 -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 E96AE3A66B4 for <sixpac@ietf.org>; Wed, 17 Nov 2010 21:00:20 -0800 (PST)
Received: by yxd39 with SMTP id 39so1761184yxd.31 for <sixpac@ietf.org>; Wed, 17 Nov 2010 21:01:07 -0800 (PST)
Received: by 10.150.203.1 with SMTP id a1mr315726ybg.94.1290056467232; Wed, 17 Nov 2010 21:01:07 -0800 (PST)
Received: from [172.22.12.84] ([220.229.255.7]) by mx.google.com with ESMTPS id w5sm28815ybe.10.2010.11.17.21.01.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 17 Nov 2010 21:01:06 -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: <B23B311878A0B4438F5F09F47E01AAE05103C096C7@NOK-EUMSG-01.mgdnok.nokia.com>
Date: Thu, 18 Nov 2010 13:01:02 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B319CDD-C6D5-4CCC-B177-1D63C9996D96@magorcorp.com>
References: <B23B311878A0B4438F5F09F47E01AAE05103C096C7@NOK-EUMSG-01.mgdnok.nokia.com>
To: <Simo.Veikkolainen@nokia.com> <Simo.Veikkolainen@nokia.com>
X-Mailer: Apple Mail (2.1082)
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: Thu, 18 Nov 2010 05:00:24 -0000

Hi Simo, 

A question about REQ-1: 
When it says "SIP Contact" information - does this mean literally the value in the SIP Contact: header? 

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?

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. ???

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