[sfc] RFC 8979 on Subscriber and Performance Policy Identifier Context Headers in the Network Service Header (NSH)
rfc-editor@rfc-editor.org Sat, 06 February 2021 06: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 D90EC3A0E21;
Fri, 5 Feb 2021 22:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, 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 7jrx4p0r3Cfd; Fri, 5 Feb 2021 22:58:13 -0800 (PST)
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 D2FB83A0E1E;
Fri, 5 Feb 2021 22:58:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30)
id 98A6BF40740; Fri, 5 Feb 2021 22:57:51 -0800 (PST)
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: <20210206065751.98A6BF40740@rfc-editor.org>
Date: Fri, 5 Feb 2021 22:57:51 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/-8gh9TJW3-nuvHiQzuoiFEr3hj4>
Subject: [sfc] =?utf-8?q?RFC_8979_on_Subscriber_and_Performance_Policy_Id?=
=?utf-8?q?entifier_Context_Headers_in_the_Network_Service_Header_=28NSH?=
=?utf-8?q?=29?=
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 06 Feb 2021 06:58:16 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8979
Title: Subscriber and Performance Policy Identifier
Context Headers in the Network Service
Header (NSH)
Author: B. Sarikaya,
D. von Hugo,
M. Boucadair
Status: Standards Track
Stream: IETF
Date: February 2021
Mailbox: sarikaya@ieee.org,
dirk.von-hugo@telekom.de,
mohamed.boucadair@orange.com
Pages: 11
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-sfc-serviceid-header-14.txt
URL: https://www.rfc-editor.org/info/rfc8979
DOI: 10.17487/RFC8979
This document defines the Subscriber and Performance Policy
Identifier Context Headers. These Variable-Length Context Headers
can be carried in the Network Service Header (NSH) and are used to
inform Service Functions (SFs) of subscriber- and performance-related
information for the sake of policy enforcement and appropriate
Service Function Chaining (SFC) operations. The structure of each
Context Header and their use and processing by NSH-aware nodes are
described.
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