Eric Rescorla's No Objection on draft-ietf-bfd-yang-16: (with COMMENT)

Eric Rescorla <> Wed, 04 July 2018 22:33 UTC

Return-Path: <>
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id 1790A131067; Wed, 4 Jul 2018 15:33:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <>
To: The IESG <>
Cc:,,,, Jeffrey Haas <>
Subject: Eric Rescorla's No Objection on draft-ietf-bfd-yang-16: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.81.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Wed, 04 Jul 2018 15:33:17 -0700
Archived-At: <>
X-Mailman-Version: 2.1.26
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Jul 2018 22:33:17 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-bfd-yang-16: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Rich version of this review at:

S 2.1.4.
>              Minimum TTL of incoming BFD control packets.
>   2.1.4.  MPLS Traffic Engineering Tunnels
>      For MPLS-TE tunnels, BFD is configured under the MPLS-TE tunnel since
>      the desired failure detection parameters is a property of the MPLS-TE

"parameters are"

S 2.8.
>   2.8.  BFD over LAG hierarchy
>      A "lag" node is added under the "bfd" node in control-plane-protocol.
>      The configuration and operational state data for each BFD LAG session
>      is under this "lag" node.

There seems to be a lot of replication (e.g., number of sessions). Is
it possible to somehow refactor this so that's common?