OSPF Multiple Area Links
draft-ietf-ospf-mlinks-03
Document | Type |
Expired Internet-Draft
(ospf WG)
Expired & archived
|
|
---|---|---|---|
Author | Dr. Patrick W. Murphy | ||
Last updated | 2002-02-20 | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo describes an option to the OSPF Version 2 specification which allows multiple areas to share the same OSPF link. One area is always configured as the link's primary area. The link's remaining areas are termed secondary. Two border routers adjacent across the same secondary area may forward the area's intra-area traffic across the link. This option applies to standard areas, stub areas, and NSSAs. It works over any OSPF interface. Routers with this option configured are backward compatible with routers running the standard OSPF Version 2 compliant implementation as defined in RFC 2328. Please send comments to ospf@discuss.microsoft.com.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)