draft-ietf-bmwg-igp-dataplane-conv-meth-10.txt   draft-ietf-bmwg-igp-dataplane-conv-meth-11.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: September 2006 Expires in: November 2006
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
Brent Imhoff Brent Imhoff
Juniper Networks Juniper Networks
Benchmarking Methodology for Benchmarking Methodology for
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-meth-10.txt> <draft-ietf-bmwg-igp-dataplane-conv-meth-11.txt>
Intellectual Property Rights (IPR) statement: Intellectual Property Rights (IPR) statement:
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.
Status of this Memo Status of this Memo
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 6, line 12 skipping to change at page 6, line 12
configure SONET with minimum carrier-loss-delay or Bi-directional configure SONET with minimum carrier-loss-delay or Bi-directional
Forwarding Detection (BFD). Forwarding Detection (BFD).
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.2.7 Offered Load 3.2.7 Offered Load
The offered Load MUST be the Throughput of the device as defined The offered Load MUST be the Throughput of the device as defined
in [5] and benchmarked in [6] at a fixed packet size. in [5] and benchmarked in [6] at a fixed packet size.
Packet size is measured in bytes and includes the IP header and Packet size is measured in bytes and includes the IP header and
payload. The packet size is selectable and MUST be recorded. payload. The packet size is selectable and MUST be recorded.
The Throughput MUST be measured at the Preferred Egress Interface The Forwarding Rate [7] MUST be measured at the Preferred Egress
and the Next-Best Egress Interface. The duration of offered load Interface and the Next-Best Egress Interface. The duration of
MUST be greater than the convergence time. The destination offered load MUST be greater than the convergence time. The
addresses for the offered load MUST be distributed such that all destination addresses for the offered load MUST be distributed
routes are matched. This enables Full Convergence [2] to be such that all routes are matched. This enables Full Convergence
observed. [2] to be observed.
3.3 Reporting Format 3.3 Reporting Format
For each test case, it is recommended that the following reporting For each test case, it is recommended that the following reporting
format be completed: format be completed:
Parameter Units Parameter Units
--------- ----- --------- -----
IGP (ISIS or OSPF) IGP (ISIS or OSPF)
Interface Type (GigE, POS, ATM, etc.) Interface Type (GigE, POS, ATM, etc.)
Packet Size offered to DUT bytes Packet Size offered to DUT bytes
skipping to change at page 13, line 35 skipping to change at page 13, line 35
is not performed on devices or systems connected to operating is not performed on devices or systems connected to operating
networks. networks.
7. Acknowledgements 7. Acknowledgements
Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of Thanks to Sue Hares, Al Morton, Kevin Dubray, and participants of
the BMWG for their contributions to this work. the BMWG for their contributions to this work.
8. References 8. References
8.1 Normative References 8.1 Normative References
[1] Poretsky, S., "Considerations for Benchmarking IGP [1] Poretsky, S., "Considerations for Benchmarking IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-10, Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-11,
work in progress, March 2006. work in progress, May 2006.
[2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP [2] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-10, Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-11,
work in progress, March 2006. work in progress, May 2006.
[3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual [3] Callon, R., "Use of OSI IS-IS for Routing in TCP/IP and Dual
Environments", RFC 1195, IETF, December 1990. Environments", RFC 1195, IETF, December 1990.
[4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998. [4] Moy, J., "OSPF Version 2", RFC 2328, IETF, April 1998.
[5] Bradner, S., "Benchmarking Terminology for Network [5] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, IETF, March 1991. Interconnection Devices", RFC 1242, IETF, March 1991.
[6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for [6] Bradner, S. and McQuaid, J., "Benchmarking Methodology for
Network Interconnect Devices", RFC 2544, IETF, March 1999. Network Interconnect Devices", RFC 2544, IETF, March 1999.
[7] Mandeville, R., "Benchmarking Terminology for LAN
Switching Devices", RFC 2285, February 1998.
8.2 Informative References 8.2 Informative References
None None
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
9. Author's Address 9. Author's Address
Scott Poretsky Scott Poretsky
Reef Point Systems Reef Point Systems
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
 End of changes. 6 change blocks. 
12 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/