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

Esko Dijk <esko.dijk@iotconsultancy.nl> Mon, 30 March 2020 11:17 UTC

Return-Path: <esko.dijk@iotconsultancy.nl>
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 090D63A13D2; Mon, 30 Mar 2020 04:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.011
X-Spam-Level:
X-Spam-Status: No, score=0.011 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=iotconsultancynl.onmicrosoft.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 gZ4c9i1XrR4E; Mon, 30 Mar 2020 04:17:30 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130101.outbound.protection.outlook.com [40.107.13.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A963A13D0; Mon, 30 Mar 2020 04:17:28 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GCG3DUc7FWicZx6yEXOJhTIrNQdCkr0T4HnNHA82fGrMVF+XFX2q5ntD0as33soSQerWEpAP9iv7/ueVgmS10bnYcxyJhmgpyN0AKqAHmTwKYEXz8bdd/FLjkURQCpoUsLEYVBp6futZiHfmT89A83EEFqLHeSJ51rFlJYLzDNzy2cNGZPISRT29JhJo3OFHBkWmCa8Nj32K+lRUhq+JzlH8QJD4sEC1PeRB4G8VYRF3X9JCVxPSLA/yysx5tEV7FwkrFXTx8/I+EiHSlXHCK6D1xkgRePz+19GK6zIzmS07+gpkNXjQlkN5cfsm7Immsgt62Bj3lAzb/NCMuQYS9A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LMCEI6ryyZWCUpQ77lCkDbNsPgTCcP1zhT9dH29l0qY=; b=LnO30753klJt3X6rNl5S6kd5uP/MsIE7gjzOEjK3UhcpleqPRzexgvtKWkqT/6SvggGpitynJ/suZCqBXDVwA7zIS8U87abqr0GxENgPP35NQsvqHASFAtpfFTKHnbzLA+HF/kPkJPvRDbXGWq0wRkgt/tEXpBnB4mg09EreQ41H/UD1d9sY12Jp0rTZN33aU457dq4c2+t44IY2hK17VHr5oSx/VUPt3W+1VOo6I134v1tSeQxqUDG9tbop2R95Tuc4VyGUp5JK+as5rcvRFxPO99mGtRbhk55FrUoDvF1/KnepbXQH4qEPsv4bAAwkC9ZqrtSdTLiGWxyy7ZuwLQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=iotconsultancy.nl; dmarc=pass action=none header.from=iotconsultancy.nl; dkim=pass header.d=iotconsultancy.nl; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iotconsultancynl.onmicrosoft.com; s=selector2-iotconsultancynl-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LMCEI6ryyZWCUpQ77lCkDbNsPgTCcP1zhT9dH29l0qY=; b=AAkvNDA1fQB4lvA+iAHO/S+/p65WrO0AwlF4kzu6jiQ4w8kaulesKZ4juYTRQkgAELObRpkHg5m9Q0UjPlZESNWv5ZAXG2AiXz+bNfiH2Pob0BSjKrb0JHzBdyxpoLNQag/qQvyFP6D6GZLw5wSjMPQfC34tl4ISop61Ih73Kmk=
Received: from AM5P190MB0275.EURP190.PROD.OUTLOOK.COM (10.161.62.28) by AM5SPR01MB03.EURP190.PROD.OUTLOOK.COM (10.161.64.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.18; Mon, 30 Mar 2020 11:17:25 +0000
Received: from AM5P190MB0275.EURP190.PROD.OUTLOOK.COM ([fe80::8c96:a66b:e170:bf8f]) by AM5P190MB0275.EURP190.PROD.OUTLOOK.COM ([fe80::8c96:a66b:e170:bf8f%3]) with mapi id 15.20.2856.019; Mon, 30 Mar 2020 11:17:24 +0000
From: Esko Dijk <esko.dijk@iotconsultancy.nl>
To: "core@ietf.org WG" <core@ietf.org>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: =?utf-8?B?W2NvcmVdIPCflJQgV0cgTGFzdCBDYWxsIG9mIENPUkVDT05GIGRyYWZ0czog?= =?utf-8?B?ZHJhZnQtaWV0Zi1jb3JlLXlhbmctY2Jvci0xMiwgLXNpZC0xMSwgLWNvbWkt?= =?utf-8?Q?09,_-yang-library-01_/_-sid-11_review?=
Thread-Index: AdYGauCXENFcYkg2Q0mXOYdiGy0Jfg==
Date: Mon, 30 Mar 2020 11:17:24 +0000
Message-ID: <AM5P190MB0275B51995123947A5F1A5DBFDCB0@AM5P190MB0275.EURP190.PROD.OUTLOOK.COM>
Accept-Language: en-US, nl-NL
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=esko.dijk@iotconsultancy.nl;
x-originating-ip: [85.147.167.236]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8d8bc56b-4410-4ce2-2912-08d7d49bec7d
x-ms-traffictypediagnostic: AM5SPR01MB03:
x-microsoft-antispam-prvs: <AM5SPR01MB030975B81FEE56AA794E70FDCB0@AM5SPR01MB03.EURP190.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0358535363
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM5P190MB0275.EURP190.PROD.OUTLOOK.COM; PTR:; CAT:NONE; SFTY:; SFS:(10019020)(366004)(396003)(346002)(376002)(136003)(39830400003)(66946007)(450100002)(6506007)(71200400001)(53546011)(66446008)(64756008)(66556008)(66476007)(86362001)(76116006)(316002)(9686003)(81156014)(7696005)(55016002)(81166006)(8936002)(2906002)(4326008)(186003)(33656002)(5660300002)(52536014)(44832011)(508600001)(26005)(966005)(6916009); DIR:OUT; SFP:1102;
received-spf: None (protection.outlook.com: iotconsultancy.nl does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2GQLRZf36muHABm5w4vdjuGfwtwNvkLrbsjHhSmumGTDNBqE0FLfRa7mf16OHEI7bahR+8iyEbFirCGDO4jOdS+8SOSpSYr/HopkA2l/9mop7tC4KBlNt8oEhXL68bFHCIWqGIZooKi2a4TScP7Wjs7vQw/iVB2EC5J1SVUYJqs/8l7sqdfmwAsxyj/mKRlT9kSeHC9dl0ywBR9kHYNohrLuVhaLCxD/GIZvvQBEI3HzDvFim4bJApTxahgsrv32CS4iA1KUt4vS8TCnMfrNa3vZagLNjHrqWHhI2rSwDAEgOGTg5u3ZUsUkMnUXQeYgeObvrzA943ogMHpDpbywKJcQ9PeL0T4OVvexhneYjeTVoNJq1MGHoFbZ00RHdJkIRD+m8btn24FwN3g1MC8lh54+fmDfK++f++q8fKLn4AD8cuH99vLHzrXhzTD1qAJiRnij+bLMauDvRjEKaqMEmyShSNRXyhcXaFGHxLH9hUKUV3MdonXVtHX+pnE7YuW/eRjOxXiAdsOtle4SkAUeiA==
x-ms-exchange-antispam-messagedata: U2h2xMYKkYU+ujDu+OSCLGxXdWHhxCfuNLcAQ0Wh4TLXSueek+MskuA/C4qaWZQN+9o4mSZ9xfzhTufvsKJs3H8mGrDY7m5p+rLx1yWwjioh5UaNvAQcUK5nBub8gLesspK3Yq858AYNOhsmtNBENg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: iotconsultancy.nl
X-MS-Exchange-CrossTenant-Network-Message-Id: 8d8bc56b-4410-4ce2-2912-08d7d49bec7d
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2020 11:17:24.7581 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 58bbf628-15d2-46bc-820b-863b6774d44b
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: kF2ibYUz2QKMvEdhUkQe2Sy4LqtHNuk0XdLEyTsVMssBjoJj96xmz+4IDZxpTUh5Bt9zPQSTTFo4iD7gFyqpTGsgpE0qLFRqhyapgvgmNyY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5SPR01MB03
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/hhASW9Fy_0fmI2UGJgjkoIA_A-M>
Subject: Re: [netmod] =?utf-8?b?W2NvcmVdIPCflJQgV0cgTGFzdCBDYWxsIG9mIENPUkVD?= =?utf-8?q?ONF_drafts=3A_draft-ietf-core-yang-cbor-12=2C_-sid-11=2C_-comi-?= =?utf-8?q?09=2C_-yang-library-01_/_-sid-11_review?=
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: Mon, 30 Mar 2020 11:17:32 -0000

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