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-svc-template-03.txt
< prev
next >
Wrap
Text File
|
1997-10-02
|
3KB
|
68 lines
A new Request for Comments is now available in online RFC libraries.
RFC 2216
Title: Network Element Service Specification Template
Author: S. Shenker, J. Wroclawski
Status: Informational
Date: September 1997
Mailbox: shenker@parc.xerox.com, jtw@lcs.mit.edu
Pages: 22
Characters: 53655
Updates/Obsoletes: None
URL: ftp://ds.internic.net/rfc/rfc2216.txt
This document defines a framework for specifying services provided
by network elements, and available to applications, in an
internetwork which offers multiple qualities of service. The
document first provides some necessary context -- including
relevant definitions and suggested data formats -- and then
specifies a "template" which service specification documents
should follow. The specification template includes per-element
requirements such as the service's packet handling behavior,
parameters required and made available by the service, traffic
specification and policing requirements, and traffic ordering
relationships. It also includes evaluation criteria for elements
providing the service, and examples of how the service might be
implemented (by network elements) and used (by applications).
This document is a product of the Integrated Services
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@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