Re: I-D Action: draft-ietf-bfd-yang-06.txt

"Reshad Rahman (rrahman)" <> Fri, 28 July 2017 01:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D5B80131ED0; Thu, 27 Jul 2017 18:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 DAltmPGim1xz; Thu, 27 Jul 2017 18:03:02 -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 46F79131ECF; Thu, 27 Jul 2017 18:03:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=10728; q=dns/txt; s=iport; t=1501203782; x=1502413382; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=wtMUGumVvQY9LySfW0XwghkGvbN3Sli00JSYRVtw62Y=; b=BjIdgAMsNdPZvxsj+Tvw6Eu8SL2fAgm6vCxnR+ytil9+CI/O2/tlGjJ0 hhzIqCbjKf2Awokg7DA3BbyE78+xfh0Ze5wdjul9B6FAHkP7XQT06Wci3 cQfSUZv5y0iSlOI6cRPgYfIn2Dv3KZFUus8SjRO7wajMXK+0SGDc7w+nS A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.40,423,1496102400"; d="scan'208";a="460790931"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jul 2017 01:03:01 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v6S131kj008611 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 28 Jul 2017 01:03:01 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 27 Jul 2017 20:03:00 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Thu, 27 Jul 2017 20:03:00 -0500
From: "Reshad Rahman (rrahman)" <>
To: "Acee Lindem (acee)" <>, Yingzhen Qu <>, Jeffrey Haas <>, "" <>
CC: "" <>, "" <>
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
Thread-Topic: I-D Action: draft-ietf-bfd-yang-06.txt
Thread-Index: AQHS8drqXiPB9yzw8Uyz6SEnSzAzYaJFxYCAgBeSvYCAAT4qwIAGf4+AgAMdioCAABQjAP//8hkAgAASYgD///B3AIAAawoA
Date: Fri, 28 Jul 2017 01:03:00 +0000
Message-ID: <>
References: <> <> <> <594D005A3CB0724DB547CF3E9A9E810B5227CF@dfweml501-mbb> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="euc-kr"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 28 Jul 2017 01:03:05 -0000

Hi Acee,

What I see @
1) bfd-client-base-cfg-parms has leaf enabled only. BTW this grouping is
defined twice, this will be fixed when I get rid of ietf-bfd-clients.yang
2) bfd-grouping-base-cfg-parms has multiplier/timers.

Let me get rid of the client module and have everything in the types

I am not sure why you’re not seeing something different.


On 2017-07-27, 3:40 PM, "Acee Lindem (acee)" <> wrote:

