Re: [dispatch] Requesting DISPATCH advice on draft-haluska-sipping-directory-assistance-09

Cullen Jennings <fluffy@cisco.com> Tue, 27 October 2009 13:12 UTC

Return-Path: <fluffy@cisco.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 1D43028C143 for <dispatch@core3.amsl.com>; Tue, 27 Oct 2009 06:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.093
X-Spam-Level:
X-Spam-Status: No, score=-109.093 tagged_above=-999 required=5 tests=[AWL=1.506, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 9lpp2d4didd6 for <dispatch@core3.amsl.com>; Tue, 27 Oct 2009 06:12:56 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 969353A6782 for <dispatch@ietf.org>; Tue, 27 Oct 2009 06:12:55 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkEAAImO5kqQ/uCWe2dsb2JhbACbPAEBFiQGpHCYOII5AQaBfwSLYQ
X-IronPort-AV: E=Sophos;i="4.44,633,1249257600"; d="scan'208";a="52877892"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 27 Oct 2009 13:13:08 +0000
Received: from ams3-vpn-dhcp5824.cisco.com (ams3-vpn-dhcp5824.cisco.com [10.61.86.191]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9RDD89v016121; Tue, 27 Oct 2009 13:13:08 GMT
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="windows-1252"; format="flowed"; delsp="yes"
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <8B6A9EC265011E4CB70F99C64426E8C205388882DD@rrc-dte-exmb2.dte.telcordia.com>
Date: Tue, 27 Oct 2009 14:13:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F81C62F0-74C5-4822-8B22-1E9F4C2F07FC@cisco.com>
References: <8B6A9EC265011E4CB70F99C64426E8C205388882DD@rrc-dte-exmb2.dte.telcordia.com>
To: "Haluska, John J" <jhaluska@telcordia.com>
X-Mailer: Apple Mail (2.1076)
Cc: "dispatch@ietf.org" <dispatch@ietf.org>, "gonzalo.camarillo@ericsson.com" <gonzalo.camarillo@ericsson.com>
Subject: Re: [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: Tue, 27 Oct 2009 13:12:57 -0000

When I see all the things that this includes, much of it normative in  
behavior, I don't think AD sponsoring is a route we should take.

Cullen <RAI AD>

On Oct 26, 2009, at 21:08 , Haluska, John J wrote:

> 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 (1K)