IETF Logo Mail Archive

Re: Correcting BFD Echo model

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Sun, 26 February 2017 22:52 UTC

Return-Path: <rrahman@cisco.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 6ED691294AA; Sun, 26 Feb 2017 14:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 sOsS14Jy3nmQ; Sun, 26 Feb 2017 14:52:57 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2503412941E; Sun, 26 Feb 2017 14:52:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5021; q=dns/txt; s=iport; t=1488149577; x=1489359177; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=zBJI35oQ1RjjWy0RVUNtBNFSNIGxYqPY45YlF1r/jmM=; b=VWZaz6SGXaR6TuQNJT0wFXhD0qT5+ADPKtlE+xH+Ogywenw5ZG7nxVFp TxmtePP37T83zlK3k7Ok12Ex4WD/TXd9hLuMnvmAhsCD9dzCAB1qB7Z/I Dk9FOxW8qetVklbFXSRuLDps8JtqkS+IvI6AFNNsltQ5wKtS1nvyMiv4f o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ASAQD8WrNY/5FdJa1dGQEBAQEBAQEBAQEBBwEBAQEBgm5igWoHjVyRXogMh32FLIINhiICghA/GAECAQEBAQEBAWIohHABAQEEgQkCAQgRAwECKAchERQJCAIEARKJXAMVsXaHKQ2EAAEBAQEBAQEDAQEBAQEBAQEghkyEb4JRgiOFRQWVbYV3OgGOBYQhgXuFIIl9ikqIZgEfOIEBVBWHC3WJSYENAQEB
X-IronPort-AV: E=Sophos;i="5.35,211,1484006400"; d="scan'208,217";a="390804564"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Feb 2017 22:52:56 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v1QMqu1L026091 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 26 Feb 2017 22:52:56 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 26 Feb 2017 16:52:55 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1210.000; Sun, 26 Feb 2017 16:52:55 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-yang@ietf.org" <draft-ietf-bfd-yang@ietf.org>
Subject: Re: Correcting BFD Echo model
Thread-Topic: Correcting BFD Echo model
Thread-Index: AQHSj8Gxk5FkqTOyS0attHx6x8g/UaF791cA
Date: Sun, 26 Feb 2017 22:52:55 +0000
Message-ID: <D4D8BE31.25AE5C%rrahman@cisco.com>
References: <CA+RyBmWcU79iCBYM_bi__Ce1RpWwNn_jZCkPHv3Sc+qtybt_pg@mail.gmail.com>
In-Reply-To: <CA+RyBmWcU79iCBYM_bi__Ce1RpWwNn_jZCkPHv3Sc+qtybt_pg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.8.160830
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.241.101]
Content-Type: multipart/alternative; boundary="_000_D4D8BE3125AE5Crrahmanciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/q9LcVO2WbJwEMmng1d_GEg9R_ik>
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: Sun, 26 Feb 2017 22:52:58 -0000

Hi Greg,

Can you please explain why you believe this should go in RPC?

Regards,
Reshad.

From: Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>
Date: Saturday, February 25, 2017 at 6:48 PM
To: "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>, "draft-ietf-bfd-yang@ietf.org<mailto:draft-ietf-bfd-yang@ietf.org>" <draft-ietf-bfd-yang@ietf.org<mailto:draft-ietf-bfd-yang@ietf.org>>
Subject: Correcting BFD Echo model
Resent-From: <alias-bounces@ietf.org<mailto:alias-bounces@ietf.org>>
Resent-To: <vero.zheng@huawei.com<mailto:vero.zheng@huawei.com>>, Reshad <rrahman@cisco.com<mailto:rrahman@cisco.com>>, <mjethanandani@gmail.com<mailto:mjethanandani@gmail.com>>, <santosh.pallagatti@gmail.com<mailto:santosh.pallagatti@gmail.com>>, <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>
Resent-Date: Saturday, February 25, 2017 at 6:48 PM

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