draft-ietf-bmwg-ipv6-tran-tech-benchmarking-04.txt   draft-ietf-bmwg-ipv6-tran-tech-benchmarking-05.txt 
Benchmarking Working Group M. Georgescu Benchmarking Working Group M. Georgescu
Internet Draft L. Pislaru Internet Draft L. Pislaru
Intended status: Informational RCS&RDS Intended status: Informational RCS&RDS
Expires: September 2017 G. Lencse Expires: September 2017 G. Lencse
Szechenyi Istvan University Szechenyi Istvan University
March 1, 2017 March 29, 2017
Benchmarking Methodology for IPv6 Transition Technologies Benchmarking Methodology for IPv6 Transition Technologies
draft-ietf-bmwg-ipv6-tran-tech-benchmarking-04.txt draft-ietf-bmwg-ipv6-tran-tech-benchmarking-05.txt
Abstract Abstract
There are benchmarking methodologies addressing the performance of There are benchmarking methodologies addressing the performance of
network interconnect devices that are IPv4- or IPv6-capable, but the network interconnect devices that are IPv4- or IPv6-capable, but the
IPv6 transition technologies are outside of their scope. This IPv6 transition technologies are outside of their scope. This
document provides complementary guidelines for evaluating the document provides complementary guidelines for evaluating the
performance of IPv6 transition technologies. More specifically, performance of IPv6 transition technologies. More specifically,
this document targets IPv6 transition technologies that employ this document targets IPv6 transition technologies that employ
encapsulation or translation mechanisms, as dual-stack nodes can be encapsulation or translation mechanisms, as dual-stack nodes can be
skipping to change at page 1, line 46 skipping to change at page 1, line 46
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 1, 2016. This Internet-Draft will expire on September 29, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 5, line 47 skipping to change at page 5, line 47
| | Generic category | IPv6 Transition Technology | | | Generic category | IPv6 Transition Technology |
+---+--------------------+------------------------------------+ +---+--------------------+------------------------------------+
| 1 | Dual-stack | Dual IP Layer Operations [RFC4213] | | 1 | Dual-stack | Dual IP Layer Operations [RFC4213] |
+---+--------------------+------------------------------------+ +---+--------------------+------------------------------------+
| 2 | Single translation | NAT64 [RFC6146], IVI [RFC6219] | | 2 | Single translation | NAT64 [RFC6146], IVI [RFC6219] |
+---+--------------------+------------------------------------+ +---+--------------------+------------------------------------+
| 3 | Double translation | 464XLAT [RFC6877], MAP-T [RFC7599] | | 3 | Double translation | 464XLAT [RFC6877], MAP-T [RFC7599] |
+---+--------------------+------------------------------------+ +---+--------------------+------------------------------------+
| 4 | Encapsulation | DSLite[RFC6333], MAP-E [RFC7597] | | 4 | Encapsulation | DSLite[RFC6333], MAP-E [RFC7597] |
| | | Lightweight 4over6 [RFC7596] | | | | Lightweight 4over6 [RFC7596] |
| | | 6RD [RFC5569] | | | | 6RD [RFC5569], 6PE [RFC4798], 6VPE |
| | | 6VPE [RFC4659] |
+---+--------------------+------------------------------------+ +---+--------------------+------------------------------------+
2. Conventions used in this document 2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
In this document, these words will appear with that interpretation In this document, these words will appear with that interpretation
only when in ALL CAPS. Lower case uses of these words are not to be only when in ALL CAPS. Lower case uses of these words are not to be
skipping to change at page 13, line 39 skipping to change at page 13, line 39
D(i-1) - the One-way delay of i-1 th frame in the stream 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 Given the nature of IPDV, reporting a single number might lead to
over-summarization. In this context, the report for each measurement over-summarization. In this context, the report for each measurement
SHOULD include 3 values: Dmin, Dmed, and Dmax SHOULD include 3 values: Dmin, Dmed, and Dmax
Where: Dmin - the minimum IPDV in the stream Where: Dmin - the minimum IPDV in the stream
Dmed - the median IPDV of the stream Dmed - the median IPDV of the stream
Dmax - the maximum IPDVin the stream Dmax - the maximum IPDV in the stream
The test MUST be repeated at least 20 times. To summarize the 20 The test MUST be repeated at least 20 times. To summarize the 20
repetitions, for each of the 3 (Dmin, Dmed and Dmax) the median repetitions, for each of the 3 (Dmin, Dmed and Dmax) the median
value SHOULD be reported. value SHOULD be reported.
Reporting format: The median for the 3 proposed values SHOULD be Reporting format: The median for the 3 proposed values SHOULD be
reported. The IPDV results SHOULD be reported in a table with a row 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 for each of the tested frame sizes. The columns SHOULD include the
frame size and associated frame rate for the tested media types and frame size and associated frame rate for the tested media types and
sub-columns for the three proposed reported values. Following the sub-columns for the three proposed reported values. Following the
skipping to change at page 14, line 19 skipping to change at page 14, line 19
7.5. Back-to-back Frames 7.5. Back-to-back Frames
Use Section 26.4 of [RFC2544] unmodified. Use Section 26.4 of [RFC2544] unmodified.
7.6. System Recovery 7.6. System Recovery
Use Section 26.5 of [RFC2544] unmodified. Use Section 26.5 of [RFC2544] unmodified.
7.7. Reset 7.7. Reset
Use Section 26.6 of [RFC2544] unmodified. Use Section 4 of [RFC6201] unmodified.
8. Additional Benchmarking Tests for Stateful IPv6 Transition 8. Additional Benchmarking Tests for Stateful IPv6 Transition
Technologies Technologies
This section describes additional tests dedicated to the stateful This section describes additional tests dedicated to the stateful
IPv6 transition technologies. For the tests described in this IPv6 transition technologies. For the tests described in this
section the DUT devices SHOULD follow the test setup and test section the DUT devices SHOULD follow the test setup and test
parameters recommendations presented in [RFC3511] (Sections 4, 5). parameters recommendations presented in [RFC3511] (Sections 4, 5).
In addition to the IPv4/IPv6 transition function, a network node can In addition to the IPv4/IPv6 transition function, a network node can
skipping to change at page 24, line 10 skipping to change at page 24, line 10
[RFC2663] Srisuresh, P., and M. Holdrege. "IP Network Address [RFC2663] Srisuresh, P., and M. Holdrege. "IP Network Address
Translator (NAT) Terminology and Considerations", RFC2663, Translator (NAT) Terminology and Considerations", RFC2663,
DOI 10.17487/RFC2663, August 1999, <http://www.rfc- DOI 10.17487/RFC2663, August 1999, <http://www.rfc-
editor.org/info/rfc2663>. editor.org/info/rfc2663>.
[RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms
for IPv6 Hosts and Routers", RFC 4213, DOI for IPv6 Hosts and Routers", RFC 4213, DOI
10.17487/RFC4213, October 2005, <http://www.rfc- 10.17487/RFC4213, October 2005, <http://www.rfc-
editor.org/info/rfc4213>. editor.org/info/rfc4213>.
[RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
"BGP-MPLS IP Virtual Private Network (VPN) Extension for
IPv6 VPN", RFC 4659, September 2006, <http://www.rfc-
editor.org/info/4659>.
[RFC4798] De Clercq, J., Ooms, D., Prevost, S., and F. Le Faucheur,
"Connecting IPv6 Islands over IPv4 MPLS Using IPv6
Provider Edge Routers (6PE)", RFC 4798, February 2007,
<http://www.rfc-editor.org/info/rfc4798>
[RFC5569] Despres, R., "IPv6 Rapid Deployment on IPv4 [RFC5569] Despres, R., "IPv6 Rapid Deployment on IPv4
Infrastructures (6rd)", RFC 5569, DOI 10.17487/RFC5569, Infrastructures (6rd)", RFC 5569, DOI 10.17487/RFC5569,
January 2010, <http://www.rfc-editor.org/info/rfc5569>. January 2010, <http://www.rfc-editor.org/info/rfc5569>.
[RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for [RFC6144] Baker, F., Li, X., Bao, C., and K. Yin, "Framework for
IPv4/IPv6 Translation", RFC 6144, DOI 10.17487/RFC6144, IPv4/IPv6 Translation", RFC 6144, DOI 10.17487/RFC6144,
April 2011, <http://www.rfc-editor.org/info/rfc6144>. April 2011, <http://www.rfc-editor.org/info/rfc6144>.
[RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful
NAT64: Network Address and Protocol Translation from IPv6 NAT64: Network Address and Protocol Translation from IPv6
 End of changes. 7 change blocks. 
6 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/