From mailman-owner@lists.bell-labs.com Thu Jun 1 05:12:51 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 ESMTP id FAA17929 for ; Thu, 1 Jun 2000 05:12:50 -0400 (EDT) From: mailman-owner@lists.bell-labs.com Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id CDD9D44407 for ; Thu, 1 Jun 2000 05:02:45 -0400 (EDT) Subject: lists.bell-labs.com mailing list memberships reminder To: pint-archive@ietf.org X-No-Archive: yes Precedence: bulk X-Mailman-Version: 1.1 Precedence: bulk List-Id: Message-Id: <20000601090245.CDD9D44407@lists.bell-labs.com> Date: Thu, 1 Jun 2000 05:02:45 -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@lists.ietf.org From pint-admin@lists.bell-labs.com Sun Jun 4 21:48: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 ESMTP id VAA11877 for ; Sun, 4 Jun 2000 21:48: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 3C29D44336; Sun, 4 Jun 2000 21:38:08 -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 1D0F144336 for ; Sun, 4 Jun 2000 09:54:17 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Sun Jun 4 10:02:19 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 4F67744344; Sun, 4 Jun 2000 09:49:10 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 2922A44341 for ; Sun, 4 Jun 2000 09:49:10 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 5E5F852C4; Sun, 4 Jun 2000 09:49:25 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id 955C652B6 for ; Sun, 4 Jun 2000 09:49:22 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Sun Jun 4 09:47:13 EDT 2000 Received: from cundall.co.uk ([193.118.192.45]) by dusty; Sun Jun 4 09:47:13 EDT 2000 Received: from [193.118.192.41] by cundall.co.uk with ESMTP (Eudora Internet Mail Server 1.3.1); Sun, 4 Jun 2000 14:46:24 +0100 Mime-Version: 1.0 X-Sender: lwc@193.118.192.24 Message-Id: Date: Sun, 4 Jun 2000 14:47:20 +0100 To: sip@lists.bell-labs.com From: Lawrence Conroy Cc: pint@lists.research.bell-labs.com Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: [PINT] UDP support changed from SHOULD to MUST Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com * UDP support changed from SHOULD to MUST in SIP 2453 bis draft. It looks like support for UDP is gradually moving from a SHOULD to a MUST in SIP. In PINT we may not have that assumption. We can have a good reason for using TCP only (inline content, security using TLS, ...), so *for PINT* I'd prefer to leave this as a SHOULD. I wonder if the move to a MUST in the core spec will cause grief for any other extension or application. The key point here is ->in the core spec<- I had the same feeling at the Interim meeting in D.C. when the subject of "Busy Line Verification" was raised - there's a lot of focus on VoIP, when I can easily imagine SIP being used for a much wider set of applications even for "straight" conferences; for example, Quake, as Dean suggests. Let's imagine an Operator listening in on the sampled Quake audio track that I'm conferencing. How long before the Police arrive? An over-emphasis on VoIP can lead to bad assumptions, IMHO - SIP is much wider than that. -- lwc@roke.co.uk -- +44 1794 833666 ------------------------------------------------------------- Herewith a pointless waste of a few lines, stating that Roke Manor Research Limited is NOT responsible for my rantings and that they would very much like people to sue me rather than them if this email contains racist or sexist comments, please. Also, I can't do anything; only our lawyers can, so speak to them. Oh, and by the way, if our I.T. department has so mangled our email system that this has been misdirected, beware that having read this far, your eyes are about to fall out from reading this highly sensitive information, unless you immediately forget that this ever darkened your mailbox. Do it now. ------------------------------------------------------------- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Sun Jun 4 21:48:52 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 ESMTP id VAA11888 for ; Sun, 4 Jun 2000 21:48:52 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 6BCCD44363; Sun, 4 Jun 2000 21:38:10 -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 9562D4434F for ; Sun, 4 Jun 2000 09:34:17 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Sun Jun 4 09:42:18 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 4CB1744344; Sun, 4 Jun 2000 09:29:09 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 1D71E44341 for ; Sun, 4 Jun 2000 09:29:09 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 79DEF52C4; Sun, 4 Jun 2000 09:29:23 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.research.bell-labs.com (Postfix) with SMTP id B0D8352B6 for ; Sun, 4 Jun 2000 09:29:20 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by grubby; Sun Jun 4 09:27:56 EDT 2000 Received: from cundall.co.uk ([193.118.192.45]) by dusty; Sun Jun 4 09:27:55 EDT 2000 Received: from [193.118.192.41] by cundall.co.uk with ESMTP (Eudora Internet Mail Server 1.3.1); Sun, 4 Jun 2000 14:26:54 +0100 Mime-Version: 1.0 X-Sender: lwc@193.118.192.24 Message-Id: Date: Sun, 4 Jun 2000 14:27:53 +0100 To: sip@lists.bell-labs.com From: Lawrence Conroy Cc: pint@lists.research.bell-labs.com Content-Type: text/plain; charset="us-ascii" ; format="flowed" Subject: [PINT] Basic Question Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com * There have been a number of comments that SDP carried with SIP needs at least one RTP session:- To which I reply... Nooooooo.... For VoIP/Games/... usage of SIP I like the delayed media sessions section of the bis draft. Please don't dump it, even though this has no media sessions at all in the SDP. Even for not-transient situations, we MAY have this situation...for example, PINT doesn't use RTP sessions, but it still has SDP. I suspect that the ATM stuff may NOT use RTP either - one may find VoATM distasteful, but there are customers for it; SIP/SDP may be used as a hybrid. Whilst for VoIP sessions, lack of an RTP media session is strange, this is not always true, even when SIP is being used. -- All the best, Lawrence ----------------------------------------------------------------------- | Lawrence Conroy, | "These Opinions must be mine, 'cos if they | | Roke Manor Research | were my Company's they'd pay me for them" | |- lwc@roke.co.uk ---+- Tel: +44 1794 833666 Fax: +44 1794 833434 --| _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Mon Jun 5 09:57:50 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 ESMTP id JAA02413 for ; Mon, 5 Jun 2000 09:57:50 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 95A9D44379; Mon, 5 Jun 2000 09:47:54 -0400 (EDT) Delivered-To: pint@share.research.bell-labs.com Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by lists.bell-labs.com (Postfix) with SMTP id C2267443C1 for ; Sun, 4 Jun 2000 23:04:11 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Sun Jun 4 23:12:24 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 9CDF744344; Sun, 4 Jun 2000 22:59:15 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 75B4144341 for ; Sun, 4 Jun 2000 22:59:15 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 360DC52C4; Sun, 4 Jun 2000 22:59:25 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id 6EE0D52AB for ; Sun, 4 Jun 2000 22:59:22 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Sun Jun 4 22:57:36 EDT 2000 Received: from redball.dynamicsoft.com ([216.173.40.51]) by dusty; Sun Jun 4 22:57:35 EDT 2000 Received: from dynamicsoft.com (1Cust107.tnt4.freehold.nj.da.uu.net [63.36.112.107]) by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id WAA00514; Sun, 4 Jun 2000 22:58:55 -0400 (EDT) Message-ID: <393B1720.1A3AC5BC@dynamicsoft.com> Date: Sun, 04 Jun 2000 22:57:36 -0400 From: Jonathan Rosenberg Organization: dynamicsoft X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Lawrence Conroy Cc: sip@lists.bell-labs.com, pint@lists.research.bell-labs.com References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [PINT] Re: [SIP] UDP support changed from SHOULD to MUST Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com Content-Transfer-Encoding: 7bit Lawrence Conroy wrote: > > * UDP support changed from SHOULD to MUST in SIP 2453 bis draft. > It looks like support for UDP is gradually moving from a SHOULD to a > MUST in SIP. It was to solve the sticky situation that without at least a common transport, UA to UA communication would not be possible. It would require proxies that do conversions to record-route, and all kinds of other stuff. Simply stating that everyone needs to use UDP made things much easier, and in any case, I suspect nearly everyone does UDP anyway. However, please shout if this change is not a happy one for you.... In the case of pint, I would simply suggest that all pint implementations MUST support TCP as well, in which case you won't have a problem. Yes, you'll have to do UDP also to be compliant to the baseline spec, but it turns out that supporting both is really not that hard if done properly. > I had the same feeling at the Interim meeting in D.C. when the > subject of "Busy Line Verification" was raised - there's a lot of > focus on VoIP, when I can easily imagine SIP being used for a much > wider set of applications even for "straight" conferences; for > example, Quake, as Dean suggests. This change has exactly zero to do with telephony. Its as simple as UA to UA communication not being always possible without a common baseline transport. -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: (732) 741-7244 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 Fri Jun 9 13:07:34 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 ESMTP id NAA15394 for ; Fri, 9 Jun 2000 13:07:34 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id EC26444382; Fri, 9 Jun 2000 12:31:42 -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 2F2AF44339 for ; Fri, 9 Jun 2000 06:29:42 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Jun 9 06:38:20 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 93BB744344; Fri, 9 Jun 2000 06:25:11 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 6C54644341 for ; Fri, 9 Jun 2000 06:25:11 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 4040652D0; Fri, 9 Jun 2000 06:25:22 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.research.bell-labs.com (Postfix) with SMTP id 0BF2052AB for ; Fri, 9 Jun 2000 06:25:17 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by grubby; Fri Jun 9 06:24:26 EDT 2000 Received: from smtp2.cluster.oleane.net ([195.25.12.17]) by dusty; Fri Jun 9 06:24:26 EDT 2000 Received: from oleane (dyn-1-2-224.Vin.dialup.oleane.fr [194.2.4.224]) by smtp2.cluster.oleane.net with SMTP id MAA10854 for ; Fri, 9 Jun 2000 12:25:01 +0200 (CEST) Message-ID: <004c01bfd1fc$ab598e00$7501a8c0@oleane.oleane.com> From: "Peter Lewis" To: Date: Fri, 9 Jun 2000 12:22:51 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0049_01BFD20D.6E4B4E20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Subject: [PINT] MGC CALL FOR PAPER Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com This is a multi-part message in MIME format. ------=_NextPart_000_0049_01BFD20D.6E4B4E20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MGCP/Megaco Conference 14 to 17 November 2000. Second edition: = deployment experiences, operational issues, interoperability status. Please get more details on the call for papers online: http://www.upperside.fr/bamgc2yk.htm ------=_NextPart_000_0049_01BFD20D.6E4B4E20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
MGCP/Megaco Conference 14 to 17 = November 2000.=20 Second edition: deployment experiences, operational issues, = interoperability=20 status.
Please get = more details on=20 the call for papers online:
http://www.upperside.fr/bam= gc2yk.htm
------=_NextPart_000_0049_01BFD20D.6E4B4E20-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Fri Jun 9 13:12:31 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 ESMTP id NAA15456 for ; Fri, 9 Jun 2000 13:12:31 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id C209244394; Fri, 9 Jun 2000 12:32:00 -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 AFD1A44338 for ; Fri, 9 Jun 2000 11:01:37 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Jun 9 11:10:21 EDT 2000 Received: by lists.bell-labs.com (Postfix) id E531044341; Fri, 9 Jun 2000 10:57:11 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 9B71444345 for ; Fri, 9 Jun 2000 10:57:11 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 5B81B52D0; Fri, 9 Jun 2000 10:57:22 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id C0AFD52C4 for ; Fri, 9 Jun 2000 10:57:20 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Fri Jun 9 10:56:56 EDT 2000 Received: from mail-blue.research.att.com ([135.207.30.102]) by dusty; Fri Jun 9 10:56:55 EDT 2000 Received: from postal.research.att.com (postal.research.att.com [135.207.23.30]) by mail-blue.research.att.com (Postfix) with ESMTP id 865004CE2D for ; Fri, 9 Jun 2000 10:56:54 -0400 (EDT) Received: from research.att.com (fpdhcp073.research.att.com [135.207.28.73]) by postal.research.att.com (8.8.7/8.8.7) with ESMTP id KAA20166 for ; Fri, 9 Jun 2000 10:56:50 -0400 (EDT) Message-ID: <39410484.47DCB2B5@research.att.com> Date: Fri, 09 Jun 2000 10:51:48 -0400 From: "Gregory W. Bond" Organization: AT&T Labs - Research, Florham Park, NJ X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: pint@lists.research.bell-labs.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [PINT] 3rd CFP (EXTENDED DEADLINE): IP Telecom Services Workshop 2000 Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com Content-Transfer-Encoding: 7bit [Please accept our apologies for multiple copies of this call.] ------------- THIRD CALL FOR PAPERS --------------- ------------- EXTENDED DEADLINE --------------- 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 23, 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 23, 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 _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Sun Jun 11 11:21:06 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 ESMTP id LAA07742 for ; Sun, 11 Jun 2000 11:21:05 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id D663744336; Sun, 11 Jun 2000 11:10:20 -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 EAC0844336 for ; Fri, 9 Jun 2000 15:43:35 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Jun 9 15:53:12 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 6BCD944348; Fri, 9 Jun 2000 15:26:58 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 4399D44345 for ; Fri, 9 Jun 2000 15:26:58 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id D063852C4; Fri, 9 Jun 2000 15:27:09 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from ans.ih.lucent.com (ans.ih.lucent.com [135.2.78.5]) by lists.research.bell-labs.com (Postfix) with SMTP id E431652B6 for ; Fri, 9 Jun 2000 15:27:06 -0400 (EDT) Received: by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2) id OAA02565; Fri, 9 Jun 2000 14:26:49 -0500 Cc: Lawrence Conroy , pint@lists.research.bell-labs.com, SPIRITS list Received: from lucent.com by ans.ih.lucent.com (SMI-8.6/EMS-1.5 sol2) id OAA02553; Fri, 9 Jun 2000 14:26:47 -0500 Message-ID: <39414575.C030AC3C@lucent.com> Date: Fri, 09 Jun 2000 14:28:53 -0500 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: sip@lists.bell-labs.com Original-CC: Lawrence Conroy , pint@lists.research.bell-labs.com, SPIRITS list Subject: Re: [PINT] UDP support changed from SHOULD to MUST References: Content-Type: multipart/mixed; boundary="------------47E8D138D00E5CB71F3B136B" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com This is a multi-part message in MIME format. --------------47E8D138D00E5CB71F3B136B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Please see my comments inline. Regards, Alec Lawrence Conroy wrote: > * UDP support changed from SHOULD to MUST in SIP 2453 bis draft. > It looks like support for UDP is gradually moving from a SHOULD to a > MUST in SIP. > > In PINT we may not have that assumption. We can have a good reason > for using TCP only (inline content, security using TLS, ...), so *for > PINT* I'd prefer to leave this as a SHOULD. > I would like to add to what Lawrence is saying that some SIP applications might need a more flexible and rapid session set up than others. PINT is a good example, SPIRITS might as well be another one, assuming that the WG will decide to use SIP. > > I wonder if the move to a MUST in the core spec will cause grief for > any other extension or application. > > The key point here is ->in the core spec<- Looks like the core spec. needs to be more accommodating to the needs of extensions (PINT). SHOULD is just fine. Why break something that actually works? > > > I had the same feeling at the Interim meeting in D.C. when the > subject of "Busy Line Verification" was raised - there's a lot of > focus on VoIP, when I can easily imagine SIP being used for a much > wider set of applications even for "straight" conferences; for > example, Quake, as Dean suggests. > Let's imagine an Operator listening in on the sampled Quake audio > track that I'm conferencing. How long before the Police arrive? An > over-emphasis on VoIP can lead to bad assumptions, IMHO - SIP is much > wider than that. > -- > lwc@roke.co.uk -- +44 1794 833666 > ------------------------------------------------------------- > Herewith a pointless waste of a few lines, stating that > Roke Manor Research Limited is NOT responsible for my rantings > and that they would very much like people to sue me rather than > them if this email contains racist or sexist comments, please. > Also, I can't do anything; only our lawyers can, so speak to them. > Oh, and by the way, if our I.T. department has so mangled our > email system that this has been misdirected, beware that having > read this far, your eyes are about to fall out from reading > this highly sensitive information, unless you immediately > forget that this ever darkened your mailbox. Do it now. > ------------------------------------------------------------- > > _______________________________________________ > PINT mailing list > PINT@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/pint --------------47E8D138D00E5CB71F3B136B 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 --------------47E8D138D00E5CB71F3B136B-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Sun Jun 11 11:22:26 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 ESMTP id LAA07762 for ; Sun, 11 Jun 2000 11:22:25 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 4959444350; Sun, 11 Jun 2000 11:10:30 -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 CB12344336 for ; Sat, 10 Jun 2000 00:33:31 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Sat Jun 10 00:42:24 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 637C844346; Sat, 10 Jun 2000 00:29:15 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 3B24844345 for ; Sat, 10 Jun 2000 00:29:15 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 40ACE52C4; Sat, 10 Jun 2000 00:29:21 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id 59F8A52AB for ; Sat, 10 Jun 2000 00:29:18 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Sat Jun 10 00:28:45 EDT 2000 Received: from redball.dynamicsoft.com ([216.173.40.51]) by dusty; Sat Jun 10 00:28:44 EDT 2000 Received: from dynamicsoft.com (1Cust37.tnt2.freehold.nj.da.uu.net [63.17.114.37]) by redball.dynamicsoft.com (8.9.3+Sun/8.10.0.Beta12) with ESMTP id AAA17842; Sat, 10 Jun 2000 00:29:50 -0400 (EDT) Message-ID: <3941C415.C9995130@dynamicsoft.com> Date: Sat, 10 Jun 2000 00:29:09 -0400 From: Jonathan Rosenberg Organization: dynamicsoft X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alec Brusilovsky Cc: sip@lists.bell-labs.com, Lawrence Conroy , pint@lists.research.bell-labs.com, SPIRITS list Subject: Re: [SIP] Re: [PINT] UDP support changed from SHOULD to MUST References: <39414575.C030AC3C@lucent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com Content-Transfer-Encoding: 7bit Alec Brusilovsky wrote: > > Please see my comments inline. > > Regards, > Alec > > Lawrence Conroy wrote: > > > * UDP support changed from SHOULD to MUST in SIP 2453 bis draft. > > It looks like support for UDP is gradually moving from a SHOULD to a > > MUST in SIP. > > > > In PINT we may not have that assumption. We can have a good reason > > for using TCP only (inline content, security using TLS, ...), so *for > > PINT* I'd prefer to leave this as a SHOULD. > > > > I would like to add to what Lawrence is saying that some SIP applications > might need a more flexible and rapid session set up than others. PINT is a > good example, SPIRITS might as well be another one, assuming that the WG > will decide to use SIP. Right; both UDP and TCP are still there. You can still do TCP if you want, or just UDP, but just not ONLY TCP. > > > > > I wonder if the move to a MUST in the core spec will cause grief for > > any other extension or application. > > > > The key point here is ->in the core spec<- > > Looks like the core spec. needs to be more accommodating to the needs of > extensions (PINT). SHOULD is just fine. Why break something that actually > works? Because it doesn't - thats the problem. UA to UA interoperability is not possible in all cases unless there is a baseline transport. The "core spec" must be a workable protocol in its own right, without clarifications and specifics being defined only in extensions, as pint is. -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: (732) 741-7244 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 Jun 14 16:23:18 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 ESMTP id QAA03684 for ; Wed, 14 Jun 2000 16:23:17 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 19DFB44388; Wed, 14 Jun 2000 16:12: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 AB3BF443D2 for ; Wed, 14 Jun 2000 15:42:54 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Jun 14 15:52:46 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 6253744347; Wed, 14 Jun 2000 15:39:37 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 3283544345 for ; Wed, 14 Jun 2000 15:39:37 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 4CA2D52C4; Wed, 14 Jun 2000 15:39:46 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from hotair.hobl.lucent.com (hotair.hobl.lucent.com [199.118.135.2]) by lists.research.bell-labs.com (Postfix) with SMTP id 890C752B6 for ; Wed, 14 Jun 2000 15:39:43 -0400 (EDT) Received: from bell-labs.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2) id PAA04071; Wed, 14 Jun 2000 15:39:32 -0400 Message-ID: <3947DF70.81CE297B@bell-labs.com> Date: Wed, 14 Jun 2000 15:39:28 -0400 From: faynberg@bell-labs.com Organization: Lucent Technologies X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4 (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: pint Cc: sob@harvard.edu X-Priority: 1 (Highest) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [PINT] The IANA Considerations Section in the PINT MIB Draft Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com Content-Transfer-Encoding: 7bit Ladies and Gentlemen: With the advice and help of Scott Bradner, the Editors are extending the draft by adding the IANA Considerations section with the following text: "IANA Considerations All extensions to the values listed in this MIB must be done through Standards Action processes as defined in RFC 2434." The reference to RFC 2434 will also be added to the list of references. The new draft will be published shortly. Igor and Steve _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Wed Jun 14 16:23:54 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 ESMTP id QAA03696 for ; Wed, 14 Jun 2000 16:23:53 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id AED0844399; Wed, 14 Jun 2000 16:12: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 AB3BF443D2 for ; Wed, 14 Jun 2000 15:42:54 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Jun 14 15:52:46 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 6253744347; Wed, 14 Jun 2000 15:39:37 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 3283544345 for ; Wed, 14 Jun 2000 15:39:37 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 4CA2D52C4; Wed, 14 Jun 2000 15:39:46 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from hotair.hobl.lucent.com (hotair.hobl.lucent.com [199.118.135.2]) by lists.research.bell-labs.com (Postfix) with SMTP id 890C752B6 for ; Wed, 14 Jun 2000 15:39:43 -0400 (EDT) Received: from bell-labs.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2) id PAA04071; Wed, 14 Jun 2000 15:39:32 -0400 Message-ID: <3947DF70.81CE297B@bell-labs.com> Date: Wed, 14 Jun 2000 15:39:28 -0400 From: faynberg@bell-labs.com Organization: Lucent Technologies X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4 (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: pint Cc: sob@harvard.edu X-Priority: 1 (Highest) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [PINT] The IANA Considerations Section in the PINT MIB Draft Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com Content-Transfer-Encoding: 7bit Ladies and Gentlemen: With the advice and help of Scott Bradner, the Editors are extending the draft by adding the IANA Considerations section with the following text: "IANA Considerations All extensions to the values listed in this MIB must be done through Standards Action processes as defined in RFC 2434." The reference to RFC 2434 will also be added to the list of references. The new draft will be published shortly. Igor and Steve _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Wed Jun 14 18:36: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 ESMTP id SAA05364 for ; Wed, 14 Jun 2000 18:36:41 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 9A1C044338; Wed, 14 Jun 2000 18:25:27 -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 DBEC844338 for ; Wed, 14 Jun 2000 17:12:53 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Wed Jun 14 17:23:49 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 8740744346; Wed, 14 Jun 2000 17:10:39 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 56EA344345 for ; Wed, 14 Jun 2000 17:10:39 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 5DA4252C4; Wed, 14 Jun 2000 17:10:48 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from ihrh1.emsr.lucent.com (ihrh1.emsr.lucent.com [135.1.218.53]) by lists.research.bell-labs.com (Postfix) with SMTP id 63ECA52AB for ; Wed, 14 Jun 2000 17:10:45 -0400 (EDT) Received: from ihemlsrv.firewall.lucent.com by ihrh1.emsr.lucent.com (SMI-8.6/EMS-1.5 Solaris/emsr) id QAA08723 for ; Wed, 14 Jun 2000 16:10:31 -0500 Received: from ihemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id RAA19682 for ; Wed, 14 Jun 2000 17:10:33 -0400 (EDT) Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id RAA19652 for ; Wed, 14 Jun 2000 17:10:32 -0400 (EDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21) id ; Wed, 14 Jun 2000 23:10:32 +0200 Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB07B28DCE@nl0006exch002u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: pint , faynberg@bell-labs.com Cc: Scott Bradner Subject: RE: [PINT] The IANA Considerations Section in the PINT MIB Draft Date: Wed, 14 Jun 2000 23:10:28 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com You might want to wait with re-publication for potential other IETF Last Call comments and for possible comments by the MIB Doctor review. Bert > ---------- > From: faynberg@bell-labs.com[SMTP:faynberg@bell-labs.com] > Sent: Wednesday, June 14, 2000 9:39 PM > To: pint > Cc: sob@harvard.edu > Subject: [PINT] The IANA Considerations Section in the PINT MIB Draft > Importance: High > > Ladies and Gentlemen: > > With the advice and help of Scott Bradner, the Editors are extending the > draft > by adding the IANA Considerations section with the following text: > > "IANA Considerations > All extensions to the values listed in this MIB must be done > through Standards Action processes as defined in RFC 2434." > > The reference to RFC 2434 will also be added to the list of references. > > The new draft will be published shortly. > > Igor and Steve > > > > _______________________________________________ > 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 Thu Jun 15 19:17:24 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 ESMTP id TAA17546 for ; Thu, 15 Jun 2000 19:17:24 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 8C21B44336; Thu, 15 Jun 2000 19:06:03 -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 8BCD5443C4 for ; Thu, 15 Jun 2000 18:22:45 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Jun 15 18:32:20 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 277A144346; Thu, 15 Jun 2000 18:19:11 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id F0E7D44345 for ; Thu, 15 Jun 2000 18:19:10 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id AE6BE52C4; Thu, 15 Jun 2000 18:19:19 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id BCD1052AB for ; Thu, 15 Jun 2000 18:19:16 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Thu Jun 15 18:19:02 EDT 2000 Received: from boreas.isi.edu ([128.9.160.161]) by dusty; Thu Jun 15 18:19:01 EDT 2000 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA22788; Thu, 15 Jun 2000 15:18:57 -0700 (PDT) Message-Id: <200006152218.PAA22788@boreas.isi.edu> To: IETF-Announce: ; Cc: rfc-ed@ISI.EDU, pint@lists.research.bell-labs.com Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Jun 2000 15:18:57 -0700 From: RFC Editor Subject: [PINT] RFC 2848 on The PINT Service Protocol Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2848 Title: The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services Author(s): S. Petrack, L. Conroy Status: Standards Track Date: June 2000 Mailbox: scott.petrack@metatel.com, lwc@roke.co.uk Pages: 73 Characters: 168851 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pint-protocol-04.txt URL: ftp://ftp.isi.edu/in-notes/rfc2848.txt This document contains the specification of the PINT Service Protocol 1.0, 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 protocol is specified as a set of enhancements and additions to the SIP 2.0 and SDP protocols. This document is a product of the PSTN and Internet Internetworking Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000615151650.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2848 --OtherAccess Content-Type: Message/External-body; name="rfc2848.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000615151650.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Thu Jun 15 22:44:05 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 ESMTP id WAA22457 for ; Thu, 15 Jun 2000 22:44:05 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 23857443D1; Thu, 15 Jun 2000 22:22:48 -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 C1D2B44383 for ; Thu, 15 Jun 2000 20:20:43 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Jun 15 20:30:17 EDT 2000 Received: by lists.bell-labs.com (Postfix) id C077744346; Thu, 15 Jun 2000 20:17:07 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 9371D44345 for ; Thu, 15 Jun 2000 20:17:07 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id 49A4E52C4; Thu, 15 Jun 2000 20:17:16 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from hotair.hobl.lucent.com (hotair.hobl.lucent.com [199.118.135.2]) by lists.research.bell-labs.com (Postfix) with SMTP id 7B35D52AB for ; Thu, 15 Jun 2000 20:17:13 -0400 (EDT) Received: from bell-labs.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2) id UAA16471; Thu, 15 Jun 2000 20:17:02 -0400 Message-ID: <394971FB.CB23EB99@bell-labs.com> Date: Thu, 15 Jun 2000 20:16:59 -0400 From: faynberg@bell-labs.com Organization: Lucent Technologies X-Mailer: Mozilla 4.6 [en]C-CCK-MCD EMS-1.4 (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: pint Subject: [Fwd: [PINT] RFC 2848 on The PINT Service Protocol] X-Priority: 1 (Highest) Content-Type: multipart/mixed; boundary="------------68499648110FF92ECBF0B9F9" Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com This is a multi-part message in MIME format. --------------68499648110FF92ECBF0B9F9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Congratulations to Scott and Lawrence and also to all who have contributed! Now we have the protocol RFC and a beautiful RFC number (all based on powers of two), too. Igor and Steve --------------68499648110FF92ECBF0B9F9 Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from holta.ho.lucent.com by hotair.hobl.lucent.com (SMI-8.6/EMS-1.5 sol2) id TAA14115; Thu, 15 Jun 2000 19:18:03 -0400 Received: from hoemail2.firewall.lucent.com by holta.ho.lucent.com (SMI-8.6/EMS-1.5 sol2) id TAA22801; Thu, 15 Jun 2000 19:24:05 -0400 Received: from hoemail2.firewall.lucent.com (localhost [127.0.0.1]) by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id TAA07141 for ; Thu, 15 Jun 2000 19:18:02 -0400 (EDT) Received: from lists.bell-labs.com (share.research.bell-labs.com [204.178.16.58] (may be forged)) by hoemail2.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id TAA07132 for ; Thu, 15 Jun 2000 19:18:02 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id B5262443C0; Thu, 15 Jun 2000 19:06:04 -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 8BCD5443C4 for ; Thu, 15 Jun 2000 18:22:45 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Jun 15 18:32:20 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 277A144346; Thu, 15 Jun 2000 18:19:11 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id F0E7D44345 for ; Thu, 15 Jun 2000 18:19:10 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id AE6BE52C4; Thu, 15 Jun 2000 18:19:19 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id BCD1052AB for ; Thu, 15 Jun 2000 18:19:16 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Thu Jun 15 18:19:02 EDT 2000 Received: from boreas.isi.edu ([128.9.160.161]) by dusty; Thu Jun 15 18:19:01 EDT 2000 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id PAA22788; Thu, 15 Jun 2000 15:18:57 -0700 (PDT) Message-Id: <200006152218.PAA22788@boreas.isi.edu> To: IETF-Announce:;@lists.bell-labs.com@holta.ho.lucent.com@hotair.hobl.lucent.com Cc: rfc-ed@ISI.EDU, pint@lists.research.bell-labs.com Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 15 Jun 2000 15:18:57 -0700 From: RFC Editor Subject: [PINT] RFC 2848 on The PINT Service Protocol Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2848 Title: The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services Author(s): S. Petrack, L. Conroy Status: Standards Track Date: June 2000 Mailbox: scott.petrack@metatel.com, lwc@roke.co.uk Pages: 73 Characters: 168851 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pint-protocol-04.txt URL: ftp://ftp.isi.edu/in-notes/rfc2848.txt This document contains the specification of the PINT Service Protocol 1.0, 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 protocol is specified as a set of enhancements and additions to the SIP 2.0 and SDP protocols. This document is a product of the PSTN and Internet Internetworking Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000615151650.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2848 --OtherAccess Content-Type: Message/External-body; name="rfc2848.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000615151650.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint --------------68499648110FF92ECBF0B9F9-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Tue Jun 20 14:56:57 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 ESMTP id OAA01618 for ; Tue, 20 Jun 2000 14:56: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 1339644339; Tue, 20 Jun 2000 14:44:58 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from ietf.org (odin.ietf.org [132.151.1.176]) by lists.bell-labs.com (Postfix) with ESMTP id B53CC44339 for ; Tue, 20 Jun 2000 13:17:06 -0400 (EDT) Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA29976 for ; Tue, 20 Jun 2000 13:29:01 -0400 (EDT) Date: Tue, 20 Jun 2000 13:28:46 -0400 (Eastern Daylight Time) From: Steve Coya To: pint@lists.bell-labs.com Message-ID: X-X-Sender: scoya@odin.cnri.reston.va.us MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1459430-17236-961522126=:-412095" Content-ID: Subject: [PINT] I-D ACTION:draft-ietf-pint-mib-02.txt (fwd) Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1459430-17236-961522126=:-412095 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: FYI - we had a problem posting the announcement with the PINT list email address, and we had to remove it from the envelope. Steve & Natalia ---------- Forwarded message ---------- Date: Tue, 20 Jun 2000 13:00:33 -0400 From: Internet-Drafts@ietf.org To: IETF-Announce: ; Subject: I-D ACTION:draft-ietf-pint-mib-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the PSTN and Internet Internetworking Working Group of the IETF. Title : Management Information Base for the PINT Services Architecture Author(s) : M. Krishnaswamy, D. Romascanu Filename : draft-ietf-pint-mib-02.txt Pages : 20 Date : 19-Jun-00 PINT services are an emerging set of new Internet based applications where voice (and fax) requests to the PSTN (Public Switched Telephone Network) are carried over the Internet. RFC 2458 [1] gives a good introduction to the (pre-standard) PINT architecture and services. It also has examples of some of the early implementations of pre- PINT. This document defines a MIB which contains the elements for monitoring the performance of a PINT based service. The MIB consists of details of the four basic PINT services and their performance statistics measured under various criteria. It is not the purpose of this MIB to enable management of the PINT networking elements. We are concerned only with the PINT specific performance parameters. While it is understood that PINT service performance is closely related to host and network performance, they are not addressed here. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-pint-mib-02.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-ietf-pint-mib-02.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-ietf-pint-mib-02.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. --1459430-17236-961522126=:-412095 Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="1459430-2608-961522126=:-412095" Content-ID: Content-Description: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1459430-2608-961522126=:-412095 Content-Type: MESSAGE/EXTERNAL-BODY; ACCESS-TYPE=mail-server; SERVER="mailserv@ietf.org" Content-ID: --1459430-2608-961522126=:-412095 Content-Type: MESSAGE/EXTERNAL-BODY; NAME="draft-ietf-pint-mib-02.txt"; SITE="ftp.ietf.org"; ACCESS-TYPE=anon-ftp; DIRECTORY=internet-drafts Content-ID: --1459430-2608-961522126=:-412095-- --1459430-17236-961522126=:-412095-- _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Mon Jun 26 08:56:44 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 ESMTP id IAA03642 for ; Mon, 26 Jun 2000 08:56:43 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id ADCFA44336; Mon, 26 Jun 2000 08:43:57 -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 B513C44336 for ; Mon, 26 Jun 2000 08:41:17 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon Jun 26 08:52:19 EDT 2000 Received: by lists.bell-labs.com (Postfix) id 24B0444348; Mon, 26 Jun 2000 08:39:10 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id E381144347 for ; Mon, 26 Jun 2000 08:39:09 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id CD3E952C8; Mon, 26 Jun 2000 08:39:12 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.research.bell-labs.com (Postfix) with SMTP id 1323F52C4 for ; Mon, 26 Jun 2000 08:39:10 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by grubby; Mon Jun 26 08:38:57 EDT 2000 Received: from mail-blue.research.att.com ([135.207.30.102]) by dusty; Mon Jun 26 08:38:57 EDT 2000 Received: from postal.research.att.com (postal.research.att.com [135.207.23.30]) by mail-blue.research.att.com (Postfix) with ESMTP id 5904B4CE1C for ; Mon, 26 Jun 2000 08:38:54 -0400 (EDT) Received: from smb.research.att.com (postal.research.att.com [135.207.23.30]) by postal.research.att.com (8.8.7/8.8.7) with ESMTP id IAA13174 for ; Mon, 26 Jun 2000 08:38:53 -0400 (EDT) Received: from smb.research.att.com (localhost.research.att.com [127.0.0.1]) by smb.research.att.com (Postfix) with ESMTP id ED7F735DC2 for ; Mon, 26 Jun 2000 08:38:52 -0400 (EDT) X-Mailer: exmh version 2.1.1 10/15/1999 From: Steve Bellovin To: pint@lists.research.bell-labs.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 26 Jun 2000 08:38:52 -0400 Message-Id: <20000626123853.ED7F735DC2@smb.research.att.com> Subject: [PINT] patent issued on much of PINT Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com Folks may want to have a look at U.S. patent 6,072,780 (text available from http://164.195.100.11/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1='6,072,780'.WKU.&OS=PN/6,072,780&RS=PN/6,072,780 if you want). If you have prior art, note that the original provisional application was filed in August, 1996, about 8 months before the first PINT BoF. Also note that U.S. law gives priority to "first to invent", rather than the "first to file" principle used in most of the rest of the world. --Steve Bellovin _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint From pint-admin@lists.bell-labs.com Mon Jun 26 09:18:28 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 ESMTP id JAA04439 for ; Mon, 26 Jun 2000 09:18:28 -0400 (EDT) Received: from share.research.bell-labs.com (localhost.localdomain [127.0.0.1]) by lists.bell-labs.com (Postfix) with ESMTP id 41F8A44365; Mon, 26 Jun 2000 09:05:24 -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 76C9144346 for ; Mon, 26 Jun 2000 09:05:22 -0400 (EDT) Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon Jun 26 09:16:20 EDT 2000 Received: by lists.bell-labs.com (Postfix) id B24C044349; Mon, 26 Jun 2000 09:03:10 -0400 (EDT) Delivered-To: pint@lists.bell-labs.com Received: from lists.research.bell-labs.com (paperless.dnrc.bell-labs.com [135.180.161.172]) by lists.bell-labs.com (Postfix) with ESMTP id 810F444347 for ; Mon, 26 Jun 2000 09:03:10 -0400 (EDT) Received: by lists.research.bell-labs.com (Postfix) id E984E52C8; Mon, 26 Jun 2000 09:03:14 -0400 (EDT) Delivered-To: pint@lists.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.research.bell-labs.com (Postfix) with SMTP id 21E3F52C4 for ; Mon, 26 Jun 2000 09:03:11 -0400 (EDT) Received: from dusty.research.bell-labs.com ([135.104.2.7]) by scummy; Mon Jun 26 09:02:56 EDT 2000 Received: from newdev.harvard.edu ([140.247.60.212]) by dusty; Mon Jun 26 09:02:56 EDT 2000 Received: (from sob@localhost) by newdev.harvard.edu (8.9.3/8.9.3) id JAA01508; Mon, 26 Jun 2000 09:02:54 -0400 (EDT) Date: Mon, 26 Jun 2000 09:02:54 -0400 (EDT) From: Scott Bradner Message-Id: <200006261302.JAA01508@newdev.harvard.edu> To: pint@lists.research.bell-labs.com, smb@research.att.com Subject: Re: [PINT] patent issued on much of PINT Sender: pint-admin@lists.bell-labs.com Errors-To: pint-admin@lists.bell-labs.com X-Mailman-Version: 1.1 Precedence: bulk List-Id: IETF PINT Mailing List X-BeenThere: pint@lists.bell-labs.com a shorter URL for the patent is http://www.patents.ibm.com/details?pn=US06072780__ Scott _______________________________________________ PINT mailing list PINT@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/pint