[rfc-dist] RFC 8669 on Segment Routing Prefix Segment Identifier Extensions for BGP
rfc-editor@rfc-editor.org Fri, 06 December 2019 22:34 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42E45120164 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 6 Dec 2019 14:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 QQzCrlIaM1Ko for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 6 Dec 2019 14:34:49 -0800 (PST)
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 E614F1209B7 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 6 Dec 2019 14:34:48 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C26BBF40745; Fri, 6 Dec 2019 14:34:43 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 15240F40737; Fri, 6 Dec 2019 14:34:43 -0800 (PST)
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
Message-Id: <20191206223443.15240F40737@rfc-editor.org>
Date: Fri, 06 Dec 2019 14:34:43 -0800
Subject: [rfc-dist] RFC 8669 on Segment Routing Prefix Segment Identifier Extensions for BGP
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8669
Title: Segment Routing Prefix Segment Identifier
Extensions for BGP
Author: S. Previdi,
C. Filsfils,
A. Lindem, Ed.,
A. Sreekantiah,
H. Gredler
Status: Standards Track
Stream: IETF
Date: December 2019
Mailbox: stefano@previdi.net,
cfilsfils@cisco.com,
acee@cisco.com,
arjunhrs@gmail.com,
hannes@rtbrick.com
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-idr-bgp-prefix-sid-27.txt
URL: https://www.rfc-editor.org/info/rfc8669
DOI: 10.17487/RFC8669
Segment Routing (SR) leverages the source-routing paradigm. A node
steers a packet through an ordered list of instructions called
"segments". A segment can represent any instruction, topological or
service based. The ingress node prepends an SR header to a packet
containing a set of segment identifiers (SIDs). Each SID represents a
topological or service-based instruction. Per-flow state is
maintained only on the ingress node of the SR domain. An "SR domain"
is defined as a single administrative domain for global SID
assignment.
This document defines an optional, transitive BGP attribute for
announcing information about BGP Prefix Segment Identifiers (BGP
Prefix-SIDs) and the specification for SR-MPLS SIDs.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org