Re: [OSPF] [RTG-DIR] Rtg Dir review of draft-ietf-ospf-sbfd-discriminator-04.txt

"Acee Lindem (acee)" <> Thu, 28 April 2016 09:25 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A451112D5F6; Thu, 28 Apr 2016 02:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.516
X-Spam-Status: No, score=-15.516 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 0zE710rwLz1A; Thu, 28 Apr 2016 02:25:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 203D712D197; Thu, 28 Apr 2016 02:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=22483; q=dns/txt; s=iport; t=1461835523; x=1463045123; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UJYHreoblsmEnhVkhdzIqRUdqPlkR+0iaegBk48IcuU=; b=TB3krjorur/xuFaQmmCGdEWXrhGOA65O+e3yT6Xuv7TtIWRzVDyo9pMJ a1zCVPTjKcwvh9RcvdUN7QjISbQyTpNm0Na1DZR6R9kwtOCT5hoLodFHR PVHYqV8ayrqJzdh8xGWbr9BSnz7ppRqiLxXhrIx92c3t0PRs61PnNuPew 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.24,546,1454976000"; d="scan'208,217";a="266313796"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Apr 2016 09:25:09 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id u3S9P9uF009269 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 28 Apr 2016 09:25:09 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 28 Apr 2016 05:25:08 -0400
Received: from ([]) by ([]) with mapi id 15.00.1104.009; Thu, 28 Apr 2016 05:25:08 -0400
From: "Acee Lindem (acee)" <>
To: "Les Ginsberg (ginsberg)" <>, Manav Bhatia <>, Adrian Farrel <>
Thread-Topic: [RTG-DIR] Rtg Dir review of draft-ietf-ospf-sbfd-discriminator-04.txt
Thread-Index: AQHRoQ9D661ZC0oqxEWFSHtLIzbuCZ+fMHSA///tHgA=
Date: Thu, 28 Apr 2016 09:25:08 +0000
Message-ID: <>
References: <069b01d1a086$46d4d470$d47e7d50$> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D3474E595DE46aceeciscocom_"
MIME-Version: 1.0
Archived-At: <>
Cc: "<>" <>, "" <>, "" <>, OSPF WG List <>
Subject: Re: [OSPF] [RTG-DIR] Rtg Dir review of draft-ietf-ospf-sbfd-discriminator-04.txt
X-Mailman-Version: 2.1.17
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: Thu, 28 Apr 2016 09:25:25 -0000

Hi Les,

From: "Les Ginsberg (ginsberg)" <<>>
Date: Thursday, April 28, 2016 at 2:32 AM
To: Manav Bhatia <<>>, Adrian Farrel <<>>
Cc: "<<>>" <<>>, Routing Directorate <<>>, "<>" <<>>, OSPF WG List <<>>
Subject: RE: [RTG-DIR] Rtg Dir review of draft-ietf-ospf-sbfd-discriminator-04.txt

Adrian –

As an interested bystander (given I am co-author on the companion IS-IS S-BFD draft) I share the concerns expressed by Carlos and Manav.

Churning S-BFD discriminator assignments is about as likely as churning IP/IPv6 address assignments on a node – it is simply not something that any deployment would be likely to do.
IGP drafts pay close attention to churn for advertisements of information which is expected to be dynamic - is a good example of this. But there is no reason to expect a similar issue with S-BFD discriminators. Therefore, for the same reasons that base protocol specifications do not discuss the impact of churn in advertising prefix reachability we saw no reason to discuss it in the context of advertising S-BFD discriminators.

Explaining why S-BFD churn is not likely a concern and that area or AS flooding will not be impacted would probably satisfy the comment. However, I won’t speak for Adrian.


It would be helpful if you provided some context as to  why you have raised this point.


From: rtg-dir [] On Behalf Of Manav Bhatia
Sent: Wednesday, April 27, 2016 10:32 PM
To: Adrian Farrel
Cc: <<>>;<>;<>; OSPF WG List
Subject: Re: [RTG-DIR] Rtg Dir review of draft-ietf-ospf-sbfd-discriminator-04.txt

Hi Adrian,

Thanks for the extensive review. I have a minor comment on a minor issue that you raised.

Minor Issues:

I should like to see some small amount of text on the scaling impact on
OSPF. 1. How much additional information will implementations have to
store per node/link in the network? 2. What is the expected churn in
LSAs introduced by this mechanism (especially when the Reflector is
turned on and off)?

Isnt this implementation specific? This is what will differentiate one vendor implementation from the other.

I am not sure how we can quantify this -- any ideas?

This is akin to saying that IS-IS, in contrast to OSPFv2, is more attuned for partial SPF runs because the node information is cleanly separated from the reachability information. However, this isnt entirely true. While i concede that node information is mixed with prefix information in OSPFv2, there still are ways in which clever implementations could separate the two and do exactly what IS-IS does.

I took this rather circuitous approach to drive home the point that scalability, churn, overheads on the system are in many cases dependent on the protocol implementation and by that token outside the scope of the IETF drafts.

You *do* have...
   A change in information in the S-BFD Discriminator TLV MUST NOT
   trigger any SPF computation at a receiving router.
...which is a help.

I would be alarmed if an implementation in an absence of this pedantic note triggered SPF runs each time an S-BFD disc changed ! I mean if you understand the idea being discussed then you also understand that a change in this TLV has no bearing on the reachability anywhere. And that knowledge should be enough to prevent SPF runs in most cases !

I know that we have added this note but if we need to explicitly spell such things out in all standards then we clearly have bigger problems ! :-)

Cheers, Manav