draft-ietf-bmwg-igp-dataplane-conv-term-06.txt   draft-ietf-bmwg-igp-dataplane-conv-term-07.txt 
Network Working Group Network Working Group
INTERNET-DRAFT INTERNET-DRAFT
Expires in: December 2005 Expires in: January 2006
Scott Poretsky Scott Poretsky
Quarry Technologies Reef Point Systems
Brent Imhoff Brent Imhoff
LightCore LightCore
June 2005 July 2005
Terminology for Benchmarking Terminology for Benchmarking
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
<draft-ietf-bmwg-igp-dataplane-conv-term-06.txt> <draft-ietf-bmwg-igp-dataplane-conv-term-07.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
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 June also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and June be updated, replaced, or obsoleted by other months and may be updated, replaced, or obsoleted by other
documents at any time. It is inappropriate to use Internet-Drafts documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in as reference material or to cite them other than as "work in
progress." 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.
skipping to change at page 3, line 23 skipping to change at page 3, line 23
Convergence------->\ / Event Transition Convergence------->\ / Event Transition
Recovery Transition \ / Recovery Transition \ /
\_____/<------Packet Loss \_____/<------Packet Loss
X-axis = Time X-axis = Time
Y-axis = Forwarding Rate Y-axis = Forwarding Rate
Figure 1. Convergence Graph Figure 1. Convergence Graph
2. Existing definitions 2. Existing definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "June", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[Br97]. RFC 2119 defines the use of these key words to help make the [Br97]. RFC 2119 defines the use of these key words to help make the
intent of standards track documents as clear as possible. While this intent of standards track documents as clear as possible. While this
document uses these keywords, this document is not a standards track document uses these keywords, this document is not a standards track
document. document.
3. Term Definitions 3. Term Definitions
3.1 Convergence Event 3.1 Convergence Event
Definition: Definition:
skipping to change at page 5, line 40 skipping to change at page 5, line 40
3.5 Convergence Packet Loss 3.5 Convergence Packet Loss
Definition: Definition:
The amount of packet loss produced by a Convergence Event The amount of packet loss produced by a Convergence Event
until Route Convergence occurs. until Route Convergence occurs.
Discussion: Discussion:
Packet loss can be observed as a reduction of forwarded traffic from Packet loss can be observed as a reduction of forwarded traffic from
the maximum forwarding rate. Convergence Packet Loss include packets the maximum forwarding rate. Convergence Packet Loss include packets
that were lost and packets that were delayed due to buffering. that were lost and packets that were delayed due to buffering.
Convergence Packet Loss June or June not reach 100%. Convergence Packet Loss may or may not reach 100%.
Measurement Units: Measurement Units:
number of packets number of packets
Issues: Issues:
None None
See Also: See Also:
Route Convergence Route Convergence
Convergence Event Convergence Event
skipping to change at page 7, line 43 skipping to change at page 7, line 43
Convergence Event Instant Convergence Event Instant
Full Convergence Full Convergence
3.9 Convergence Event Transition 3.9 Convergence Event Transition
Definition: Definition:
The characteristic of a router in which forwarding rate The characteristic of a router in which forwarding rate
gradually reduces to zero after a Convergence Event. gradually reduces to zero after a Convergence Event.
Discussion: Discussion:
The Convergence Event Transition is best observed for The Convergence Event Transition is best observed for
Full Convergence. The Convergence Event Transition June Full Convergence. The Convergence Event Transition may
not be linear. not be linear.
Measurement Units: Measurement Units:
seconds/milliseconds seconds/milliseconds
Issues: Issues:
None None
See Also: See Also:
Convergence Event Convergence Event
skipping to change at page 8, line 14 skipping to change at page 8, line 14
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.10 Convergence Recovery Transition 3.10 Convergence Recovery Transition
Definition: Definition:
The characteristic of a router in which forwarding rate The characteristic of a router in which forwarding rate
gradually increases to equal the offered load. gradually increases to equal the offered load.
Discussion: Discussion:
The Convergence Recovery Transition is best observed for The Convergence Recovery Transition is best observed for
Full Convergence. The Convergence Event Transition June Full Convergence. The Convergence Event Transition may
not be linear. not be linear.
Measurement Units: Measurement Units:
seconds/milliseconds seconds/milliseconds
Issues: Issues:
None None
See Also: See Also:
Full Convergence Full Convergence
skipping to change at page 10, line 33 skipping to change at page 10, line 33
See Also: See Also:
Convergence Event Convergence Event
Rate-Derived Convergence Time Rate-Derived Convergence Time
3.14 Packet Sampling Interval 3.14 Packet Sampling Interval
Definition: Definition:
The interval at which the tester (test equipment) polls to make The interval at which the tester (test equipment) polls to make
measurements for arriving packet flows. measurements for arriving packet flows.
Discussion: Discussion:
Metrics measured at the Packet Sampling Interval June include Metrics measured at the Packet Sampling Interval may include
Forwarding Rate and Convergence Packet Loss. Forwarding Rate and Convergence Packet Loss.
Measurement Units: Measurement Units:
seconds or milliseconds seconds or milliseconds
Issues: Issues:
Packet Sampling Interval can influence the Convergence Graph. Packet Sampling Interval can influence the Convergence Graph.
This is particularly true as implementations achieve Full This is particularly true as implementations achieve Full
Convergence in less than 1 second. The Convergence Event Convergence in less than 1 second. The Convergence Event
Transition and Convergence Recovery Transition can become Transition and Convergence Recovery Transition can become
skipping to change at page 13, line 7 skipping to change at page 13, line 7
N/A N/A
Issues: Issues:
None None
See Also: See Also:
Preferred Egress Interface Preferred Egress Interface
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
3.20 Stale Forwarding 3.20 Stale Forwarding
Definition: Definition:
Forwarding of traffic to route entries that no longer exist Forwarding of traffic to route entries that no longer exist
or to route entries with next-hops that are no longer preferred. or to route entries with next-hops that are no longer preferred.
Discussion: Discussion:
Stale Forwarding can be caused by a Convergence Event and is Stale Forwarding can be caused by a Convergence Event and is
also known as a "black-hole" since it June produce packet loss. also known as a "black-hole" since it may produce packet loss.
Stale Forwarding exists until Network Convergence is achieved. Stale Forwarding exists until Network Convergence is achieved.
Measurement Units: Measurement Units:
N/A N/A
Issues: Issues:
None None
See Also: See Also:
Network Convergence Network Convergence
skipping to change at page 14, line 10 skipping to change at page 14, line 10
Documents of this type do not directly affect the security of Documents of this type do not directly affect the security of
Internet or corporate networks as long as benchmarking Internet or corporate networks as long as benchmarking
is not performed on devices or systems connected to operating is not performed on devices or systems connected to operating
networks. networks.
IGP Data Plane Route Convergence IGP Data Plane Route Convergence
5. Normative References 5. Normative References
[1] Poretsky, S., "Benchmarking Applicability for IGP Data Plane [1] Poretsky, S., "Benchmarking Applicability for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-05, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-app-07,
work in progress, February 2005. work in progress, July 2005.
[2] Poretsky, S., "Benchmarking Methodology for IGP Data Plane [2] Poretsky, S., "Benchmarking Methodology for IGP Data Plane
Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-05, Route Convergence", draft-ietf-bmwg-igp-dataplane-conv-meth-07,
work in progress, February 2005. work in progress, July 2005.
[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, December 1990. Environments", RFC 1195, 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] S. Casner, C. Alaettinoglu, and C. Kuan, "A Fine-Grained View [5] S. Casner, C. Alaettinoglu, and C. Kuan, "A Fine-Grained View
of High Performance Networking", NANOG 22, June 2001. of High Performance Networking", NANOG 22, June 2001.
[6] L. Ciavattone, A. Morton, and G. Ramachandran, "Standardized [6] L. Ciavattone, A. Morton, and G. Ramachandran, "Standardized
Active Measurements on a Tier 1 IP Backbone", IEEE Communications Active Measurements on a Tier 1 IP Backbone", IEEE Communications
Magazine, pp90-97, June, 2003. Magazine, pp90-97, may, 2003.
6. Author's Address 6. Author's Address
Scott Poretsky Scott Poretsky
Quarry Technologies Reef Point Systems
8 New England Executive Park 8 New England Executive Park
Burlington, MA 01803 Burlington, MA 01803
USA USA
Phone: + 1 781 395 5090 Phone: + 1 781 395 5090
EMail: sporetsky@quarrytech.com EMail: sporetsky@quarrytech.com
Brent Imhoff Brent Imhoff
USA USA
EMail: bimhoff@planetspork.com EMail: bimhoff@planetspork.com
skipping to change at page 15, line 16 skipping to change at page 15, line 16
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an attempt assurances of licenses to be made available, or the result of an attempt
made to obtain a general license or permission for the use of such made to obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can be proprietary rights by implementers or users of this specification can be
obtained from the IETF on-line IPR repository at obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
that June cover technology that June be required to implement this stan- that may cover technology that may be required to implement this stan-
dard. Please address the information to the IETF at ietf-ipr@ietf.org. dard. Please address the information to the IETF at ietf-ipr@ietf.org.
Disclaimer of Warranty Disclaimer of Warranty
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA-
TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF TION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
 End of changes. 

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