From extest-admin@lists.bell-labs.com Sun Oct 1 06:02:21 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA07551 for ; Sun, 1 Oct 2000 06:02:21 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 754F244467 for ; Sun, 1 Oct 2000 05:02:12 -0400 (EDT) Subject: lists.bell-labs.com mailing list memberships reminder From: mailman-owner@lists.bell-labs.com To: pint-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: extest-admin@lists.bell-labs.com Errors-To: extest-admin@lists.bell-labs.com X-BeenThere: extest@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk Message-Id: <20001001090212.754F244467@lists.bell-labs.com> Date: Sun, 1 Oct 2000 05:02:12 -0400 (EDT) This is a reminder, sent out once a month, about your lists.bell-labs.com mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, pint-request@lists.bell-labs.com) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@lists.bell-labs.com. Thanks! Passwords for pint-archive@lists.ietf.org: List Password // URL ---- -------- pint@lists.bell-labs.com hQOO http://lists.bell-labs.com/mailman/options/pint/pint-archive%40lists.ietf.org From pint-admin@lists.bell-labs.com Mon Oct 2 17:06:58 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA14152 for ; Mon, 2 Oct 2000 17:06:57 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id AC35244341; Mon, 2 Oct 2000 16:07:01 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from nw128.netaddress.usa.net (nw128.netaddress.usa.net [204.68.24.28]) by lists.bell-labs.com (Postfix) with SMTP id 5BCEF4433E for ; Mon, 2 Oct 2000 16:06:31 -0400 (EDT) Received: (qmail 2766 invoked by uid 60001); 2 Oct 2000 21:06:27 -0000 Message-ID: <20001002210627.2765.qmail@nw128.netaddress.usa.net> Received: from 204.68.24.28 by nw128 for [209.24.141.50] via web-mailer(34FM.0700.4.03) on Mon Oct 2 21:06:27 GMT 2000 From: Nishith Chudasama To: pint@lists.bell-labs.com X-Mailer: USANET web-mailer (34FM.0700.4.03) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Subject: [PINT] PSTN to IP call origination Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: 2 Oct 00 15:06:27 MDT Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA14152 Hi All, Can anybody let me know if there are any standards for establishing a call from PSTN to IP network? I am primarily interested in the standards for addressing some PC in an IP network from PSTN. Thanks & Regards, Nishith. ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Tue Oct 3 01:03:01 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA20875 for ; Tue, 3 Oct 2000 01:03:01 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 00ED54433E; Tue, 3 Oct 2000 00:03:01 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51]) by lists.bell-labs.com (Postfix) with ESMTP id 51E5644338 for ; Tue, 3 Oct 2000 00:02:30 -0400 (EDT) Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50]) by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id BAA11243; Tue, 3 Oct 2000 01:04:27 -0400 (EDT) Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21) id ; Tue, 3 Oct 2000 00:58:59 -0400 Message-ID: From: Jonathan Rosenberg To: "'Nishith Chudasama'" , "'pint@lists.bell-labs.com'" Subject: RE: [PINT] PSTN to IP call origination MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Tue, 3 Oct 2000 00:58:58 -0400 The signaling component is addressed by protocols like SIP (rfc2543). For addressing, enum (rfc2916) allows telephone numbers to be mapped to things like SIP URLs. There is also a tel URL (rfc2806). -Jonathan R. --- Jonathan D. Rosenberg 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000 http://www.dynamicsoft.com > -----Original Message----- > From: Nishith Chudasama [mailto:nishith76@usa.net] > Sent: Monday, October 02, 2000 5:06 PM > To: pint@lists.bell-labs.com > Subject: [PINT] PSTN to IP call origination > > > Hi All, > > Can anybody let me know if there are any standards for > establishing a call > from PSTN to IP network? > > I am primarily interested in the standards for addressing > some PC in an IP > network from PSTN. > > Thanks & Regards, > Nishith. > > ____________________________________________________________________ > Get free email and a permanent address at > http://www.netaddress.com/?N=1 > > _______________________________________________ > PINT mailing list > PINT@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/pint > _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Tue Oct 3 17:31:02 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23709 for ; Tue, 3 Oct 2000 17:31:01 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 3D55E4433C; Tue, 3 Oct 2000 16:31:02 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from nwcst317.netaddress.usa.net (nwcst317.netaddress.usa.net [204.68.23.62]) by lists.bell-labs.com (Postfix) with SMTP id 5552244338 for ; Tue, 3 Oct 2000 16:30:06 -0400 (EDT) Received: (qmail 18076 invoked by uid 60001); 3 Oct 2000 21:30:02 -0000 Message-ID: <20001003213002.18075.qmail@nwcst317.netaddress.usa.net> Received: from 204.68.23.62 by nwcst317 for [209.24.141.50] via web-mailer(34FM.0700.4.03) on Tue Oct 3 21:30:02 GMT 2000 From: Nishith Chudasama To: Jonathan Rosenberg , "pint@lists.bell-labs.com" Subject: Re: [RE: [PINT] PSTN to IP call origination] X-Mailer: USANET web-mailer (34FM.0700.4.03) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: 3 Oct 00 15:30:02 MDT Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA23709 Thanks Jonathan, I was aware of RFC2806 but RFC2916 was new to me.... But as far as I understand, these are the conventions to call a PSTN subscriber from within an IP network. Actually I wanted to know the number mapping in the reverse direction (originator in PSTN and destination being a SIP URL in IP network). For example, I am the originator in PSTN network and I want to call a SIP user having a specific SIP URL. How can I do that? As per my knowledge, we should use some SIP gateway for this. But are there any guidelines for PSTN user to specify SIP URL (Using DP or DTMF)? If yes, kindly let me know the procedure for this. Also please correct me if my concepts are wrong. Thanks in advance, Nishith. Jonathan Rosenberg wrote: The signaling component is addressed by protocols like SIP (rfc2543). For addressing, enum (rfc2916) allows telephone numbers to be mapped to things like SIP URLs. There is also a tel URL (rfc2806). -Jonathan R. --- Jonathan D. Rosenberg 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000 http://www.dynamicsoft.com > -----Original Message----- > From: Nishith Chudasama [mailto:nishith76@usa.net] > Sent: Monday, October 02, 2000 5:06 PM > To: pint@lists.bell-labs.com > Subject: [PINT] PSTN to IP call origination > > > Hi All, > > Can anybody let me know if there are any standards for > establishing a call > from PSTN to IP network? > > I am primarily interested in the standards for addressing > some PC in an IP > network from PSTN. > > Thanks & Regards, > Nishith. > > ____________________________________________________________________ > Get free email and a permanent address at > http://www.netaddress.com/?N=1 > > _______________________________________________ > PINT mailing list > PINT@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/pint > ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1 _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Tue Oct 3 17:40:01 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23831 for ; Tue, 3 Oct 2000 17:40:00 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 5CDAD44351; Tue, 3 Oct 2000 16:40:02 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from redball.dynamicsoft.com (redball.dynamicsoft.com [216.173.40.51]) by lists.bell-labs.com (Postfix) with ESMTP id 84FE244338 for ; Tue, 3 Oct 2000 16:39:15 -0400 (EDT) Received: from DYN-EXCH-001.dynamicsoft.com ([216.173.40.50]) by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id RAA18821; Tue, 3 Oct 2000 17:41:07 -0400 (EDT) Received: by DYN-EXCH-001.dynamicsoft.com with Internet Mail Service (5.5.2650.21) id ; Tue, 3 Oct 2000 17:35:38 -0400 Message-ID: From: Jonathan Rosenberg To: "'Nishith Chudasama'" , Jonathan Rosenberg , "'pint@lists.bell-labs.com'" Subject: RE: [RE: [PINT] PSTN to IP call origination] MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Tue, 3 Oct 2000 17:35:37 -0400 > -----Original Message----- > From: Nishith Chudasama [mailto:nishith76@usa.net] > Sent: Tuesday, October 03, 2000 5:30 PM > To: Jonathan Rosenberg; pint@lists.bell-labs.com > Subject: Re: [RE: [PINT] PSTN to IP call origination] > > > Thanks Jonathan, > > I was aware of RFC2806 but RFC2916 was new to me.... > But as far as I understand, these are the conventions to call a PSTN > subscriber from within an IP network. That is not correct. RFC2916 addresses exactly what you want - originator in PSTN and destination being a SIP URL in the IP network. The PSTN->IP gateway would look up the dialed number in ENUM and obtain the SIP URL. -Jonathan R. --- Jonathan D. Rosenberg 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Wed Oct 4 09:20:01 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA19027 for ; Wed, 4 Oct 2000 09:20:01 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 8E4EF443B4; Wed, 4 Oct 2000 08:20:02 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by lists.bell-labs.com (Postfix) with ESMTP id 3FFBE44338; Mon, 2 Oct 2000 17:39:24 -0400 (EDT) Received: from fokus.gmd.de (dhcp082 [195.37.78.210]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id AAA10539; Tue, 3 Oct 2000 00:38:48 +0200 (MET DST) Message-ID: <39D90E55.217B38D@fokus.gmd.de> From: Jiri Kuthan Organization: GMD Fokus X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: kuthan@fokus.gmd.de Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: [PINT] iptel2001 Call for Papers Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Tue, 03 Oct 2000 00:38:13 +0200 Content-Transfer-Encoding: 8bit Call for Papers 2nd IP Telephony Workshop April 2-3, 2001 - Columbia University, New York City http://www.fokus.gmd.de/events/iptel2001/ Objectives ---------- Internet telephony is rapidly evolving from research to design and deployment. The objectives of the IP Telephony Workshop are to bring together researchers, developers, vendors and service providers active in this area and stimulate discussion on innovation, research, implementation, deployment experiences and future directions. Scope & Topics -------------- Original technical articles related to IP telephony are solicited. Only papers with significant technical content, not "white papers" or tutorials, will be considered for publication: - Research papers (unique ideas, novel algorithms, architectures, measurements, theoretical and/or analytical contributions) - Surveys, state-of-the-art studies, technology comparisons - Implementation and deployment reports - Standardization reports Particular areas of interest include, but are not limited to, the following: - Integration with Internet services (e.g., web, instant messaging, games) - Added-value services (e.g., call centers, conferencing) - Mobility and 3rd generation wireless - Authentication, authorization, accounting, charging, settlement - QoS support - Security (e.g., privacy, authentication, certification authorities, firewall traversal) - Call signaling & processing - Feature creation - Supporting services (e.g., call routing, lookup services) - Audio & video encoding and transmission - Management and provisioning - Interworking with the PSTN - Design and deployment considerations (e.g., performance, scalability, reliability) Important Dates --------------- Full paper due November 27th, 2000 Notification of acceptance January 12th, 2001 Final version due January 31st, 2001 Program published and February 5th, 2001 registration opens Workshop April 2nd-3rd, 2001 iptel2001 Organizing Committee ------------------------------ Program Chair H. Schulzrinne Columbia University Program Committee M. Arango Sun Microsystems F. Baker Cisco W. Bauerfeld T-Nova G. Bond AT&T Research S. Bradner Harvard University G. Carle GMD FOKUS J. Crowcroft UCL C. Huitema Microsoft G. S. Kuo National Central University, Taiwan J. Kuthan GMD Fokus T. Magedanz IKV++ GmbH W. Marshall AT&T Research K. Mehdi University of Kansas D. Oran Cisco J. Ott University of Bremen T. La Porta Bell Labs B. Rosen Marconi J. Rosenberg dynamicsoft H. Sinnreich MCI WorldCom R. Steinmetz Technical University of Darmstadt H. Stüttgen NEC CCRLE W. Wimmreuter Siemens L. Wolf University of Karlsruhe A. Wolisz Technical University of Berlin M. Zitterbart Technical University of Braunschweig Submission Instructions ----------------------- Authors are invited to submit full papers written in English before November 27th, 2000. The submissions will be reviewed, and accepted papers will be included in the program. Notifications of acceptance will be sent out on January 12th, 2000. Deadline for submission of camera-ready copies is January 31st, 2001. Authors of accepted papers will need to sign a Copyright Transfer Form and submit a Netbib entry. Papers must be submitted electronically using the Web site at http://www.cs.columbia.edu/iptel Submissions must be in PDF or Postscript; any other documents cannot be accepted. Postscript papers must use only standard PostScript fonts: Times Roman, Courier, Symbol, and Helvetica. Papers must be formatted according to the IEEE Transactions format except for the font size, which MUST be 11pt. Templates are available at the Web site http://www.fokus.gmd.de/events/iptel2001/cfp/ Because of the size limitation on the final manuscript, and to ensure that the reviewed paper and the final version have a similar size, papers with more than 11 pages cannot be reviewed. Submissions must include: title, authors, affiliation, abstract, list of keywords, and contact information. One of the authors of each accepted paper must present the paper at iptel'2001. Contact Address --------------- Please, send all your inquiries regarding iptel2001 to iptel2001@egroups.com. _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Tue Oct 10 10:59:00 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA05476 for ; Tue, 10 Oct 2000 10:59:00 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 31CE5443AA; Tue, 10 Oct 2000 09:59:02 -0400 (EDT) Delivered-To: pint@share.research.bell-labs.com Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by lists.bell-labs.com (Postfix) with SMTP id 86577443A8 for ; Tue, 10 Oct 2000 09:58:06 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Tue Oct 10 10:56:11 EDT 2000 Received: by lists.bell-labs.com (Postfix) id B5A5744380; Tue, 10 Oct 2000 10:43:01 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from ans.ih.lucent.com (ans.ih.lucent.com [135.2.78.5]) by lists.bell-labs.com (Postfix) with SMTP id 6D54A4437D for ; Tue, 10 Oct 2000 10:43:01 -0400 (EDT) Received: by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2) id JAA03192; Tue, 10 Oct 2000 09:42:50 -0500 Cc: Jonathan Rosenberg , "'pint@lists.bell-labs.com'" Received: from lucent.com by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2) id JAA03172; Tue, 10 Oct 2000 09:42:47 -0500 Message-ID: <39E32BB2.2B46370B@lucent.com> From: Alec Brusilovsky X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en,ru,uk MIME-Version: 1.0 To: "'Nishith Chudasama'" Original-CC: Jonathan Rosenberg , "'pint@lists.bell-labs.com'" Subject: Re: [RE: [PINT] PSTN to IP call origination] References: Content-Type: multipart/mixed; boundary="------------6FD37D09830921EA9AAFE3ED" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Tue, 10 Oct 2000 09:46:10 -0500 This is a multi-part message in MIME format. --------------6FD37D09830921EA9AAFE3ED Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I would like to recommend another useful resource. It is recently published Converged Networks and Services: Internetworking IP and the PSTN: http://www.amazon.com/exec/obidos/ASIN/0471356441/qid%3D963414149/sr%3D1-2/102-5350463-4117738 Regards, Alec Jonathan Rosenberg wrote: > > -----Original Message----- > > From: Nishith Chudasama [mailto:nishith76@usa.net] > > Sent: Tuesday, October 03, 2000 5:30 PM > > To: Jonathan Rosenberg; pint@lists.bell-labs.com > > Subject: Re: [RE: [PINT] PSTN to IP call origination] > > > > > > Thanks Jonathan, > > > > I was aware of RFC2806 but RFC2916 was new to me.... > > But as far as I understand, these are the conventions to call a PSTN > > subscriber from within an IP network. > > That is not correct. > > RFC2916 addresses exactly what you want - originator in PSTN and destination > being a SIP URL in the IP network. The PSTN->IP gateway would look up the > dialed number in ENUM and obtain the SIP URL. > > -Jonathan R. > --- > Jonathan D. Rosenberg 72 Eagle Rock Ave. > Chief Scientist First Floor > dynamicsoft East Hanover, NJ 07936 > jdrosen@dynamicsoft.com FAX: (973) 952-5050 > http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000 > http://www.dynamicsoft.com > > _______________________________________________ > PINT mailing list > PINT@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/pint --------------6FD37D09830921EA9AAFE3ED Content-Type: text/x-vcard; charset=us-ascii; name="abrusilovsky.vcf" Content-Description: Card for Alec Brusilovsky Content-Disposition: attachment; filename="abrusilovsky.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Brusilovsky;Alec tel;fax:+1 630 713 5840 tel;work:+1 630 713 8401 x-mozilla-html:FALSE org:Lucent (jg7290000) version:2.1 email;internet:abrusilovsky@lucent.com title:MTS adr;quoted-printable:;;IHP 1A-423=0D=0A263 Shuman Blvd,P O Box 3050;Naperville;IL;60566-7050;U S x-mozilla-cpt:;-29888 fn:Alec Brusilovsky end:vcard --------------6FD37D09830921EA9AAFE3ED-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Thu Oct 19 08:00:58 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA09329 for ; Thu, 19 Oct 2000 08:00:57 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 0C0564434C; Thu, 19 Oct 2000 07:01:01 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by lists.bell-labs.com (Postfix) with ESMTP id C217144337 for ; Thu, 19 Oct 2000 07:00:39 -0400 (EDT) Received: from etbh01.etb.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id e9JC1LX14666 for ; Thu, 19 Oct 2000 14:01:21 +0200 (MET DST) Message-ID: <00c701c039c4$6c05da30$5ef9cb8a@etb.bel.alcatel.be> From: "Stephane Nicoll" To: "PINT Mailing List" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00C4_01C039D5.2F393730" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: [PINT] information needed Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Thu, 19 Oct 2000 14:02:14 +0200 This is a multi-part message in MIME format. ------=_NextPart_000_00C4_01C039D5.2F393730 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi to all pint workers, I've already ask you some information on PINT and i've bought yout last = book Igor. I have accomplished some works on two months but now i'm = faces with several questions. 1) Anyone has an url to get rfc2848 in PDF or PS format ? 2) I'm searching of things relating to the difficulty for providing PINT = services and TNIP services as well. The purpose of my thesis is to find out which protocols are best suited = to provide PINT and TNIP services (that is to say provide IN on the = internet and "vice versa") and what are the problems to provide these = services.=20 Every help, url, books are welcome. Many thanks again to all of you Stephane ------=_NextPart_000_00C4_01C039D5.2F393730 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi to all pint workers,
 
