Re: [BLISS] Use of the PUBLISH transaction for the SUS/RES procedures
"Huelsemann, Martin" <Martin.Huelsemann@telekom.de> Tue, 27 May 2008 04:28 UTC
Return-Path: <bliss-bounces@ietf.org>
X-Original-To: bliss-archive@optimus.ietf.org
Delivered-To: ietfarch-bliss-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41BCB3A6B8F; Mon, 26 May 2008 21:28:15 -0700 (PDT)
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 31D863A6B8F for <bliss@core3.amsl.com>; Mon, 26 May 2008 21:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGQMw-eYSGtq for <bliss@core3.amsl.com>; Mon, 26 May 2008 21:28:13 -0700 (PDT)
Received: from tcmail23.telekom.de (tcmail23.telekom.de [217.6.95.237]) by core3.amsl.com (Postfix) with ESMTP id B02633A6B84 for <bliss@ietf.org>; Mon, 26 May 2008 21:28:08 -0700 (PDT)
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de [10.125.177.105]) by tcmail21.telekom.de with ESMTP; Tue, 27 May 2008 06:28:07 +0200
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 27 May 2008 06:28:07 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 27 May 2008 06:28:01 +0200
Message-Id: <CCA850DCD3FBE2479D5076C5C187322203FF8787@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <F452BB3496398949B9D6634F9B6B155704128142@S4DE9JSAAMW.ost.t-com.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BLISS] Use of the PUBLISH transaction for the SUS/RES procedures
Thread-Index: Aci3UFva3AEq8ifaQrekSONAWYlQnADGPYewAVGB6eA=
References: <CCA850DCD3FBE2479D5076C5C187322203F6E6B7@S4DE9JSAAHW.ost.t-com.de> <482D7E13.4000804@cisco.com> <F452BB3496398949B9D6634F9B6B155704128142@S4DE9JSAAMW.ost.t-com.de>
From: "Huelsemann, Martin" <Martin.Huelsemann@telekom.de>
To: "Alexeitsev, D" <D.Alexeitsev@telekom.de>, pkyzivat@cisco.com
X-OriginalArrivalTime: 27 May 2008 04:28:07.0326 (UTC) FILETIME=[0FFB23E0:01C8BFB2]
Cc: bliss@ietf.org
Subject: Re: [BLISS] Use of the PUBLISH transaction for the SUS/RES procedures
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: bliss-bounces@ietf.org
Errors-To: bliss-bounces@ietf.org
The proposal to sort of publish to caller's supension and resumption state was also resulting from previous comments, that just unsubscribe to the call-completion information won't (or better: has not to) change the CC state. So when the monitor calculates who's next for CC, a unsubscribed caller ('s agent) would still be considered to be the next candidate for the CC call somehow if he is on top of the queue, which then of course would reduce the performance of the service.
To avoid this publishing sus/res information seems to be a valid and explicit solution.
BR, Martin
>
>
> >OTOH, its far from clear to me that this is preferable to
> the existing
> >proposal for the candidate caller to unsubscribe when it
> doesn't want to
> >be called back.
>
> Why? Could you describe the issue?
>
> Greetings,
> Denis Alexeitsev
>
_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www.ietf.org/mailman/listinfo/bliss
- [BLISS] Use of the PUBLISH transaction for the SU… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Alexeitsev, D
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… DRAGE, Keith (Keith)
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Paul Kyzivat
- Re: [BLISS] Use of the PUBLISH transaction for th… Huelsemann, Martin