RFC 7880 on Seamless Bidirectional Forwarding Detection (S-BFD)
rfc-editor@rfc-editor.org Wed, 13 July 2016 00:48 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 F06DD12D0E1; Tue, 12 Jul 2016 17:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 FviA3Mom4H3X; Tue, 12 Jul 2016 17:48:04 -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 6C5C712D66D; Tue, 12 Jul 2016 17:48:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 65EE6B81336; Tue, 12 Jul 2016 17:48:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7880 on Seamless Bidirectional Forwarding Detection (S-BFD)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160713004804.65EE6B81336@rfc-editor.org>
Date: Tue, 12 Jul 2016 17:48:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/SLv4IHgxS7-H3CZpwT315uD2RWQ>
Cc: rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 13 Jul 2016 00:48:06 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7880
Title: Seamless Bidirectional Forwarding Detection (S-BFD)
Author: C. Pignataro, D. Ward,
N. Akiya, M. Bhatia, S. Pallagatti
Status: Standards Track
Stream: IETF
Date: July 2016
Mailbox: cpignata@cisco.com,
wardd@cisco.com,
nobo.akiya.dev@gmail.com,
manav@ionosnetworks.com,
santosh.pallagatti@gmail.com
Pages: 24
Characters: 45987
Updates: RFC 5880
I-D Tag: draft-ietf-bfd-seamless-base-11.txt
URL: https://www.rfc-editor.org/info/rfc7880
DOI: http://dx.doi.org/10.17487/RFC7880
This document defines Seamless Bidirectional Forwarding Detection
(S-BFD), a simplified mechanism for using BFD with a large proportion
of negotiation aspects eliminated, thus providing benefits such as
quick provisioning, as well as improved control and flexibility for
network nodes initiating path monitoring.
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