[Sipping] draft-haluska-sipping-directory-assistance-02.txt

"Haluska, John J" <jhaluska@telcordia.com> Fri, 16 February 2007 02:03 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHsRC-0004SA-Tg; Thu, 15 Feb 2007 21:03:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HHsRB-0004LY-36 for sipping@ietf.org; Thu, 15 Feb 2007 21:03:01 -0500
Received: from dnsmx2pya.telcordia.com ([128.96.20.32]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HHsR9-0007Df-Ok for sipping@ietf.org; Thu, 15 Feb 2007 21:03:01 -0500
Received: from pya-dte-ieg01.cc.telcordia.com (pya-dte-ieg01.cc.telcordia.com [128.96.20.21]) by dnsmx2pya.telcordia.com (8.11.7+Sun/8.9.3) with SMTP id l1G22xq20684 for <sipping@ietf.org>; Thu, 15 Feb 2007 21:02:59 -0500 (EST)
Received: from rrc-dte-exbh01.dte.telcordia.com ([128.96.150.31]) by pya-dte-ieg01.cc.telcordia.com (SMSSMTP 4.1.9.35) with SMTP id M2007021521032012129 for <sipping@ietf.org>; Thu, 15 Feb 2007 21:03:20 -0500
Received: from rrc-dte-exs01.dte.telcordia.com ([128.96.150.34]) by rrc-dte-exbh01.dte.telcordia.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 Feb 2007 21:03:20 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 15 Feb 2007 21:03:19 -0500
Message-ID: <A09345776B6C7A4985573569C0F300430EAE5290@rrc-dte-exs01.dte.telcordia.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-haluska-sipping-directory-assistance-02.txt
Thread-Index: AcdRbqFXZX/0yE6tRnKwu4nbta1czA==
From: "Haluska, John J" <jhaluska@telcordia.com>
To: sipping@ietf.org
X-OriginalArrivalTime: 16 Feb 2007 02:03:20.0424 (UTC) FILETIME=[A1AF9680:01C7516E]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Subject: [Sipping] draft-haluska-sipping-directory-assistance-02.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0326898135=="
Errors-To: sipping-bounces@ietf.org

Hello All, 


We are seeking comments on the latest revision of draft-haluska-sipping-directory-assistance-02.txt

This revision goes into much more discussion about applying specific SIP mechanisms for these kinds of services. 

We would appreciate any technical input on the choices of mechanisms, and the usage of these mechanisms. 


Until it is available in the ID repository, it is available at

ftp://ftp.research.telcordia.com/pub/world/haluska/draft-haluska-sipping-directory-assistance-02.txt


Thanks much

John Haluska
_______________________________________________
Sipping mailing list  https://www1.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