[netmod] WG LC comment on draft-ietf-netconf-nmda-netconf-02

Robert Wilton <rwilton@cisco.com> Fri, 26 January 2018 12:01 UTC

Return-Path: <rwilton@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 A334712DA1D; Fri, 26 Jan 2018 04:01:08 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 Ds32VTjaSd1A; Fri, 26 Jan 2018 04:01:06 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBDA912D946; Fri, 26 Jan 2018 04:01:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9186; q=dns/txt; s=iport; t=1516968066; x=1518177666; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=mawhOgM+SU/94s7CC/0S84Cs8HIAuGcTUvNaP0EbnE4=; b=ZWK0L+PKEUqDv2kbTC2Hh9Ge5Wj1Rspxc3vJ8j9aO6rvl6jHG6fG8Y4L RPiZpFnI4+juI55ufIyI6FS2se3TrixNO+UNftRMC0/hP/8nj3GIdl9Rr Q1nLX85XPdPS67bM+EEBPx3dHR1YbaayXI9Xg9WeX7IfOeEzLA+y+A6Rv E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CMAQDiF2ta/xbLJq1cGQEBAQEBAQEBAQEBAQcBAQEBAYJKgV50J4NdixiPeJFwh2sKGAEKhElPAoJ1FAEBAQEBAQEBAmsohSQBAQQBASFLCxAJEAoqAgInMAYBDAYCAQGKMRCTYZ1xgicmijEBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYRSg2yBaCmGNAEBAgGBWIMtgmUFpBOIF41PghuGIINxh3yKf4JhgWyIE4E8NiIlgSszGggbFT2CKoRYQTcBAY4DAQEB
X-IronPort-AV: E=Sophos;i="5.46,416,1511827200"; d="scan'208,217";a="1611657"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jan 2018 12:01:03 +0000
Received: from [10.63.23.78] (dhcp-ensft1-uk-vla370-10-63-23-78.cisco.com [10.63.23.78]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0QC131c022777; Fri, 26 Jan 2018 12:01:03 GMT
To: Mahesh Jethanandani <mjethanandani@gmail.com>, netconf <netconf@ietf.org>
Cc: NETMOD Working Group <netmod@ietf.org>
References: <CF60B198-564B-499A-9B17-E992569074CB@gmail.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <b33594be-d4e8-d75a-aace-0d0b66ad5ee3@cisco.com>
Date: Fri, 26 Jan 2018 12:01:03 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CF60B198-564B-499A-9B17-E992569074CB@gmail.com>
Content-Type: multipart/alternative; boundary="------------4BF34C2E5CC90A2DD2A11A13"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/GZ2hMorb-5q4ErQTd101FzWj3-U>
Subject: [netmod] WG LC comment on draft-ietf-netconf-nmda-netconf-02
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: Fri, 26 Jan 2018 12:01:08 -0000

Hi,

One minor point that came up after the WG LC drafts had been posted is 
that draft-ietf-netconf-nmda-netconf-02 explicitly references the path 
"/yang-library/checksum", which means that the draft has a hard 
dependency on this leaf always existing at this path in YANG library.

e.g. section 2 of draft-ietf-netconf-nmda-netconf-02 contains:

    The parameter "checksum" has the same value as the leaf
    "/yang-library/checksum" from "ietf-yang-library".  This parameter
    MUST be present.

I think that it would be more flexible if the draft only referred to a 
"YANG library checksum", and then have Yang Library bis formally define 
the "YANG library checksum" term.  This is to avoid the need to formally 
update NMDA NETCONF draft, if the checksum path ever needs to be updated 
in a future revision of YANG library.


To give an example of where we hit a similar issue, was in RFC 7950, 
section 5.6.4, that has to be updated by 
draft-ietf-netconf-nmda-netconf-02 because it explicitly references the 
"/modules-state/module" list.   Generally, I think that it would be good 
to try and avoid these tight dependencies where possible, and try to 
have them more loosely coupled.

E.g., text from 7950:


        5.6.4 <https://tools.ietf.org/html/rfc7950#section-5.6.4>.
        Announcing Conformance Information in NETCONF



    This document defines the following mechanism for announcing
    conformance information.  Other mechanisms may be defined by future
    specifications.

    A NETCONF server MUST announce the modules it implements (see
    Section 5.6.5 <https://tools.ietf.org/html/rfc7950#section-5.6.5>) by implementing the YANG module "ietf-yang-library"
    defined in [RFC7895 <https://tools.ietf.org/html/rfc7895>] and listing all implemented modules in the
    "/modules-state/module" list.


Requiring this text in draft-ietf-netconf-nmda-netconf-02:

    This document updates [RFC7950], Section 5.6.4, to allow servers to
    advertise the capability :yang-library:1.1 instead of :yang-
    library:1.0, and to implement the subtree "/yang-library"
    [I-D.ietf-netconf-rfc7895bis] instead of "/modules-state".

Thanks,
Rob



On 17/01/2018 18:39, Mahesh Jethanandani wrote:
> The authors of draft-ietf-netconf-nmda-netconf and draft-ietf-netconf-nmda-restconf have posted updates to their drafts, and believe that the documents are ready for LC.
>
> This starts a 2 week LC on the two drafts that will end on January 31. Please send your comments on this thread. Comments like “I have reviewed the documents and believe they are ready for publication”, or “I have concerns about the document because …” are welcome and useful for the authors.
>
> Authors please indicate whether you are aware of any IPR for either of the drafts.
>
> Thanks.
>
> Mahesh & Kent
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf