[BLISS] I-D Action:draft-ietf-bliss-call-completion-08.txt

Internet-Drafts@ietf.org Tue, 28 December 2010 13:15 UTC

Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 10C993A6962; Tue, 28 Dec 2010 05:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Mr8Ke5eqD65R; Tue, 28 Dec 2010 05:15:01 -0800 (PST)
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id 564F33A695D; Tue, 28 Dec 2010 05:15:01 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20101228131501.12668.64958.idtracker@localhost>
Date: Tue, 28 Dec 2010 05:15:01 -0800
Cc: bliss@ietf.org
Subject: [BLISS] I-D Action:draft-ietf-bliss-call-completion-08.txt
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/mail-archive/web/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>
X-List-Received-Date: Tue, 28 Dec 2010 13:15:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Basic Level of Interoperability for SIP Services Working Group of the IETF.

	Title           : Call Completion for Session Initiation Protocol (SIP)
	Author(s)       : D. Worley, et al.
	Filename        : draft-ietf-bliss-call-completion-08.txt
	Pages           : 31
	Date            : 2010-12-28

The call completion features allow the calling user of a failed call
to be notified when the called user becomes available to receive a

For the realization of a basic solution without queueing call-
completion requests, this document references the usage of the the
dialog event package (defined in RFC 4235) that is described as
'automatic redial' in (RFC 5359, SIP Service Examples).

For the realization of a more comprehensive solution with queueing
call-completion requests, this document introduces an architecture
for implementing these features in the Session Initiation Protocol:
"Call completion" implementations associated with the caller's and
callee's endpoints cooperate to place the caller's request for call
completion into a queue at the callee's endpoint, and, when a
caller's request is ready to be serviced, re-attempt the original,
failed call.

The deployment of a certain SIP call-completion solution is also
dependent on the needed level of interoperability with existing call-
completion solutions in other networks.

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the