Re: Last Call: <draft-ietf-bfd-yang-13.txt> (YANG Data Model for Bidirectional Forwarding Detection (BFD)) to Proposed Standard

"Reshad Rahman (rrahman)" <> Sat, 26 May 2018 15:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 482B712DA09; Sat, 26 May 2018 08:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OFyNqqQFxbhN; Sat, 26 May 2018 08:10:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0AB4812DA05; Sat, 26 May 2018 08:10:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=4438; q=dns/txt; s=iport; t=1527347444; x=1528557044; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=jlA1rhz+ZsQEV7a+r4q/QaI+4KvWIjTQDVQZCqjJ2ko=; b=eVfWiudPzc4O3xcS7+J77ruh59QddweTU3tG07TOBoQLik4f+h2/6u9u SUbQjn7Vi3Bix9fFhGO53QYxoV9WO4JvAT5NjUZM/SLbL8lftNuwn2+4c TIc7zYO3NXvZuUWLd58HXa58G2Czu3YIVwEN0JWgSby/lrWnc+ivUq2mn I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.49,444,1520899200"; d="scan'208";a="399337926"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2018 15:10:43 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id w4QFAgNU025029 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 26 May 2018 15:10:43 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 26 May 2018 10:10:42 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Sat, 26 May 2018 10:10:42 -0500
From: "Reshad Rahman (rrahman)" <>
To: "tom p." <>, "" <>
CC: "" <>, "" <>, "" <>
Subject: Re: Last Call: <draft-ietf-bfd-yang-13.txt> (YANG Data Model for Bidirectional Forwarding Detection (BFD)) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-bfd-yang-13.txt> (YANG Data Model for Bidirectional Forwarding Detection (BFD)) to Proposed Standard
Thread-Index: AQHT9Cv61vh7ba7JDkyK/ePx55YBV6RB4eESgABN9oA=
Date: Sat, 26 May 2018 15:10:42 +0000
Message-ID: <>
References: <> <008e01d3f4e4$dba327a0$>
In-Reply-To: <008e01d3f4e4$dba327a0$>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 26 May 2018 15:10:46 -0000

Hi Tom,

Thanks for the review. I will add the missing reference statements, I believe this was just an oversight because there are/were no RFC numbers for these imported modules (there is now for ietf-routing).  So I will add the usual RFC XXX with a note for the RFC Editor.


On 2018-05-26, 7:31 AM, "tom p." <> wrote:

    This I-D has a number of import statements from other YANG modules for
    which there is no Reference statement where I believe that there should
    be, statements such as .
      import iana-bfd-types
      import ietf-bfd
      import ietf-bfd-mpls
      import ietf-te
      import ietf-routing
    In the first three cases, it may be that the editors of this I-D
    consider that such a reference is not needed because the relevant
    modules are in the same I-D but such thinking is erroneous.  These are
    separate modules which will lead independent existences in the wild so
    that there will be nothing to tell a user of e.g.  module
    where to look for
    ietf-bfd-types, ietf-bfd,  ietf-bfd-mpls
    These need  reference statement such as
      reference "RFC XXXX:   YANG Data Model for BFD";
    Tom Petch
    ----- Original Message -----
    From: "The IESG" <>
    To: "IETF-Announce" <>
    Cc: <>; <>;
    Sent: Friday, May 25, 2018 2:26 PM
    > The IESG has received a request from the Bidirectional Forwarding
    > WG (bfd) to consider the following document: - 'YANG Data Model for
    > Bidirectional Forwarding Detection (BFD)'
    >   <draft-ietf-bfd-yang-13.txt> as Proposed Standard
    > The IESG plans to make a decision in the next few weeks, and solicits
    > comments on this action. Please send substantive comments to the
    > mailing lists by 2018-06-08. Exceptionally, comments may
    > sent to instead. In either case, please retain the
    beginning of
    > the Subject line to allow automated sorting.
    > Abstract
    >    This document defines a YANG data model that can be used to
    >    and manage Bidirectional Forwarding Detection (BFD).
    >    The YANG modules in this document conform to the Network Management
    >    Datastore Architecture (NMDA).
    > The file can be obtained via
    > IESG discussion can be tracked via
    > No IPR declarations have been submitted directly on this I-D.
    > The document contains these normative downward references.
    > See RFC 3967 for additional information:
    >     draft-ietf-teas-yang-te: A YANG Data Model for Traffic Engineering
    Tunnels and Interfaces (None - IETF stream)
    >     draft-ietf-mpls-base-yang: A YANG Data Model for MPLS Base (None -
    IETF stream)