Re: [netmod] [core] 🔔 admin WG Last Call of CORECONF drafts: draft-ietf-core-yang-yang-library-01

Ivaylo Petrov <ivaylo@ackl.io> Sun, 12 April 2020 17:23 UTC

Return-Path: <ivaylo@ackl.io>
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 CA5263A1092 for <netmod@ietfa.amsl.com>; Sun, 12 Apr 2020 10:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ackl-io.20150623.gappssmtp.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 sxZnKLgcOBk7 for <netmod@ietfa.amsl.com>; Sun, 12 Apr 2020 10:23:14 -0700 (PDT)
Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB663A1090 for <netmod@ietf.org>; Sun, 12 Apr 2020 10:23:14 -0700 (PDT)
Received: by mail-wr1-x42b.google.com with SMTP id j2so8004174wrs.9 for <netmod@ietf.org>; Sun, 12 Apr 2020 10:23:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ZJNv4u4Z66dnbrnlsrhUOXnaVIzy7JF0j4FZlB9Mcx8=; b=X8+cqT1qXYeHrcPbrzzmdu5bSnGNqJR0hNcxWOykNCEZGsvCz1vsF99LEHZ5FDxL69 tYdgxNfOMfq9p2z2dG7ux/w/mZCPd+zNQobzoHncH1m0Eouxkfo+UsyYrUUfWusr6hTJ Vo0djsRKhp9OrgsI+hsNPf2seyouI1hJ+qI55D9QIBI3NQptJyrOumWNHq1uJs7DoHUR GExIgpOvTzosxY2McOVA5u8XBri6ehVkr6Ioglufjwg2tqgwXsBvQ/wBrLorHyr3Nfbw AYS0JEV5lM6iYc1bU88GAMrYes4tzUGJfENVAQoiufNR/9DFU06Tnj6NLBZXuA1JnGDk aj6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ZJNv4u4Z66dnbrnlsrhUOXnaVIzy7JF0j4FZlB9Mcx8=; b=hHFl0vesDQEM77sxRdc9SG5r7TYe7LRs5hEd4+/dgNtED6us5FFC88yLjmPQOnmgNI BpY19LnuiroKk0ZSIlPkiYawDfioOZijPZ2jchMjUmtqBB47HD0690/KKDdxbWbymwvX sX4NZQA0NnHf1BtoVWgGi8hB+VN5FxLpaHeu4i06kPPK6J1da4kiBoKlpqxkcMr9Rbqi HPdS062NSBv4RUf2YK44j1sQvCNv15u8tgTvZ9JqDBXD69l8kJDbCtZKngTAQYKXplgK DAXqCpzz6NuzdRmQYWkeQFAX3AEM8lNWBY5yplbnucXa92jXEhmHFt5O74YaobSed6ku s5MQ==
X-Gm-Message-State: AGi0PuZ81YR6B5mz/oDFOottzwSiZfl+rViD/2CDx2tgSd+hcinQi7Gf Q4M6T42lcLeOIBCa9v14OfVpqzP28iolsMjdAytDTA==
X-Google-Smtp-Source: APiQypJ/F43IEX74k1NMeV69iAL5QBEhp+lPvY+JJEloxDvJY66dhpnM5W/5SlSiseCnUKxyryMWFQnMGekgdEh0i58=
X-Received: by 2002:a5d:500b:: with SMTP id e11mr6407251wrt.272.1586712192779; Sun, 12 Apr 2020 10:23:12 -0700 (PDT)
MIME-Version: 1.0
References: <9AD3C4BB-7965-4776-84C4-6B5BFDCAA262@tzi.org> <e3a61d2c-1183-5ece-74d8-b1bad26ddfe6@ericsson.com> <15C8F1D1-B560-4D52-8D77-377C6B1C0518@tzi.org> <DB7PR07MB56578E540FA99F4494970ADEA0CB0@DB7PR07MB5657.eurprd07.prod.outlook.com> <CAJFkdRzjEGvGMT=xmtuZRgK1gYNFsouy-cSBjrzuiBqafUDWJQ@mail.gmail.com> <DB7PR07MB565769ABAF13EB4EC9C17EB0A0C10@DB7PR07MB5657.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB565769ABAF13EB4EC9C17EB0A0C10@DB7PR07MB5657.eurprd07.prod.outlook.com>
From: Ivaylo Petrov <ivaylo@ackl.io>
Date: Sun, 12 Apr 2020 19:22:46 +0200
Message-ID: <CAJFkdRw2aKOyj4vNhH0aG0citG0TY0VNeRFbMQDKrX+SUXOPBw@mail.gmail.com>
To: tom petch <ietfc@btconnect.com>
Cc: core <core@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009c9b3905a31b3853"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/W3zuik1TYLDJreiO4gcOLItEfGA>
Subject: Re: [netmod] =?utf-8?b?W2NvcmVdICDwn5SUIGFkbWluIFdHIExhc3QgQ2FsbCBv?= =?utf-8?q?f_CORECONF_drafts=3A_draft-ietf-core-yang-yang-library-01?=
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 12 Apr 2020 17:23:17 -0000

Hello Tom,

Thank you for the additional details! I updated the security considerations
and the link [1] can still be used for the diff between version -01 of the
draft and our current version. If there are no new comments in the next few
days, I intend to submit a new revision of the draft.

Best regards,
Ivaylo

[1]:
https://tools.ietf.org/rfcdiff?url1=draft-ietf-core-yang-library&url2=http://core-wg.github.io/yang-cbor/draft-ietf-core-yang-library-latest.txt.txt.





On Thu, Apr 9, 2020 at 10:47 AM tom petch <ietfc@btconnect.com> wrote:

