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

<Martin.Huelsemann@telekom.de> Fri, 06 May 2011 12:26 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 11F26E06EF for <bliss@ietfa.amsl.com>; Fri, 6 May 2011 05:26:40 -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 6EqKun7s6kle for <bliss@ietfa.amsl.com>; Fri, 6 May 2011 05:26:39 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id F2968E06EA for <bliss@ietf.org>; Fri, 6 May 2011 05:26:38 -0700 (PDT)
Received: from he111297.emea1.cds.t-internal.com ([10.125.90.15]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 06 May 2011 14:26:21 +0200
Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.131]) by HE111297.EMEA1.CDS.T-INTERNAL.COM ([fe80::9835:b110:c489:6d64%16]) with mapi; Fri, 6 May 2011 14:26:21 +0200
From: <Martin.Huelsemann@telekom.de>
To: <shida@ntt-at.com>, <bliss@ietf.org>
Date: Fri, 6 May 2011 14:26:20 +0200
Thread-Topic: AW: [BLISS] I-D Action:draft-ietf-bliss-call-completion-09.txt
Thread-Index: AcwIYnI3JognKiOBRpONy51AxPoiKADhiJpw
Message-ID: <9762ACF04FA26B4388476841256BDE020114421013B9@HE111543.emea1.cds.t-internal.com>
References: <20110414123003.28126.54267.idtracker@ietfc.amsl.com> <9762ACF04FA26B4388476841256BDE020113F82C0956@HE111543.emea1.cds.t-internal.com> <E0B0D561-77BF-4468-BE7A-6E1884C54D43@ntt-at.com>
In-Reply-To: <E0B0D561-77BF-4468-BE7A-6E1884C54D43@ntt-at.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-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: Fri, 06 May 2011 12:26:40 -0000

Dear colleagues,

the -10 version of the draft has been uploaded:

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


Best regards
Martin




> -----Ursprüngliche Nachricht-----
> Von: Shida Schubert [mailto:shida@ntt-at.com]
> Gesendet: Montag, 2. Mai 2011 02:47
> An: Hülsemann, Martin
> Cc: bliss@ietf.org; Jesske, Roland;
> j.dave.smith@siemens-enterprise.com
> Betreff: Re: AW: [BLISS] I-D
> Action:draft-ietf-bliss-call-completion-09.txt
>
>
> All;
>
>  As we have received no feedback on the proposed changes, I
> will ask the authors to reflect the changes and submit the
> version 10.
>
>  I will do a proto-writeup based on version 10.
>
>  Many Thanks
>   Shida (As a chair)
>






> On Apr 14, 2011, at 11:59 PM, <Martin.Huelsemann@telekom.de>;
> <Martin.Huelsemann@telekom.de>; wrote:
>
> > 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.
> >>
>
>