
From internet-drafts@ietf.org  Fri Sep  7 04:26:56 2012
Return-Path: <internet-drafts@ietf.org>
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 3E09A21F87E6; Fri,  7 Sep 2012 04:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.419
X-Spam-Level: 
X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4kP5Sdqu-ZY; Fri,  7 Sep 2012 04:26:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6B421F87DA; Fri,  7 Sep 2012 04:26:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20120907112655.31762.48528.idtracker@ietfa.amsl.com>
Date: Fri, 07 Sep 2012 04:26:55 -0700
Cc: bliss@ietf.org
Subject: [BLISS] I-D Action: draft-ietf-bliss-call-completion-16.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: Fri, 07 Sep 2012 11:26:56 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Basic Level of Interoperability for SIP S=
ervices 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-16.txt
	Pages           : 36
	Date            : 2012-09-07

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-16

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bliss-call-completion-16


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From Martin.Huelsemann@telekom.de  Fri Sep  7 04:36:42 2012
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 3C29021E803C for <bliss@ietfa.amsl.com>; Fri,  7 Sep 2012 04:36:42 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VfcAIZX8P4iQ for <bliss@ietfa.amsl.com>; Fri,  7 Sep 2012 04:36:41 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0CB21E8034 for <bliss@ietf.org>; Fri,  7 Sep 2012 04:36:40 -0700 (PDT)
Received: from he111296.emea1.cds.t-internal.com ([10.125.90.14]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 07 Sep 2012 13:36:33 +0200
Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.3]) by HE111296.EMEA1.CDS.T-INTERNAL.COM ([fe80::19ac:3fb4:a382:6df4%16]) with mapi; Fri, 7 Sep 2012 13:36:32 +0200
From: <Martin.Huelsemann@telekom.de>
To: <bliss@ietf.org>
Date: Fri, 7 Sep 2012 13:36:31 +0200
Thread-Topic: [BLISS] I-D Action: draft-ietf-bliss-call-completion-16.txt
Thread-Index: Ac2M67BE74aWsXXYSACmx9xFW+KbIAAAEWiA
Message-ID: <9762ACF04FA26B4388476841256BDE02011659ED60FE@HE111543.emea1.cds.t-internal.com>
References: <20120907112655.31762.48528.idtracker@ietfa.amsl.com>
In-Reply-To: <20120907112655.31762.48528.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-16.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: Fri, 07 Sep 2012 11:36:42 -0000

Hi,

a new revision of the CC draft was uploaded, in which the presence server c=
omponent of the CC monitor was specified a littlebit more exactly. Please c=
heck if the functionality is considered appropriately now.


Best regards, Martin



> -----Urspr=FCngliche Nachricht-----
> Von: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> Im Auftrag von internet-drafts@ietf.org
> Gesendet: Freitag, 7. September 2012 13:27
> An: i-d-announce@ietf.org
> Cc: bliss@ietf.org
> Betreff: [BLISS] I-D Action: draft-ietf-bliss-call-completion-16.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-16.txt
>       Pages           : 36
>       Date            : 2012-09-07
>
> 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-16
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bliss-call-completion-16
>
>
> 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
>
