﻿<?xml version="1.0" encoding="UTF-8"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- One method to get references from the online citation libraries.
    There has to be one entity for each item to be referenced. 
    An alternate method (rfc include) is described in the references. -->

<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml">
<!ENTITY RFC8219 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.8219.xml">

]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs), 
    please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable Processing Instructions (PIs) that most I-Ds might want to use.
    (Here they are set differently than their defaults in xml2rfc v1.32) -->
<?rfc strict="yes" ?>
<!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC) -->
<?rfc toc="yes"?>
<!-- generate a ToC -->
<?rfc tocdepth="4"?>
<!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references -->
<?rfc symrefs="yes"?>
<!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?>
<!-- sort the reference entries alphabetically -->
<!-- control vertical white space 
    (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?>
<!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?>
<!-- keep one blank line between list items -->
<!-- end of list of popular I-D processing instructions -->
<rfc category="info" docName="draft-lencse-v6ops-transition-benchmarking-00" ipr="trust200902">

  <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the 
          full title is longer than 39 characters -->

    <title abbrev="Benchmarking of IPv4aaS Technologies">Performance Analysis of IPv6 Transition
    Technologies for IPv4aaS</title>

    <!-- add 'role="editor"' below for the editors if appropriate -->

    <!-- Another author who claims to be an editor -->

    <author fullname="Gabor Lencse" initials="G." surname="Lencse">
      <organization >Szechenyi Istvan University</organization>
      <address>
        <postal>
          <street>Egyetem ter 1.</street>
          <!-- Reorder these if your country does things differently -->
          <city>Gyor</city>
          <region></region>
          <code>H-9026</code>
          <country>Hungary</country>
        </postal>
        <phone></phone>
        <email>lencse@sze.hu</email>
      </address>
    </author>

    <date year="2021" />

    <!-- Meta-data Declarations -->

    <area>ops</area>

    <workgroup>v6ops</workgroup>

    <!-- WG name at the upperleft corner of the doc,
          IETF is fine for individual submissions.  
    If this element is not present, the default is "Network Working Group",
          which is used by the RFC Editor as a nod to the history of the IETF. -->

    <keyword>IPv6, Transition Technologies, Comparison, IPv4aaS, IPv6-only, 464XLAT, DNS64, Dual Stack Lite, Lightweight 4over6, MAP-E, MAP-T</keyword>

    <!-- Keywords will be incorporated into HTML output
          files in a meta tag but they have no effect on text or nroff
          output. If you submit your draft to the RFC Editor, the
          keywords will be used for the search engine. -->

    <abstract>
      <t>Several IPv6 transition technologies have been developed to
      provide customers with IPv4-as-a-Service (IPv4aaS) for ISPs with an
      IPv6-only access and/or core network. All these technologies have their
      advantages and disadvantages, and depending on existing topology, skills,
      strategy and other preferences, one of these technologies may be the
      most appropriate solution for a network operator.</t>

      <t>This document examines and compares the performance of some free 
	  software implementations of the five most prominent
      IPv4aaS technologies (464XLAT, Dual Stack Lite, Lightweight 4over6, 
	  MAP-E, MAP-T).</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>IETF has standardized several IPv6 transition technologies 
	  <xref target="LEN2019"/> and occupied a neutral position trusting 
	  the selection of the most appropriate ones to the market.  
	  <xref target="I-D.ietf-v6ops-transition-comparison"/> provides a
      comprehensive comparative analysis of the five most prominent 
	  IPv4aaS technologies to assist operators with this problem. 
	  This document adds one more detail: performance analysis and 
	  comparison of the examined IPv4aaS technologies.</t>

      <t>Currently this document is a stub. It has been created to 
	  provide a citable reference for the above mentioned I-D.</t>
	  
      <section title="Requirements Language">
        <t>
           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 BCP14 <xref target="RFC2119"/> <xref target="RFC8174"/> 
           when, and only when, they appear in all capitals, as shown here.
         </t>
      </section>
    </section>

 
   <section anchor="Acknowledgements" title="Acknowledgements">
     <t>The authors would like to thank ...  TBD </t>
   </section>

   <!-- Possibly a 'Contributors' section ... -->

   <section anchor="IANA" title="IANA Considerations">
     <t>This document does not make any request to IANA.</t>
   </section>

   <section anchor="Security" title="Security Considerations">
     <t>TBD. </t>

   </section>
 </middle>

 <!--  *****BACK MATTER ***** -->

 <back>
   <!-- References split into informative and normative -->

   <!-- There are 2 ways to insert reference entries from the citation libraries:
    1. define an ENTITY at the top, and use "ampersand character"RFC2629; here (as shown)
    2. simply use a PI "less than character"?rfc include="reference.RFC.2119.xml"?> here
       (for I-Ds: include="reference.I-D.narten-iana-considerations-rfc2434bis.xml")

    Both are cited textually in the same manner: by using xref elements.
    If you use the PI option, xml2rfc will, by default, try to find included files in the same
    directory as the including file. You can also define the XML_LIBRARY environment variable
    with a value containing a set of directories to search.  These can be either in the local
    filing system or remote ones accessed by http (http://domain/dir/... ).-->

   <references title="Normative References">
    <!--?rfc include="http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"?-->

    &RFC2119;
    &RFC8174;
    &RFC8219;

   </references>

   <references title="Informative References">
     <!-- Here we use entities that we defined at the beginning. -->
 
    <?rfc include='reference.I-D.ietf-v6ops-transition-comparison'?>

<!--    <?rfc include='reference.I-D.lencse-v6ops-transition-scale-up'?> -->

<!--    <?rfc include='reference.I-D.lencse-v6ops-transition-benchmarking'?> -->

 
    <reference anchor="LEN2019" 
    target="http://www.hit.bme.hu/~lencse/publications/e102-b_10_2021.pdf">
      <front>
        <title>Comprehensive Survey of IPv6 Transition Technologies: 
		A Subjective Classification for Security Analysis
        </title>

        <author initials="G." surname="Lencse">
          <organization></organization>
        </author>
        <author initials="Y." surname="Kadobayashi">
          <organization></organization>
        </author>

        <date day="1" month="Oct" year="2019" />
      </front>
      <seriesInfo name="" value="IEICE Transactions on Communications, vol. E102-B, no.10, pp. 2021-2035."/>
      <seriesInfo name="" value="DOI: 10.1587/transcom.2018EBR0002"/>
    </reference>
	
	<reference anchor="LEN2020" 
    target="http://www.hit.bme.hu/~lencse/publications/291-1113-1-PB.pdf">
      <front>
        <title>Adding RFC 4814 Random Port Feature to Siitperf: Design, Implementation and 
		Performance Estimation
        </title>

        <author initials="G." surname="Lencse">
          <organization></organization>
        </author>
		
		<date day="" month="" year="2020" />
     
      </front>
      <seriesInfo name="" value="International Journal of Advances in Telecommunications, Electrotechnics, Signals and Systems, vol 9, no 3, pp. 18-26"/>
	  <seriesInfo name="" value="DOI: 10.11601/ijates.v9i3.291"/>
    </reference>
	
	<reference anchor="LEN2021" 
    target="http://www.hit.bme.hu/~lencse/publications/IEICE-2020-siitperf-revised.pdf">
      <front>
        <title>Design and Implementation of a Software Tester for Benchmarking Stateless NAT64 Gateways
        </title>

        <author initials="G." surname="Lencse">
          <organization></organization>
        </author>
		
		<date day="" month="" year="2021" />
     
      </front>
      <seriesInfo name="" value="IEICE Transactions on Communications"/>
	  <seriesInfo name="" value="DOI: 10.1587/transcom.2019EBN0010"/>
    </reference>
	
   </references>

   <section anchor="change_log" title="Change Log">
    <section title="00">
      <t>Initial version.
      </t>
    </section>

   </section>
  </back>
</rfc>