Skip to main content

Network Service Header (NSH) and Segment Routing Integration for Service Function Chaining (SFC)
draft-ietf-spring-nsh-sr-01

The information below is for an old version of the document.
Document Type This is an older version of an Internet-Draft whose latest revision is Active
Authors Jim Guichard , Haoyu Song , Jeff Tantsura , Joel M. Halpern , Wim Henderickx , Mohamed Boucadair , Syed Hassan
Last updated 2020-04-06 (Latest revision 2019-10-04)
Replaces draft-guichard-spring-nsh-sr
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
Reviews
OPSDIR Last Call Review Incomplete, due 2022-06-30
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 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 Service Function Forwarders (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 Service Function Path (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
Haoyu Song
Jeff Tantsura
Joel M. Halpern
Wim Henderickx
Mohamed Boucadair
Syed Hassan

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