From owner-issll@mercury.lcs.mit.edu Thu May 4 22:32:15 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25604 for ; Thu, 4 May 2000 22:32:14 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id UAA03914 for issll-outgoing; Thu, 4 May 2000 20:08:37 -0400 (EDT) Received: from mail.resumecard.com (IDENT:root@host220.resumecard.com [4.17.135.220]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id UAA03937 for ; Thu, 4 May 2000 20:08:35 -0400 (EDT) Received: from nt4wk02 (host210.resumecard.com [4.17.135.210]) by mail.resumecard.com (8.9.3/8.8.7) with SMTP id SAA29842; Thu, 4 May 2000 18:58:36 -0400 Reply-To: From: "Pamela Johnson" To: Date: Thu, 4 May 2000 19:33:59 -0400 Message-ID: <00c301bfb621$58386490$6d0110ac@resumecard.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk Content-Transfer-Encoding: 7bit (You are receiving this email because you have been identified as a user who may benefit from this special career information. You are NOT on a mailing list and will NOT receive any more emails if you do not reply.) Hi, I'm writing to tell you about ResumeCARD.com - the Internet's first site dedicated to career networking. At ResumeCARD.com we've organized all the tools and services you need to market yourself and help yourself stand-out. Because you've been identified for this special promotion, we are offering you a limited time FREE offer... *** EMAIL us your RESUME ***** and we will BUILD YOU: 1) an interactive HTML RESUME complete with your own URL (resumecard.com/YOUR_NAME) AND 2) send you FREE 100 PERSONALIZED RESUMECARDS (ResumeCARDs are networking cards with your contact information and unique URL linking contacts DIRECTLY to your online resume) (Of course, you can always build your own ResumePAGE yourself at www.resumecard.com and we'll still send you your 100 FREE ResumeCARDs. We just thought we'd help take the labor out of it...) --> To see a sample ResumePAGE visit: www.resumecard.com/thuggins --> For more information click here: http://www.resumecard.com/why.asp ***** Email your resume to mailto:pamela.johnson@resumecard.com (PC MS WORD or ASCII/TEXT format preferred) ***** Thank you for your time, Pamela ====================== ResumeCARD.com, Inc. www.resumecard.com How to Network ---------------------- From owner-issll@mercury.lcs.mit.edu Tue May 9 15:03:35 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28249 for ; Tue, 9 May 2000 15:03:35 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id NAA02481 for issll-outgoing; Tue, 9 May 2000 13:20:48 -0400 (EDT) Received: from scooby.lineone.net ([194.75.152.224]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id NAA02466; Tue, 9 May 2000 13:20:40 -0400 (EDT) Received: from ukd ([195.171.177.9]) by scooby.lineone.net (8.9.3/8.9.3) with SMTP id QAA06295; Tue, 9 May 2000 16:50:29 +0100 (BST) Message-ID: <014f01bfb9cf$8fae5900$09b1abc3@ukd> From: "Formacompany" To: "Finance Director" Subject: Instant on-line credit reports Date: Tue, 9 May 2000 16:56:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk Content-Transfer-Encoding: 7bit Do you need fast accurate information to assist you when appraising potential customers, and suppliers? The UK Data internet website www.ukdata.com contains 28 million pages of data with full information on every UK company! Credit Reports-Director Searches-Accounts-Annual Returns All of these products and many more are available to you immediately, and can be downloaded to and printed from your personal computer. Free samples of all reports are available at www.ukdata.com. Please also visit www.formacompany.co.uk the on-line company formation website Thank You Charles Fletcher www.ukdata.com an instant report on every UK business www.formacompany.co.uk the on-line company formation site www.irishdata.ie - instant reports on all Irish companies From owner-issll@mercury.lcs.mit.edu Thu May 11 19:41:31 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11087 for ; Thu, 11 May 2000 19:41:30 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id SAA02867 for issll-outgoing; Thu, 11 May 2000 18:28:31 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id SAA02871 for ; Thu, 11 May 2000 18:28:29 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA15740; Thu, 11 May 2000 15:28:25 -0700 (PDT) Message-Id: <200005112228.PAA15740@boreas.isi.edu> To: IETF-Announce: ; Subject: RFC 2814 on SBM (Subnet Bandwidth Manager) Cc: rfc-ed@isi.edu, issll@mercury.lcs.mit.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 11 May 2000 15:28:25 -0700 From: RFC Editor Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2814 Title: SBM (Subnet Bandwidth Manager): A Protocol for RSVP-based Admission Control over IEEE 802-style networks Author(s): R. Yavatkar, D. Hoffman, Y. Bernet, F. Baker, M. Speer Status: Standards Track Date: May 2000 Mailbox: yavatkar@ibeam.intel.com, yoramb@microsoft.com, fred@cisco.com, speer@Eng.Sun.COM Pages: 60 Characters: 141886 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2814.txt This document describes a signaling method and protocol for RSVP-based admission control over IEEE 802-style LANs. The protocol is designed to work both with the current generation of IEEE 802 LANs as well as with the recent work completed by the IEEE 802.1 committee. This document is a product of the Integrated Services Over Specific Link Layers Working Group of the IETF. This is now a Propsed 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: <000511152559.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2814 --OtherAccess Content-Type: Message/External-body; name="rfc2814.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000511152559.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Thu May 11 19:42:35 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11104 for ; Thu, 11 May 2000 19:42:35 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id SAA02896 for issll-outgoing; Thu, 11 May 2000 18:31:12 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id SAA02887 for ; Thu, 11 May 2000 18:31:11 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA15956; Thu, 11 May 2000 15:31:08 -0700 (PDT) Message-Id: <200005112231.PAA15956@boreas.isi.edu> To: IETF-Announce: ; Subject: RFC 2815 on Int-Serv Mappings on IEEE 802 Networks Cc: rfc-ed@isi.edu, issll@mercury.lcs.mit.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 11 May 2000 15:31:08 -0700 From: RFC Editor Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2815 Title: Integrated Service Mappings on IEEE 802 Networks Author(s): M. Seaman, A. Smith, E. Crawley, J. Wroclawski Status: Standards Track Date: May 2000 Mailbox: mick@telseon.com, andrew@extremenetworks.com, esc@unispheresolutions.com, jtw@lcs.mit.edu Pages: 17 Characters: 42403 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2815.txt This document describes mappings of IETF Integrated Services over LANs built from IEEE 802 network segments which may be interconnected by IEEE 802.1D MAC Bridges (switches). It describes parameter mappings for supporting Controlled Load and Guaranteed Service using the inherent capabilities of relevant IEEE 802 technologies and, in particular, 802.1D-1998 queuing features in switches. These mappings are one component of the Integrated Services over IEEE 802 LANs framework. This document is a product of the Integrated Services Over Specific Link Layers 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: <000511152855.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2815 --OtherAccess Content-Type: Message/External-body; name="rfc2815.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000511152855.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Thu May 11 19:42:39 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11115 for ; Thu, 11 May 2000 19:42:39 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id SAA02892 for issll-outgoing; Thu, 11 May 2000 18:34:09 -0400 (EDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id SAA02898 for ; Thu, 11 May 2000 18:34:07 -0400 (EDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA16402; Thu, 11 May 2000 15:34:06 -0700 (PDT) Message-Id: <200005112234.PAA16402@boreas.isi.edu> To: rfc-dist@rfc-editor.org Subject: RFC 2816 on Framework for Int-Serv Over IEEE 802 LAN Cc: rfc-ed@isi.edu, issll@mercury.lcs.mit.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 11 May 2000 15:34:06 -0700 From: RFC Editor Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2816 Title: A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies Author(s): A. Ghanwani, J. Pace, V. Srinivasan, A. Smith, M. Seaman Status: Informational Date: May 2000 Mailbox: aghanwan@nortelnetworks.com, pacew@us.ibm.com, vijay@cosinecom.com, andrew@extremenetworks.com, mick@telseon.com Pages: 47 Characters: 119043 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2816.txt This memo describes a framework for supporting IETF Integrated Services on shared and switched LAN infrastructure. It includes background material on the capabilities of IEEE 802 like networks with regard to parameters that affect Integrated Services such as access latency, delay variation and queuing support in LAN switches. It discusses aspects of IETF's Integrated Services model that cannot easily be accommodated in different LAN environments. It outlines a functional model for supporting the Resource Reservation Protocol (RSVP) in such LAN environments. Details of extensions to RSVP for use over LANs are described in an accompanying memo [14]. Mappings of the various Integrated Services onto IEEE 802 LANs are described in another memo [13]. This document is a product of the Integrated Services Over Specific Link Layers Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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: <000511153200.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2816 --OtherAccess Content-Type: Message/External-body; name="rfc2816.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000511153200.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Sun May 14 20:28:49 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12496 for ; Sun, 14 May 2000 20:28:47 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id TAA02183 for issll-outgoing; Sun, 14 May 2000 19:19:14 -0400 (EDT) Received: from ssmtp01.melange.isp (smtp.arrakis.es [212.59.199.83]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id TAA02177 for ; Sun, 14 May 2000 19:19:12 -0400 (EDT) Received: from ssmtp01.melange.isp ([127.0.0.1]) by ssmtp01.melange.isp (Netscape Messaging Server 4.15) with SMTP id FUKONU06.B6E for ; Mon, 15 May 2000 01:16:42 +0200 Received: from zephyr.isi.edu ([128.9.160.160]) by ssmtp04.melange.isp (Netscape Messaging Server 4.15) with ESMTP id FUF9UL03.NS5 for ; Fri, 12 May 2000 02:08:45 +0100 Received: (from majordom@localhost) by zephyr.isi.edu (8.8.7/8.8.6) id PAA26578 for rfc-dist-outgoing; Thu, 11 May 2000 15:33:39 -0700 (PDT) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id PAA26571 for ; Thu, 11 May 2000 15:33:37 -0700 (PDT) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA16402; Thu, 11 May 2000 15:34:06 -0700 (PDT) Message-Id: <200005112234.PAA16402@boreas.isi.edu> To: rfc-dist@rfc-editor.org Subject: RFC 2816 on Framework for Int-Serv Over IEEE 802 LAN Cc: rfc-ed@isi.edu, issll@mercury.lcs.mit.edu Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 11 May 2000 15:34:06 -0700 From: RFC Editor Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A new Request for Comments is now available in online RFC libraries. RFC 2816 Title: A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies Author(s): A. Ghanwani, J. Pace, V. Srinivasan, A. Smith, M. Seaman Status: Informational Date: May 2000 Mailbox: aghanwan@nortelnetworks.com, pacew@us.ibm.com, vijay@cosinecom.com, andrew@extremenetworks.com, mick@telseon.com Pages: 47 Characters: 119043 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2816.txt This memo describes a framework for supporting IETF Integrated Services on shared and switched LAN infrastructure. It includes background material on the capabilities of IEEE 802 like networks with regard to parameters that affect Integrated Services such as access latency, delay variation and queuing support in LAN switches. It discusses aspects of IETF's Integrated Services model that cannot easily be accommodated in different LAN environments. It outlines a functional model for supporting the Resource Reservation Protocol (RSVP) in such LAN environments. Details of extensions to RSVP for use over LANs are described in an accompanying memo [14]. Mappings of the various Integrated Services onto IEEE 802 LANs are described in another memo [13]. This document is a product of the Integrated Services Over Specific Link Layers Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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: <000511153200.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2816 --OtherAccess Content-Type: Message/External-body; name="rfc2816.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000511153200.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- From owner-issll@mercury.lcs.mit.edu Mon May 15 13:42:42 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07735 for ; Mon, 15 May 2000 13:42:39 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id MAA01734 for issll-outgoing; Mon, 15 May 2000 12:13:21 -0400 (EDT) Received: from relay.faa.gov (relay.faa.gov [204.108.10.6]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id MAA01754 for ; Mon, 15 May 2000 12:13:09 -0400 (EDT) Received: from faa.gov ([192.168.254.2]) by relay.faa.gov (Pro-8.9.3/Pro-8.9.3) with SMTP id MAA20752; Mon, 15 May 2000 12:05:35 -0400 (EDT) Received: from POP3 Client by faa.gov (ccMail Link to SMTP R8.20.00.25) id AA958396463; Mon, 15 May 2000 12:10:00 -0500 Message-Id: <0005159583.AA958396463@faa.gov> X-Mailer: ccMail Link to SMTP R8.20.00.25 Date: Thu, 11 May 2000 15:34:06 -0500 From: RFC Editor To: Cc: , , , Subject: RFC 2816 on Framework for Int-Serv Over IEEE 802 LAN MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="simple boundary" Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --simple boundary Content-Type: text/plain; charset=US-ASCII Content-Description: "cc:Mail Note Part" Content-Transfer-Encoding: 7bit A new Request for Comments is now available in online RFC libraries. RFC 2816 Title: A Framework for Integrated Services Over Shared and Switched IEEE 802 LAN Technologies Author(s): A. Ghanwani, J. Pace, V. Srinivasan, A. Smith, M. Seaman Status: Informational Date: May 2000 Mailbox: aghanwan@nortelnetworks.com, pacew@us.ibm.com, vijay@cosinecom.com, andrew@extremenetworks.com, mick@telseon.com Pages: 47 Characters: 119043 Updates/Obsoletes/SeeAlso: None URL: ftp://ftp.isi.edu/in-notes/rfc2816.txt This memo describes a framework for supporting IETF Integrated Services on shared and switched LAN infrastructure. It includes background material on the capabilities of IEEE 802 like networks with regard to parameters that affect Integrated Services such as access latency, delay variation and queuing support in LAN switches. It discusses aspects of IETF's Integrated Services model that cannot easily be accommodated in different LAN environments. It outlines a functional model for supporting the Resource Reservation Protocol (RSVP) in such LAN environments. Details of extensions to RSVP for use over LANs are described in an accompanying memo [14]. Mappings of the various Integrated Services onto IEEE 802 LANs are described in another memo [13]. This document is a product of the Integrated Services Over Specific Link Layers Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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. --simple boundary Content-Type: text/plain; charset=US-ASCII Content-Description: "cc:Mail Note Part" Content-Transfer-Encoding: 7bit --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <000511153200.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc2816 --OtherAccess Content-Type: Message/External-body; name="rfc2816.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <000511153200.RFC@RFC-EDITOR.ORG> --OtherAccess-- --simple boundary-- From owner-issll@mercury.lcs.mit.edu Tue May 23 21:23:36 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14253 for ; Tue, 23 May 2000 21:23:36 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id UAA01609 for issll-outgoing; Tue, 23 May 2000 20:22:08 -0400 (EDT) Received: from photon.idirect.com (photon.idirect.com [207.136.80.123]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id UAA04476 for ; Tue, 23 May 2000 20:22:06 -0400 (EDT) From: offshore1444@yahoo.com Received: from bc-vic-a53-02-38.look.ca ([216.66.129.134] helo=look.ca) by photon.idirect.com with smtp (Exim 3.12 #9) id 12r5U9-0006sK-00; Mon, 15 May 2000 01:59:37 +0500 Reply-To: offshore1444@yahoo.com To: offshore1444@yahoo.com Subject: Tired of the 9 to 5 Yet? Message-Id: Date: Mon, 15 May 2000 01:59:37 +0500 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk Ladies and Gentlemen, We thought this might be of interest to you because we received your commercial email, or you were referred to us as someone interested in business opportunities. WE PROMPTLY HONOR ALL REMOVE REQUESTS. To be removed from all future mailings, please reply with REMOVE in the subject heading Do you have the desire to make $2000 to $5000 PLUS PER WEEK, beginning almost immediately? How does $10,000 TO $20,000 PLUS PER MONTH, and a realistic STRONG SIX FIGURES this year sound? And, how about generating all of this by just sharing information? This is NOT, Lotions, Potions, Pills, Water Filters, Shopping Clubs, Long Distance Services. No Hype, No Meetings, No MLM! There Is No One Else Doing What We're Doing! If you can bring desire and an honest effort to the table, we can show you how to NEVER WORRY ABOUT MONEY AGAIN! Opportunity is truly knocking! To find out more, call Toll Free. 1-800-636-6773 ext 3886 God bless From owner-issll@mercury.lcs.mit.edu Thu May 25 07:55:26 2000 Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04703 for ; Thu, 25 May 2000 07:55:25 -0400 (EDT) Received: (from daemon@localhost) by mercury.lcs.mit.edu (8.9.1/8.9.1) id GAA06701 for issll-outgoing; Thu, 25 May 2000 06:35:04 -0400 (EDT) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by mercury.lcs.mit.edu (8.9.1/8.9.1) with ESMTP id GAA06695 for ; Thu, 25 May 2000 06:35:02 -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 GAA02863; Thu, 25 May 2000 06:35:02 -0400 (EDT) Message-Id: <200005251035.GAA02863@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: issll@mercury.lcs.mit.edu From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-issll-diffserv-rsvp-05.txt Date: Thu, 25 May 2000 06:35:02 -0400 Sender: owner-issll@mercury.lcs.mit.edu Precedence: bulk --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Integrated Services over Specific Link Layers Working Group of the IETF. Title : A Framework For Integrated Services Operation Over Diffserv Networks Author(s) : Y. Bernet, R. Yavatkar, P. Ford, F. Baker, L. Zhang, M. Speer, B. Braden, B. Davie, J. Wroclawski, E. Felstaine Filename : draft-ietf-issll-diffserv-rsvp-05.txt Pages : 27 Date : 24-May-00 The Integrated Services architecture provides a means for the delivery of end-to-end QoS to applications over heterogeneous networks. To support this end-to-end model, the Intserv architecture must be supported over a wide variety of different types of network elements. In this context, a network that supports Differentiated Services (Diffserv) may be viewed as a network element in the total end-to-end path. This document describes a framework by which Integrated Services may be supported over Diffserv networks. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-issll-diffserv-rsvp-05.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-issll-diffserv-rsvp-05.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-issll-diffserv-rsvp-05.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: <20000524104340.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-issll-diffserv-rsvp-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-issll-diffserv-rsvp-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000524104340.I-D@ietf.org> --OtherAccess-- --NextPart--