Re: [netmod] example modules in 6087bis
Andy Bierman <andy@yumaworks.com> Tue, 24 January 2017 19:34 UTC
Return-Path: <andy@yumaworks.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 DAA3212968A for <netmod@ietfa.amsl.com>; Tue, 24 Jan 2017 11:34:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.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 JWKwcoBOJ55R for <netmod@ietfa.amsl.com>; Tue, 24 Jan 2017 11:34:14 -0800 (PST)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 D3BE91295D0 for <netmod@ietf.org>; Tue, 24 Jan 2017 11:34:13 -0800 (PST)
Received: by mail-qt0-x230.google.com with SMTP id x49so199449798qtc.2 for <netmod@ietf.org>; Tue, 24 Jan 2017 11:34:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mZYw6KK6hNFTooWRDKhI2X60KRL5u7AtYtcpa23iK94=; b=f1AG9xvxX8tgQIGfmdxIvsrXpfyik22zeXikrUUMBNNfaznPQEIoabkc96M31OzYEw 2T0lCGLV61B8dor69hnLwvb0Mq4dLr7Q4P2NVph1b8PqWQRtqOrw61No/FoKdmbLcit1 Qt5mq87sjauYIBV6zzcJx87GJv6j0RsJoKC7tjWeGhFFIbA3+koBU9+69KIHMq5+tv47 7s+ILhF4Ql3rVc5sMubOly8IcsCNO2TesTSW7mt378y/Jjm+WcjqOXahkABrvZll/nvL D90FLUQpEaMRV4Pm7Ydq6QEHcPOYr6RRixGcMRshLkJ2zF/JDe5/RjNrGclEi89rgZEt 038g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mZYw6KK6hNFTooWRDKhI2X60KRL5u7AtYtcpa23iK94=; b=fJ1xRTLk1MMebDSoKrYvwmidTAwyCF3pMP0GouPhZKvquz+ObFaiSHhRtC/3AbZcRk ZvVq+5MZj7gjaqXj08olh1Z8Y7aIMkblK/qMn2iSL+fro/4rmCeXsdoNZTNVNLJqQ/vg /LA1leyFUMH2B7+et8+kz/LGicvf1k05oDlhY4nRN/8BPFJQ1aA50MhYNwtOqDK6UVYp 5bZ0AfmIGvfNHDX3b2K+H/aPFfREuOR7PdQwnbiE4tpe0JVvm8ZEkbOyhKo/SYyRG/j3 65CWsck+/OtQy1ticy0LQrFYFG+2lTFfou7iWCi+4VvmFbnNretXRs0yxHgUesX238iP 8DoQ==
X-Gm-Message-State: AIkVDXKPm5RPXL0MmNodk25euAgRBhE6xyXoS6oGLEYRd6W8gtsMWddmBIzRnt8odnZlwxigCyt2zUw3jh14Ig==
X-Received: by 10.200.45.177 with SMTP id p46mr28906467qta.240.1485286452822; Tue, 24 Jan 2017 11:34:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.145.66 with HTTP; Tue, 24 Jan 2017 11:34:12 -0800 (PST)
In-Reply-To: <20170124.202630.843995888894291234.mbj@tail-f.com>
References: <CABCOCHRkFwDrQrGqk61nh-3fc+emtJEshdEMqA+G4r2YaKxwdg@mail.gmail.com> <003354d9-841f-37b2-a594-6e9983110984@cisco.com> <093ED4A3-081D-418A-B233-E75148133635@juniper.net> <20170124.202630.843995888894291234.mbj@tail-f.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 24 Jan 2017 11:34:12 -0800
Message-ID: <CABCOCHTeBzZ7u-=U_CuU2WUXwGxRiHj8kVCRuhwFiSSzb2txow@mail.gmail.com>
To: Martin Bjorklund <mbj@tail-f.com>
Content-Type: multipart/alternative; boundary="001a114796e869184d0546dc3302"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/hhvt0EQTYY41HrjJuY-p52AV8wo>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Subject: Re: [netmod] example modules in 6087bis
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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, 24 Jan 2017 19:34:16 -0000
Hi, On Tue, Jan 24, 2017 at 11:26 AM, Martin Bjorklund <mbj@tail-f.com> wrote: > Kent Watsen <kwatsen@juniper.net> wrote: > > Hi Andy, > > > > I think this discussion has come to a head. Please submit an updated > 6087bis as soon as you can. Some comments: > > > > > > 1) on the 3rd line below, should the text clarify that --ietf is only > for IETF modules? Also, how does the MUST here jive with the SHOULD in > Section 4.10? > > > > - MUST use CODE BEGINS for a real module > > - MUST NOT use CODE BEGINS for an example module > > - MUST pass pyang --ietf for a real module > > - MUST pass pyang for example module > > > > > > 2) related to #1, Section 5 says "In general, modules in IETF Standards > Track specifications MUST comply with all syntactic and semantic > requirements of YANG [RFC7950]." > > > > First, what does "In general...MUST" mean? - maybe the > > sentence should start with "Modules in IETF..."? > > > > Second, can we add a statement for non-IETF SDOs that might > > have other conventions/restrictions? Would we recommend > > --strict for starters, until they can add an SDO-specific > > flag (e.g., --<sdo>) to pyang? > > We wouldn't talk about any specific tool; we'd just talk about > compliance with this document. Other SDOs will have to decide on > their own rules, but we can suggest that they use all our rules except > the naming convention for modules and namespaces. > > > I would like the --ietf parameter to be renamed --normative so it is not IETF-specific and it is clear IETF example modules should not use it. Probably too late for that. Agree wrt/ naming conventions. e.g., openconfig uses ALL_CAPS for identityrefs and IETF does not. Andy > > 3) The first paragraph in Section 4.6 isn't clear, how about this? > > > > OLD > > This section contains the module(s) defined by the specification. > > These modules SHOULD be written using the YANG syntax defined in > > [RFC7950]. YANG 1.0 [RFC6020] MAY be used if no YANG 1.1 constructs > > or semantics are needed in the module. > > > > NEW > > This section contains the module(s) defined by the YANG specification. > > These modules SHOULD be written using the YANG 1.1 [RFC7950] syntax; > > YANG 1.0 [RFC6020] syntax MAY be used if no YANG 1.1 constructs > > or semantics are needed in the module. > > > > Note: this reads better, but I wonder, since YANG 1.0 syntax is a > > subset of YANG 1.1 syntax, what is really being said here? - that > > yang-version statement is optional? Or maybe, instead of focusing > > on syntax, the statement should regard the version of YANG used? > > The point is that yang-version 1.1 SHOULD be used, and yang-version 1 > MAY be used. > > > 4) Lastly, picking up on this discussion: > > > > https://www.ietf.org/mail-archive/web/netmod/current/msg17277.html. > > > > can add an Informational reference to RFC 4151 in Section 5.9? > > Maybe something like this: > > > > OLD > > > > The following examples are for non-Standards-Track modules. The > > domain "example.com" SHOULD be used in all namespace URIs for example > > modules. > > > > http://example.com/ns/example-interfaces > > > > http://example.com/ns/example-system > > > > NEW > > > > The following URIs exemplify what might be used by non Standards > > Track modules. Note that the domain "example.com" SHOULD be used > > by example modules in IETF drafts. > > > > Example URIs using URLs per RFC 3986 [RFC3986]: > > > > http://example.com/ns/example-interfaces > > http://example.com/ns/example-system > > > > Example URIs using tags per RFC 4151 [RFC4151]: > > > > tag:example.com,2017:example-interfaces > > tag:example.com,2017:example-system > > I would like to see urn:example:<module-name>, that's what I usually > use here. > > > /martin >
- [netmod] example modules in 6087bis Martin Bjorklund
- Re: [netmod] example modules in 6087bis Andy Bierman
- Re: [netmod] example modules in 6087bis Martin Bjorklund
- Re: [netmod] example modules in 6087bis Benoit Claise
- Re: [netmod] example modules in 6087bis Andy Bierman
- Re: [netmod] example modules in 6087bis Martin Bjorklund
- Re: [netmod] example modules in 6087bis Ladislav Lhotka
- Re: [netmod] example modules in 6087bis Benoit Claise
- Re: [netmod] example modules in 6087bis Kent Watsen
- Re: [netmod] example modules in 6087bis Martin Bjorklund
- Re: [netmod] example modules in 6087bis Andy Bierman
- Re: [netmod] example modules in 6087bis Kent Watsen
- Re: [netmod] example modules in 6087bis Benoit Claise
- Re: [netmod] example modules in 6087bis Martin Bjorklund
- Re: [netmod] example modules in 6087bis Mahesh Jethanandani
- Re: [netmod] example modules in 6087bis-10 t.petch