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

Dear colleagues,

due to a boilerplate error the 18 version of the CC draft was uploaded, which changes the boilerplate from 'pre-5378' back to 'trust200902' (as it was until the 16 version).

Otherwise the 17 version and the 18 version are identical.

Best regards, Martin

> -----Ursprüngliche Nachricht-----
> Von: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]
> Im Auftrag von internet-drafts@ietf.org
> Gesendet: Freitag, 30. November 2012 11:08
> An: i-d-announce@ietf.org
> Cc: bliss@ietf.org
> Betreff: [BLISS] I-D Action: draft-ietf-bliss-call-completion-18.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-18.txt
>       Pages           : 37
>       Date            : 2012-11-30
>
> 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-18
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-bliss-call-completion-18
>
>
> 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
>