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

Jeffrey Haas <jhaas@pfrc.org> Mon, 31 July 2017 20:55 UTC

Return-Path: <jhaas@pfrc.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B5A1327C1; Mon, 31 Jul 2017 13:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 TB13y_enL3vi; Mon, 31 Jul 2017 13:55:49 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id EC3AE1327C0; Mon, 31 Jul 2017 13:55:47 -0700 (PDT)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 1E66F1E37F; Mon, 31 Jul 2017 16:56:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <BAF4C9E6-ED02-4E25-89DD-2FA181AF3B72@gmail.com>
Date: Mon, 31 Jul 2017 16:55:46 -0400
Cc: Yingzhen Qu <yingzhen.qu@huawei.com>, "Acee Lindem (acee)" <acee@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-yang@ietf.org" <draft-ietf-bfd-yang@ietf.org>, "draft-ietf-ospf-yang@ietf.org" <draft-ietf-ospf-yang@ietf.org>, Reshad Rahman <rrahman@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3637B198-8F82-4A85-A4A1-4383AF98088D@pfrc.org>
References: <D59FB38C.2CE83D%rrahman@cisco.com> <D59FB594.BA3A0%acee@cisco.com> <D59FB7D2.2CE8F1%rrahman@cisco.com> <D59FB934.BA3C3%acee@cisco.com> <D59FBE2A.2CEA06%rrahman@cisco.com> <D5A01A7B.BA49E%acee@cisco.com> <C71CC69E-DAE4-49E0-983A-9B2EE9B4CD46@gmail.com> <D5A12762.2D4DB5%rrahman@cisco.com> <E4E310A2-A79C-403E-B68E-A39B76E2C5E0@gmail.com> <773E4FFC-D66A-49E5-A03A-58B7DBA82D90@gmail.com> <20170731170550.GO24942@pfrc.org> <BAF4C9E6-ED02-4E25-89DD-2FA181AF3B72@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/H0gbjcAsJt1fBKmNCHGk9oxlkRM>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 31 Jul 2017 20:55:51 -0000

Mahesh,

> On Jul 31, 2017, at 4:26 PM, Mahesh Jethanandani <mjethanandani@gmail.com>; wrote:
> 
> Jeff,
> 
>> On Jul 31, 2017, at 10:05 AM, Jeffrey Haas <jhaas@pfrc.org>; 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
>> protocol client configuration impacts or is it chosen by the system
>> automatically?
> 
> I am not sure I understand. 
> 
> For Echo mode, there is a separate grouping called echo-cfg-parms that allows clients to specify the desired-min-echo-tx-interval and required-min-echo-rx-interval. 
> 
> That is somehow different from desired-min-tx-interval and required-min-rx-interval that one can specify for a normal BFD session. For the life of me, I do not understand why the two need to be different :-(. I must be getting amnesia. Maybe one of the co-authors will jog my memory.

The protocol permits those values to be distinct from the async ones.  They should be in a separate set of params.

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.

My implementation doesn't support echo, so I don't have any opinion about where configuration of those belongs or not.

-- Jeff



> 
> Cheers.
> 
>> 
>> -- jeff
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com
> 
>