This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-tsvwg-rsvp-proxy-proto.
Abstract:
Resource Reservation Protocol (RSVP) signaling can be used to make end-to-end
resource reservations in an IP network in order to guarantee the Quality of Service (QoS) required
by certain flows. With conventional 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. Where the receiver is not RSVP-
capable, an RSVP router may behave as an RSVP Receiver Proxy, thereby performing RSVP signaling on
behalf of the receiver. This allows resource reservations to be established on the segment of the
end-to- end path from the sender to the RSVP Receiver Proxy. However, as discussed
in the companion document "RSVP Proxy Approaches", RSVP extensions are needed
to facilitate operations with an RSVP Receiver Proxy whose signaling is triggered by
receipt of RSVP Path messages from the sender. This document specifies these extensions.
[STANDARDS-TRACK]
Authors:
Ashok Narayanan <ashokn@cisco.com>
Le Faucheur <allan.guillou@sfr.com>
Jukka Manner <jukka.manner@tkk.fi>
Francois Le Faucheur <flefauch@cisco.com>
Le Faucheur <allan.guillou@sfr.com>
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)
datatracker.ietf.org