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

"Reshad Rahman (rrahman)" <rrahman@cisco.com> Sat, 26 May 2018 15:10 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 482B712DA09; Sat, 26 May 2018 08:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
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: 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 OFyNqqQFxbhN; Sat, 26 May 2018 08:10:44 -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 0AB4812DA05; Sat, 26 May 2018 08:10:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; 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-Anti-Spam-Result: A0DNAAAheAlb/5xdJa1bGQEBAQEBAQEBAQEBAQcBAQEBAYMVL2J9KAqDbYgEjG2BeYEPkzuBeAsjhEkCF4F4ITQYAQIBAQEBAQECbBwMhSgBAQEDASMROgsMBAIBCBIDAQQCHwcCAgIwFAECDgIEAQ0FgyICgXcID6YbghyIQYFjBYEJhy2BVD+BDySCaYMRAgMBgVwXgmkwgiQCmGIJAoVqiHKBO4Nvh1yJbIZ3AhETAYEkHTiBUnAVZQGCCAEPgkiISIU+b44sgRkBAQ
X-IronPort-AV: E=Sophos;i="5.49,444,1520899200"; d="scan'208";a="399337926"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2018 15:10:43 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-5.cisco.com (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 xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 26 May 2018 10:10:42 -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.1320.000; Sat, 26 May 2018 10:10:42 -0500
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "tom p." <daedulus@btconnect.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-ietf-bfd-yang@ietf.org" <draft-ietf-bfd-yang@ietf.org>, "bfd-chairs@ietf.org" <bfd-chairs@ietf.org>
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: <609C9D00-FF77-4D36-AAE3-9D0A7B074594@cisco.com>
References: <152725478007.13001.4823972789715702212.idtracker@ietfa.amsl.com> <008e01d3f4e4$dba327a0$4001a8c0@gateway.2wire.net>
In-Reply-To: <008e01d3f4e4$dba327a0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.248.1]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3DCBEF94B952AE40814EA639D7E17360@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Ns3XMGksZpXdAFhM8wh2-obG3CU>
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: 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.

Regards,
Reshad.


On 2018-05-26, 7:31 AM, "tom p." <daedulus@btconnect.com> 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
    ietf-bfd-mpls-te
    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" <iesg-secretary@ietf.org>
    To: "IETF-Announce" <ietf-announce@ietf.org>
    Cc: <rtg-bfd@ietf.org>; <draft-ietf-bfd-yang@ietf.org>;
    <bfd-chairs@ietf.org>
    Sent: Friday, May 25, 2018 2:26 PM
    
    > The IESG has received a request from the Bidirectional Forwarding
    Detection
    > 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
    final
    > comments on this action. Please send substantive comments to the
    > ietf@ietf.org mailing lists by 2018-06-08. Exceptionally, comments may
    be
    > sent to iesg@ietf.org 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
    configure
    >    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
    > https://datatracker.ietf.org/doc/draft-ietf-bfd-yang/
    >
    > IESG discussion can be tracked via
    > https://datatracker.ietf.org/doc/draft-ietf-bfd-yang/ballot/
    >
    >
    > 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)
    >
    >
    >