NSH and Segment Routing Integration for Service Function Chaining (SFC)
draft-guichard-spring-nsh-sr-01
Document | Type | Replaced Internet-Draft (candidate for spring WG) | |
---|---|---|---|
Authors | Jim Guichard , Haoyu Song , Jeff Tantsura , Joel Halpern , Wim Henderickx , Mohamed Boucadair , Syed Hassan | ||
Last updated | 2019-06-27 (latest revision 2019-03-11) | ||
Replaces | draft-guichard-sfc-nsh-sr | ||
Replaced by | draft-ietf-spring-nsh-sr | ||
Stream | Internent Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | Replaced by draft-ietf-spring-nsh-sr | |
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-guichard-spring-nsh-sr-01.txt
Abstract
This document describes two application scenarios where Network Service Header (NSH) and Segment Routing (SR) techniques can be deployed together to support Service Function Chaining (SFC) in an efficient manner while maintaining separation of the service and transport planes as originally intended by the SFC architecture. In the first scenario, an NSH-based SFC is created using SR as the transport between SFFs. SR in this case is just one of many encapsulations that could be used to maintain the transport- independent nature of NSH-based service chains. In the second scenario, SR is used to represent each service hop of the NSH-based SFC as a segment within the segment-list. SR and NSH in this case are integrated. In both scenarios SR is responsible for steering packets between SFFs along a given SFP while NSH is responsible for maintaining the integrity of the service plane, the SFC instance context, and any associated metadata. These application scenarios demonstrate that NSH and SR can work jointly and complement each other leaving the network operator with the flexibility to use whichever transport technology makes sense in specific areas of their network infrastructure, and still maintain an end-to-end service plane using NSH.
Authors
Jim Guichard
(james.n.guichard@huawei.com)
Haoyu Song
(haoyu.song@huawei.com)
Jeff Tantsura
(jefftant.ietf@gmail.com)
Joel Halpern
(joel.halpern@ericsson.com)
Wim Henderickx
(wim.henderickx@nokia.com)
Mohamed Boucadair
(mohamed.boucadair@orange.com)
Syed Hassan
(shassan@cisco.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)