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

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Internet Architecture Board <iab@iab.org>,
    RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'RSVP Extensions for Path-Triggered RSVP Receiver Proxy' to Proposed Standard

The IESG has approved the following document:

- 'RSVP Extensions for Path-Triggered RSVP Receiver Proxy '
   <draft-ietf-tsvwg-rsvp-proxy-proto-11.txt> as a Proposed Standard


This document is the product of the Transport Area Working Group. 

The IESG contact person is Lars Eggert.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-proto-11.txt

Technical Summary
                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 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.
                
                The Proto document defines the RSVP extensions that are 
                needed to facilitate operations with an RSVP Receiver 
                Proxy whose signaling is triggered by receipt of RSVP 
                Path messages from the sender.  

Working Group Summary
             The consensus for the publication was strong but from a 
             small group within the WG.

Document Quality
             The shepherd doesn't know of any implementations. The 
             documents could have benefited from wider review.

Personnel
             WG Shepherd and responsible AD is Magnus Westerlund.