[bmwg] RFC 4062 on OSPF Benchmarking Terminology and Concepts

rfc-editor@rfc-editor.org Thu, 28 April 2005 19:56 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DRF7a-0000Em-Gb; Thu, 28 Apr 2005 15:56:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DQZQb-0003Cw-Pg; Tue, 26 Apr 2005 19:25:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01085; Tue, 26 Apr 2005 19:25:14 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQZd9-0002LU-Cc; Tue, 26 Apr 2005 19:38:15 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j3QNMO612526; Tue, 26 Apr 2005 16:22:24 -0700 (PDT)
Message-Id: <200504262322.j3QNMO612526@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 26 Apr 2005 16:22:24 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
X-Mailman-Approved-At: Thu, 28 Apr 2005 15:56:24 -0400
Cc: bmwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [bmwg] RFC 4062 on OSPF Benchmarking Terminology and Concepts
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
Sender: bmwg-bounces@ietf.org
Errors-To: bmwg-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.


        RFC 4062

        Title:      OSPF Benchmarking Terminology and Concepts
        Author(s):  V. Manral, R. White, A. Shaikh
        Status:     Informational
        Date:       April 2005
        Mailbox:    vishwas@sinett.com, riw@cisco.com,
                    ashaikh@research.att.com
        Pages:      9
        Characters: 15784
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-bmwg-ospfconv-term-10.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4062.txt


This document explains the terminology and concepts used in OSPF
benchmarking.  Although some of these terms may be defined elsewhere
(and we will refer the reader to those definitions in some cases) we
include discussions concerning these terms, as they relate
specifically to the tasks involved in benchmarking the OSPF protocol.


This document is a product of the Benchmarking Methodology Working
Group of the IETF.

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 IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        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 RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc4062.txt"><ftp://ftp.isi.edu/in-notes/rfc4062.txt>
_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg