datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

Resource Reservation Protocol (RSVP) Extensions for Path-Triggered RSVP Receiver Proxy
RFC 5946

Internet Engineering Task Force (IETF)                    F. Le Faucheur
Request for Comments: 5946                                         Cisco
Updates: 2205                                                  J. Manner
Category: Standards Track                               Aalto University
ISSN: 2070-1721                                             A. Narayanan
                                                                   Cisco
                                                              A. Guillou
                                                                     SFR
                                                                H. Malik
                                                                  Airtel
                                                            October 2010

            Resource Reservation Protocol (RSVP) Extensions
                 for Path-Triggered RSVP Receiver Proxy

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc5946.

Le Faucheur, et al.          Standards Track                    [Page 1]
RFC 5946             RSVP Receiver Proxy Extensions         October 2010

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Le Faucheur, et al.          Standards Track                    [Page 2]
RFC 5946             RSVP Receiver Proxy Extensions         October 2010

Table of Contents

   1. Introduction ....................................................4
      1.1. Conventions Used in This Document ..........................7
   2. Terminology .....................................................7
   3. RSVP Extensions for Sender Notification .........................8
      3.1. Sender Notification via PathErr Message ...................11
           3.1.1. Composition of SESSION and Sender Descriptor .......14
           3.1.2. Composition of ERROR_SPEC ..........................14

[include full document text]