> From: Ivaylo Petrov <ivaylo@ackl.io>
> Sent: 08 April 2020 13:06
> Hello Tom,
>
> Thank you for your review and your comments! They were indeed very
> helpful. I will try to spend some more time making sure we follow the
> recommendations from RFC8407, but for now please find my answers below
> (prefixed with [IP]). Note that the diff after handing your comments can be
> found at [1] for the txt file diff and [2] for the raw Markdown diff.
>
> <TP>
> I like your initials!
>
> On Security, no, RFC8407 requires you to use the boilerplate from the
> wiki; except that you cannot since you must reference CORECONF but I think
> that you must use the boiler plate with minimal change ie just adding the
> reference to CORECONF.  The Security in RFC7895 is out of date, no RESTCONF.
>
> Otherwise, looks ok and I will look again when a new I-D appears - I do
> like the plain text I-D format as a way of working:-)
>
> tom petch
>
> Best regards,
> Ivaylo
>
> [1]:
> https://tools.ietf.org/rfcdiff?url1=draft-ietf-core-yang-library&url2=http://core-wg.github.io/yang-cbor/draft-ietf-core-yang-library-latest.txt
> [2]:
> https://github.com/core-wg/yang-cbor/commit/2aa29f2468c827fd4b58cad6a5decba795d9c767
>
>
> On Mon, Mar 30, 2020 at 12:11 PM tom petch <ietfc@btconnect.com<mailtomailto:
> ietfc@btconnect.com>> wrote:
> There is quite a lot wrong with the admin of the YANG-library I-D when
> compared with RFC8407 IMHO
>
> Security considerations does not conform to boiler plate
>
> [IP]: Adding the following text in the beginning of the security
> considerations will make it follow the same structure as RFC7895. Would
> that be acceptable for you?
>
> The YANG module defined in this memo is designed to be accessed via
> CORECONF
> {{-comi}}, NETCONF {{RFC6241}} or RESTCONF {{RFC8040}}. Depending on the
> used
> protocol, the security considerations of some or all of those will apply.
>
> IANA considerations does not register name space
>
> [IP]: I added such registration. Please let me know if it looks fine. The
> relevant text is:
>
> ## YANG Namespace Registration
>
> This document registers the following XML namespace URN in the "IETF XML
> Registry", following the format defined in {{RFC3688}}:
>
> URI: please assign
> urn:ietf:params:xml:ns:yang:ietf-constrained-yang-library
>
> Registrant Contact: The IESG.
>
> XML: N/A, the requested URI is an XML namespace.
>
> RFC 6991  is imported and so MUST be a Normative reference
>
> [IP]: Fixed
>
> ietf-sid-file is imported and so MUST be a Normative  not Informative
> reference for the I-D
>
> [IP]: Fixed
>
> reference ietf-core-sid would be better as RFC YYYY with an RFC Editor
> note asking them to replace YYYY with the number assigned to 'YANG Schema
> ...
>
> [IP]: Fixed
>
> Organization Netconf WG seems an odd choice and contradicts contact details
>
> [IP]: Changed to CoRE WG
>
> Contact does not normally specify WG Chairs
>
>
> [IP]: I removed the chairs and left only the group and the editors. Is
> that what you had in mind?
>
> more than one revision clause
>
> [IP]: Fixed
>
> CORECONF not an abbreviation I recognise
>
> [IP]: We have received other comments related to this. We will discuss
> them during the meeting today and try to clarify this.
>
> I will look some more as and when these are addressed (or I see IETF Last
> Call:-)
>
> Tom Petch
> ________________________________________
> From: netmod <netmod-bounces@ietf.org<mailto:netmod-bounces@ietf.org>> on
> behalf of Carsten Bormann <cabo@tzi.org<mailto:cabo@tzi.org>>
> Sent: 09 March 2020 13:04
> To: core
> Cc: netmod@ietf.org<mailto:netmod@ietf.org>
> Subject: [netmod] 🔔 WG Last Call of CORECONF drafts:
> draft-ietf-core-yang-cbor-12, -sid-11, -comi-09, -yang-library-01
>
> It took us a long time to get the four CORECONF drafts in sync,
> but now we are ready for WGLC.
>
> This starts a working group last call for
> — draft-ietf-core-yang-cbor-12
> — draft-ietf-core-sid-11
> — draft-ietf-core-comi-09
> — draft-ietf-core-yang-library-01
>
> ending on
>
>         24:00 UTC on Tuesday, March 31, 2020.
>
> (This includes some extra time for the IETF week and for cross-WG
> coordination.)
>
> This WGLC is copied to the netmod WG mailing list; please do have a look
> at these drafts as they are slated to become a part of the greater
> YANG/NETCONF/RESTCONF family.  We intend the discussion to be on the
> CoRE mailing list, but if you find a fundamental issue with YANG or
> RESTCONF, feel free to discuss that on netmod instead.
>
> Please start a new email thread for each major issue that will need
> discussion and make sure the subject line includes the draft name and
> some sort of name for the issue.  (Minor issues such as typos can also
> be sent to the authors.)
>
> If you read the draft and think it looks fine, please send a one line
> email to the list or to the chairs letting us know that so we can get
> a feel of how broad the review has been.
>
> (To reviewers and authors:)  If you are aware of any patent claims that
> might apply to systems that implement these drafts, please review BCP 78
> and BCP 79 and make any appropriate IPR declaration before the last-call
> ends. If you are not sure whether you need to make a declaration or not,
> please talk to the chairs and we will help.
>
> Grüße, Carsten
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org<mailto:netmod@ietf.org>
> https://www.ietf.org/mailman/listinfo/netmod
> _______________________________________________
> core mailing list
> core@ietf.org<mailto:core@ietf.org>
> https://www.ietf.org/mailman/listinfo/core
>