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

<Martin.Huelsemann@telekom.de> Thu, 14 April 2011 15:01 UTC

Return-Path: <Martin.Huelsemann@telekom.de>
X-Original-To: bliss@ietfc.amsl.com
Delivered-To: bliss@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 68801E073D for <bliss@ietfc.amsl.com>; Thu, 14 Apr 2011 08:01:27 -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 ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ER3-2k35CONQ for <bliss@ietfc.amsl.com>; Thu, 14 Apr 2011 08:01:26 -0700 (PDT)
Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by ietfc.amsl.com (Postfix) with ESMTP id 33748E0791 for <bliss@ietf.org>; Thu, 14 Apr 2011 08:01:26 -0700 (PDT)
Received: from he111527.emea1.cds.t-internal.com ([10.125.90.86]) by tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 14 Apr 2011 16:59:06 +0200
Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.191]) by HE111527.EMEA1.CDS.T-INTERNAL.COM ([2002:7cd:5a56::7cd:5a56]) with mapi; Thu, 14 Apr 2011 16:59:06 +0200
From: Martin.Huelsemann@telekom.de
To: bliss@ietf.org
Date: Thu, 14 Apr 2011 16:59:05 +0200
Thread-Topic: [BLISS] I-D Action:draft-ietf-bliss-call-completion-09.txt
Thread-Index: Acv6n76+hM08BsrjRAmEjg5vNc43cgADLmiw
Message-ID: <9762ACF04FA26B4388476841256BDE020113F82C0956@HE111543.emea1.cds.t-internal.com>
References: <20110414123003.28126.54267.idtracker@ietfc.amsl.com>
In-Reply-To: <20110414123003.28126.54267.idtracker@ietfc.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
Cc: j.dave.smith@siemens-enterprise.com
Subject: Re: [BLISS] I-D Action:draft-ietf-bliss-call-completion-09.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, 14 Apr 2011 15:01:27 -0000

Dear colleagues,

a 09 version of the CC draft was uploaded. This versions includes corrections (ABNF, wrong example, missing timer), resulting from the 3 sustantial comments I got during WGLC. Further there are editorials (spelling corrections, wording clarifications, example clarifications).


After WGLC I got comments refelecting different reqirements for CC running on a device and not on a server in the network, which would change some SHALLs to SHOULDs, see my last mail to the list. As I said in my opinion those changes are very useful for a more comprehensive CC solution, and therefore should be considered. I have therefore provided a 10_draft_a version of the internet draft. You can check the differences at



 http://bliss-ietf.org/drafts/diff_09_10_draft_a.html


 http://bliss-ietf.org/drafts/draft-ietf-bliss-call-completion-10_draft_a.txt



Regards, Martin




> -----Ursprüngliche Nachricht-----
> Von: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> Im Auftrag von Internet-Drafts@ietf.org
> Gesendet: Donnerstag, 14. April 2011 14:30
> An: i-d-announce@ietf.org
> Cc: bliss@ietf.org
> Betreff: [BLISS] I-D Action:draft-ietf-bliss-call-completion-09.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)       : D. Worley, et al.
>       Filename        : draft-ietf-bliss-call-completion-09.txt
>       Pages           : 31
>       Date            : 2011-04-14
>
> The call completion features allow the calling user of a
> failed call to be notified when the called user becomes
> available to receive a call.
>
> For the realization of a basic solution without queuing call-
> completion requests, this document references the usage of
> the 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 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:
> http://www.ietf.org/internet-drafts/draft-ietf-bliss-call-completion-09.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> Below is the data which will enable a MIME compliant mail
> reader implementation to automatically retrieve the ASCII
> version of the Internet-Draft.
>