[dispatch] Requesting DISPATCH advice on draft-haluska-sipping-directory-assistance-09
"Haluska, John J" <jhaluska@telcordia.com> Mon, 26 October 2009 20:08 UTC
Return-Path: <jhaluska@telcordia.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C532328C35E for <dispatch@core3.amsl.com>; Mon, 26 Oct 2009 13:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 2B9EbCMZ2T4b for <dispatch@core3.amsl.com>; Mon, 26 Oct 2009 13:08:08 -0700 (PDT)
Received: from dnsmx1rrc.telcordia.com (dnsmx1rrc.telcordia.com [128.96.20.41]) by core3.amsl.com (Postfix) with ESMTP id 7912628C377 for <dispatch@ietf.org>; Mon, 26 Oct 2009 13:08:07 -0700 (PDT)
Received: from rrc-dte-ieg01.dte.telcordia.com (rrc-dte-ieg01.cc.telcordia.com [128.96.20.22]) by dnsmx1rrc.telcordia.com (8.13.8+Sun/8.13.8) with ESMTP id n9QK8Kdg000859 for <dispatch@ietf.org>; Mon, 26 Oct 2009 16:08:20 -0400 (EDT)
X-AuditID: 80601416-0000111400000554-3b-4ae601b02939
Received: from rrc-dte-exhb1.dte.telcordia.com ([128.96.20.12]) by rrc-dte-ieg01.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 26 Oct 2009 16:08:16 -0400
Received: from rrc-dte-exmb2.dte.telcordia.com ([128.96.180.27]) by rrc-dte-exhb1.dte.telcordia.com ([128.96.20.12]) with mapi; Mon, 26 Oct 2009 16:08:17 -0400
From: "Haluska, John J" <jhaluska@telcordia.com>
To: "dispatch@ietf.org" <dispatch@ietf.org>
Date: Mon, 26 Oct 2009 16:08:15 -0400
Thread-Topic: Requesting DISPATCH advice on draft-haluska-sipping-directory-assistance-09
Thread-Index: AcpWeA2WBVek9ZpOQ0qn5vfnJxC+pA==
Message-ID: <8B6A9EC265011E4CB70F99C64426E8C205388882DD@rrc-dte-exmb2.dte.telcordia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8B6A9EC265011E4CB70F99C64426E8C205388882DDrrcdteexmb2dt_"
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: "Haluska, John J" <jhaluska@telcordia.com>, "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
Subject: [dispatch] Requesting DISPATCH advice on draft-haluska-sipping-directory-assistance-09
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2009 20:08:15 -0000
Hello All, We've been discussing with Cullen an AD-sponsored path for draft-haluska-sipping-directory-assistance. Having received an extensive review from Spencer Dawkins (thanks Spencer), one comment was that we should consider breaking up the 100+ page document into several more manageable documents, potentially organized into e.g., - a description of the services - a description of standards gaps - a set of call flows - a set of best current practices Cullen suggested that we talk to the DISPATCH working group to see what kind of split makes sense, he was thinking that possibly some material (e.g., protocol gaps) might have the potential to become the basis of future work in DISPATCH or other working groups. We'd definitely appreciate any advice on this from the DISPATCH working group. A pointer to the announcement for the latest revision (-09) of the document is provided below. Again the input we're looking for is advice on splitting up the document. Thanks much, John Haluska = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D Action:draft-haluska-sipping-directory-assistance-09.txt X-RSN: 1/0/935/27107/30454 X-HREF: http://www.ietf.org/ibin/c5i?mid=6&rid=49&k1=935&k2=30454 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Considerations for Information Services and Operator Services Using SIP Author(s) : J. Haluska, et al. Filename : draft-haluska-sipping-directory-assistance-09.txt Pages : 109 Date : 2009-10-23 Information Services are services whereby information is provided in response to user requests, and may include involvement of a human or automated agent. A popular existing Information Service is Directory Assistance (DA). Moving ahead, Information Services providers envision exciting multimedia services that support simultaneous voice and data interactions with full operator backup at any time during the call. Information Services providers are planning to migrate to SIP based platforms, which will enable such advanced services, while continuing to support traditional DA services. Operator Services are traditional PSTN services which often involve providing human or automated assistance to a caller, and often require the specialized capabilities traditionally provided by an operator services switch. Market and/or regulatory factors in some jurisdictions dictate that some subset of Operator Services continue to be provided going forward. This document aims to identify how Operator and Information Services can be implemented using existing or currently proposed SIP mechanisms, to identity existing protocol gaps, and to provide a set of Best Current Practices to facilitate interoperability. For Operator Services, the intention is to describe how current operator services can continue to be provided to PSTN based subscribers via a SIP based operator services architecture. It also looks at how current operator services might be provided to SIP based subscribers via such an architecture, but does not consider the larger question of the need for or usefulness or suitability of each of these services for SIP based subscribers. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-haluska-sipping-directory-assistance-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. _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ***** Click below to download the attachment(s) in this message: Attachment: draft_haluska_sipping_directory_assistance_09.txt<http://www.ietf.org/bin/c5i?mid=6&gid=0&rid=8&k1=935&file=i-d-announce.30454.1.txt> (1K)
- [dispatch] Requesting DISPATCH advice on draft-ha… Haluska, John J
- Re: [dispatch] Requesting DISPATCH advice on draf… Paul Kyzivat
- Re: [dispatch] Requesting DISPATCH advice on draf… Spencer Dawkins
- Re: [dispatch] Requesting DISPATCH advice on draf… Cullen Jennings