MPLS Encapsulation for SFC NSH
draft-malis-mpls-sfc-encapsulation-03
Document | Type |
Replaced Internet-Draft
(mpls WG)
Expired & archived
|
|
---|---|---|---|
Authors | Andrew G. Malis , Stewart Bryant , Joel M. Halpern , Wim Henderickx | ||
Last updated | 2018-10-30 (Latest revision 2018-10-11) | ||
Replaced by | draft-ietf-mpls-sfc-encapsulation | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
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 | (None) | ||
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 is available in these formats:
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 G. Malis
Stewart Bryant
Joel M. Halpern
Wim Henderickx
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)