Segment Routing in IP RAN use case
draft-kh-spring-ip-ran-use-case-02

Document Type Expired Internet-Draft (individual)
Last updated 2015-05-14 (latest revision 2014-11-10)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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
https://www.ietf.org/archive/id/draft-kh-spring-ip-ran-use-case-02.txt

Abstract

Segment Routing (SR) leverages the source routing paradigm. An ingress node steers a packet through a controlled set of instructions, called segments, by pre-pending the packet with an SR header. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to an SR node or global within an SR domain. SR allows one to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node of the SR domain. This document introduces the segment routing in IP Radio Access Network (IP RAN, mobile backhaul network) use case. Additional requirements to support segment routing in the IP RAN scenarios are discussed.

Authors

Bhumip Khasnabish (bhumip.khasnabish@ztetx.com)
fangwei hu (hu.fangwei@zte.com.cn)
Luis Contreras (luismiguel.contrerasmurillo@telefonica.com)

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