I've already ask you some information on PINT and = i've bought=20 yout last book Igor. I have accomplished some works on two months but = now i'm=20 faces with several questions.
 
1) Anyone has an url to get rfc2848 in PDF or PS = format=20 ?
2) I'm searching of things relating to the = difficulty for=20 providing PINT services and TNIP services as well.
 
The purpose of my thesis is to find out which=20 protocols are best suited to provide PINT and TNIP services (that = is to say=20 provide IN on the internet and "vice versa") and what are the problems = to=20 provide these services.
 
Every help, url, books are welcome.
 
Many thanks again to all of you
 
 
Stephane
 
------=_NextPart_000_00C4_01C039D5.2F393730-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Thu Oct 19 08:34:42 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA15325 for ; Thu, 19 Oct 2000 08:34:42 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 8FC3444351; Thu, 19 Oct 2000 07:34:02 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by lists.bell-labs.com (Postfix) with ESMTP id 47FE044337 for ; Thu, 19 Oct 2000 07:33:45 -0400 (EDT) Received: from etbh01.etb.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id e9JCYH121546 for ; Thu, 19 Oct 2000 14:34:18 +0200 (MET DST) Message-ID: <010c01c039c9$05f90730$5ef9cb8a@etb.bel.alcatel.be> From: "Stephane Nicoll" To: "PINT Mailing List" MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0109_01C039D9.C94AE8B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: [PINT] Again one question Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Thu, 19 Oct 2000 14:35:11 +0200 This is a multi-part message in MIME format. ------=_NextPart_000_0109_01C039D9.C94AE8B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello again, I've one more question : "Why the PINT group has choosen SIP and not = H.323? In other words, what are the properties or the requierements that = has driven the group to this decision? Thanks a lot in advance Stephane ------=_NextPart_000_0109_01C039D9.C94AE8B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello again,
 
