Browse Prior Art Database

Resource ReSerVation Protocol (RSVP) -- Version 1 Applicability Statement Some Guidelines on Deployment (RFC2208)

IP.com Disclosure Number: IPCOM000002766D
Original Publication Date: 1997-Sep-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 5 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Mankin: AUTHOR [+9]

Abstract

This document describes the applicability of RSVP along with the Integrated Services protocols and other components of resource reservation and offers guidelines for deployment of resource reservation at this time. This document accompanies the first submission of RSVP and integrated services specifications onto the Internet standards track.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 22% of the total text.

Network Working Group A. Mankin, Ed.

Request for Comments: 2208 USC/ISI

Category: Informational F. Baker

Cisco Systems

B. Braden

USC/ISI

S. Bradner

Harvard

M. O`Dell

UUNET Technologies

A. Romanow

Sun Microsystems

A. Weinrib

Intel Corporation

L. Zhang

UCLA

September 1997

Resource ReSerVation Protocol (RSVP)

Version 1 Applicability Statement

Some Guidelines on Deployment

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 describes the applicability of RSVP along with the

Integrated Services protocols and other components of resource

reservation and offers guidelines for deployment of resource

reservation at this time. This document accompanies the first

submission of RSVP and integrated services specifications onto the

Internet standards track.

1. Introduction

RSVP [RFC 2205] is a unicast and multicast signalling protocol,

designed to install and maintain reservation state information at

each router along the path of a stream of data. The state handled by

RSVP is defined by services [RFC 2211] and [RFC 2212] specified by

the Integrated Services WG. These services and RSVP are being

introduced to the IETF's standards track jointly. From henceforth,

the acronym RSVP on its own is used as a shorthand for the signalling

protocol combined with the integrated service specifications.

RSVP must be used in conjunction with several additional components,

described in Table 1.

Table 1 Additional Components of Resource Reservation

1. Message formats in which parameters for desired services can be

expressed. A proposed standard set of these formats is specified

in [RFC 2210].

2. Router and host mechanisms (e.g. packet classification and

scheduling, admission control algorithms) to implement one or

both of the models [RFC 2211] and [RFC 2212], which are al...