Re: Gen-Art LC review: draft-ietf-netmod-yang-metadata-04

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Fri, 11 March 2016 17:16 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8F212D9BE; Fri, 11 Mar 2016 09:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 bfzfPtjLbUfv; Fri, 11 Mar 2016 09:16:40 -0800 (PST)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AA3E12D995; Fri, 11 Mar 2016 09:16:39 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id DBD7F1975; Fri, 11 Mar 2016 18:16:37 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id R59nQBzr_BTf; Fri, 11 Mar 2016 18:16:14 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Fri, 11 Mar 2016 18:16:36 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id D87172003D; Fri, 11 Mar 2016 18:16:36 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id N01f7KPIVcKs; Fri, 11 Mar 2016 18:16:35 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 255032003A; Fri, 11 Mar 2016 18:16:35 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 190073A2E0FC; Fri, 11 Mar 2016 18:16:35 +0100 (CET)
Date: Fri, 11 Mar 2016 18:16:35 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "tom p." <daedulus@btconnect.com>
Subject: Re: Gen-Art LC review: draft-ietf-netmod-yang-metadata-04
Message-ID: <20160311171634.GA10970@elstar.local>
Mail-Followup-To: "tom p." <daedulus@btconnect.com>, Ladislav Lhotka <lhotka@nic.cz>, Robert Sparks <rjsparks@nostrum.com>, General Area Review Team <gen-art@ietf.org>, ietf@ietf.org, netmod@ietf.org, draft-ietf-netmod-yang-metadata.all@ietf.org
References: <56D60EF5.7020001@nostrum.com> <m27fhbvb07.fsf@birdie.labs.nic.cz> <56E209E3.4030805@nostrum.com> <415C6558-F5D2-4575-B380-C082171DFA21@nic.cz> <033701d17b91$710ce580$4001a8c0@gateway.2wire.net> <20160311130707.GA10591@elstar.local> <014101d17bb7$2a799de0$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <014101d17bb7$2a799de0$4001a8c0@gateway.2wire.net>
User-Agent: Mutt/1.4.2.3i
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/xBj1MN98fVBGgxIccsfoJbBI0qg>
Cc: draft-ietf-netmod-yang-metadata.all@ietf.org, netmod@ietf.org, General Area Review Team <gen-art@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Mar 2016 17:16:43 -0000

I assume 'An annotation carries a single value.' should be clear
enough. A reference to section 7.6 is actually misleading since
that section deals with many more things that are not applicable
to leafs. But I think we are already done with this.

/js

On Fri, Mar 11, 2016 at 04:39:54PM +0000, tom p. wrote:
> ----- Original Message -----
> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> Sent: Friday, March 11, 2016 1:07 PM
> 
> 
> > On Fri, Mar 11, 2016 at 11:15:28AM +0000, tom p. wrote:
> > > Lada, Robert
> > >
> > > The other angle from which this might be approached is that the I-D
> > > already says
> > >
> > > "   Using the "type" statement, a type is specified for the
> annotation
> > >    value according to the same rules as for YANG "leaf" type. "
> > >
> > > while rfc6020bis says
> > >
> > > "   The "leaf" statement is used to define a scalar variable of a
> > >    particular built-in or derived type."
> > >
> > > so if you know your YANG off by heart, then you will know that
> > > annotations must be scalar.  I agree that the text needs to be
> clearer.
> > > Perhaps,
> > > OLD
> > > "   o  annotations are scalar values and cannot be further
> structured;"
> > > NEW
> > > "Annotations obey the same rules as for a YANG "leaf" type
> [rfc6020bis
> > > s.7.6] and so are limited to scalar variables."
> >
> > There is no 'leaf type' in YANG. YANG has leaf nodes in the schema
> > tree. An annotation is not a node in the schema tree. Perhaps
> > something like this:
> 
> Juergen
> 
> Well, I know, but I was quoting directly from yang-metadata-04 s.3,
> namely
> 
> "Using the "type" statement, a type is specified for the annotation
>    value according to the same rules as for YANG "leaf" type. "
> 
> which is why I gave a reference to s7.6 of RFC6020bis rather than s.7.4.
> 
> Perhaps change s.3 in addition to your change
> 
> OLD
>    Using the "type" statement, a type is specified for the annotation
>    value according to the same rules as for YANG "leaf" type.
> NEW
>    Using the "type" statement, a type is specified for the annotation
>    value according to the same rules as for the type of a YANG
> "leaf"[RFC6020bis s.7.6].
> 
> I do think that that mention of leaf is helpful - as you say, the WG
> agreed to this restriction as opposed to allowing more complex
> annotations and referencing "leaf" for me makes that clearer.
> 
> Tom Petch
> 
> >   An annotation carries a single value. The type substatement, which
> >   must be present, takes as an argument the name of an existing
> >   built-in or derived type and the value of the annotation must match
> >   this type. See Section 7.4 of [RFC6020bis] for details.
> >
> > /js
> >
> 

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