IETF Logo Mail Archive

Correcting BFD Echo model

Greg Mirsky <gregimirsky@gmail.com> Sat, 25 February 2017 23:48 UTC

Return-Path: <gregimirsky@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 3BED312A3F1; Sat, 25 Feb 2017 15:48:38 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 Cyxsxx-2TqXv; Sat, 25 Feb 2017 15:48:37 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (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 30D80129549; Sat, 25 Feb 2017 15:48:37 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id k4so33935866otc.0; Sat, 25 Feb 2017 15:48:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/Js/7/C3+uz4aFV/5EKnB4t0WwrVN6JyKXpmRShi+ps=; b=mxtv1UKxmIUDXfD9gAMUKaSsz6fzdYDQ+CmoRSUUbYXyDe3EvkoMCjDwoMHlizoCaT B+aYlDna7GYO6sONkD+mCPOBEPEd7dqiWFrTWbKuuNdgT/RsZQ6ChyQrIELRGYznNtWl 1Ko0sOiQurFbKZDuc/fQh+S4qdVUw07hC0ybe0PrIWQZwDregQlGkRQqbg6gR/oZ3v3e cFljNV5GeD2k79kS3ptOvYXHHio8z7TA6R5nctrQx0A7XvTWM/zLKGrmQeaPbPTxhoc7 iCRnOwIdJY09xvwMZPe5fK/wCdIwM82qCHW3Ld9RIOeGJDinSqZOdQ7Oi/Yt1pQNNrEp p9aA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/Js/7/C3+uz4aFV/5EKnB4t0WwrVN6JyKXpmRShi+ps=; b=mZPr2EneyongxqeYJIPdPpJXgP8KI/Tk/EUcEC9u1Ekawn3fqi6qtWpvbNnrxwfwuQ kd8nnUxqWyQcNAI+RxRBRv6Z941hUL2JrBNrX2ambOn6Xk066hxOa754WOZi2pumUmLg da5QqRWwhgJIwV1DtEtqy3FA4xgqk0GirFlSgSekywJOtZCYboCbPv3fInVqtSft644I T+aNiF52YkkvpqgGFfbut4s+DnyFy09Z4fhCDWQtK9MkZTA8beAL01g0ZnrdOBv/WUcL ApdxQL2GGny2cJOmsMMsekXmdGlsmaFK1JlJ2+9MilxD3zg8AMHDf8giCMvqoOUv2Bdc 32EQ==
X-Gm-Message-State: AMke39mlT0bxD/dJc6jQg9rlTLjLNeiCsv3blHVvarL8IqJssqHrkA/0/7/fQbRRtYeUX+gzI0EYvW2jz/9kBg==
X-Received: by 10.157.56.137 with SMTP id p9mr3822654otc.68.1488066516391; Sat, 25 Feb 2017 15:48:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.21.21 with HTTP; Sat, 25 Feb 2017 15:48:36 -0800 (PST)
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sat, 25 Feb 2017 15:48:36 -0800
Message-ID: <CA+RyBmWcU79iCBYM_bi__Ce1RpWwNn_jZCkPHv3Sc+qtybt_pg@mail.gmail.com>
Subject: Correcting BFD Echo model
To: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, draft-ietf-bfd-yang@ietf.org
Content-Type: multipart/alternative; boundary="001a11c10e5e1ca1210549637c1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/z8XOrGMBM9quIYDCxziIj7wScGI>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 25 Feb 2017 23:48:38 -0000

Dear All,
I've reviewed the BFD YANG model and now I'm thinking that
desired-min-echo-tx-interval
and attributing to it the behavior, i.e. when the value is 0, of Required
Min Echo RX Interval are not in the right place. I think that definition of
desired transmit interval of BFD Echo should be in corresponding RPC
definition, not in configuration part of the model.
Appreciate your comments.

Regards,
Greg

v2.23.0 | Report a Bug | By Email