MPLS Encapsulation for SFC NSH
draft-malis-mpls-sfc-encapsulation-03

Document Type Replaced Internet-Draft (mpls WG)
Last updated 2018-10-30 (latest revision 2018-10-11)
Replaced by draft-ietf-mpls-sfc-encapsulation
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd Loa Andersson
IESG IESG state Replaced by draft-ietf-mpls-sfc-encapsulation
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Loa Andersson <loa@pi.nu>

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-malis-mpls-sfc-encapsulation-03.txt

Abstract

This document describes how to use a Service Function Forwarder (SFF) Label (similar to a pseudowire label or VPN label) to indicate the presence of a Service Function Chaining (SFC) Network Service Header (NSH) between an MPLS label stack and the packet payload. This allows SFC packets using the NSH to be forwarded between SFFs over an MPLS network, and the selection between multiple SFFs in the destination MPLS node.

Authors

Andrew Malis (agmalis@gmail.com)
Stewart Bryant (stewart.bryant@gmail.com)
Joel Halpern (joel.halpern@ericsson.com)
Wim Henderickx (wim.henderickx@nokia.com)

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