Re: [netmod] Ben Campbell's No Objection on draft-ietf-netmod-yang-model-classification-07: (with COMMENT)

Benoit Claise <bclaise@cisco.com> Wed, 07 June 2017 12:50 UTC

Return-Path: <bclaise@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D6612EC16; Wed, 7 Jun 2017 05:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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, 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 VGS5aBfbLa1m; Wed, 7 Jun 2017 05:50:48 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AE2D129459; Wed, 7 Jun 2017 05:50:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7144; q=dns/txt; s=iport; t=1496839847; x=1498049447; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=mwMfbO3ennvVWhNOKacJHyQ4DJW237UU1MBeNSnAGuc=; b=GzHdEZ62W5QS0H/hZBXVm01JvRv1H/n3sDYFJc0I+YaKpUG+cxjmq+RZ fUVJZz+FiklCb44OhNA7VbuTzs4sUSgvaOJYxpf4F34LJYxrGZ/jXnAjP XQM6rMRHXwAsCdxCHwAkY/8Xq/fXrlXHygJVB1IxzJBo+ErZNOgnIdp2H Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ATAQBk9TdZ/xbLJq1eGgEBAQECAQEBAQgBAQEBhDqBDYNzihhzkHWQR4U5ghAuhXYCgy4YAQIBAQEBAQEBayiFGQEEASNWEAtCAgJXBgEMCAEBih8IEK5SgiYri1IBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYZhgguCdYQ7EgGDLoJhBYlNlGyHJowSggaFPoNLhnGMKog9Hzh/CzAhCBsVhgKBTj42AYchgjABAQE
X-IronPort-AV: E=Sophos;i="5.39,311,1493683200"; d="scan'208,217";a="694974931"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2017 12:50:42 +0000
Received: from [10.55.221.37] (ams-bclaise-nitro4.cisco.com [10.55.221.37]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v57CofvF025089; Wed, 7 Jun 2017 12:50:42 GMT
To: Ben Campbell <ben@nostrum.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-netmod-yang-model-classification@ietf.org, Lou Berger <lberger@labn.net>, netmod-chairs@ietf.org, netmod@ietf.org
References: <149671949959.3984.3647471702123309969.idtracker@ietfa.amsl.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <5ff62d49-9b3b-9fe2-9f34-bf4660009302@cisco.com>
Date: Wed, 07 Jun 2017 14:50:39 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149671949959.3984.3647471702123309969.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------8A3242BB47E0419367AF2503"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/_3nd3vR_wgAXa8-8WmalHsUTRtw>
Subject: Re: [netmod] Ben Campbell's No Objection on draft-ietf-netmod-yang-model-classification-07: (with COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2017 12:50:50 -0000

Hi Ben,

Thanks for your review. See in-line.
> Ben Campbell has entered the following ballot position for
> draft-ietf-netmod-yang-model-classification-07: 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 https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-model-classification/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Substantive:
>
> -4: That seems almost a challenge :-) But seriously, I dont know if it makes
> sense to discuss this sort of thing in this document-- but it seems like
> sensitivity of content might be a consideration when "typing" models. For
> example, models that include security credentials or keys. (An answer of
> "that's not what we are talking about" would be perfectly sensible.)
Actually, the security considerations related to the YANG module should 
not influence the YANG module classification.
I wrote "should" because I can't think of a single case.
To complete the Security Considerations section, here is a proposal.
OLD:

    This document doesn't have any Security Considerations.

NEW:
    The document specifying the YANG module to-be-classified already contains a Security Considerations
    section. This document doesn't add to or modify this Security Considerations section.

>
> Editorial:
>
> -1, " A number of module types have created substantial discussion during   the
> development of this document including those concerned with   topologies."
>
> I'm not sure I understand that sentence. Is the antecedent of "those" "module
> types", or "discussions"? Are we talking about network topologies?
OLD:

    A number of module types have created substantial discussion during
    the development of this document including those concerned with
    topologies.

NEW:
    A number of module types have created substantial discussion during
    the development of this document: for example, those concerned with
    topologies.

>
> The section ends with "See figure 1". But that figure seems more related to
> section 2. Is the reference out of place?
The reference is right. Positioning the YANG modules from a location 
point of view (equipment vendor, controller, orchestrator) helps people 
grasp the concepts of Network Element YANG Modules versus Network 
Service YANG Modules

Regards, Benoit
>
>
> .
>