Re: [netmod] [Technical Errata Reported] RFC7950 (5879)

Schönwälder, Jürgen <J.Schoenwaelder@jacobs-university.de> Tue, 22 October 2019 15:37 UTC

Return-Path: <J.Schoenwaelder@jacobs-university.de>
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 E60F512009C for <netmod@ietfa.amsl.com>; Tue, 22 Oct 2019 08:37:47 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jacobsuniversity.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 M0_QucCnejeT for <netmod@ietfa.amsl.com>; Tue, 22 Oct 2019 08:37:44 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20043.outbound.protection.outlook.com [40.107.2.43]) (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 677CB120073 for <netmod@ietf.org>; Tue, 22 Oct 2019 08:37:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oHwLZj5neQ2ZPNsvWKyVtd6+yg1T2la6+t/ZZg3/fP7a7K6t2gI7aKk3GgixnmENfIybMbnvQjHz1j/xRBAYHr7ASUKo5pqofQ57FkZmnKWrZZfEbw4dZ0tMA4OmDnXULX1WdqR8UzqFMSvD4XJHynvaMHLoobShqsJSHwCKYxD5i93kj8DpqKAOvCle8mpR/RRyGjyjfSGgvDrJ2MY/ou+b/9u4ZA0vHGXb5TnSuqO4gddDent2cza3ox/NW0xsZXQTSHZl3MTFcdSBI4p1phVUVO/zgBZp1yUbJKdhtyShB0LdorntxxmKGdC1L6RXTCLBULBA8RVniqqV7j4cOA==
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=f4RoNDtL/jzeKw3AgUo2pegiB2pOpemabwsW1ptvb0s=; b=nRCKk7GRbMmNG/1CQMcbJucqLIoZdLn7wFc4ed7Q1vUn2QKr/aN1Z5IDBgQAQ/GueQh+NfsfGQAIyCfwP9XI918ipasZjuVzXAaYjGpFVCZ6itd1WhMRzgyqw5wq0QlNP3yxKF+X/0QIpc6QEBKgsg+Fyfq5VeZje0AQYltW2xxACEXvCr7VVqbG7VAQPcKc0UKuETmRLgvhrZAmdKR+8PUt5G+80n+6MkHCtzsjfyCnFdYiRG//Vfx8crHCGt/dOonPV5riLC9fybRXTOqJRcPbsv6MOGr2tfBBO+onwyl5wDC5n+Fs+DfIgoQG1t9yeyz76SI4DJk8EVQNKnQKOQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=jacobs-university.de; dmarc=pass action=none header.from=jacobs-university.de; dkim=pass header.d=jacobs-university.de; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jacobsuniversity.onmicrosoft.com; s=selector2-jacobsuniversity-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=f4RoNDtL/jzeKw3AgUo2pegiB2pOpemabwsW1ptvb0s=; b=JHdSlCbsyg6EhS9+ZjIf1u0ifbIoaCPhji74xVSqkFmTVCC2/4W4VQUUWre8DW+zM+GZWX+mvlPhHOd21DDYKQ+EQeOnI6Olh8S7c5DGr7+TSH2Y1UiMHPJhab5uteXz1BxppFy6iW4OoE9UzEwdYkJ0yeoOQQgr0XC3ftCnyDs=
Received: from AM4P190MB0129.EURP190.PROD.OUTLOOK.COM (10.172.218.17) by AM4P190MB0180.EURP190.PROD.OUTLOOK.COM (10.172.218.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2367.24; Tue, 22 Oct 2019 15:37:41 +0000
Received: from AM4P190MB0129.EURP190.PROD.OUTLOOK.COM ([fe80::1112:b17:e675:4506]) by AM4P190MB0129.EURP190.PROD.OUTLOOK.COM ([fe80::1112:b17:e675:4506%9]) with mapi id 15.20.2367.022; Tue, 22 Oct 2019 15:37:41 +0000
From: =?iso-8859-1?Q?Sch=F6nw=E4lder=2C_J=FCrgen?= <J.Schoenwaelder@jacobs-university.de>
To: "Rob Wilton (rwilton)" <rwilton@cisco.com>
CC: Martin Bjorklund <mbj@tail-f.com>, "rfc-editor@rfc-editor.org" <rfc-editor@rfc-editor.org>, "ibagdona@gmail.com" <ibagdona@gmail.com>, "warren@kumari.net" <warren@kumari.net>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] [Technical Errata Reported] RFC7950 (5879)
Thread-Index: AQHViOuVXcD8Fw3mlkGtoHC6DGNDzqdmy28A
Date: Tue, 22 Oct 2019 15:37:41 +0000
Message-ID: <20191022153740.fdn4yewitln4eu5c@anna.jacobs.jacobs-university.de>
References: <20191022114319.CD85BF4071D@rfc-editor.org> <20191022.170229.971604522071303700.mbj@tail-f.com> <MN2PR11MB436681482C373D5B2E692899B5680@MN2PR11MB4366.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB436681482C373D5B2E692899B5680@MN2PR11MB4366.namprd11.prod.outlook.com>
Reply-To: =?iso-8859-1?Q?Sch=F6nw=E4lder=2C_J=FCrgen?= <J.Schoenwaelder@jacobs-university.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: AM0PR01CA0095.eurprd01.prod.exchangelabs.com (2603:10a6:208:10e::36) To AM4P190MB0129.EURP190.PROD.OUTLOOK.COM (2603:10a6:200:5f::17)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=J.Schoenwaelder@jacobs-university.de;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:638:709:5::7]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: a80afe96-ffb3-4320-a514-08d75705c656
x-ms-traffictypediagnostic: AM4P190MB0180:
x-ms-exchange-purlcount: 3
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM4P190MB018030EED6DDDB812E7687A0DE680@AM4P190MB0180.EURP190.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(346002)(136003)(366004)(396003)(376002)(189003)(13464003)(199004)(76176011)(86362001)(6116002)(305945005)(99286004)(66556008)(64756008)(66446008)(6506007)(386003)(7736002)(66946007)(3450700001)(2906002)(52116002)(186003)(316002)(53546011)(66476007)(102836004)(786003)(6916009)(45776006)(486006)(6306002)(43066004)(1076003)(14444005)(256004)(6246003)(966005)(8676002)(5660300002)(6486002)(476003)(14454004)(81166006)(81156014)(229853002)(478600001)(8936002)(25786009)(71190400001)(6436002)(71200400001)(46003)(11346002)(54906003)(4326008)(446003)(6512007); DIR:OUT; SFP:1101; SCL:1; SRVR:AM4P190MB0180; H:AM4P190MB0129.EURP190.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: jacobs-university.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 5nMUO8MBkI7LL/mC4xP7UQadrS+CPokW++UtuqYmJgXod9Vlk+wciRyCR7EtyaPqzNhYTJwgDelswPNkAhpMdo5WBWF3pisvMCqmxKRKzO6//jNrjvHRY0lfJNHkNHMeUr9IMORtxzCNTnOh2AoAFTFQe6H6BI5cR+BYCeq3GPpUBv2graN+Ti0F1gL/sHCS4GB39q7WHhw/RnBnUcHUy7nQtWc0HtDeZULqliw8irxWAsZG8X7yvTS+XZx3DcUWUC1vBfwtGOnUP5stWyIqiDxIWKQzVV6rZmS4KG9GHGaPiTQDyadd8ZPRsqTa2DdYYR/nWKhiWDvHNXFHrrtmXkS5kqsTZrWBgUeY1MxMCSPMs+k8KoDpIFu4mNF17CfaAlDeaP2bByuOwXmpmFIYZqoCqhcEIndiWnoeH5zGyEfWz1JLOw/CNrtCPZgY04F3lKlchDvMbEs9qAQfeprXyXK2VGOyNpvAA6UGY82DFd4=
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C731C7EAE6BE0F47B75CA24ADE7CA116@EURP190.PROD.OUTLOOK.COM>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: jacobs-university.de
X-MS-Exchange-CrossTenant-Network-Message-Id: a80afe96-ffb3-4320-a514-08d75705c656
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2019 15:37:41.2813 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f78e973e-5c0b-4ab8-bbd7-9887c95a8ebd
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2qwQiJks6KJO8bWDFvntmru2P1oQO5ZbQ7eonSrKOFvicbk8KZFsN8mYEyhlydZmTnnUkOfGu172ZwwfuGZkxXKUiN0xdWSOo2/cXoE530I=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4P190MB0180
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/EI5B8UXDkxA9LncFAtS6BT1kdoI>
Subject: Re: [netmod] [Technical Errata Reported] RFC7950 (5879)
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: Tue, 22 Oct 2019 15:37:48 -0000

