SRIFT: Segment Routing In Fat Trees

Document Type Expired Internet-Draft (individual)
Authors Zhaohui Zhang  , Jeff Tantsura  , Don Fedyk 
Last updated 2020-05-07 (latest revision 2019-11-04)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document specifies signaling procedures for Segment Routing [RFC8402] with RIFT. Each node's loopback address, Segment Routing Global Block (SRGB) and Node Segment Identifier (SID), which must be unique within the SR domain and are typically assigned by SR controllers or management, are distributed southbound from the Top Of Fabric (TOF) nodes via the Key-Value distribution mechanism, so that each node can compute how to reach a node represented by the topmost Node SIDs . For an ingress node to send SR traffic to another node via an explicit path, an SR controller signals the corresponding label stack to the ingress node so that the ingress node can send packets accordingly.


Zhaohui Zhang (
Jeff Tantsura (
Don Fedyk (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)