Service Function Chaining with Stitched Tunnels
draft-hegde-spring-sfc-stitched-tunnel-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shraddha Hegde , Colby Barth | ||
| Last updated | 2021-07-11 (Latest revision 2021-01-07) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
The term "service function chaining" is used to describe the definition and instantiation of an ordered list of instances of such service functions, and the subsequent "steering" of traffic flows through those service functions.This document describes transport mechanisms that use stitched tunnels to achieve end-to-end service chaining. This document specifies two different types of transport encodings, one based on SR-MPLS and another based on IP tunnels.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)