I've one more question : "Why the PINT group has = choosen SIP=20 and not H.323? In other words, what are the properties or the = requierements that=20 has driven the group to this decision?
 
Thanks a lot in advance
 
Stephane
------=_NextPart_000_0109_01C039D9.C94AE8B0-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Thu Oct 19 12:33:58 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23345 for ; Thu, 19 Oct 2000 12:33:58 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 2EEBB44337; Thu, 19 Oct 2000 11:34:01 -0400 (EDT) Delivered-To: pint@share.research.bell-labs.com Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by lists.bell-labs.com (Postfix) with SMTP id 7860544336 for ; Thu, 19 Oct 2000 11:10:06 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Oct 19 12:08:05 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 3FCAE44380; Thu, 19 Oct 2000 11:54:56 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from hotair.hobl.lucent.com (hotair.hobl.lucent.com [199.118.135.2]) by lists.bell-labs.com (Postfix) with SMTP id 11B4B4437D for ; Thu, 19 Oct 2000 11:54:56 -0400 (EDT) Received: from lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2) id LAA27274; Thu, 19 Oct 2000 11:54:36 -0400 Message-ID: <39EF1902.73BAFC7@lucent.com> From: Igor Faynberg X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Stephane Nicoll Cc: PINT Mailing List Subject: Re: [PINT] information needed References: <00c701c039c4$6c05da30$5ef9cb8a@etb.bel.alcatel.be> Content-Type: multipart/alternative; boundary="------------2027F4AFB0056E88C5B2A01C" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Thu, 19 Oct 2000 11:53:39 -0400 --------------2027F4AFB0056E88C5B2A01C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Stephane Nicoll wrote: > Hi to all pint workers, > > Hi there! > .... > 2) I'm searching of things relating to the difficulty for providing > PINT services and TNIP services as well. The purpose of my thesis is > to find out which protocols are best suited to provide PINT and TNIP > services (that is to say provide IN on the internet and "vice versa") > and what are the problems to provide these services. Stephane, you may want to take a look at the SPIRITS WG page (http://www.ietf.org/html.charters/spirits-charter.html)--that is what the thing that was at certain time referred to as TNIP had become. There, you will find all the answers your questions (see also the supporting link). Specifically, you will find there a draft "Pre-Spirits Implementations of PSTN-initiated Services," which has recently been approved as an Informational RFC. This document talks about present implementations of both PINT services and Internet Call Waiting. (I don't think there were difficulties in implementations, at least one thing I can say with confidence is that we experienced none here in Lucent.) We are expecting implementations reports. You may also look at the VON presentations on the subject--Scott Petrack has made a detailed one on the E-Dial implementation at the recent VON developers conference. Anyway, please finish you thesis and come to work with us in PINT and SPIRITS! With best regards, Igor --------------2027F4AFB0056E88C5B2A01C Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

