Re: [OSPF] Advertising S-BFD discriminators in OSPF

Manav Bhatia <> Fri, 26 September 2014 01:27 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3E1551A00B0 for <>; Thu, 25 Sep 2014 18:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7CilKkiZrhIu for <>; Thu, 25 Sep 2014 18:27:27 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 93EFC1A00F2 for <>; Thu, 25 Sep 2014 18:27:27 -0700 (PDT)
Received: by with SMTP id u20so8992378oif.29 for <>; Thu, 25 Sep 2014 18:27:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kQdpjS4pMOaoCve2mX4zcSxt9X1S/RR2V0vfNw0fD1k=; b=DfUwWaK104ziGslnifHwRgLLAO1avqslNUJFl066of+Vpna18XkVvcBzBFoMkeOvvC UsWJjP3qa0zlYX/8ehO3CZVC5V1R5uIEvt7F0wjMFT/ms78Nl25Q1Je9mjBVa46Plzjn jqiU3WPMM9H+QlElzRVbbZXxHnf2G3HfSMKGDdQIB8c/nCE6fndCIJm9eUpI609pwi6Z hHn9jVKCgOegeA+9birlMI7avgpmng60MzEDM6BYT+J1qRa4XdGAZbYbZb2T1sUIgsn/ mHWDHWCM5suKajzP1iFrWLq0m6JPmOOsynKXcyV87vH3Qi4LcEitRChE+FDT0bUGfW/o /0Ew==
MIME-Version: 1.0
X-Received: by with SMTP id pm8mr6505129oeb.76.1411694846878; Thu, 25 Sep 2014 18:27:26 -0700 (PDT)
Received: by with HTTP; Thu, 25 Sep 2014 18:27:26 -0700 (PDT)
In-Reply-To: <>
References: <> <>
Date: Fri, 26 Sep 2014 06:57:26 +0530
Message-ID: <>
From: Manav Bhatia <>
To: Michael Barnes <>
Content-Type: text/plain; charset=UTF-8
Cc: OSPF - OSPF WG List <>
Subject: Re: [OSPF] Advertising S-BFD discriminators in OSPF
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Sep 2014 01:27:29 -0000

Hi Michael,

Very interesting.

I think there is a disconnect because of our interpretation of what an
RI LSA is envisioned to carry. I assume its meant to advertise
"optional router capabilities" while you believe its to be used solely
for advertising "optional OSPF router capabilities". IMO, limiting the
scope of RI to just OSPF is like using a humvee with all its bells and
whistles to distribute balloons to the children in your friendly
neighborhood park! We wanted a mechanism wherein each router could
proudly tell the world that it was an S-BFD capable node and along
with it also advertise the unique discriminator that the others would
use to reach it. RI we felt, was the perfect tool that we could use
for this purpose.

And btw we're not the first ones to use RI for advertising a router
capability that isnt pertinent to OSPF per se (RFC 5088).

Cheers, Manav

On Fri, Sep 26, 2014 at 12:47 AM, Michael Barnes <> wrote:
> Hi Manav,
> Perhaps I missed some earlier discussion, on why you decided to add the
> S-BFD Discriminator TLV to the RI LSA, but I would prefer it not be in that
> LSA. I would like to leave the RI LSA with only information pertinent to
> OSPF rather than pollute it with information for which OSPF has no interest.
> If you're concerned with a trend of creating a new Opaque type for every
> application which might want OSPF to carry information for it, then I would
> suggest we create a generic Application Information LSA.
> Regards,
> Michael
> On 05/30/2014 01:47 AM, Manav Bhatia wrote:
>> Hi,
>> We had submitted the following draft a couple of weeks ago.
>> This draft introduces a new OSPF RI TLV that allows OSPF routers to
>> flood the S-BFD discriminator values in the routing domain.
>> S-BFD is a new charter item (will be approved very soon) in the BFD WG.
>> Would appreciate comments on this.
>> Cheers, Manav
>> _______________________________________________
>> OSPF mailing list