Subject: Fw: RFC 4883 on Benchmarking Terminology for Resource ReservationCapable Routers

From: "Adrian Farrel" <[email-masked]>
Date: Thu, 26 Jul 2007 21:40:47 +0100

This is not intended to be directly relevant to us, but some of you may be 
interested to consider the direction and possible implications for RSVP-TE.

Adrian
----- Original Message ----- 
From: <[email-masked]>
To: <[email-masked]>; <[email-masked]>
Cc: <[email-masked]>; <[email-masked]>
Sent: Wednesday, July 25, 2007 5:01 PM
Subject: RFC 4883 on Benchmarking Terminology for Resource 
ReservationCapable Routers

> A new Request for Comments is now available in online RFC libraries.
>
>        RFC 4883
>
>        Title:      Benchmarking Terminology for Resource Reservation
>                    Capable Routers
>        Author:     G. Feher, K. Nemeth,
>                    A. Korn, I. Cselenyi
>        Status:     Informational
>        Date:       July 2007
>        Mailbox:    [email-masked],
>                    [email-masked],
>                    [email-masked],
>                    [email-masked]
>
>        Pages:      24
>        Characters: 54205
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-ietf-bmwg-benchres-term-08.txt
>        URL:        http://www.rfc-editor.org/rfc/rfc4883.txt
>
> The primary purpose of this document is to define terminology
> specific to the benchmarking of resource reservation signaling of
> Integrated Services (IntServ) IP routers.  These terms can be used in
> additional documents that define benchmarking methodologies for
> routers that support resource reservation or reporting formats for
> the benchmarking measurements.