RFC 8584 on Framework for Ethernet VPN Designated Forwarder Election Extensibility

rfc-editor@rfc-editor.org Thu, 25 April 2019 04:12 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 36BBD120137; Wed, 24 Apr 2019 21:12:39 -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 kU1a0_NG_ICi; Wed, 24 Apr 2019 21:12:37 -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 47E2E1200B8; Wed, 24 Apr 2019 21:12:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7116FB81B66; Wed, 24 Apr 2019 21:12:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8584 on Framework for Ethernet VPN Designated Forwarder Election Extensibility
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: <20190425041229.7116FB81B66@rfc-editor.org>
Date: Wed, 24 Apr 2019 21:12:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/z5JJfCDmkkHHkw6DXn4lAAeSHOk>
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: Thu, 25 Apr 2019 04:12:39 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8584

        Title:      Framework for Ethernet VPN Designated 
                    Forwarder Election Extensibility 
        Author:     J. Rabadan, Ed.,
                    S. Mohanty, Ed.,
                    A. Sajassi, 
                    J. Drake,
                    K. Nagaraj, 
                    S. Sathappan
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2019
        Mailbox:    jorge.rabadan@nokia.com, 
                    satyamoh@cisco.com, 
                    sajassi@cisco.com,  
                    jdrake@juniper.net, 
                    kiran.nagaraj@nokia.com,  
                    senthil.sathappan@nokia.com
        Pages:      32
        Characters: 69774
        Updates:    RFC 7432

        I-D Tag:    draft-ietf-bess-evpn-df-election-framework-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8584

        DOI:        10.17487/RFC8584

An alternative to the default Designated Forwarder (DF) selection
algorithm in Ethernet VPNs (EVPNs) is defined.  The DF is the
Provider Edge (PE) router responsible for sending Broadcast, Unknown
Unicast, and Multicast (BUM) traffic to a multihomed Customer Edge
(CE) device on a given VLAN on a particular Ethernet Segment (ES).
In addition, the ability to influence the DF election result for a
VLAN based on the state of the associated Attachment Circuit (AC) is
specified.  This document clarifies the DF election Finite State
Machine in EVPN services.  Therefore, it updates the EVPN
specification (RFC 7432).

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