[trill] RFC 8564 on Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)
rfc-editor@rfc-editor.org Fri, 26 April 2019 04:04 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5FF6120292; Thu, 25 Apr 2019 21:04:31 -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 YOtmOw5Q5l5l; Thu, 25 Apr 2019 21:04:29 -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 219B3120113; Thu, 25 Apr 2019 21:04:29 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 802F2B82C07; Thu, 25 Apr 2019 21:04:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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, trill@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190426040420.802F2B82C07@rfc-editor.org>
Date: Thu, 25 Apr 2019 21:04:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/eKhLzQBlXqjzG9gOdG2eMy4kiU8>
Subject: [trill] RFC 8564 on Support of Point-to-Multipoint Bidirectional Forwarding Detection (BFD) in Transparent Interconnection of Lots of Links (TRILL)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Apr 2019 04:04:32 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8564
Title: Support of Point-to-Multipoint Bidirectional Forwarding
Detection (BFD) in Transparent Interconnection of
Lots of Links (TRILL)
Author: M. Zhang,
S. Pallagatti,
V. Govindan
Status: Standards Track
Stream: IETF
Date: April 2019
Mailbox: zhangmingui@huawei.com,
santosh.pallagatti@gmail.com,
venggovi@cisco.com
Pages: 8
Characters: 15696
Updates: RFC 7175, RFC 7177
I-D Tag: draft-ietf-trill-p2mp-bfd-09.txt
URL: https://www.rfc-editor.org/info/rfc8564
DOI: 10.17487/RFC8564
Point-to-multipoint (P2MP) Bidirectional Forwarding Detection (BFD)
is designed to verify multipoint connectivity. This document
specifies the support of P2MP BFD in Transparent Interconnection of
Lots of Links (TRILL). Similar to TRILL point-to-point BFD, BFD
Control packets in TRILL P2MP BFD are transmitted using RBridge
Channel messages. This document updates RFCs 7175 and 7177.
This document is a product of the Transparent Interconnection of Lots of Links 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