Browse Prior Art Database

Network Element Service Specification Template (RFC2216)

IP.com Disclosure Number: IPCOM000002774D
Original Publication Date: 1997-Sep-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 22 page(s) / 32K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Shenker: AUTHOR [+1]

Related Documents

10.17487/RFC2216: DOI

Abstract

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. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 6% of the total text.

Network Working Group S. Shenker Request for Comments: 2216 J. Wroclawski Category: Informational Xerox PARC/MIT LCS September 1997

Network Element Service Specification Template

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Abstract

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).

Introduction

This document defines the framework used to specify the functionality of internetwork system components which support the the ability to provide multiple, dynamically selectable qualities of service to applications using an internetwork. The behavior of individual routers and subnetworks is captured as a set of "services", some or all of which may be offered by each element. The concatenation of these services along the end-to-end data paths used by an application provides overall quality of service control.

The definition of a service states what is required of a router (or, more generally, any network element; a router, switch, subnet, etc.) which supports a particular service. The service definition also

Shenker & Wroclawski Informational [Page 1]

RFC 2216 Network Element Service Template September 1997

specifies parameters used to invoke the service, the relationship between those parameters and the service delivered, and the end-to- end behavior obtained by concatenating several instances of the service.

Each service definition also specifies the interface between that service and the environment. This includes the parameters needed to invoke the service, informational parameters which the service must make available for use by setup, routing, and management mechanisms, and information which should be carried between end-nodes and network elements by those mechanisms in order to achieve the desired end-to- end behavior. However, a service definition does not describe the specific protocols or mechanisms used to establish state in the network elements for flows that use the described service.

Services defined following the guidelines of this document are intended for use both within the global Internet and private IP networks. In certain cases a concatenation of network element se...

Processing...
Loading...