Re: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 -- 1010 Effect of non-correlation on the event model
"Worley, Dale R (Dale)" <email@example.com> Fri, 29 October 2010 00:54 UTC
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D7FED3A69A9 for <firstname.lastname@example.org>; Thu, 28 Oct 2010 17:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-102.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([22.214.171.124]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ft98PNd44ezz for <email@example.com>; Thu, 28 Oct 2010 17:54:19 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [126.96.36.199]) by core3.amsl.com (Postfix) with ESMTP id 60BBC3A6778 for <firstname.lastname@example.org>; Thu, 28 Oct 2010 17:54:19 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,255,1286164800"; d="scan'208";a="247106706"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([188.8.131.52]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 Oct 2010 20:55:53 -0400
X-IronPort-AV: E=Sophos;i="4.58,255,1286164800"; d="scan'208";a="530941685"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([184.108.40.206]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 28 Oct 2010 20:55:53 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 28 Oct 2010 20:55:53 -0400
From: "Worley, Dale R (Dale)" <email@example.com>
To: Shida Schubert <firstname.lastname@example.org>, BLISS <email@example.com>
Date: Thu, 28 Oct 2010 20:54:53 -0400
Thread-Topic: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 -- 1010 Effect of non-correlation on the event model
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 -- 1010 Effect of non-correlation on the event model
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 00:54:20 -0000
Paul K. has suggested that we treat call-completion subscriptions as being subscriptions to "the status of the queue" (the queue for the destination AOR), but that filtering is in effect such that each subscriber sees only the status of the queue entry that coresponds to his subscription. This idea seems to me to be enough to align our use of subscriptions with the formal model of RFC 3265, and thus allow us to have call-completion subscriptions operate like everyone wants them to without adding any further machinery. It also provides a way to add future extensions that provide special subscriptions that show the entire queue. Within that model, we need to make the following wording changes: (I've shortened CECE ("calls eligible for completion entity") to CCE ("call-completion entity").) Section 5 The callee's monitor manages CC for a single URI. This URI is likely to be a published AOR, or more likely "an AOR without its voicemail", but it may be as narrowly scoped as a single UA's contact URI. The monitor manages a dynamic set of call-completion entities (called "CCEs") which represent CC requests, or equivalently, the existing incoming call-completion subscriptions. This set is also called a queue, because a queue data structure often aids in implementing the monitor's policies for selecting CCEs for CC recall. Each CCE has an availability state, which is either "available" (for recall) or "not available" (for recall). It is not visible via subscriptions. Each CCE has a recall state which is visible via subscriptions. The recall state is either "queued" or "ready". Each CCE carries the From URI of the SUBSCRIBE request that caused its creation. CC subscriptions arrive at the the monitor by being addressed to the managed URI, or URIs the monitor returns in Call-Info headers. The request URI of the SUBSCRIBE request determines the queue to which the resulting CCE is added. The resulting subscription reports the status of the queue. The base event data is the status of all the CCEs in the queue, but the data returned by each subscription is filtered to report only the status of that subscription's CCE. (Further standardization may define means for obtaining more comprehensive information about a queue.) When a CCE is created, it is given the availability state "available" and recall state "queued". The monitor may receive PIDF bodies [RFC3863], via PUBLISH requests directed at its URI. These PUBLISH requests are expected to be sent by subscribers to suspend and resume their CC requests. A CCE is identified by the request-URI (if it was taken from a call-completion event notification and identifies the CCE) or the From URI of the request (matching the From URI recorded in the CCE). Receipt of a PUBLISH with 'status' of 'open' sets the availability state of the CCE to 'available'; 'status' of 'closed' sets the availability state of the CCE to 'not-available'. The monitor MUST select for recall only CC requests whose CCE's have availability state 'available', and for which the callee appears to be available considering the 'm' value of the CCE. Within that constraint, the monitor's selections are determined by its policy. Often, a monitor will choose the acceptable CCE that has been in the queue the longest. When the monitor has selected a CCE for recall, it changes the CCE's recall state from 'queued' to 'ready', which triggers a notification on the CCE's subscription. If a selected subscriber then suspends its request by sending a PUBLISH with status 'closed', the CCE becomes not-available, and the monitor changes the CCE's recall state to 'queued'. This may cause another CCE (e.g., that has been in the queue for less time) to be selected for recall. Dale
- Re: [BLISS] WGLC for draft-ietf-bliss-call-comple… Worley, Dale R (Dale)