RFC 9086 on Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing 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: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B8A3A1BDB; Sat, 14 Aug 2021 06:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eN78X44p5K4o; Sat, 14 Aug 2021 06:05:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E9A53A1BD7; Sat, 14 Aug 2021 06:05:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 62348F407D4; Sat, 14 Aug 2021 06:04:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9086 on Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing BGP Egress Peer Engineering
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, idr@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210814130427.62348F407D4@rfc-editor.org>
Date: Sat, 14 Aug 2021 06:04:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/uVgmUsU20d71edj_iaPDKU2KZDk>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Aug 2021 13:05:10 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9086
Title: Border Gateway Protocol - Link State (BGP-LS)
Extensions for Segment Routing BGP
Egress Peer Engineering
Author: S. Previdi,
K. Talaulikar, Ed.,
C. Filsfils,
K. Patel,
S. Ray,
J. Dong
Status: Standards Track
Stream: IETF
Date: August 2021
Mailbox: stefano@previdi.net,
ketant@cisco.com,
cfilsfil@cisco.com,
keyur@arrcus.com,
raysaikat@gmail.com,
jie.dong@huawei.com
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgpls-segment-routing-epe-19.txt
URL: https://www.rfc-editor.org/info/rfc9086
DOI: 10.17487/RFC9086
A node steers a packet through a controlled set of instructions,
called segments, by prepending the packet with a list of segment
identifiers (SIDs). A segment can represent any instruction,
topological or service based. SR segments allow steering a flow
through any topological path and service chain while maintaining
per-flow state only at the ingress node of the SR domain.
This document describes an extension to Border Gateway Protocol -
Link State (BGP-LS) for advertisement of BGP Peering Segments along
with their BGP peering node information so that efficient BGP Egress
Peer Engineering (EPE) policies and strategies can be computed based
on Segment Routing.
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 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