RFC 7419 on Common Interval Support in Bidirectional Forwarding Detection

rfc-editor@rfc-editor.org Thu, 01 January 2015 02:41 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 (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id D3C751A1B22; Wed, 31 Dec 2014 18:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Z-Bl1h5_ITcu; Wed, 31 Dec 2014 18:41:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 442CE1A1B21; Wed, 31 Dec 2014 18:41:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3390A180448; Wed, 31 Dec 2014 18:41:26 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7419 on Common Interval Support in Bidirectional Forwarding Detection
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150101024126.3390A180448@rfc-editor.org>
Date: Wed, 31 Dec 2014 18:41:26 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/XDPNMiSVRm4xSDMTnd6g7R5-bk4
Cc: rtg-bfd@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 01 Jan 2015 02:41:34 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7419

        Title:      Common Interval Support in Bidirectional 
                    Forwarding Detection 
        Author:     N. Akiya, M. Binderberger, G. Mirsky
        Status:     Informational
        Stream:     IETF
        Date:       December 2014
        Mailbox:    nobo@cisco.com, 
        Pages:      8
        Characters: 16944
        Updates:    RFC 5880

        I-D Tag:    draft-ietf-bfd-intervals-05.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7419.txt

Bidirectional Forwarding Detection (BFD) requires that messages be
transmitted at regular intervals and provides a way to negotiate the
interval used by BFD peers.  Some BFD implementations may be
restricted to only support several interval values.  When such BFD
implementations speak to each other, there is a possibility of two
sides not being able to find a common value for the interval to run
BFD sessions.

This document updates RFC 5880 by defining a small set of interval
values for BFD that we call "Common Intervals" and recommends
implementations to support the defined intervals.  This solves the
problem of finding an interval value that both BFD speakers can
support while allowing a simplified implementation as seen for
hardware-based BFD.  It does not restrict an implementation from
supporting more intervals in addition to the Common Intervals.

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

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