<pre>Internet Engineering Task Force (IETF)                      M. Georgescu
Request for Comments: 8219                                    L. Pislaru
Category: Informational                                          RCS&amp;RDS
ISSN: 2070-1721                                                G. Lencse
                                             Szechenyi Istvan University
                                                             August 2017


       <span class="h1">Benchmarking Methodology for IPv6 Transition Technologies</span>

Abstract

   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.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc8219">http://www.rfc-editor.org/info/rfc8219</a>.














<span class="grey">Georgescu, et al.             Informational                     [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.





































<span class="grey">Georgescu, et al.             Informational                     [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-4">4</a>
      <a href="#section-1.1">1.1</a>. IPv6 Transition Technologies ...............................<a href="#page-4">4</a>
   <a href="#section-2">2</a>. Conventions Used in This Document ...............................<a href="#page-6">6</a>
   <a href="#section-3">3</a>. Terminology .....................................................<a href="#page-7">7</a>
   <a href="#section-4">4</a>. Test Setup ......................................................<a href="#page-7">7</a>
      <a href="#section-4.1">4.1</a>. Single-Translation Transition Technologies .................<a href="#page-8">8</a>
      4.2. Encapsulation and Double-Translation Transition
           Technologies ...............................................<a href="#page-8">8</a>
   <a href="#section-5">5</a>. Test Traffic ....................................................<a href="#page-9">9</a>
      <a href="#section-5.1">5.1</a>. Frame Formats and Sizes ....................................<a href="#page-9">9</a>
           <a href="#section-5.1.1">5.1.1</a>. Frame Sizes to Be Used over Ethernet ...............<a href="#page-10">10</a>
      <a href="#section-5.2">5.2</a>. Protocol Addresses ........................................<a href="#page-10">10</a>
      <a href="#section-5.3">5.3</a>. Traffic Setup .............................................<a href="#page-10">10</a>
   <a href="#section-6">6</a>. Modifiers ......................................................<a href="#page-11">11</a>
   <a href="#section-7">7</a>. Benchmarking Tests .............................................<a href="#page-11">11</a>
      <a href="#section-7.1">7.1</a>. Throughput ................................................<a href="#page-11">11</a>
      <a href="#section-7.2">7.2</a>. Latency ...................................................<a href="#page-11">11</a>
      <a href="#section-7.3">7.3</a>. Packet Delay Variation ....................................<a href="#page-13">13</a>
           <a href="#section-7.3.1">7.3.1</a>. PDV ................................................<a href="#page-13">13</a>
           <a href="#section-7.3.2">7.3.2</a>. IPDV ...............................................<a href="#page-14">14</a>
      <a href="#section-7.4">7.4</a>. Frame Loss Rate ...........................................<a href="#page-15">15</a>
      <a href="#section-7.5">7.5</a>. Back-to-Back Frames .......................................<a href="#page-15">15</a>
      <a href="#section-7.6">7.6</a>. System Recovery ...........................................<a href="#page-15">15</a>
      <a href="#section-7.7">7.7</a>. Reset .....................................................<a href="#page-15">15</a>
   8. Additional Benchmarking Tests for Stateful IPv6 Transition
      Technologies ...................................................<a href="#page-15">15</a>
      <a href="#section-8.1">8.1</a>. Concurrent TCP Connection Capacity ........................<a href="#page-15">15</a>
      <a href="#section-8.2">8.2</a>. Maximum TCP Connection Establishment Rate .................<a href="#page-15">15</a>
   <a href="#section-9">9</a>. DNS Resolution Performance .....................................<a href="#page-15">15</a>
      <a href="#section-9.1">9.1</a>. Test and Traffic Setup ....................................<a href="#page-16">16</a>
      <a href="#section-9.2">9.2</a>. Benchmarking DNS Resolution Performance ...................<a href="#page-17">17</a>
           <a href="#section-9.2.1">9.2.1</a>. Requirements for the Tester ........................<a href="#page-18">18</a>
   <a href="#section-10">10</a>. Overload Scalability ..........................................<a href="#page-19">19</a>
      <a href="#section-10.1">10.1</a>. Test Setup ...............................................<a href="#page-19">19</a>
           <a href="#section-10.1.1">10.1.1</a>. Single-Translation Transition Technologies ........<a href="#page-19">19</a>
           10.1.2. Encapsulation and Double-Translation
                   Transition Technologies ...........................<a href="#page-20">20</a>
      <a href="#section-10.2">10.2</a>. Benchmarking Performance Degradation .....................<a href="#page-21">21</a>
           10.2.1. Network Performance Degradation with
                   Simultaneous Load .................................<a href="#page-21">21</a>
           10.2.2. Network Performance Degradation with
                   Incremental Load ..................................<a href="#page-22">22</a>
   <a href="#section-11">11</a>. NAT44 and NAT66 ...............................................<a href="#page-22">22</a>
   <a href="#section-12">12</a>. Summarizing Function and Variation ............................<a href="#page-23">23</a>
   <a href="#section-13">13</a>. Security Considerations .......................................<a href="#page-23">23</a>
   <a href="#section-14">14</a>. IANA Considerations ...........................................<a href="#page-24">24</a>



<span class="grey">Georgescu, et al.             Informational                     [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   <a href="#section-15">15</a>. References ....................................................<a href="#page-24">24</a>
      <a href="#section-15.1">15.1</a>. Normative References .....................................<a href="#page-24">24</a>
      <a href="#section-15.2">15.2</a>. Informative References ...................................<a href="#page-25">25</a>
   <a href="#appendix-A">Appendix A</a>. Theoretical Maximum Frame Rates........................<a href="#page-29">29</a>
   Acknowledgements...................................................<a href="#page-30">30</a>
   Authors' Addresses ................................................<a href="#page-30">30</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The methodologies described in [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>] and [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] help vendors
   and network operators alike analyze the performance of IPv4 and
   IPv6-capable network devices.  The methodology presented in [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>]
   is mostly IP version independent, while [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] contains
   complementary recommendations that are specific to the latest IP
   version, IPv6.  However, [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] does not cover IPv6 transition
   technologies.

   IPv6 is not backwards compatible, which means that IPv4-only nodes
   cannot directly communicate with IPv6-only nodes.  To solve this
   issue, IPv6 transition technologies have been proposed and
   implemented.

   This document presents benchmarking guidelines dedicated to IPv6
   transition technologies.  The benchmarking tests can provide insights
   about the performance of these technologies, which can act as useful
   feedback for developers and network operators going through the IPv6
   transition process.

   The document also includes an approach to quantify performance when
   operating in overload.  Overload scalability can be defined as a
   system's ability to gracefully accommodate a greater number of flows
   than the maximum number of flows that the Device Under Test (DUT) can
   operate normally.  The approach taken here is to quantify the
   overload scalability by measuring the performance created by an
   excessive number of network flows and comparing performance to the
   non-overloaded case.

<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>.  IPv6 Transition Technologies</span>

   Two of the basic transition technologies, dual IP layer (also known
   as dual stack) and encapsulation, are presented in [<a href="./rfc4213" title="&quot;Basic Transition Mechanisms for IPv6 Hosts and Routers&quot;">RFC4213</a>].
   IPv4/IPv6 translation is presented in [<a href="./rfc6144" title="&quot;Framework for IPv4/IPv6 Translation&quot;">RFC6144</a>].  Most of the
   transition technologies employ at least one variation of these
   mechanisms.  In this context, a generic classification of the
   transition technologies can prove useful.






<span class="grey">Georgescu, et al.             Informational                     [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   We can consider a production network transitioning to IPv6 as being
   constructed using the following IP domains:

   o  Domain A: IPvX-specific domain

   o  Core domain: IPvY-specific or dual-stack (IPvX and IPvY) domain

   o  Domain B: IPvX-specific domain

   Note: X,Y are part of the set {4,6}, and X is NOT EQUAL to Y.

   The transition technologies can be categorized according to the
   technology used for traversal of the core domain:

   1.  Dual stack: Devices in the core domain implement both IP
       protocols.

   2.  Single translation: In this case, the production network is
       assumed to have only two domains: Domain A and the core domain.
       The core domain is assumed to be IPvY specific.  IPvX packets are
       translated to IPvY at the edge between Domain A and the core
       domain.

   3.  Double translation: The production network is assumed to have all
       three domains; Domains A and B are IPvX specific, while the core
       domain is IPvY specific.  A translation mechanism is employed for
       the traversal of the core network.  The IPvX packets are
       translated to IPvY packets at the edge between Domain A and the
       core domain.  Subsequently, the IPvY packets are translated back
       to IPvX at the edge between the core domain and Domain B.

   4.  Encapsulation: The production network is assumed to have all
       three domains; Domains A and B are IPvX specific, while the core
       domain is IPvY specific.  An encapsulation mechanism is used to
       traverse the core domain.  The IPvX packets are encapsulated to
       IPvY packets at the edge between Domain A and the core domain.
       Subsequently, the IPvY packets are de-encapsulated at the edge
       between the core domain and Domain B.

   The performance of dual-stack transition technologies can be fully
   evaluated using the benchmarking methodologies presented by [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>]
   and [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>].  Consequently, this document focuses on the other
   three categories: single-translation, double-translation, and
   encapsulation transition technologies.

   Another important aspect by which IPv6 transition technologies can be
   categorized is their use of stateful or stateless mapping algorithms.
   The technologies that use stateful mapping algorithms (e.g., Stateful



<span class="grey">Georgescu, et al.             Informational                     [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   NAT64 [<a href="./rfc6146" title="&quot;Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers&quot;">RFC6146</a>]) create dynamic correlations between IP addresses or
   {IP address, transport protocol, transport port number} tuples, which
   are stored in a state table.  For ease of reference, IPv6 transition
   technologies that employ stateful mapping algorithms will be called
   "stateful IPv6 transition technologies".  The efficiency with which
   the state table is managed can be an important performance indicator
   for these technologies.  Hence, additional benchmarking tests are
   RECOMMENDED for stateful IPv6 transition technologies.

   Table 1 contains the generic categories and associations with some of
   the IPv6 transition technologies proposed in the IETF.  Please note
   that the list is not exhaustive.

      +---+--------------------+------------------------------------+
      |   | Generic category   | IPv6 Transition Technology         |
      +---+--------------------+------------------------------------+
      | 1 | Dual stack         | Dual IP Layer Operations [<a href="./rfc4213" title="&quot;Basic Transition Mechanisms for IPv6 Hosts and Routers&quot;">RFC4213</a>] |
      +---+--------------------+------------------------------------+
      | 2 | Single translation | NAT64 [<a href="./rfc6146" title="&quot;Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers&quot;">RFC6146</a>], IVI [<a href="./rfc6219" title="&quot;The China Education and Research Network (CERNET) IVI Translation Design and Deployment for the IPv4/IPv6 Coexistence and Transition&quot;">RFC6219</a>]     |
      +---+--------------------+------------------------------------+
      | 3 | Double translation | 464XLAT [<a href="./rfc6877" title="&quot;464XLAT: Combination of Stateful and Stateless Translation&quot;">RFC6877</a>], MAP-T [<a href="./rfc7599" title="&quot;Mapping of Address and Port using Translation (MAP-T)&quot;">RFC7599</a>] |
      +---+--------------------+------------------------------------+
      | 4 | Encapsulation      | DS-Lite [<a href="./rfc6333" title="&quot;Dual- Stack Lite Broadband Deployments Following IPv4 Exhaustion&quot;">RFC6333</a>], MAP-E [<a href="./rfc7597" title="&quot;Mapping of Address and Port with Encapsulation (MAP-E)&quot;">RFC7597</a>],|
      |   |                    | Lightweight 4over6 [<a href="./rfc7596" title="&quot;Lightweight 4over6: An Extension to the Dual- Stack Lite Architecture&quot;">RFC7596</a>],      |
      |   |                    | 6rd [<a href="./rfc5569" title="&quot;IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)&quot;">RFC5569</a>], 6PE [<a href="./rfc4798" title="&quot;Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)&quot;">RFC4798</a>],      |
      |   |                    | 6VPE [<a href="./rfc4659" title="&quot;BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN&quot;">RFC4659</a>]                     |
      +---+--------------------+------------------------------------+

            Table 1: IPv6 Transition Technologies Categories

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Conventions Used in This Document</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in <a href="https://www.rfc-editor.org/bcp/bcp14">BCP</a>
   <a href="https://www.rfc-editor.org/bcp/bcp14">14</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>] [<a href="./rfc8174" title="&quot;Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words&quot;">RFC8174</a>] when, and only when, they appear in all
   capitals, as shown here.

   Although these terms are usually associated with protocol
   requirements, in this document, the terms are requirements for users
   and systems that intend to implement the test conditions and claim
   conformance with this specification.









<span class="grey">Georgescu, et al.             Informational                     [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Terminology</span>

   A number of terms used in this memo have been defined in other RFCs.
   Please refer to the RFCs below for definitions, testing procedures,
   and reporting formats.

   o  Throughput (Benchmark) [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>]

   o  Frame Loss Rate (Benchmark) [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>]

   o  Back-to-Back Frames (Benchmark) [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>]

   o  System Recovery (Benchmark) [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>]

   o  Reset (Benchmark) [<a href="./rfc6201" title="&quot;Device Reset Characterization&quot;">RFC6201</a>]

   o  Concurrent TCP Connection Capacity (Benchmark) [<a href="./rfc3511" title="&quot;Benchmarking Methodology for Firewall Performance&quot;">RFC3511</a>]

   o  Maximum TCP Connection Establishment Rate (Benchmark) [<a href="./rfc3511" title="&quot;Benchmarking Methodology for Firewall Performance&quot;">RFC3511</a>]

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Test Setup</span>

   The test environment setup options recommended for benchmarking IPv6
   transition technologies are very similar to the ones presented in
   <a href="./rfc2544#section-6">Section&nbsp;6 of [RFC2544]</a>.  In the case of the Tester setup, the options
   presented in [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>] and [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] can be applied here as well.
   However, the DUT setup options should be explained in the context of
   the targeted categories of IPv6 transition technologies: single
   translation, double translation, and encapsulation.

   Although both single Tester and sender/receiver setups are applicable
   to this methodology, the single Tester setup will be used to describe
   the DUT setup options.

   For the test setups presented in this memo, dynamic routing SHOULD be
   employed.  However, the presence of routing and management frames can
   represent unwanted background data that can affect the benchmarking
   result.  To that end, the procedures defined in Sections <a href="#section-11.2">11.2</a> and
   11.3 of [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>] related to routing and management frames SHOULD be
   used here.  Moreover, the "trial description" recommendations
   presented in <a href="./rfc2544#section-23">Section&nbsp;23 of [RFC2544]</a> are also valid for this memo.

   In terms of route setup, the recommendations of <a href="./rfc2544#section-13">Section&nbsp;13 of
   [RFC2544]</a> are valid for this document, assuming that IPv6-capable
   routing protocols are used.






<span class="grey">Georgescu, et al.             Informational                     [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  Single-Translation Transition Technologies</span>

   For the evaluation of single-translation transition technologies, a
   single DUT setup (see Figure 1) SHOULD be used.  The DUT is
   responsible for translating the IPvX packets into IPvY packets.  In
   this context, the Tester device SHOULD be configured to support both
   IPvX and IPvY.

                           +--------------------+
                           |                    |
              +------------|IPvX   Tester   IPvY|&lt;-------------+
              |            |                    |              |
              |            +--------------------+              |
              |                                                |
              |            +--------------------+              |
              |            |                    |              |
              +-----------&gt;|IPvX     DUT    IPvY|--------------+
                           |                    |
                           +--------------------+

                        Figure 1: Test Setup 1 (Single DUT)

<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Encapsulation and Double-Translation Transition Technologies</span>

   For evaluating the performance of encapsulation and double-
   translation transition technologies, a dual DUT setup (see Figure 2)
   SHOULD be employed.  The Tester creates a network flow of IPvX
   packets.  The first DUT is responsible for the encapsulation or
   translation of IPvX packets into IPvY packets.  The IPvY packets are
   de-encapsulated/translated back to IPvX packets by the second DUT and
   forwarded to the Tester.

                           +--------------------+
                           |                    |
     +---------------------|IPvX   Tester   IPvX|&lt;------------------+
     |                     |                    |                   |
     |                     +--------------------+                   |
     |                                                              |
     |      +--------------------+      +--------------------+      |
     |      |                    |      |                    |      |
     +-----&gt;|IPvX    DUT 1  IPvY |-----&gt;|IPvY   DUT 2   IPvX |------+
            |                    |      |                    |
            +--------------------+      +--------------------+

                         Figure 2: Test Setup 2 (Dual DUT)






<span class="grey">Georgescu, et al.             Informational                     [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   One of the limitations of the dual DUT setup is the inability to
   reflect asymmetries in behavior between the DUTs.  Considering this,
   additional performance tests SHOULD be performed using the single DUT
   setup.

   Note: For encapsulation IPv6 transition technologies in the single
   DUT setup, the Tester SHOULD be able to send IPvX packets
   encapsulated as IPvY in order to test the de-encapsulation
   efficiency.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Test Traffic</span>

   The test traffic represents the experimental workload and SHOULD meet
   the requirements specified in this section.  The requirements are
   dedicated to unicast IP traffic.  Multicast IP traffic is outside of
   the scope of this document.

<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>.  Frame Formats and Sizes</span>

   [<a id="ref-RFC5180">RFC5180</a>] describes the frame size requirements for two commonly used
   media types: Ethernet and SONET (Synchronous Optical Network).
   [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>] also covers other media types, such as token ring and Fiber
   Distributed Data Interface (FDDI).  The recommendations of those two
   documents can be used for the dual-stack transition technologies.
   For the rest of the transition technologies, the frame overhead
   introduced by translation or encapsulation MUST be considered.

   The encapsulation/translation process generates different size frames
   on different segments of the test setup.  For instance, the single-
   translation transition technologies will create different frame sizes
   on the receiving segment of the test setup, as IPvX packets are
   translated to IPvY.  This is not a problem if the bandwidth of the
   employed media is not exceeded.  To prevent exceeding the limitations
   imposed by the media, the frame size overhead needs to be taken into
   account when calculating the maximum theoretical frame rates.  The
   calculation method for the Ethernet, as well as a calculation
   example, are detailed in <a href="#appendix-A">Appendix A</a>.  The details of the media
   employed for the benchmarking tests MUST be noted in all test
   reports.

   In the context of frame size overhead, MTU recommendations are needed
   in order to avoid frame loss due to MTU mismatch between the virtual
   encapsulation/translation interfaces and the physical network
   interface controllers (NICs).  To avoid this situation, the larger
   MTU between the physical NICs and virtual encapsulation/translation
   interfaces SHOULD be set for all interfaces of the DUT and Tester.





<span class="grey">Georgescu, et al.             Informational                     [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   To be more specific, the minimum IPv6 MTU size (1280 bytes) plus the
   encapsulation/translation overhead is the RECOMMENDED value for the
   physical interfaces as well as virtual ones.

<span class="h4"><a class="selflink" id="section-5.1.1" href="#section-5.1.1">5.1.1</a>.  Frame Sizes to Be Used over Ethernet</span>

   Based on the recommendations of [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>], the following frame sizes
   SHOULD be used for benchmarking IPvX/IPvY traffic on Ethernet links:
   64, 128, 256, 512, 768, 1024, 1280, 1518, 1522, 2048, 4096, 8192, and
   9216.

   For Ethernet frames exceeding 1500 bytes in size, the [<a href="#ref-IEEE802.1AC">IEEE802.1AC</a>]
   standard can be consulted.

   Note: For single-translation transition technologies (e.g., NAT64) in
   the IPv6 -&gt; IPv4 translation direction, 64-byte frames SHOULD be
   replaced by 84-byte frames.  This would allow the frames to be
   transported over media such as the ones described by the [<a href="#ref-IEEE802.1Q">IEEE802.1Q</a>]
   standard.  Moreover, this would also allow the implementation of a
   frame identifier in the UDP data.

   The theoretical maximum frame rates considering an example of frame
   overhead are presented in <a href="#appendix-A">Appendix A</a>.

<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>.  Protocol Addresses</span>

   The selected protocol addresses should follow the recommendations of
   <a href="./rfc5180#section-5">Section&nbsp;5 of [RFC5180]</a> for IPv6 and <a href="./rfc2544#section-12">Section&nbsp;12 of [RFC2544]</a> for IPv4.

   Note: Testing traffic with extension headers might not be possible
   for the transition technologies that employ translation.  Proposed
   IPvX/IPvY translation algorithms such as IP/ICMP translation
   [<a href="./rfc7915" title="&quot;IP/ICMP Translation Algorithm&quot;">RFC7915</a>] do not support the use of extension headers.

<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>.  Traffic Setup</span>

   Following the recommendations of [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>], all tests described
   SHOULD be performed with bidirectional traffic.  Unidirectional
   traffic tests MAY also be performed for a fine-grained performance
   assessment.

   Because of the simplicity of UDP, UDP measurements offer a more
   reliable basis for comparison than other transport-layer protocols.
   Consequently, for the benchmarking tests described in <a href="#section-7">Section 7</a> of
   this document, UDP traffic SHOULD be employed.






<span class="grey">Georgescu, et al.             Informational                    [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   Considering that a transition technology could process both native
   IPv6 traffic and translated/encapsulated traffic, the following
   traffic setups are recommended:

   i)   IPvX only traffic (where the IPvX traffic is to be
        translated/encapsulated by the DUT)
   ii)  90% IPvX traffic and 10% IPvY native traffic
   iii) 50% IPvX traffic and 50% IPvY native traffic
   iv)  10% IPvX traffic and 90% IPvY native traffic

   For the benchmarks dedicated to stateful IPv6 transition
   technologies, included in <a href="#section-8">Section 8</a> of this memo (Concurrent TCP
   Connection Capacity and Maximum TCP Connection Establishment Rate),
   the traffic SHOULD follow the recommendations of Sections <a href="#section-5.2.2.2">5.2.2.2</a> and
   5.3.2.2 of [<a href="./rfc3511" title="&quot;Benchmarking Methodology for Firewall Performance&quot;">RFC3511</a>].

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Modifiers</span>

   The idea of testing under different operational conditions was first
   introduced in <a href="./rfc2544#section-11">Section&nbsp;11 of [RFC2544]</a> and represents an important
   aspect of benchmarking network elements, as it emulates, to some
   extent, the conditions of a production environment.  <a href="./rfc5180#section-6">Section&nbsp;6 of
   [RFC5180]</a> describes complementary test conditions specific to IPv6.
   The recommendations in [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>] and [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] can also be followed
   for testing of IPv6 transition technologies.

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Benchmarking Tests</span>

   The following sub-sections describe all recommended benchmarking
   tests.

<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>.  Throughput</span>

   Use <a href="./rfc2544#section-26.1">Section&nbsp;26.1 of [RFC2544]</a> unmodified.

<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>.  Latency</span>

   Objective: To determine the latency.  Typical latency is based on the
   definitions of latency from [<a href="./rfc1242" title="&quot;Benchmarking Terminology for Network Interconnection Devices&quot;">RFC1242</a>].  However, this memo provides a
   new measurement procedure.

   Procedure: Similar to [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>], the throughput for DUT at each of
   the listed frame sizes SHOULD be determined.  Send a stream of frames
   at a particular frame size through the DUT at the determined
   throughput rate to a specific destination.  The stream SHOULD be at
   least 120 seconds in duration.





<span class="grey">Georgescu, et al.             Informational                    [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   Identifying tags SHOULD be included in at least 500 frames after 60
   seconds.  For each tagged frame, the time at which the frame was
   fully transmitted (timestamp A) and the time at which the frame was
   received (timestamp B) MUST be recorded.  The latency is timestamp B
   minus timestamp A as per the relevant definition from <a href="./rfc1242">RFC 1242</a>,
   namely, latency as defined for store and forward devices or latency
   as defined for bit forwarding devices.

   We recommend encoding the identifying tag in the payload of the
   frame.  To be more exact, the identifier SHOULD be inserted after the
   UDP header.

   From the resulted (at least 500) latencies, two quantities SHOULD be
   calculated.  One is the typical latency, which SHOULD be calculated
   with the following formula:

   TL = Median(Li)

   Where:

   o  TL = the reported typical latency of the stream

   o  Li = the latency for tagged frame i

   The other measure is the worst-case latency, which SHOULD be
   calculated with the following formula:

   WCL = L99.9thPercentile

   Where:

   o  WCL = the reported worst-case latency

   o  L99.9thPercentile = the 99.9th percentile of the stream-measured
      latencies

   The test MUST be repeated at least 20 times with the reported value
   being the median of the recorded values for TL and WCL.

   Reporting Format:  The report MUST state which definition of latency
   (from <a href="./rfc1242">RFC 1242</a>) was used for this test.  The summarized latency
   results SHOULD be reported in the format of a table with a row for
   each of the tested frame sizes.  There SHOULD be columns for the
   frame size, the rate at which the latency test was run for that frame
   size, the media types tested, and the resultant typical latency, and
   the worst-case latency values for each type of data stream tested.
   To account for the variation, the 1st and 99th percentiles of the 20




<span class="grey">Georgescu, et al.             Informational                    [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   iterations MAY be reported in two separated columns.  For a fine-
   grained analysis, the histogram (as exemplified in <a href="./rfc5481#section-4.4">Section&nbsp;4.4 of
   [RFC5481]</a>) of one of the iterations MAY be displayed.

<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>.  Packet Delay Variation</span>

   [<a id="ref-RFC5481">RFC5481</a>] presents two metrics: Packet Delay Variation (PDV) and
   Inter Packet Delay Variation (IPDV).  Measuring PDV is RECOMMENDED;
   for a fine-grained analysis of delay variation, IPDV measurements MAY
   be performed.

<span class="h4"><a class="selflink" id="section-7.3.1" href="#section-7.3.1">7.3.1</a>.  PDV</span>

   Objective: To determine the Packet Delay Variation as defined in
   [<a href="./rfc5481" title="&quot;Packet Delay Variation Applicability Statement&quot;">RFC5481</a>].

   Procedure: As described by [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>], first determine the throughput
   for the DUT at each of the listed frame sizes.  Send a stream of
   frames at a particular frame size through the DUT at the determined
   throughput rate to a specific destination.  The stream SHOULD be at
   least 60 seconds in duration.  Measure the one-way delay as described
   by [<a href="./rfc3393" title="&quot;IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)&quot;">RFC3393</a>] for all frames in the stream.  Calculate the PDV of the
   stream using the formula:

   PDV = D99.9thPercentile - Dmin

   Where:

   o  D99.9thPercentile = the 99.9th percentile (as described in
      [<a href="./rfc5481" title="&quot;Packet Delay Variation Applicability Statement&quot;">RFC5481</a>]) of the one-way delay for the stream

   o  Dmin = the minimum one-way delay in the stream

   As recommended in [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>], the test MUST be repeated at least 20
   times with the reported value being the median of the recorded
   values.  Moreover, the 1st and 99th percentiles SHOULD be calculated
   to account for the variation of the dataset.

   Reporting Format: The PDV results SHOULD be reported in a table with
   a row for each of the tested frame sizes and columns for the frame
   size and the applied frame rate for the tested media types.  Two
   columns for the 1st and 99th percentile values MAY be displayed.
   Following the recommendations of [<a href="./rfc5481" title="&quot;Packet Delay Variation Applicability Statement&quot;">RFC5481</a>], the RECOMMENDED units of
   measurement are milliseconds.







<span class="grey">Georgescu, et al.             Informational                    [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h4"><a class="selflink" id="section-7.3.2" href="#section-7.3.2">7.3.2</a>.  IPDV</span>

   Objective: To determine the Inter Packet Delay Variation as defined
   in [<a href="./rfc5481" title="&quot;Packet Delay Variation Applicability Statement&quot;">RFC5481</a>].

   Procedure: As described by [<a href="./rfc2544" title="&quot;Benchmarking Methodology for Network Interconnect Devices&quot;">RFC2544</a>], first determine the throughput
   for the DUT at each of the listed frame sizes.  Send a stream of
   frames at a particular frame size through the DUT at the determined
   throughput rate to a specific destination.  The stream SHOULD be at
   least 60 seconds in duration.  Measure the one-way delay as described
   by [<a href="./rfc3393" title="&quot;IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)&quot;">RFC3393</a>] for all frames in the stream.  Calculate the IPDV for
   each of the frames using the formula:

   IPDV(i) = D(i) - D(i-1)

   Where:

   o  D(i) = the one-way delay of the i-th frame in the stream

   o  D(i-1) = the one-way delay of (i-1)th frame in the stream

   Given the nature of IPDV, reporting a single number might lead to
   over-summarization.  In this context, the report for each measurement
   SHOULD include three values: Dmin, Dmed, and Dmax.

   Where:

   o  Dmin = the minimum IPDV in the stream

   o  Dmed = the median IPDV of the stream

   o  Dmax = the maximum IPDV in the stream

   The test MUST be repeated at least 20 times.  To summarize the 20
   repetitions, for each of the three (Dmin, Dmed, and Dmax), the median
   value SHOULD be reported.

   Reporting format: The median for the three proposed values SHOULD be
   reported.  The IPDV results SHOULD be reported in a table with a row
   for each of the tested frame sizes.  The columns SHOULD include the
   frame size and associated frame rate for the tested media types and
   sub-columns for the three proposed reported values.  Following the
   recommendations of [<a href="./rfc5481" title="&quot;Packet Delay Variation Applicability Statement&quot;">RFC5481</a>], the RECOMMENDED units of measurement
   are milliseconds.







<span class="grey">Georgescu, et al.             Informational                    [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h3"><a class="selflink" id="section-7.4" href="#section-7.4">7.4</a>.  Frame Loss Rate</span>

   Use <a href="./rfc2544#section-26.3">Section&nbsp;26.3 of [RFC2544]</a> unmodified.

<span class="h3"><a class="selflink" id="section-7.5" href="#section-7.5">7.5</a>.  Back-to-Back Frames</span>

   Use <a href="./rfc2544#section-26.4">Section&nbsp;26.4 of [RFC2544]</a> unmodified.

<span class="h3"><a class="selflink" id="section-7.6" href="#section-7.6">7.6</a>.  System Recovery</span>

   Use <a href="./rfc2544#section-26.5">Section&nbsp;26.5 of [RFC2544]</a> unmodified.

<span class="h3"><a class="selflink" id="section-7.7" href="#section-7.7">7.7</a>.  Reset</span>

   Use <a href="./rfc6201#section-4">Section&nbsp;4 of [RFC6201]</a> unmodified.

<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Additional Benchmarking Tests for Stateful IPv6 Transition</span>
<span class="h2">    Technologies</span>

   This section describes additional tests dedicated to stateful IPv6
   transition technologies.  For the tests described in this section,
   the DUT devices SHOULD follow the test setup and test parameters
   recommendations presented in Sections <a href="#section-5.2">5.2</a> and <a href="#section-5.3">5.3</a> of [<a href="./rfc3511" title="&quot;Benchmarking Methodology for Firewall Performance&quot;">RFC3511</a>].

   The following additional tests SHOULD be performed.

<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>.  Concurrent TCP Connection Capacity</span>

   Use <a href="./rfc3511#section-5.2">Section&nbsp;5.2 of [RFC3511]</a> unmodified.

<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>.  Maximum TCP Connection Establishment Rate</span>

   Use <a href="./rfc3511#section-5.3">Section&nbsp;5.3 of [RFC3511]</a> unmodified.

<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>.  DNS Resolution Performance</span>

   This section describes benchmarking tests dedicated to DNS64 (see
   [<a href="./rfc6147" title="&quot;DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to IPv4 Servers&quot;">RFC6147</a>]), used as DNS support for single-translation technologies
   such as NAT64.












<span class="grey">Georgescu, et al.             Informational                    [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>.  Test and Traffic Setup</span>

   The test setup in Figure 3 follows the setup proposed for single-
   translation IPv6 transition technologies in Figure 1.

      1:AAAA query    +--------------------+
         +------------|                    |&lt;-------------+
         |            |IPv6   Tester   IPv4|              |
         |  +--------&gt;|                    |----------+   |
         |  |         +--------------------+ 3:empty  |   |
         |  | 6:synt'd                         AAAA,  |   |
         |  |   AAAA  +--------------------+ 5:valid A|   |
         |  +---------|                    |&lt;---------+   |
         |            |IPv6     DUT    IPv4|              |
         +-----------&gt;|       (DNS64)      |--------------+
                      +--------------------+ 2:AAAA query, 4:A query

                   Figure 3: Test Setup 3 (DNS64)

   The test traffic SHOULD be composed of the following messages.

   1.  Query for the AAAA record of a domain name (from client to DNS64
       server)

   2.  Query for the AAAA record of the same domain name (from DNS64
       server to authoritative DNS server)

   3.  Empty AAAA record answer (from authoritative DNS server to DNS64
       server)

   4.  Query for the A record of the same domain name (from DNS64 server
       to authoritative DNS server)

   5.  Valid A record answer (from authoritative DNS server to DNS64
       server)

   6.  Synthesized AAAA record answer (from DNS64 server to client)

   The Tester plays the role of DNS client as well as authoritative DNS
   server.  It MAY be realized as a single physical device, or
   alternatively, two physical devices MAY be used.

   Please note that:

   o  If the DNS64 server implements caching and there is a cache hit,
      then step 1 is followed by step 6 (and steps 2 through 5 are
      omitted).




<span class="grey">Georgescu, et al.             Informational                    [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   o  If the domain name has a AAAA record, then it is returned in step
      3 by the authoritative DNS server, steps 4 and 5 are omitted, and
      the DNS64 server does not synthesize a AAAA record but returns the
      received AAAA record to the client.

   o  As for the IP version used between the Tester and the DUT, IPv6
      MUST be used between the client and the DNS64 server (as a DNS64
      server provides service for an IPv6-only client), but either IPv4
      or IPv6 MAY be used between the DNS64 server and the authoritative
      DNS server.

<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>.  Benchmarking DNS Resolution Performance</span>

   Objective: To determine DNS64 performance by means of the maximum
   number of successfully processed DNS requests per second.

   Procedure: Send a specific number of DNS queries at a specific rate
   to the DUT, and then count the replies from the DUT that are received
   in time (within a predefined timeout period from the sending time of
   the corresponding query, having the default value 1 second) and that
   are valid (contain a AAAA record).  If the count of sent queries is
   equal to the count of received replies, the rate of the queries is
   raised, and the test is rerun.  If fewer replies are received than
   queries were sent, the rate of the queries is reduced, and the test
   is rerun.  The duration of each trial SHOULD be at least 60 seconds.
   This will reduce the potential gain of a DNS64 server, which is able
   to exhibit higher performance by storing the requests and thus also
   utilizing the timeout time for answering them.  For the same reason,
   no higher timeout time than 1 second SHOULD be used.  For further
   considerations, see [<a href="#ref-Lencse1" title="&quot;Benchmarking Methodology for DNS64 Servers&quot;">Lencse1</a>].

   The maximum number of processed DNS queries per second is the fastest
   rate at which the count of DNS replies sent by the DUT is equal to
   the number of DNS queries sent to it by the test equipment.

   The test SHOULD be repeated at least 20 times, and the median and
   1st/99th percentiles of the number of processed DNS queries per
   second SHOULD be calculated.

   Details and parameters:

   1.  Caching

       First, all the DNS queries MUST contain different domain names
       (or domain names MUST NOT be repeated before the cache of the DUT
       is exhausted).  Then, new tests MAY be executed when domain names
       are 20%, 40%, 60%, 80%, and 100% cached.  Ensuring that a record




<span class="grey">Georgescu, et al.             Informational                    [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


       is cached requires repeating a domain name both "late enough"
       after the first query to be already resolved and be present in
       the cache and "early enough" to be still present in the cache.

   2.  Existence of a AAAA record

       First, all the DNS queries MUST contain domain names that do not
       have a AAAA record and have exactly one A record.  Then, new
       tests MAY be executed when 20%, 40%, 60%, 80%, and 100% of domain
       names have a AAAA record.

   Please note that the two conditions above are orthogonal; thus, all
   their combinations are possible and MAY be tested.  The testing with
   0% cached domain names and with 0% existing AAAA records is REQUIRED,
   and the other combinations are OPTIONAL.  (When all the domain names
   are cached, then the results do not depend on what percentage of the
   domain names have AAAA records; thus, these combinations are not
   worth testing one by one.)

   Reporting format: The primary result of the DNS64 test is the median
   of the number of processed DNS queries per second measured with the
   above mentioned "0% + 0% combination".  The median SHOULD be
   complemented with the 1st and 99th percentiles to show the stability
   of the result.  If optional tests are done, the median and the 1st
   and 99th percentiles MAY be presented in a two-dimensional table
   where the dimensions are the proportion of the repeated domain names
   and the proportion of the DNS names having AAAA records.  The two
   table headings SHOULD contain these percentage values.
   Alternatively, the results MAY be presented as a corresponding two-
   dimensional graph.  In this case, the graph SHOULD show the median
   values with the percentiles as error bars.  From both the table and
   the graph, one-dimensional excerpts MAY be made at any given fixed-
   percentage value of the other dimension.  In this case, the fixed
   value MUST be given together with a one-dimensional table or graph.

<span class="h4"><a class="selflink" id="section-9.2.1" href="#section-9.2.1">9.2.1</a>.  Requirements for the Tester</span>

   Before a Tester can be used for testing a DUT at rate r queries per
   second with t seconds timeout, it MUST perform a self-test in order
   to exclude the possibility that the poor performance of the Tester
   itself influences the results.  To perform a self-test, the Tester is
   looped back (leaving out DUT), and its authoritative DNS server
   subsystem is configured to be able to answer all the AAAA record
   queries.  To pass the self-test, the Tester SHOULD be able to answer
   AAAA record queries at rate of 2*(r+delta) within a 0.25*t timeout,
   where the value of delta is at least 0.1.





<span class="grey">Georgescu, et al.             Informational                    [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   Explanation: When performing DNS64 testing, each AAAA record query
   may result in at most two queries sent by the DUT: the first for a
   AAAA record and the second for an A record (they are both sent when
   there is no cache hit and also no AAAA record exists).  The
   parameters above guarantee that the authoritative DNS server
   subsystem of the DUT is able to answer the queries at the required
   frequency using up not more than half of the timeout time.

   Note: A sample open-source test program, dns64perf++, is available
   from [<a href="#ref-Dns64perf">Dns64perf</a>] and is documented in [<a href="#ref-Lencse2" title="&quot;Design and Implementation of a Test Program for Benchmarking DNS64 Servers&quot;">Lencse2</a>].  It implements only
   the client part of the Tester and should be used together with an
   authoritative DNS server implementation, e.g., BIND, NSD, or YADIFA.
   Its experimental extension for testing caching is available from
   [<a href="#ref-Lencse3">Lencse3</a>] and is documented in [<a href="#ref-Lencse4" title="&quot;Enabling Dns64perf++ for Benchmarking the Caching Performance of DNS64 Servers&quot;">Lencse4</a>].

<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>.  Overload Scalability</span>

   Scalability has been often discussed; however, in the context of
   network devices, a formal definition or a measurement method has not
   yet been proposed.  In this context, we can define overload
   scalability as the ability of each transition technology to
   accommodate network growth.  Poor scalability usually leads to poor
   performance.  Considering this, overload scalability can be measured
   by quantifying the network performance degradation associated with an
   increased number of network flows.

   The following subsections describe how the test setups can be
   modified to create network growth and how the associated performance
   degradation can be quantified.

<span class="h3"><a class="selflink" id="section-10.1" href="#section-10.1">10.1</a>.  Test Setup</span>

   The test setups defined in <a href="#section-4">Section 4</a> have to be modified to create
   network growth.

<span class="h4"><a class="selflink" id="section-10.1.1" href="#section-10.1.1">10.1.1</a>.  Single-Translation Transition Technologies</span>

   In the case of single-translation transition technologies, the
   network growth can be generated by increasing the number of network
   flows (NFs) generated by the Tester machine (see Figure 4).











<span class="grey">Georgescu, et al.             Informational                    [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


                        +-------------------------+
           +------------|NF1                   NF1|&lt;-------------+
           |  +---------|NF2      Tester       NF2|&lt;----------+  |
           |  |      ...|                         |           |  |
           |  |   +-----|NFn                   NFn|&lt;------+   |  |
           |  |   |     +-------------------------+       |   |  |
           |  |   |                                       |   |  |
           |  |   |     +-------------------------+       |   |  |
           |  |   +----&gt;|NFn                   NFn|-------+   |  |
           |  |      ...|           DUT           |           |  |
           |  +--------&gt;|NF2    (translator)   NF2|-----------+  |
           +-----------&gt;|NF1                   NF1|--------------+
                        +-------------------------+

                 Figure 4: Test Setup 4 (Single DUT with Increased
                              Network Flows)

<span class="h4"><a class="selflink" id="section-10.1.2" href="#section-10.1.2">10.1.2</a>.  Encapsulation and Double-Translation Transition Technologies</span>

   Similarly, for the encapsulation and double-translation transition
   technologies, a multi-flow setup is recommended.  Considering a
   multipoint-to-point scenario, for most transition technologies, one
   of the edge nodes is designed to support more than one connecting
   device.  Hence, the recommended test setup is an n:1 design, where n
   is the number of client DUTs connected to the same server DUT (see
   Figure 5).

                          +-------------------------+
     +--------------------|NF1                   NF1|&lt;--------------+
     |  +-----------------|NF2      Tester       NF2|&lt;-----------+  |
     |  |              ...|                         |            |  |
     |  |   +-------------|NFn                   NFn|&lt;-------+   |  |
     |  |   |             +-------------------------+        |   |  |
     |  |   |                                                |   |  |
     |  |   |    +-----------------+    +---------------+    |   |  |
     |  |   +---&gt;| NFn  DUT n  NFn |---&gt;|NFn         NFn| ---+   |  |
     |  |        +-----------------+    |               |        |  |
     |  |     ...                       |               |        |  |
     |  |        +-----------------+    |     DUT n+1   |        |  |
     |  +-------&gt;| NF2  DUT 2  NF2 |---&gt;|NF2         NF2|--------+  |
     |           +-----------------+    |               |           |
     |           +-----------------+    |               |           |
     +----------&gt;| NF1  DUT 1  NF1 |---&gt;|NF1         NF1|-----------+
                 +-----------------+    +---------------+

                Figure 5: Test Setup 5 (DUAL DUT with Increased
                             Network Flows)




<span class="grey">Georgescu, et al.             Informational                    [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   This test setup can help to quantify the scalability of the server
   device.  However, for testing the overload scalability of the client
   DUTs, additional recommendations are needed.

   For encapsulation transition technologies, an m:n setup can be
   created, where m is the number of flows applied to the same client
   device and n the number of client devices connected to the same
   server device.

   For translation-based transition technologies, the client devices can
   be separately tested with n network flows using the test setup
   presented in Figure 4.

<span class="h3"><a class="selflink" id="section-10.2" href="#section-10.2">10.2</a>.  Benchmarking Performance Degradation</span>

<span class="h4"><a class="selflink" id="section-10.2.1" href="#section-10.2.1">10.2.1</a>.  Network Performance Degradation with Simultaneous Load</span>

   Objective: To quantify the performance degradation introduced by n
   parallel and simultaneous network flows.

   Procedure: First, the benchmarking tests presented in <a href="#section-7">Section 7</a> have
   to be performed for one network flow.

   The same tests have to be repeated for n network flows, where the
   network flows are started simultaneously.  The performance
   degradation of the X benchmarking dimension SHOULD be calculated as
   relative performance change between the 1-flow (single flow) results
   and the n-flow results, using the following formula:

               Xn - X1
       Xpd = ----------- * 100, where: X1 = result for 1-flow
                  X1                   Xn = result for n-flows

   This formula SHOULD be applied only for "lower is better" benchmarks
   (e.g., latency).  For "higher is better" benchmarks (e.g.,
   throughput), the following formula is RECOMMENDED:

               X1 - Xn
       Xpd = ----------- * 100, where: X1 = result for 1-flow
                  X1                   Xn = result for n-flows

   As a guideline for the maximum number of flows n, the value can be
   deduced by measuring the Concurrent TCP Connection Capacity as
   described by [<a href="./rfc3511" title="&quot;Benchmarking Methodology for Firewall Performance&quot;">RFC3511</a>], following the test setups specified by
   <a href="#section-4">Section 4</a>.






<span class="grey">Georgescu, et al.             Informational                    [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   Reporting Format: The performance degradation SHOULD be expressed as
   a percentage.  The number of tested parallel flows n MUST be clearly
   specified.  For each of the performed benchmarking tests, there
   SHOULD be a table containing a column for each frame size.  The table
   SHOULD also state the applied frame rate.  In the case of benchmarks
   for which more than one value is reported (e.g., IPDV, discussed in
   <a href="#section-7.3.2">Section 7.3.2</a>), a column for each of the values SHOULD be included.

<span class="h4"><a class="selflink" id="section-10.2.2" href="#section-10.2.2">10.2.2</a>.  Network Performance Degradation with Incremental Load</span>

   Objective: To quantify the performance degradation introduced by n
   parallel and incrementally started network flows.

   Procedure: First, the benchmarking tests presented in <a href="#section-7">Section 7</a> have
   to be performed for one network flow.

   The same tests have to be repeated for n network flows, where the
   network flows are started incrementally in succession, each after
   time t.  In other words, if flow i is started at time x, flow i+1
   will be started at time x+t.  Considering the time t, the time
   duration of each iteration must be extended with the time necessary
   to start all the flows, namely, (n-1)xt.  The measurement for the
   first flow SHOULD be at least 60 seconds in duration.

   The performance degradation of the x benchmarking dimension SHOULD be
   calculated as relative performance change between the 1-flow results
   and the n-flow results, using the formula presented in
   <a href="#section-10.2.1">Section 10.2.1</a>.  Intermediary degradation points for 1/4*n, 1/2*n,
   and 3/4*n MAY also be performed.

   Reporting Format: The performance degradation SHOULD be expressed as
   a percentage.  The number of tested parallel flows n MUST be clearly
   specified.  For each of the performed benchmarking tests, there
   SHOULD be a table containing a column for each frame size.  The table
   SHOULD also state the applied frame rate and time duration T, which
   is used as an incremental step between the network flows.  The units
   of measurement for T SHOULD be seconds.  A column for the
   intermediary degradation points MAY also be displayed.  In the case
   of benchmarks for which more than one value is reported (e.g., IPDV,
   discussed in <a href="#section-7.3.2">Section 7.3.2</a>), a column for each of the values SHOULD
   be included.

<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>.  NAT44 and NAT66</span>

   Although these technologies are not the primary scope of this
   document, the benchmarking methodology associated with single-
   translation technologies as defined in <a href="#section-4.1">Section 4.1</a> can be employed to




<span class="grey">Georgescu, et al.             Informational                    [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   benchmark implementations that use NAT44 (as defined by [<a href="./rfc2663" title="&quot;IP Network Address Translator (NAT) Terminology and Considerations&quot;">RFC2663</a>]
   with the behavior described by [<a href="./rfc7857" title="&quot;Updates to Network Address Translation (NAT) Behavioral Requirements&quot;">RFC7857</a>]) and implementations that
   use NAT66 (as defined by [<a href="./rfc6296" title="&quot;IPv6-to-IPv6 Network Prefix Translation&quot;">RFC6296</a>]).

<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>.  Summarizing Function and Variation</span>

   To ensure the stability of the benchmarking scores obtained using the
   tests presented in Sections <a href="#section-7">7</a> through <a href="#section-9">9</a>, multiple test iterations are
   RECOMMENDED.  Using a summarizing function (or measure of central
   tendency) can be a simple and effective way to compare the results
   obtained across different iterations.  However, over-summarization is
   an unwanted effect of reporting a single number.

   Measuring the variation (dispersion index) can be used to counter the
   over-summarization effect.  Empirical data obtained following the
   proposed methodology can also offer insights on which summarizing
   function would fit better.

   To that end, data presented in [<a href="#ref-ietf95pres">ietf95pres</a>] indicate the median as a
   suitable summarizing function and the 1st and 99th percentiles as
   variation measures for DNS Resolution Performance and PDV.  The
   median and percentile calculation functions SHOULD follow the
   recommendations of <a href="./rfc2330#section-11.3">Section&nbsp;11.3 of [RFC2330]</a>.

   For a fine-grained analysis of the frequency distribution of the
   data, histograms or cumulative distribution function plots can be
   employed.

<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>.  Security Considerations</span>

   Benchmarking activities as described in this memo are limited to
   technology characterization using controlled stimuli in a laboratory
   environment, with dedicated address space and the constraints
   specified in the sections above.

   The benchmarking network topology will be an independent test setup
   and MUST NOT be connected to devices that may forward the test
   traffic into a production network or misroute traffic to the test
   management network.

   Further, benchmarking is performed on a "black-box" basis, relying
   solely on measurements observable external to the DUT or System Under
   Test (SUT).  Special capabilities SHOULD NOT exist in the DUT/SUT
   specifically for benchmarking purposes.  Any implications for network
   security arising from the DUT/SUT SHOULD be identical in the lab and
   in production networks.





<span class="grey">Georgescu, et al.             Informational                    [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>.  IANA Considerations</span>

   The IANA has allocated the prefix 2001:2::/48 [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] for IPv6
   benchmarking.  For IPv4 benchmarking, the 198.18.0.0/15 prefix was
   reserved, as described in [<a href="./rfc6890" title="&quot;Special-Purpose IP Address Registries&quot;">RFC6890</a>].  The two ranges are sufficient
   for benchmarking IPv6 transition technologies.  Thus, no action is
   requested.

<span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a>.  References</span>

<span class="h3"><a class="selflink" id="section-15.1" href="#section-15.1">15.1</a>.  Normative References</span>

   [<a id="ref-RFC1242">RFC1242</a>]  Bradner, S., "Benchmarking Terminology for Network
              Interconnection Devices", <a href="./rfc1242">RFC 1242</a>, DOI 10.17487/RFC1242,
              July 1991, &lt;<a href="http://www.rfc-editor.org/info/rfc1242">http://www.rfc-editor.org/info/rfc1242</a>&gt;.

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
              DOI 10.17487/RFC2119, March 1997,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.

   [<a id="ref-RFC2330">RFC2330</a>]  Paxson, V., Almes, G., Mahdavi, J., and M. Mathis,
              "Framework for IP Performance Metrics", <a href="./rfc2330">RFC 2330</a>,
              DOI 10.17487/RFC2330, May 1998,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2330">http://www.rfc-editor.org/info/rfc2330</a>&gt;.

   [<a id="ref-RFC2544">RFC2544</a>]  Bradner, S. and J. McQuaid, "Benchmarking Methodology for
              Network Interconnect Devices", <a href="./rfc2544">RFC 2544</a>,
              DOI 10.17487/RFC2544, March 1999,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2544">http://www.rfc-editor.org/info/rfc2544</a>&gt;.

   [<a id="ref-RFC3393">RFC3393</a>]  Demichelis, C. and P. Chimento, "IP Packet Delay Variation
              Metric for IP Performance Metrics (IPPM)", <a href="./rfc3393">RFC 3393</a>,
              DOI 10.17487/RFC3393, November 2002,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3393">http://www.rfc-editor.org/info/rfc3393</a>&gt;.

   [<a id="ref-RFC3511">RFC3511</a>]  Hickman, B., Newman, D., Tadjudin, S., and T. Martin,
              "Benchmarking Methodology for Firewall Performance",
              <a href="./rfc3511">RFC 3511</a>, DOI 10.17487/RFC3511, April 2003,
              &lt;<a href="http://www.rfc-editor.org/info/rfc3511">http://www.rfc-editor.org/info/rfc3511</a>&gt;.

   [<a id="ref-RFC5180">RFC5180</a>]  Popoviciu, C., Hamza, A., Van de Velde, G., and D.
              Dugatkin, "IPv6 Benchmarking Methodology for Network
              Interconnect Devices", <a href="./rfc5180">RFC 5180</a>, DOI 10.17487/RFC5180,
              May 2008, &lt;<a href="http://www.rfc-editor.org/info/rfc5180">http://www.rfc-editor.org/info/rfc5180</a>&gt;.






<span class="grey">Georgescu, et al.             Informational                    [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   [<a id="ref-RFC5481">RFC5481</a>]  Morton, A. and B. Claise, "Packet Delay Variation
              Applicability Statement", <a href="./rfc5481">RFC 5481</a>, DOI 10.17487/RFC5481,
              March 2009, &lt;<a href="http://www.rfc-editor.org/info/rfc5481">http://www.rfc-editor.org/info/rfc5481</a>&gt;.

   [<a id="ref-RFC6201">RFC6201</a>]  Asati, R., Pignataro, C., Calabria, F., and C. Olvera,
              "Device Reset Characterization", <a href="./rfc6201">RFC 6201</a>,
              DOI 10.17487/RFC6201, March 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6201">http://www.rfc-editor.org/info/rfc6201</a>&gt;.

   [<a id="ref-RFC8174">RFC8174</a>]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
              <a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
              May 2017, &lt;<a href="http://www.rfc-editor.org/info/rfc8174">http://www.rfc-editor.org/info/rfc8174</a>&gt;.

<span class="h3"><a class="selflink" id="section-15.2" href="#section-15.2">15.2</a>.  Informative References</span>

   [<a id="ref-RFC2663">RFC2663</a>]  Srisuresh, P. and M. Holdrege, "IP Network Address
              Translator (NAT) Terminology and Considerations",
              <a href="./rfc2663">RFC 2663</a>, DOI 10.17487/RFC2663, August 1999,
              &lt;<a href="http://www.rfc-editor.org/info/rfc2663">http://www.rfc-editor.org/info/rfc2663</a>&gt;.

   [<a id="ref-RFC4213">RFC4213</a>]  Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms
              for IPv6 Hosts and Routers", <a href="./rfc4213">RFC 4213</a>,
              DOI 10.17487/RFC4213, October 2005,
              &lt;<a href="http://www.rfc-editor.org/info/rfc4213">http://www.rfc-editor.org/info/rfc4213</a>&gt;.

   [<a id="ref-RFC4659">RFC4659</a>]  De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
              "BGP-MPLS IP Virtual Private Network (VPN) Extension for
              IPv6 VPN", <a href="./rfc4659">RFC 4659</a>, DOI 10.17487/RFC4659, September 2006,
              &lt;<a href="http://www.rfc-editor.org/info/rfc4659">http://www.rfc-editor.org/info/rfc4659</a>&gt;.

   [<a id="ref-RFC4798">RFC4798</a>]  De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur,
              "Connecting IPv6 Islands over IPv4 MPLS Using IPv6
              Provider Edge Routers (6PE)", <a href="./rfc4798">RFC 4798</a>,
              DOI 10.17487/RFC4798, February 2007,
              &lt;<a href="http://www.rfc-editor.org/info/rfc4798">http://www.rfc-editor.org/info/rfc4798</a>&gt;.

   [<a id="ref-RFC5569">RFC5569</a>]  Despres, R., "IPv6 Rapid Deployment on IPv4
              Infrastructures (6rd)", <a href="./rfc5569">RFC 5569</a>, DOI 10.17487/RFC5569,
              January 2010, &lt;<a href="http://www.rfc-editor.org/info/rfc5569">http://www.rfc-editor.org/info/rfc5569</a>&gt;.

   [<a id="ref-RFC6144">RFC6144</a>]  Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
              IPv4/IPv6 Translation", <a href="./rfc6144">RFC 6144</a>, DOI 10.17487/RFC6144,
              April 2011, &lt;<a href="http://www.rfc-editor.org/info/rfc6144">http://www.rfc-editor.org/info/rfc6144</a>&gt;.

   [<a id="ref-RFC6146">RFC6146</a>]  Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful
              NAT64: Network Address and Protocol Translation from IPv6
              Clients to IPv4 Servers", <a href="./rfc6146">RFC 6146</a>, DOI 10.17487/RFC6146,
              April 2011, &lt;<a href="http://www.rfc-editor.org/info/rfc6146">http://www.rfc-editor.org/info/rfc6146</a>&gt;.



<span class="grey">Georgescu, et al.             Informational                    [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   [<a id="ref-RFC6147">RFC6147</a>]  Bagnulo, M., Sullivan, A., Matthews, P., and I. van
              Beijnum, "DNS64: DNS Extensions for Network Address
              Translation from IPv6 Clients to IPv4 Servers", <a href="./rfc6147">RFC 6147</a>,
              DOI 10.17487/RFC6147, April 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6147">http://www.rfc-editor.org/info/rfc6147</a>&gt;.

   [<a id="ref-RFC6219">RFC6219</a>]  Li, X., Bao, C., Chen, M., Zhang, H., and J. Wu, "The
              China Education and Research Network (CERNET) IVI
              Translation Design and Deployment for the IPv4/IPv6
              Coexistence and Transition", <a href="./rfc6219">RFC 6219</a>,
              DOI 10.17487/RFC6219, May 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6219">http://www.rfc-editor.org/info/rfc6219</a>&gt;.

   [<a id="ref-RFC6296">RFC6296</a>]  Wasserman, M. and F. Baker, "IPv6-to-IPv6 Network Prefix
              Translation", <a href="./rfc6296">RFC 6296</a>, DOI 10.17487/RFC6296, June 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6296">http://www.rfc-editor.org/info/rfc6296</a>&gt;.

   [<a id="ref-RFC6333">RFC6333</a>]  Durand, A., Droms, R., Woodyatt, J., and Y. Lee, "Dual-
              Stack Lite Broadband Deployments Following IPv4
              Exhaustion", <a href="./rfc6333">RFC 6333</a>, DOI 10.17487/RFC6333, August 2011,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6333">http://www.rfc-editor.org/info/rfc6333</a>&gt;.

   [<a id="ref-RFC6877">RFC6877</a>]  Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
              Combination of Stateful and Stateless Translation",
              <a href="./rfc6877">RFC 6877</a>, DOI 10.17487/RFC6877, April 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6877">http://www.rfc-editor.org/info/rfc6877</a>&gt;.

   [<a id="ref-RFC6890">RFC6890</a>]  Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman,
              "Special-Purpose IP Address Registries", <a href="https://www.rfc-editor.org/bcp/bcp153">BCP 153</a>,
              <a href="./rfc6890">RFC 6890</a>, DOI 10.17487/RFC6890, April 2013,
              &lt;<a href="http://www.rfc-editor.org/info/rfc6890">http://www.rfc-editor.org/info/rfc6890</a>&gt;.

   [<a id="ref-RFC7596">RFC7596</a>]  Cui, Y., Sun, Q., Boucadair, M., Tsou, T., Lee, Y., and I.
              Farrer, "Lightweight 4over6: An Extension to the Dual-
              Stack Lite Architecture", <a href="./rfc7596">RFC 7596</a>, DOI 10.17487/RFC7596,
              July 2015, &lt;<a href="http://www.rfc-editor.org/info/rfc7596">http://www.rfc-editor.org/info/rfc7596</a>&gt;.

   [<a id="ref-RFC7597">RFC7597</a>]  Troan, O., Ed., Dec, W., Li, X., Bao, C., Matsushima, S.,
              Murakami, T., and T. Taylor, Ed., "Mapping of Address and
              Port with Encapsulation (MAP-E)", <a href="./rfc7597">RFC 7597</a>,
              DOI 10.17487/RFC7597, July 2015,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7597">http://www.rfc-editor.org/info/rfc7597</a>&gt;.

   [<a id="ref-RFC7599">RFC7599</a>]  Li, X., Bao, C., Dec, W., Ed., Troan, O., Matsushima, S.,
              and T. Murakami, "Mapping of Address and Port using
              Translation (MAP-T)", <a href="./rfc7599">RFC 7599</a>, DOI 10.17487/RFC7599, July
              2015, &lt;<a href="http://www.rfc-editor.org/info/rfc7599">http://www.rfc-editor.org/info/rfc7599</a>&gt;.




<span class="grey">Georgescu, et al.             Informational                    [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   [<a id="ref-RFC7857">RFC7857</a>]  Penno, R., Perreault, S., Boucadair, M., Ed., Sivakumar,
              S., and K. Naito, "Updates to Network Address Translation
              (NAT) Behavioral Requirements", <a href="https://www.rfc-editor.org/bcp/bcp127">BCP 127</a>, <a href="./rfc7857">RFC 7857</a>,
              DOI 10.17487/RFC7857, April 2016,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7857">http://www.rfc-editor.org/info/rfc7857</a>&gt;.

   [<a id="ref-RFC7915">RFC7915</a>]  Bao, C., Li, X., Baker, F., Anderson, T., and F. Gont,
              "IP/ICMP Translation Algorithm", <a href="./rfc7915">RFC 7915</a>,
              DOI 10.17487/RFC7915, June 2016,
              &lt;<a href="http://www.rfc-editor.org/info/rfc7915">http://www.rfc-editor.org/info/rfc7915</a>&gt;.

   [<a id="ref-Dns64perf">Dns64perf</a>]
              Bakai, D., "A C++11 DNS64 performance tester",
              &lt;<a href="https://github.com/bakaid/dns64perfpp">https://github.com/bakaid/dns64perfpp</a>&gt;.

   [<a id="ref-ietf95pres">ietf95pres</a>]
              Georgescu, M., "Benchmarking Methodology for IPv6
              Transition Technologies", IETF 95 Proceedings, Buenos
              Aires, Argentina, April 2016,
              &lt;<a href="https://www.ietf.org/proceedings/95/slides/slides-95-bmwg-2.pdf">https://www.ietf.org/proceedings/95/slides/</a>
              <a href="https://www.ietf.org/proceedings/95/slides/slides-95-bmwg-2.pdf">slides-95-bmwg-2.pdf</a>&gt;.

   [<a id="ref-Lencse1">Lencse1</a>]  Lencse, G., Georgescu, M., and Y. Kadobayashi,
              "Benchmarking Methodology for DNS64 Servers", Computer
              Communications, vol. 109, no. 1, pp. 162-175,
              DOI 10.1016/j.comcom.2017.06.004, September 2017,
              &lt;<a href="http://www.sciencedirect.com/science/article/pii/S0140366416305904?via%3Dihub">http://www.sciencedirect.com/science/article/pii/</a>
              <a href="http://www.sciencedirect.com/science/article/pii/S0140366416305904?via%3Dihub">S0140366416305904?via%3Dihub</a>&gt;

   [<a id="ref-Lencse2">Lencse2</a>]  Lencse, G. and D. Bakai, "Design and Implementation of a
              Test Program for Benchmarking DNS64 Servers", IEICE
              Transactions on Communications, Vol. E100-B, No. 6,
              pp. 948-954, DOI 10.1587/transcom.2016EBN0007, June 2017,
              &lt;<a href="https://www.jstage.jst.go.jp/article/transcom/E100.B/6/E100.B_2016EBN0007/_article">https://www.jstage.jst.go.jp/article/transcom/E100.B/</a>
              <a href="https://www.jstage.jst.go.jp/article/transcom/E100.B/6/E100.B_2016EBN0007/_article">6/E100.B_2016EBN0007/_article</a>&gt;.

   [<a id="ref-Lencse3">Lencse3</a>]  dns64perfppc,
              &lt;<a href="http://www.hit.bme.hu/~lencse/dns64perfppc/">http://www.hit.bme.hu/~lencse/dns64perfppc/</a>&gt;.

   [<a id="ref-Lencse4">Lencse4</a>]  Lencse, G., "Enabling Dns64perf++ for Benchmarking the
              Caching Performance of DNS64 Servers", unpublished, review
              version, &lt;<a href="http://www.hit.bme.hu/~lencse/publications/IEICE-2016-dns64perfppc-for-review.pdf">http://www.hit.bme.hu/~lencse/publications/</a>
              <a href="http://www.hit.bme.hu/~lencse/publications/IEICE-2016-dns64perfppc-for-review.pdf">IEICE-2016-dns64perfppc-for-review.pdf</a>&gt;.








<span class="grey">Georgescu, et al.             Informational                    [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


   [<a id="ref-IEEE802.1AC">IEEE802.1AC</a>]
              IEEE, "IEEE Standard for Local and metropolitan area
              networks -- Media Access Control (MAC) Service
              Definition", IEEE 802.1AC.

   [<a id="ref-IEEE802.1Q">IEEE802.1Q</a>]
              IEEE, "IEEE Standard for Local and metropolitan area
              networks -- Bridges and Bridged Networks", IEEE Std
              802.1Q.










































<span class="grey">Georgescu, et al.             Informational                    [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Theoretical Maximum Frame Rates</span>

   This appendix describes the recommended calculation formulas for the
   theoretical maximum frame rates to be employed over Ethernet as
   example media.  The formula takes into account the frame size
   overhead created by the encapsulation or translation process.  For
   example, the 6in4 encapsulation described in [<a href="./rfc4213" title="&quot;Basic Transition Mechanisms for IPv6 Hosts and Routers&quot;">RFC4213</a>] adds 20 bytes
   of overhead to each frame.

   Considering X to be the frame size and O to be the frame size
   overhead created by the encapsulation or translation process, the
   maximum theoretical frame rate for Ethernet can be calculated using
   the following formula:

                Line Rate (bps)
         ------------------------------------
         (8 bits/byte) * (X+O+20) bytes/frame

   The calculation is based on the formula recommended by [<a href="./rfc5180" title="&quot;IPv6 Benchmarking Methodology for Network Interconnect Devices&quot;">RFC5180</a>] in
   <a href="#appendix-A.1">Appendix A.1</a>.  As an example, the frame rate recommended for testing
   a 6in4 implementation over 10 Mb/s Ethernet with 64 bytes frames is:

                10,000,000 (bps)
         --------------------------------------  = 12,019 fps
         (8 bits/byte) * (64+20+20) bytes/frame

   The complete list of recommended frame rates for 6in4 encapsulation
   can be found in the following table:

   +------------+---------+----------+-----------+------------+
   | Frame size | 10 Mb/s | 100 Mb/s | 1000 Mb/s | 10000 Mb/s |
   | (bytes)    | (fps)   | (fps)    | (fps)     | (fps)      |
   +------------+---------+----------+-----------+------------+
   | 64         | 12,019  | 120,192  | 1,201,923 | 12,019,231 |
   | 128        | 7,440   | 74,405   | 744,048   | 7,440,476  |
   | 256        | 4,223   | 42,230   | 422,297   | 4,222,973  |
   | 512        | 2,264   | 22,645   | 226,449   | 2,264,493  |
   | 678        | 1,740   | 17,409   | 174,094   | 1,740,947  |
   | 1024       | 1,175   | 11,748   | 117,481   | 1,174,812  |
   | 1280       | 947     | 9,470    | 94,697    | 946,970    |
   | 1518       | 802     | 8,023    | 80,231    | 802,311    |
   | 1522       | 800     | 8,003    | 80,026    | 800,256    |
   | 2048       | 599     | 5,987    | 59,866    | 598,659    |
   | 4096       | 302     | 3,022    | 30,222    | 302,224    |
   | 8192       | 152     | 1,518    | 15,185    | 151,846    |
   | 9216       | 135     | 1,350    | 13,505    | 135,048    |
   +------------+---------+----------+-----------+------------+




<span class="grey">Georgescu, et al.             Informational                    [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc8219">RFC 8219</a>      Benchmarking for IPv6 Transition Technologies  August 2017</span>


Acknowledgements

   The authors thank Youki Kadobayashi and Hiroaki Hazeyama for their
   constant feedback and support.  The thanks should be extended to the
   NECOMA project members for their continuous support.  We thank
   Emanuel Popa, Ionut Spirlea, and the RCS&amp;RDS IP/MPLS Backbone Team
   for their support and insights.  We thank Scott Bradner for the
   useful suggestions and note that portions of text from Scott's
   documents were used in this memo (e.g., the "Latency" section).  A
   big thank you to Al Morton and Fred Baker for their detailed review
   of the document and very helpful suggestions.  Other helpful comments
   and suggestions were offered by Bhuvaneswaran Vengainathan, Andrew
   McGregor, Nalini Elkins, Kaname Nishizuka, Yasuhiro Ohara, Masataka
   Mawatari, Kostas Pentikousis, Bela Almasi, Tim Chown, Paul Emmerich,
   and Stenio Fernandes.  A special thank you to the RFC Editor Team for
   their thorough editorial review and helpful suggestions.

Authors' Addresses

   Marius Georgescu
   RCS&amp;RDS
   Strada Dr. Nicolae D. Staicovici 71-75
   Bucharest 030167
   Romania

   Phone: +40 31 005 0979
   Email: marius.georgescu@rcs-rds.ro


   Liviu Pislaru
   RCS&amp;RDS
   Strada Dr. Nicolae D. Staicovici 71-75
   Bucharest 030167
   Romania

   Phone: +40 31 005 0979
   Email: liviu.pislaru@rcs-rds.ro


   Gabor Lencse
   Szechenyi Istvan University
   Egyetem ter 1.
   Gyor
   Hungary

   Phone: +36 20 775 8267
   Email: lencse@sze.hu




Georgescu, et al.             Informational                    [Page 30]
</pre>