RFC 8596 on MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)
rfc-editor@rfc-editor.org Fri, 07 June 2019 20:50 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5DFD120296; Fri, 7 Jun 2019 13:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAx_fG7Z0eqx; Fri, 7 Jun 2019 13:50:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C1A120277; Fri, 7 Jun 2019 13:50:12 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 80358B80B08; Fri, 7 Jun 2019 13:50:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8596 on MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190607205001.80358B80B08@rfc-editor.org>
Date: Fri, 07 Jun 2019 13:50:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gZX56c5jQKKxR4wSOdPRCbu_Cd4>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2019 20:50:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8596
Title: MPLS Transport Encapsulation for the
Service Function Chaining (SFC) Network Service
Header (NSH)
Author: A. Malis,
S. Bryant,
J. Halpern,
W. Henderickx
Status: Informational
Stream: IETF
Date: June 2019
Mailbox: agmalis@gmail.com,
stewart.bryant@gmail.com,
joel.halpern@ericsson.com,
wim.henderickx@nokia.com
Pages: 9
Characters: 18605
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-sfc-encapsulation-04.txt
URL: https://www.rfc-editor.org/info/rfc8596
DOI: 10.17487/RFC8596
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 original packet/
frame. This allows SFC packets using the NSH to be forwarded between
SFFs over an MPLS network, and to select one of multiple SFFs in the
destination MPLS node.
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC