RFC 8562 on Bidirectional Forwarding Detection (BFD) for Multipoint Networks
rfc-editor@rfc-editor.org Wed, 03 April 2019 03:07 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 5F926120475; Tue, 2 Apr 2019 20:07:10 -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 res35tegc29b; Tue, 2 Apr 2019 20:07:07 -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 62246120479; Tue, 2 Apr 2019 20:07:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E9B5BB8242D; Tue, 2 Apr 2019 20:06:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8562 on Bidirectional Forwarding Detection (BFD) for Multipoint Networks
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: <20190403030652.E9B5BB8242D@rfc-editor.org>
Date: Tue, 02 Apr 2019 20:06:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/6BtBQ-16yTpYKRV1H5nDAV_iuP0>
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: Wed, 03 Apr 2019 03:07:16 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8562 Title: Bidirectional Forwarding Detection (BFD) for Multipoint Networks Author: D. Katz, D. Ward, S. Pallagatti, Ed., G. Mirsky, Ed. Status: Standards Track Stream: IETF Date: April 2019 Mailbox: dkatz@juniper.net, wardd@cisco.com, santosh.pallagatti@gmail.com, gregimirsky@gmail.com Pages: 23 Characters: 45501 Updates: RFC 5880 I-D Tag: draft-ietf-bfd-multipoint-19.txt URL: https://www.rfc-editor.org/info/rfc8562 DOI: 10.17487/RFC8562 This document describes extensions to the Bidirectional Forwarding Detection (BFD) protocol for its use in multipoint and multicast networks. This document updates RFC 5880. This document is a product of the Bidirectional Forwarding Detection 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