From owner-pint-outgoing@lists.research.bell-labs.com Wed Mar 1 06:18:00 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27746 for ; Wed, 1 Mar 2000 06:17:59 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 9AFE052AB; Wed, 1 Mar 2000 06:15:21 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 11F7452D4; Wed, 1 Mar 2000 06:15:20 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com Message-Id: <200003011113.GAA27623@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: pint@lists.research.bell-labs.com, spirits@lists.research.bell-lab From: Internet-Drafts@ietf.org Reply-To: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-canal-p909-pint-spirits-00.txt Date: Wed, 01 Mar 2000 06:13:20 -0500 Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : EURESCOM P909 contribution to PINT and SPIRITS Interaction between Internet and PSTN to request services from one domain to the other Author(s) : V. Blavette, G. Canal, U. Herzog, C. Licciardi, S. Tuffin Filename : draft-canal-p909-pint-spirits-00.txt Pages : 25 Date : 29-Feb-00 This document is intended to provide input to the IETF SPIRITS Working Group(SPIRITS WG) and to the IETF PINT Working Group (PINT WG) from the viewpoint of European network operators that are involved in EURESCOM P909 Project 'Enabling Technologies for IN Evolution and IN-Internet Integration'. The input is based on current results that were achieved in the project. As the project title says P909 project deals with IN-Internet integration issues. The project has defined an architecture for IN-Internet inte gration and it has selected and described some IN-Internet services which can be interesting from the business perspective and challenging from the technical perspective. Some of these services are 'officially' chartered in IETF: ICW in SPIRITS, Click-to-Dial (Request to Call) as well as proposed Conference Service in PINT. However, there are additional IN-Internet convergence services that P909 studies and that are included in this document only as examples. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-canal-p909-pint-spirits-00.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-canal-p909-pint-spirits-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-canal-p909-pint-spirits-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. 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: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000229105747.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-canal-p909-pint-spirits-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-canal-p909-pint-spirits-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000229105747.I-D@ietf.org> --OtherAccess-- --NextPart-- --------- This message came from the IETF PINT Working Group Mailing List. From owner-pint-outgoing@lists.research.bell-labs.com Mon Mar 6 04:43:38 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01357 for ; Mon, 6 Mar 2000 04:43:37 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 975D452AB; Mon, 6 Mar 2000 04:39:37 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 0D2BA52E7; Mon, 6 Mar 2000 04:39:36 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com To: pint@lists.research.bell-labs.com Date: Mon, 6 Mar 2000 04:35:36 -0500 Message-ID: <00e101bf874f$1e26f920$0401a8c0@oleane.com> From: "Peter Lewis" Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk To: Subject: SIP 2000 International Conference Date: Mon, 6 Mar 2000 10:33:45 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DE_01BF8757.73594D00" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 This is a multi-part message in MIME format. ------=_NextPart_000_00DE_01BF8757.73594D00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Unknown and even rejected by many vendors and operators only a few = months ago, SIP is on the brink of making a definitive name for itself.=20 Visit the SIP 2000 International Conference programme: http://www.upperside.fr/basip.htm ------=_NextPart_000_00DE_01BF8757.73594D00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Unknown and even rejected by many vendors and operators only a few = months=20 ago, SIP is on the brink of making a definitive name for itself.
Visit the SIP 2000 International Conference programme:
http://www.upperside.fr/basip.= htm
 