>Hi Reshad, 
>On 7/27/17, 3:35 PM, "Reshad Rahman (rrahman)" <> wrote:
>>Hi Acee,
>>1) I’ll see if others chime in on this but I am fine with having the
>>client grouping in ietf-bfd-types.yang.
>>2) bfd-grouping-common-cfg-parms has much more than just the
>>multiplier/timers that the IGPs need. It also has BFD specific stuff
>>(demand-mode, BFD auth) which IMO has no business outside of BFD.
>>bfd-grouping-base-cfg-parms has only the multiplier/timers.
>Perhaps, the addition of multiplier/timers to bfd-grouping-base-cfg-parms
>isn’t pushed to GitHub yet. This version
>ypes.yang only has the enabled leaf.
>>On 2017-07-27, 3:30 PM, "Acee Lindem (acee)" <> wrote:
>>>Hi Reshad, 
>>>On 7/27/17, 3:19 PM, "Reshad Rahman (rrahman)" <>
>>>>Hi Acee,
>>>>When we met we agreed to have a new model for clients. Afterwards I
>>>>decided to create a new types module, and still went ahead with the
>>>>clients module. I am fine with having everything in the types module
>>>>client module).
>>>Although I don’t feel that strongly - I just don’t see that putting the
>>>client config params in wrappers provides any benefit. As for
>>>it requires more one more local modules for validation and one more
>>>of indirection to see what we are really allowing to be configured.
>>>>I am not sure I fully understand your comment/question on
>>>>bfd-client-ext-cfg-parms/bfd-grouping-common-cfg-parms. The reason we
>>>>2 groupings is that some protocols may decide to have just the enable
>>>>and others may also want the multiplier/timer.
>>>The bfd-client-ext-cfg-parms grouping should use
>>>bfd-types:bfd-grouping-common-cfg-parms rather than
>>>bfd-types:bfd-client-base-cfg-parms - no? This would be more obvious w/o
>>>the client module.
>>>>On 2017-07-27, 3:07 PM, "Acee Lindem (acee)" <> wrote:
>>>>>Hi Reshad, 
>>>>>Why do we need a new YANG model for clients? Why can’t they just use
>>>>>ietf-bfd-types.yang? I’d like to avoid the unnecessary levels of
>>>>>indirection. In fact, it looks wrong to me since the grouping
>>>>>bfd-client-ext-cfg-parms uses the grouping bfd-grouping-base-cfg-parms
>>>>>which only contains the enabled leaf. I believe you meant to use
>>>>>bfd-grouping-common-cfg-parms in the other new model. However, I don’t
>>>>>any reason why client shouldn’t use this directly.
>>>>>On 7/25/17, 2:33 PM, "Reshad Rahman (rrahman)" <>
>>>>>>Hi Yingzhen,
>>>>>>The grouping is available @
>>>>>>If you¹d like changes to the grouping, send me an email.
>>>>>>On 2017-07-21, 12:22 PM, "Yingzhen Qu" <>
>>>>>>>Hi Reshad,
>>>>>>>Thanks for the summary.
>>>>>>>Both ospf and isis models will make corresponding changes when the
>>>>>>>BFD grouping is available.
>>>>>>>-----Original Message-----
>>>>>>>From: Reshad Rahman (rrahman) []
>>>>>>>Sent: Thursday, July 20, 2017 7:19 AM
>>>>>>>To: Jeffrey Haas <>rg>;
>>>>>>>Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
>>>>>>>We (BFD and OSPF YANG authors) had a discussion yesterday.
>>>>>>>The agreement is that since IGP peers are auto-discovered, we want
>>>>>>>back the basic BFD config (multiplier + intervals) in IGP via a
>>>>>>>BFD will provide that grouping in a specific YANG module. IGP BFD
>>>>>>>will be in a separate module (separate from the main IGP module).
>>>>>>>On 2017-07-05, 12:21 PM, "Rtg-bfd on behalf of Jeffrey Haas"
>>>>>>>< on behalf of> wrote:
>>>>>>>>Thanks authors for the edits on the BFD yang module.  This gets us
>>>>>>>>significant step closer to alignment with the rest of IETF for
>>>>>>>>I'd like to encourage the working group to provide feedback on this
>>>>>>>>issue and also the changes in the module.
>>>>>>>>As noted in another thread, we still have to figure out how to deal
>>>>>>>>with accommodating interaction of the BFD yang module with client
>>>>>>>>example, the IGPs.  In particular, how do you configure the
>>>>>>>>of the BFD sessions that may be dynamically instantiated based on
>>>>>>>>control protocol activity?
>>>>>>>>-- Jeff
>>>>>>>>On Fri, Jun 30, 2017 at 12:55:59PM -0700,
>>>>>>>>> A New Internet-Draft is available from the on-line
>>>>>>>>> This draft is a work item of the Bidirectional Forwarding
>>>>>>>>>of the IETF.
>>>>>>>>>         Title           : YANG Data Model for Bidirectional
>>>>>>>>>Detection (BFD)
>>>>>>>>>         Authors         : Reshad Rahman
>>>>>>>>>                           Lianshu Zheng
>>>>>>>>>                           Mahesh Jethanandani
>>>>>>>>>                           Santosh Pallagatti
>>>>>>>>>                           Greg Mirsky
>>>>>>>>> 	Filename        : draft-ietf-bfd-yang-06.txt
>>>>>>>>> 	Pages           : 59
>>>>>>>>> 	Date            : 2017-06-30
>>>>>>>>> Abstract:
>>>>>>>>>    This document defines a YANG data model that can be used to
>>>>>>>>>    and manage Bidirectional Forwarding Detection (BFD).
>>>>>>>>> The IETF datatracker status page for this draft is:
>>>>>>>>> There are also htmlized versions available at:
>>>>>>>>> A diff from the previous version is available at:
>>>>>>>>> Please note that it may take a couple of minutes from the time of
>>>>>>>>>submission  until the htmlized version and diff are available at
>>>>>>>>> Internet-Drafts are also available by anonymous FTP at: