[bmwg] RFC 8219 on Benchmarking Methodology for IPv6 Transition Technologies

rfc-editor@rfc-editor.org Sat, 12 August 2017 23:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D123B13240F; Sat, 12 Aug 2017 16:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s4jR1QIYfN9d; Sat, 12 Aug 2017 16:56:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04047132408; Sat, 12 Aug 2017 16:56:28 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 504BBB818BC; Sat, 12 Aug 2017 16:56:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, bmwg@ietf.org
Message-Id: <20170812235611.504BBB818BC@rfc-editor.org>
Date: Sat, 12 Aug 2017 16:56:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/fIKYDu2A9aHvvM0O96Hb4E11WHI>
Subject: [bmwg] RFC 8219 on Benchmarking Methodology for IPv6 Transition Technologies
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Aug 2017 23:56:30 -0000

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

        
        RFC 8219

        Title:      Benchmarking Methodology for IPv6 Transition 
                    Technologies 
        Author:     M. Georgescu, 
                    L. Pislaru,
                    G. Lencse
        Status:     Informational
        Stream:     IETF
        Date:       August 2017
        Mailbox:    marius.georgescu@rcs-rds.ro, 
                    liviu.pislaru@rcs-rds.ro, 
                    lencse@sze.hu
        Pages:      30
        Characters: 66085
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bmwg-ipv6-tran-tech-benchmarking-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8219

        DOI:        10.17487/RFC8219

Benchmarking methodologies that address the performance of
network interconnect devices that are IPv4- or IPv6-capable exist,
but the IPv6 transition technologies are outside of their scope.
This document provides complementary guidelines for evaluating the
performance of IPv6 transition technologies.  More specifically,
this document targets IPv6 transition technologies that employ
encapsulation or translation mechanisms, as dual-stack nodes can be
tested using the recommendations of RFCs 2544 and 5180.
The methodology also includes a metric for benchmarking load
scalability.

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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC