Re: [core] 🔔 WG Last Call of CORECONF drafts: draft-ietf-core-yang-cbor-12, -sid-11, -comi-09, -yang-library-01 / -sid-11 review

Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu> Mon, 30 March 2020 12:26 UTC

Return-Path: <Laurent.Toutain@telecom-bretagne.eu>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1833A150E; Mon, 30 Mar 2020 05:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.186
X-Spam-Level:
X-Spam-Status: No, score=-0.186 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telecom-bretagne.eu
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 92SOWAJE84cd; Mon, 30 Mar 2020 05:26:27 -0700 (PDT)
Received: from zproxy130.enst.fr (zproxy130.enst.fr [IPv6:2001:660:330f:2::c2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BB0C3A150B; Mon, 30 Mar 2020 05:26:26 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id 824A0120ABC; Mon, 30 Mar 2020 14:26:25 +0200 (CEST)
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id USymcwRO6AzM; Mon, 30 Mar 2020 14:26:24 +0200 (CEST)
Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id CD34812150A; Mon, 30 Mar 2020 14:26:24 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy130.enst.fr CD34812150A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telecom-bretagne.eu; s=CFDC2CFA-4654-11E5-AACD-7BCC68B6580D; t=1585571184; bh=P9HDwzzSVtLl+BYUPbSdTpVt9bLU8FQY1tUcX6l5DXE=; h=MIME-Version:From:Date:Message-ID:To; b=hBB/sOQhH1akabEJwRcR1J8zZ20w+N9gv4sagdOhqNVEgSkSCAx5GCSrvH1mSB/HT C0yj1IVeNH5wR0OLltEjRRZSuRthto0uAAQqGmkYr2kY7A2obeCGCAXS+HyZpPsVMa oBPJaehYqzaJHuwfmCvJiFQurJ8aHGytPbInmlxw=
X-Virus-Scanned: amavisd-new at zproxy130.enst.fr
Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id RHI4SqztipeU; Mon, 30 Mar 2020 14:26:24 +0200 (CEST)
Received: from mail-yb1-f174.google.com (mail-yb1-f174.google.com [209.85.219.174]) by zproxy130.enst.fr (Postfix) with ESMTPSA id 7E87112133C; Mon, 30 Mar 2020 14:26:24 +0200 (CEST)
Received: by mail-yb1-f174.google.com with SMTP id g6so8906278ybh.12; Mon, 30 Mar 2020 05:26:24 -0700 (PDT)
X-Gm-Message-State: ANhLgQ3Pq4XIoajsUidCpCt58NW5PFK33AX81zSQpIyqyaniTCunsr2K 8o4s85iYI3bJt9/O82Bj3P13bZOokUKwpIUWyWw=
X-Google-Smtp-Source: ADFU+vtsyw/Xu70hRdQU4ZNvA4vyGjQS6Qb1iYACnQNdIWLhGRV3QsnPZvbOPWKPnG11LhbezOdRZzVMREwVByeqjvc=
X-Received: by 2002:a25:bc03:: with SMTP id i3mr11099284ybh.462.1585571183184; Mon, 30 Mar 2020 05:26:23 -0700 (PDT)
MIME-Version: 1.0
References: <AM5P190MB0275B51995123947A5F1A5DBFDCB0@AM5P190MB0275.EURP190.PROD.OUTLOOK.COM>
In-Reply-To: <AM5P190MB0275B51995123947A5F1A5DBFDCB0@AM5P190MB0275.EURP190.PROD.OUTLOOK.COM>
From: Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>
Date: Mon, 30 Mar 2020 14:25:44 +0200
X-Gmail-Original-Message-ID: <CABONVQa9zzuOama-NY5bNtYWVT_rcC3wnmDZDDBQ-d=3SDmCPw@mail.gmail.com>
Message-ID: <CABONVQa9zzuOama-NY5bNtYWVT_rcC3wnmDZDDBQ-d=3SDmCPw@mail.gmail.com>
To: "core@ietf.org WG" <core@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000023d02605a2118f8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/RCg5k-BEaQ-FnMbIgZY94K5Mlos>
Subject: Re: [core] =?utf-8?q?=F0=9F=94=94_WG_Last_Call_of_CORECONF_drafts=3A?= =?utf-8?q?_draft-ietf-core-yang-cbor-12=2C_-sid-11=2C_-comi-09=2C_-yang-l?= =?utf-8?q?ibrary-01_/_-sid-11_review?=
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Mar 2020 12:26:31 -0000

Hi,

I've uses these drafts, mainly -sid, -cbor, -comi, when I was defining the
SCHC Data Model to study the impact of CORECONF on the serialization.
For me, it is a mature work describing CORECONF. Documents are clear with
examples. I looked at the diff for the latest versions and I don't see
any significant changes, so for me, these documents are ready.

Laurent

On Mon, Mar 30, 2020 at 1:18 PM Esko Dijk <esko.dijk@iotconsultancy.nl>
wrote:

> Hello CoRE,
>
> I did a quick review of the -sid-11 draft; it looks ready for publication.
> Some minor issues found :
>
> Reference to RFC 7120 early allocation procedure: the allocation policies
> for the registries are all "Expert review". And the RFC 7120 early
> allocation procedure is defined, to do early allocations. However RFC 7120
> mentions that this procedure only applies in case :
>    (Section 2)
>    a. The code points must be from a space designated as "RFC
>        Required", "IETF Review", or "Standards Action".  Additionally,
>        requests for early assignment of code points from a
>        "Specification Required" registry are allowed if the
>        specification will be published as an RFC.
> So at first sight it looks like the procedure is not applicable, taken
> strictly. However IANA indicates (
> https://www.iana.org/help/protocol-registration) that "Expert review" is
> part of "Specification Required" so it would apply still. But in RFC 8126
> this is not mentioned in the same manner - so it could confuse some readers
> about whether it applies or not. Maybe some text could be added to state
> why RFC 7120 process does apply to the "Expert review" policy, even though
> "Expert review" is not listed under Section 2 point a. of RFC 7120.  (Note
> that early allocation by RFC 7120 only applies to "Expert review"
> allocations for draft documents that aim to become RFC.)
>
> Section 6.3.3: table column 1 is very narrow and it breaks the entry point
> integer number, which is confusing. Why not make this column wider by one
> character? One of the last 2 columns can be made more narrow if needed.
>
> Section 3: "RESCONF" -> RESTCONF
>
> Section 3: CoRECONF -> CORECONF
>
> Section 3: "For example how this could be achieved, please refer to"
> -> For examples on how this could be achieved, please refer to
>
> Section 3: "For diagram of one"
> -> For a diagram of one ...
>
> Best regards
>
> Esko
>
> IoTconsultancy.nl  |  Email/Skype: esko.dijk@iotconsultancy.nl
>
>
>
> -----Original Message-----
> From: core <core-bounces@ietf.org> On Behalf Of Carsten Bormann
> Sent: Monday, March 9, 2020 14:05
> To: core <core@ietf.org>
> Cc: netmod@ietf.org
> Subject: [core] 🔔 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
>
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
> _______________________________________________
> core mailing list
> core@ietf.org
> https://www.ietf.org/mailman/listinfo/core
>


-- 
Laurent Toutain
+--- VoIP (recommended) ---+----------- Télécom Bretagne -----------+
| Tel: +33 2 22 06 8156    | Tel: + 33 2 99 12 7026                 | Visit
:
| Mob: +33 6 800 75 900    |                                        |
| Fax: +33 2 22 06 8445    | Fax: +33 2 99 12 7030                  |
http://class.touta.in
| Laurent@Touta.in         | Laurent.Toutain@Telecom-Bretagne.eu    |
+--------------------------+----------------------------------------+