Skip to main content

An Evaluation on RSVP Transport Mechanism

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

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


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.


Ping Pan
Henning Schulzrinne

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