So we need to extend and clarify the terminology but this can't be
done via an errata. Looking at the RFC 8342 terms, we may need to also
define 'module schema', which is pretty much what the current 'schema
tree' definition is (or we just keep that definition).

(I am not sure 'YANG schema' as proposed in the packages work is a
 good term, but then this is a draft and this can be improved.)

I am also not sure that 'set of all modules implemented by a server'
(proposed by Lada) is a good definition; in the NMDA world, a server
implements several datastores and each datastore has a datastore
schema and they can be different.

Bottom line: I think the errata should be rejected and we should check
that we have a proper issue on the YANG issue next tracker to address
this terminology issue in the future.

/js

On Tue, Oct 22, 2019 at 03:15:49PM +0000, Rob Wilton (rwilton) wrote:
> I agree with Lada that having such a definition would be useful.
> 
> But I also agree with Martin that this isn't really an erratum.
> 
> It is also worth noting that RFC 8342 defines:
> 
>    o  schema node: A node in the schema tree.  The formal definition is
>       provided in RFC 7950.
> 
>    o  datastore schema: The combined set of schema nodes for all modules
>       supported by a particular datastore, taking into consideration any
>       deviations and enabled features for that datastore.
> 
> The latest version of the packages draft (not posted yet), defines:
> 
>    o  YANG schema: A datastore schema, not bound to any particular
>       datastore.
> 
> Thanks,
> Rob
> 
> 
> > -----Original Message-----
> > From: netmod <netmod-bounces@ietf.org>; On Behalf Of Martin Bjorklund
> > Sent: 22 October 2019 16:02
> > To: rfc-editor@rfc-editor.org
> > Cc: ibagdona@gmail.com; netmod@ietf.org; warren@kumari.net
> > Subject: Re: [netmod] [Technical Errata Reported] RFC7950 (5879)
> > 
> > Hi,
> > 
> > The problem is that it is not clear that we can use this new definition
> > with the rest of the text in the RFC that uses this term.
> > For example, section 7.1.5 talks about "the imported module's schema
> > tree", and this doesn't really work if the schema tree is not tied to a
> > module.
> > 
> > Also the proposed definition is recursive since it is defined in terms of
> > "schema node", and a "schema node" is already defined as "a node in the
> > schema tree".
> > 
> > So it probably makes sense to look at this definition (and the text and
> > other definitions) if we do a document update, but as it is currently
> > written I think it should be rejected.
> > 
> > 
> > /martin
> > 
> > 
> > 
> > RFC Errata System <rfc-editor@rfc-editor.org>; wrote:
> > > The following errata report has been submitted for RFC7950, "The YANG
> > > 1.1 Data Modeling Language".
> > >
> > > --------------------------------------
> > > You may review the report below and at:
> > > https://www.rfc-editor.org/errata/eid5879
> > >
> > > --------------------------------------
> > > Type: Technical
> > > Reported by: Ladislav Lhotka <lhotka@nic.cz>;
> > >
> > > Section: 3
> > >
> > > Original Text
> > > -------------
> > > o  schema tree: The definition hierarchy specified within a module.
> > >
> > >
> > > Corrected Text
> > > --------------
> > > o  schema tree: The hierarchy of schema nodes defined in the set of all
> > modules
> > >    implemented by a server, as specified in the YANG library data
> > [RFC7895].
> > >
> > >
> > >
> > > Notes
> > > -----
> > > The original definition of the term has two problems:
> > >
> > > 1. Schema tree is not limited to a single module. Some YANG constructs,
> > such as augment and leafref type, may refer to a schema node that is
> > defined in another module.
> > >
> > > 2. Apart from schema nodes, YANG modules contain definitions that do not
> > contribute to the schema tree: groupings, typedefs, identities etc.
> > >
> > > Instructions:
> > > -------------
> > > This erratum is currently posted as "Reported". If necessary, please
> > > use "Reply All" to discuss whether it should be verified or rejected.
> > > When a decision is reached, the verifying party can log in to change
> > > the status and edit the report, if necessary.
> > >
> > > --------------------------------------
> > > RFC7950 (draft-ietf-netmod-rfc6020bis-14)
> > > --------------------------------------
> > > Title               : The YANG 1.1 Data Modeling Language
> > > Publication Date    : August 2016
> > > Author(s)           : M. Bjorklund, Ed.
> > > Category            : PROPOSED STANDARD
> > > Source              : Network Modeling
> > > Area                : Operations and Management
> > > Stream              : IETF
> > > Verifying Party     : IESG
> > >
> > 
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>