RFC 3623 on Graceful OSPF Restart
rfc-editor@rfc-editor.org Fri, 14 November 2003 23:46 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 SAA05647 for <ietf-announce-web-archive@odin.ietf.org>; Fri, 14 Nov 2003 18:46:53 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1AKnMo-0002LG-Dt for ietf-announce-list@asgard.ietf.org; Fri, 14 Nov 2003 18:28:42 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1AKnJI-00025B-BP for all-ietf@asgard.ietf.org; Fri, 14 Nov 2003 18:25:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05103 for <all-ietf@ietf.org>; Fri, 14 Nov 2003 18:24:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AKnJG-0006Im-00 for all-ietf@ietf.org; Fri, 14 Nov 2003 18:25:02 -0500
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 1AKnJF-0006Id-00 for all-ietf@ietf.org; Fri, 14 Nov 2003 18:25:01 -0500
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id hAENOxs02329; Fri, 14 Nov 2003 15:24:59 -0800 (PST)
Message-Id: <200311142324.hAENOxs02329@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3623 on Graceful OSPF Restart
Cc: rfc-editor@rfc-editor.org, ospf@peach.ease.lsoft.com
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 14 Nov 2003 15:24:59 -0800
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3623 Title: Graceful OSPF Restart Author(s): J. Moy, P. Pillay-Esnault, A. Lindem Status: Standards Track Date: November 2003 Mailbox: jmoy@sycamorenet.com, padma@juniper.net, acee@redback.com Pages: 18 Characters: 38757 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ospf-hitless-restart-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3623.txt 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". A restarting router may not be capable of adjusting its forwarding in a timely manner when the network topology changes. In order to avoid the possible resulting routing loops, the procedure in this memo automatically reverts to a normal OSPF restart when such a topology change is detected, or when one or more of the restarting router's neighbors do not support the enhancements in this memo. Proper network operation during a graceful restart makes assumptions upon the operating environment of the restarting router; these assumptions are also documented. This document is a product of the Open Shortest Path First IGP Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3623 on Graceful OSPF Restart rfc-editor