IETF Logo Mail Archive

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

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Thu, 20 July 2017 14:18 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 206071276AF; Thu, 20 Jul 2017 07:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 k2BeCIjJB7jO; Thu, 20 Jul 2017 07:18:38 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74F8112704A; Thu, 20 Jul 2017 07:18:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2696; q=dns/txt; s=iport; t=1500560318; x=1501769918; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vSoVVFxrlp8hvQfYOrw8gTmnnjXyliL9p80BY4EVlSE=; b=S5nGqP4fQ0OcT3JWpGo9DS4R1yeMgSn3SnT0ObWl/+LDNtkq02138I8T PgGwwvZNzzar38TuwfPW9hJxackQ0ZZlELHkV75TdaMBVHSPAHAc2ZJcC p22i59/CZK6Hw2Vm2fIh0gaWIDUTTGzYYE/xAqWpT0wKBZAl8JUSRoD4K 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CYAADdunBZ/4QNJK1cGQEBAQEBAQEBAQEBBwEBAQEBg1pkgRQHjgSRaJYFghEshRsCg3Q/GAECAQEBAQEBAWsohRkBBTo/EAIBCA4KHhAyJQIEAQ0Fii8QtBGLIgEBAQEBAQEBAQEBAQEBAQEBAQEBAR2DKINNhQWDJoc4BZ8+AodJjE+CDFeEeYpYlV0BHziBCnUVH4c/AXaIbIEOAQEB
X-IronPort-AV: E=Sophos;i="5.40,384,1496102400"; d="scan'208";a="270569976"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jul 2017 14:18:37 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v6KEIbKv011366 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 20 Jul 2017 14:18:37 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Jul 2017 09:18:36 -0500
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; Thu, 20 Jul 2017 09:18:36 -0500
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
CC: "draft-ietf-bfd-yang@ietf.org" <draft-ietf-bfd-yang@ietf.org>, "draft-ietf-ospf-yang@ietf.org" <draft-ietf-ospf-yang@ietf.org>
Subject: Re: I-D Action: draft-ietf-bfd-yang-06.txt
Thread-Topic: I-D Action: draft-ietf-bfd-yang-06.txt
Thread-Index: AQHS8drqXiPB9yzw8Uyz6SEnSzAzYaJFxYCAgBeSvYA=
Date: Thu, 20 Jul 2017 14:18:36 +0000
Message-ID: <D596866E.2C3552%rrahman@cisco.com>
References: <149885255897.4584.3006333522740435620@ietfa.amsl.com> <20170705162103.GQ2289@pfrc.org>
In-Reply-To: <20170705162103.GQ2289@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.81.238]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7428FA4CECDCDE4D9E046C68410AFD9E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/x_18lVKaFhW-YO-FrnlImYQ49aI>
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: Thu, 20 Jul 2017 14:18:40 -0000

We (BFD and OSPF YANG authors) had a discussion yesterday.

The agreement is that since IGP peers are auto-discovered, we want to add
back the basic BFD config (multiplier + intervals) in IGP via a grouping.
BFD will provide that grouping in a specific YANG module. IGP BFD YANG
will be in a separate module (separate from the main IGP module).


Regards,
Reshad.

On 2017-07-05, 12:21 PM, "Rtg-bfd on behalf of Jeffrey Haas"
<rtg-bfd-bounces@ietf.org on behalf of jhaas@pfrc.org> wrote:

>Thanks authors for the edits on the BFD yang module.  This gets us a
>significant step closer to alignment with the rest of IETF for network
>instancing.
>
>I'd like to encourage the working group to provide feedback on this issue
>and also the changes in the module.
>
>As noted in another thread, we still have to figure out how to deal with
>accommodating interaction of the BFD yang module with client protocols.
>For
>example, the IGPs.  In particular, how do you configure the properties of
>the BFD sessions that may be dynamically instantiated based on control
>protocol activity?
>
>-- Jeff
>
>On Fri, Jun 30, 2017 at 12:55:59PM -0700, internet-drafts@ietf.org wrote:
>> 
>> A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>> This draft is a work item of the Bidirectional Forwarding Detection of
>>the IETF.
>> 
>>         Title           : YANG Data Model for Bidirectional Forwarding
>>Detection (BFD)
>>         Authors         : Reshad Rahman
>>                           Lianshu Zheng
>>                           Mahesh Jethanandani
>>                           Santosh Pallagatti
>>                           Greg Mirsky
>> 	Filename        : draft-ietf-bfd-yang-06.txt
>> 	Pages           : 59
>> 	Date            : 2017-06-30
>> 
>> Abstract:
>>    This document defines a YANG data model that can be used to configure
>>    and manage Bidirectional Forwarding Detection (BFD).
>> 
>> 
>> 
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-bfd-yang/
>> 
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-ietf-bfd-yang-06
>> https://datatracker.ietf.org/doc/html/draft-ietf-bfd-yang-06
>> 
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-yang-06
>> 
>> 
>> Please note that it may take a couple of minutes from the time of
>>submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>

v2.23.0 | Report a Bug | By Email