[spring] RFC 9087 on Segment Routing Centralized BGP Egress Peer Engineering

rfc-editor@rfc-editor.org Sat, 14 August 2021 13:05 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id C227B3A1BDC; Sat, 14 Aug 2021 06:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id v2OgMuu5RYXs; Sat, 14 Aug 2021 06:05:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CB133A1BED; Sat, 14 Aug 2021 06:05:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2F7FEF407F3; Sat, 14 Aug 2021 06:04:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, spring@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210814130452.2F7FEF407F3@rfc-editor.org>
Date: Sat, 14 Aug 2021 06:04:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ji9RXAFcMXZ7ku8wQ-DkcL5ay7k>
Subject: [spring] RFC 9087 on Segment Routing Centralized BGP Egress Peer Engineering
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Aug 2021 13:05:47 -0000

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

        RFC 9087

        Title:      Segment Routing Centralized BGP Egress 
                    Peer Engineering 
        Author:     C. Filsfils, Ed.,
                    S. Previdi,
                    G. Dawra, Ed.,
                    E. Aries,
                    D. Afanasiev
        Status:     Informational
        Stream:     IETF
        Date:       August 2021
        Mailbox:    cfilsfil@cisco.com,
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-segment-routing-central-epe-10.txt

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

        DOI:        10.17487/RFC9087

Segment Routing (SR) leverages source routing. A node steers a packet
through a controlled set of instructions, called segments, by
prepending the packet with an SR header. A segment can represent any
instruction, topological or service based. SR allows for the
enforcement of a flow through any topological path while maintaining
per-flow state only at the ingress node of the SR domain.

The Segment Routing architecture can be directly applied to the MPLS
data plane with no change on the forwarding plane. It requires a
minor extension to the existing link-state routing protocols.

This document illustrates the application of Segment Routing to solve
the BGP Egress Peer Engineering (BGP-EPE) requirement. The SR-based
BGP-EPE solution allows a centralized (Software-Defined Networking,
or SDN) controller to program any egress peer policy at ingress
border routers or at hosts within the domain.

This document is a product of the Source Packet Routing in Networking Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

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