Alternative Implementations of OSPF Area Border Routers
draft-ietf-ospf-abr-alt-05
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 3509.
|
|
---|---|---|---|
Authors | Derek M. Yeung , Acee Lindem , Alex D. Zinin | ||
Last updated | 2015-10-14 (Latest revision 2002-10-24) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 3509 (Informational) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Bill Fenner | ||
IESG note | |||
Send notices to | <rohit@utstar.com>, <john.moy@sycamorenet.com> |
draft-ietf-ospf-abr-alt-05
A new Request for Comments is now available in online RFC libraries. RFC 3509 Title: Alternative Implementations of OSPF Area Border Routers Author(s): A. Zinin, A. Lindem, D. Yeung Status: Informational Date: April 2003 Mailbox: zinin@psg.com, acee@redback.com, myeung@procket.com Pages: 12 Characters: 24326 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ospf-abr-alt-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3509.txt Open Shortest Path First (OSPF) is a link-state intra-domain routing protocol used for routing in IP networks. Though the definition of the Area Border Router (ABR) in the OSPF specification does not require a router with multiple attached areas to have a backbone connection, it is actually necessary to provide successful routing to the inter-area and external destinations. If this requirement is not met, all traffic destined for the areas not connected to such an ABR or out of the OSPF domain, is dropped. This document describes alternative ABR behaviors implemented in Cisco and IBM routers. This document is a product of the Open Shortest Path First IGP Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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.