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