------=_NextPart_000_00DE_01BF8757.73594D00-- --------- This message came from the IETF PINT Working Group Mailing List. From owner-pint-outgoing@lists.research.bell-labs.com Tue Mar 7 15:48:01 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08741 for ; Tue, 7 Mar 2000 15:47:59 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 02F5052AB; Tue, 7 Mar 2000 15:45:21 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 7820952D5; Tue, 7 Mar 2000 15:45:20 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com Message-ID: <87A245E94948D3118DE30008C716B01394759B@c0005v1idc1.oss.level3.com> From: Jon.Peterson@Level3.com To: pint@lists.research.bell-labs.com Subject: PINT 'm= modem'? Date: Tue, 7 Mar 2000 13:44:28 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk Hey list, Has anyone out there considered allowing a media type of 'modem' in the SDP associated with a PINT request? Today, of course, there are such values as 'pager' and 'fax' (even 'html'), but something like a modem would probably be covered under the generic blanket of audio/voice. I ask because there are potentially services that involve a PSTN-Internet gateway calling out to a desktop modem that could fall under the PINT paradigm; one in which two legs of a call are originated from a gateway (or perhaps one leg targets components integrated with the gateway) in which it could useful, for routing purposes, to specifically flag the legs as 'modem' calls in the SDP. These might not necessarily be 'click-to' services, but some sort of events in the Internet could result in the need to acquire a connection with a modem. Is there any document to date associated with PINT that examines cases like this? If not, is there any prevailing sentiment about the inclusion of such a category in the PINT standard? Thanks. Jon Peterson Level(3) Communications --------- This message came from the IETF PINT Working Group Mailing List. From owner-pint-outgoing@lists.research.bell-labs.com Fri Mar 10 10:26:23 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18055 for ; Fri, 10 Mar 2000 10:26:22 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id AF21852E1; Fri, 10 Mar 2000 10:09:45 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 94B5452E4; Fri, 10 Mar 2000 10:09:44 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com Message-ID: <20000310112740.8429.qmail@web117.yahoomail.com> Date: Fri, 10 Mar 2000 03:27:40 -0800 (PST) From: Luis Novais Subject: H.323 interconnection to V5.2 To: pint@lists.research.bell-labs.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk Not sure if this is the right place, but can You provide me some information regarding How to connect H.323 equipment to V5.2 equipment. Best Regards, Luis Novais __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com --------- This message came from the IETF PINT Working Group Mailing List. From owner-pint-outgoing@lists.research.bell-labs.com Mon Mar 20 09:25:56 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21961 for ; Mon, 20 Mar 2000 09:25:55 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id 1D0D052D6; Mon, 20 Mar 2000 09:23:23 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 89EF052DB; Mon, 20 Mar 2000 09:23:22 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com Message-Id: <200003201421.JAA20282@ietf.org> To: IETF-Announce: ; Cc: RFC Editor Cc: Internet Architecture Board Cc: pint@lists.research.bell-labs.com From: The IESG Subject: Protocol Action: The PINT Service Protocol:Extensions to SIP and SDP for IP Access to Telephone Call Services to Proposed Standard Date: Mon, 20 Mar 2000 09:21:56 -0500 Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk The IESG has approved the Internet-Draft 'The PINT Service Protocol:Extensions to SIP and SDP for IP Access to Telephone Call Services' as a Proposed Standard. This document is the product of the PSTN and Internet Internetworking Working Group. The IESG contact persons are Scott Bradner and Vern Paxson. Technical Summary This document contains the specification of the PINT Service Protocol, which defines a protocol for invoking certain telephone services from an IP network. These services include placing basic calls, sending and receiving faxes, and receiving content over the telephone. The PINT protocol is specified as a set of enhancements and additions to the SIP and SDP protocols. Three functions are defined by the PINT protocol: Request to Call, Request to Fax, and Request to Hear Content. An example usage of the PINT protocol would be by a web server that would like to send a request to a traditional telephone (POTS) service provider to place a phone call between a call center run by a company and a customer of that company in response to a mouse click on a web page. Working Group Summary This document has strong support in the working group and no issues were raised during IETF last-call. Protocol Quality The document was reviewed for the IESG by Scott Bradner. There are a number of implementations in development. Note to IANA: Igor Faynberg will serve as the Pint "expert" to the IANA. --------- This message came from the IETF PINT Working Group Mailing List. From owner-pint-outgoing@lists.research.bell-labs.com Mon Mar 20 12:05:55 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28039 for ; Mon, 20 Mar 2000 12:05:54 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id AB9FC52DC; Mon, 20 Mar 2000 12:03:25 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 2FDF252DD; Mon, 20 Mar 2000 12:03:25 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com Message-ID: <017d01bf928d$f7bb6240$99dd5c18@tampabay.rr.com> From: "Bill Hamlin" To: Subject: anything out there? Date: Mon, 20 Mar 2000 12:01:42 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_017A_01BF9264.0E7D70B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_017A_01BF9264.0E7D70B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Does anyone know of any commercial implementations of the server (PSTN) = side of the PINT specification that may be available for use? =20 Thanks, Bill Hamlin ------=_NextPart_000_017A_01BF9264.0E7D70B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Does anyone know of any commercial implementations = of the=20 server (PSTN) side of the PINT specification that may be available for=20 use? 
 
