An Evaluation on RSVP Transport Mechanism
draft-pan-nsis-rsvp-transport-01

Document Type Expired Internet-Draft (individual)
Authors Ping Pan  , Henning Schulzrinne 
Last updated 2003-03-05
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-pan-nsis-rsvp-transport-01.txt

Abstract

In this memo, we look into some of the transport-layer design issues in the original RSVP as defined in RFC2205 [RFC2205]. Based on the observation, we conclude that the current RSVP transport mechanism may not be adequate to support some applications. We recommend to use a different transport layer protocol such as TCP for next-generation signaling protocols.

Authors

Ping Pan (pan@watson.ibm.com)
Henning Schulzrinne (hgs+geopriv@cs.columbia.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)