IETF Logo Mail Archive

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

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 31 July 2017 20:26 UTC

Return-Path: <mjethanandani@gmail.com>
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 C3251129B43; Mon, 31 Jul 2017 13:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4Kzy6XmwBc9R; Mon, 31 Jul 2017 13:26:24 -0700 (PDT)
Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86AAF1318A2; Mon, 31 Jul 2017 13:26:24 -0700 (PDT)
Received: by mail-oi0-x241.google.com with SMTP id e124so24557667oig.0; Mon, 31 Jul 2017 13:26:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bw2jitfn4GNU4rrkCbqH5HF5GkNkMJGzOdECRvehTuk=; b=pu8ivDqWxz5IJknfLUANlLYvTyQl9mLjFyluP1lxf8KwDtGZDA34YaNr+zWEbsfK/l kL2rG7U01YgYsM+fidIUbZnxZJ9MkhKf0Kvw6l5yiALtr98AEPw0LAUAnM+nCVITtZId /PIdWTUYAGOR8n1VpGwdrgNiMqk2+1hGcyOU2HGBMIreaBzHyLZpZ5UbEYTDcQeeLSw9 Ozb8N9x7ToTg23WRGmaExPL2J/jdEtETj47rNiyLOluERKaGbt5BW/TZ3wNjx7t5q0PW RCMNrBOYVimyAZT2e4vYTxAOHI4KschWqUi64sgY/Q6dpoc4ak9dXW0wpM9dXk35q3Fs v9nA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bw2jitfn4GNU4rrkCbqH5HF5GkNkMJGzOdECRvehTuk=; b=LlfHELslw4yHo7WG2ypFdD+7VVFS1Yxqpj3+9GUQ+fhcgGnizh5VQ+jbLFeWbick/y JHZ9hB3llwUA1PGEjDGzeMOCDeLO5ONpx/hkVJoRIBa0/9GyFuNo8yhJUW28wQmLnxGQ 5eEDziBmjRGOaBrujef7v5HId9KADbbXPfGi76NkCfDA0UyA0t/naEdMNKLe3R7uiW/p ZL0rQSZ4qy2uPi9W4QRtKkxPDNWzN8LlxRa/9iPS5yiNVOpQZWJmQsQTXok/fWUQvwNu JP/Pd1tqPUhTtLLZH8H+nW/WvmimKnzq2qrDAXyQudiC6C+rTXjppVJWcAEZTJvZETKI h5CA==
X-Gm-Message-State: AIVw112QJJM1GIHhfHm2+WfwxB0Y1kG+mkvRBGja3FjkYGKp0U4R+gNm nSDO0J3NPo9dY1NNx14F6Q==
X-Received: by 10.202.184.8 with SMTP id i8mr10964724oif.266.1501532783964; Mon, 31 Jul 2017 13:26:23 -0700 (PDT)
Received: from ?IPv6:2001:420:30d:1320:a4d9:8b58:f92c:ca51? ([2001:420:30d:1320:a4d9:8b58:f92c:ca51]) by smtp.gmail.com with ESMTPSA id u77sm785183oie.0.2017.07.31.13.26.22 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 31 Jul 2017 13:26:23 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <20170731170550.GO24942@pfrc.org>
Date: Mon, 31 Jul 2017 13:26:48 -0700
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: <BAF4C9E6-ED02-4E25-89DD-2FA181AF3B72@gmail.com>
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>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/HQ4imggf0YExGBECE-HMEjtMK1Q>
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:26:26 -0000

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.

Cheers.

> 
> -- jeff

Mahesh Jethanandani
mjethanandani@gmail.com

v2.23.0 | Report a Bug | By Email