RFC 8614 on Updated Processing of Control Flags for BGP Virtual Private LAN Service (VPLS)
rfc-editor@rfc-editor.org Tue, 18 June 2019 22:28 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 11B30120301; Tue, 18 Jun 2019 15:28:33 -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 WElXtR9I9PiU; Tue, 18 Jun 2019 15:28:31 -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 73A671202EC; Tue, 18 Jun 2019 15:28:31 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BD148B822CC; Tue, 18 Jun 2019 15:28:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8614 on Updated Processing of Control Flags for BGP Virtual Private LAN Service (VPLS)
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: <20190618222810.BD148B822CC@rfc-editor.org>
Date: Tue, 18 Jun 2019 15:28:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Y_TjIXY6IGUapTadMm6L4yeC9lI>
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: Tue, 18 Jun 2019 22:28:33 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8614
Title: Updated Processing of Control Flags
for BGP Virtual Private LAN Service (VPLS)
Author: R. Singh,
K. Kompella,
S. Palislamovic
Status: Standards Track
Stream: IETF
Date: June 2019
Mailbox: ravis@juniper.net,
kireeti@juniper.net,
senad.palislamovic@nokia.com
Pages: 9
Characters: 20579
Updates: RFC 4761
I-D Tag: draft-ietf-bess-bgp-vpls-control-flags-08.txt
URL: https://www.rfc-editor.org/info/rfc8614
DOI: 10.17487/RFC8614
This document updates the meaning of the Control Flags field in the
"Layer2 Info Extended Community" used for BGP Virtual Private LAN
Service (VPLS) Network Layer Reachability Information (NLRI) as
defined in RFC 4761. This document updates RFC 4761.
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