Protocol Action: 'Graceful OSPF Restart' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Fri, 15 August 2003 20:10 UTC
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11768 for <ospf-archive@LISTS.IETF.ORG>; Fri, 15 Aug 2003 16:10:52 -0400 (EDT)
Received: from PEACH.EASE.LSOFT.COM (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <2.00ADE7CF@cherry.ease.lsoft.com>; Fri, 15 Aug 2003 16:10:44 -0400
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 51304073 for OSPF@PEACH.EASE.LSOFT.COM; Fri, 15 Aug 2003 16:10:44 -0400
Received: from 132.151.6.40 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Fri, 15 Aug 2003 16:00:44 -0400
Received: from apache by asgard.ietf.org with local (Exim 4.14) id 19nkjU-0000ix-Nb; Fri, 15 Aug 2003 15:59:32 -0400
X-test-idtracker: no
Message-ID: <E19nkjU-0000ix-Nb@asgard.ietf.org>
Date: Fri, 15 Aug 2003 15:59:32 -0400
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Comments: RFC822 error: <W> Incorrect or incomplete address field found and ignored.
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: 'Graceful OSPF Restart' to Proposed Standard
Comments: cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
To: OSPF@PEACH.EASE.LSOFT.COM
Precedence: list
The IESG has approved the Internet-Draft 'Graceful OSPF Restart' <draft-ietf-ospf-hitless-restart-08.txt> as a Proposed Standard. This document is the product of the Open Shortest Path First IGP Working Group. The IESG contact persons are Alex Zinin and Bill Fenner. Technical Summary This memo documents an enhancement to the OSPF routing protocol, whereby an OSPF router can stay on the forwarding path even as its OSPF software is restarted. This is called "graceful restart" or "non-stop forwarding". Deployment of this mechanism in the service provider networks should decrease unnecessary path recalculation and traffic rerouting. Working Group Summary The WG considered two proposals to address the graceful restart problem--the one represented in draft-nguyen-ospf-restart, and the one described in the submitted document. The main difference between the two proposals was in the mechanism for graceful restart signaling, database synchronization and determining when graceful restart had completed. At the 50th IETF in Minneapolis the WG made a decision via rough consensus to proceed with the latter approach, which since then has receive substantial technical review within the WG and passed the WG Last Call. The described mechanism has been implemented and deployed by several vendors. Protocol Quality The specification has been reviewed for the IESG by Alex Zinin.