[mpls] RFC 9658 on Multipoint LDP Extensions for Multi-Topology Routing

A new Request for Comments is now available in online RFC libraries.

        RFC 9658

        Title:      Multipoint LDP Extensions for Multi-Topology 
                    Routing 
        Author:     IJ. Wijnands,
                    M. Mishra, Ed.,
                    K. Raza,
                    Z. Zhang,
                    A. Gulko
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2024
        Mailbox:    ice@braindump.be,
                    mankamis@cisco.com,
                    skraza@cisco.com,
                    zzhang@juniper.net,
                    arkadiy.gulko@edwardjones.com
        Pages:      14
        Updates:    RFC 7307

        I-D Tag:    draft-ietf-mpls-mldp-multi-topology-09.txt

        URL:        https://www.rfc-editor.org/info/rfc9658

        DOI:        10.17487/RFC9658

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.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC