Re: [Netconf] draft-ietf-netconf-nmda-netconf review

Robert Wilton <rwilton@cisco.com> Tue, 15 May 2018 13:14 UTC

Return-Path: <rwilton@cisco.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77155127775 for <netconf@ietfa.amsl.com>; Tue, 15 May 2018 06:14:56 -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 z5MwFx-raSQZ for <netconf@ietfa.amsl.com>; Tue, 15 May 2018 06:14:49 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D6C12D0C3 for <netconf@ietf.org>; Tue, 15 May 2018 06:14:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1630; q=dns/txt; s=iport; t=1526390089; x=1527599689; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=mVD3hwevR5oBbfe7yoCnrunKvbHjfAYv7HYBv9JguVM=; b=QD8rdd9H79RjOAzCxkJJYiGNjIEsz5zIY+swQhZYVPgJ0APGXwH2cLoT 7aXCvbVa86KXl1PdmV85ofbsDykXEITxJu2rxDlmzkugme1FPOlkoxlH7 SpihHcZEjb+jmS/U2+TQWsMtkBGzp1+PHgJdQytsZ84BDpB11qB6H6kuX A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DQAQDH3Ppa/xbLJq1cGQEBAQEBAQEBAQEBAQcBAQEBAYQkfCiDdIhijWQIIYEPlSoLGAuEA0YCgzk4FAECAQEBAQEBAmwcDIUoAQEBAwEBASEPAQU2GwsOCgICJgICJzAGAQwGAgEBgx8CgXcID6sBghyEWINxgiIFgQmIcD+BMgyCXIMRAQGBSoMWglQCmDkJjkwGh1mFGIs8hSmBJTMhgVIzGggbFTuCQ4sQhT8+MI9KAQE
X-IronPort-AV: E=Sophos;i="5.49,403,1520899200"; d="scan'208";a="3794468"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 May 2018 13:14:47 +0000
Received: from [10.63.23.78] (dhcp-ensft1-uk-vla370-10-63-23-78.cisco.com [10.63.23.78]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w4FDElc7015225; Tue, 15 May 2018 13:14:47 GMT
To: Mahesh Jethanandani <mjethanandani@gmail.com>, Netconf <netconf@ietf.org>
References: <69877EC3-DE3E-4428-A2A2-56A2AC29CDCD@gmail.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <f3265966-98e4-3698-9f9a-8318c20bb331@cisco.com>
Date: Tue, 15 May 2018 14:14:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <69877EC3-DE3E-4428-A2A2-56A2AC29CDCD@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GQA4un3nJaR0LDW5U-RnqD6aMrY>
Subject: Re: [Netconf] draft-ietf-netconf-nmda-netconf review
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 May 2018 13:14:56 -0000

Hi Mahesh,

On 15/05/2018 09:36, Mahesh Jethanandani wrote:
> A quick review of the draft has revealed the following issue and question.
>
> 1. A run of pyang on the model reveals the following:
>
>> pyang --ietf ietf-netconf-nmda@2018-04-20.yang
> ietf-netconf-nmda@2018-04-20.yang:205: warning: RFC 6087: 4.10,4.12: statement "enum" should have a "description” substatement
>
> 2. This is a follow-up to the discussion on the mailing list. Reading through this draft, RFC7950, RFC6020, and rfc7895bis, it is not clear if a NETCONF server that wants to support both YANG 1.0 and YANG 1.1, needs to do from a schema advertisement perspective. Does it advertise the schemas as part of <hello> and as part of yang-library:1.1? Does it advertise both YANG 1.0 and 1.1 models in both the modes?
It is the specific modules that are being supported that are YANG 
1.0/YANG 1.1 rather than the NETCONF server generically.

So, I think that this is really a variant of the broader question: Can a 
device implement multiple revisions of a YANG module?  This seems like a 
question that may be appropriate to be considered by the YANG versioning DT.

But my recollection of the current RFCs (and YANG library bis draft) is 
that a standards compliant server only advertises a single revision of a 
module, and hence supporting multiple revisions is beyond the scope of 
the current standards documents.

Thanks,
Rob


>
>
> Mahesh Jethanandani // as shepherd
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf