Re: [Sipping-tispan] [CCBS/CCNR]

Miguel Garcia <Miguel.An.Garcia@nokia.com> Fri, 02 September 2005 11:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EBA8I-0001zV-SD; Fri, 02 Sep 2005 07:54:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EBA8H-0001y2-AG for sipping-tispan@megatron.ietf.org; Fri, 02 Sep 2005 07:54:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01235 for <sipping-tispan@ietf.org>; Fri, 2 Sep 2005 07:54:56 -0400 (EDT)
Received: from mgw-ext03.nokia.com ([131.228.20.95]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EBAAP-0007wh-Gp for sipping-tispan@ietf.org; Fri, 02 Sep 2005 07:57:10 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-ext03.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id j82Bs9ru005422; Fri, 2 Sep 2005 14:54:10 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Sep 2005 14:54:52 +0300
Received: from [127.0.0.1] ([172.21.35.75]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Fri, 2 Sep 2005 14:54:52 +0300
Message-ID: <43183D8C.3060303@nokia.com>
Date: Fri, 02 Sep 2005 14:54:52 +0300
From: Miguel Garcia <Miguel.An.Garcia@nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, es-es
MIME-Version: 1.0
To: "Michael Hammer (mhammer)" <mhammer@cisco.com>
Subject: Re: [Sipping-tispan] [CCBS/CCNR]
References: <072C5B76F7CEAB488172C6F64B30B5E382E1A9@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E382E1A9@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Sep 2005 11:54:52.0987 (UTC) FILETIME=[2123E8B0:01C5AFB5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit
Cc: sipping-tispan@ietf.org
X-BeenThere: sipping-tispan@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of requirements for SIP introduced by ETSI TISPAN <sipping-tispan.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sipping-tispan>
List-Post: <mailto:sipping-tispan@ietf.org>
List-Help: <mailto:sipping-tispan-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping-tispan>, <mailto:sipping-tispan-request@ietf.org?subject=subscribe>
Sender: sipping-tispan-bounces@ietf.org
Errors-To: sipping-tispan-bounces@ietf.org

Hi Michel:

Inline comments.

Michael Hammer (mhammer) wrote:

>  
> 
> 
>>-----Original Message-----
>>From: sipping-tispan-bounces@ietf.org 
>>[mailto:sipping-tispan-bounces@ietf.org] On Behalf Of Miguel Garcia
>>Sent: Thursday, September 01, 2005 5:19 AM
>>To: sipping-tispan@ietf.org
>>Subject: [Sipping-tispan] [CCBS/CCNR]
>>
>>Hi:
>>
>>with respect the added CCBS/CCNR requirements, I think 
>>something is still missing.
>>
>>- A bit more elaboration on the queue management, precisely, 
>>what are the implications for the service (I think there is 
>>the concept of a "timeslot" in which a user can return a 
>>call, and if it doesn't happen, the user misses his turn in 
>>the queue ... or somethign like that.
> 
> 
> How about:
> 
> The submission of a CCBS/CCNR queue request must include a time limit.
> 

Probably this isn't a must, but a may, but otherwise I agree. That 
wasn't my question either, but the principle is ok.


> The CCBS/CCNR queue service may adjust the request time limits based on
> local policy.
> 

Sure as well.

> 
> 
>>- A definition of a "CCBS/CCNR request", which at the moment, 
>>misleads me in the interpretation of the service. It can mean 
>>two different
>>things: "Please add me to the CCBS/CCNR queue of the callee", 
>>or "this is a session returned as a result of an indication 
>>from CCBS/CCNR".
> 
> 
> and:
> 
> The CCBS/CCNR callee must have the means to inform a queued caller that
> the callee is free along with the means for the caller to originate the
> subsequent session setup such that it can be distinguished by the callee
> from other possible session setups.

Yes, also agreed.

/Miguel


> 
> Mike
> 
> 
>>- Perhaps and explanation that the queue manager must be able 
>>to distinguish between "call in return to CCBS/CCNR free 
>>indication" from regular calls. This is related to the 
>>"timeslot" concept as well.
>>
>>Anyone with further information of the requirements, please comment.
>>
>>/Miguel
>>
>>-- 
>>Miguel A. Garcia           tel:+358-50-4804586
>>sip:miguel.an.garcia@openlaboratory.net
>>Nokia Research Center      Helsinki, Finland
>>
>>
>>_______________________________________________
>>Sipping-tispan mailing list
>>Sipping-tispan@ietf.org
>>https://www1.ietf.org/mailman/listinfo/sipping-tispan
> 
> 

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


_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan