Last Call: <draft-ietf-bfd-intervals-03.txt> (Common Interval Support in BFD) to Informational RFC

The IESG <> Tue, 19 August 2014 00:42 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D37531A872C; Mon, 18 Aug 2014 17:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AykT4ZEzurDj; Mon, 18 Aug 2014 17:42:55 -0700 (PDT)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id A782F1A8725; Mon, 18 Aug 2014 17:42:55 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <>
To: IETF-Announce <>
Subject: Last Call: <draft-ietf-bfd-intervals-03.txt> (Common Interval Support in BFD) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p5
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Mon, 18 Aug 2014 17:42:55 -0700
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 19 Aug 2014 00:42:57 -0000

The IESG has received a request from the Bidirectional Forwarding
Detection WG (bfd) to consider the following document:
- 'Common Interval Support in BFD'
  <draft-ietf-bfd-intervals-03.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the mailing lists by 2014-09-01. Exceptionally, comments may be
sent to instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.


   BFD requires that messages are 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 interval
   value to run BFD sessions.

   This document defines 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.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.