RFC 5180 on IPv6 Benchmarking Methodology for Network Interconnect Devices

rfc-editor@rfc-editor.org Mon, 19 May 2008 23:36 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF8BA3A6B87; Mon, 19 May 2008 16:36:16 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A0DE3A6B5D; Mon, 19 May 2008 16:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
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 B6gHy7KQ5lkg; Mon, 19 May 2008 16:36:14 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 4987F3A6A62; Mon, 19 May 2008 16:36:14 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 75A4112BB55; Mon, 19 May 2008 16:36:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5180 on IPv6 Benchmarking Methodology for Network Interconnect Devices
From: rfc-editor@rfc-editor.org
Message-Id: <20080519233615.75A4112BB55@bosco.isi.edu>
Date: Mon, 19 May 2008 16:36:15 -0700
Cc: bmwg@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5180

        Title:      IPv6 Benchmarking Methodology for Network 
                    Interconnect Devices 
        Author:     C. Popoviciu, A. Hamza,
                    G. Van de Velde, D. Dugatkin
        Status:     Informational
        Date:       May 2008
        Mailbox:    cpopovic@cisco.com, 
                    ahamza@cisco.com, 
                    gunter@cisco.com,
                    diego@fastsoft.com
        Pages:      20
        Characters: 41712
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bmwg-ipv6-meth-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5180.txt

The benchmarking methodologies defined in RFC 2544 are IP version
independent.  However, RFC 2544 does not address some of the
specificities of IPv6.  This document provides additional
benchmarking guidelines, which in conjunction with RFC 2544, lead to a
more complete and realistic evaluation of the IPv6 performance of
network interconnect devices.  IPv6 transition mechanisms are outside
the scope of this document.  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 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.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce