Re: RFC 7419 on Common Interval Support in Bidirectional Forwarding Detection

Greg Mirsky <gregimirsky@gmail.com> Thu, 01 January 2015 05:06 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43AF61A1B40 for <rtg-bfd@ietfa.amsl.com>; Wed, 31 Dec 2014 21:06:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 TabNyJRdzVjQ for <rtg-bfd@ietfa.amsl.com>; Wed, 31 Dec 2014 21:06:11 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87A9F1A1B36 for <rtg-bfd@ietf.org>; Wed, 31 Dec 2014 21:06:11 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id rd18so15467109iec.22 for <rtg-bfd@ietf.org>; Wed, 31 Dec 2014 21:06:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gyO86fXUX+QGhQaoe5qXWZUKPGK8XXqVxSshUIztgvw=; b=PiZunvDI6PJVE7Jhi1FqR0rWfDsmI3WvYWPrxCnSCpBcjbWrph4v0qLnG0g7pHvf2m XogBwNJdrGLzutCq4sNtS4lH0F2atRD7Qs1LriTqs/qXibEuF3I0j6lZp4KlHt40mEho YZr8ZKX6aeO3wTZT/ljh3cNHwQ4iZg5Q1l3ur7vFDS1oB+AbLo1B1GMqR0P8tw2puBu+ PoUaDtuWS0wLABysSkwy4+0r2RiLnoMHoJv+LJ9zFSjezBgfSVETALNrSxcowPNae0K4 4Zej3Bwg5N3AKXYTh2cUlKAod1EYcMbjAEpypLehgmtatXPKlLkX1sa7BAvAcsexTmRy TPBQ==
MIME-Version: 1.0
X-Received: by 10.50.29.107 with SMTP id j11mr57542178igh.32.1420088770431; Wed, 31 Dec 2014 21:06:10 -0800 (PST)
Received: by 10.107.174.168 with HTTP; Wed, 31 Dec 2014 21:06:10 -0800 (PST)
In-Reply-To: <CF5BA7B8-BEB7-49E4-B481-2463605785AA@pfrc.org>
References: <20150101024126.3390A180448@rfc-editor.org> <CF5BA7B8-BEB7-49E4-B481-2463605785AA@pfrc.org>
Date: Wed, 31 Dec 2014 21:06:10 -0800
Message-ID: <CA+RyBmWsd2kdGsiJrEJypmHhxix461iDFsa-x2rq=peZbjBHHw@mail.gmail.com>
Subject: Re: RFC 7419 on Common Interval Support in Bidirectional Forwarding Detection
From: Greg Mirsky <gregimirsky@gmail.com>
To: Jeff Haas <jhaas@pfrc.org>
Content-Type: multipart/alternative; boundary="047d7bd760c4b61135050b902e68"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/HEQwtn9_QBT49lhjZwJXKRVeTUw
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 01 Jan 2015 05:06:14 -0000

Happy New Year and the best wishes to All!

On Wed, Dec 31, 2014 at 7:56 PM, Jeff Haas <jhaas@pfrc.org> wrote:

> Happy new year and congratulations to the Working Group for another RFC!
>
> Jeff
>
> > On Dec 31, 2014, at 21:41, rfc-editor@rfc-editor.org wrote:
> >
> > 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,
> >                    mbinderb@cisco.com,
> >                    gregory.mirsky@ericsson.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
> >  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/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
> >
>
>