Re: [Sipping] Comment on draft-haluska-sipping-directory-assistance-05
"Haluska, John J" <jhaluska@telcordia.com> Tue, 22 July 2008 00:18 UTC
Return-Path: <sipping-bounces@ietf.org>
X-Original-To: sipping-archive@optimus.ietf.org
Delivered-To: ietfarch-sipping-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8931F3A684D; Mon, 21 Jul 2008 17:18:38 -0700 (PDT)
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04FFF3A6848 for <sipping@core3.amsl.com>; Mon, 21 Jul 2008 17:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_16=0.6, J_CHICKENPOX_44=0.6]
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 9yT2Y7tDZsqg for <sipping@core3.amsl.com>; Mon, 21 Jul 2008 17:18:36 -0700 (PDT)
Received: from dnsmx1rrc.telcordia.com (dnsmx1rrc.telcordia.com [128.96.20.41]) by core3.amsl.com (Postfix) with ESMTP id 657843A67E7 for <sipping@ietf.org>; Mon, 21 Jul 2008 17:18:34 -0700 (PDT)
Received: from pya-dte-ieg01.cc.telcordia.com (pya-dte-ieg01.cc.telcordia.com [128.96.20.21]) by dnsmx1rrc.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id m6M0JCK22724; Mon, 21 Jul 2008 20:19:12 -0400 (EDT)
Received: from rrc-dte-exhb1.dte.telcordia.com ([128.96.20.12]) by pya-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id M2008072120190925596 ; Mon, 21 Jul 2008 20:19:09 -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, 21 Jul 2008 20:19:09 -0400
From: "Haluska, John J" <jhaluska@telcordia.com>
To: "jmpolk@cisco.com" <jmpolk@cisco.com>, "sipping@ietf.org" <sipping@ietf.org>
Date: Mon, 21 Jul 2008 20:19:08 -0400
Thread-Topic: [Sipping] Comment on draft-haluska-sipping-directory-assistance-05
Thread-Index: AQHI65COv1xpT5IVkEa1QUpWpnBtDA==
Message-ID: <8B6A9EC265011E4CB70F99C64426E8C2028C833F4D@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
MIME-Version: 1.0
Subject: Re: [Sipping] Comment on draft-haluska-sipping-directory-assistance-05
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sipping-bounces@ietf.org
Errors-To: sipping-bounces@ietf.org
James Thanks a lot for your comment and for taking an interest in this draft, and I apologize for the delayed response. You're correct that location could play an important role for such services. This is not covered in the current document; we'll definitely consider how the SIP location conveyance document could fit in. Thanks again for your comment. John Haluska =============================================== To: sipping at ietf.org Subject: [Sipping] Comment on draft-haluska-sipping-directory-assistance-05 From: "James M. Polk" <jmpolk at cisco.com> Date: Tue, 13 May 2008 13:01:11 -0500 Authentication-results: sj-dkim-1; header.From=jmpolk at cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); Delivered-to: ietfarch-sipping-web-archive at core3.amsl.com Delivered-to: sipping at core3.amsl.com Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=3547; t=1210701683; x=1211565683; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk at cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk at cisco.com> |Subject:=20Comment=20on=20draft-haluska-sipping-directory- assistance-05 |Sender:=20; bh=cstd37V5wVYej3ZaQ3feQuGfFhmYqreYz0Nzf6Gz8O0=; b=n85BPIAERTk7lo3dhCDhN4QKfKE0HBtZuCJRUNxvN4VG+SUlMDbhLm2KBm XyvOzvmjeJDHQCLWvVwWf2oFxKROCvjNjDMJu0SgGwZgGLzVJESD94XG0slt 19rbocnnW/FEV1zr2u3nvoIwX83pwjvRtCEPI7/uDKCapBjO2sNfg=; In-reply-to: <20080513171501.DA5543A68C6@core3.amsl.com> List-archive: <https://www.ietf.org/mailman/private/sipping> List-help: <mailto:sipping-request@ietf.org?subject=help> List-id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org> List-post: <mailto:sipping@ietf.org> List-subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe> List-unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe> References: <20080513171501.DA5543A68C6@core3.amsl.com> Sender: sipping-bounces at ietf.org I think the ability to provide physical location should be considered for some of this solution, given that at least some of the DA information will (perhaps need to be) location specific to within a geographic area, or pertaining to the location of the requester. I can give countless examples if needed. Here are a few - Which Pizza Hut? - Which Joe's Barbershop? - Which Main Street? 1st Street? 2nd Street? 5th Avenue? - With Peachtree road/lane/avenue/turnpike/street/etc... (in just Atlanta)? - How does "the system" know the person is calling from Atlanta? - ... from Manhattan and not the Bronx or Brooklyn? Automated answers will likely depend on where someone is requesting from, or where someone is requesting to/for. Human ones probably will too... The reference to use for SIP Location Conveyance can be found here: http://tools.ietf.org/wg/sip/draft-ietf-sip-location-conveyance/ This ID is done except for one final header parameter (a result of WGLC comments). James At 12:15 PM 5/13/2008, Internet-Drafts at ietf.org wrote: >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-05.txt > Pages : 91 > Date : 2008-05-08 > >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 reproduce the current PSTN behaviour. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-haluska-sipping-directory-assistance-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. > > ><ftp://ftp.ietf.org/internet-drafts/draft-haluska-sipping-directory-assistance-05.txt> >_______________________________________________ >I-D-Announce mailing list >I-D-Announce at 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 _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors at cs.columbia.edu for questions on current sip Use sip at ietf.org for new developments of core SIP _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] Comment on draft-haluska-sipping-direct… James M. Polk
- Re: [Sipping] Comment on draft-haluska-sipping-di… Haluska, John J