[nvo3] RFC 9521 on Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve)
rfc-editor@rfc-editor.org Tue, 16 January 2024 21:06 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06EB7C14F619; Tue, 16 Jan 2024 13:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2g7lHTYLF_0Q; Tue, 16 Jan 2024 13:05:56 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6322C14F61A; Tue, 16 Jan 2024 13:05:56 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id A3C05B3AF0; Tue, 16 Jan 2024 13:05:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nvo3@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240116210556.A3C05B3AF0@rfcpa.amsl.com>
Date: Tue, 16 Jan 2024 13:05:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/FaxJa2ku2w5U4eATRnwNI2N6RJ0>
Subject: [nvo3] RFC 9521 on Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve)
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2024 21:06:01 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9521
Title: Bidirectional Forwarding Detection (BFD) for
Generic Network Virtualization Encapsulation (Geneve)
Author: X. Min,
G. Mirsky,
S. Pallagatti,
J. Tantsura,
S. Aldrin
Status: Standards Track
Stream: IETF
Date: January 2024
Mailbox: xiao.min2@zte.com.cn,
gregimirsky@gmail.com,
santosh.pallagatti@gmail.com,
jefftant.ietf@gmail.com,
aldrin.ietf@gmail.com
Pages: 11
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-nvo3-bfd-geneve-13.txt
URL: https://www.rfc-editor.org/info/rfc9521
DOI: 10.17487/RFC9521
This document describes the use of the Bidirectional Forwarding
Detection (BFD) protocol in point-to-point Generic Network
Virtualization Encapsulation (Geneve) unicast tunnels used to make up
an overlay network.
This document is a product of the Network Virtualization Overlays 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