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

        
        RFC 9830

        Title:      Advertising Segment Routing Policies in BGP 
        Author:     S. Previdi,
                    C. Filsfils,
                    K. Talaulikar, Ed.,
                    P. Mattes,
                    D. Jain
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2025
        Mailbox:    [email protected],
                    [email protected],
                    [email protected],
                    [email protected],
                    [email protected]
        Pages:      36
        Updates:    RFC 9012

        I-D Tag:    draft-ietf-idr-sr-policy-safi-13.txt

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

        DOI:        10.17487/RFC9830

A Segment Routing (SR) Policy is an ordered list of segments (also
referred to as "instructions") that define a source-routed policy. An
SR Policy consists of one or more Candidate Paths (CPs), each
comprising one or more segment lists. A headend can be provisioned
with these CPs using various mechanisms such as Command-Line
Interface (CLI), Network Configuration Protocol (NETCONF), Path
Computation Element Communication Protocol (PCEP), or BGP.

This document specifies how BGP can be used to distribute SR Policy
CPs. It introduces a BGP SAFI for advertising a CP of an SR Policy
and defines sub-TLVs for the Tunnel Encapsulation Attribute to signal
information related to these CPs.

Furthermore, this document updates RFC 9012 by extending the Color
Extended Community to support additional steering modes over SR
Policy.

This document is a product of the Inter-Domain Routing 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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org

Reply via email to