Subject: RFC 4883 on Benchmarking Terminology for Resource Reservation Capable Routers

From: [email-masked]
Date: Wed, 25 Jul 2007 09:01:07 -0700 (PDT)

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.  This memo provides information for the Internet community.

This document is a product of the Benchmarking Methodology

Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community. 

It does not specify an Internet standard of any kind. Distribution

of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.

Requests to be added to or deleted from the IETF distribution list

should be sent to [email-masked].  Requests to be

added to or deleted from the RFC-DIST distribution list should

be sent to [email-masked].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending

an EMAIL message to [email-masked] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email-masked]

        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the

author of the RFC in question, or to [email-masked].  Unless

specifically noted otherwise on the RFC itself, all RFCs are for

unlimited distribution.

Submissions for Requests for Comments should be sent to

[email-masked].  Please consult RFC 2223, Instructions to RFC

Authors, for further information.

The RFC Editor Team

USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ietf-announce