RFC 7882 on Seamless Bidirectional Forwarding Detection (S-BFD) Use Cases
rfc-editor@rfc-editor.org Wed, 13 July 2016 00:48 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 63CA012DB53;
Tue, 12 Jul 2016 17:48:47 -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 cV3nW8x2WzDt; Tue, 12 Jul 2016 17:48:42 -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 EEF0912DB38;
Tue, 12 Jul 2016 17:48:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30)
id B5D57B81347; Tue, 12 Jul 2016 17:48:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7882 on Seamless Bidirectional Forwarding Detection (S-BFD) Use
Cases
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160713004837.B5D57B81347@rfc-editor.org>
Date: Tue, 12 Jul 2016 17:48:37 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/yCKLjPm_Ewhtcs9iSWE0AqwkPas>
Cc: rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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, 13 Jul 2016 00:48:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7882
Title: Seamless Bidirectional Forwarding Detection (S-BFD)
Use Cases
Author: S. Aldrin, C. Pignataro,
G. Mirsky, N. Kumar
Status: Informational
Stream: IETF
Date: July 2016
Mailbox: aldrin.ietf@gmail.com,
cpignata@cisco.com,
gregory.mirsky@ericsson.com,
naikumar@cisco.com
Pages: 15
Characters: 35774
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-bfd-seamless-use-case-08.txt
URL: https://www.rfc-editor.org/info/rfc7882
DOI: http://dx.doi.org/10.17487/RFC7882
This document describes various use cases for Seamless Bidirectional
Forwarding Detection (S-BFD) and provides requirements such that
protocol mechanisms allow for simplified detection of forwarding
failures.
These use cases support S-BFD, which is a simplified mechanism for
using BFD with a large proportion of negotiation aspects eliminated,
accelerating the establishment of a BFD session. The benefits of
S-BFD include quick provisioning, as well as improved control and
flexibility for network nodes initiating path monitoring.
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