RFC 9658: Multipoint LDP Extensions for Multi-Topology Routing
In plain English — editorial summary, not part of the RFC
Multi-Topology Routing (MTR) is a technology that enables service differentiation within an IP network. The Flexible Algorithm (FA) is another mechanism for creating a sub-topology within a topology using defined topology constraints and computation algorithms. In order to deploy Multipoint LDP (mLDP) in a network that supports MTR, FA, or other methods of signaling non-default IGP Algorithms (IPAs), mLDP is required to become topology and algorithm aware. This document specifies extensions to mLDP to support the use of MTR/IPAs such that, when building multipoint Label Switched Paths (LSPs), the LSPs can follow a particular topology and algorithm. This document updates RFC 7307 by allocating eight bits from a previously reserved field to be used as the "IPA" field.
Document record
- Document ID
- RFC9658
- Published
- October 2024
- Authors
- IJ. Wijnands; M. Mishra; K. Raza; Z. Zhang; A. Gulko
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Updates:
- RFC 7307
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9214OSPFv3 Code Point for MPLS LSP PingCurrent
April 2022
- RFC 9085Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment RoutingUpdated
August 2021
- RFC 9070YANG Data Model for MPLS LDPCurrent
March 2022
- RFC 9020YANG Data Model for Segment RoutingCurrent
May 2021
- RFC 9017Special-Purpose Label TerminologyCurrent
April 2021
- RFC 8964Deterministic Networking (DetNet) Data Plane: MPLSCurrent
January 2021
- RFC 8957Synonymous Flow Label FrameworkCurrent
January 2021
- RFC 8690Clarification of Segment ID Sub-TLV Length for RFC 8287Current
December 2019
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?