Stephane Nicoll wrote:

 Hi to all pint workers,

Hi there!
....
  2) I'm searching of things relating to the difficulty for providing PINT services and TNIP services as well. The purpose of my thesis is to find out which protocols are best suited to provide PINT and TNIP services (that is to say provide IN on the internet and "vice versa") and what are the problems to provide these services. 


Stephane, you may want to take a look at the SPIRITS WG page (http://www.ietf.org/html.charters/spirits-charter.html)--that is what the thing that was at certain time referred to as TNIP had become. There, you will find all the answers your questions (see also the supporting link). Specifically, you will find there a draft
"Pre-Spirits Implementations of PSTN-initiated Services," which has recently been approved as an Informational RFC. This document talks about present implementations of both PINT services and Internet Call Waiting. (I don't think there were difficulties in implementations, at least one thing I can say with confidence is that we experienced none here in Lucent.) We are expecting implementations reports.

You may also look at the VON presentations on the subject--Scott Petrack has made a detailed one on the E-Dial implementation at the recent VON developers conference.

Anyway, please finish you thesis and come to work with us in PINT and SPIRITS!

With best regards,

Igor
  --------------2027F4AFB0056E88C5B2A01C-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Thu Oct 19 13:49:58 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA06098 for ; Thu, 19 Oct 2000 13:49:57 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id BB1C644384; Thu, 19 Oct 2000 12:49:01 -0400 (EDT) Delivered-To: pint@share.research.bell-labs.com Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by lists.bell-labs.com (Postfix) with SMTP id BCEEB4434A for ; Thu, 19 Oct 2000 11:44:06 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Oct 19 12:43:30 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 2B99744380; Thu, 19 Oct 2000 12:30:21 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from hotair.hobl.lucent.com (hotair.hobl.lucent.com [199.118.135.2]) by lists.bell-labs.com (Postfix) with SMTP id F1A6F4437D for ; Thu, 19 Oct 2000 12:30:20 -0400 (EDT) Received: from lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2) id MAA29892; Thu, 19 Oct 2000 12:30:20 -0400 Message-ID: <39EF2161.F3BDAC0A@lucent.com> From: Igor Faynberg X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Stephane Nicoll Cc: PINT Mailing List Subject: Re: [PINT] Again one question References: <010c01c039c9$05f90730$5ef9cb8a@etb.bel.alcatel.be> Content-Type: multipart/alternative; boundary="------------B41C91B708DD27F5AD17C698" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Thu, 19 Oct 2000 12:29:22 -0400 --------------B41C91B708DD27F5AD17C698 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Stephane Nicoll wrote: > Hello again, I've one more question : "Why the PINT group has choosen > SIP and not H.323? In other words, what are the properties or the > requierements that has driven the group to this decision? A bit of history: Technically, only three protocols were discussed in PINT to begin with (see RFC 2458): 1) A Lucent-prototype one, specifically developed for PINT services; 2) a CTI-like Simple Computer Telephony Protocol; 3) HTTP (with some extensions). We never formally worked on the requirements, but the problem was rather straight-forward, and it already had a few proposed solutions. The MMUSIC people (Scott Petrack, Dave Oran, and Jonathan Rosenberg--in the order of microphone use, according to my memory) immediately pointed out that there already was a protocol (two protocols--SIP and SDP, actually) under development that would do what was needed: 1) relatively simple secure Internet-friendly transactions 2) ability to specify media characteristics; and 3) ability to transfer content. M. Handley made a presentation at the first PINT meeting, then Henning worked with us and co-authored RFC 2458, which effectively had the requirements. Because of Hui-Lan's continuos effort as ISOC representative to ITU-T SG 11, SIP was recognized as the "IN service access" mechanism in ITU. So, PINT was the first SIP application in the IETF. Now, why not H.323? (This question was asked a couple of times before, of course.) Very simple: H.323 is a VoIP protocol, but VoIP is NOT part of PINT charter. Of course, hypothetically, one could pick-up a subset of H.323, mask unnecessary parameters, add others as extensions, etc., but no one ever proposed such an action. In other words, H.323 is rather a counterpart of Q.931 and ISUP than INAP/TC. PINT chose the SIP function which WAS a counterpart of INAP/TC stack. The PINT problem needed a simple direct solution to service access, and such a solution was found and later used for many other services. Igor --------------B41C91B708DD27F5AD17C698 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

Stephane Nicoll wrote:

Hello again, I've one more question : "Why the PINT group has choosen SIP and not H.323? In other words, what are the properties or the requierements that has driven the group to this decision? 
A bit of history:

Technically, only three protocols were discussed in PINT to begin with (see RFC 2458): 1) A Lucent-prototype one, specifically developed for PINT services; 2) a CTI-like Simple Computer Telephony Protocol; 3) HTTP (with some extensions).

