[OSPF] FW: I-D Action: draft-ietf-bfd-yang-06.txt

"Acee Lindem (acee)" <acee@cisco.com> Thu, 20 July 2017 14:25 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 18EAF120725 for <ospf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id vv79G71AIXHo for <ospf@ietfa.amsl.com>; Thu, 20 Jul 2017 07:25:57 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A288D12704A for <ospf@ietf.org>; Thu, 20 Jul 2017 07:25:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4140; q=dns/txt; s=iport; t=1500560757; x=1501770357; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ociRV99fWYSXOQFc1gJ7nd27L1kxUw0PTlHW5sYN2BI=; b=Fcd68jJ9HFsQgH2HAtJh8LdnEfGdq8/rr5/sht7kIMPr1s7SYDVeJl57 SPHm+YSW0RTTBaFgJq9qTX0LP1Sop3ntw4UnL6sHNQGVRLVDSF6PyQ+ba QGhf0IAAWC4dHznAt0GeCt05jHrEoTzm5pDhvj1H9ok5DJHWSvUGtSGVC o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.40,384,1496102400"; d="scan'208";a="456806131"
Received: from rcdn-core-1.cisco.com ([]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Jul 2017 14:25:56 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com []) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v6KEPuWi011288 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Thu, 20 Jul 2017 14:25:56 GMT
Received: from xch-rtp-015.cisco.com ( by XCH-RTP-012.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 20 Jul 2017 10:25:55 -0400
Received: from xch-rtp-015.cisco.com ([]) by XCH-RTP-015.cisco.com ([]) with mapi id 15.00.1210.000; Thu, 20 Jul 2017 10:25:55 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: OSPF WG List <ospf@ietf.org>
Thread-Topic: I-D Action: draft-ietf-bfd-yang-06.txt
Thread-Index: AQHS8drqXiPB9yzw8Uyz6SEnSzAzYaJFxYCAgBeSvYD//4wugA==
Date: Thu, 20 Jul 2017 14:25:55 +0000
Message-ID: <D596352B.B9D5B%acee@cisco.com>
References: <149885255897.4584.3006333522740435620@ietfa.amsl.com> <20170705162103.GQ2289@pfrc.org> <D596866E.2C3552%rrahman@cisco.com>
In-Reply-To: <D596866E.2C3552%rrahman@cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <F4F26F1D9EF61247901617772A2639BF@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/cytHqDBkjFU7RxTctVbv9Euad60>
Subject: [OSPF] FW: I-D Action: draft-ietf-bfd-yang-06.txt
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 14:25:59 -0000

FYI - We will have a separate OSPF BFD YANG module that augments the OSPF
interfaces and uses the BFD provided grouping. This will be done as part
of the current draft.


On 7/20/17, 10:18 AM, "Reshad Rahman (rrahman)" <rrahman@cisco.com> wrote:

>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).
>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
>>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.
>>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
>>> 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
>>>    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
>>> 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/