Re: AW: [Sipping-tispan] [CCBS/CCNR]
Miguel Garcia <Miguel.An.Garcia@nokia.com> Mon, 05 September 2005 11:30 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1ECFB0-0005r4-2s; Mon, 05 Sep 2005 07:30:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1ECFAy-0005qz-7N
for sipping-tispan@megatron.ietf.org; Mon, 05 Sep 2005 07:30:12 -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 HAA11243
for <sipping-tispan@ietf.org>; Mon, 5 Sep 2005 07:30:11 -0400 (EDT)
Received: from mgw-ext01.nokia.com ([131.228.20.93])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ECFDh-0003qF-4D
for sipping-tispan@ietf.org; Mon, 05 Sep 2005 07:33:03 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
by mgw-ext01.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
j85BU84q031879; Mon, 5 Sep 2005 14:30:08 +0300
Received: from esebh002.NOE.Nokia.com ([172.21.138.77]) by
esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
Mon, 5 Sep 2005 14:30:08 +0300
Received: from [127.0.0.1] ([172.21.35.75]) by esebh002.NOE.Nokia.com with
Microsoft SMTPSVC(5.0.2195.6881); Mon, 5 Sep 2005 14:30:08 +0300
Message-ID: <431C2C3F.1050809@nokia.com>
Date: Mon, 05 Sep 2005 14:30:07 +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: "Schmidt, Christian" <christian-schmidt@siemens.com>
Subject: Re: AW: [Sipping-tispan] [CCBS/CCNR]
References: <72963DDDF17D7949ABD18DC5DA58E7700583EE@MCHP7R5A.ww002.siemens.net>
In-Reply-To: <72963DDDF17D7949ABD18DC5DA58E7700583EE@MCHP7R5A.ww002.siemens.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-OriginalArrivalTime: 05 Sep 2005 11:30:08.0360 (UTC)
FILETIME=[2B790E80:01C5B20D]
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mgw-ext01.nokia.com id
j85BU84q031879
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Content-Transfer-Encoding: quoted-printable
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
Some (inline) thoughts.
Schmidt, Christian wrote:
> Some additional questions / comments:
> - Are CCBS / CCNR related to a terminal or an AOR of caller/callee?
I guess they are related to an AOR, not to a terminal.
> - A more precise definition of state change is needed (e.g. using BYE or INVITE for a call, avoiding busy/idle expression)
Seems reasonable to me
> - What is the meaning of "the callee showed activity"? Could this be WWW search as well?
I guess so, if the terminal implements HTTP... I think you have in mind
a computer, so if the user returns and the computer registers activity
on the keyboard, then the user is no longer idle, and an indication
could be sent... this looks like presence
> - A message toward the caller about state change of the callee is missing
Ok
> - Are multiple request possible for CCNR as with CCBS?
I guess so, providing they are addressed to different users.
> - Is it possible for a caller to have simultaneous CCBS and CCNR requests?
Why not?
> - If a CCBS / CCNR request is cancelled from the network, should the caller be informed?
yes, definitely. I am not sure if the network can cancel such request,
but the user should be informed.
> - The same expression as in the other requirements should be used, meaning caller and callee instead of UAC and UAS. Or UAC and UAS have to be explained in this context.
Good point.
Thanks
MIguel
> Regards,
> Christian
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: sipping-tispan-bounces@ietf.org [mailto:sipping-tispan-bounces@ietf.org] Im Auftrag von Miguel Garcia
> Gesendet: Donnerstag, 1. September 2005 11:19
> An: sipping-tispan@ietf.org
> Betreff: [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.
> - 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".
> - 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
- AW: [Sipping-tispan] [CCBS/CCNR] Schmidt, Christian
- Re: AW: [Sipping-tispan] [CCBS/CCNR] Miguel Garcia