From shida@ntt-at.com Mon Jan 10 16:22:35 2011 Return-Path: X-Original-To: bliss@core3.amsl.com Delivered-To: bliss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB1FF3A6819 for ; Mon, 10 Jan 2011 16:22:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IoyB3wp37vDx for ; Mon, 10 Jan 2011 16:22:35 -0800 (PST) Received: from gateway14.websitewelcome.com (gateway14.websitewelcome.com [67.18.94.7]) by core3.amsl.com (Postfix) with SMTP id E3B6D3A67E9 for ; Mon, 10 Jan 2011 16:22:34 -0800 (PST) Received: (qmail 8632 invoked from network); 11 Jan 2011 00:27:13 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway14.websitewelcome.com with SMTP; 11 Jan 2011 00:27:13 -0000 Received: from [122.130.140.219] (port=49416 helo=[192.168.1.6]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1PcS2W-0002aV-M6 for bliss@ietf.org; Mon, 10 Jan 2011 18:24:45 -0600 From: Shida Schubert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 11 Jan 2011 09:24:46 +0900 Message-Id: To: BLISS Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator465.hostgator.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ntt-at.com Subject: [BLISS] Another WG last call on "Call Completion" X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jan 2011 00:22:35 -0000 As a lot of comments were provided on the = draft-ietf-bliss-call-completion=20 during WGLC with many being technical, I am running another WG=20 last call on "Call Completion".=20 =20 This is to announce a second cycle of two week working group last call=20= so please send your comments to the list including nits by the 25th of = January. I especially encourage those that have commented during WGLC to=20 make sure your comments are reflected or addressed in the new=20 version.=20 http://tools.ietf.org/html/draft-ietf-bliss-call-completion-08.txt Regards Shida Schubert (As WG chair)= From Martin.Huelsemann@telekom.de Thu Jan 13 05:50:12 2011 Return-Path: X-Original-To: bliss@core3.amsl.com Delivered-To: bliss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 244C03A6B89 for ; Thu, 13 Jan 2011 05:50:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.505 X-Spam-Level: X-Spam-Status: No, score=-2.505 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x42e58YnMaVF for ; Thu, 13 Jan 2011 05:50:08 -0800 (PST) Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 7EC3B3A6B8A for ; Thu, 13 Jan 2011 05:50:04 -0800 (PST) Received: from he111528.emea1.cds.t-internal.com ([10.125.90.87]) by tcmail81.telekom.de with ESMTP/TLS/AES128-SHA; 13 Jan 2011 14:52:20 +0100 Received: from HE111543.emea1.cds.t-internal.com ([169.254.4.142]) by HE111528.EMEA1.CDS.T-INTERNAL.COM ([2002:7cd:5a57::7cd:5a57]) with mapi; Thu, 13 Jan 2011 14:52:13 +0100 From: To: Date: Thu, 13 Jan 2011 14:52:12 +0100 Thread-Topic: AW: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 Thread-Index: AcumrBdP1d8NrH0XTaqGPW/I/s6DuAMfDfYQ Message-ID: <9762ACF04FA26B4388476841256BDE0201139BE6806E@HE111543.emea1.cds.t-internal.com> References: <46705063-0A81-4DE5-927A-C74FC13AF6C9@agnada.com> <101C6067BEC68246B0C3F6843BCCC1E307DE1D0102@MCHP058A.global-ad.net> <101C6067BEC68246B0C3F6843BCCC1E307E07C1013@MCHP058A.global-ad.net> <4CE95289.9090405@digium.com> <9762ACF04FA26B4388476841256BDE0201127D06BA87@HE111543.emea1.cds.t-internal.com> <4D1A0FDD.6070908@digium.com> In-Reply-To: <4D1A0FDD.6070908@digium.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: bliss@ietf.org, R.Jesske@telekom.de Subject: Re: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2011 13:50:12 -0000 Hi Kevin, for me it's okay to remove the example. What about the example in the last sentence of the next paragraph? "E.g., the call may have connected to the callee's voicemail, which would return a 200 status to the INVITE but from the caller's point of view is "no reply"." Regards, Martin > -----Urspr=FCngliche Nachricht----- > Von: Kevin P. Fleming [mailto:kpfleming@digium.com] > Gesendet: Dienstag, 28. Dezember 2010 17:27 > An: H=FClsemann, Martin > Cc: andrew.hutton@siemens-enterprise.com; bliss@ietf.org > Betreff: Re: AW: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 > > On 12/27/2010 09:29 AM, Martin.Huelsemann@telekom.de wrote: > > Hi, > > > > I tried to rephrase it: > > > > > > "The caller's UA sends an INVITE to a request URI. One or > more forks of this request reach one or more of the callee's > UAs. If the call-completion feature is available, the > callee's monitor (note there can be a monitor for each of the > callee's UAs) inserts a Call-Info header with its URI and > with "purpose=3Dcall-completion" in appropriate non-100 > provisional or final response messages to the initial INVITE > and forwards them to the caller. On receipt of a non-100 > provisional or a final response with the indication that the > call-completion feature is available, the calling user can > invoke the feature. The reason for invoking usually is a > situation where the INVITE fails and the resulting dialog(s) > are terminated, or a 200 OK to the INVITE was received from > some other UA (e.g. the callee's voicemail)." > > This looks much better to me, all except the last sentence. > > I'm not sure we need an example of why a user might wish to > invoke call completion services at this point in the > document; the rationale for this entire set of services is > spelled out earlier in the document, and providing an example > like this sometimes results in implementors incorrectly > assuming that invoking the services as a result of other > circumstances is not allowed by the RFC. > > If we do leave the example in, I'd prefer it to be worded > like this, though: > > =3D=3D=3D=3D > Frequently, the call-completion feature will be invoked by > the caller (by requesting that their UA do so) when the > initial INVITE did not result in a session being established > with the callee. This could occur if all of the callee's UAs > respond with failure responses (4xx or 5xx response codes), > or even if one of the callee's UAs responds with a '200 OK' > but that UA does not actually connect the caller to the > callee (a voicemail system, for example). > =3D=3D=3D=3D > > It isn't possible for 'some other UA' to respond with a 200 > OK to the INVITE; the only UAs that can respond to the INVITE > are those that are included in the set of "callee's UAs" as > defined earlier in the paragraph. Another UA could become > involved if one of the callee's UAs responds with a 302, but > I don't think you want to complicate this text with trying to > accommodate that example. > > > > > > > > > Regards, Martin > > > > > > > > > > > > > >> -----Urspr=FCngliche Nachricht----- > >> Von: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org] Im > >> Auftrag von Kevin P. Fleming > >> Gesendet: Sonntag, 21. November 2010 18:11 > >> An: bliss@ietf.org > >> Betreff: Re: [BLISS] WGLC for draft-ietf-bliss-call-completion-07 > >> > >> On 11/09/2010 08:13 PM, Hutton, Andrew wrote: > >>> Hi Martin, > >>> > >>> See below. > >>> > >>> Regards > >>> Andy > >>> > >>>>> Hi, > >>>>> > >>>>> The following comments are based on feedback I obtained > from some > >>>>> developers. Sorry that they are sent last minute. > >>>>> > >>>>> 1. Section 4.2 "Call-Completion procedures" (1st > Para.). The text > >>>>> indicates that call completion procedures are not > required if the > >>>>> callee's UAs return a success response. This is > incorrect and in > >>>>> conflict with the definition of "Failed Call" in the > definitions. > >>>>> The requirement for call completion is independent of the > >>>>> success/failure of the SIP INVITE request. > >>>>> > >>>>> > >>>>> 2. Section 4.2. (2nd para.) Again it is implied that the call > >>>>> completion procedures seems tied to the state of the preceding > >>>>> INVITE initiated dialog with the statement "Eventually, > >> the INVITE > >>>>> fails, or the resulting dialog(s) are terminated". > >> However it is not > >>>>> the case that the call completion procedures are > >> independent of the > >>>>> state any proceeding dialog. For example it should be > possible to > >>>>> initiate call completion even before the original INVITE > >> dialog is > >>>>> terminated. > >>>> > >>>> I've tried to combine the 2 paragrapgs: > >>>> > >>>> "The caller's UA sends an INVITE to a request URI. One or > >> more forks > >>>> of this request reach one or more of the callee's UAs. > >> However there > >>>> might be the situation that the calling user considers the > >> result of > >>>> the call insufficient to satisfy his needs, e.g. the > >> INVITE fails and > >>>> the resulting dialog(s) are terminated, or the INVITE > >> might succeed > >>>> at some other UA." > >>>> > >>> > >>> [AndyHutton] - I think it needs to be made clear that the > >> SUBSCRIBE for call completion can be initiated whatever > the state of > >> the original INVITE dialog. For example a 180 or 200OK > response could > >> be received to the original INVITE request and the user decides to > >> invoke call completion before terminating the INVITE > dialog. Maybe a > >> statement to this effect could be made in section 4.2 > and/or section > >> 6.2. > >> > >> I agree. When the UAS sends any response that includes the > >> call-completion information, the UAC is free to SUBSCRIBE for call > >> completion services. > >> > >> -- > >> Kevin P. Fleming > >> Digium, Inc. | Director of Software Technologies > >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > >> skype: kpfleming | jabber: kfleming@digium.com Check us out at > >> www.digium.com& www.asterisk.org > >> _______________________________________________ > >> BLISS mailing list > >> BLISS@ietf.org > >> https://www.ietf.org/mailman/listinfo/bliss > >> > > > -- > Kevin P. Fleming > Digium, Inc. | Director of Software Technologies > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > skype: kpfleming | jabber: kfleming@digium.com Check us out > at www.digium.com & www.asterisk.org > From shida@ntt-at.com Mon Jan 24 05:00:09 2011 Return-Path: X-Original-To: bliss@core3.amsl.com Delivered-To: bliss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5D153A6845 for ; Mon, 24 Jan 2011 05:00:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.335 X-Spam-Level: X-Spam-Status: No, score=-101.335 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cQxZFxFaTmJl for ; Mon, 24 Jan 2011 05:00:09 -0800 (PST) Received: from gateway03.websitewelcome.com (gateway03.websitewelcome.com [69.41.248.28]) by core3.amsl.com (Postfix) with SMTP id 174533A6839 for ; Mon, 24 Jan 2011 05:00:09 -0800 (PST) Received: (qmail 24617 invoked from network); 24 Jan 2011 13:01:59 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway03.websitewelcome.com with SMTP; 24 Jan 2011 13:01:59 -0000 Received: from [60.237.173.240] (port=57949 helo=[192.168.1.10]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1PhM4R-0003oa-3B for bliss@ietf.org; Mon, 24 Jan 2011 07:02:59 -0600 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1082) From: Shida Schubert In-Reply-To: Date: Mon, 24 Jan 2011 22:02:50 +0900 Content-Transfer-Encoding: 7bit Message-Id: <36056508-E30C-40A2-86D7-1B9BA8692ED2@ntt-at.com> References: To: BLISS X-Mailer: Apple Mail (2.1082) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator465.hostgator.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ntt-at.com Subject: [BLISS] WGLC for Call Completion ending in few days X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 13:00:09 -0000 I am sending this e-mail to remind people that WGLC for call completion is ending in few days. I highly encourage those who commented during the first cycle of WGLC to make sure comments provided are reflected in the latest version of the draft. Regards Shida (As chair) From shida@ntt-at.com Fri Jan 28 23:44:22 2011 Return-Path: X-Original-To: bliss@core3.amsl.com Delivered-To: bliss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FF323A6895 for ; Fri, 28 Jan 2011 23:44:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.265 X-Spam-Level: X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rml4JCKHRd8 for ; Fri, 28 Jan 2011 23:44:21 -0800 (PST) Received: from gateway16.websitewelcome.com (gateway16.websitewelcome.com [67.18.21.17]) by core3.amsl.com (Postfix) with SMTP id 8FEE03A6977 for ; Fri, 28 Jan 2011 23:44:20 -0800 (PST) Received: (qmail 2428 invoked from network); 29 Jan 2011 07:46:55 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway16.websitewelcome.com with SMTP; 29 Jan 2011 07:46:55 -0000 Received: from [122.133.78.228] (port=53813 helo=[192.168.1.10]) by gator465.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1Pj5WZ-0000nh-Cx for bliss@ietf.org; Sat, 29 Jan 2011 01:47:12 -0600 From: Shida Schubert Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: Sat, 29 Jan 2011 16:47:26 +0900 Message-Id: <038FC578-F801-4215-B022-C907854BAF80@ntt-at.com> To: BLISS Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator465.hostgator.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ntt-at.com Subject: [BLISS] Conference Announcement - SIP Network Operators X-BeenThere: bliss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jan 2011 07:44:22 -0000 [as chair: This appeared relevant - so I have forwarded] The SIP Forum is holding its first SIP Network Operators Conference = (SIPNOC) on April 25th to the 27th, 2011, at the Hyatt Dulles Hotel in = Herndon, Virginia =96 a few minutes from Dulles International Airport.=20= SIPNOC is a technical conference developed for service providers and = carriers to gather and discuss the challenges of deploying and = implementing SIP-based communications technology, and to share the = best-practices and strategies that enable the successful and profitable = operation of SIP-based services and applications in fixed and mobile IP = network environments. Unlike other events, this conference is for SIP = network operations personnel, such as NOC engineers, rather than a = high-level conference for executives. For more information about SIPNOC, including the preliminary schedule of = events and other important details about the conference, please visit = http://www.sipnoc.org. The SIPNOC Program Committee is seeking proposals for presentations, = panels, or BOFs (Birds-Of-a-Feather sessions) for the SIPNOC 2011 = program. We invite presentations highlighting issues relating to SIP = network deployments. Operators are encouraged to present on successes, = issues, and concerns found in their deployments. Vendors are encouraged = to work with operators to present real-world deployment experiences. The deadline for submission of presentation/paper abstracts and draft = slides is February 21, 2011. Full details of the submission process and policies, as well as other = SIPNOC 2011 dates of interest, can be found at: http://www.sipforum.org/content/view/374/275/ I look forward to seeing you at the event! Best Wishes, Eric Burger SIPNOC Chair_______________________________________________ sip-clf mailing list sip-clf@ietf.org https://www.ietf.org/mailman/listinfo/sip-clf=