From rjsparks@nostrum.com Wed Oct 14 13:48:01 2009 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 883123A6918 for ; Wed, 14 Oct 2009 13:48:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.312 X-Spam-Level: X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, SPF_PASS=-0.001] 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 d9nVQnglm2AU for ; Wed, 14 Oct 2009 13:48:00 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 7F3D13A6882 for ; Wed, 14 Oct 2009 13:48:00 -0700 (PDT) Received: from dn3-232.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id n9EKlsoX031798 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Oct 2009 15:47:58 -0500 (CDT) (envelope-from rjsparks@nostrum.com) Message-Id: From: Robert Sparks To: bliss@ietf.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Wed, 14 Oct 2009 15:47:53 -0500 References: X-Mailer: Apple Mail (2.936) Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism) Cc: Jason Fischl Subject: [BLISS] BLISS co-chair changes 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: Wed, 14 Oct 2009 20:48:01 -0000 As mentioned earlier, Jason Fischl has stepped down as BLISS co-chair. Please join me in thanking him for the effort he's put into the group's progress since it was formed. Scott Lawrence has joined Shida as co-chair. Please welcome him to the role. RjS From root@core3.amsl.com Wed Oct 14 14:15:01 2009 Return-Path: X-Original-To: bliss@ietf.org Delivered-To: bliss@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id B66D93A6966; Wed, 14 Oct 2009 14:15:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20091014211501.B66D93A6966@core3.amsl.com> Date: Wed, 14 Oct 2009 14:15:01 -0700 (PDT) Cc: bliss@ietf.org Subject: [BLISS] I-D Action:draft-ietf-bliss-call-park-extension-01.txt 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: Wed, 14 Oct 2009 21:15:01 -0000 --NextPart 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 : Implementing Call Park and Retrieve using the Session Initiation Protocol (SIP) Author(s) : M. Procter Filename : draft-ietf-bliss-call-park-extension-01.txt Pages : 19 Date : 2009-10-14 Call Park and Call Retrieve are useful telephony services that are familiar to many users. Existing implementations using the Session Initiation Protocol (SIP) show that a variety of approaches can be Taken, with varying degrees of interoperability. This draft discusses a number of feature variations, and how they may be implemented using existing techniques. An additional URI parameter is also described, which enables further common use-cases to be implemented. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bliss-call-park-extension-01.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. --NextPart Content-Type: Message/External-body; name="draft-ietf-bliss-call-park-extension-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-10-14140134.I-D@ietf.org> --NextPart-- From shida@ntt-at.com Sun Oct 18 19:17:35 2009 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 EA7FB3A6971 for ; Sun, 18 Oct 2009 19:17:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.058 X-Spam-Level: X-Spam-Status: No, score=-1.058 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_40=-0.185, IP_NOT_FRIENDLY=0.334] 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 gWJnQPK+Gn0R for ; Sun, 18 Oct 2009 19:17:35 -0700 (PDT) Received: from gateway01.websitewelcome.com (gateway01.websitewelcome.com [69.93.126.19]) by core3.amsl.com (Postfix) with SMTP id 2FEA23A68FF for ; Sun, 18 Oct 2009 19:17:35 -0700 (PDT) Received: (qmail 13472 invoked from network); 19 Oct 2009 02:27:48 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway01.websitewelcome.com with SMTP; 19 Oct 2009 02:27:48 -0000 Received: from fl1-122-135-49-232.tky.mesh.ad.jp ([122.135.49.232]:49571 helo=[192.168.1.4]) by gator465.hostgator.com with esmtpa (Exim 4.69) (envelope-from ) id 1MzhoY-0002tr-5C for bliss@ietf.org; Sun, 18 Oct 2009 21:17:38 -0500 From: Shida Schubert Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 19 Oct 2009 11:17:39 +0900 Message-Id: <5536A111-64D5-4976-A94B-4B36EEE0B737@ntt-at.com> To: bliss@ietf.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) 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] Requests for Agenda Time 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, 19 Oct 2009 02:17:36 -0000 All, The 76th IETF meeting is coming up in 3 weeks. We have requested 1 hour for Hiroshima. If you would like a slot on the agenda for Hiroshima, please let Scott and I know as soon as possible. Regards Shida From L.Liess@telekom.de Mon Oct 19 05:38:57 2009 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 1B39F3A6997; Mon, 19 Oct 2009 05:38:57 -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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GXzLTXqDLTJx; Mon, 19 Oct 2009 05:38:56 -0700 (PDT) Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 97FB73A6887; Mon, 19 Oct 2009 05:38:54 -0700 (PDT) Received: from s4de9jsaano.mgb.telekom.de (HELO S4DE9JSAANO.ost.t-com.de) ([10.125.177.105]) by tcmail81.telekom.de with ESMTP; 19 Oct 2009 14:38:56 +0200 Received: from S4DE9JSAANI.ost.t-com.de ([10.125.177.223]) by S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Oct 2009 14:38:55 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 19 Oct 2009 14:38:54 +0200 Message-ID: <40FB0FFB97588246A1BEFB05759DC8A0038854EC@S4DE9JSAANI.ost.t-com.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New version for the Alert-Info URNs draft: draft-liess-dispatch-alert-info-urns-00.txt Thread-Index: AcpQq3YunVR8UxnZT5+ec/k+hRAeoQAAZzpQ From: To: , X-OriginalArrivalTime: 19 Oct 2009 12:38:55.0465 (UTC) FILETIME=[1F1D0D90:01CA50B9] Cc: anwars@avaya.com, Gonzalo.Camarillo@ericsson.com, R.Jesske@telekom.de Subject: [BLISS] New version for the Alert-Info URNs draft: draft-liess-dispatch-alert-info-urns-00.txt 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, 19 Oct 2009 12:38:57 -0000 =20 Hi, We've re-submitted the Alert-Info URNs draft for DISPATCH http://www.ietf.org/internet-drafts/draft-liess-dispatch-alert-info-urns -00.txt . (The previous version od the draft was in BLISS and we had a presentation in BLISS at the last IETF.) We did some major changes, as suggested on the mailing list, e.g.: Added: =20 - Description of the interoperability problems for PBX-services (in the Introduction chapter)=20 - Requirements for the Alert-Info URNs mechanism=20 - Alert-Info URNs Indications for country-specific tones Changed:=20 - Initial IANA Registration mechanism to avoid combinatorial explosion of IANA values.=20 Many thanks for the comments and suggestions, Laura=20 =20 -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, October 19, 2009 1:00 PM To: i-d-announce@ietf.org Subject: I-D Action:draft-liess-dispatch-alert-info-urns-00.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Alert-Info URNs for the Session Initiation Protocol (SIP) Author(s) : D. Alexeitsev, et al. Filename : draft-liess-dispatch-alert-info-urns-00.txt Pages : 25 Date : 2009-10-19 The Session Initiation Protocol (SIP) supports the capability to provide a reference to the alternative ringback tone (RBT) for caller, or ring tone (RT) for callee using the Alert-Info header. However, the reference addresses only the network resources with specific rendering properties. There is currently no support for predefined standard identifiers for ringback tones or semantic indications without tied rendering. To overcome this limitations and support new applications a family of the URNs is defined in this specification. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-liess-dispatch-alert-info-urns -00.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. From root@core3.amsl.com Mon Oct 19 05:45:01 2009 Return-Path: X-Original-To: bliss@ietf.org Delivered-To: bliss@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id B2D963A69A0; Mon, 19 Oct 2009 05:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20091019124501.B2D963A69A0@core3.amsl.com> Date: Mon, 19 Oct 2009 05:45:01 -0700 (PDT) Cc: bliss@ietf.org Subject: [BLISS] I-D Action:draft-ietf-bliss-ach-analysis-05.txt 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, 19 Oct 2009 12:45:01 -0000 --NextPart 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 : An Analysis of Automatic Call Handling Implementation Issues in the Session Initiation Protocol (SIP) Author(s) : J. Elwell Filename : draft-ietf-bliss-ach-analysis-05.txt Pages : 19 Date : 2009-10-19 This discusses problems associated with automatic call handling (ACH) when using the Session Initiation Protocol (SIP) and specifies some best practices to help achieve interoperability. This work is being discussed on the bliss@ietf.org mailing list. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bliss-ach-analysis-05.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. --NextPart Content-Type: Message/External-body; name="draft-ietf-bliss-ach-analysis-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-10-19054256.I-D@ietf.org> --NextPart-- From john.elwell@siemens-enterprise.com Mon Oct 19 05:51:30 2009 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 A471828C120 for ; Mon, 19 Oct 2009 05:51:30 -0700 (PDT) X-Quarantine-ID: X-Virus-Scanned: amavisd-new at amsl.com X-Amavis-Alert: BAD HEADER, MIME error: error: illegal encoding [base64] for MIME type message/external-body X-Spam-Flag: NO X-Spam-Score: -5.735 X-Spam-Level: X-Spam-Status: No, score=-5.735 tagged_above=-999 required=5 tests=[AWL=0.514, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4] 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 Vrrd06HFVqVk for ; Mon, 19 Oct 2009 05:51:29 -0700 (PDT) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by core3.amsl.com (Postfix) with ESMTP id 7B6723A69A4 for ; Mon, 19 Oct 2009 05:51:29 -0700 (PDT) Received: from mail2.siemens.de (localhost [127.0.0.1]) by david.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id n9JCpZTM006068 for ; Mon, 19 Oct 2009 14:51:35 +0200 Received: from DEMCHP99ET3MSX.ww902.siemens.net ([139.25.131.243]) by mail2.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id n9JCpZ2m028676 for ; Mon, 19 Oct 2009 14:51:35 +0200 Received: from DEMCHP99E35MSX.ww902.siemens.net ([169.254.2.61]) by DEMCHP99ET3MSX.ww902.siemens.net ([139.25.131.243]) with mapi; Mon, 19 Oct 2009 14:51:34 +0200 From: "Elwell, John" To: "bliss@ietf.org" Date: Mon, 19 Oct 2009 14:51:16 +0200 Thread-Topic: [BLISS] I-D Action:draft-ietf-bliss-ach-analysis-05.txt Thread-Index: AcpQukbLYfUfYvm8QzWrE0S+GK3mfwAADz8g Message-ID: <7402509E63C5A145A6095D46C179A5B71477DE46@DEMCHP99E35MSX.ww902.siemens.net> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: multipart/mixed; boundary="_003_7402509E63C5A145A6095D46C179A5B71477DE46DEMCHP99E35MSXw_" MIME-Version: 1.0 Subject: [BLISS] FW: I-D Action:draft-ietf-bliss-ach-analysis-05.txt 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, 19 Oct 2009 12:51:30 -0000 --_003_7402509E63C5A145A6095D46C179A5B71477DE46DEMCHP99E35MSXw_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The reason for this new version is solely because the old one had expired. = It still awaits draft-ietf references to replace the draft-roach and draft-= griffin references, before it can be progressed. John=20 > -----Original Message----- > From: bliss-bounces@ietf.org [mailto:bliss-bounces@ietf.org]=20 > On Behalf Of Internet-Drafts@ietf.org > Sent: 19 October 2009 13:45 > To: i-d-announce@ietf.org > Cc: bliss@ietf.org > Subject: [BLISS] I-D Action:draft-ietf-bliss-ach-analysis-05.txt >=20 > A New Internet-Draft is available from the on-line=20 > Internet-Drafts directories. > This draft is a work item of the Basic Level of=20 > Interoperability for SIP Services Working Group of the IETF. >=20 >=20 > Title : An Analysis of Automatic Call=20 > Handling Implementation Issues in the Session Initiation=20 > Protocol (SIP) > Author(s) : J. Elwell > Filename : draft-ietf-bliss-ach-analysis-05.txt > Pages : 19 > Date : 2009-10-19 >=20 > This discusses problems associated with automatic call handling (ACH) > when using the Session Initiation Protocol (SIP) and specifies some > best practices to help achieve interoperability. >=20 > This work is being discussed on the bliss@ietf.org mailing list. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-bliss-ach-analy > sis-05.txt >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > = --_003_7402509E63C5A145A6095D46C179A5B71477DE46DEMCHP99E35MSXw_ Content-Type: message/external-body; name="draft-ietf-bliss-ach-analysis-05.url" Content-Description: draft-ietf-bliss-ach-analysis-05.url Content-Disposition: attachment; filename="draft-ietf-bliss-ach-analysis-05.url"; size=97; creation-date="Mon, 19 Oct 2009 14:47:11 GMT"; modification-date="Mon, 19 Oct 2009 14:47:11 GMT" Content-Transfer-Encoding: base64 W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1pZXRmLWJsaXNzLWFjaC1hbmFseXNpcy0wNS50eHQNCg== --_003_7402509E63C5A145A6095D46C179A5B71477DE46DEMCHP99E35MSXw_ Content-Type: text/plain; name="ATT00001.txt" Content-Description: ATT00001.txt Content-Disposition: attachment; filename="ATT00001.txt"; size=130; creation-date="Mon, 19 Oct 2009 14:47:11 GMT"; modification-date="Mon, 19 Oct 2009 14:47:11 GMT" Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkJMSVNTIG1h aWxpbmcgbGlzdA0KQkxJU1NAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v bGlzdGluZm8vYmxpc3MNCg== --_003_7402509E63C5A145A6095D46C179A5B71477DE46DEMCHP99E35MSXw_-- From Fred_Stacey@Mitel.com Mon Oct 19 09:41:33 2009 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 00C1F3A6853 for ; Mon, 19 Oct 2009 09:41:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] 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 pyqDKullo8cX for ; Mon, 19 Oct 2009 09:41:32 -0700 (PDT) Received: from smtp.mitel.com (smtp.mitel.com [216.191.234.102]) by core3.amsl.com (Postfix) with ESMTP id E13673A677E for ; Mon, 19 Oct 2009 09:41:31 -0700 (PDT) Received: from localhost (smtp.mitel.com [127.0.0.1]) by smtp.mitel.com (Postfix) with ESMTP id C3E5A2C024 for ; Mon, 19 Oct 2009 12:41:38 -0400 (EDT) X-Virus-Scanned: by amavisd-new (virusonly) at mitel.com Received: from smtp.mitel.com ([127.0.0.1]) by localhost (smtp.mitel.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6RQYipnprrk for ; Mon, 19 Oct 2009 12:41:38 -0400 (EDT) Received: from ottlnmta.mitel.com (ottlnmta.mitel.com [10.44.16.150]) by smtp.mitel.com (Postfix) with ESMTP id 47D842C027 for ; Mon, 19 Oct 2009 12:41:38 -0400 (EDT) From: Fred_Stacey@Mitel.com To: bliss@ietf.org Message-ID: Date: Mon, 19 Oct 2009 12:41:12 -0400 X-MIMETrack: Serialize by Router on OTTLNMTA/Mitel(Release 6.5.6FP3|March 27, 2008) at 10/19/2009 12:41:38 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: [BLISS] Fred Stacey is out of the office. 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, 19 Oct 2009 16:41:33 -0000 I will be out of the office starting 10/19/2009 and will not return until 10/26/2009. I will be travelling on business for the week of Oct 19. For Sun Microsystems related issues, please contact Arnaud Bellens For 5560 IPT related issues, please contact Simon Binder Otherwise, if the matter is of an urgent nature, please contact Stephen Bray or Tim Kostyniuk From pkyzivat@cisco.com Mon Oct 19 13:44:08 2009 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 8DA8B3A6933; Mon, 19 Oct 2009 13:44:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.428 X-Spam-Level: X-Spam-Status: No, score=-6.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] 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 E1ub6bAJBiAE; Mon, 19 Oct 2009 13:44:07 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id C093C3A6975; Mon, 19 Oct 2009 13:44:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=4619; q=dns/txt; s=rtpiport02001; t=1255985054; x=1257194654; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Paul=20Kyzivat=20|Subject: =20Re:=20[dispatch]=20New=20version=20for=20the=20Alert-I nfo=20URNs=20draft:=09draft-liess-dispatch-alert-info-urn s-00.txt|Date:=20Mon,=2019=20Oct=202009=2016:44:03=20-040 0|Message-ID:=20<4ADCCF93.2070208@cisco.com>|To:=20L.Lies s@telekom.de|CC:=20dispatch@ietf.org,=20bliss@ietf.org, =20anwars@avaya.com,=20R.Jesske@telekom.de|MIME-Version: =201.0|Content-Transfer-Encoding:=207bit|In-Reply-To:=20< 40FB0FFB97588246A1BEFB05759DC8A0038854EC@S4DE9JSAANI.ost. t-com.de>|References:=20<40FB0FFB97588246A1BEFB05759DC8A0 038854EC@S4DE9JSAANI.ost.t-com.de>; bh=fupIlR0ByZHkOMTN6/M1E/nSm5T+7SlnyUaMQkPoNK4=; b=Q8CsLiesp0bkzOnW8sIUfUywg7pCFZgwpWPWVvILSQjCIByueuhZQ0T1 ql2gFx2nb1BLtjvvYXLEQWTquyPdUHUWdvXRw4xPKxkKoMZEOuAWBpW+P 9PAT/4bNlsu5fkboDwBvdHwSSjpW/hDRIV4t4XQ2pFwuS+yHlLo0V80pP M=; Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAPdr3EqtJV2b/2dsb2JhbADDX5cYgjmBeAQ X-IronPort-AV: E=Sophos;i="4.44,587,1249257600"; d="scan'208";a="63854079" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-2.cisco.com with ESMTP; 19 Oct 2009 20:44:13 +0000 Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id n9JKi7hd031437; Mon, 19 Oct 2009 20:44:13 GMT Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Oct 2009 16:44:11 -0400 Received: from [161.44.174.156] ([161.44.174.156]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Oct 2009 16:44:11 -0400 Message-ID: <4ADCCF93.2070208@cisco.com> Date: Mon, 19 Oct 2009 16:44:03 -0400 From: Paul Kyzivat User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: L.Liess@telekom.de References: <40FB0FFB97588246A1BEFB05759DC8A0038854EC@S4DE9JSAANI.ost.t-com.de> In-Reply-To: <40FB0FFB97588246A1BEFB05759DC8A0038854EC@S4DE9JSAANI.ost.t-com.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Oct 2009 20:44:11.0300 (UTC) FILETIME=[E980E640:01CA50FC] Cc: bliss@ietf.org, dispatch@ietf.org, R.Jesske@telekom.de, anwars@avaya.com Subject: Re: [BLISS] [dispatch] New version for the Alert-Info URNs draft: draft-liess-dispatch-alert-info-urns-00.txt 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, 19 Oct 2009 20:44:08 -0000 This seems to be shaping up well. I think the requirements are quite clear now. I don't fully understand what is intended regarding combination of multiple alert URNs for a specific situation. Section 4.5 states: > finally, a short Albanian auto-callback tone could be indicated > Alert-Info: , > , . while section 7.3.6 states: > Alert URN Indications from the same group should not be combined. I could find no definition of what constitutes a "group". The first thing that comes to mind is "service" vs. "tone", but the above example violates that. It seems to me that you need some notion of orthogonal properties in order to define what can/cannot be combined. It would be good to have more detail about how a recipient should deal with multiple URNs. I'm also uncertain of what your intent is regarding top-level vs. additional indications. As specified, I believe a given "additional indication" name is always defined with regard to its parent, so that "short" as used in "normal.short" might mean something entirely different than "priority.short", or might not be defined for priority at all. Yet from the registration text in 7.3.2 it sounds like the intent is for priority, short, and delayed to be defined for all pbx-tones. If that is the intent, then I don't think the existing text meets that intent. I also wonder if the existing hierarchy will work well in practice, or if some other organization might not work better. For instance, it might be more convenient to specify ringing.fr with the clear understanding that if you don't know about ringing.fr you can just treat it as ringing. I'm also confused by PBX tones vs. Public telephone tones. In what way is "normal" different from "ringing"? I would think that PBX tones would be a superset of common pstn tones. A nit: in 4.3.2 I would expext the forward to be indicated, if at all, with a 181 rather than a 180. Thanks, Paul L.Liess@telekom.de wrote: > > Hi, > > We've re-submitted the Alert-Info URNs draft for DISPATCH > http://www.ietf.org/internet-drafts/draft-liess-dispatch-alert-info-urns > -00.txt . (The previous version od the draft was in BLISS and we had a > presentation in BLISS at the last IETF.) > > We did some major changes, as suggested on the mailing list, e.g.: > Added: > - Description of the interoperability problems for PBX-services (in > the Introduction chapter) > - Requirements for the Alert-Info URNs mechanism > - Alert-Info URNs Indications for country-specific tones > Changed: > - Initial IANA Registration mechanism to avoid combinatorial explosion > of IANA values. > > > Many thanks for the comments and suggestions, > Laura > > > > > > -----Original Message----- > From: i-d-announce-bounces@ietf.org > [mailto:i-d-announce-bounces@ietf.org] On Behalf Of > Internet-Drafts@ietf.org > Sent: Monday, October 19, 2009 1:00 PM > To: i-d-announce@ietf.org > Subject: I-D Action:draft-liess-dispatch-alert-info-urns-00.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > Title : Alert-Info URNs for the Session Initiation > Protocol (SIP) > Author(s) : D. Alexeitsev, et al. > Filename : draft-liess-dispatch-alert-info-urns-00.txt > Pages : 25 > Date : 2009-10-19 > > The Session Initiation Protocol (SIP) supports the capability to > provide a reference to the alternative ringback tone (RBT) for > caller, or ring tone (RT) for callee using the Alert-Info header. > However, the reference addresses only the network resources with > specific rendering properties. There is currently no support for > predefined standard identifiers for ringback tones or semantic > indications without tied rendering. To overcome this limitations and > support new applications a family of the URNs is defined in this > specification. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-liess-dispatch-alert-info-urns > -00.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. > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > From root@core3.amsl.com Mon Oct 26 07:45:01 2009 Return-Path: X-Original-To: bliss@ietf.org Delivered-To: bliss@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id 84F653A6359; Mon, 26 Oct 2009 07:45:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20091026144501.84F653A6359@core3.amsl.com> Date: Mon, 26 Oct 2009 07:45:01 -0700 (PDT) Cc: bliss@ietf.org Subject: [BLISS] I-D Action:draft-ietf-bliss-shared-appearances-04.txt 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, 26 Oct 2009 14:45:01 -0000 --NextPart 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 : Shared Appearances of a Session Initiation Protocol (SIP) Address of Record (AOR) Author(s) : A. Johnston, et al. Filename : draft-ietf-bliss-shared-appearances-04.txt Pages : 65 Date : 2009-10-26 This document describes the requirements and implementation of a group telephony feature commonly known as Bridged Line Appearance (BLA) or Multiple Line Appearance (MLA), or Shared Call/Line Appearance (SCA). When implemented using the Session Initiation Protocol (SIP), it is referred to as shared appearances of an Address of Record (AOR) since SIP does not have the concept of lines. This feature is commonly offered in IP Centrex services and IP-PBX offerings and is likely to be implemented on SIP IP telephones and SIP feature servers used in a business environment. This document discusses use cases, lists requirements and defines SIP extensions to implement this feature. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-bliss-shared-appearances-04.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. --NextPart Content-Type: Message/External-body; name="draft-ietf-bliss-shared-appearances-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-10-26073555.I-D@ietf.org> --NextPart-- From root@core3.amsl.com Mon Oct 26 08:00:02 2009 Return-Path: X-Original-To: bliss@ietf.org Delivered-To: bliss@core3.amsl.com Received: by core3.amsl.com (Postfix, from userid 0) id F2E303A67CF; Mon, 26 Oct 2009 08:00:01 -0700 (PDT) From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 Message-Id: <20091026150001.F2E303A67CF@core3.amsl.com> Date: Mon, 26 Oct 2009 08:00:01 -0700 (PDT) Cc: bliss@ietf.org Subject: [BLISS] I-D Action:draft-ietf-bliss-call-completion-05.txt 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, 26 Oct 2009 15:00:02 -0000 --NextPart 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-05.txt Pages : 30 Date : 2009-10-26 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 queueing call- completion requests, this document references the usage of the the dialog event package [RFC4235] as described as 'automatic redial' in [RFC5359]. For the realization of a more comprehensive solution with queueing 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-05.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. --NextPart Content-Type: Message/External-body; name="draft-ietf-bliss-call-completion-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2009-10-26075448.I-D@ietf.org> --NextPart-- From shida@ntt-at.com Tue Oct 27 02:33:25 2009 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 3C42B28C1D2 for ; Tue, 27 Oct 2009 02:33:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.662 X-Spam-Level: X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334] 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 VpG6IFM8sZIA for ; Tue, 27 Oct 2009 02:33:24 -0700 (PDT) Received: from gateway14.websitewelcome.com (gateway14.websitewelcome.com [67.18.137.86]) by core3.amsl.com (Postfix) with SMTP id 6EFA73A6A06 for ; Tue, 27 Oct 2009 02:33:24 -0700 (PDT) Received: (qmail 8024 invoked from network); 27 Oct 2009 09:53:44 -0000 Received: from gator465.hostgator.com (69.56.174.130) by gateway14.websitewelcome.com with SMTP; 27 Oct 2009 09:53:44 -0000 Received: from fl1-122-135-49-232.tky.mesh.ad.jp ([122.135.49.232]:53689 helo=[192.168.1.4]) by gator465.hostgator.com with esmtpa (Exim 4.69) (envelope-from ) id 1N2iQr-000719-TV for bliss@ietf.org; Tue, 27 Oct 2009 04:33:38 -0500 From: Shida Schubert Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Date: Tue, 27 Oct 2009 18:33:36 +0900 Message-Id: <749E8EB2-597B-4076-9C58-9F8EC8C94F8E@ntt-at.com> To: bliss@ietf.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) 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 draft-ietf-bliss-shared-appearances 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, 27 Oct 2009 09:33:25 -0000 This mail is to initiate a WGLC on http://tools.ietf.org/id/draft-ietf-bliss-shared-appearances-04.txt Shared Appearances Intended Status: Informational This is a two week working group last call so please send your comments to the list and any nits directly to the editor by the 10th of November. Alan is wanting to discuss any comments that comes up during WGLC at IETF76. Regards Shida Schubert (As WG chair) From alan@sipstation.com Thu Oct 29 06:53:23 2009 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 DB63F3A6AAB; Thu, 29 Oct 2009 06:53:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 1OnRU4rZe97c; Thu, 29 Oct 2009 06:53:22 -0700 (PDT) Received: from mho-01-ewr.mailhop.org (mho-01-ewr.mailhop.org [204.13.248.71]) by core3.amsl.com (Postfix) with ESMTP id 4461A3A6ABE; Thu, 29 Oct 2009 06:53:22 -0700 (PDT) Received: from 24-107-145-15.dhcp.stls.mo.charter.com ([24.107.145.15] helo=aidan-DS.sipserver.homeip.net) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1N3VRY-000NDI-PA; Thu, 29 Oct 2009 13:53:37 +0000 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 24.107.145.15 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/FTsT9OAmwQtvk92kjRUO7cCsDirP1x8s= Message-ID: <4AE99E5E.9090801@sipstation.com> Date: Thu, 29 Oct 2009 08:53:34 -0500 From: Alan Johnston User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Paul Kyzivat References: <40FB0FFB97588246A1BEFB05759DC8A0038854EC@S4DE9JSAANI.ost.t-com.de> <4ADCCF93.2070208@cisco.com> In-Reply-To: <4ADCCF93.2070208@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bliss@ietf.org, dispatch@ietf.org, R.Jesske@telekom.de, L.Liess@telekom.de, anwars@avaya.com Subject: Re: [BLISS] [dispatch] New version for the Alert-Info URNs draft: draft-liess-dispatch-alert-info-urns-00.txt 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, 29 Oct 2009 13:53:24 -0000 Paul, One comment below. Thanks, Alan Paul Kyzivat wrote: > This seems to be shaping up well. I think the requirements are quite > clear now. > > I don't fully understand what is intended regarding combination of > multiple alert URNs for a specific situation. Section 4.5 states: > >> finally, a short Albanian auto-callback tone could be indicated >> Alert-Info: , >> , . > > while section 7.3.6 states: > >> Alert URN Indications from the same group should not be combined. > > I could find no definition of what constitutes a "group". The first > thing that comes to mind is "service" vs. "tone", but the above > example violates that. It seems to me that you need some notion of > orthogonal properties in order to define what can/cannot be combined. > > It would be good to have more detail about how a recipient should deal > with multiple URNs. > > I'm also uncertain of what your intent is regarding top-level vs. > additional indications. As specified, I believe a given "additional > indication" name is always defined with regard to its parent, so that > "short" as used in "normal.short" might mean something entirely > different than "priority.short", or might not be defined for priority > at all. > > Yet from the registration text in 7.3.2 it sounds like the intent is > for priority, short, and delayed to be defined for all pbx-tones. If > that is the intent, then I don't think the existing text meets that > intent. As it has been pointed out, short, long, and delayed are not compatible with the semantic approach of this draft so I think we should remove them as they are currently. I need to investigate to see whether they have been used in the past as stand-ins for a particular service, or whether we need to define specific tones for them. Priority, I still think, is useful - we just need to figure out how to fit it in properly. > > I also wonder if the existing hierarchy will work well in practice, or > if some other organization might not work better. For instance, it > might be more convenient to specify ringing.fr with the clear > understanding that if you don't know about ringing.fr you can just > treat it as ringing. > > I'm also confused by PBX tones vs. Public telephone tones. In what way > is "normal" different from "ringing"? I would think that PBX tones > would be a superset of common pstn tones. > > A nit: in 4.3.2 I would expext the forward to be indicated, if at all, > with a 181 rather than a 180. > > Thanks, > Paul > > L.Liess@telekom.de wrote: >> >> Hi, >> >> We've re-submitted the Alert-Info URNs draft for DISPATCH >> http://www.ietf.org/internet-drafts/draft-liess-dispatch-alert-info-urns >> -00.txt . (The previous version od the draft was in BLISS and we had a >> presentation in BLISS at the last IETF.) >> >> We did some major changes, as suggested on the mailing list, e.g.: >> Added: - Description of the interoperability problems for >> PBX-services (in >> the Introduction chapter) - Requirements for the Alert-Info URNs >> mechanism - Alert-Info URNs Indications for country-specific tones >> Changed: - Initial IANA Registration mechanism to avoid >> combinatorial explosion >> of IANA values. >> >> Many thanks for the comments and suggestions, >> Laura >> >> >> >> -----Original Message----- >> From: i-d-announce-bounces@ietf.org >> [mailto:i-d-announce-bounces@ietf.org] On Behalf Of >> Internet-Drafts@ietf.org >> Sent: Monday, October 19, 2009 1:00 PM >> To: i-d-announce@ietf.org >> Subject: I-D Action:draft-liess-dispatch-alert-info-urns-00.txt >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> >> Title : Alert-Info URNs for the Session Initiation >> Protocol (SIP) >> Author(s) : D. Alexeitsev, et al. >> Filename : draft-liess-dispatch-alert-info-urns-00.txt >> Pages : 25 >> Date : 2009-10-19 >> >> The Session Initiation Protocol (SIP) supports the capability to >> provide a reference to the alternative ringback tone (RBT) for >> caller, or ring tone (RT) for callee using the Alert-Info header. >> However, the reference addresses only the network resources with >> specific rendering properties. There is currently no support for >> predefined standard identifiers for ringback tones or semantic >> indications without tied rendering. To overcome this limitations and >> support new applications a family of the URNs is defined in this >> specification. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-liess-dispatch-alert-info-urns >> -00.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. >> _______________________________________________ >> dispatch mailing list >> dispatch@ietf.org >> https://www.ietf.org/mailman/listinfo/dispatch >> > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >