draft-ietf-rtgwg-uloop-delay-01.txt   draft-ietf-rtgwg-uloop-delay-02.txt 
Routing Area Working Group S. Litkowski Routing Area Working Group S. Litkowski
Internet-Draft B. Decraene Internet-Draft B. Decraene
Intended status: Standards Track Orange Intended status: Standards Track Orange
Expires: October 7, 2016 C. Filsfils Expires: December 5, 2016 C. Filsfils
P. Francois P. Francois
Cisco Systems Cisco Systems
April 5, 2016 June 3, 2016
Microloop prevention by introducing a local convergence delay Microloop prevention by introducing a local convergence delay
draft-ietf-rtgwg-uloop-delay-01 draft-ietf-rtgwg-uloop-delay-02
Abstract Abstract
This document describes a mechanism for link-state routing protocols This document describes a mechanism for link-state routing protocols
to prevent local transient forwarding loops in case of link failure. to prevent local transient forwarding loops in case of link failure.
This mechanism Proposes a two-steps convergence by introducing a This mechanism Proposes a two-steps convergence by introducing a
delay between the convergence of the node adjacent to the topology delay between the convergence of the node adjacent to the topology
change and the network wide convergence. change and the network wide convergence.
As this mechanism delays the IGP convergence it may only be used for As this mechanism delays the IGP convergence it may only be used for
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on October 7, 2016. This Internet-Draft will expire on December 5, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 12, line 18 skipping to change at page 12, line 18
A ------ B A ------ B
| | ^ | | ^
10 | | 5 | T 10 | | 5 | T
| | | | | |
E--------C E--------C
| 1 | 1
1 | 1 |
S S
The network above is considered to have a convergence time about 1 The network above is considered to have a convergence time about 1
second, so ULOOP_DELAY_UP_TIMER and ULOOP_DELAY_DOWN_TIMER will be second, so ULOOP_DELAY_DOWN_TIMER will be adjusted to this value. We
adjusted to this value. We also consider FRR running on each node. also consider FRR running on each node.
8.1. Local link down 8.1. Local link down
The table below describes the events and associating timing that The table below describes the events and associating timing that
happens on router C and E when link B-C goes down. As C detects a a happens on router C and E when link B-C goes down. As C detects a a
single local event corresponding to a link down (its LSP + LSP from B single local event corresponding to a link down (its LSP + LSP from B
received), it decides to apply the local delay down behavior and no received), it decides to apply the local delay down behavior and no
microloop is formed. microloop is formed.
+-----------+-------------+------------------+----------------------+ +-----------+-------------+------------------+----------------------+
skipping to change at page 21, line 31 skipping to change at page 21, line 31
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC5715] Shand, M. and S. Bryant, "A Framework for Loop-Free [RFC5715] Shand, M. and S. Bryant, "A Framework for Loop-Free
Convergence", RFC 5715, DOI 10.17487/RFC5715, January Convergence", RFC 5715, DOI 10.17487/RFC5715, January
2010, <http://www.rfc-editor.org/info/rfc5715>. 2010, <http://www.rfc-editor.org/info/rfc5715>.
14.2. Informative References 14.2. Informative References
[I-D.ietf-rtgwg-lfa-manageability] [I-D.ietf-rtgwg-lfa-manageability]
Litkowski, S., Decraene, B., Filsfils, C., Raza, K., Litkowski, S., Decraene, B., Filsfils, C., Raza, K., and
Horneffer, M., and P. Sarkar, "Operational management of M. Horneffer, "Operational management of Loop Free
Loop Free Alternates", draft-ietf-rtgwg-lfa- Alternates", draft-ietf-rtgwg-lfa-manageability-11 (work
manageability-11 (work in progress), June 2015. in progress), June 2015.
[I-D.ietf-rtgwg-microloop-analysis] [I-D.ietf-rtgwg-microloop-analysis]
Zinin, A., "Analysis and Minimization of Microloops in Zinin, A., "Analysis and Minimization of Microloops in
Link-state Routing Protocols", draft-ietf-rtgwg-microloop- Link-state Routing Protocols", draft-ietf-rtgwg-microloop-
analysis-01 (work in progress), October 2005. analysis-01 (work in progress), October 2005.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<http://www.rfc-editor.org/info/rfc3630>. <http://www.rfc-editor.org/info/rfc3630>.
 End of changes. 6 change blocks. 
10 lines changed or deleted 10 lines changed or added

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