Thanks,
Bill Hamlin
 
 
------=_NextPart_000_017A_01BF9264.0E7D70B0-- --------- This message came from the IETF PINT Working Group Mailing List. From owner-pint-outgoing@lists.research.bell-labs.com Fri Mar 31 09:32:59 2000 Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14036 for ; Fri, 31 Mar 2000 09:32:59 -0500 (EST) Received: by lists.research.bell-labs.com (Postfix) id D2E1052D6; Fri, 31 Mar 2000 09:10:28 -0500 (EST) Delivered-To: pint-outgoing-local@paperless.dnrc.bell-labs.com Received: by lists.research.bell-labs.com (Postfix, from userid 20006) id 1741B52E1; Fri, 31 Mar 2000 09:09:33 -0500 (EST) Delivered-To: pint-local@paperless.dnrc.bell-labs.com Message-ID: <38E2065B.95DCA085@research.att.com> Date: Wed, 29 Mar 2000 08:34:19 -0500 From: IPTS 2000 X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: iptel@lists.research.bell-labs.com, pint@lists.research.bell-labs.com, sigtran@standards.nortelnetworks.com, sip@lists.research.bell-labs.com Cc: ipts2000@research.att.com Subject: Initial CFP: IP Telecom Services 2000 Workshop Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pint@lists.research.bell-labs.com Precedence: bulk Content-Transfer-Encoding: 7bit [Please accept our apologies for multiple copies of this call.] ------------- PRELIMINARY CALL FOR PAPERS --------------- IP TELECOM SERVICES WORKSHOP 2000 (IPTS 2000) co-located with Fall 2000 Voice on the Net (VON) organized by AT&T Labs Research pulver.com Cobb Galleria, Atlanta, Georgia, U.S.A September 11, 2000 submission deadline: June 16, 2000 http://www.research.att.com/conf/ipts2000/ ----------------------------------------------------------- IPTS 2000 is a new workshop dedicated to the important, emerging field of IP Telecom Services research. In contrast to the services available on the PSTN, a new world of telecom services is possible on an IP-based infrastructure. This world presents new challenges for service development, deployment and management. This one-day workshop will serve as a forum for the dissemination of research relating to these challenges. The IPTS 2000 Program Committee invites submission of papers on substantial, original and previously unpublished research in IP telecom services, including, but not limited to: - service architectures (e.g. AIN, SoftSwitch, JAIN, Parlay, DFC) - service creation environments - protocols, standards and interoperability (e.g. H.323, SIP, MGCP, Megaco/H.248, etc.) - service programming languages - service management - billing, fault tolerance, monitoring - novel services We welcome papers describing original research; position papers describing research interests in the field, work in progress, or future directions of research; project or system descriptions. IMPORTANT DATES June 16, 2000 Submission deadline July 21, 2000 Notification of acceptance August 25, 2000 Final version of papers September 11, 2000 IPTS 2000 PAPER SUBMISSIONS Papers must describe original, previously unpublished work that has not been simultaneously submitted for publication elsewhere. They must be written in English, not exceeding 6 pages including figures, tables and references in 10-12 point font on 8.5x11-inch (US letter) paper. The first page must include an abstract of up to 200 words, keywords, and email address of the corresponding author. All papers must be submitted electronically unless specifically approved by the Workshop Co-Chairs. Submissions in PostScript or PDF format should be sent to mailto:ipts2000@research.att.com. Authors of accepted papers are expected to present their contribution at the workshop. The proceedings will be published in hardcopy and on the web. REVIEW PROCEDURE All submissions will be subject to academic peer review by the IPTS 2000 Program Committee under the chairmanship of the Workshop Co-Chairs. Each paper will receive three written reviews, and reviews will be returned to the authors. The Workshop Co-Chairs have final authority over the review process and all decisions relating to acceptance of papers. Review criteria include originality of ideas, technical soundness, significance of results, and quality of presentation. CONFERENCE VENUE AND RELATED EVENTS IPTS 2000 will be held on September 11, 2000 in Atlanta, Georgia. The workshop will be co-located with Fall 2000 Voice on the Net (VON). Details about Fall 2000 VON can be found at http://pulver.com. IPTS 2000 is organized by AT&T Labs Research (http://www.research.att.com) and pulver.com (http://pulver.com). WORKSHOP CO-CHAIRS Greg Bond, AT&T Labs Research Eric Cheung, AT&T Labs Research PROGRAM COMMITTEE Mauricio Arango, Sun Microsystems Labs Joanne Atlee, University of Waterloo Ralph Blumenthal, Daewoo Telecom Scott Hoffpauir, BroadSoft Evan Magill, University of Strathclyde Peter Mataga, dynamicsoft Bernie Pagurek, Carleton University Jonathan Rosenberg, dynamicsoft Henning Schulzrinne, Columbia University Greg Utas, Nortel Networks Pamela Zave, AT&T Labs Research FURTHER GENERAL INFORMATION http://www.research.att.com/conf/ipts2000 --------- This message came from the IETF PINT Working Group Mailing List.