[AAA-DOCTORS] FW: Evaluation: draft-ietf-tsvwg-rsvp-proxy-proto-08.txt to Proposed Standard

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Sun, 03 May 2009 15:46 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: aaa-doctors@core3.amsl.com
Delivered-To: aaa-doctors@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B1FF3A6F52; Sun, 3 May 2009 08:46:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99+at64Pcnu0; Sun, 3 May 2009 08:46:26 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 2B2883A70E2; Sun, 3 May 2009 08:46:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.40,287,1238990400"; d="scan'208";a="144738661"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 03 May 2009 11:47:20 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 03 May 2009 11:47:19 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 03 May 2009 17:44:41 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A040165A163@307622ANEX5.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Evaluation: draft-ietf-tsvwg-rsvp-proxy-proto-08.txt to Proposed Standard
Thread-Index: AcnIz2NWeZrN3qgqT+SzG7SuiT/gjADNqJeg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: aaa-doctors@ietf.org, ops-dir@ietf.org
Subject: [AAA-DOCTORS] FW: Evaluation: draft-ietf-tsvwg-rsvp-proxy-proto-08.txt to Proposed Standard
X-BeenThere: aaa-doctors@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: AAA Doctors E-mail List <aaa-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aaa-doctors>
List-Post: <mailto:aaa-doctors@ietf.org>
List-Help: <mailto:aaa-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aaa-doctors>, <mailto:aaa-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 May 2009 15:46:27 -0000

 


A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-rsvp-proxy-proto-08
.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.

Note to RFC Editor
 
 (Insert note to RFC Editor here)

IESG Note

 (Insert IESG Note here)

IANA Note

 (Insert IANA Note here)