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

Jeffrey Haas <jhaas@pfrc.org> Mon, 14 August 2017 17:10 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 F2BA61323AA; Mon, 14 Aug 2017 10:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 0BHZkdotKKNS; Mon, 14 Aug 2017 10:10:45 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id CB8541323AF; Mon, 14 Aug 2017 10:10:45 -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 5893B1E3B3; Mon, 14 Aug 2017 13:11:20 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
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: <D5B73133.2D861A%rrahman@cisco.com>
Date: Mon, 14 Aug 2017 13:10:43 -0400
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, 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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEFA04B6-55B8-42C4-ABC6-F50F5F9C77AB@pfrc.org>
References: <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> <3637B198-8F82-4A85-A4A1-4383AF98088D@pfrc.org> <D26CB257-E4B2-42FA-940E-BF77C8BC1751@gmail.com> <20170801144129.GC24942@pfrc.org> <F319C69C-3A4E-4C5C-ADA4-37BDFD97E91A@gmail.com> <20170801163340.GD24942@pfrc.org> <D5B73133.2D861A%rrahman@cisco.com>
To: Reshad Rahman <rrahman@cisco.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/dxMwtXWYT_evTTVZL5Me3cYACo0>
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, 14 Aug 2017 17:10:47 -0000

> On Aug 14, 2017, at 11:24 AM, Reshad Rahman (rrahman) <rrahman@cisco.com>; 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 echo are vendor specific. e.g.
> An implementation which has echo as continuous would likely have echo
> configuration whereas an implementation which has echo as on-demand may
> use RPC. There is an example of a vendor augmentation for echo config in
> Appendix A.1.

Right.  The point was what the echo configuration should look like.  Based on glancing at a couple of vendor configs that use echo, it's mostly "use echo" as a boolean behavior.  This is in contrast with permitting the user to specify distinct echo vs. async timer values.

I'm totally fine leaving the "on demand" case out of scope.

-- Jeff