Jeff, I agree.
Regards,
Reshad.
On 2017-08-14, 1:10 PM, "Jeffrey Haas" wrote:
>
>> On Aug 14, 2017, at 11:24 AM, Reshad Rahman (rrahman)
>> wrote:
>>
>> I am gradually catching up to emails so I may not have absorbed all the
>> emails I have gone through yetŠ.
>>
>> Regarding echo config,
> On Aug 14, 2017, at 11:24 AM, Reshad Rahman (rrahman)
> wrote:
>
> I am gradually catching up to emails so I may not have absorbed all the
> emails I have gone through yetŠ.
>
> Regarding echo config, we agreed in Chicago to remove the echo config
> based on the fact that implementations of
I am gradually catching up to emails so I may not have absorbed all the
emails I have gone through yetŠ.
Regarding echo config, we agreed in Chicago to remove the echo config
based on the fact that implementations of echo are vendor specific. e.g.
An implementation which has echo as continuous wou
> On Aug 7, 2017, at 9:47 AM, Jeffrey Haas wrote:
>
> On Tue, Aug 01, 2017 at 05:52:01PM -0700, Mahesh Jethanandani wrote:
>> I will be uploading the changes shortly.
>
> Are we at the point where we should look at the model contents again?
The BFD model is uploaded and should be evaluated to
On Tue, Aug 01, 2017 at 05:52:01PM -0700, Mahesh Jethanandani wrote:
> I will be uploading the changes shortly.
Are we at the point where we should look at the model contents again?
-- Jeff
> On Aug 1, 2017, at 9:33 AM, Jeffrey Haas wrote:
>
> On Tue, Aug 01, 2017 at 08:33:38AM -0700, Mahesh Jethanandani wrote:
>>> I'm ambivalent. This depends really on real world behavior.
>>>
>>> As we saw from some brief googling yesterday on Cisco IOS/IOS-XR docs, that
>>> implementation does
On Tue, Aug 01, 2017 at 08:33:38AM -0700, Mahesh Jethanandani wrote:
> > I'm ambivalent. This depends really on real world behavior.
> >
> > As we saw from some brief googling yesterday on Cisco IOS/IOS-XR docs, that
> > implementation doesn't appear to expose echo intervals as a separably
> > co
> On Aug 1, 2017, at 7:41 AM, Jeffrey Haas wrote:
>
> Mahesh,
>
> On Mon, Jul 31, 2017 at 05:17:34PM -0700, Mahesh Jethanandani wrote:
>>> My point, unless my very quick glance at the module mislead me, is that you
>>> can't configure to use echo mode - if it's supported - in the grouping
>>>
Mahesh,
On Mon, Jul 31, 2017 at 05:17:34PM -0700, Mahesh Jethanandani wrote:
> > My point, unless my very quick glance at the module mislead me, is that you
> > can't configure to use echo mode - if it's supported - in the grouping
> > imported by the IGPs.
>
> In the current model, it is model
Ashesh,
On Mon, Jul 31, 2017 at 09:39:57PM +, Ashesh Mishra wrote:
> From what I understand, the echo intervals have an inverse relationship with
> their control interval counterparts. Faster echo allows for slower control
> frame rate. So they are necessarily different values. That said, ha
> On Jul 31, 2017, at 1:55 PM, Jeffrey Haas wrote:
>
> Mahesh,
>
>> On Jul 31, 2017, at 4:26 PM, Mahesh Jethanandani
>> wrote:
>>
>> Jeff,
>>
>>> On Jul 31, 2017, at 10:05 AM, Jeffrey Haas wrote:
>>>
>>> On Fri, Jul 28, 2017 at 03:58:06PM -0700, Mahesh Jethanandani wrote:
The changes
>From what I understand, the echo intervals have an inverse relationship with
>their control interval counterparts. Faster echo allows for slower control
>frame rate. So they are necessarily different values. That said, having never
>implemented echo mode, I can't comment how they should get gro
Mahesh,
> On Jul 31, 2017, at 4:26 PM, Mahesh Jethanandani
> wrote:
>
> Jeff,
>
>> On Jul 31, 2017, at 10:05 AM, Jeffrey Haas wrote:
>>
>> On Fri, Jul 28, 2017 at 03:58:06PM -0700, Mahesh Jethanandani wrote:
>>> The changes are done and pushed to GitHub. Use the grouping
>>> client-cfg-parm
Jeff,
> On Jul 31, 2017, at 10:05 AM, Jeffrey Haas wrote:
>
> On Fri, Jul 28, 2017 at 03:58:06PM -0700, Mahesh Jethanandani wrote:
>> The changes are done and pushed to GitHub. Use the grouping client-cfg-parms.
>
> Question: For implementations that use Echo mode, is that something the
> proto
d enable leaf. ISIS model need to do the same
>>>> change, ietf-isis-bfd.yang will look the same as ietf-ospf-bfd.yang.
>>>>
>>>> Please let me know your commetns.
>>>>
>>>> Thanks,
>>>> Yingzhen
>>>>
>>>>
acee) ; Reshad Rahman ;
> Jeffrey Haas ; rtg-bfd@ietf.org;
> draft-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
> Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
>
> Yingzhen,
>
> Overall the model looks good to me.
>
> I notice that you decided to (re)define t
-Original Message-
>>> From: Mahesh Jethanandani [mailto:mjethanand...@gmail.com]
>>> Sent: Friday, July 28, 2017 2:25 PM
>>> To: Acee Lindem (acee)
>>> Cc: Reshad Rahman ; Yingzhen Qu
>>>; Jeffrey Haas ;
>>>rtg-bfd@ietf.org; draft-ietf-bfd-y...@
;
>> -Original Message-
>> From: Mahesh Jethanandani [mailto:mjethanand...@gmail.com]
>> Sent: Friday, July 28, 2017 2:25 PM
>> To: Acee Lindem (acee)
>> Cc: Reshad Rahman ; Yingzhen Qu
>>; Jeffrey Haas ;
>>rtg-bfd@ietf.org; draft-ietf-bfd-y...@ie
com]
Sent: Sunday, July 30, 2017 9:43 PM
To: Yingzhen Qu
Cc: Acee Lindem (acee) ; Reshad Rahman ;
Jeffrey Haas ; rtg-bfd@ietf.org; draft-ietf-bfd-y...@ietf.org;
draft-ietf-ospf-y...@ietf.org
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
Yingzhen,
Overall the model looks good to me.
I n
On Sun, Jul 30, 2017 at 05:14:28PM +, Yingzhen Qu wrote:
> Please see attached ospf bfd module. Base ospf module also needs to be
> updated to remove the bfd enable leaf. ISIS model need to do the same change,
> ietf-isis-bfd.yang will look the same as ietf-ospf-bfd.yang.
>
> Please let me k
On Fri, Jul 28, 2017 at 03:58:06PM -0700, Mahesh Jethanandani wrote:
> The changes are done and pushed to GitHub. Use the grouping client-cfg-parms.
Question: For implementations that use Echo mode, is that something the
protocol client configuration impacts or is it chosen by the system
automatic
rds,
>>>>>>> Reshad.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 2017-07-27, 3:07 PM, "Acee Lindem (acee)" wrote:
>>>>>>>
>>>>>>>> Hi Reshad,
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
>>>>
gt;>>
>>>>>>>> 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
>>>>>&
e
>>>>>>> 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.
>>>>>>>
>>
t;>>
>>>>>>> Regards,
>>>>>>> Reshad.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 2017-07-27, 3:07 PM, "Acee Lindem (acee)"
>>>>>>>
t;> 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
>>
draft-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
Thanks Yingzhen. FYI I will be on holiday for the next 2 weeks.
Acee, can you please get in touch with ISIS YANG authors?
Regards,
Reshad.
On 2017-07-28, 12:25 PM, "Yingzhen Qu&quo
t;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.
>>>>>>>
>>>>>&
rg
Cc: draft-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
Thanks much Reshad - Yingzhen will be adding but the ietf-ospf-bfd module to
the OSPF model and draft.
Acee
On 7/28/17, 11:08 AM, "Reshad Rahman (rrahman)" wrote:
&
;>>Thanks,
>>>>>>Acee
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>Regards,
>>>>>>>Reshad.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>&
odel 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
>>&g
e
>>>>>>bfd-grouping-common-cfg-parms in the other new model. However, I
>>>>>>don’t
>>>>>>see
>>>>>>any reason why client shouldn’t use this directly.
>>>>>>Thanks,
>>>>>>Acee
>>>>
>see
>>>>>any reason why client shouldn’t use this directly.
>>>>>Thanks,
>>>>>Acee
>>>>>
>>>>>On 7/25/17, 2:33 PM, "Reshad Rahman (rrahman)"
>>>>>wrote:
>>>>>
>>>>
grouping is available @
>>>>>https://github.com/jhaas-pfrc/ietf-bfd-yang/blob/master/src/yang/ietf-
>>>>>b
>>>>>f
>>>>>d
>>>>>-
>>>>>c
>>>>>lients.yang
>>>>>
>>
egards,
>>>>Reshad.
>>>>
>>>>On 2017-07-21, 12:22 PM, "Yingzhen Qu" wrote:
>>>>
>>>>>Hi Reshad,
>>>>>
>>>>>Thanks for the summary.
>>>>>
>>>>>Both ospf and isis model
;
>>>>Thanks for the summary.
>>>>
>>>>Both ospf and isis models will make corresponding changes when the new
>>>>BFD grouping is available.
>>>>
>>>>Thanks,
>>>>Yingzhen
>>>>
>>>>-Origi
t;Thanks,
>>>Yingzhen
>>>
>>>-----Original Message-----
>>>From: Reshad Rahman (rrahman) [mailto:rrah...@cisco.com]
>>>Sent: Thursday, July 20, 2017 7:19 AM
>>>To: Jeffrey Haas ; rtg-bfd@ietf.org
>>>Cc: draft-ietf-bfd-y...@ietf.org; draft
isco.com]
>>Sent: Thursday, July 20, 2017 7:19 AM
>>To: Jeffrey Haas ; rtg-bfd@ietf.org
>>Cc: draft-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
>>Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
>>
>>We (BFD and OSPF YANG authors) had a discussion y
-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
Hi Yingzhen,
The grouping is available @
https://github.com/jhaas-pfrc/ietf-bfd-yang/blob/master/src/yang/ietf-bfd-c
lients.yang
If you¹d like changes to the grouping, send me an email.
Re
;To: Jeffrey Haas ; rtg-bfd@ietf.org
>Cc: draft-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
>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
; rtg-bfd@ietf.org
Cc: draft-ietf-bfd-y...@ietf.org; draft-ietf-ospf-y...@ietf.org
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 to add back
the basic BFD config
We (BFD and OSPF YANG authors) had a discussion yesterday.
The agreement is that since IGP peers are auto-discovered, we want to add
back the basic BFD config (multiplier + intervals) in IGP via a grouping.
BFD will provide that grouping in a specific YANG module. IGP BFD YANG
will be in a separat
Thanks authors for the edits on the BFD yang module. This gets us a
significant step closer to alignment with the rest of IETF for network
instancing.
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 stil
44 matches
Mail list logo
