draft-ietf-bmwg-ipv6-meth-03.txt   draft-ietf-bmwg-ipv6-meth-04.txt 
Network Working Group C. Popoviciu Network Working Group C. Popoviciu
Internet-Draft A. Hamza Internet-Draft A. Hamza
Expires: March 1, 2008 G. Van de Velde Intended status: Informational G. Van de Velde
Cisco Systems Expires: April 10, 2008 Cisco Systems
D. Dugatkin D. Dugatkin
IXIA IXIA
August 29, 2007 October 8, 2007
IPv6 Benchmarking Methodology for Network Interconnect Devices IPv6 Benchmarking Methodology for Network Interconnect Devices
<draft-ietf-bmwg-ipv6-meth-03.txt> <draft-ietf-bmwg-ipv6-meth-04.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." 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 March 1, 2008. This Internet-Draft will expire on April 10, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
The Benchmarking Methodologies defined in RFC2544 [8] are IP version The Benchmarking Methodologies defined in RFC2544 [8] are IP version
independent. However, RFC 2544 does not address some of the independent. However, RFC 2544 does not address some of the
specificities of IPv6. This document provides additional specificities of IPv6. This document provides additional
skipping to change at page 2, line 25 skipping to change at page 2, line 25
5.1.1. Frame Sizes to be used on Ethernet . . . . . . . . . . 5 5.1.1. Frame Sizes to be used on Ethernet . . . . . . . . . . 5
5.1.2. Frame Sizes to be used on SONET . . . . . . . . . . . 5 5.1.2. Frame Sizes to be used on SONET . . . . . . . . . . . 5
5.2. Protocol Addresses Selection . . . . . . . . . . . . . . . 6 5.2. Protocol Addresses Selection . . . . . . . . . . . . . . . 6
5.2.1. DUT Protocol Addresses . . . . . . . . . . . . . . . . 6 5.2.1. DUT Protocol Addresses . . . . . . . . . . . . . . . . 6
5.2.2. Test Traffic Protocol Addresses . . . . . . . . . . . 7 5.2.2. Test Traffic Protocol Addresses . . . . . . . . . . . 7
5.3. Traffic with Extension Headers . . . . . . . . . . . . . . 7 5.3. Traffic with Extension Headers . . . . . . . . . . . . . . 7
5.4. Traffic set up . . . . . . . . . . . . . . . . . . . . . . 9 5.4. Traffic set up . . . . . . . . . . . . . . . . . . . . . . 9
6. Modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . 9 6. Modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.1. Management and Routing Traffic . . . . . . . . . . . . . . 9 6.1. Management and Routing Traffic . . . . . . . . . . . . . . 9
6.2. Filters . . . . . . . . . . . . . . . . . . . . . . . . . 9 6.2. Filters . . . . . . . . . . . . . . . . . . . . . . . . . 9
6.2.1. Filter Format . . . . . . . . . . . . . . . . . . . . 10 6.2.1. Filter Format . . . . . . . . . . . . . . . . . . . . 9
6.2.2. Filter Types . . . . . . . . . . . . . . . . . . . . . 10 6.2.2. Filter Types . . . . . . . . . . . . . . . . . . . . . 10
7. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . . 11 7. Benchmarking Tests . . . . . . . . . . . . . . . . . . . . . . 11
7.1. Throughput . . . . . . . . . . . . . . . . . . . . . . . . 12 7.1. Throughput . . . . . . . . . . . . . . . . . . . . . . . . 12
7.2. Latency . . . . . . . . . . . . . . . . . . . . . . . . . 12 7.2. Latency . . . . . . . . . . . . . . . . . . . . . . . . . 12
7.3. Frame Loss . . . . . . . . . . . . . . . . . . . . . . . . 13 7.3. Frame Loss . . . . . . . . . . . . . . . . . . . . . . . . 12
7.4. Back-to-Back Frames . . . . . . . . . . . . . . . . . . . 13 7.4. Back-to-Back Frames . . . . . . . . . . . . . . . . . . . 13
7.5. System Recovery . . . . . . . . . . . . . . . . . . . . . 13 7.5. System Recovery . . . . . . . . . . . . . . . . . . . . . 13
7.6. Reset . . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.6. Reset . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
9. Security Considerations . . . . . . . . . . . . . . . . . . . 14 9. Security Considerations . . . . . . . . . . . . . . . . . . . 13
10. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. Conclusions . . . . . . . . . . . . . . . . . . . . . . . . . 14
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
12.1. Normative References . . . . . . . . . . . . . . . . . . . 15 12.1. Normative References . . . . . . . . . . . . . . . . . . . 15
12.2. Informative References . . . . . . . . . . . . . . . . . . 15 12.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Theoretical Maximum Frame Rates Reference . . . . . . 16 Appendix A. Theoretical Maximum Frame Rates Reference . . . . . . 15
A.1. Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . 16 A.1. Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . 16
A.2. Packet over SONET . . . . . . . . . . . . . . . . . . . . 16 A.2. Packet over SONET . . . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . . . . 19
1. Introduction 1. Introduction
The benchmarking methodologies defined by RFC2544 [8] are proving to The benchmarking methodologies defined by RFC2544 [8] are proving to
be useful in consistently evaluating IPv4 forwarding performance of be useful in consistently evaluating IPv4 forwarding performance of
network elements. Adherence to these testing and result analysis network elements. Adherence to these testing and result analysis
skipping to change at page 5, line 51 skipping to change at page 5, line 51
interface types are provided in Appendix A. interface types are provided in Appendix A.
5.1.2. Frame Sizes to be used on SONET 5.1.2. Frame Sizes to be used on SONET
Packet over SONET (PoS) interfaces are commonly used for edge uplinks Packet over SONET (PoS) interfaces are commonly used for edge uplinks
and high bandwidth core links. Evaluating the forwarding performance and high bandwidth core links. Evaluating the forwarding performance
of PoS interfaces supported by the DUT is recommended. The following of PoS interfaces supported by the DUT is recommended. The following
frame sizes SHOULD be used for this media type: 47, 64, 128, 256, frame sizes SHOULD be used for this media type: 47, 64, 128, 256,
512, 1024, 1280, 1518, 2048, 4096 bytes. 512, 1024, 1280, 1518, 2048, 4096 bytes.
Note: The 47 bytes SONET frame has no practical use since it can The theoretical maximum frame rates for each frame size and the
carry only the 40 bytes header of an IPv6 packet and no upper layer various PoS interface types are provided in Appendix A.
protocol information. It represents however the smallest frame size
for this media type.
The maximum frame rates for each frame size and the various PoS
interface types are provided in Appendix A.
5.2. Protocol Addresses Selection 5.2. Protocol Addresses Selection
There are two aspects of IPv6 benchmarking testing where IP address There are two aspects of IPv6 benchmarking testing where IP address
selection considerations MUST be analyzed: The selection of IP selection considerations MUST be analyzed: The selection of IP
addresses for the DUT and the selection of addresses for test addresses for the DUT and the selection of addresses for test
traffic. traffic.
5.2.1. DUT Protocol Addresses 5.2.1. DUT Protocol Addresses
skipping to change at page 17, line 15 skipping to change at page 17, line 10
and Frame Relay. All these encapsulations use a 4-byte header, a 2- and Frame Relay. All these encapsulations use a 4-byte header, a 2-
or 4-byte FCS field and a 1-byte Flag which are all accounted for in or 4-byte FCS field and a 1-byte Flag which are all accounted for in
the overall frame size. The maximum frame rate for various interface the overall frame size. The maximum frame rate for various interface
types can be calculated with the formula (where X represents the types can be calculated with the formula (where X represents the
frame size in bytes): frame size in bytes):
Line Rate (bps) Line Rate (bps)
------------------------------ ------------------------------
(8bits/byte)*(X+1)bytes/frame (8bits/byte)*(X+1)bytes/frame
The maximum throughput for various PoS interface types and frame The theoretical maximum frame rates for various PoS interface types
sizes: and frame sizes:
Size OC-3c OC-12c OC-48c OC-192c OC-768c Size OC-3c OC-12c OC-48c OC-192c OC-768c
Bytes fps fps fps fps fps Bytes fps fps fps fps fps
47 390,000 1,560,000 6,240,000 24,960,000 99,840,000 47 390,000 1,560,000 6,240,000 24,960,000 99,840,000
64 288,000 1,152,000 4,608,000 18,432,000 73,728,000 64 288,000 1,152,000 4,608,000 18,432,000 73,728,000
128 145,116 580,465 2,321,860 9,287,441 37,149,767 128 145,116 580,465 2,321,860 9,287,441 37,149,767
256 72,840 291,361 1,165,447 4,661,789 18,647,159 256 72,840 291,361 1,165,447 4,661,789 18,647,159
512 36,491 145,964 583,859 2,335,438 9,341,754 512 36,491 145,964 583,859 2,335,438 9,341,754
1024 18,263 73,053 292,214 1,168,858 4,675,434 1024 18,263 73,053 292,214 1,168,858 4,675,434
 End of changes. 10 change blocks. 
18 lines changed or deleted 13 lines changed or added

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