RSVP Proxy Approaches
draft-lefaucheur-tsvwg-rsvp-proxy-00

 
Document Type Replaced Internet-Draft (individual)
Last updated 2007-02-28 (latest revision 2006-10-16)
Replaced by draft-ietf-tsvwg-rsvp-proxy-proto
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tsvwg-rsvp-proxy-proto
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-lefaucheur-tsvwg-rsvp-proxy-00.txt

Abstract

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.

Authors

Francois Le Faucheur (flefauch@cisco.com)

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