Micro-loop Prevention by Introducing a Local Convergence Delay
draft-ietf-rtgwg-uloop-delay-09

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, chrisbowers.ietf@gmail.com, rtgwg-chairs@ietf.org, akatlas@gmail.com, draft-ietf-rtgwg-uloop-delay@ietf.org, rfc-editor@rfc-editor.org, rtgwg@ietf.org
Subject: Protocol Action: 'Micro-loop prevention by introducing a local convergence delay' to Proposed Standard (draft-ietf-rtgwg-uloop-delay-09.txt)

The IESG has approved the following document:
- 'Micro-loop prevention by introducing a local convergence delay'
  (draft-ietf-rtgwg-uloop-delay-09.txt) as Proposed Standard

This document is the product of the Routing Area Working Group.

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-uloop-delay/

Ballot Text

Technical Summary

 Transient forwarding loops can occur among routers using hop-by-hop
forwarding. This document describes a mechanism for link-state routing protocols
to prevent local transient forwarding loops in case of link failure.
This mechanism proposes a two-steps convergence by introducing a
delay between the convergence of the router adjacent to the topology
change and the network wide convergence.


Working Group Summary

   The final version of the document has strong consensus in the WG. Input 
from the WG was incorporated in the document, which affected both the 
scope and substance of the document. 

Document Quality

   he document is of high quality.
  
  A Routing Area Directorate early review of draft-ietf-rtgwg-uloop-delay-01
  was done by Matthew Bocci.  It noted mainly grammatical problems, as well as a requesting a few 
  technical clarifications.  draft-ietf-rtgwg-uloop-delay-03 addressed both the
  grammatical and technical clarifications from the review.
  
  As discussed in the document, the mechanism described has at least three implementation
  and has been deployed in live networks.

Personnel

  Document Shepherd: Chris Bowers
  Responsible Area Director: Alia Atlas

RFC Editor Note