We never formally worked on the requirements, but the problem was rather straight-forward, and it already had a few proposed solutions. The MMUSIC people (Scott Petrack, Dave Oran, and Jonathan Rosenberg--in the order of microphone use, according to my memory) immediately pointed out that there already was a protocol (two protocols--SIP and SDP, actually) under development that  would do what was needed: 1) relatively simple secure Internet-friendly transactions 2) ability to specify media characteristics; and 3) ability to transfer content. M. Handley made a presentation at the first PINT meeting, then Henning worked with us and co-authored RFC 2458, which effectively had the requirements. Because of Hui-Lan's continuos effort as ISOC representative to ITU-T SG 11, SIP was recognized as the "IN service access" mechanism in ITU.

So, PINT was the first SIP application in the IETF.

Now, why not H.323?  (This question was asked a couple of times before, of course.) Very simple: H.323 is a VoIP protocol, but VoIP is NOT part of PINT charter. Of course, hypothetically, one could pick-up a subset of H.323, mask unnecessary parameters, add others as extensions, etc., but no one ever proposed such an action. In other words, H.323 is rather a counterpart of Q.931 and ISUP than INAP/TC. PINT chose the SIP function which WAS a counterpart of INAP/TC stack.

The PINT problem needed a simple direct solution to service access, and such a solution was found and later used for many other services.

