IETF Logo Mail Archive

Re: [OSPF] IETF OSPF YANG and BFD Configuration

Mahesh Jethanandani <mjethanandani@gmail.com> Thu, 18 May 2017 21:39 UTC

Return-Path: <mjethanandani@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0D7129C67; Thu, 18 May 2017 14:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, 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 UJD9PbNm07fr; Thu, 18 May 2017 14:39:07 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 1F5AF129B42; Thu, 18 May 2017 14:33:05 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id h4so71044700oib.3; Thu, 18 May 2017 14:33:05 -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:message-id:references :to; bh=qLzXKiTFvv9FQ/laPK2vRBfEZ47HfmF7Hp/iDno0oxA=; b=OzgyNplcM/zuxjsg66CinTkDc2/wiwO0SiM7gYj//GBdRwF6Fp6ha3UN/egIE7Oyz/ ly4p2kV5W1b6sAicPhzHb8WgYgNhvLDjbcje05e/99gKewR2s0jyHHclWn6Hil1CBwIz GIDdd9eAAIiXwm4G5yB/GGRDuh7FRJFTd9EbVrvlWgEURExammudae3kGYcdU8ucmYPN IfxfldS3r2Eg24+UoYxWNEJm5zPlTZHk08sOpo+ab1JH5YJHrd/4+MIuZgGhsfgaJ5N6 BP8vdLjscg4Ksk1I+u3BdAoWJZpByYC2iyx2G/gaZRq7t6ofe9JmLNEs+Ox7vL0hNEDM FOHQ==
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 :message-id:references:to; bh=qLzXKiTFvv9FQ/laPK2vRBfEZ47HfmF7Hp/iDno0oxA=; b=UjGlnIf7ArDhz1Q4tIB/UiBkIDSiBp275wNMbkgDS+J1fGUokDsyyF+Kk/fOdnhf0O v9CEcsnN1cDwu9uLRri1Bjo0swF+qkIkA8ek5NJQNl9dO9eOAABqqg6F3TArJPJNlCn3 khHeuoIxx6QrEGqTy3WjLYY5RuIbJ8/bkBCnlSOx+wd3blB1y4EIbkWZWYVVpqpYfV5+ IQ3xCFYmJq0Ckme8+vaJluTCrCtilh6m+oS0taEg4RLDU54ZZWQMRWJKjFt96DDuTUtC BXBGTskHW1zpuuwKy8nsDLrMTCUoaUlWrd2LeDGShcHap/H3JkBnPAS5W7URH3872Bl1 7snw==
X-Gm-Message-State: AODbwcDimFxYX5BWtb7h9R3h8isro4NZMtu2ZyO1+sBk/29eRjMv5zEw VAl0Mz09cBqFdQ==
X-Received: by 10.157.80.163 with SMTP id b35mr4078360oth.151.1495143184450; Thu, 18 May 2017 14:33:04 -0700 (PDT)
Received: from ?IPv6:2001:420:30d:1320:9cd1:5396:73dc:f0b0? ([2001:420:30d:1320:9cd1:5396:73dc:f0b0]) by smtp.gmail.com with ESMTPSA id g29sm3235397ote.2.2017.05.18.14.33.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 18 May 2017 14:33:03 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9BFB785C-BD46-40A9-871E-DCC239993987"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <D5436DE8.AF5B7%acee@cisco.com>
Date: Thu, 18 May 2017 14:33:07 -0700
Cc: Jeffrey Haas <jhaas@juniper.net>, OSPF WG List <ospf@ietf.org>, "bfd@ietf.org" <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>
Message-Id: <38DEB571-2918-4464-B18A-71B24221772F@gmail.com>
References: <D5436DE8.AF5B7%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/taJstuWmIXzyGlvMIJWmoom_rSU>
Subject: Re: [OSPF] IETF OSPF YANG and BFD Configuration
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, 18 May 2017 21:39:10 -0000

Agree with Acee’s assessment. After much debate, we decided that we should leave BFD parameter configuration in the BFD model itself, and have any IGP protocol reference the BFD instance in BFD itself. This makes sense specially if multiple protocols fate-share the BFD session.

Cheers.

> On May 18, 2017, at 12:27 PM, Acee Lindem (acee) <acee@cisco.com> wrote:
> 
> Hi Jeff, 
> 
> At the OSPF WG Meeting in Chicago, you suggested that we may want to provide configuration of BFD parameters within the OSPF model (ietf-ospf.yang). We originally did have this configuration. However, after much discussion and coordination with the BFD YANG design team, we agreed to leave the BFD session parameters in BFD and only enable BFD within the OSPF and IS-IS models. 
> 
> We did discuss the fact that vendors (notably Cisco IOS-XR and Juniper JUNOS) do allow configuration within the IGPs. However, the consensus was to leave the BFD configuration in the BFD model. The heuristics to determine what parameters to use when the same BFD endpoint was configured with different parameters in different protocols were proprietary and somewhat of a hack. 
> 
> I may have not remembered all the details so I’d encourage others to chime in. 
> 
> Thanks,
> Acee 

Mahesh Jethanandani
mjethanandani@gmail.com

v2.23.0 | Report a Bug | By Email