Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Miguel Garcia <Miguel.An.Garcia@nokia.com> Wed, 28 September 2005 11:02 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1EKZhs-0006rq-Kv; Wed, 28 Sep 2005 07:02:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1EKZhr-0006rW-MB
for sipping-tispan@megatron.ietf.org; Wed, 28 Sep 2005 07:02:35 -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 HAA28464
for <sipping-tispan@ietf.org>; Wed, 28 Sep 2005 07:02:33 -0400 (EDT)
Received: from mgw-ext04.nokia.com ([131.228.20.96])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKZpG-0000xJ-SB
for sipping-tispan@ietf.org; Wed, 28 Sep 2005 07:10:17 -0400
Received: from esebh108.NOE.Nokia.com (esebh108.ntc.nokia.com [172.21.143.145])
by mgw-ext04.nokia.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id
j8SB06Gg009784; Wed, 28 Sep 2005 14:00:08 +0300
Received: from esebh001.NOE.Nokia.com ([172.21.138.28]) by
esebh108.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 28 Sep 2005 14:02:23 +0300
Received: from [127.0.0.1] ([172.21.36.219]) by esebh001.NOE.Nokia.com with
Microsoft SMTPSVC(5.0.2195.6881); Wed, 28 Sep 2005 14:02:23 +0300
Message-ID: <433A783F.4010908@nokia.com>
Date: Wed, 28 Sep 2005 14:02:23 +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: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
References: <072C5B76F7CEAB488172C6F64B30B5E39C9773@xmb-rtp-20b.amer.cisco.com>
In-Reply-To: <072C5B76F7CEAB488172C6F64B30B5E39C9773@xmb-rtp-20b.amer.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 28 Sep 2005 11:02:23.0437 (UTC)
FILETIME=[1A9A37D0:01C5C41C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d
Content-Transfer-Encoding: 7bit
Cc: Tessa Silvia <Silvia.Tessa@TILAB.COM>, 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 Mike: Inline discussion. Michael Hammer (mhammer) wrote: > Miguel, > > Continuing on my earlier comment: By network are you taking routers? No. I am referring to SIP entities in general, including proxies, registrars, application servers, etc., as required. > > If you mean voice host applications such as proxies, are you suggesting > that a proxy in the middle of a network somewhere will do this > prioritization? Yes, exactly. I don't know yet if this will be a proxy or an application server, or what. But according to the requirement there should be a SIP entity that is able to do such prioritization. > > If you mean some service of the callee, what is the chance that 2 calls > will arrive simultaneously? Very little, if not to say, impossible. But withing a period of time, it is possible (see below). > > Or do you mean the callee (or his server) will know that there is a > caller camped on and will intentionally delay incoming calls while a > "subscriber free" indication is sent toward the caller and completed > with some notification or timer before moving on to the regular call? Something like that. By reading the spec, once the callee becomes free, it gives him a few seconds (max. 15 seconds) in case he wants to make another call (this is the so-called idle timer). If a call arrives during this time, it will have the same treatment as "busy". I think the above also applies to the period of time when the caller is indicated that the callee is free, so that the caller can accept a CCBS recall. > > I certainly hope you are not suggesting that we elevate CCBS calls to > the status of emergency calling. There are only so many useful levels > of priority, and this could muddy the water. No, no, I am not suggesting that. /Miguel > > Mike > > >>-----Original Message----- >>From: sipping-tispan-bounces@ietf.org >>[mailto:sipping-tispan-bounces@ietf.org] On Behalf Of Miguel Garcia >>Sent: Tuesday, September 27, 2005 7:47 AM >>To: Schmidt, Christian >>Cc: Tessa Silvia; sipping-tispan@ietf.org >>Subject: Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f >> >> >> >>Schmidt, Christian wrote: >> >> >>> >>>We have already have REQ 12 stating that >>> Any communication performed as a result of the execution of a >>>CCBS/CCNR request should be distinguishable from regular >> >>communications. >> >>>So, all terminating call are "distinguishable" and any policy a >>>network might have could be easily based on this, without >> >>further requirements. >> >>>Other views ? >>> >>>Christian: I see, perhaps you can add a short explanation >> >>for this purpose: >> >>> Any communication performed as a result of the execution of a >>>CCBS/CCNR request should be distinguishable from regular >> >>communications. >> >>>This can be used to priorize CCBS/CCNR calls towards the callee. >>>What do you think? >>> >> >>I have a proposal for this requirement: >> >> >> REQ-CCBS/CCNR-12: >> It must be possible for the network to priotirize >>CCBS/CCNR recalls >> towards the callee, above regular calls. This implies that any >> communication performed as a result of the execution of a >>CCBS/CCNR >> request should be distinguishable from regular communications. >> >> >>/Miguel >> >> >> >>>Regards >>>Silvia >>> >> >> >>-- >>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
- AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Schmidt, Christian
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- RE: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Michael Hammer (mhammer)
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Paul Kyzivat
- AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Schmidt, Christian
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Paul Kyzivat
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Miguel Garcia
- AW: [Sipping-tispan] Re: CCBS/CCNR in Version -02f Jesske, R
- Re: AW: [Sipping-tispan] Re: CCBS/CCNR in Version… Paul Kyzivat