SRIFT: Segment Routing in Fat Trees
draft-ietf-rift-sr-03
| Document | Type |
Expired Internet-Draft
(rift WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhaohui (Jeffrey) Zhang , Jeff Tantsura , Jordan Head | ||
| Last updated | 2026-09-18 (Latest revision 2026-03-17) | ||
| Replaces | draft-zzhang-rift-sr | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies signaling procedures for Segment Routing in RIFT. Each node's loopback address, Segment Routing Global Block (SRGB) and Node Segment Identifier (Node-SID), which are typically assigned by a configuration management system and distibuted by routing protocols, are distributed southbound from the Top Of Fabric (TOF) nodes via RIFT's Key-Value distribution mechanism, so that each node can compute how to reach a segment represented by the active SID in a packet. An SR controller signals SR policies to ingress nodes so that they can send packets with a desired segment list to steer traffic.
Authors
Zhaohui (Jeffrey) Zhang
Jeff Tantsura
Jordan Head
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)