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

"Anton Tveretin" <fas_vm@surguttel.ru> Fri, 15 February 2013 16:47 UTC

Return-Path: <fas_vm@surguttel.ru>
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 7AFF321F8733; Fri, 15 Feb 2013 08:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.128
X-Spam-Level:
X-Spam-Status: No, score=-1.128 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, STOX_REPLY_TYPE=0.001]
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 jy48NgComa6H; Fri, 15 Feb 2013 08:47:21 -0800 (PST)
Received: from mail.s86.ru (mail.s86.ru [217.8.80.233]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB2421F8862; Fri, 15 Feb 2013 08:47:21 -0800 (PST)
Received: by mail.s86.ru (Postfix, from userid 1116) id DF679514DD4; Fri, 15 Feb 2013 22:43:33 +0600 (YEKT)
Received: from Gateway (unknown [151.252.65.175]) by mail.s86.ru (Postfix) with ESMTPA id B7788514B9F; Fri, 15 Feb 2013 22:43:30 +0600 (YEKT)
Message-ID: <8EEE2034E98F4A69BF59117AD6248055@Gateway>
From: "Anton Tveretin" <fas_vm@surguttel.ru>
To: <internet-drafts@ietf.org>, <bliss@ietf.org>, <iesg@ietf.org>
References: <20130211145406.7287.62144.idtracker@ietfa.amsl.com>
Date: Fri, 15 Feb 2013 22:22:14 +0600
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-Antivirus: avast! (VPS 130215-0, 15.02.2013), Outbound message
X-Antivirus-Status: Clean
Subject: Re: [BLISS] I-D Action: draft-ietf-bliss-call-completion-19.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, 15 Feb 2013 16:47:22 -0000

Authors just ignored my suggestion (sent 2012-12-31). So this standard could 
make interoperability issues.
Maybe I'm wrong, but this should be discussed.

----- Original Message ----- 
From: <internet-drafts@ietf.org>;
To: <i-d-announce@ietf.org>;
Cc: <bliss@ietf.org>;
Sent: Monday, February 11, 2013 8:54 PM
Subject: [BLISS] I-D Action: draft-ietf-bliss-call-completion-19.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-19.txt
> Pages           : 39
> Date            : 2013-02-11
>
> 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-19
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-bliss-call-completion-19
>
>
> 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