RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f

"GARCIN Sebastien RD-CORE-ISS" <sebastien.garcin@francetelecom.com> Thu, 29 September 2005 08:11 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKtVt-0002t3-HX; Thu, 29 Sep 2005 04:11:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EKtVr-0002rV-0O for sipping-tispan@megatron.ietf.org; Thu, 29 Sep 2005 04:11:31 -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 EAA25713 for <sipping-tispan@ietf.org>; Thu, 29 Sep 2005 04:11:28 -0400 (EDT)
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EKtdQ-0002Ht-JI for sipping-tispan@ietf.org; Thu, 29 Sep 2005 04:19:24 -0400
Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Thu, 29 Sep 2005 10:10:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Date: Thu, 29 Sep 2005 10:10:58 +0200
Message-ID: <49E7012A614B024B80A7D175CB9A64EC06C8B63E@ftrdmel1.rd.francetelecom.fr>
Thread-Topic: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
Thread-Index: AcXEvlRKYkP5p44lSim/kDReUBt2vAADd5ug
From: "GARCIN Sebastien RD-CORE-ISS" <sebastien.garcin@francetelecom.com>
To: "Elwell, John" <john.elwell@siemens.com>, "Miguel Garcia" <Miguel.An.Garcia@nokia.com>, "Michael Hammer \(mhammer\)" <mhammer@cisco.com>
X-OriginalArrivalTime: 29 Sep 2005 08:10:59.0129 (UTC) FILETIME=[53171A90:01C5C4CD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Content-Transfer-Encoding: quoted-printable
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

John,

You seems to want try and open the endless debate about where the intelligence should be placed in the network or in the terminals. The approach you are proposing is not something that TISPAN will accept so I suggest that we move out of this debate.

sébastien 
 

-----Message d'origine-----
De : sipping-tispan-bounces@ietf.org [mailto:sipping-tispan-bounces@ietf.org] De la part de Elwell, John
Envoyé : jeudi 29 septembre 2005 08:20
À : Miguel Garcia; Michael Hammer (mhammer)
Cc : Tessa Silvia; sipping-tispan@ietf.org
Objet : RE: [Sipping-tispan] Re: CCBS/CCNR in Version -02f

Miguel,

In-line,

John

> -----Original Message-----
> From: Miguel Garcia [mailto:Miguel.An.Garcia@nokia.com]
> Sent: 28 September 2005 10:31
> To: Michael Hammer (mhammer)
> Cc: Tessa Silvia; sipping-tispan@ietf.org
> Subject: Re: [Sipping-tispan] Re: CCBS/CCNR in Version -02f
> 
> Hi Mike:
> 
> Inline discussion.
> 
> Michael Hammer (mhammer) wrote:
> 
> > Miguel,
> > 
> > I think there is still a little bit of schizophrenia in the 
> > requirements.  I assume that a server is acting on behalf
> of either the
> > caller or the callee, but not both because each could be served by a 
> > different host, domain, or organization.  The first
> requirement seems to
> > assume that the CCBS is a terminating service of the callee.  Other 
> > requirements seem to assume that the CCBS is a service of
> the caller.
> > Which is it?
> 
> Both. It has been demonstrated that CCBS is a service that requires 
> cooperation of both the originating and terminatine service providers.
> This cooperation is mostly required to manage queues of both the 
> caller and callee, and to manage susped/resume states.
[JRE] It is not clear to me what the involvement of the originating service provider is. Perhaps this comes down to what exactly are the requirements for notifying the caller that a call may now succeed. Is this notification constrained to go to the same UA that requested CCBS/CCNR in the first place, or should it go to any UA currently registered as a contact for the caller's AoR? In my opinion the former is sufficient and indeed probably preferable. If I request CCBS/CCNR from a particular UA I would expect to receive the notification on that same UA and make the new call attempt from there. In the relatively infrequent event that I move to a different UA in the intervening period, I could simply request CCBS/CCNR again from the new UA.

So on the assumption that CCBS/CCNR involves only a single UA on the caller side, what service does the originating service provider perform? Why can't the UA directly request CCBS/CCNR and communicate with the service provider on the callee side to achieve this? The caller's UA will receive notification when a the call can be made and can present that information to the caller somehow, allowing the caller to choose when to proceed with that call, e.g., whether to interrupt any ongoing communications in order to make that call.


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

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