From owner-tcp-impl@lerc.nasa.gov Fri Apr 9 07:34:45 1999 Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAB01148 for ; Fri, 9 Apr 1999 07:34:45 -0400 (EDT) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id WAA21381 for tcp-impl-outgoing; Thu, 8 Apr 1999 22:47:21 -0400 (EDT) Received: from tuvok.lerc.nasa.gov (ras119.lerc.nasa.gov [139.88.123.119]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id WAA21373 for ; Thu, 8 Apr 1999 22:47:12 -0400 (EDT) Received: from tuvok.lerc.nasa.gov (localhost [127.0.0.1]) by tuvok.lerc.nasa.gov (8.8.5/8.8.5) with ESMTP id VAA01513 for ; Thu, 8 Apr 1999 21:40:41 -0400 (EDT) Message-Id: <199904090140.VAA01513@tuvok.lerc.nasa.gov> To: tcp-impl@grc.nasa.gov From: Mark Allman Reply-To: mallman@grc.nasa.gov Subject: RFC Editor: RFC 2581 on TCP Congestion Control Organization: Late Night Hackers, NASA Glenn, Cleveland, Ohio Song-of-the-Day: Nobody Told Me Date: Thu, 08 Apr 1999 21:40:40 -0400 Sender: owner-tcp-impl@lerc.nasa.gov Precedence: bulk FYI... ------- Forwarded Message To: IETF-Announce:;@ietf.org Subject: RFC 2581 on TCP Congestion Control Cc: rfc-ed@ISI.EDU Date: Thu, 08 Apr 1999 16:53:18 -0700 From: RFC Editor - --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2581: Title: TCP Congestion Control Author(s): M. Allman, V. Paxson, W. Stevens Status: Proposed Standard Date: April 1999 Mailbox: mallman@grc.nasa.gov, vern@aciri.org, rstevens@kohala.com Pages: 14 Characters: 31351 Obsoletes: 2001 I-D Tag: draft-ietf-tcpimpl-cong-control-05.txt URL: ftp://ftp.isi.edu/in-notes/rfc2581.txt his document defines TCP's four intertwined congestion control algorithms: slow start, congestion avoidance, fast retransmit, and fast recovery. In addition, the document specifies how TCP should begin transmission after a relatively long idle period, as well as discussing various acknowledgment generation methods. This document is a product of the TCP Implementation 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 Alegre Ramos 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: <990408165134.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2581 - --OtherAccess Content-Type: Message/External-body; name="rfc2581.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <990408165134.RFC@RFC-EDITOR.ORG> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message From owner-tcp-impl@lerc.nasa.gov Fri Apr 9 18:23:17 1999 Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08039 for ; Fri, 9 Apr 1999 18:23:17 -0400 (EDT) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id PAA04770 for tcp-impl-outgoing; Fri, 9 Apr 1999 15:01:51 -0400 (EDT) Received: from guns.lerc.nasa.gov (guns.lerc.nasa.gov [139.88.44.160]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id PAA04759 for ; Fri, 9 Apr 1999 15:01:48 -0400 (EDT) Received: from guns.lerc.nasa.gov by guns.lerc.nasa.gov with ESMTP (NASA LeRC 8.7.4.1/2.01-local) id PAA14957; Fri, 9 Apr 1999 15:01:47 -0400 (EDT) Message-Id: <199904091901.PAA14957@guns.lerc.nasa.gov> To: tcp-impl@grc.nasa.gov From: Mark Allman Reply-To: mallman@grc.nasa.gov Subject: RFC Editor: RFC 2582 on NewReno Modification to TCP's Fast Recovery Organization: Late Night Hackers, NASA Glenn, Cleveland, Ohio Song-of-the-Day: Finishing Touches Date: Fri, 09 Apr 1999 15:01:47 -0400 Sender: owner-tcp-impl@lerc.nasa.gov Precedence: bulk FYI... ------- Forwarded Message To: IETF-Announce:;@ietf.org Subject: RFC 2582 on NewReno Modification to TCP's Fast Recovery Cc: rfc-ed@ISI.EDU Date: Fri, 09 Apr 1999 10:37:58 -0700 From: RFC Editor - --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2582: Title: The NewReno Modification to TCP's Fast Recovery Algorithm Author(s): S. Floyd, T. Henderson Status: Experimental Date: April 1999 Mailbox: floyd@acm.org, tomh@cs.berkeley.edu Pages: 12 Characters: 29393 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-tcpimpl-newreno-02.txt URL: ftp://ftp.isi.edu/in-notes/rfc2582.txt RFC 2001 documents the following four intertwined TCP congestion control algorithms: Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery. RFC 2581 explicitly allows certain modifications of these algorithms, including modifications that use the TCP Selective Acknowledgement (SACK) option, and modifications that respond to "partial acknowledgments" (ACKs which cover new data, but not all the data outstanding when loss was detected) in the absence of SACK. This document describes a specific algorithm for responding to partial acknowledgments, referred to as NewReno. This response to partial acknowledgments was first proposed by Janey Hoe. This document is the product of the TCP Implementation Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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 Alegre Ramos 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: <990409103016.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2582 - --OtherAccess Content-Type: Message/External-body; name="rfc2582.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <990409103016.RFC@RFC-EDITOR.ORG> - --OtherAccess-- - --NextPart-- ------- End of Forwarded Message From owner-tcp-impl@lerc.nasa.gov Thu Apr 15 15:14:22 1999 Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12290 for ; Thu, 15 Apr 1999 15:14:21 -0400 (EDT) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id LAA12074 for tcp-impl-outgoing; Thu, 15 Apr 1999 11:34:59 -0400 (EDT) Received: from ietf.org (fw01.lerc.nasa.gov [139.88.145.14]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id LAA10859 for ; Thu, 15 Apr 1999 11:30:00 -0400 (EDT) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03321; Thu, 15 Apr 1999 11:29:55 -0400 (EDT) Message-Id: <199904151529.LAA03321@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: tcp-impl@grc.nasa.gov From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-tcpimpl-pmtud-01.txt Date: Thu, 15 Apr 1999 11:29:55 -0400 Sender: owner-tcp-impl@lerc.nasa.gov Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the TCP Implementation Working Group of the IETF. Title : TCP Problems with Path MTU Discovery Author(s) : K. Lahey Filename : draft-ietf-tcpimpl-pmtud-01.txt Pages : 14 Date : 14-Apr-99 This memo catalogs several known TCP implementation problems dealing with Path MTU Discovery [RFC1191], including the long-standing black hole problem, stretch ACKs due to confusion between MSS and segment size, and MSS advertisement based on PMTU. The goal in doing so is to improve conditions in the existing Internet by enhancing the quality of current TCP/IP implementations. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-tcpimpl-pmtud-01.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-tcpimpl-pmtud-01.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-tcpimpl-pmtud-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <19990414163906.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-tcpimpl-pmtud-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-tcpimpl-pmtud-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19990414163906.I-D@ietf.org> --OtherAccess-- --NextPart-- From owner-tcp-impl@lerc.nasa.gov Fri Apr 16 21:14:03 1999 Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18941 for ; Fri, 16 Apr 1999 21:14:02 -0400 (EDT) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id SAA21349 for tcp-impl-outgoing; Fri, 16 Apr 1999 18:04:54 -0400 (EDT) Received: from mtiwmhc05.worldnet.att.net (fw01.lerc.nasa.gov [139.88.145.14]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id RAA20299 for ; Fri, 16 Apr 1999 17:59:09 -0400 (EDT) Received: from joe-s-hp ([12.79.24.210]) by mtiwmhc05.worldnet.att.net (InterMail v03.02.07 118 124) with SMTP id <19990416215908.EGOS27267@joe-s-hp> for ; Fri, 16 Apr 1999 21:59:08 +0000 Message-ID: <000401be8853$cca9dd60$0b01a8c0@joe-s-hp> Reply-To: "Joseph P. Gleason" From: "Joseph P. Gleason" To: Subject: Job Posting Date: Fri, 16 Apr 1999 17:49:35 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-tcp-impl@lerc.nasa.gov Precedence: bulk Content-Transfer-Encoding: 8bit Dear We are seeking Network Protocol Experts for permanent positions in Piscataway NJ and wondered if you have any suggestions on where we might post our job description to reach such candidates. Any thoughts or direction you might have to offer will be most appreciated. The job description is presented below for your information. Thank you, Joe Gleason ____________________________ Job Description for KR011200JPG Network Protocol (TCP/IP and IPX) Expert Permanent Location: Piscataway, NJ Responsibilities will involve research and leading the porting and development effort of IP/IPX protocol stacks and related modules. Requirements: A BSCS or MSCS, and at least 5 years related experience. You should have in-depth expertise in the development and porting of IP & IPX protocol stacks including gateway / router protocols, address resolution protocols (ARP, RARP, BOOTP) and name server protocols (DNS, DHCP). Knowledge of NetBIOS & NetBEUI protocols and services like Firewalls and VPN ’s is a plus. Knowledge of ATM, Frame Relay and related protocols is a plus. Our client's products enable a convergence of advanced data, Internet, telephony and video communications services, vastly reducing the cost and time to network providers to offer traditional services while enabling them to deploy new highly differentiable services. They are focusing on the development of a new class of advanced, software-rich, programmable multi-service platforms for the network edge, which will allow network service providers to create unique differentiable service offerings to their business customers. Our client offers excellent compensation, benefits, and an employee incentive plan that will grow in value as the Company itself grows. Please refer to Job #KR011200JPG when replying. Contacts: Ann Boschetti, Les Faulkner, or Joe Gleason The KOHL Group, Inc. (973) 984-2214 email: kohlgroup@worldnet.att.net ___________________________________ Joseph P. Gleason, V.P. Technical Services The KOHL Group, Inc. 1719 Route 10, Suite 315 Parsippany, NJ 07054 Ph (973) 984-2214; Fax (973) 984-8489 Email: JPGLEASON@worldnet.att.net From owner-tcp-impl@lerc.nasa.gov Mon Apr 26 15:35:32 1999 Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22501 for ; Mon, 26 Apr 1999 15:35:32 -0400 (EDT) Received: (from listserv@localhost) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) id MAA18952 for tcp-impl-outgoing; Mon, 26 Apr 1999 12:17:50 -0400 (EDT) Received: from mailhost.iprg.nokia.com (fw01.lerc.nasa.gov [139.88.145.14]) by lombok-fi.lerc.nasa.gov (NASA LeRC 8.9.1.1/8.9.1) with ESMTP id MAA16718 for ; Mon, 26 Apr 1999 12:10:13 -0400 (EDT) Received: from vienna.iprg.nokia.com (vienna.iprg.nokia.com [205.226.11.35]) by mailhost.iprg.nokia.com (8.8.8/8.6.10) with ESMTP id JAA22395 for ; Mon, 26 Apr 1999 09:10:11 -0700 (PDT) From: Fred Bauer Received: (fred@localhost) by vienna.iprg.nokia.com (8.8.8/8.6.12) id JAA25251 for tcp-impl@lerc.nasa.gov; Mon, 26 Apr 1999 09:10:11 -0700 (PDT) Date: Mon, 26 Apr 1999 09:10:11 -0700 (PDT) Message-Id: <199904261610.JAA25251@vienna.iprg.nokia.com> To: tcp-impl@lerc.nasa.gov Subject: INFOCOM 2000 Call For Papers Sender: owner-tcp-impl@lerc.nasa.gov Precedence: bulk INFOCOM 2000 CALL FOR PAPERS IEEE Infocom 2000 (Israel) http://www.comnet.technion.ac.il/infocom2000 (U.S.A.) http://www.cse.ucsc.edu/~rom/infocom2000 (Japan) http://halo.kuamp.kyoto-u.ac.jp/~infocom (general) http://www.comsoc.org/confs/infocom Dan Panorama Hotel, Tel Aviv, Israel March 26-30, 2000 Sponsored by the IEEE Communications and Computer Societies SCOPE ===== For the last 18 years, Infocom has been the major conference on computer communications and networking, bringing together researchers and implementors of every aspect of data communications and networks presenting the most up-to-date results and achievements in the field. The 19-th annual conference on Computer Communications, Infocom 2000, will be held at the Dan Panorama Hotel in Tel-Aviv, Israel, during the week of March 26-30, 2000. The conference is sponsored by the technical committees on computer communications of the IEEE Communications and Computers Societies. The Infocom 2000 organizing committee is soliciting original papers describing state-of-the-art research and development in all areas of computer networking and data communications. Topics of interest include, but are not limited to, the following: Active Networks Network Management and Control BISDN and ATM Network Reliability Billing and Pricing Network Restoration Congestion and Admission Control Network Signaling Distributed Network Algorithms Network Standards High-Speed Network Protocols Network and Protocol Performance Integrated Control of Networks Optical Networks Intelligent Networks Personal Communications Systems Internet Photonic Switching Internetworking Protocol Design and Analysis Lightwave Networks Quality of Service Mobility Routing and Routing Protocols Multicast/Broadcast Algorithms Security and Privacy Multimedia Protocols Switch Architectures Multimedia Terminals and Systems Testbeds and Measurements Multiple Access Traffic Management and Control Network Architectures Video Networking Network Design and Planning Wireless Networks and Protocols PAPER SUBMISSION ================ Papers must be submitted electronically in the manner and format detailed below. Authors for whom this presents a severe problem should contact one of the technical program committee co-chairs to discuss alternatives. Papers must be formatted according to the IEEE standard format except for the font size, which must be 11pt. To make it easy to adhere to the formatting standard we offer templates and samples for LaTex, MSWord, and FrameMaker (consult at the web pages referenced on top of this message). Submission must be in PDF. However, the committee will also accept Postscript from Latex, FrameMaker, or MSWord source file. Postscript papers must use only standard PostScript fonts: Times Roman, Courier, Symbol, and Helvetica. (Postscript output from MSWord typically does not work on non-Microsoft platforms. The use of the Apple LaserWriter II printer driver is strongly recommended). The above formatted papers can be submitted in a compressed form (gzip, zip, compress). 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 will not be reviewed| (this is roughly ----------------------------------------------------- equivalent to 20 double-spaced pages). Papers must be submitted electronically using the Web site at . This web page contains exact and detailed instructions. The submission process includes providing detailed contact information. To save space authors can omit this information from the paper itself. Authors will receive an immediate notification of the successful receipt of the file containing their paper. Subsequently, a formal notification will be sent after verifying that the paper can be printed successfully. ---------------------------------------------------------------- |Submissions will only be accepted before or on July 1st, 1999.| ---------------------------------------------------------------- Submission deadlines are strict! Papers that have been improperly submitted or improperly formatted by the submission date will not be considered. To avoid last minute problems, authors are encouraged to submit their papers well in advance of the deadline. THE REVIEW PROCESS ================== Each paper will typically be reviewed by three independent reviewers, whose reviews will be relayed to the corresponding author. To facilitate the review process authors will be asked to classify the paper according to a list of categories so that the most appropriate reviewers handle the paper. This year a new step will be introduced into the process whereby authors will have a chance to provide a limited rebuttal on the reviews before the program committee makes its final decision. TRAVEL GRANTS ============= Limited travel assistance to students, post-docs and junior faculty for defraying some of the costs of presenting a paper in the conference will be available. Please refer to the conference web sites for further details later this year. IMPORTANT DATES =============== Complete paper due July 1, 1999 Notification of acceptance October 31, 1999 Final version due December 3, 1999 PROGRAM COMMITTEE CO-CHAIRS [infocom@comnet.technion.ac.il] =========================== Raphael Rom, Technion, Israel Henning Schulzrinne, Columbia University, USA