Igor --------------B41C91B708DD27F5AD17C698-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Fri Oct 20 09:40:59 2000 Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA12560 for ; Fri, 20 Oct 2000 09:40:58 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 922FD44338; Fri, 20 Oct 2000 08:41:01 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from cundall.co.uk (dorfl.roke.co.uk [193.118.192.45]) by lists.bell-labs.com (Postfix) with ESMTP id 3D44344336 for ; Fri, 20 Oct 2000 08:40:22 -0400 (EDT) Received: from [193.118.192.55] by cundall.co.uk with ESMTP (Eudora Internet Mail Server 1.3.1); Fri, 20 Oct 2000 14:36:56 +0100 Mime-Version: 1.0 X-Sender: lwc@193.118.192.24 Message-Id: In-Reply-To: <39EF2161.F3BDAC0A@lucent.com> References: <010c01c039c9$05f90730$5ef9cb8a@etb.bel.alcatel.be> <39EF2161.F3BDAC0A@lucent.com> To: Igor Faynberg , Stephane Nicoll From: Lawrence Conroy Subject: Re: [PINT] Again one question Cc: PINT Mailing List Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-BeenThere: pint@lists.bell-labs.com X-Mailman-Version: 2.0beta6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF PINT Mailing List List-Unsubscribe: , List-Archive: http://lists.bell-labs.com/pipermail/pint/ Date: Fri, 20 Oct 2000 14:40:02 +0100 At 12:29 pm -0400 19/10/00, Igor Faynberg wrote: > > >Stephane Nicoll wrote: > >>Hello again, I've one more question : "Why the PINT group has >>choosen SIP and not H.323? In other words, what are the properties >>or the requierements that has driven the group to this decision? >> >A bit of history: > >Now, why not H.323? (This question was asked a couple of times >before, of course.) Very simple: H.323 is a VoIP protocol, but VoIP >is NOT part of PINT charter. Of course, hypothetically, one could >pick-up a subset of H.323, mask unnecessary parameters, add others >as extensions, etc., but no one ever proposed such an action. In >other words, H.323 is rather a counterpart of Q.931 and ISUP than >INAP/TC. PINT chose the SIP function which WAS a counterpart of >INAP/TC stack. Hi Stephane, Igor has given an excellent summary. I should add that some people *DID* suggest that H.323 might be considered early on in the group (I seem to remember in the Los Angeles Meeting in early '98). I remember that the response was that PINT was always open to proposals, and people were asked to come up with the details on how it could be used; No proposals were actually delivered. In answer to a question in the Los Angeles meeting, I suggested that we *could* use H.323/245/225, but the easiest way was to set up a T.120 association between PINT client and PINT server once the initial H.323/245 association had been set up, and then send whatever messages one wanted over that T.120 association. It seemed difficult to send (for example) a text document or a graphic using a "pure" H.323/245 connection. As Igor points out, the idea of changing H.323/245 to "fit" PINT's needs was too challenging, particularly as these change proposals would need to be made in the ITU and/or ETSI. The rough consensus at the time appeared to be that this was a LOT more complex than the equivalent SIP scheme, where we could just re-use some of the attributes and send any needed documents or references within the body parts of the message. In summary; H.323 hard for technical and standards group reasons ; SIP/SDP easy, extensible, and a fairly natural fit to carry the information we needed (and the experts were in the same room!). BTW, RFC2848 was created using BBEdit (a pure text editor) - If you want I'll distill it for you, but text is its native format. What's the problem? regards, Lawrence _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint