CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 14:32:24 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=pJGG7K4eNtlx3D1S1wCoAKR9tH1J9wEe4xHDvctr6LY-1760193144-1.0.1.1-9uuC4pr8Tu3mXCrxAuxzKdjdbXwVSF6STs0a6yQcpTuXRAT6dmDc5inH41zo9kWkd.K12LWs4RIoYFvf0fiLPnAR0X_A_ZrpGOpMN6wAxfs; path=/; expires=Sat, 11-Oct-25 15:02:24 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cf11090c4da403-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8670 » RFC Editor
Search RFCs
RFC 8670
BGP Prefix Segment in Large-Scale Data Centers, December 2019
- File formats:
- Also available: XML file for editing
- Status:
- INFORMATIONAL
- Authors:
- C. Filsfils, Ed.
S. Previdi
G. Dawra
E. Aries
P. Lapukhov - Stream:
- IETF
- Source:
- spring (rtg)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8670
Discuss this RFC: Send questions or comments to the mailing list spring@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8670
Abstract
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us