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

"Rob Wilton (rwilton)" <rwilton@cisco.com> Tue, 22 October 2019 16:26 UTC

Return-Path: <rwilton@cisco.com>
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 3D79D1200E7 for <netmod@ietfa.amsl.com>; Tue, 22 Oct 2019 09:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=DF4pmy0O; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=PMSgjXPV
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 RSwfOkzX8iX9 for <netmod@ietfa.amsl.com>; Tue, 22 Oct 2019 09:26:31 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0275912004A for <netmod@ietf.org>; Tue, 22 Oct 2019 09:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6205; q=dns/txt; s=iport; t=1571761591; x=1572971191; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=oATxSsq6Y2pJlTMkDBZib3PIRdVGz2EGWNp0cQ+uizo=; b=DF4pmy0OctujCukFq72HX+OlPMGK84MMS9CM+4KYpiiy2rCAspCFcKlt N27OpVuMhl2aPV63LY+utgkH+aNIOXNg25TXTuaPX+biEq/HveV92/MoT fRgTuBGkQM336lnT3kE+8jpfuT/UjIeteoq/wDqxa20cS2Q0maBjP26gI 0=;
IronPort-PHdr: 9a23:UVXGthfIOC1Vt3/ghDpOPBBalGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGRD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/dTM7GNhFUndu/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B/AAD3LK9d/5RdJa1iAxkBAQEBAQEBAQEBAQEBAQEBAREBAQEBAQEBAQEBAYF7gUtQBWxXIAQLKgqHYwOKWIJciW+OFIJSA1QJAQEBDAEBGAsKAgEBg3tFAoMqJDgTAgMJAQEEAQEBAgEFBG2FNwyFSwEBAQQBARAuAQEsCwELAgICAQgQAQQBAQEuGwYGCx0IAgQOBQgagwGCRgMuAQIMpxcCgTiIYYIngn4BAQWFCQ0LghcDBgWBMYwPGIFAP4ERRoJMPoEEgRdHAQGBOhEYBRomgnuCLI0SJoIJhnWBNZUJLUEKgiSHDokzBVWEJoI7h1OPQI91hmiCEIwWgnoCBAIEBQIOAQEFgWkigVhwFRohgmxQEBSDBoNzM4RhhT90gSmMJ4ExAYEjAQE
X-IronPort-AV: E=Sophos;i="5.68,216,1569283200"; d="scan'208";a="651967040"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Oct 2019 16:26:27 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by rcdn-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x9MGQQ9O022440 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 22 Oct 2019 16:26:26 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 22 Oct 2019 11:26:25 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 22 Oct 2019 11:26:07 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 22 Oct 2019 12:26:07 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IAhZOiHXomuGMu1QHIvTud0svOjfElmNYVv/8ouXx4vzpxn0DvpRT3Ed1Vkm5Vagm+B/Ob2Tx+GCtXlygyeWVPaTAwaLJ6Z7Fuy9sphPcnviLtRWHVPy+JB2DEg/o2rLwV+occBpTZ5E6pm58KvQTvaJgjgRWRfni2R/gSVL6Ui+e3pPxoz2XxA/ep8yPMW19Qz9YLTuVxKKT5nOnV4aBXGstznnZ5dOPhoXeYS9Y3Fyo33QHdXjEtidEmN1VPSQ81WwSii05ffvjHopDmqYine43d5yB3e8P2sGKfGVFG586+a0KjgmQNWPOMFqkMaRR+6C9ov1qu2dZnwyktsn9g==
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=7yy82ENBjl8BvLfYHzjvqt/5dGe2IxoZzwUggaJRIcI=; b=daWDBbr8DVduTUhNdTc7+e2OPFhSUdZ4PszoJdw/SWzNGMdKq6tamoeCbKWWz3ql+/mhJxj48jwemGSo1h+McWm7B7Yg6ozqxZMUHSIuJDNg8bTDrG5XYYP7QOkpH0RS1RSya9Dr99U7o3z8jDH05fNPZJgNctyr3cjWE67zb/yYjBs5dIfDC8IvwWOrsDj5XV7eHSA0cDOZjJuIg/1FYn7zPcBEpT3c4eWrvlIR7cKeYhnWP/tche6iYTcP9twLI2+aOjK80oENmh4AHQBgTAqpPK9J45mqJ2DtMD0t69rTeQmuCeHBAJ7LLq3/L2IyM+wEm4oAZL6hzGs8xicTKw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=7yy82ENBjl8BvLfYHzjvqt/5dGe2IxoZzwUggaJRIcI=; b=PMSgjXPVKSGydVx4kruL2eJ/7H945Hqof9j7DOFiNXJ/6KYID19gXf9LNWANRh8IEdDp9wVgbv3Ckxa6LHldM5fI5gHZIpzlwZm/Mrki+GQWdbDv7H8vgSp6SGH709+0U/O3Im0JXJ+MSGdc/uYJTN7x71FPu1eibM5/s7S9x7M=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB4143.namprd11.prod.outlook.com (20.179.150.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2347.19; Tue, 22 Oct 2019 16:26:05 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::cca:41bd:b0bb:c549]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::cca:41bd:b0bb:c549%2]) with mapi id 15.20.2347.029; Tue, 22 Oct 2019 16:26:05 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: "Schönwälder, Jürgen" <J.Schoenwaelder@jacobs-university.de>
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: AQHViM30HuRaqySg8UOIHZIEP5XN5qdmwdaAgAACInCAAAezgIAADLBw
Date: Tue, 22 Oct 2019 16:26:05 +0000
Message-ID: <MN2PR11MB4366463FDAE0BA1103C46E1AB5680@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <20191022114319.CD85BF4071D@rfc-editor.org> <20191022.170229.971604522071303700.mbj@tail-f.com> <MN2PR11MB436681482C373D5B2E692899B5680@MN2PR11MB4366.namprd11.prod.outlook.com> <20191022153740.fdn4yewitln4eu5c@anna.jacobs.jacobs-university.de>
In-Reply-To: <20191022153740.fdn4yewitln4eu5c@anna.jacobs.jacobs-university.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.40]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6aef1945-df28-4c7f-7957-08d7570c8958
x-ms-traffictypediagnostic: MN2PR11MB4143:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <MN2PR11MB4143E788ED47FC7C203B7AA2B5680@MN2PR11MB4143.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01986AE76B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(396003)(376002)(136003)(39860400002)(346002)(189003)(199004)(13464003)(6246003)(7696005)(81156014)(9686003)(966005)(25786009)(478600001)(8676002)(54906003)(476003)(33656002)(81166006)(66556008)(66476007)(66446008)(64756008)(6436002)(14454004)(66946007)(5660300002)(52536014)(6306002)(55016002)(316002)(76116006)(76176011)(229853002)(4326008)(14444005)(256004)(486006)(7736002)(74316002)(102836004)(86362001)(446003)(8936002)(26005)(6506007)(53546011)(2906002)(99286004)(71200400001)(71190400001)(3846002)(66066001)(6116002)(66574012)(11346002)(6916009)(186003)(305945005); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4143; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /chYk3IySRAxYJogPosOVU029gjPDPqfQggBubnYsDn9D7f55o0hPw7kPcq4E5Y9WJLvLWWv20CZrD6YMTC992IOjF6DFnxKiCrFo9OB0xUTQhzDaYI5+IPRRlPlqbXQG/wx/NL0FaWBAcs36dTKGSAJs6iPW4NOdnKYORrqgUM8jpWDdFyxkBPS73F6rgPjrVNrHVYhSGQ48cn/rFnUrpTvPdDL8NEnFXRJiZxifiO5xc0xETJjADvsD9y4f5idgpAiRpZVpumHX41BOzDiJGLgizcR0y3nARfmToXKmUtlKPFbitFPGx9yI/b+xSbYc1fzDHrxxx1/rpf8+PbiF88JTBaGCwj1KWqpUc06BYlOmPgFYQGhRls2Pjq3ieju7QcM3jln8VYDN6tZc0CyhK1bFkv6XssyVGSFpsWPK6ZgAe+8nVMdXW6180glvhItH7QdByUHHyVjnjX/6UqEVoOnUdy/DFgVj1fEMJh19cM=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 6aef1945-df28-4c7f-7957-08d7570c8958
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2019 16:26:05.0735 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Ond0QdTNK8Eo9cyQmlPchevxlvFfzlNybg8M5ILMha6EqzH4YcLZGNMZDhYU/s0Fe8t7od07pCDbUPDaLojK5w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4143
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.28, xch-aln-018.cisco.com
X-Outbound-Node: rcdn-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5uDEBwgNehfLaPONpDSjVnCcWx8>
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 16:26:33 -0000

Yes.

I've raised https://github.com/netmod-wg/yang-next/issues/96 to track this.  Please modify/extend as appropriate.

Thanks,
Rob


> -----Original Message-----
> From: Schönwälder, Jürgen <J.Schoenwaelder@jacobs-university.de>
> Sent: 22 October 2019 16:38
> To: Rob Wilton (rwilton) <rwilton@cisco.com>
> Cc: Martin Bjorklund <mbj@tail-f.com>; rfc-editor@rfc-editor.org;
> ibagdona@gmail.com; warren@kumari.net; netmod@ietf.org
> Subject: Re: [netmod] [Technical Errata Reported] RFC7950 (5879)
> 
> 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/>