FW: RFC 2815 on Int-Serv Mappings on IEEE 802 Networks
fyi.
Jim Carlo(jcarlo@ti.com) Cellular:1-214-693-1776 Voice&Fax:1-214-853-5274
TI Fellow, Networking Standards at Texas Instruments
Chair, ISO/IEC JTC1/SC6 Telecom and Info Exchange Between Systems
Chair, IEEE802 LAN/MAN Standards Committee
-----Original Message-----
From: owner-issll@mercury.lcs.mit.edu
[mailto:owner-issll@mercury.lcs.mit.edu] On Behalf Of RFC Editor
Sent: Thursday, May 11, 2000 5:31 PM
To: IETF-Announce: ;
Cc: rfc-ed@isi.edu; issll@mercury.lcs.mit.edu
Subject: RFC 2815 on Int-Serv Mappings on IEEE 802 Networks
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.