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

<Martin.Huelsemann@telekom.de> Thu, 02 August 2012 11:29 UTC

Return-Path: <Martin.Huelsemann@telekom.de>
X-Original-To: bliss@ietfa.amsl.com
Delivered-To: bliss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B41421F8DA4 for <bliss@ietfa.amsl.com>; Thu, 2 Aug 2012 04:29:35 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RenPwJ8vpagt for <bliss@ietfa.amsl.com>; Thu, 2 Aug 2012 04:29:34 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id 110C421F8DA6 for <bliss@ietf.org>; Thu, 2 Aug 2012 04:29:33 -0700 (PDT)
Received: from he111296.emea1.cds.t-internal.com ([10.125.90.14]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 02 Aug 2012 13:29:01 +0200
Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.163]) by HE111296.EMEA1.CDS.T-INTERNAL.COM ([fe80::19ac:3fb4:a382:6df4%16]) with mapi; Thu, 2 Aug 2012 13:29:01 +0200
From: <Martin.Huelsemann@telekom.de>
To: <bliss@ietf.org>
Date: Thu, 2 Aug 2012 13:29:00 +0200
Thread-Topic: [BLISS] I-D Action: draft-ietf-bliss-call-completion-15.txt
Thread-Index: Ac1wlAMl7ERzTdx2ThiGgHpMWI8VigACbI5g
Message-ID: <9762ACF04FA26B4388476841256BDE020115FF999CA9@HE111543.emea1.cds.t-internal.com>
References: <20120802094825.27637.79622.idtracker@ietfa.amsl.com>
In-Reply-To: <20120802094825.27637.79622.idtracker@ietfa.amsl.com>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [BLISS] I-D Action: draft-ietf-bliss-call-completion-15.txt
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: Thu, 02 Aug 2012 11:29:35 -0000

Dear colleagues,

a new version of the call-completion draft has been uploaded.

There are no technical changes, but we've tried to clarify a lot of things, based on the questions that came up at the AD review. Please check of all the points have been addressed:

http://tools.ietf.org/rfcdiff?url1=http://tools.ietf.org/id/draft-ietf-bliss-call-completion-14.txt&url2=http://tools.ietf.org/id/draft-ietf-bliss-call-completion-15.txt


I think one of the most important clarifications was that in context of suspend/resume procedures PUBLISH is used in accordance with RFC 3903, an example has been added.


Regards, Martin






> -----Urspr√ľngliche Nachricht-----
> Von: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> Im Auftrag von internet-drafts@ietf.org
> Gesendet: Donnerstag, 2. August 2012 11:48
> An: i-d-announce@ietf.org
> Cc: bliss@ietf.org
> Betreff: [BLISS] I-D Action: draft-ietf-bliss-call-completion-15.txt
>
>
> 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)       : Dale R. Worley
>                           Martin Huelsemann
>                           Roland Jesske
>                           Denis Alexeitsev
>       Filename        : draft-ietf-bliss-call-completion-15.txt
>       Pages           : 35
>       Date            : 2012-08-02
>
> Abstract:
>    The call completion 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 the SIP 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 "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 of the original, failed call is made.
>
>    The architecture is designed to interoperate well with
> existing call-
>    completion solutions in other networks.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-bliss-call-completion
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-bliss-call-completion-15
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-bliss-call-completion-15
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www.ietf.org/mailman/listinfo/bliss
>