Protocol Action: 'Graceful OSPF Restart' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Fri, 15 August 2003 20:29 UTC

Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12386 for <ietf-announce-web-archive@odin.ietf.org>; Fri, 15 Aug 2003 16:29:43 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19nkke-0000mi-2k for ietf-announce-list@asgard.ietf.org; 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
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, OSPF@PEACH.EASE.LSOFT.COM
Subject: Protocol Action: 'Graceful OSPF Restart' to Proposed Standard
Message-Id: <E19nkjU-0000ix-Nb@asgard.ietf.org>
Date: Fri, 15 Aug 2003 15:59:32 -0400
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

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.