Skip to main content

Segment Routing Policy Architecture
draft-filsfils-spring-segment-routing-policy-06

Document Type Replaced Internet-Draft (spring WG)
Expired & archived
Authors Clarence Filsfils , Siva Sivabalan , Shraddha Hegde , Daniel Voyer , Steven Lin , Alex Bogdanov , Przemysław Gniewomir Król , Martin Horneffer , Dirk Steinberg , Bruno Decraene , Stephane Litkowski , Paul Mattes , Zafar Ali , Ketan Talaulikar , Jose Liste , Francois Clad , Syed Raza
Last updated 2018-05-30 (Latest revision 2018-05-21)
Replaced by RFC 9256
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
Stream WG state Adopted by a WG
Revised I-D Needed - Issue raised by WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-spring-segment-routing-policy
Consensus boilerplate Yes
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

Segment Routing (SR) allows a headend node to steer a packet flow along any path. Intermediate per-flow states are eliminated thanks to source routing. The headend node steers a flow into an SR Policy. The header of a packet steered in an SR Policy is augmented with the ordered list of segments associated with that SR Policy. This document details the concepts of SR Policy and steering into an SR Policy.

Authors

Clarence Filsfils
Siva Sivabalan
Shraddha Hegde
Daniel Voyer
Steven Lin
Alex Bogdanov
Przemysław Gniewomir Król
Martin Horneffer
Dirk Steinberg
Bruno Decraene
Stephane Litkowski
Paul Mattes
Zafar Ali
Ketan Talaulikar
Jose Liste
Francois Clad
Syed Raza

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