OSPFv2 Multi-Instance Extensions
RFC 6549
| Document | Type |
RFC - Proposed Standard
(March 2012; Errata)
Updates RFC 2328
|
|
|---|---|---|---|
| Last updated | 2018-12-20 | ||
| Replaces | draft-acee-ospf-multi-instance | ||
| Stream | IETF | ||
| Formats | plain text pdf htmlized with errata bibtex | ||
| Reviews | |||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 6549 (Proposed Standard) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Stewart Bryant | ||
| IESG note | Manav Bhatia (manav.bhatia@alcatel-lucent.com) is the document shepherd. | ||
| Send notices to | manav.bhatia@alcatel-lucent.com | ||
Internet Engineering Task Force (IETF) A. Lindem
Request for Comments: 6549 Ericsson
Updates: 2328 A. Roy
Category: Standards Track S. Mirtorabi
ISSN: 2070-1721 Cisco Systems
March 2012
OSPFv2 Multi-Instance Extensions
Abstract
OSPFv3 includes a mechanism to support multiple instances of the
protocol running on the same interface. OSPFv2 can utilize such a
mechanism in order to support multiple routing domains on the same
subnet.
This document defines the OSPFv2 Instance ID to enable separate
OSPFv2 protocol instances on the same interface. Unlike OSPFv3 where
the Instance ID can be used for multiple purposes, such as putting
the same interface in multiple areas, the OSPFv2 Instance ID is
reserved for identifying protocol instances.
This document updates RFC 2328.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 5741.
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6549.
Lindem, et al. Standards Track [Page 1]
RFC 6549 OSPFv2 Multi-Instance Extensions March 2012
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction ....................................................2
1.1. Requirements Notation ......................................3
2. OSPFv2 Instance Packet Encoding .................................3
3. OSPFv2 Interface Instance ID ....................................4
3.1. Sending and Receiving OSPFv2 Packets .......................4
3.2. Interface Instance ID Values ...............................4
4. State Sharing Optimizations between OSPFv2 Instances ............5
5. OSPFv2 Authentication Impacts ...................................5
6. Backward Compatibility and Deployment Considerations ............5
7. Security Considerations .........................................6
8. IANA Considerations .............................................6
9. References ......................................................7
9.1. Normative References .......................................7
9.2. Informative References .....................................7
Appendix A. Acknowledgments.... ....................................8
1. Introduction
OSPFv3 [OSPFV3] includes a mechanism to support multiple instances of
a protocol running on the same interface. OSPFv2 [OSPFV2] can
utilize such a mechanism in order to support multiple routing domains
on the same subnet.
This document defines the OSPFv2 Instance ID to enable separate
OSPFv2 protocol instances on the same interface. Unlike OSPFv3 where
the Instance ID can be used for multiple purposes, such as putting
the same interface in multiple areas, the OSPFv2 Instance ID is
reserved for identifying protocol instances.
Lindem, et al. Standards Track [Page 2]
RFC 6549 OSPFv2 Multi-Instance Extensions March 2012
1.1. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC-KEYWORDS].
2. OSPFv2 Instance Packet Encoding
This document extends OSPFv2 with a mechanism to differentiate
packets for different instances sent and received on the same
interface. In support of this capability, a modified packet header
format with the Authentication Type field split into an Instance ID
and AuType.
0 1 2 3
Show full document text