draft-ietf-bmwg-protection-term-06.txt   draft-ietf-bmwg-protection-term-07.txt 
Network Working Group S. Poretsky Network Working Group S. Poretsky
Internet Draft Allot Communications Internet Draft Allot Communications
Expires: September 8, 2009 Expires: April 2010
Intended Status: Informational Rajiv Papneja Intended Status: Informational Rajiv Papneja
Isocore Isocore
J. Karthik J. Karthik
S. Vapiwala S. Vapiwala
Cisco Systems Cisco Systems
March 8, 2009 October 2009
Benchmarking Terminology for Protection Performance Benchmarking Terminology
<draft-ietf-bmwg-protection-term-06.txt > for Protection Performance
<draft-ietf-bmwg-protection-term-07.txt >
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may 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 months Internet-Drafts are draft documents valid for a maximum of six months
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 September 8, 2009. This Internet-Draft will expire on April 15, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
skipping to change at page 25, line 16 skipping to change at page 25, line 16
3.6.2 Packet-Loss Based Method (PLBM) 3.6.2 Packet-Loss Based Method (PLBM)
Definition: Definition:
The method used to calculate Failover Time (or Reversion Time) The method used to calculate Failover Time (or Reversion Time)
from the amount of Failover Packet Loss. from the amount of Failover Packet Loss.
Discussion: Discussion:
PLBM includes failure detection time and time for data traffic to PLBM includes failure detection time and time for data traffic to
begin traversing the Backup Path. Failover Time can be begin traversing the Backup Path. Failover Time can be
calculated using PLBM from the amount Failover Packet Loss as calculated using PLBM from the amount Failover Packet Loss as
shown below in Equation 3: shown below in Equation 3. Note: If traffic is sent to more than 1
destination, PLBM gives the average loss over the measured destinations
(Equation 3) (Equation 3)
(Equation 3a) (Equation 3a)
PLBM Failover Time = PLBM Failover Time =
Number of packets lost / Number of packets lost /
(Offered Load rate * 1000) (Offered Load rate * 1000)
(Equation 3b) (Equation 3b)
PLBM Restoration Time = PLBM Restoration Time =
Number of packets lost / Number of packets lost /
skipping to change at page 27, line 18 skipping to change at page 27, line 18
Network-layer Traffic Control Mechanisms", RFC 4689, Network-layer Traffic Control Mechanisms", RFC 4689,
November 2006. November 2006.
[5] Bradner, S., "Key words for use in RFCs to Indicate [5] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, July 1997. Requirement Levels", RFC 2119, July 1997.
[6] Not used. [6] Not used.
[7] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP [7] Poretsky, S., Imhoff, B., "Benchmarking Terminology for IGP
Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-16, Convergence", draft-ietf-bmwg-igp-dataplane-conv-term-16,
work in progress, March 2009. work in progress, October 2009.
[8] Pan., P. et al, "Fast Reroute Extensions to RSVP-TE for LSP [8] Pan., P. et al, "Fast Reroute Extensions to RSVP-TE for LSP
Paths", RFC 4090, May 2005. Paths", RFC 4090, May 2005.
[9] Nichols, K., et al, "Definition of the Differentiated [9] Nichols, K., et al, "Definition of the Differentiated
Services Field (DS Field) in the IPv4 and IPv6 Headers", Services Field (DS Field) in the IPv4 and IPv6 Headers",
RFC 2474, December 1998. RFC 2474, December 1998.
[10] Morton, A., et al, "Packet Reordering Metrics", RFC 4737, [10] Morton, A., et al, "Packet Reordering Metrics", RFC 4737,
November 2006. November 2006.
 End of changes. 7 change blocks. 
14 lines changed or deleted 16 lines changed or added

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