RFC 3918 on Methodology for IP Multicast Benchmarking

rfc-editor@rfc-editor.org Tue, 05 October 2004 00:15 UTC

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 UAA10686; Mon, 4 Oct 2004 20:15:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEd84-0008SH-3N; Mon, 04 Oct 2004 20:24:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEcvt-0000b9-TO; Mon, 04 Oct 2004 20:11:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CEcm6-0006zb-Gv; Mon, 04 Oct 2004 20:01:50 -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 UAA09415; Mon, 4 Oct 2004 20:01:48 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CEcvH-0005vk-FB; Mon, 04 Oct 2004 20:11:19 -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 i9500TJ12802; Mon, 4 Oct 2004 17:00:29 -0700 (PDT)
Message-Id: <200410050000.i9500TJ12802@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: Mon, 04 Oct 2004 17:00:29 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: bmwg@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 3918 on Methodology for IP Multicast Benchmarking
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a

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


        RFC 3918

        Title:      Methodology for IP Multicast Benchmarking
        Author(s):  D. Stopp, B. Hickman
        Status:     Informational
        Date:       October 2004
        Mailbox:    debby@ixiacom.com, brooks.hickman@spirentcom.com
        Pages:      31
        Characters: 64652
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-bmwg-mcastm-14.txt

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


The purpose of this document is to describe methodology specific to
the benchmarking of multicast IP forwarding devices.  It builds upon
the tenets set forth in RFC 2544, RFC 2432 and other IETF
Benchmarking Methodology Working Group (BMWG) efforts.  This
document seeks to extend these efforts to the multicast paradigm.

The BMWG produces two major classes of documents: Benchmarking
Terminology documents and Benchmarking Methodology documents.  The
Terminology documents present the benchmarks and other related
terms.  The Methodology documents define the procedures required to
collect the benchmarks cited in the corresponding Terminology
documents.

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/rfc3918.txt"><ftp://ftp.isi.edu/in-notes/rfc3918.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce