[rfc-dist] RFC 8670 on BGP Prefix Segment in Large-Scale Data Centers

rfc-editor@rfc-editor.org Fri, 06 December 2019 22:35 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 43963120A2E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 6 Dec 2019 14:35:09 -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=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 gZDi_AyjiSZG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 6 Dec 2019 14:35:07 -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 D73CC120114 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 6 Dec 2019 14:35:03 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 10D62F40750; Fri, 6 Dec 2019 14:34:58 -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 73152F4073B; Fri, 6 Dec 2019 14:34:57 -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: <20191206223457.73152F4073B@rfc-editor.org>
Date: Fri, 6 Dec 2019 14:34:57 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8670_on_BGP_Prefix_Segment_in_Large-Sca?= =?utf-8?q?le_Data_Centers?=
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, spring@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 8670

        Title:      BGP Prefix Segment in Large-Scale 
                    Data Centers 
        Author:     C. Filsfils, Ed.,
                    S. Previdi,
                    G. Dawra,
                    E. Aries,
                    P. Lapukhov
        Status:     Informational
        Stream:     IETF
        Date:       December 2019
        Mailbox:    cfilsfil@cisco.com, 
                    stefano@previdi.net, 
                    gdawra.ietf@gmail.com,
                    exa@arrcus.com, 
                    petr@fb.com
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-segment-routing-msdc-11.txt

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

        DOI:        10.17487/RFC8670

This document describes the motivation for, and benefits of, applying
Segment Routing (SR) in BGP-based large-scale data centers. It
describes the design to deploy SR in those data centers for both the
MPLS and IPv6 data planes.

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
  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