RFC 6549: OSPFv2 Multi-Instance Extensions
In plain English — editorial summary, not part of the RFC
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. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6549
- Published
- March 2012
- Authors
- A. Lindem; A. Roy; S. Mirtorabi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Updates:
- RFC 2328
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5838Support of Address Families in OSPFv3Updated
April 2010
- RFC 7254A Uniform Resource Name Namespace for the Global System for Mobile Communications Association (GSMA) and the International Mobile station Equipment Identity (IMEI)Current
May 2014
- RFC 7255Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance IDCurrent
May 2014
- RFC 8464A URN Namespace for Device Identity and Mobile Equipment Identity (MEID)Current
September 2018
- RFC 8465Using the Mobile Equipment Identity (MEID) URN as an Instance IDCurrent
September 2018
- RFC 6550RPL: IPv6 Routing Protocol for Low-Power and Lossy NetworksUpdated
March 2012
- RFC 6551Routing Metrics Used for Path Calculation in Low-Power and Lossy NetworksCurrent
March 2012
- RFC 6552Objective Function Zero for the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
March 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?