[bess] RFC 8395 on Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
rfc-editor@rfc-editor.org Wed, 27 June 2018 05:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43230130F40; Tue, 26 Jun 2018 22:36:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 RfDacJaxWZJf; Tue, 26 Jun 2018 22:36:32 -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 0B4C2130EF3; Tue, 26 Jun 2018 22:36:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 68605B81236; Tue, 26 Jun 2018 22:36:27 -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, bess@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180627053627.68605B81236@rfc-editor.org>
Date: Tue, 26 Jun 2018 22:36:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/Ef5Rc-HkfGqngiu4o_zKhBAFicc>
Subject: [bess] RFC 8395 on Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2018 05:36:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8395
Title: Extensions to BGP-Signaled Pseudowires to
Support Flow-Aware Transport Labels
Author: K. Patel,
S. Boutros,
J. Liste,
B. Wen,
J. Rabadan
Status: Standards Track
Stream: IETF
Date: June 2018
Mailbox: keyur@arrcus.com,
sboutros@vmware.com,
jliste@cisco.com,
bin_wen@cable.comcast.com,
jorge.rabadan@nokia.com
Pages: 10
Characters: 17404
Updates: RFC 4761
I-D Tag: draft-ietf-bess-fat-pw-bgp-04.txt
URL: https://www.rfc-editor.org/info/rfc8395
DOI: 10.17487/RFC8395
This document defines protocol extensions required to synchronize flow
label states among Provider Edges (PEs) when using the BGP-based
signaling procedures. These protocol extensions are equally
applicable to point-to-point Layer 2 Virtual Private Networks
(L2VPNs). This document updates RFC 4761 by defining new flags in the
Control Flags field of the Layer2 Info Extended Community.
This document is a product of the BGP Enabled Services 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