draft-ietf-bmwg-mcastm-09.txt   draft-ietf-bmwg-mcastm-10.txt 
Network Working Group Debra Stopp Network Working Group Debra Stopp
Hardev Soor Hardev Soor
INTERNET-DRAFT IXIA INTERNET-DRAFT IXIA
Expires in: November 2002 Expires in: March 2003
Methodology for IP Multicast Benchmarking Methodology for IP Multicast Benchmarking
<draft-ietf-bmwg-mcastm-09.txt> <draft-ietf-bmwg-mcastm-10.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
The BMWG produces two major classes of documents: Benchmarking The BMWG produces two major classes of documents: Benchmarking
Terminology documents and Benchmarking Methodology documents. The Terminology documents and Benchmarking Methodology documents. The
Terminology documents present the benchmarks and other related Terminology documents present the benchmarks and other related
terms. The Methodology documents define the procedures required to terms. The Methodology documents define the procedures required to
collect the benchmarks cited in the corresponding Terminology collect the benchmarks cited in the corresponding Terminology
documents. documents.
Table of Contents Table of Contents
1. INTRODUCTION....................................................3 1. INTRODUCTION...................................................3
2. KEY WORDS TO REFLECT REQUIREMENTS...............................3 2. KEY WORDS TO REFLECT REQUIREMENTS..............................3
3. TEST SET UP.....................................................3 3. TEST SET UP....................................................3
3.1. Test Considerations...........................................5 3.1. Test Considerations..........................................5
3.1.1. IGMP Support...............................................5 3.1.1. IGMP Support..............................................5
3.1.2. Group Addresses............................................5 3.1.2. Group Addresses...........................................5
3.1.3. Frame Sizes................................................6 3.1.3. Frame Sizes...............................................6
3.1.4. TTL........................................................6 3.1.4. TTL.......................................................6
3.1.5. Trial Duration.............................................6 3.1.5. Trial Duration............................................6
3.2. Layer 2 Support...............................................6 3.2. Layer 2 Support..............................................6
4. FORWARDING AND THROUGHPUT.......................................6 4. FORWARDING AND THROUGHPUT......................................6
4.1. Mixed Class Throughput........................................6 4.1. Mixed Class Throughput.......................................6
4.2. Scaled Group Forwarding Matrix................................8 4.2. Scaled Group Forwarding Matrix...............................8
4.3. Aggregated Multicast Throughput...............................8 4.3. Aggregated Multicast Throughput..............................8
4.4. Encapsulation/Decapsulation (Tunneling) Throughput............9 4.4. Encapsulation/Decapsulation (Tunneling) Throughput...........9
4.4.1. Encapsulation Throughput...................................9 4.4.1. Encapsulation Throughput..................................9
4.4.2. Decapsulation Throughput..................................10 4.4.2. Decapsulation Throughput.................................10
4.4.3. Re-encapsulation Throughput...............................10 4.4.3. Re-encapsulation Throughput..............................11
5. FORWARDING LATENCY.............................................11 5. FORWARDING LATENCY............................................12
5.1. Multicast Latency............................................11 5.1. Multicast Latency...........................................12
5.2. Min/Max Multicast Latency....................................14 5.2. Min/Max Multicast Latency...................................15
6. OVERHEAD.......................................................15 6. OVERHEAD......................................................16
6.1. Group Join Delay.............................................15 6.1. Group Join Delay............................................16
6.2. Group Leave Delay............................................15 6.2. Group Leave Delay...........................................16
7. CAPACITY.......................................................16 7. CAPACITY......................................................17
7.1. Multicast Group Capacity.....................................16 7.1. Multicast Group Capacity....................................17
8. INTERACTION....................................................17 8. INTERACTION...................................................18
8.1. Forwarding Burdened Multicast Latency........................17 8.1. Forwarding Burdened Multicast Latency.......................18
8.2. Forwarding Burdened Group Join Delay.........................18 8.2. Forwarding Burdened Group Join Delay........................19
9. SECURITY CONSIDERATIONS........................................19 9. SECURITY CONSIDERATIONS.......................................20
10. ACKNOWLEDGEMENTS..............................................19 10. ACKNOWLEDGEMENTS.............................................20
11. REFERENCES....................................................20 11. REFERENCES...................................................21
12. AUTHOR'S ADDRESSES............................................21 12. AUTHOR'S ADDRESSES...........................................22
13. FULL COPYRIGHT STATEMENT......................................21 13. FULL COPYRIGHT STATEMENT.....................................22
1. Introduction 1. Introduction
This document defines a specific set of tests that vendors can use This document defines a specific set of tests that vendors can use
to measure and report the performance characteristics and to measure and report the performance characteristics and
forwarding capabilities of network devices that support IP forwarding capabilities of network devices that support IP
multicast protocols. The results of these tests will provide the multicast protocols. The results of these tests will provide the
user comparable data from different vendors with which to evaluate user comparable data from different vendors with which to evaluate
these devices. these devices.
A previous document, " Terminology for IP Multicast Benchmarking" A previous document, " Terminology for IP Multicast Benchmarking"
skipping to change at page 7, line 52 skipping to change at page 7, line 52
multicast traffic. multicast traffic.
Throughput measurement is defined in RFC1242 [Br91]. A search Throughput measurement is defined in RFC1242 [Br91]. A search
algorithm MUST be utilized to determine the maximum offered frame algorithm MUST be utilized to determine the maximum offered frame
rate with a zero frame loss rate. rate with a zero frame loss rate.
Result Result
Parameters to be measured MUST include the aggregate offered load, Parameters to be measured MUST include the aggregate offered load,
number of multicast frames offered, number of unicast frames number of multicast frames offered, number of unicast frames
offered, number multicast frames received, number of unicast frames offered, number of multicast frames received, number of unicast
received and transmit duration of offered frames. frames received and transmit duration of offered frames.
4.2. Scaled Group Forwarding Matrix 4.2. Scaled Group Forwarding Matrix
Objective Objective
To determine Forwarding Rate as a function of tested multicast To determine Forwarding Rate as a function of tested multicast
groups for a fixed number of tested DUT/SUT ports. groups for a fixed number of tested DUT/SUT ports.
Procedure Procedure
skipping to change at page 9, line 35 skipping to change at page 9, line 35
offered frames. offered frames.
Constructing a table from the measurements might be useful in Constructing a table from the measurements might be useful in
illustrating the effect of modifying the number of active egress illustrating the effect of modifying the number of active egress
ports on the tested system. ports on the tested system.
4.4. Encapsulation/Decapsulation (Tunneling) Throughput 4.4. Encapsulation/Decapsulation (Tunneling) Throughput
This sub-section provides the description of tests that help in This sub-section provides the description of tests that help in
obtaining throughput measurements when a DUT/SUT or a set of DUTs obtaining throughput measurements when a DUT/SUT or a set of DUTs
are acting as tunnel endpoints are acting as tunnel endpoints.
4.4.1. Encapsulation Throughput 4.4.1. Encapsulation Throughput
Objective Objective
To determine the maximum rate at which frames offered a DUT/SUT are To determine the maximum rate at which frames offered a DUT/SUT are
encapsulated and correctly forwarded by the DUT/SUT without loss. encapsulated and correctly forwarded by the DUT/SUT without loss.
Procedure Procedure
Traffic is sent through a DUT/SUT that has been configured to Traffic is offered to the ingress interface of a DUT/SUT <Figure 1>
encapsulate the frames. Traffic is received on a test port prior to that has been configured to encapsulate the frames and received on
decapsulation and throughput is calculated based on RFC2544. a test port prior to decapsulation at the egress interface.
The DUT/SUT SHOULD be configured such that the constitution of
traffic will consist of either:
a) A single tunnel encapsulating one or more multicast address
groups OR
b) Multiple tunnels, each encapsulating one or more multicast
address groups.
Each tunnel created by the ingress DUT/SUT SHOULD contain the same
number of multicast address groups per tunnel interface.
The offered load on the ingress port MUST not oversubscribe the
outbound link of the DUT/SUT with respect to the benchmarked
throughput at the encapsulated frame size.
Results Results
Parameters to be measured SHOULD include the measured throughput Based on the resulting encapsulated frame size, parameters to be
per tunnel. measured MUST include the maximum offered load at which no frame
loss occurred, the number of encapsulated multicast frames offered
per tunnel interface, and the number of encapsulated multicast
frames received per tunnel interface.
The nature of the traffic stream contributing to the result MUST be The nature of the traffic stream contributing to the result MUST be
reported. All required reporting parameters of encapsulation reported. All required reporting parameters of multicast
throughput MUST be reflected in the results report, such as the encapsulation throughput MUST be reflected in the results report,
transmitted packet size(s), offered load of the packet stream and such as the encapsulation format, transmitted packet size(s),
transmit duration of offered frames. encapsulated frame size, and transmit duration of offered frames.
4.4.2. Decapsulation Throughput 4.4.2. Decapsulation Throughput
Objective Objective
To determine the maximum rate at which frames offered a DUT/SUT are To determine the maximum rate at which frames offered a DUT/SUT are
decapsulated and correctly forwarded by the DUT/SUT without loss. decapsulated and correctly forwarded by the DUT/SUT without loss.
Procedure Procedure
Encapsulated traffic is sent through a DUT/SUT that has been Encapsulated traffic is offered to the egress interface of a
configured to decapsulate the frames. Traffic is received on a test DUT/SUT <Figure 1> that has been configured to decapsulate the
port after decapsulation and throughput is calculated based on frames.
RFC2544.
The constitution of traffic SHOULD consist of either:
a) A single tunnel encapsulating one or more multicast address
groups OR
b) Multiple tunnels, each encapsulating one or more multicast
address groups.
Due to the nature of decapsulation, the offered load on the
encapsulated egress port will be less than the offered load on the
decapsulated egress interface.
Results Results
Parameters to be measured SHOULD include the measured throughput Based on the resulting decapsulated frame size, parameters to be
per tunnel. measured MUST include the maximum offered load at which no frame
loss occurred, the number of encapsulated multicast frames offered
per tunnel interface, and the number of multicast frames received
after decapsulation.
The nature of the traffic stream contributing to the result MUST be The nature of the traffic stream contributing to the result MUST be
reported. All required reporting parameters of decapsulation reported. All required reporting parameters of multicast
throughput MUST be reflected in the results report, such as the decapsulation throughput MUST be reflected in the results report,
transmitted packet size(s), offered load of the packet stream and such as the transmitted packet size(s), decapsulated frame size,
transmit duration of offered frames. and transmit duration of offered frames.
4.4.3. Re-encapsulation Throughput 4.4.3. Re-encapsulation Throughput
Objective Objective
To determine the maximum rate at which frames of one encapsulated To determine the maximum rate at which frames of one encapsulated
format offered a DUT/SUT are converted to another encapsulated format offered a DUT/SUT are converted to another encapsulated
format and correctly forwarded by the DUT/SUT without loss. format and correctly forwarded by the DUT/SUT without loss.
Procedure Procedure
Traffic is sent through a DUT/SUT that has been configured to Encapsulated traffic of one type is offered to the egress interface
encapsulate frames into one format, then re-encapsulate the frames of a DUT/SUT <Figure 1> that has been configured to re-encapsulate
into another format. Traffic is received on a test port after all the frames using a different encapsulation format.
decapsulation is complete and throughput is calculated based on
RFC2544. The DUT/SUT SHOULD be configured such that the constitution of
traffic will consist of either:
c) A single tunnel encapsulating one or more multicast address
groups OR
d) Multiple tunnels, each encapsulating one or more multicast
address groups.
Each tunnel created by the ingress DUT/SUT SHOULD contain the same
number of multicast address groups per tunnel interface.
The offered load on the ingress port MUST not oversubscribe the
outbound link with respect to the offered load at the higher end of
the DUT/SUTĘs capacity based on the encapsulated frame size.
Results Results
Parameters to be measured SHOULD include the measured throughput Based on the resulting encapsulated frame size, parameters to be
per tunnel. measured MUST include the maximum offered load at which no frame
loss occurred, the number of encapsulated multicast frames offered
per tunnel interface, and the number of encapsulated multicast
frames received per tunnel interface.
The nature of the traffic stream contributing to the result MUST be The nature of the traffic stream contributing to the result MUST be
reported. All required reporting parameters of re-encapsulation reported. All required reporting parameters of multicast
throughput MUST be reflected in the results report, such as the encapsulation throughput MUST be reflected in the results report,
transmitted packet size(s), offered load of the packet stream and such as the encapsulation format on the egress interface,
transmit duration of offered frames. transmitted packet size(s), encapsulated frame size, and transmit
duration of offered frames.
5. Forwarding Latency 5. Forwarding Latency
This section presents methodologies relating to the This section presents methodologies relating to the
characterization of the forwarding latency of a DUT/SUT in a characterization of the forwarding latency of a DUT/SUT in a
multicast environment. It extends the concept of latency multicast environment. It extends the concept of latency
characterization presented in RFC 2544. characterization presented in RFC 2544.
In order to lessen the effect of packet buffering in the DUT/SUT, In order to lessen the effect of packet buffering in the DUT/SUT,
the latency tests MUST be run at the measured multicast throughput the latency tests MUST be run at the measured multicast throughput
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/