Re: [Sipping] New OMA suggested requirements for draft-ietf-sipping-uri-list-conferencing-04.txt

Miguel Garcia <Miguel.An.Garcia@nokia.com> Wed, 08 February 2006 08:05 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6kKS-0005Vz-IR; Wed, 08 Feb 2006 03:05:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6kKO-0005VA-QV for sipping@megatron.ietf.org; Wed, 08 Feb 2006 03:05:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26112 for <sipping@ietf.org>; Wed, 8 Feb 2006 03:03:36 -0500 (EST)
Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6kWk-00015o-2B for sipping@ietf.org; Wed, 08 Feb 2006 03:18:17 -0500
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k18850c9016733; Wed, 8 Feb 2006 10:05:02 +0200
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Feb 2006 10:05:11 +0200
Received: from [127.0.0.1] ([172.21.34.231]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Wed, 8 Feb 2006 10:05:11 +0200
Message-ID: <43E9A636.3030008@nokia.com>
Date: Wed, 08 Feb 2006 10:05:10 +0200
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Dean Willis <dean.willis@softarmor.com>
Subject: Re: [Sipping] New OMA suggested requirements for draft-ietf-sipping-uri-list-conferencing-04.txt
References: <5D35B8AE-D546-4275-AB39-741EB818F84C@softarmor.com>
In-Reply-To: <5D35B8AE-D546-4275-AB39-741EB818F84C@softarmor.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Feb 2006 08:05:11.0307 (UTC) FILETIME=[624CADB0:01C62C86]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
Cc: Sipping List <sipping@ietf.org>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org

Actually, I spoke with Gonzalo about this potential usage of the 
'capacity' extension some time ago already.

I believe we should the following:

- Extract the 'capacity' extension to the resource-list from 
draft-ietf-sipping-uri-list-message-06.txt and place it in a separate 
document that just defines the XML schema and side-by effects (IANA 
registration, etc.).

- Modify draft-ietf-sipping-uri-list-message-06.txt to refer to the 
'capacity' extension draft.

- Modify draft-ietf-sipping-uri-list-conferencing-04.txt to refer to the 
'capacity' extension draft.

This is an editorial work, I can submit the 'capacity' draft in the next 
days. Is this acceptable?

/Miguel

Dean Willis wrote:
> 
> OM is looking at uri-list conferencing for their push-to-talk work. .
> 
> One of their needs is to inform POC recipients of the "cc" list -- that 
> is, the set of other URIs invited to the conference. They also have a 
> need for "bcc" participants who get invited but not advertised.
> 
> This is allowed for in the message-list work 
> (draft-ietf-sipping-uri-list-message-06.txt) by having the message 
> exploder include a copy of the recipient list on outbound messages, and 
> allows for tagging each target as a "to", "cc" or "bcc" using the usual 
> email semantics.
> 
> 
> Should we:
> 
> 1) Address this in our uri-list draft before publishing it (it's past 
> WGLC).
> 
> 2) Request OMA author a draft that extends our draft.
> 
> 
> I believe we could basically paste the recipient-notification text from 
> uri-list-message into uri-list-conferencing. But this is a fairly late 
> phase to be changing the requirements.
> 
> To meet the full set of conferencing requirements in current OMA 
> discussions, we would also need to add the role 'anonymous' and add some 
> discussion of how the roles interact with the conference-package 
> notifications.
> 
> What do you think?
> 
> -- 
> Dean
> 
> _______________________________________________
> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sip@ietf.org for new developments of core SIP
> 

-- 
Miguel A. Garcia           tel:+358-50-4804586
sip:miguel.an.garcia@openlaboratory.net
Nokia Research Center      Helsinki, Finland


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP