[mpls] RFC 8957 on Synonymous Flow Label Framework
rfc-editor@rfc-editor.org Fri, 22 January 2021 17:23 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B5CB3A12A9; Fri, 22 Jan 2021 09:23:48 -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=unavailable 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 irIZEMlPEARy; Fri, 22 Jan 2021 09:23:45 -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 8620B3A12E5; Fri, 22 Jan 2021 09:23:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9311CF4070E; Fri, 22 Jan 2021 09:23:24 -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, mpls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210122172324.9311CF4070E@rfc-editor.org>
Date: Fri, 22 Jan 2021 09:23:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/70YtjqYsImtR8Cn1JAl75mIWo5s>
Subject: [mpls] RFC 8957 on Synonymous Flow Label Framework
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2021 17:23:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8957
Title: Synonymous Flow Label Framework
Author: S. Bryant,
M. Chen,
G. Swallow,
S. Sivabalan,
G. Mirsky
Status: Standards Track
Stream: IETF
Date: January 2021
Mailbox: sb@stewartbryant.com,
mach.chen@huawei.com,
swallow.ietf@gmail.com,
ssivabal@ciena.com,
gregimirsky@gmail.com
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-sfl-framework-11.txt
URL: https://www.rfc-editor.org/info/rfc8957
DOI: 10.17487/RFC8957
RFC 8372 ("MPLS Flow Identification Considerations") describes the
requirement for introducing flow identities within the MPLS
architecture. This document describes a method of accomplishing this
by using a technique called "Synonymous Flow Labels" in which labels
that mimic the behavior of other labels provide the identification
service. These identifiers can be used to trigger per-flow operations
on the packet at the receiving label switching router.
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