RFC 8971 on Bidirectional Forwarding Detection (BFD) for Virtual eXtensible Local Area Network (VXLAN)

rfc-editor@rfc-editor.org Mon, 14 December 2020 15:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916D53A10B0; Mon, 14 Dec 2020 07:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[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 HU2YbPqGfTS9; Mon, 14 Dec 2020 07:52:40 -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 874E23A10A7; Mon, 14 Dec 2020 07:52:40 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DA138F40705; Mon, 14 Dec 2020 07:52:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8971 on Bidirectional Forwarding Detection (BFD) for Virtual eXtensible Local Area Network (VXLAN)
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, rtg-bfd@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201214155236.DA138F40705@rfc-editor.org>
Date: Mon, 14 Dec 2020 07:52:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/4Q5Z5K1117ZYUjCWj6oJoQUN-14>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Dec 2020 15:52:45 -0000

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

        
        RFC 8971

        Title:      Bidirectional Forwarding Detection (BFD) for 
                    Virtual eXtensible Local Area Network (VXLAN) 
        Author:     S. Pallagatti, Ed.,
                    G. Mirsky, Ed.,
                    S. Paragiri,
                    V. Govindan,
                    M. Mudigonda
        Status:     Informational
        Stream:     IETF
        Date:       December 2020
        Mailbox:    santosh.pallagatti@gmail.com, 
                    gregimirsky@gmail.com, 
                    sudarsan.225@gmail.com,
                    venggovi@cisco.com, 
                    mmudigon@cisco.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bfd-vxlan-16.txt

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

        DOI:        10.17487/RFC8971

This document describes the use of the Bidirectional Forwarding
Detection (BFD) protocol in point-to-point Virtual eXtensible Local
Area Network (VXLAN) tunnels used to form an overlay network.

This document is a product of the Bidirectional Forwarding Detection Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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