home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_i
/
draft-ietf-intserv-ctrl-load-svc-05.txt
< prev
next >
Wrap
Text File
|
1997-10-02
|
2KB
|
69 lines
A new Request for Comments is now available in online RFC libraries.
RFC 2211
Title: Specification of the Controlled-Load Network
Element Service
Author: J. Wroclawski
Status: Proposed Standard
Date: September 1997
Mailbox: jtw@lcs.mit.edu
Pages: 19
Characters: 46523
Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2211.txt
This memo specifies the network element behavior required to
deliver Controlled-Load service in the Internet. Controlled-load
service provides the client data flow with a quality of service
closely approximating the QoS that same flow would receive from an
unloaded network element, but uses capacity (admission) control to
assure that this service is received even when the network element
is overloaded.
This document is a product of the Integrated Services
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@ISI.EDU.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@ISI.EDU
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 admin@DS.INTERNIC.NET. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1543, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute