[BLISS] RFC 6910 on Completion of Calls for the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Mon, 15 April 2013 21:50 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bliss@ietfa.amsl.com
Delivered-To: bliss@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0C66621F9434; Mon, 15 Apr 2013 14:50:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.3
X-Spam-Status: No, score=-102.3 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 1RfHBDBoT+YG; Mon, 15 Apr 2013 14:50:56 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9A1FD21F9418; Mon, 15 Apr 2013 14:50:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A6236B1E002; Mon, 15 Apr 2013 14:50:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130415215001.A6236B1E002@rfc-editor.org>
Date: Mon, 15 Apr 2013 14:50:01 -0700 (PDT)
X-Mailman-Approved-At: Wed, 17 Apr 2013 20:22:00 -0700
Cc: bliss@ietf.org, rfc-editor@rfc-editor.org
Subject: [BLISS] RFC 6910 on Completion of Calls for the Session Initiation Protocol (SIP)
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 15 Apr 2013 21:50:57 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6910

        Title:      Completion of Calls for the 
                    Session Initiation Protocol (SIP) 
        Author:     D. Worley, M. Huelsemann,
                    R. Jesske, D. Alexeitsev
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2013
        Mailbox:    worley@ariadne.com, 
        Pages:      37
        Characters: 86166
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bliss-call-completion-19.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6910.txt

The "completion of calls" feature defined in this specification
allows the caller of a failed call to be notified when the callee
becomes available to receive a call.

For the realization of a basic solution without queuing, this
document references the usage of the dialog event package (RFC 4235)
that is described as 'Automatic Redial' in "Session Initiation                           
Protocol Service Examples" (RFC 5359).

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

The architecture is designed to interoperate well with existing
completion of calls solutions in other networks.

This document is a product of the Basic Level of Interoperability for SIP Services Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC