[sfc] RFC 8393 on Operating the Network Service Header (NSH) with Next Protocol "None"
rfc-editor@rfc-editor.org Tue, 08 May 2018 22:58 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1639F12EB55; Tue, 8 May 2018 15:58:37 -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 cpSbB7qTAf_Y; Tue, 8 May 2018 15:58:35 -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 0CD7512EB27; Tue, 8 May 2018 15:58:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C7ADCB81C54; Tue, 8 May 2018 15:58:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, sfc@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180508225822.C7ADCB81C54@rfc-editor.org>
Date: Tue, 08 May 2018 15:58:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/0Xidk4YWwtmfnYGE-7uPs85TC_E>
Subject: [sfc] RFC 8393 on Operating the Network Service Header (NSH) with Next Protocol "None"
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 22:58:37 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8393
Title: Operating the Network Service Header (NSH)
with Next Protocol "None"
Author: A. Farrel,
J. Drake
Status: Standards Track
Stream: IETF
Date: May 2018
Mailbox: afarrel@juniper.net,
jdrake@juniper.net
Pages: 12
Characters: 27141
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-farrel-sfc-convent-06.txt
URL: https://www.rfc-editor.org/info/rfc8393
DOI: 10.17487/RFC8393
This document describes a network that supports Service Function
Chaining (SFC) using the Network Service Header (NSH) with no payload
data and carrying only metadata. This is achieved by defining a new
NSH "Next Protocol" type value of "None".
This document illustrates some of the functions that may be achieved
or enhanced by this mechanism, but it does not provide an exhaustive
list of use cases, nor is it intended to be definitive about the
functions it describes. It is expected that other documents will
describe specific use cases in more detail and will define the
protocol mechanics for each use case.
This document is a product of the Service Function Chaining 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