RFC 8595 on An MPLS-Based Forwarding Plane for Service Function Chaining
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 807DC120161; Fri, 7 Jun 2019 13:50:06 -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 vLS8kowkWwrA; Fri, 7 Jun 2019 13:50:04 -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 5FD891201B4; Fri, 7 Jun 2019 13:50:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8EE75B8092C; Fri, 7 Jun 2019 13:49:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8595 on An MPLS-Based Forwarding Plane for Service Function Chaining
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: <20190607204953.8EE75B8092C@rfc-editor.org>
Date: Fri, 07 Jun 2019 13:49:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/HCn8AKJLKfyIIeeScmL1TcMMNoA>
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:07 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8595
Title: An MPLS-Based Forwarding Plane for
Service Function Chaining
Author: A. Farrel,
S. Bryant,
J. Drake
Status: Standards Track
Stream: IETF
Date: June 2019
Mailbox: adrian@olddog.co.uk,
stewart.bryant@gmail.com,
jdrake@juniper.net
Pages: 32
Characters: 69090
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-sfc-07.txt
URL: https://www.rfc-editor.org/info/rfc8595
DOI: 10.17487/RFC8595
This document describes how Service Function Chaining (SFC) can be
achieved in an MPLS network by means of a logical representation of
the Network Service Header (NSH) in an MPLS label stack. That is,
the NSH is not used, but the fields of the NSH are mapped to fields
in the MPLS label stack. This approach does not deprecate or replace
the NSH, but it acknowledges that there may be a need for an interim
deployment of SFC functionality in brownfield networks.
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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