RFC 8604 on Interconnecting Millions of Endpoints with Segment Routing
rfc-editor@rfc-editor.org Mon, 17 June 2019 22:42 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 55EF1120234 for <ietf-announce@ietfa.amsl.com>; Mon, 17 Jun 2019 15:42:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 sQ0qywcRozmy for <ietf-announce@ietfa.amsl.com>; Mon, 17 Jun 2019 15:42:51 -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 75A381202F3 for <ietf-announce@ietf.org>; Mon, 17 Jun 2019 15:42:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B5D70B80D43; Mon, 17 Jun 2019 15:42:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8604 on Interconnecting Millions of Endpoints with Segment Routing
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190617224231.B5D70B80D43@rfc-editor.org>
Date: Mon, 17 Jun 2019 15:42:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/AmXr4n_1mniEOukBxF2M8S9Fl2o>
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: Mon, 17 Jun 2019 22:42:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8604
Title: Interconnecting Millions of Endpoints
with Segment Routing
Author: C. Filsfils, Ed.,
S. Previdi,
G. Dawra, Ed.,
W. Henderickx,
D. Cooper
Status: Informational
Stream: Independent
Date: June 2019
Mailbox: cfilsfil@cisco.com,
stefano@previdi.net,
gdawra.ietf@gmail.com,
wim.henderickx@nokia.com,
Dave.Cooper@centurylink.com
Pages: 11
Characters: 20559
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-filsfils-spring-large-scale-interconnect-13.txt
URL: https://www.rfc-editor.org/info/rfc8604
DOI: 10.17487/RFC8604
This document describes an application of Segment Routing to scale
the network to support hundreds of thousands of network nodes, and
tens of millions of physical underlay endpoints. This use case can
be applied to the interconnection of massive-scale Data Centers (DCs)
and/or large aggregation networks. Forwarding tables of midpoint and
leaf nodes only require a few tens of thousands of entries. This may
be achieved by the inherently scaleable nature of Segment Routing and
the design proposed in this document.
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