RFC 4915: Multi-Topology (MT) Routing in OSPF
In plain English — editorial summary, not part of the RFC
This document describes an extension to Open Shortest Path First (OSPF) in order to define independent IP topologies called Multi- Topologies (MTs). The Multi-Topologies extension can be used for computing different paths for unicast traffic, multicast traffic, different classes of service based on flexible criteria, or an in- band network management topology. An optional extension to exclude selected links from the default topology is also described. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4915
- Published
- June 2007
- Authors
- P. Psenak; S. Mirtorabi; A. Roy; L. Nguyen; P. Pillay-Esnault
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4940IANA Considerations for OSPFCurrent
July 2007
- RFC 4970Extensions to OSPF for Advertising Optional Router CapabilitiesObsoleted
July 2007
- RFC 4750OSPF Version 2 Management Information BaseCurrent
December 2006
- RFC 5088OSPF Protocol Extensions for Path Computation Element (PCE) DiscoveryUpdated
January 2008
- RFC 5185OSPF Multi-Area AdjacencyCurrent
May 2008
- RFC 5187OSPFv3 Graceful RestartCurrent
June 2008
- RFC 5250The OSPF Opaque LSA OptionCurrent
July 2008
- RFC 5252OSPF-Based Layer 1 VPN Auto-DiscoveryCurrent
July 2008
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?