Skip to main content

RSVP Proxy Approaches

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author François Le Faucheur
Last updated 2007-02-28 (Latest revision 2006-10-16)
Replaced by RFC 5946
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tsvwg-rsvp-proxy-proto
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:


RSVP signaling can be used to make end-to-end resource reservations in an IP network in order to guarantee the QoS required by certain flows. With RSVP, both the data sender and receiver of a given flow take part in RSVP signaling. Yet, there are many use cases where resource reservation is required, but the receiver, the sender, or both, is not RSVP-capable. This document defines RSVP Proxy behaviors allowing RSVP routers to perform RSVP signaling on behalf of a receiver or a sender that is not RSVP-capable. This allows resource reservations to be established on parts of the end-to-end path.


François Le Faucheur

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