RFC 9161 on Operational Aspects of Proxy ARP/ND in Ethernet Virtual Private Networks

rfc-editor@rfc-editor.org Fri, 14 January 2022 05:36 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 C6D063A1B2B; Thu, 13 Jan 2022 21:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 YUgNiY_k6hMR; Thu, 13 Jan 2022 21:36:25 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B29923A1B1C; Thu, 13 Jan 2022 21:36:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 499) id 6DEF4F5DCE; Thu, 13 Jan 2022 21:36:23 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9161 on Operational Aspects of Proxy ARP/ND in Ethernet Virtual Private Networks
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: <20220114053623.6DEF4F5DCE@rfc-editor.org>
Date: Thu, 13 Jan 2022 21:36:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/JkgChAHtE5d1nCfmTPGpCjb_m9k>
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: Fri, 14 Jan 2022 05:36:32 -0000

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

        
        RFC 9161

        Title:      Operational Aspects of Proxy ARP/ND 
                    in Ethernet Virtual Private Networks 
        Author:     J. Rabadan, Ed.,
                    S. Sathappan,
                    K. Nagaraj,
                    G. Hankins,
                    T. King
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2022
        Mailbox:    jorge.rabadan@nokia.com,
                    senthil.sathappan@nokia.com,
                    kiran.nagaraj@nokia.com,
                    greg.hankins@nokia.com,
                    thomas.king@de-cix.net
        Pages:      22
        Updates:    RFC 7432

        I-D Tag:    draft-ietf-bess-evpn-proxy-arp-nd-16.txt

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

        DOI:        10.17487/RFC9161

This document describes the Ethernet Virtual Private Network (EVPN)
Proxy ARP/ND function augmented by the capability of the ARP/ND
Extended Community. From that perspective, this document updates the
EVPN specification to provide more comprehensive documentation of the
operation of the Proxy ARP/ND function. The EVPN Proxy ARP/ND
function and the ARP/ND Extended Community help operators of Internet
Exchange Points, Data Centers, and other networks deal with IPv4 and
IPv6 address resolution issues associated with large Broadcast
Domains by reducing and even suppressing the flooding produced by
address resolution in the EVPN network.

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