OSPF Multi-Instance Extensions
draft-acee-ospf-multi-instance-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Acee Lindem , Abhay Roy , Sina Mirtorabi | ||
Last updated | 2012-10-19 (Latest revision 2008-09-21) | ||
Replaced by | draft-ietf-ospf-multi-instance | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-ospf-multi-instance | |
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
OSPFv3 includes a mechanism for supporting multiple instances on the same link. OSPFv2 could benefit from such a mechanism in order to support multiple routing domains on the same subnet. The OSPFv2 instance ID is reserved for support of separate OSPFv2 protocol instances. This is different from OSPFv3 where it could be used for other purposes such as putting the same link in multiple areas. OSPFv2 supports this capability using a separate subnet or the OSPF multi-area adjacency capability.
Authors
Acee Lindem
Abhay Roy
Sina Mirtorabi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)