Last Call Review of draft-ietf-rtgwg-spf-uloop-pb-statement-10
review-ietf-rtgwg-spf-uloop-pb-statement-10-opsdir-lc-chown-2019-01-28-00
Request | Review of | draft-ietf-rtgwg-spf-uloop-pb-statement |
---|---|---|
Requested revision | No specific revision (document currently at 10) | |
Type | Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2018-12-18 | |
Requested | 2018-12-04 | |
Authors | Stephane Litkowski , Bruno Decraene , Martin Horneffer | |
I-D last updated | 2019-01-28 | |
Completed reviews |
Rtgdir Early review of -03
by Tomonori Takeda
(diff)
Rtgdir Last Call review of -08 by Tomonori Takeda (diff) Genart Last Call review of -08 by Dan Romascanu (diff) Secdir Last Call review of -09 by Phillip Hallam-Baker (diff) Opsdir Last Call review of -10 by Tim Chown |
|
Assignment | Reviewer | Tim Chown |
State | Completed Snapshot | |
Review |
review-ietf-rtgwg-spf-uloop-pb-statement-10-opsdir-lc-chown-2019-01-28
|
|
Reviewed revision | 10 | |
Result | Ready | |
Completed | 2019-01-28 |
review-ietf-rtgwg-spf-uloop-pb-statement-10-opsdir-lc-chown-2019-01-28-00
Hi, I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. This draft looks at the impact of using different link state IGPs on transient micro-loops that may occur between two or more routers in a hop-by-hop packet forwarding scenario, usually caused when formed when two routers fail to update their FIBs for a given prefix at the same time. While a final conclusion section would be desirable, the document is otherwise ready for publication.