
From nobody Tue Jan  2 00:28:13 2018
Return-Path: <mvasko@cesnet.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9807F1200B9 for <yang-doctors@ietfa.amsl.com>; Tue,  2 Jan 2018 00:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=cesnet.cz
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 GcEk4Fubbb4O for <yang-doctors@ietfa.amsl.com>; Tue,  2 Jan 2018 00:28:08 -0800 (PST)
Received: from kalendar.cesnet.cz (kalendar.cesnet.cz [IPv6:2001:718:1:1f:50:56ff:feee:34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D31B21243FE for <yang-doctors@ietf.org>; Tue,  2 Jan 2018 00:28:07 -0800 (PST)
Received: by kalendar.cesnet.cz (Postfix, from userid 999) id 9324E602DC; Tue,  2 Jan 2018 09:28:04 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=kalendar; t=1514881684; bh=GA/BnW9wilr1fK1bxurYhZsKPVuWwtruHXbikmaTB1o=; h=In-Reply-To:From:Date:Cc:To:Subject; b=CcuPsiqeKyXvhMXukn5m8Ek1ooi06m5Hrmr3Hd0N8K6eQllUV0B00o2+ToTAiNS4r 2C7kNIR/GAfFq75wVfP8iWe0h5w7aCK5CMV3WGxiCCDzZy60jAuZXpddRW+y8HXSAz YMVa6+lAWDiSIAh4WsThhV5wXguw1CATuv1DaF5M=
Content-Type: text/plain; charset="utf-8"
In-Reply-To: <CABCOCHTtwwjw_uAPLCrnn7Cj+NVVCNjyuNUYTjg_qTXidtCmSw@mail.gmail.com>
From: =?utf-8?q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>
X-Forward: 2001:67c:1220:80c:f5:8e35:ef0e:146c
Date: Tue, 02 Jan 2018 09:28:04 +0100
Cc: "Ladislav Lhotka" <lhotka@nic.cz>, "Martin Bjorklund" <mbj@tail-f.com>, "Mahesh Jethanandani" <mjethanandani@gmail.com>, "YANG Doctors" <yang-doctors@ietf.org>
To: "Andy Bierman" <andy@yumaworks.com>
MIME-Version: 1.0
Message-ID: <923-5a4b4280-29-4f262000@198821908>
User-Agent: SOGoMail 2.3.23
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/HI5zJdMreQtvmllnl72EPn6LyAw>
Subject: Re: [yang-doctors] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyBG?= =?utf-8?q?wd=3A_Re=3A_Issue_with_ietf-dslite=402017-11-15=2Eyang__and_yan?= =?utf-8?q?gdump-pro?=
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 08:28:11 -0000

Hello everyone,

we would like to clarify a few things from this discussion. We are disp=
laying some warnings in case of some almost-certainly invalid XPath exp=
ressions so we were wondering if it makes sense to add another if we de=
tect an equality comparison of an identityref and an identity name with=
out the use of derived-from(-or-self)() functions.

Another issue, "local module" has no formal definition as was mentioned=
. One can infer it is the module where the statement in question is def=
ined but a definition would be appreciated. The same problem is with th=
e term "current module" which it seems can be used interchangeably. Las=
tly, "current node" has no definition either and so we assumed it to be=
 the node returned by the function current().

Kind regards,
Michal

On Monday, December 25, 2017 20:14 CET, Andy Bierman <andy@yumaworks.co=
m> wrote: 
 
> On Mon, Dec 25, 2017 at 10:53 AM, Ladislav Lhotka <lhotka@nic.cz> wro=
te:
> 
> > On Sun, 2017-12-24 at 18:54 -0300, Mahesh Jethanandani wrote:
> > > > On Dec 23, 2017, at 10:49 AM, Martin Bjorklund <mbj@tail-f.com>=
 wrote:
> > > >
> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > On Sat, 2017-12-23 at 13:01 +0100, Martin Bjorklund wrote:=

> > > > > > Andy Bierman <andy@yumaworks.com> wrote:
> > > > > > > > On Sat, Dec 23, 2017 at 2:21 AM, Martin Bjorklund <
> > mbj@tail-f.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > See section 9.10.3 in RFC 7950:
> > > > > > > >
> > > > > > > >   The string value of a node of type "identityref" in a=
 "must"
> > or
> > > > > > > >   "when" XPath expression is the referred identity's qu=
alified
> > name
> > > > > > > >   with the prefix present.
> > > > > > > >
> > > > > > > > and re. the prefix:
> > > > > > > >
> > > > > > > >   If the referred identity is defined in an
> > > > > > > >   imported module, the prefix in the string value is th=
e prefix
> > > > > > > > defined
> > > > > > > >   in the corresponding "import" statement.  Otherwise, =
the
> > prefix in
> > > > > > > >   the string value is the prefix for the current module=
.
> > > > > > > >
> > > > > > > >
> > > > > > > > I most cases you should consider using derived-from-or-=
self
> > instead
> > > > > > > > of
> > > > > > > > equality test for identiyrefs.
> > > > > > >
> > > > > > > So what is "the current module"?
> > > > > > > What is the resolution of 'X'? Is it foo:X or bar:X?
> > > > > >
> > > > > > foo:X
> > > > >
> > > > > No, the resolution of 'X' is 'X'
> > > >
> > > > Yes!  Sorry, I misread the question.  I though the question was=
 what
> > > > prefix should be used.
> > >
> > > The question started with a 'when' statement (which I understand =
should
> > be
> > > changed to 'derived-from') using a identity name that is defined =
in the
> > other
> > > (bar) module. Should the 'derived-from' statement reference the i=
dentity
> > using
> > > the prefix 'b:X' or just 'X', using Andy's example?
> >
> > Both are possible in Andy's example, the former refers to the ident=
ity "X"
> > defined in module "bar", the latter refers to the identity "X" defi=
ned in
> > the
> > local module ("foo").
> >
> >
> I see the term "local module" used 11 times in RFC 7950, but it is no=
t
> defined anywhere.
> IMO the only intuitive solution is that all scoped names are resolved=
 in
> the same module,
> which is the module defining the actual statements. Is that the local=

> module?
> 
> 
> Lada
> >
> 
> 
> Andy
> 
> 
> >
> > >
> > > >
> > > >
> > > > /martin
> > > >
> > > >
> > > > > because it is an XPath 1.0 string and XPath
> > > > > knows nothing about YANG identities. Because of the rule of s=
ec.
> > 9.10.3,
> > > > > the
> > > > > equality expression is always false.
> > > > >
> > > > > That's why we introduced the new XPath functions derived-from=
() and
> > > > > derived-
> > > > > from-or-self() in YANG 1.1.
> > > > >
> > > > > Lada
> > > > >
> > > > > >
> > > > > >
> > > > > > /martin
> > > > > >
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > /martin
> > > > > > >
> > > > > > > Andy
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Andy Bierman <andy@yumaworks.com> wrote:
> > > > > > > > > > On Fri, Dec 15, 2017 at 4:38 AM, Radek Krej=C4=8D=C3=
=AD <
> > rkrejci@cesnet.cz
> > > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Hi,
> > > > > > > > > > I'm adding Michal Vasko to cc, he knows better how =
these
> > things
> > > > > > > > > > are
> > > > > > > > > > checked in libyang.
> > > > > > > > > >
> > > > > > > > > > It seems to me that Andy refers the text which does=
 not
> > apply
> > > > > > > > > > here.
> > > > > > > > > > The
> > > > > > > > > > identity name was used as part of XPath expresion
> > (when-stmt),
> > > > > > > > > > so the
> > > > > > > > > > definition of the context nodes for the when-stmt (=
RFC
> > 7950, sec
> > > > > > > >
> > > > > > > > 7.21.5)
> > > > > > > > > > and XPath context rules should apply here. Not the =
rules
> > for the
> > > > > > > > > > identityref's base statement. In this case, the whe=
n-stmt
> > is in
> > > > > > > >
> > > > > > > > augment so
> > > > > > > > > > the context node (which we also understand as the c=
urrent
> > node
> > > > > > > > > > in this
> > > > > > > > > > case) is the augment's target node. And according t=
o XPath
> > > > > > > > > > context
> > > > > > > >
> > > > > > > > rules
> > > > > > > > > > (RFC 7950, sec 6.4.1):
> > > > > > > > > >
> > > > > > > > > > o  Names without a namespace prefix belong to the s=
ame
> > namespace
> > > > > > > > > > as
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > identifier of the current node.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I cc:ed YANG doctors to get more opinions...
> > > > > > > > >
> > > > > > > > > The current node is the augment-stmt.
> > > > > > > > > Note that it does not say context node, which is the =
target
> > of the
> > > > > > > >
> > > > > > > > augment.
> > > > > > > > > I think prefixes (and default prefix) are resolved in=
 the
> > module
> > > > > > > >
> > > > > > > > containing
> > > > > > > > > the statement.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > module foo {
> > > > > > > > >
> > > > > > > > >   import bar { prefix b; }
> > > > > > > > >   identity X;
> > > > > > > > >
> > > > > > > > >   augment b:/some-node {
> > > > > > > > >      leaf test {
> > > > > > > > >         type string;
> > > > > > > > >         when "/b:some-node/b:other-node =3D 'X'";
> > > > > > > > >      }
> > > > > > > > >   }
> > > > > > > > > }
> > > > > > > > >
> > > > > > > > > module bar {
> > > > > > > > >
> > > > > > > > >   identity W;
> > > > > > > > >   identity X { base W; }
> > > > > > > > >   container some-node {
> > > > > > > > >       leaf other-node {
> > > > > > > > >         type identityref { base W; }
> > > > > > > > >       }
> > > > > > > > >   }
> > > > > > > > > }
> > > > > > > > >
> > > > > > > > > Q) Does other-node =3D 'X' resolve to foo:X or bar:X?=
  IMO:
> > foo:X
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Andy
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > In this particular case, the augment node with the=

> > when-stmt
> > > > > > > > > > augments
> > > > > > > >
> > > > > > > > the
> > > > > > > > > > same module which defines napt44, so they are in th=
e
> > correct
> > > > > > > > > > namespace
> > > > > > > >
> > > > > > > > and
> > > > > > > > > > the identity name can be used without the prefix. S=
o it
> > should
> > > > > > > > > > be
> > > > > > > > > > fine,
> > > > > > > > > > while I believe that using prefix in the cases of
> > identities is
> > > > > > > > > > always
> > > > > > > > > > better approach. From the first sight (it may be
> > challenging for
> > > > > > > > > > human
> > > > > > > >
> > > > > > > > to
> > > > > > > > > > correctly resolve the context/current node in some =
cases),
> > I
> > > > > > > > > > would
> > > > > > > > > > also
> > > > > > > > > > expect prefix.
> > > > > > > > > >
> > > > > > > > > > I propose to keep the change in the draft (added na=
t
> > prefix),
> > > > > > > > > > since it
> > > > > > > > > > improves readability of the expression. But I don't=
 think
> > that
> > > > > > > > > > it is
> > > > > > > > > > an
> > > > > > > > > > error to ommit the prefix.
> > > > > > > > > >
> > > > > > > > > > Regards,
> > > > > > > > > > Radek
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Dne 19.11.2017 v 20:42 Benoit Claise napsal(a):
> > > > > > > > > > > Hi Radek,
> > > > > > > > > > >
> > > > > > > > > > > Here is a bug report for you.
> > > > > > > > > > >
> > > > > > > > > > > Regards, Benoit
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > -------- Forwarded Message --------
> > > > > > > > > > > Subject:      Re: Issue with ietf-dslite@2017-11-=
15.yang
> > and
> > > > > > > > > >
> > > > > > > > > > yangdump-pro
> > > > > > > > > > > Date:         Sat, 18 Nov 2017 13:22:58 -0800
> > > > > > > > > > > From:         Andy Bierman <andy@yumaworks.com>
> > > > > > > > > > > To:   Benoit Claise <bclaise@cisco.com>
> > > > > > > > > > > CC:   draft-ietf-softwire-dslite-yang@ietf.org <=

> > > > > > > > > >
> > > > > > > > > > draft-ietf-softwire-dslite-yang@ietf.org>, Mahesh
> > Jethanandani <
> > > > > > > > > > mjethanandani@gmail.com>
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Hi,
> > > > > > > > > > >
> > > > > > > > > > > yangdump-pro is correct. Every other compiler mis=
sed
> > it...
> > > > > > > > > > >
> > > > > > > > > > > 9.10.2.  The identityref's "base" Statement
> > > > > > > > > > >
> > > > > > > > > > >   The "base" statement, which is a substatement t=
o the
> > "type"
> > > > > > > > > > >   statement, MUST be present at least once if the=
 type is
> > > > > > > > > > >   "identityref".  The argument is the name of an=

> > identity, as
> > > > > > > >
> > > > > > > > defined
> > > > > > > > > > >   by an "identity" statement.  If a prefix is pre=
sent on
> > the
> > > > > > > >
> > > > > > > > identity
> > > > > > > > > > >   name, it refers to an identity defined in the m=
odule
> > that
> > > > > > > > > > > was
> > > > > > > > > > >   imported with that prefix.  *Otherwise, an iden=
tity
> > with the
> > > > > > > >
> > > > > > > > matching
> > > > > > > > > > name MUST be defined in the current module or an in=
cluded
> > > > > > > > > > submodule.*
> > > > > > > > > > >
> > > > > > > > > > > Using ietf-dslite@2017-11-15.yang and
> > ietf-nat@2017-11-15.yang
> > > > > > > > > > >
> > > > > > > > > > > When I change 'natp44' to 'nat:natp44' in both
> > when-stmts:
> > > > > > > > > > >
> > > > > > > > > > > andy@andy-homedev:~/Desktop/FD1289/IETF$ yangdump=
-pro
> > > > > > > > > >
> > > > > > > > > > ietf-dslite@2017-11-15.yang modpath=3D.
> > > > > > > > > > >
> > > > > > > > > > > *** /home/andy/Desktop/FD1289/
> > IETF/ietf-dslite@2017-11-15.yang
> > > > > > > > > > > *** 0 Errors, 0 Warnings
> > > > > > > > > > >
> > > > > > > > > > > andy@andy-homedev:~/Desktop/FD1289/IETF$
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Andy
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Sat, Nov 18, 2017 at 11:07 AM, Benoit Claise
> > <bclaise@cisco
> > > > > > > > > > > .com
> > > > > > > > > >
> > > > > > > > > > <mailto:bclaise@cisco.com>> wrote:
> > > > > > > > > > >
> > > > > > > > > > >    Hi Andy,
> > > > > > > > > > >
> > > > > > > > > > >    Can you please have a look at
> > ietf-dslite@2017-11-15.yang
> > > > > > > > > > > at
> > > > > > > > > >
> > > > > > > > > > http://www.claise.be/IETFYANGPageCompilation.html <=

> > > > > > > >
> > > > > > > > http://www.claise.be/
> > > > > > > > > > IETFYANGPageCompilation.html> .
> > > > > > > > > > >    yangdump-pro reports a new error, while the ot=
her
> > > > > > > > > > > validators are
> > > > > > > > > >
> > > > > > > > > > fine.
> > > > > > > > > > >
> > > > > > > > > > >    Copying Mahesh, as YANG doctor.
> > > > > > > > > > >
> > > > > > > > > > >    Regards, Benoit
> > > > > >
> > > > > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F
> > > > > > yang-doctors mailing list
> > > > > > yang-doctors@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > > > >
> > > > > --
> > > > > Ladislav Lhotka
> > > > > Head, CZ.NIC Labs
> > > > > PGP Key ID: 0xB8F92B08A9F76C67
> > > >
> > > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F
> > > > yang-doctors mailing list
> > > > yang-doctors@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > --
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> >
> > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=

> > yang-doctors mailing list
> > yang-doctors@ietf.org
> > https://www.ietf.org/mailman/listinfo/yang-doctors
> >
 
 


From nobody Tue Jan  2 10:19:22 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28CF12D7EA; Tue,  2 Jan 2018 10:19:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 vRMGUyvEkHkY; Tue,  2 Jan 2018 10:19:12 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4BF124B17; Tue,  2 Jan 2018 10:19:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22001; q=dns/txt; s=iport; t=1514917151; x=1516126751; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=51nw2j9aDW7HslWkuFzH3xpj3AdAwOtgmvv4jQsudSw=; b=RKRGnGqmF0wwv+Mbb79QSgYv8oCOEvW4wknUWMgZurqFnDQVAO29OnGm L4FsiAz+ZvonmsPAt+kEBWJvt4B4GyoZ2ovsSgONQBp7V3Cbs9v+n45na joGmrogmI6krzcTbP/0hXyS1/ufNZHjlt2fJOIk36/NJEcKM68eZe8JpX s=;
X-IronPort-AV: E=Sophos;i="5.45,498,1508803200"; d="scan'208,217";a="1222475"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2018 18:19:08 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w02IJ848020393; Tue, 2 Jan 2018 18:19:08 GMT
To: =?UTF-8?B?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>, yang-doctors@ietf.org
Cc: draft-ietf-pim-yang.all@ietf.org, ietf@ietf.org, pim@ietf.org, "bfd-chairs@ietf.org" <netmod-chairs@ietf.org>, Alia Atlas <akatlas@gmail.com>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>
References: <151380493227.2629.15496937140050941194@ietfa.amsl.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <1f41bfe5-65f5-3db4-2283-506e947722f9@cisco.com>
Date: Tue, 2 Jan 2018 19:19:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <151380493227.2629.15496937140050941194@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------F04A5FE119F91450D7C7D0A6"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/7kErwkHs4ylykBG249uQm5AJvZg>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-pim-yang-12
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 18:19:15 -0000

This is a multi-part message in MIME format.
--------------F04A5FE119F91450D7C7D0A6
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi JÃ¼rgen,
> Reviewer: JÃ¼rgen SchÃ¶nwÃ¤lder
> Review result: Almost Ready
>
> * General YANG Review Remarks
>
>    This document depends on a number of other I-Ds. Is it safe to
>    process this document while the other documents this document
>    depends on are not yet through the process? Who is tracking things
>    and making sure that any changes in other documents that may impact
>    the PIM document are detected and handled appropriately before
>    publication?
I do look at the YANG module dependencies, thanks to tooling.
Let's look at the draft-ietf-pim-yang-12 dependencies:

    https://www.yangcatalog.org/yang-search/impact_analysis.php?modules[]=ietf-pim-dm@2017-12-08.yang&modules[]=ietf-pim-sm@2017-12-08.yang&modules[]=ietf-pim-base@2017-12-08.yang&modules[]=ietf-pim-bidir@2017-12-08.yang&modules[]=ietf-pim-rp@2017-12-08.yang&recurse=2&rfcs=1&show_subm=1&show_dir=dependencies

[I-D.ietf-rtgwg-routing-types] is RFC 8294. We will update the tool.
[I-D.ietf-netmod-rfc7223bis] is on the Jan 11th IESG telechat.
[I-D.ietf-netmod-rfc8022bis] is in IETF LC now and on the Jan 25th IESG 
telechat
The only unknown to me is the state of [I-D.ietf-bfd-yang]. Copying Alia 
and the BFD chairs.

In terms of I-D normative references, 
https://tools.ietf.org/html/draft-ietf-pim-yang-12#section-9.1, there is 
an extra related one:
 Â Â Â  [I-D.ietf-netmod-revised-datastores] is on the Jan 11th IESG telechat

So we're getting there...

Regards, Benoit
>
>    It is generally good style to write complete sentences in
>    description statements. Some of the description statements are just
>    fractions of a sentence.
>
>    I think we do not recommend anymore to list WG chairs in the contact
>    statement.
>
>    It is sometimes not clear why you define groupings that are only
>    used once (and sometimes are likely not reusable since they contain
>    relative paths in must expressions).
>
> * Introduction
>
>    - Is there a reason why you refer to RFC 6020 and to RFC 7950 in
>      sections 1 and 1.2? Why do you need the reference to RFC 6020?
>
>    - What are 'wider' management interfaces? If you mention NETCONF,
>      why not mention RESTCONF?
>
>    - s/Protocol-Independent Multicast (PIM) devices
>       /devices supporting Protocol-Independent Multicast (PIM)/
>
>    - So which YANG terminology applies, RFC 6020 or RFC 7950? I
>      personally think using YANG 1.1 is pretty safe these days.
>
> * Design of Data Model
>
>    - I did not really understand Section 2.5. It seems you are
>      duplicating objects for different address families but on some
>      systems these duplicate objects must have the same value. If so,
>      where would the must expression go and how does an implementation
>      add such a must expression? How many of such must expressions
>      would there have to be? Did you consider having address family
>      independent objects and optionally (controlled by a feature) per
>      address family objects that overwrite the independent settings?
>
> * Module Structure
>
>    - s/is included/is imported/
>
>    - The tree diagrams are rather long. It would likely help readers if
>      the diagram would be split into meaningful units and additional
>      text added to describe the units.
>
>      Are lists of the form
>
>            |  +--rw ipv4-rp* [ipv4-address]
>            |  |  +--rw ipv4-address    inet:ipv4-address
>
>      designed for exensibility? Otherwise, this may be collapsed into
>      a simple leaf-list.
>
>    - Since I am not familiar with details of PIM, I can't comment on
>      the question whether the model makes sense or not.
>
> * PIM base Module
>
>    - YANG modules compile cleanly according to the tracker page.
>
>    - As said above, consider using YANG 1.1. The ietf-routing module
>      actually uses YANG 1.1 so you will need a YANG 1.1 compiler
>      anyway.
>
>    - Consider adding reference statements to the feature definitions
>      in case a feature is described in a protocol specification.
>
>    - The value of timer-value is not really clear, you could have used
>      rt-types:timer-value-seconds16 directly.
>
>    - Why is graceful-restart/duration using an ad-hoc type for 16-bit
>      seconds and not timer-value? Is it because infinity and not-set
>      does not apply?
>
>    - Does a bfd/hello-interval of 'infinity' or 'not-set' make sense?
>
>    - More explicit description of bfd/hello-holdtime? Is a choice
>      really appropriate (hello-holdtime-or-multiplier)? Can I not have
>      both holdtime and multiplier? Perhaps I am just not clear what
>      holdtime does...
>
>    - Does a bfd/jp-interval of 'infinity' or 'not-set' make sense?
>
>    - More explicit description of bfd/jp-holdtime? Is a choice really
>      appropriate (jp-holdtime-or-multiplier)? Can I not have both
>      holdtime and multiplier? Perhaps I am just not clear what holdtime
>      does...
>
>    - Please provide more meaningful descriptions:
>
>           description "Propagation description";
>           description "Override interval";
>
>    - What is the meaning of the interface augmentation 'oper-status'
>      relative to 'oper-status' defined by ietf-interfaces? Is this just
>      a duplicate with fewer states? Or is this somehow more specific to
>      multicast or PIM packets? In the later case, I think this deserves
>      to the be explained in the description clause.
>
>    - How do the ip4 and ipv6 addresses relate to ip addresses assigned
>      to an interface in ietf-ip?
>
>    - What is the meaning of hello-expiration 'not-set'?
>
>    - What is the meaning of expiration 'not-set'?
>
>    - Is it useful to return the uptime in seconds (which is changing on
>      every get that is not in the same second) or could it be an option
>      to report the time when something transitioned into the up state
>      (which is not changing)? Well, it could be that we are simply used
>      to uptime like objects. Anyway, the description of up-time should
>      make it clear what exactly is defining the state 'up'. If this
>      says up for 5 seconds, what exactly transitioned into an 'up'
>      state 5 seconds ago?
>
>    - Is the any restriction for dr-priority or is it a full 32-bit
>      unsigned number space? In some vendor documentation I saw 0..65535
>      with a default of 1. What do RFCs say?
>
>    - I am not sure what the precise meaning of the error statistic
>      counters are. What turns an received or sent messages into an
>      error message? The description of grouping statistics-error does
>      not explain this. Also, if I receive a hello and I later decide
>      that this hello must have been an error, is this hello counted
>      twice? And what about messages that could not be parsed because
>      they were malformed, where are those counted?
>
>    - Why is 'pim' a presence container?
>
>    - Do comments like 'configuration data nodes' make sense if you
>      include config false nodes in the same branch of the tree?
>
> * PIM RP Module
>
>    - Does the feature bsr-election-state depend on the feature bsr?
>
>    - Should there be a default bsr-candidate/priority?
>
>    - Do you need the address/hash-mask-length/priority in
>      bsr-state-attributes in an NMDA implementation?
>
>    - I _assume_ the bsr-next-bootstrap value has to be interpreted
>      relative to the time the value was obtained. What about making
>      this an absolute timestamp instead? Well, actually I am not sure
>      what the value represents - is it the remaining time interval
>      until the next bootstrap will be sent?
>
>    - I have no clue what to expect here:
>
>           leaf group-policy {
>             type string;
>             description "Group policy.";
>           }
>
>       What can I expect the string to contain?
>
>     - I am again uncertain how exactly to understand the value of
>       rp-candidate-next-advertisement, see similar questions above.
>
>     - What are the policy values that can go into this:
>
>         leaf policy-name {
>           type string;
>           description
>             "Static RP policy.";
>         }
>
>       Is the string just an arbitrary name or does it mean something?
>
>     - How is this supposed to be used?
>
>         leaf policy {
>           type string;
>           description
>             "ACL (Access Control List) policy used to filter group
>              addresses.";
>         }
>
>       What is the meaning of <policy>foo</policy>?
>
> * PIM SM Module
>
>    - What is the meaning of a policy-name value?
>
>                 leaf policy-name {
>                   if-feature spt-switch-policy;
>                   type string;
>                   description
>                     "Switch policy.";
>                 }
>
>    - What is the meaning of a range-policy value?
>
>             leaf range-policy {
>               type string;
>               description
>                 "Policy used to define SSM address range.";
>             }
>
> * PIM DM Module
>
>    - I wonder, would you need an identity for dense mode?
>
> * PIM BIDIR Module
>
>    - Remove
>
>       /*
>        * Typedefs
>        */
>
>    - What is the meaning of offer-interval or backoff-interval
>      'not-set'?
>
> * Implementation Status
>
>    It seems the trac page pointed to was used to collect information
>    about what proprietary implementation support, i.e., it does not
>    document to what extend the models defined in this document have
>    been implemented. There are some notable differences. For example,
>    it seems most counters implemented are 32-bit while most counters in
>    the YANG models are 64-bit. How chatty is PIM, are 64-bit counters
>    really needed and are implementors willing to move to 64-bit
>    counters?
>
> * Security Considerations
>
>    I think this needs to include a bit more details. See
>
>    https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
>
>    for the latest template that YANG module authors are expected to
>    use.
>
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors


--------------F04A5FE119F91450D7C7D0A6
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi JÃ¼rgen,<br>
    </div>
    <blockquote type="cite"
      cite="mid:151380493227.2629.15496937140050941194@ietfa.amsl.com">
      <pre wrap="">Reviewer: JÃ¼rgen SchÃ¶nwÃ¤lder
Review result: Almost Ready

* General YANG Review Remarks

  This document depends on a number of other I-Ds. Is it safe to
  process this document while the other documents this document
  depends on are not yet through the process? Who is tracking things
  and making sure that any changes in other documents that may impact
  the PIM document are detected and handled appropriately before
  publication?</pre>
    </blockquote>
    I do look at the YANG module dependencies, thanks to tooling.<br>
    Let's look at the draft-ietf-pim-yang-12 dependencies:<br>
    <blockquote><a class="moz-txt-link-freetext" href="https://www.yangcatalog.org/yang-search/impact_analysis.php?modules">https://www.yangcatalog.org/yang-search/impact_analysis.php?modules</a>[]=ietf-pim-dm@2017-12-08.yang&amp;modules[]=ietf-pim-sm@2017-12-08.yang&amp;modules[]=ietf-pim-base@2017-12-08.yang&amp;modules[]=ietf-pim-bidir@2017-12-08.yang&amp;modules[]=ietf-pim-rp@2017-12-08.yang&amp;recurse=2&amp;rfcs=1&amp;show_subm=1&amp;show_dir=dependencies<br>
    </blockquote>
    [I-D.ietf-rtgwg-routing-types] is RFC 8294. We will update the tool.<br>
    [I-D.ietf-netmod-rfc7223bis] is on the Jan 11th IESG telechat.<br>
    [I-D.ietf-netmod-rfc8022bis] is in IETF LC now and on the Jan 25th
    IESG telechat<br>
    The only unknown to me is the state of [I-D.ietf-bfd-yang]. Copying
    Alia and the BFD chairs.<br>
    <br>
    In terms of I-D normative references,
    <a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-pim-yang-12#section-9.1">https://tools.ietf.org/html/draft-ietf-pim-yang-12#section-9.1</a>,
    there is an extra related one:<br>
    Â Â Â  [I-D.ietf-netmod-revised-datastores] is on the Jan 11th IESG
    telechat<br>
    <br>
    So we're getting there...<br>
    <br>
    Regards, Benoit<br>
    <blockquote type="cite"
      cite="mid:151380493227.2629.15496937140050941194@ietfa.amsl.com">
      <pre wrap="">

  It is generally good style to write complete sentences in
  description statements. Some of the description statements are just
  fractions of a sentence.

  I think we do not recommend anymore to list WG chairs in the contact
  statement.

  It is sometimes not clear why you define groupings that are only
  used once (and sometimes are likely not reusable since they contain
  relative paths in must expressions).

* Introduction

  - Is there a reason why you refer to RFC 6020 and to RFC 7950 in
    sections 1 and 1.2? Why do you need the reference to RFC 6020?

  - What are 'wider' management interfaces? If you mention NETCONF,
    why not mention RESTCONF?

  - s/Protocol-Independent Multicast (PIM) devices
     /devices supporting Protocol-Independent Multicast (PIM)/

  - So which YANG terminology applies, RFC 6020 or RFC 7950? I
    personally think using YANG 1.1 is pretty safe these days.

* Design of Data Model

  - I did not really understand Section 2.5. It seems you are
    duplicating objects for different address families but on some
    systems these duplicate objects must have the same value. If so,
    where would the must expression go and how does an implementation
    add such a must expression? How many of such must expressions
    would there have to be? Did you consider having address family
    independent objects and optionally (controlled by a feature) per
    address family objects that overwrite the independent settings?

* Module Structure

  - s/is included/is imported/

  - The tree diagrams are rather long. It would likely help readers if
    the diagram would be split into meaningful units and additional
    text added to describe the units.

    Are lists of the form

          |  +--rw ipv4-rp* [ipv4-address]
          |  |  +--rw ipv4-address    inet:ipv4-address

    designed for exensibility? Otherwise, this may be collapsed into
    a simple leaf-list.

  - Since I am not familiar with details of PIM, I can't comment on
    the question whether the model makes sense or not.

* PIM base Module

  - YANG modules compile cleanly according to the tracker page.

  - As said above, consider using YANG 1.1. The ietf-routing module
    actually uses YANG 1.1 so you will need a YANG 1.1 compiler
    anyway.

  - Consider adding reference statements to the feature definitions
    in case a feature is described in a protocol specification.

  - The value of timer-value is not really clear, you could have used
    rt-types:timer-value-seconds16 directly.

  - Why is graceful-restart/duration using an ad-hoc type for 16-bit
    seconds and not timer-value? Is it because infinity and not-set
    does not apply?

  - Does a bfd/hello-interval of 'infinity' or 'not-set' make sense?

  - More explicit description of bfd/hello-holdtime? Is a choice
    really appropriate (hello-holdtime-or-multiplier)? Can I not have
    both holdtime and multiplier? Perhaps I am just not clear what
    holdtime does...

  - Does a bfd/jp-interval of 'infinity' or 'not-set' make sense?

  - More explicit description of bfd/jp-holdtime? Is a choice really
    appropriate (jp-holdtime-or-multiplier)? Can I not have both
    holdtime and multiplier? Perhaps I am just not clear what holdtime
    does...

  - Please provide more meaningful descriptions:

         description "Propagation description";
         description "Override interval";

  - What is the meaning of the interface augmentation 'oper-status'
    relative to 'oper-status' defined by ietf-interfaces? Is this just
    a duplicate with fewer states? Or is this somehow more specific to
    multicast or PIM packets? In the later case, I think this deserves
    to the be explained in the description clause.

  - How do the ip4 and ipv6 addresses relate to ip addresses assigned
    to an interface in ietf-ip?

  - What is the meaning of hello-expiration 'not-set'?

  - What is the meaning of expiration 'not-set'?

  - Is it useful to return the uptime in seconds (which is changing on
    every get that is not in the same second) or could it be an option
    to report the time when something transitioned into the up state
    (which is not changing)? Well, it could be that we are simply used
    to uptime like objects. Anyway, the description of up-time should
    make it clear what exactly is defining the state 'up'. If this
    says up for 5 seconds, what exactly transitioned into an 'up'
    state 5 seconds ago?

  - Is the any restriction for dr-priority or is it a full 32-bit
    unsigned number space? In some vendor documentation I saw 0..65535
    with a default of 1. What do RFCs say?

  - I am not sure what the precise meaning of the error statistic
    counters are. What turns an received or sent messages into an
    error message? The description of grouping statistics-error does
    not explain this. Also, if I receive a hello and I later decide
    that this hello must have been an error, is this hello counted
    twice? And what about messages that could not be parsed because
    they were malformed, where are those counted?

  - Why is 'pim' a presence container?

  - Do comments like 'configuration data nodes' make sense if you
    include config false nodes in the same branch of the tree?

* PIM RP Module

  - Does the feature bsr-election-state depend on the feature bsr?

  - Should there be a default bsr-candidate/priority?

  - Do you need the address/hash-mask-length/priority in
    bsr-state-attributes in an NMDA implementation?

  - I _assume_ the bsr-next-bootstrap value has to be interpreted
    relative to the time the value was obtained. What about making
    this an absolute timestamp instead? Well, actually I am not sure
    what the value represents - is it the remaining time interval
    until the next bootstrap will be sent?

  - I have no clue what to expect here:

         leaf group-policy {
           type string;
           description "Group policy.";
         }

     What can I expect the string to contain?

   - I am again uncertain how exactly to understand the value of
     rp-candidate-next-advertisement, see similar questions above.

   - What are the policy values that can go into this:

       leaf policy-name {
         type string;
         description
           "Static RP policy.";
       }

     Is the string just an arbitrary name or does it mean something?

   - How is this supposed to be used?

       leaf policy {
         type string;
         description
           "ACL (Access Control List) policy used to filter group
            addresses.";
       }

     What is the meaning of &lt;policy&gt;foo&lt;/policy&gt;?

* PIM SM Module

  - What is the meaning of a policy-name value?

               leaf policy-name {
                 if-feature spt-switch-policy;
                 type string;
                 description
                   "Switch policy.";
               }

  - What is the meaning of a range-policy value?

           leaf range-policy {
             type string;
             description
               "Policy used to define SSM address range.";
           }

* PIM DM Module

  - I wonder, would you need an identity for dense mode?

* PIM BIDIR Module

  - Remove

     /*
      * Typedefs
      */

  - What is the meaning of offer-interval or backoff-interval
    'not-set'?

* Implementation Status

  It seems the trac page pointed to was used to collect information
  about what proprietary implementation support, i.e., it does not
  document to what extend the models defined in this document have
  been implemented. There are some notable differences. For example,
  it seems most counters implemented are 32-bit while most counters in
  the YANG models are 64-bit. How chatty is PIM, are 64-bit counters
  really needed and are implementors willing to move to 64-bit
  counters?

* Security Considerations

  I think this needs to include a bit more details. See

  <a class="moz-txt-link-freetext" href="https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines">https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines</a>

  for the latest template that YANG module authors are expected to
  use.


_______________________________________________
yang-doctors mailing list
<a class="moz-txt-link-abbreviated" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/yang-doctors">https://www.ietf.org/mailman/listinfo/yang-doctors</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------F04A5FE119F91450D7C7D0A6--


From nobody Tue Jan  2 13:22:40 2018
Return-Path: <mjethanandani@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90C3D126CBF; Tue,  2 Jan 2018 13:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7dUh44ZuLm4x; Tue,  2 Jan 2018 13:22:27 -0800 (PST)
Received: from mail-pl0-x22d.google.com (mail-pl0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) (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 EC71F120726; Tue,  2 Jan 2018 13:22:26 -0800 (PST)
Received: by mail-pl0-x22d.google.com with SMTP id z5so29400290plo.10; Tue, 02 Jan 2018 13:22:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lM9ug6zjY6X9PZKvHi9M9c0Fnr+93/sThqgITeSIiRQ=; b=ZqHxFVFnp8Ficqqz45DR80XhK8goLSxcrQmS0WX496nlTAJEet9CmDZ0RxGwe0jYFs 73VZNt0AQASJ+HGEPB/jZJ9yohvyi6qL2YsEY7tVGu7SOgIluFCI6UCd5/jcvK9reI4E 8uX70PqmDEZ90NwhUc4CwUGtwkVPY5FV07yjEeJ21AKzaQLLx6Anavb/X4Ys8jkVPIuL AIw35ZNUCPBKtbQUjaXUQ8C8nUIrh3xjYLa3hp/YAuHqgYZPvOw8AqusB4hfPTenyzah 5RufnkEQbSq7OyciSEQKhzG6thoLeiQ7UyvHZ826u2TuAX/7IXDk65wmAuocakJb5TVl BF2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=lM9ug6zjY6X9PZKvHi9M9c0Fnr+93/sThqgITeSIiRQ=; b=Okiyq7LFo7ReHJ+JBVRROU4A0xP4xvm5Z9iVxRsuZdKjbeZFTKdkckkFG2V3iV00f8 vjRTxcmooiTq1cqdPPGnf62KFghUpUfCmZ8DFCYvEIuDEd2loQADebbsO/BZgQ8gbtIz hOmNGQz0e/qZ5pdsAFTbbpJEfBCccKsgfQ3p7Wy7qhTtwDw0BInlx3PRQ/sLwatGZ/E2 GoEHU7dZy3Ggc2YHV/+5pMt2/4xYkdfYe+infMqVOt0ajjVf2pOZueZkQBkUL3eprj7m v8rycQ8bCHGbpGfdEU3A1ADIykttE9xG//oB/ZLhCcclTayBNc1e0uJIuzbFEjU9cvk3 Sr0Q==
X-Gm-Message-State: AKGB3mIl7H0gd4LD6ufzLjjIkaxFxg5KUKj7i5ikY/4nXZ9kdf8mYKrY WOvNeVNK0mvZCNvjHq4pqSCvhJic
X-Google-Smtp-Source: ACJfBot/7ltCCkddybyh6AmCuhbh4oP+eSW2kgFQVSdz5W80T2xZzx9GAjbKHBOeTe8/hbEl5grPdA==
X-Received: by 10.84.163.75 with SMTP id n11mr47501987plg.426.1514928146114; Tue, 02 Jan 2018 13:22:26 -0800 (PST)
Received: from mahesh-m-m8d1.attlocal.net ([2600:1700:edb0:8fd0:e1b4:8993:26c5:eb47]) by smtp.gmail.com with ESMTPSA id v15sm97575893pfa.68.2018.01.02.13.22.24 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 02 Jan 2018 13:22:25 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <151380493227.2629.15496937140050941194@ietfa.amsl.com>
Date: Tue, 2 Jan 2018 13:22:24 -0800
Cc: YANG Doctors <yang-doctors@ietf.org>, draft-ietf-pim-yang.all@ietf.org, ietf@ietf.org, pim@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <385138EB-6551-4209-B58B-118405B6C09A@gmail.com>
References: <151380493227.2629.15496937140050941194@ietfa.amsl.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/BRgs5bW4nEVJntIMYWHmF0aMbZo>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-pim-yang-12
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 21:22:30 -0000

Few other observations.

Is the YANG model description statement not supposed to carry the IETF =
copyright statement?

There is already a enum definition for BFD state called =E2=80=9Cstate=E2=80=
=9D in the BFD types file imported by the module. Why is that not being =
used in this model?

> On Dec 20, 2017, at 1:22 PM, J=C3=BCrgen Sch=C3=B6nw=C3=A4lder =
<j.schoenwaelder@jacobs-university.de> wrote:
>=20
> Reviewer: J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
> Review result: Almost Ready
>=20
> * General YANG Review Remarks
>=20
>  This document depends on a number of other I-Ds. Is it safe to
>  process this document while the other documents this document
>  depends on are not yet through the process? Who is tracking things
>  and making sure that any changes in other documents that may impact
>  the PIM document are detected and handled appropriately before
>  publication?
>=20
>  It is generally good style to write complete sentences in
>  description statements. Some of the description statements are just
>  fractions of a sentence.
>=20
>  I think we do not recommend anymore to list WG chairs in the contact
>  statement.
>=20
>  It is sometimes not clear why you define groupings that are only
>  used once (and sometimes are likely not reusable since they contain
>  relative paths in must expressions).
>=20
> * Introduction
>=20
>  - Is there a reason why you refer to RFC 6020 and to RFC 7950 in
>    sections 1 and 1.2? Why do you need the reference to RFC 6020?
>=20
>  - What are 'wider' management interfaces? If you mention NETCONF,
>    why not mention RESTCONF?
>=20
>  - s/Protocol-Independent Multicast (PIM) devices
>     /devices supporting Protocol-Independent Multicast (PIM)/
>=20
>  - So which YANG terminology applies, RFC 6020 or RFC 7950? I
>    personally think using YANG 1.1 is pretty safe these days.
>=20
> * Design of Data Model
>=20
>  - I did not really understand Section 2.5. It seems you are
>    duplicating objects for different address families but on some
>    systems these duplicate objects must have the same value. If so,
>    where would the must expression go and how does an implementation
>    add such a must expression? How many of such must expressions
>    would there have to be? Did you consider having address family
>    independent objects and optionally (controlled by a feature) per
>    address family objects that overwrite the independent settings?
>=20
> * Module Structure
>=20
>  - s/is included/is imported/
>=20
>  - The tree diagrams are rather long. It would likely help readers if
>    the diagram would be split into meaningful units and additional
>    text added to describe the units.
>=20
>    Are lists of the form
>=20
>          |  +--rw ipv4-rp* [ipv4-address]
>          |  |  +--rw ipv4-address    inet:ipv4-address
>=20
>    designed for exensibility? Otherwise, this may be collapsed into
>    a simple leaf-list.
>=20
>  - Since I am not familiar with details of PIM, I can't comment on
>    the question whether the model makes sense or not.
>=20
> * PIM base Module
>=20
>  - YANG modules compile cleanly according to the tracker page.
>=20
>  - As said above, consider using YANG 1.1. The ietf-routing module
>    actually uses YANG 1.1 so you will need a YANG 1.1 compiler
>    anyway.
>=20
>  - Consider adding reference statements to the feature definitions
>    in case a feature is described in a protocol specification.
>=20
>  - The value of timer-value is not really clear, you could have used
>    rt-types:timer-value-seconds16 directly.
>=20
>  - Why is graceful-restart/duration using an ad-hoc type for 16-bit
>    seconds and not timer-value? Is it because infinity and not-set
>    does not apply?
>=20
>  - Does a bfd/hello-interval of 'infinity' or 'not-set' make sense?
>=20
>  - More explicit description of bfd/hello-holdtime? Is a choice
>    really appropriate (hello-holdtime-or-multiplier)? Can I not have
>    both holdtime and multiplier? Perhaps I am just not clear what
>    holdtime does...
>=20
>  - Does a bfd/jp-interval of 'infinity' or 'not-set' make sense?
>=20
>  - More explicit description of bfd/jp-holdtime? Is a choice really
>    appropriate (jp-holdtime-or-multiplier)? Can I not have both
>    holdtime and multiplier? Perhaps I am just not clear what holdtime
>    does...
>=20
>  - Please provide more meaningful descriptions:
>=20
>         description "Propagation description";
>         description "Override interval";
>=20
>  - What is the meaning of the interface augmentation 'oper-status'
>    relative to 'oper-status' defined by ietf-interfaces? Is this just
>    a duplicate with fewer states? Or is this somehow more specific to
>    multicast or PIM packets? In the later case, I think this deserves
>    to the be explained in the description clause.
>=20
>  - How do the ip4 and ipv6 addresses relate to ip addresses assigned
>    to an interface in ietf-ip?
>=20
>  - What is the meaning of hello-expiration 'not-set'?
>=20
>  - What is the meaning of expiration 'not-set'?
>=20
>  - Is it useful to return the uptime in seconds (which is changing on
>    every get that is not in the same second) or could it be an option
>    to report the time when something transitioned into the up state
>    (which is not changing)? Well, it could be that we are simply used
>    to uptime like objects. Anyway, the description of up-time should
>    make it clear what exactly is defining the state 'up'. If this
>    says up for 5 seconds, what exactly transitioned into an 'up'
>    state 5 seconds ago?
>=20
>  - Is the any restriction for dr-priority or is it a full 32-bit
>    unsigned number space? In some vendor documentation I saw 0..65535
>    with a default of 1. What do RFCs say?
>=20
>  - I am not sure what the precise meaning of the error statistic
>    counters are. What turns an received or sent messages into an
>    error message? The description of grouping statistics-error does
>    not explain this. Also, if I receive a hello and I later decide
>    that this hello must have been an error, is this hello counted
>    twice? And what about messages that could not be parsed because
>    they were malformed, where are those counted?
>=20
>  - Why is 'pim' a presence container?
>=20
>  - Do comments like 'configuration data nodes' make sense if you
>    include config false nodes in the same branch of the tree?
>=20
> * PIM RP Module
>=20
>  - Does the feature bsr-election-state depend on the feature bsr?
>=20
>  - Should there be a default bsr-candidate/priority?
>=20
>  - Do you need the address/hash-mask-length/priority in
>    bsr-state-attributes in an NMDA implementation?
>=20
>  - I _assume_ the bsr-next-bootstrap value has to be interpreted
>    relative to the time the value was obtained. What about making
>    this an absolute timestamp instead? Well, actually I am not sure
>    what the value represents - is it the remaining time interval
>    until the next bootstrap will be sent?
>=20
>  - I have no clue what to expect here:
>=20
>         leaf group-policy {
>           type string;
>           description "Group policy.";
>         }
>=20
>     What can I expect the string to contain?
>=20
>   - I am again uncertain how exactly to understand the value of
>     rp-candidate-next-advertisement, see similar questions above.
>=20
>   - What are the policy values that can go into this:
>=20
>       leaf policy-name {
>         type string;
>         description
>           "Static RP policy.";
>       }
>=20
>     Is the string just an arbitrary name or does it mean something?
>=20
>   - How is this supposed to be used?
>=20
>       leaf policy {
>         type string;
>         description
>           "ACL (Access Control List) policy used to filter group
>            addresses.";
>       }
>=20
>     What is the meaning of <policy>foo</policy>?
>=20
> * PIM SM Module
>=20
>  - What is the meaning of a policy-name value?
>=20
>               leaf policy-name {
>                 if-feature spt-switch-policy;
>                 type string;
>                 description
>                   "Switch policy.";
>               }
>=20
>  - What is the meaning of a range-policy value?
>=20
>           leaf range-policy {
>             type string;
>             description
>               "Policy used to define SSM address range.";
>           }
>=20
> * PIM DM Module
>=20
>  - I wonder, would you need an identity for dense mode?
>=20
> * PIM BIDIR Module
>=20
>  - Remove
>=20
>     /*
>      * Typedefs
>      */
>=20
>  - What is the meaning of offer-interval or backoff-interval
>    'not-set'?
>=20
> * Implementation Status
>=20
>  It seems the trac page pointed to was used to collect information
>  about what proprietary implementation support, i.e., it does not
>  document to what extend the models defined in this document have
>  been implemented. There are some notable differences. For example,
>  it seems most counters implemented are 32-bit while most counters in
>  the YANG models are 64-bit. How chatty is PIM, are 64-bit counters
>  really needed and are implementors willing to move to 64-bit
>  counters?
>=20
> * Security Considerations
>=20
>  I think this needs to include a bit more details. See
>=20
>  https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
>=20
>  for the latest template that YANG module authors are expected to
>  use.
>=20
>=20
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

Mahesh Jethanandani
mjethanandani@gmail.com


From nobody Tue Jan  2 14:03:27 2018
Return-Path: <mjethanandani@gmail.com>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC8CC12D850; Tue,  2 Jan 2018 14:03:16 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Mahesh Jethanandani <mjethanandani@gmail.com>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-netmod-rfc7277bis.all@ietf.org, ietf@ietf.org, netmod@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151493059670.30939.8241436286877635051@ietfa.amsl.com>
Date: Tue, 02 Jan 2018 14:03:16 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/m1BOmuCth6pl2SLQISlFgDyJJ_s>
Subject: [yang-doctors] Yangdoctors early review of draft-ietf-netmod-rfc7277bis-01
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 22:03:17 -0000

Reviewer: Mahesh Jethanandani
Review result: Ready

Document reviewed: draft-ietf-netmod-rfc7277bis-01

Status: Ready

This review is looking at the draft from a YANG perspective. 

Summary:

This document updates the ietf-ip YANG data model to comply with the NMDA requirements.

Comments:

I believe the document is ready. 

The YANG compilation page shows the model passing all compilations.



From nobody Wed Jan  3 01:24:56 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E964012D86A; Wed,  3 Jan 2018 01:24:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 b4dRFaByYGe9; Wed,  3 Jan 2018 01:24:53 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 703DB12D864; Wed,  3 Jan 2018 01:24:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7785; q=dns/txt; s=iport; t=1514971492; x=1516181092; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=EbH5crlmmKk+gJbyI5wTP4TQLzz2fsCShuQBuMoBxgs=; b=Rv1mJdZEdo9kdltc/SLcYAhQiTxYqFcmg1Ip7PrcOZ0CfPxiX0BBT7i2 AkmAJ6aLnNN6rx3KAa9fkNeVtlbW7CfOyW4OWFDRhEIrcvF28ed+5q1F7 yCgJ1dQsFDHgFzYsqRIPmFG5abS07mCc+9lk2ULRvHxY8qjNzR11+S8Af 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CAAQA7oExa/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQkdCeEB4sYkACSAIdmCiOFGAKEchUBAQEBAQEBAQFrKIUkBiN?= =?us-ascii?q?IDhALQgICVwYBDAgBAYoqELIHgicmihcBAQEBAQEBAQEBAQEBAQEBAQEBAQEYB?= =?us-ascii?q?YQMg2iBaAEpDIJ5gy8BhQWCRSAFkiCRLogDjTOMHIdlh1WFUIFaiAWBPDUjgU8?= =?us-ascii?q?yGggbFT2CKoRXQDcBiRUBAQE?=
X-IronPort-AV: E=Sophos;i="5.45,500,1508803200"; d="scan'208,217";a="1230423"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jan 2018 09:24:48 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w039OmML004042; Wed, 3 Jan 2018 09:24:48 GMT
To: Ladislav Lhotka <lhotka@nic.cz>, draft-ietf-rtgwg-yang-rip.all@ietf.org
Cc: yang-doctors@ietf.org
References: <m2d1h3wwxc.fsf@birdie.labs.nic.cz>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <ba73d231-6727-dfad-d461-9eb69c35b4c3@cisco.com>
Date: Wed, 3 Jan 2018 10:24:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <m2d1h3wwxc.fsf@birdie.labs.nic.cz>
Content-Type: multipart/alternative; boundary="------------356C09D58AD7C751C3D8593B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/WCF4cOZeSOatq89RKhPH4XfKFcY>
Subject: Re: [yang-doctors] YANG doctor review of draft-ietf-rtgwg-yang-rip-02
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2018 09:24:55 -0000

This is a multi-part message in MIME format.
--------------356C09D58AD7C751C3D8593B
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Lada,

draft-ietf-rtgwg-yang-rip-07 is on the Jan 11th IESG telechat.
Would you mind confirming whether this version is fine?

Regards, Benoit
> Hi,
>
> I was assigned to be the YANG doctor for this document. Here is my
> review:
>
> **** General comments
>
> Overall, the module is in a good shape and integrates nicely with the
> core routing data model [RFC 8022].
>
> The I-D text is rather scarce, apart from the module it essentially
> contains only boilerplate stuff. Some information about the context in
> which this module is supposed to be used, design decisions etc. would
> be certainly useful.
>
> A non-normative appendix with a configuration example (instance data)
> would also help people that are not fluent in YANG to understand what
> data are included in this model.
>
> Some parts of the model â€“ "distribute-list", "redistribute", "bfd",
> "authentication" on interfaces (or at least the "key" list) â€“ are
> probably not specific to RIP and could be used by other protocols as
> well. If it is so, it would be better to model them separately as
> general mechanisms.
>
> Documents containing YANG modules that are imported by ietf-rip should
> appear among normative references. One way to achieve this (which is
> also useful by itself) is to include a table of namespace prefixes,
> see e.g.
>
> https://tools.ietf.org/html/rfc8022#section-2.3
>
> **** Specific comments
>
>       - Matching identities is done in the old YANG 1.0 way, for
>         example:
>
>         when "rt:type = 'rip:ripv2' or rt:type = 'rip:ripng'"
>
>         This is fragile because the identities are matched based on
>         string equality, so the result depends on the choice of the
>         namespace prefix. Unless there is a strong reason not to use
>         YANG 1.1, this is much simpler and more rubust
>
>         when "derived-from(rt:type, 'rip:rip')"
>
>       - In "redistribution", the must expressions are outright broken,
>         e.g. for IS-IS:
>
>         must "../../../../../rt:control-plane-protocol"
>         + "[rt:name = current()]/type = 'isis'" { ... }
>
>         First, the ietf-rip module also needs to import ietf-isis, and
>         then the must statement can be rewritten like so:
>
>         must "derived-from-or-self("
>         + "../../../../../rt:control-plane-protocol"
>         + "[rt:name = current()]/type, 'isis:isis')"
>
>       - Some descriptions could mention that the parameter (feature
>         etc.) only applies to RIP. For example, in
>
>         feature interface-statistics {
>           description
>             "This feature indicates that the system supports collecting
>              per-interface statistic data.";
>         }
>
>         I would add "... related to RIP." at the end.
>
>       - Maybe it's absolutely clear to experts but the name and
>         description of the "neighbor-configuration" feature look like
>         the feature can make neighbors remotely configurable. I had to
>         look up where it is used to find out what's the real
>         meaning. Perhaps something like "explicit-neighbors" might be
>         easier to understand?
>
>       - The name of "no-supply" leaf looks strange. I checked a couple
>         of CLIs and they use "passive", "passive-interface" or
>         "send-options" for preventing RIP updates from being sent.
>
>       - In "split-horizon" leaf, I would use "poison-reverse" enum
>         rather than "poison".
>
> Lada
>


--------------356C09D58AD7C751C3D8593B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Lada,<br>
      <br>
      draft-ietf-rtgwg-yang-rip-07 is on the Jan 11th IESG telechat.<br>
      Would you mind confirming whether this version is fine?<br>
      <br>
      Regards, Benoit<small><br>
      </small></div>
    <blockquote type="cite" cite="mid:m2d1h3wwxc.fsf@birdie.labs.nic.cz">
      <pre wrap="">Hi,

I was assigned to be the YANG doctor for this document. Here is my
review:

**** General comments

Overall, the module is in a good shape and integrates nicely with the
core routing data model [RFC 8022].

The I-D text is rather scarce, apart from the module it essentially
contains only boilerplate stuff. Some information about the context in
which this module is supposed to be used, design decisions etc. would
be certainly useful.

A non-normative appendix with a configuration example (instance data)
would also help people that are not fluent in YANG to understand what
data are included in this model.

Some parts of the model â€“ "distribute-list", "redistribute", "bfd",
"authentication" on interfaces (or at least the "key" list) â€“ are
probably not specific to RIP and could be used by other protocols as
well. If it is so, it would be better to model them separately as
general mechanisms.

Documents containing YANG modules that are imported by ietf-rip should
appear among normative references. One way to achieve this (which is
also useful by itself) is to include a table of namespace prefixes,
see e.g.

<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/rfc8022#section-2.3">https://tools.ietf.org/html/rfc8022#section-2.3</a>

**** Specific comments

     - Matching identities is done in the old YANG 1.0 way, for
       example:

       when "rt:type = 'rip:ripv2' or rt:type = 'rip:ripng'"

       This is fragile because the identities are matched based on
       string equality, so the result depends on the choice of the
       namespace prefix. Unless there is a strong reason not to use
       YANG 1.1, this is much simpler and more rubust

       when "derived-from(rt:type, 'rip:rip')"

     - In "redistribution", the must expressions are outright broken,
       e.g. for IS-IS:

       must "../../../../../rt:control-plane-protocol"
       + "[rt:name = current()]/type = 'isis'" { ... }

       First, the ietf-rip module also needs to import ietf-isis, and
       then the must statement can be rewritten like so:

       must "derived-from-or-self("
       + "../../../../../rt:control-plane-protocol"
       + "[rt:name = current()]/type, 'isis:isis')"

     - Some descriptions could mention that the parameter (feature
       etc.) only applies to RIP. For example, in

       feature interface-statistics {
         description
           "This feature indicates that the system supports collecting
            per-interface statistic data.";
       }

       I would add "... related to RIP." at the end.

     - Maybe it's absolutely clear to experts but the name and
       description of the "neighbor-configuration" feature look like
       the feature can make neighbors remotely configurable. I had to
       look up where it is used to find out what's the real
       meaning. Perhaps something like "explicit-neighbors" might be
       easier to understand?

     - The name of "no-supply" leaf looks strange. I checked a couple
       of CLIs and they use "passive", "passive-interface" or
       "send-options" for preventing RIP updates from being sent.

     - In "split-horizon" leaf, I would use "poison-reverse" enum
       rather than "poison".

Lada

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------356C09D58AD7C751C3D8593B--


From nobody Wed Jan  3 07:22:51 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02AD21205D3; Wed,  3 Jan 2018 07:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 NXmDTvGKkxtQ; Wed,  3 Jan 2018 07:22:46 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 8D656126D3F; Wed,  3 Jan 2018 07:22:45 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 66BA11820413; Wed,  3 Jan 2018 16:22:42 +0100 (CET)
Received: from localhost (nat-2.nic.cz [217.31.205.2]) by trail.lhotka.name (Postfix) with ESMTPSA id CF3D71820410; Wed,  3 Jan 2018 16:22:39 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Benoit Claise <bclaise@cisco.com>, draft-ietf-rtgwg-yang-rip.all@ietf.org
Cc: yang-doctors@ietf.org
In-Reply-To: <ba73d231-6727-dfad-d461-9eb69c35b4c3@cisco.com>
References: <m2d1h3wwxc.fsf@birdie.labs.nic.cz> <ba73d231-6727-dfad-d461-9eb69c35b4c3@cisco.com>
Date: Wed, 03 Jan 2018 16:22:40 +0100
Message-ID: <878tdf3r27.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/yB2uY8kQ_0YvHfNo6Ii3297_ZcU>
Subject: Re: [yang-doctors] YANG doctor review of draft-ietf-rtgwg-yang-rip-02
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2018 15:22:50 -0000

Hi Benoit,

Benoit Claise <bclaise@cisco.com> writes:

> Hi Lada,
>
> draft-ietf-rtgwg-yang-rip-07 is on the Jan 11th IESG telechat.
> Would you mind confirming whether this version is fine?

Yes, I think Xufeng addressed all my comments and suggestions.

Thanks, Lada

>
> Regards, Benoit
>> Hi,
>>
>> I was assigned to be the YANG doctor for this document. Here is my
>> review:
>>
>> **** General comments
>>
>> Overall, the module is in a good shape and integrates nicely with the
>> core routing data model [RFC 8022].
>>
>> The I-D text is rather scarce, apart from the module it essentially
>> contains only boilerplate stuff. Some information about the context in
>> which this module is supposed to be used, design decisions etc. would
>> be certainly useful.
>>
>> A non-normative appendix with a configuration example (instance data)
>> would also help people that are not fluent in YANG to understand what
>> data are included in this model.
>>
>> Some parts of the model =E2=80=93 "distribute-list", "redistribute", "bf=
d",
>> "authentication" on interfaces (or at least the "key" list) =E2=80=93 are
>> probably not specific to RIP and could be used by other protocols as
>> well. If it is so, it would be better to model them separately as
>> general mechanisms.
>>
>> Documents containing YANG modules that are imported by ietf-rip should
>> appear among normative references. One way to achieve this (which is
>> also useful by itself) is to include a table of namespace prefixes,
>> see e.g.
>>
>> https://tools.ietf.org/html/rfc8022#section-2.3
>>
>> **** Specific comments
>>
>>       - Matching identities is done in the old YANG 1.0 way, for
>>         example:
>>
>>         when "rt:type =3D 'rip:ripv2' or rt:type =3D 'rip:ripng'"
>>
>>         This is fragile because the identities are matched based on
>>         string equality, so the result depends on the choice of the
>>         namespace prefix. Unless there is a strong reason not to use
>>         YANG 1.1, this is much simpler and more rubust
>>
>>         when "derived-from(rt:type, 'rip:rip')"
>>
>>       - In "redistribution", the must expressions are outright broken,
>>         e.g. for IS-IS:
>>
>>         must "../../../../../rt:control-plane-protocol"
>>         + "[rt:name =3D current()]/type =3D 'isis'" { ... }
>>
>>         First, the ietf-rip module also needs to import ietf-isis, and
>>         then the must statement can be rewritten like so:
>>
>>         must "derived-from-or-self("
>>         + "../../../../../rt:control-plane-protocol"
>>         + "[rt:name =3D current()]/type, 'isis:isis')"
>>
>>       - Some descriptions could mention that the parameter (feature
>>         etc.) only applies to RIP. For example, in
>>
>>         feature interface-statistics {
>>           description
>>             "This feature indicates that the system supports collecting
>>              per-interface statistic data.";
>>         }
>>
>>         I would add "... related to RIP." at the end.
>>
>>       - Maybe it's absolutely clear to experts but the name and
>>         description of the "neighbor-configuration" feature look like
>>         the feature can make neighbors remotely configurable. I had to
>>         look up where it is used to find out what's the real
>>         meaning. Perhaps something like "explicit-neighbors" might be
>>         easier to understand?
>>
>>       - The name of "no-supply" leaf looks strange. I checked a couple
>>         of CLIs and they use "passive", "passive-interface" or
>>         "send-options" for preventing RIP updates from being sent.
>>
>>       - In "split-horizon" leaf, I would use "poison-reverse" enum
>>         rather than "poison".
>>
>> Lada
>>
>

--=20
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Wed Jan  3 10:22:33 2018
Return-Path: <mjethanandani@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1829F1241F5; Wed,  3 Jan 2018 10:22:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6Q_a233_4VRO; Wed,  3 Jan 2018 10:22:28 -0800 (PST)
Received: from mail-pl0-x234.google.com (mail-pl0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) (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 62CE61200B9; Wed,  3 Jan 2018 10:22:28 -0800 (PST)
Received: by mail-pl0-x234.google.com with SMTP id z5so1713079plo.10; Wed, 03 Jan 2018 10:22:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=P5VQc1zhzQCZG5QdNd3YRMP9Iz2Djb0dmoZmMuC510I=; b=Fprk2QSjXN1v/BjTX1emKpVZVvIYGncGN3sYXoEZxZr2czd745ToMa30klxXYcOi2Y 2KelxPFnGGQDv0Yyg0wznNw9uYR+v8ItlAcvTnVHYR4LcGJBTWRrgrGSZ0ZJ0idRVryU K9bFhIWwCU7VQt3bOU1cI/MRRBdryLjoMEYuHwPwL3nSGhO5vNIOvxygGMjJxeu0HoNd YZ55kgriE9Oz9nr51Z/aO7uN1CGczBo7uDL6Y+xq+dqf8Dr+n4w74tfK5lHLXCgqNBqn H3KS2yps382imojY/YD+XW1eJeLP/M6qo79E7CU2CmNq+mUqAac1d3rn58ERcgwfCopO RQDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=P5VQc1zhzQCZG5QdNd3YRMP9Iz2Djb0dmoZmMuC510I=; b=TMMAee3Fv2prWx2+zvZVWOhfw8EvVN0wtjAvblBaWzj9BHxzr7jipY7jKs73jhx2vo 8KeS7D3i6lCJIdh90Fr70DJFlhFKZC2jFYD0Bfld4Fa2dTN9OWpaJRRepuofar100KvN TLHC4MNH/aVbqrztd6Y8SDLly8ArKqKlYqr9vt0jgQa3TqFb2kDHqp+Mqt8llp34T4hT iDfmuKVwzje14IaEd5sg1/06LWLDgCMa+iGSeOPtJT8rKlgbAGGqxw/XRuci+Iot2Ek0 /Ke3vT7ZWQZqDUMtcjCTsTYA5zRQN0fcecmnE/gstOr5cgzr4OPdHQhsD2YBK6TS2xvs xfnw==
X-Gm-Message-State: AKGB3mKfK7ZDEfDN+XsIbvhqpTWuP5BVQVlwfDeIXj4do1lb9XP0VcCr 01f58PNSQdRSB2uQXe+WnG4=
X-Google-Smtp-Source: ACJfBoscGbJ0avlL94HjdOBXqX/2ac7co9I77jkU0xfDtcPlTowdAKb3JyuRWoNyipb97VG2AMOz0Q==
X-Received: by 10.84.128.227 with SMTP id a90mr2111866pla.97.1515003747889; Wed, 03 Jan 2018 10:22:27 -0800 (PST)
Received: from mahesh-m-m8d1.attlocal.net ([2600:1700:edb0:8fd0:3ca1:1c4c:2fc0:4bdc]) by smtp.gmail.com with ESMTPSA id t75sm4574135pfi.146.2018.01.03.10.22.26 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 03 Jan 2018 10:22:26 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7D1A77AF-5402-4896-B9BC-3BBF7AFC1A5F"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <878tdf3r27.fsf@nic.cz>
Date: Wed, 3 Jan 2018 10:22:25 -0800
Cc: Benoit Claise <bclaise@cisco.com>, draft-ietf-rtgwg-yang-rip.all@ietf.org,  yang-doctors@ietf.org
Message-Id: <EBF0292A-1658-413C-8956-4C346590448C@gmail.com>
References: <m2d1h3wwxc.fsf@birdie.labs.nic.cz> <ba73d231-6727-dfad-d461-9eb69c35b4c3@cisco.com> <878tdf3r27.fsf@nic.cz>
To: Ladislav Lhotka <lhotka@nic.cz>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/IFPADeO8d3z1cqVxa3EBiI8nJU0>
Subject: Re: [yang-doctors] YANG doctor review of draft-ietf-rtgwg-yang-rip-02
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2018 18:22:31 -0000

--Apple-Mail=_7D1A77AF-5402-4896-B9BC-3BBF7AFC1A5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I am looking at the -07 version of the draft, and I see that the YANG =
model has the WG chairs listed in the model. I thought we had decided =
not to include the name of the chairs in the model. See Appendix C of =
rfc6087bis for example of a YANG module template. Also the copyright is =
pretty old (it refers to 2016), but I assume the RFC editors will update =
that.

Cheers.

> On Jan 3, 2018, at 7:22 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
>=20
> Hi Benoit,
>=20
> Benoit Claise <bclaise@cisco.com <mailto:bclaise@cisco.com>> writes:
>=20
>> Hi Lada,
>>=20
>> draft-ietf-rtgwg-yang-rip-07 is on the Jan 11th IESG telechat.
>> Would you mind confirming whether this version is fine?
>=20
> Yes, I think Xufeng addressed all my comments and suggestions.
>=20
> Thanks, Lada
>=20
>>=20
>> Regards, Benoit
>>> Hi,
>>>=20
>>> I was assigned to be the YANG doctor for this document. Here is my
>>> review:
>>>=20
>>> **** General comments
>>>=20
>>> Overall, the module is in a good shape and integrates nicely with =
the
>>> core routing data model [RFC 8022].
>>>=20
>>> The I-D text is rather scarce, apart from the module it essentially
>>> contains only boilerplate stuff. Some information about the context =
in
>>> which this module is supposed to be used, design decisions etc. =
would
>>> be certainly useful.
>>>=20
>>> A non-normative appendix with a configuration example (instance =
data)
>>> would also help people that are not fluent in YANG to understand =
what
>>> data are included in this model.
>>>=20
>>> Some parts of the model =E2=80=93 "distribute-list", "redistribute", =
"bfd",
>>> "authentication" on interfaces (or at least the "key" list) =E2=80=93 =
are
>>> probably not specific to RIP and could be used by other protocols as
>>> well. If it is so, it would be better to model them separately as
>>> general mechanisms.
>>>=20
>>> Documents containing YANG modules that are imported by ietf-rip =
should
>>> appear among normative references. One way to achieve this (which is
>>> also useful by itself) is to include a table of namespace prefixes,
>>> see e.g.
>>>=20
>>> https://tools.ietf.org/html/rfc8022#section-2.3
>>>=20
>>> **** Specific comments
>>>=20
>>>      - Matching identities is done in the old YANG 1.0 way, for
>>>        example:
>>>=20
>>>        when "rt:type =3D 'rip:ripv2' or rt:type =3D 'rip:ripng'"
>>>=20
>>>        This is fragile because the identities are matched based on
>>>        string equality, so the result depends on the choice of the
>>>        namespace prefix. Unless there is a strong reason not to use
>>>        YANG 1.1, this is much simpler and more rubust
>>>=20
>>>        when "derived-from(rt:type, 'rip:rip')"
>>>=20
>>>      - In "redistribution", the must expressions are outright =
broken,
>>>        e.g. for IS-IS:
>>>=20
>>>        must "../../../../../rt:control-plane-protocol"
>>>        + "[rt:name =3D current()]/type =3D 'isis'" { ... }
>>>=20
>>>        First, the ietf-rip module also needs to import ietf-isis, =
and
>>>        then the must statement can be rewritten like so:
>>>=20
>>>        must "derived-from-or-self("
>>>        + "../../../../../rt:control-plane-protocol"
>>>        + "[rt:name =3D current()]/type, 'isis:isis')"
>>>=20
>>>      - Some descriptions could mention that the parameter (feature
>>>        etc.) only applies to RIP. For example, in
>>>=20
>>>        feature interface-statistics {
>>>          description
>>>            "This feature indicates that the system supports =
collecting
>>>             per-interface statistic data.";
>>>        }
>>>=20
>>>        I would add "... related to RIP." at the end.
>>>=20
>>>      - Maybe it's absolutely clear to experts but the name and
>>>        description of the "neighbor-configuration" feature look like
>>>        the feature can make neighbors remotely configurable. I had =
to
>>>        look up where it is used to find out what's the real
>>>        meaning. Perhaps something like "explicit-neighbors" might be
>>>        easier to understand?
>>>=20
>>>      - The name of "no-supply" leaf looks strange. I checked a =
couple
>>>        of CLIs and they use "passive", "passive-interface" or
>>>        "send-options" for preventing RIP updates from being sent.
>>>=20
>>>      - In "split-horizon" leaf, I would use "poison-reverse" enum
>>>        rather than "poison".
>>>=20
>>> Lada
>>>=20
>>=20
>=20
> --=20
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>=20
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>
> https://www.ietf.org/mailman/listinfo/yang-doctors =
<https://www.ietf.org/mailman/listinfo/yang-doctors>
Mahesh Jethanandani
mjethanandani@gmail.com


--Apple-Mail=_7D1A77AF-5402-4896-B9BC-3BBF7AFC1A5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">I am looking at the -07 version of the draft, and I see that =
the YANG model has the WG chairs listed in the model. I thought we had =
decided not to include the name of the chairs in the model. See Appendix =
C of rfc6087bis for example of a YANG module template. Also the =
copyright is pretty old (it refers to 2016), but I assume the RFC =
editors will update that.<div class=3D""><br class=3D""></div><div =
class=3D"">Cheers.<br class=3D""><div class=3D""><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jan 3, 2018, at 7:22 AM, Ladislav Lhotka &lt;<a =
href=3D"mailto:lhotka@nic.cz" class=3D"">lhotka@nic.cz</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Hi Benoit,</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Benoit Claise &lt;</span><a =
href=3D"mailto:bclaise@cisco.com" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D"">bclaise@cisco.com</a><span style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: =
none; display: inline !important;" class=3D"">&gt; writes:</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><blockquote type=3D"cite" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D"">Hi Lada,<br class=3D""><br =
class=3D"">draft-ietf-rtgwg-yang-rip-07 is on the Jan 11th IESG =
telechat.<br class=3D"">Would you mind confirming whether this version =
is fine?<br class=3D""></blockquote><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">Yes, I think Xufeng addressed all my =
comments and suggestions.</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Thanks, Lada</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><blockquote=
 type=3D"cite" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
class=3D"">Regards, Benoit<br class=3D""><blockquote type=3D"cite" =
class=3D"">Hi,<br class=3D""><br class=3D"">I was assigned to be the =
YANG doctor for this document. Here is my<br class=3D"">review:<br =
class=3D""><br class=3D"">**** General comments<br class=3D""><br =
class=3D"">Overall, the module is in a good shape and integrates nicely =
with the<br class=3D"">core routing data model [RFC 8022].<br =
class=3D""><br class=3D"">The I-D text is rather scarce, apart from the =
module it essentially<br class=3D"">contains only boilerplate stuff. =
Some information about the context in<br class=3D"">which this module is =
supposed to be used, design decisions etc. would<br class=3D"">be =
certainly useful.<br class=3D""><br class=3D"">A non-normative appendix =
with a configuration example (instance data)<br class=3D"">would also =
help people that are not fluent in YANG to understand what<br =
class=3D"">data are included in this model.<br class=3D""><br =
class=3D"">Some parts of the model =E2=80=93 "distribute-list", =
"redistribute", "bfd",<br class=3D"">"authentication" on interfaces (or =
at least the "key" list) =E2=80=93 are<br class=3D"">probably not =
specific to RIP and could be used by other protocols as<br =
class=3D"">well. If it is so, it would be better to model them =
separately as<br class=3D"">general mechanisms.<br class=3D""><br =
class=3D"">Documents containing YANG modules that are imported by =
ietf-rip should<br class=3D"">appear among normative references. One way =
to achieve this (which is<br class=3D"">also useful by itself) is to =
include a table of namespace prefixes,<br class=3D"">see e.g.<br =
class=3D""><br class=3D""><a =
href=3D"https://tools.ietf.org/html/rfc8022#section-2.3" =
class=3D"">https://tools.ietf.org/html/rfc8022#section-2.3</a><br =
class=3D""><br class=3D"">**** Specific comments<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Matching identities is done =
in the old YANG 1.0 way, for<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;example:<br =
class=3D""><br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;when =
"rt:type =3D 'rip:ripv2' or rt:type =3D 'rip:ripng'"<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This is fragile =
because the identities are matched based on<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;string equality, so =
the result depends on the choice of the<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;namespace prefix. =
Unless there is a strong reason not to use<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;YANG 1.1, this is =
much simpler and more rubust<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;when =
"derived-from(rt:type, 'rip:rip')"<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- In "redistribution", the must =
expressions are outright broken,<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;e.g. for IS-IS:<br =
class=3D""><br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;must =
"../../../../../rt:control-plane-protocol"<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ "[rt:name =3D =
current()]/type =3D 'isis'" { ... }<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;First, the ietf-rip =
module also needs to import ietf-isis, and<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;then the must =
statement can be rewritten like so:<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;must =
"derived-from-or-self("<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ =
"../../../../../rt:control-plane-protocol"<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+ "[rt:name =3D =
current()]/type, 'isis:isis')"<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Some descriptions could =
mention that the parameter (feature<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;etc.) only applies =
to RIP. For example, in<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;feature =
interface-statistics {<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;descripti=
on<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;"This feature indicates that the system supports collecting<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;per-interface statistic data.";<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I would add "... =
related to RIP." at the end.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- Maybe it's absolutely clear =
to experts but the name and<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;description of the =
"neighbor-configuration" feature look like<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the feature can =
make neighbors remotely configurable. I had to<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;look up where it is =
used to find out what's the real<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;meaning. Perhaps =
something like "explicit-neighbors" might be<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;easier to =
understand?<br class=3D""><br class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- =
The name of "no-supply" leaf looks strange. I checked a couple<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;of CLIs and they =
use "passive", "passive-interface" or<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"send-options" for =
preventing RIP updates from being sent.<br class=3D""><br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;- In "split-horizon" leaf, I =
would use "poison-reverse" enum<br =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;rather than =
"poison".<br class=3D""><br class=3D"">Lada<br class=3D""><br =
class=3D""></blockquote><br class=3D""></blockquote><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">--<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Ladislav =
Lhotka</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Head, CZ.NIC Labs</span><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">PGP Key ID: 0xB8F92B08A9F76C67</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">yang-doctors =
mailing list</span><br style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><a =
href=3D"mailto:yang-doctors@ietf.org" style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D"">yang-doctors@ietf.org</a><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors" =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/yang-doctors</a></div></b=
lockquote></div><br class=3D""><div class=3D"">
<div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div>

</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_7D1A77AF-5402-4896-B9BC-3BBF7AFC1A5F--


From nobody Wed Jan  3 11:52:43 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CDB126C83; Wed,  3 Jan 2018 11:52:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Andy Bierman <andy@yumaworks.com>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-netmod-rfc7223bis.all@ietf.org, ietf@ietf.org, netmod@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151500915856.30927.2802442728843365900@ietfa.amsl.com>
Date: Wed, 03 Jan 2018 11:52:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/6mdiToe0MYsjiEvAwfLf2N15CjI>
Subject: [yang-doctors] Yangdoctors early review of draft-ietf-netmod-rfc7223bis-01
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jan 2018 19:52:38 -0000

Reviewer: Andy Bierman
Review result: Ready

This module appears to follow all NMDA transition guidelines.
There are no YANG compiler errors or warnings.


From nobody Thu Jan  4 03:12:59 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B896126D46 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 03:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 7VhIjf8unwi3 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 03:12:54 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24C70126CB6 for <yang-doctors@ietf.org>; Thu,  4 Jan 2018 03:12:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23339; q=dns/txt; s=iport; t=1515064374; x=1516273974; h=to:cc:from:subject:message-id:date:mime-version; bh=HQCh97Ef8ZXI0WNQ6zjzckNtmcCCXHc5AZAOyhwH9pg=; b=RNgemf8PdIRULS9uLOYpiQWLDstp1WL4asTLRNNlruAaYnsKgLkw9TVv fwvQW8q/78tMZLM/0exz3gNsHU4d9PjjVSnbIN57oCkkqcGRjnYrn25+u KKxPEDa+leA2nyNZ0hGWe593dPA3f8rHnMds44ol/vunwrYy9npNdIhkX 8=;
X-IronPort-AV: E=Sophos;i="5.45,507,1508803200"; d="scan'208,217";a="1252131"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jan 2018 11:12:52 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w04BCqbu031660; Thu, 4 Jan 2018 11:12:52 GMT
To: YANG Doctors <yang-doctors@ietf.org>
Cc: Michelle Cotton <michelle.cotton@icann.org>, amanda.baber@iana.org, sabrina.tanamal@iana.org, "Joe Clarke (jclarke)" <jclarke@cisco.com>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
Date: Thu, 4 Jan 2018 12:12:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------FDA221772A340BA9107D141A"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/FjFRTbCSZFjFtyW1wnRJ2NVF-lQ>
Subject: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 11:12:59 -0000

This is a multi-part message in MIME format.
--------------FDA221772A340BA9107D141A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Dear all,

We can say that the RFC is the source of truth but devops people "play" 
about YANG modules.
I'm trying to have a single source of truth for the repository of 
RFC-produced YANG modules, while we have multiple ones now.

IMO, it should be IANA.Â  We've discussing this option with RFC editor 
and IANA: 
https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml 
is being transformed in that direction.
The end goal is that end users, wanted to be up-to-date with the latest 
RFC-produced YANG modules, would perform a cron job such as:
 Â Â Â  rsync -avz --delete rsync.ietf.org::iana/yang-parameters .

Note: especially interested for IANA-maintained YANG modules such as 
iana-if-type

Now the follow-up question from IANA:

    We were working on the posting of the yang modules for
    _draft-ietf-rtgwg-routing-types
    <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/>_
    per our new process.Â  When requesting the final files from the
    RFC-Editor, the file they extracted using their tool and the yang
    modules appear to have a lot of blank space in them.Â  See attached

    Is this OK?Â  Do we post it as it is in the provided file from the
    RFC-Editor?Â  We know that there is some sensitivity to spacing in
    these files so we want to make sure the correct thing is being posted.

The solution should be: pyang -f yang ...
However, after some testing:

bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang -f 
yang iana-routing-types@2017-12-04.yang > newfile.yang
bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff 
iana-routing-types@2017-12-04.yang newfile.yang
16d15
<
35,39c34,39
<Â Â Â  revision 2017-12-04 {
<Â Â Â Â Â  description "Initial revision.";
<Â Â Â Â Â  reference
<Â Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.
<Â Â Â Â Â Â Â Â  Section 4.";
---
 >Â Â  revision 2017-12-04 {
 >Â Â Â Â  description
 >Â Â Â Â Â Â  "Initial revision.";
 >Â Â Â Â  reference
 >Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.
 >Â Â Â Â Â Â Â  Section 4.";
42,47d41
<
<
<
<Â Â  /*** Collection of IANA types related to routing ***/
<Â Â  /*** IANA Address Family enumeration ***/
<
50c44
<Â Â Â Â Â Â  enum ipv4 {
---
 >Â Â Â Â Â Â  enum "ipv4" {
55,56c49
<
<Â Â Â Â Â Â  enum ipv6 {
---
 >Â Â Â Â Â Â  enum "ipv6" {
61,62c54
<
<Â Â Â Â Â Â  enum nsap {
---
 >Â Â Â Â Â Â  enum "nsap" {
67,68c59
<
<Â Â Â Â Â Â  enum hdlc {
---
 >Â Â Â Â Â Â  enum "hdlc" {
73,74c64
<
<Â Â Â Â Â Â  enum bbn1822 {
---
 >Â Â Â Â Â Â  enum "bbn1822" {
80,81c70
<
<Â Â Â Â Â Â  enum ieee802 {
---
 >Â Â Â Â Â Â  enum "ieee802" {
87,88c76
<
<Â Â Â Â Â Â  enum e163 {
---
 >Â Â Â Â Â Â  enum "e163" {
93c81
<Â Â Â Â Â Â  enum e164 {
---
 >Â Â Â Â Â Â  enum "e164" {
99,100c87
<
<Â Â Â Â Â Â  enum f69 {
---
 >Â Â Â Â Â Â  enum "f69" {
105,106c92
<
<Â Â Â Â Â Â  enum x121 {
---
 >Â Â Â Â Â Â  enum "x121" {
111,112c97
<
<Â Â Â Â Â Â  enum ipx {
---
 >Â Â Â Â Â Â  enum "ipx" {
118,119c103
<
<Â Â Â Â Â Â  enum appletalk {
---
 >Â Â Â Â Â Â  enum "appletalk" {
124,125c108
<
<Â Â Â Â Â Â  enum decnet-iv {
---
 >Â Â Â Â Â Â  enum "decnet-iv" {
130,131c113
<
<Â Â Â Â Â Â  enum vines {
---
 >Â Â Â Â Â Â  enum "vines" {
136,141c118
<
<
<
<
<
<Â Â Â Â Â Â  enum e164-nsap {
---
 >Â Â Â Â Â Â  enum "e164-nsap" {
146,147c123
<
<Â Â Â Â Â Â  enum dns {
---
 >Â Â Â Â Â Â  enum "dns" {
152,153c128
<
<Â Â Â Â Â Â  enum distinguished-name {
---
 >Â Â Â Â Â Â  enum "distinguished-name" {
158,159c133
<
<Â Â Â Â Â Â  enum as-num {
---
 >Â Â Â Â Â Â  enum "as-num" {
164,165c138
<
<Â Â Â Â Â Â  enum xtp-v4 {
---
 >Â Â Â Â Â Â  enum "xtp-v4" {
171,172c144
<
<Â Â Â Â Â Â  enum xtp-v6 {
---
 >Â Â Â Â Â Â  enum "xtp-v6" {
177,178c149
<
<Â Â Â Â Â Â  enum xtp-native {
---
 >Â Â Â Â Â Â  enum "xtp-native" {
183,184c154
<
<Â Â Â Â Â Â  enum fc-port {
---
 >Â Â Â Â Â Â  enum "fc-port" {
189c159
<Â Â Â Â Â Â  enum fc-node {
---
 >Â Â Â Â Â Â  enum "fc-node" {
194,195c164
<
<Â Â Â Â Â Â  enum gwid {
---
 >Â Â Â Â Â Â  enum "gwid" {
200,201c169
<
<Â Â Â Â Â Â  enum l2vpn {
---
 >Â Â Â Â Â Â  enum "l2vpn" {
206,207c174
<
<Â Â Â Â Â Â  enum mpls-tp-section-eid {
---
 >Â Â Â Â Â Â  enum "mpls-tp-section-eid" {
213,214c180
<
<Â Â Â Â Â Â  enum mpls-tp-lsp-eid {
---
 >Â Â Â Â Â Â  enum "mpls-tp-lsp-eid" {
220,221c186
<
<Â Â Â Â Â Â  enum mpls-tp-pwe-eid {
---
 >Â Â Â Â Â Â  enum "mpls-tp-pwe-eid" {
226,227c191
<
<Â Â Â Â Â Â  enum mt-v4 {
---
 >Â Â Â Â Â Â  enum "mt-v4" {
232,237c196
<
<
<
<
<
<Â Â Â Â Â Â  enum mt-v6 {
---
 >Â Â Â Â Â Â  enum "mt-v6" {
242,243c201
<
<Â Â Â Â Â Â  enum eigrp-common-sf {
---
 >Â Â Â Â Â Â  enum "eigrp-common-sf" {
249,250c207
<
<Â Â Â Â Â Â  enum eigrp-v4-sf {
---
 >Â Â Â Â Â Â  enum "eigrp-v4-sf" {
255,256c212
<
<Â Â Â Â Â Â  enum eigrp-v6-sf {
---
 >Â Â Â Â Â Â  enum "eigrp-v6-sf" {
261,262c217
<
<Â Â Â Â Â Â  enum lcaf {
---
 >Â Â Â Â Â Â  enum "lcaf" {
268,269c223
<
<Â Â Â Â Â Â  enum bgp-ls {
---
 >Â Â Â Â Â Â  enum "bgp-ls" {
275,276c229
<
<Â Â Â Â Â Â  enum mac-48 {
---
 >Â Â Â Â Â Â  enum "mac-48" {
281,285c234
<
<
<
<
<Â Â Â Â Â Â  enum mac-64 {
---
 >Â Â Â Â Â Â  enum "mac-64" {
290,291c239
<
<Â Â Â Â Â Â  enum trill-oui {
---
 >Â Â Â Â Â Â  enum "trill-oui" {
298,299c246
<
<Â Â Â Â Â Â  enum trill-mac-24 {
---
 >Â Â Â Â Â Â  enum "trill-mac-24" {
304,305c251
<
<Â Â Â Â Â Â  enum trill-mac-40 {
---
 >Â Â Â Â Â Â  enum "trill-mac-40" {
310,311c256
<
<Â Â Â Â Â Â  enum ipv6-64 {
---
 >Â Â Â Â Â Â  enum "ipv6-64" {
317,318c262
<
<Â Â Â Â Â Â  enum trill-rbridge-port-id {
---
 >Â Â Â Â Â Â  enum "trill-rbridge-port-id" {
323,324c267
<
<Â Â Â Â Â Â  enum trill-nickname {
---
 >Â Â Â Â Â Â  enum "trill-nickname" {
330,332d272
<
<
<
336d275
<
339,341d277
<Â Â  /*** Subsequent Address Family Identifiers (SAFIs) ***/
<Â Â  /*** for multiprotocol BGP enumeration ***/
<
344c280
<Â Â Â Â Â Â  enum unicast-safi {
---
 >Â Â Â Â Â Â  enum "unicast-safi" {
349,350c285
<
<Â Â Â Â Â Â  enum multicast-safi {
---
 >Â Â Â Â Â Â  enum "multicast-safi" {
355,356c290
<
<Â Â Â Â Â Â  enum labeled-unicast-safi {
---
 >Â Â Â Â Â Â  enum "labeled-unicast-safi" {
361,362c295
<
<Â Â Â Â Â Â  enum multicast-vpn-safi {
---
 >Â Â Â Â Â Â  enum "multicast-vpn-safi" {
367,368c300
<
<Â Â Â Â Â Â  enum pseudowire-safi {
---
 >Â Â Â Â Â Â  enum "pseudowire-safi" {
373,374c305
<
<Â Â Â Â Â Â  enum tunnel-encap-safi {
---
 >Â Â Â Â Â Â  enum "tunnel-encap-safi" {
379,381c310
<
<
<Â Â Â Â Â Â  enum mcast-vpls-safi {
---
 >Â Â Â Â Â Â  enum "mcast-vpls-safi" {
386,387c315
<
<Â Â Â Â Â Â  enum tunnel-safi {
---
 >Â Â Â Â Â Â  enum "tunnel-safi" {
392,393c320
<
<Â Â Â Â Â Â  enum vpls-safi {
---
 >Â Â Â Â Â Â  enum "vpls-safi" {
398,399c325
<
<Â Â Â Â Â Â  enum mdt-safi {
---
 >Â Â Â Â Â Â  enum "mdt-safi" {
404,405c330
<
<Â Â Â Â Â Â  enum v4-over-v6-safi {
---
 >Â Â Â Â Â Â  enum "v4-over-v6-safi" {
410,411c335
<
<Â Â Â Â Â Â  enum v6-over-v4-safi {
---
 >Â Â Â Â Â Â  enum "v6-over-v4-safi" {
416,417c340
<
<Â Â Â Â Â Â  enum l1-vpn-auto-discovery-safi {
---
 >Â Â Â Â Â Â  enum "l1-vpn-auto-discovery-safi" {
422,423c345
<
<Â Â Â Â Â Â  enum evpn-safi {
---
 >Â Â Â Â Â Â  enum "evpn-safi" {
428,429c350
<
<Â Â Â Â Â Â  enum bgp-ls-safi {
---
 >Â Â Â Â Â Â  enum "bgp-ls-safi" {
434,435c355
<
<Â Â Â Â Â Â  enum bgp-ls-vpn-safi {
---
 >Â Â Â Â Â Â  enum "bgp-ls-vpn-safi" {
440,441c360
<
<Â Â Â Â Â Â  enum sr-te-safi {
---
 >Â Â Â Â Â Â  enum "sr-te-safi" {
446,447c365
<
<Â Â Â Â Â Â  enum labeled-vpn-safi {
---
 >Â Â Â Â Â Â  enum "labeled-vpn-safi" {
452,453c370
<
<Â Â Â Â Â Â  enum multicast-mpls-vpn-safi {
---
 >Â Â Â Â Â Â  enum "multicast-mpls-vpn-safi" {
458,459c375
<
<Â Â Â Â Â Â  enum route-target-safi {
---
 >Â Â Â Â Â Â  enum "route-target-safi" {
464,465c380
<
<Â Â Â Â Â Â  enum ipv4-flow-spec-safi {
---
 >Â Â Â Â Â Â  enum "ipv4-flow-spec-safi" {
470,471c385
<
<Â Â Â Â Â Â  enum vpnv4-flow-spec-safi {
---
 >Â Â Â Â Â Â  enum "vpnv4-flow-spec-safi" {
476,477c390
<
<Â Â Â Â Â Â  enum vpn-auto-discovery-safi {
---
 >Â Â Â Â Â Â  enum "vpn-auto-discovery-safi" {
485,486c398
<Â Â Â Â  reference
<Â Â Â Â Â Â  "RFC 4760: Multiprotocol Extensions for BGP-4.";
---
 >Â Â Â Â  reference "RFC 4760: Multiprotocol Extensions for BGP-4.";
bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$

pyang -f yang does more than the formatting, it adds double quotes to 
enum, remove comments, and potentially does more (I don't know what I 
don't know).

So here is the question: do we agree that the IANA, as source of truth 
for YANG modules, should apply pyang -f format before posting a YANG module?

Bonus question: if the double quotes for enum is the best solution, 
should it be a warning in validators?

Regards, Benoit








--------------FDA221772A340BA9107D141A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Dear all,<br>
    <br>
    We can say that the RFC is the source of truth but devops people
    "play" about YANG modules.<br>
    I'm trying to have a single source of truth for the repository of
    RFC-produced YANG modules, while we have multiple ones now.<br>
    <br>
    IMO, it should be IANA.Â  We've discussing this option with RFC
    editor and IANA:
    <a class="moz-txt-link-freetext" href="https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml">https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml</a>
    is being transformed in that direction.<br>
    The end goal is that end users, wanted to be up-to-date with the
    latest RFC-produced YANG modules, would perform a cron job such as:<br>
    Â Â Â  rsync -avz --delete rsync.ietf.org::iana/yang-parameters .<br>
    <br>
    Note: especially interested for IANA-maintained YANG modules such as
    iana-if-type<br>
    <br>
    Now the follow-up question from IANA:<br>
    <blockquote>
      <p class="MsoNormal"><span style="font-size:11.0pt">We were
          working on the posting of the yang modules for <u><a
href="https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/">draft-ietf-rtgwg-routing-types</a></u>
          per our new process.Â  When requesting the final files from the
          RFC-Editor, the file they extracted using their tool and the
          yang modules appear to have a lot of blank space in them.Â  See
          attached</span></p>
      <span style="font-size:11.0pt">Is this OK?Â  Do we post it as it is
        in the provided file from the RFC-Editor?Â  We know that there is
        some sensitivity to spacing in these files so we want to make
        sure the correct thing is being posted.</span></blockquote>
    The solution should be: pyang -f yang ... <br>
    However, after some testing:<br>
    <br>
    bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang
    -f yang <a class="moz-txt-link-abbreviated" href="mailto:iana-routing-types@2017-12-04.yang">iana-routing-types@2017-12-04.yang</a> &gt; newfile.yang<br>
    bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
    <a class="moz-txt-link-abbreviated" href="mailto:iana-routing-types@2017-12-04.yang">iana-routing-types@2017-12-04.yang</a> newfile.yang<br>
    16d15<br>
    &lt; <br>
    35,39c34,39<br>
    &lt;Â Â Â  revision 2017-12-04 {<br>
    &lt;Â Â Â Â Â  description "Initial revision.";<br>
    &lt;Â Â Â Â Â  reference<br>
    &lt;Â Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.<br>
    &lt;Â Â Â Â Â Â Â Â  Section 4.";<br>
    ---<br>
    &gt;Â Â  revision 2017-12-04 {<br>
    &gt;Â Â Â Â  description<br>
    &gt;Â Â Â Â Â Â  "Initial revision.";<br>
    &gt;Â Â Â Â  reference<br>
    &gt;Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.<br>
    &gt;Â Â Â Â Â Â Â  Section 4.";<br>
    42,47d41<br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt;Â Â  /*** Collection of IANA types related to routing ***/<br>
    &lt;Â Â  /*** IANA Address Family enumeration ***/<br>
    &lt; <br>
    50c44<br>
    &lt;Â Â Â Â Â Â  enum ipv4 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "ipv4" {<br>
    55,56c49<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum ipv6 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "ipv6" {<br>
    61,62c54<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum nsap {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "nsap" {<br>
    67,68c59<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum hdlc {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "hdlc" {<br>
    73,74c64<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum bbn1822 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "bbn1822" {<br>
    80,81c70<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum ieee802 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "ieee802" {<br>
    87,88c76<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum e163 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "e163" {<br>
    93c81<br>
    &lt;Â Â Â Â Â Â  enum e164 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "e164" {<br>
    99,100c87<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum f69 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "f69" {<br>
    105,106c92<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum x121 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "x121" {<br>
    111,112c97<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum ipx {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "ipx" {<br>
    118,119c103<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum appletalk {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "appletalk" {<br>
    124,125c108<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum decnet-iv {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "decnet-iv" {<br>
    130,131c113<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum vines {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "vines" {<br>
    136,141c118<br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum e164-nsap {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "e164-nsap" {<br>
    146,147c123<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum dns {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "dns" {<br>
    152,153c128<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum distinguished-name {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "distinguished-name" {<br>
    158,159c133<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum as-num {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "as-num" {<br>
    164,165c138<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum xtp-v4 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "xtp-v4" {<br>
    171,172c144<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum xtp-v6 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "xtp-v6" {<br>
    177,178c149<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum xtp-native {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "xtp-native" {<br>
    183,184c154<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum fc-port {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "fc-port" {<br>
    189c159<br>
    &lt;Â Â Â Â Â Â  enum fc-node {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "fc-node" {<br>
    194,195c164<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum gwid {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "gwid" {<br>
    200,201c169<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum l2vpn {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "l2vpn" {<br>
    206,207c174<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mpls-tp-section-eid {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mpls-tp-section-eid" {<br>
    213,214c180<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mpls-tp-lsp-eid {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mpls-tp-lsp-eid" {<br>
    220,221c186<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mpls-tp-pwe-eid {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mpls-tp-pwe-eid" {<br>
    226,227c191<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mt-v4 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mt-v4" {<br>
    232,237c196<br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mt-v6 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mt-v6" {<br>
    242,243c201<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum eigrp-common-sf {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "eigrp-common-sf" {<br>
    249,250c207<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum eigrp-v4-sf {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "eigrp-v4-sf" {<br>
    255,256c212<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum eigrp-v6-sf {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "eigrp-v6-sf" {<br>
    261,262c217<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum lcaf {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "lcaf" {<br>
    268,269c223<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum bgp-ls {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "bgp-ls" {<br>
    275,276c229<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mac-48 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mac-48" {<br>
    281,285c234<br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mac-64 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mac-64" {<br>
    290,291c239<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum trill-oui {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "trill-oui" {<br>
    298,299c246<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum trill-mac-24 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "trill-mac-24" {<br>
    304,305c251<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum trill-mac-40 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "trill-mac-40" {<br>
    310,311c256<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum ipv6-64 {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "ipv6-64" {<br>
    317,318c262<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum trill-rbridge-port-id {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "trill-rbridge-port-id" {<br>
    323,324c267<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum trill-nickname {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "trill-nickname" {<br>
    330,332d272<br>
    &lt; <br>
    &lt; <br>
    &lt; <br>
    336d275<br>
    &lt; <br>
    339,341d277<br>
    &lt;Â Â  /*** Subsequent Address Family Identifiers (SAFIs) ***/<br>
    &lt;Â Â  /*** for multiprotocol BGP enumeration ***/<br>
    &lt; <br>
    344c280<br>
    &lt;Â Â Â Â Â Â  enum unicast-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "unicast-safi" {<br>
    349,350c285<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum multicast-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "multicast-safi" {<br>
    355,356c290<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum labeled-unicast-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "labeled-unicast-safi" {<br>
    361,362c295<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum multicast-vpn-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "multicast-vpn-safi" {<br>
    367,368c300<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum pseudowire-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "pseudowire-safi" {<br>
    373,374c305<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum tunnel-encap-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "tunnel-encap-safi" {<br>
    379,381c310<br>
    &lt; <br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mcast-vpls-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mcast-vpls-safi" {<br>
    386,387c315<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum tunnel-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "tunnel-safi" {<br>
    392,393c320<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum vpls-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "vpls-safi" {<br>
    398,399c325<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum mdt-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "mdt-safi" {<br>
    404,405c330<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum v4-over-v6-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "v4-over-v6-safi" {<br>
    410,411c335<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum v6-over-v4-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "v6-over-v4-safi" {<br>
    416,417c340<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum l1-vpn-auto-discovery-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "l1-vpn-auto-discovery-safi" {<br>
    422,423c345<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum evpn-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "evpn-safi" {<br>
    428,429c350<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum bgp-ls-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "bgp-ls-safi" {<br>
    434,435c355<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum bgp-ls-vpn-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "bgp-ls-vpn-safi" {<br>
    440,441c360<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum sr-te-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "sr-te-safi" {<br>
    446,447c365<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum labeled-vpn-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "labeled-vpn-safi" {<br>
    452,453c370<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum multicast-mpls-vpn-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "multicast-mpls-vpn-safi" {<br>
    458,459c375<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum route-target-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "route-target-safi" {<br>
    464,465c380<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum ipv4-flow-spec-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "ipv4-flow-spec-safi" {<br>
    470,471c385<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum vpnv4-flow-spec-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "vpnv4-flow-spec-safi" {<br>
    476,477c390<br>
    &lt; <br>
    &lt;Â Â Â Â Â Â  enum vpn-auto-discovery-safi {<br>
    ---<br>
    &gt;Â Â Â Â Â Â  enum "vpn-auto-discovery-safi" {<br>
    485,486c398<br>
    &lt;Â Â Â Â  reference<br>
    &lt;Â Â Â Â Â Â  "RFC 4760: Multiprotocol Extensions for BGP-4.";<br>
    ---<br>
    &gt;Â Â Â Â  reference "RFC 4760: Multiprotocol Extensions for BGP-4.";<br>
    bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ <br>
    <br>
    pyang -f yang does more than the formatting, it adds double quotes
    to enum, remove comments, and potentially does more (I don't know
    what I don't know).<br>
    <br>
    So here is the question: do we agree that the IANA, as source of
    truth for YANG modules, should apply pyang -f format before posting
    a YANG module?<br>
    <br>
    Bonus question: if the double quotes for enum is the best solution,
    should it be a warning in validators?<br>
    <br>
    Regards, Benoit<br>
    Â Â Â  <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------FDA221772A340BA9107D141A--


From nobody Thu Jan  4 04:07:36 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0B1127275 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 04:07:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 dWj3zoi8tUZ0 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 04:07:29 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41E7012711A for <yang-doctors@ietf.org>; Thu,  4 Jan 2018 04:07:23 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 68AD03D; Thu,  4 Jan 2018 13:07:21 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id O9_u7ktTrHhR; Thu,  4 Jan 2018 13:07:20 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu,  4 Jan 2018 13:07:21 +0100 (CET)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 50C7120132; Thu,  4 Jan 2018 13:07:21 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 2FiXHZDJrbcC; Thu,  4 Jan 2018 13:07:20 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 80C4920131; Thu,  4 Jan 2018 13:07:19 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 3AB724203BA8; Thu,  4 Jan 2018 13:07:18 +0100 (CET)
Date: Thu, 4 Jan 2018 13:07:18 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, Michelle Cotton <michelle.cotton@icann.org>, sabrina.tanamal@iana.org, amanda.baber@iana.org
Message-ID: <20180104120718.qs5ak4r4yvn52etf@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, YANG Doctors <yang-doctors@ietf.org>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>,  "Joe Clarke (jclarke)" <jclarke@cisco.com>, Michelle Cotton <michelle.cotton@icann.org>, sabrina.tanamal@iana.org, amanda.baber@iana.org
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/eQsF3A44tXIDxMuRK8rKikHXK3o>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 12:07:34 -0000

We never managed to get this working for MIB modules but perhaps
things are working out this time. If you go for it, make sure there is
proper version control behind the solution. You will have to deal with
erratas that need to be applied etc. and clearly IANA needs to update
their modules.

/js

On Thu, Jan 04, 2018 at 12:12:52PM +0100, Benoit Claise wrote:
> Dear all,
> 
> We can say that the RFC is the source of truth but devops people "play"
> about YANG modules.
> I'm trying to have a single source of truth for the repository of
> RFC-produced YANG modules, while we have multiple ones now.
> 
> IMO, it should be IANA.  We've discussing this option with RFC editor and
> IANA: https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
> is being transformed in that direction.
> The end goal is that end users, wanted to be up-to-date with the latest
> RFC-produced YANG modules, would perform a cron job such as:
>     rsync -avz --delete rsync.ietf.org::iana/yang-parameters .
> 
> Note: especially interested for IANA-maintained YANG modules such as
> iana-if-type
> 
> Now the follow-up question from IANA:
> 
>    We were working on the posting of the yang modules for
>    _draft-ietf-rtgwg-routing-types
>    <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/>_
>    per our new process.  When requesting the final files from the
>    RFC-Editor, the file they extracted using their tool and the yang
>    modules appear to have a lot of blank space in them.  See attached
> 
>    Is this OK?  Do we post it as it is in the provided file from the
>    RFC-Editor?  We know that there is some sensitivity to spacing in
>    these files so we want to make sure the correct thing is being posted.
> 
> The solution should be: pyang -f yang ...
> However, after some testing:
> 
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang -f yang
> iana-routing-types@2017-12-04.yang > newfile.yang
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
> iana-routing-types@2017-12-04.yang newfile.yang
> 16d15
> <
> 35,39c34,39
> <    revision 2017-12-04 {
> <      description "Initial revision.";
> <      reference
> <        "RFC 8294: Common YANG Data Types for the Routing Area.
> <         Section 4.";
> ---
> >   revision 2017-12-04 {
> >     description
> >       "Initial revision.";
> >     reference
> >       "RFC 8294: Common YANG Data Types for the Routing Area.
> >        Section 4.";
> 42,47d41
> <
> <
> <
> <   /*** Collection of IANA types related to routing ***/
> <   /*** IANA Address Family enumeration ***/
> <
> 50c44
> <       enum ipv4 {
> ---
> >       enum "ipv4" {
> 55,56c49
> <
> <       enum ipv6 {
> ---
> >       enum "ipv6" {
> 61,62c54
> <
> <       enum nsap {
> ---
> >       enum "nsap" {
> 67,68c59
> <
> <       enum hdlc {
> ---
> >       enum "hdlc" {
> 73,74c64
> <
> <       enum bbn1822 {
> ---
> >       enum "bbn1822" {
> 80,81c70
> <
> <       enum ieee802 {
> ---
> >       enum "ieee802" {
> 87,88c76
> <
> <       enum e163 {
> ---
> >       enum "e163" {
> 93c81
> <       enum e164 {
> ---
> >       enum "e164" {
> 99,100c87
> <
> <       enum f69 {
> ---
> >       enum "f69" {
> 105,106c92
> <
> <       enum x121 {
> ---
> >       enum "x121" {
> 111,112c97
> <
> <       enum ipx {
> ---
> >       enum "ipx" {
> 118,119c103
> <
> <       enum appletalk {
> ---
> >       enum "appletalk" {
> 124,125c108
> <
> <       enum decnet-iv {
> ---
> >       enum "decnet-iv" {
> 130,131c113
> <
> <       enum vines {
> ---
> >       enum "vines" {
> 136,141c118
> <
> <
> <
> <
> <
> <       enum e164-nsap {
> ---
> >       enum "e164-nsap" {
> 146,147c123
> <
> <       enum dns {
> ---
> >       enum "dns" {
> 152,153c128
> <
> <       enum distinguished-name {
> ---
> >       enum "distinguished-name" {
> 158,159c133
> <
> <       enum as-num {
> ---
> >       enum "as-num" {
> 164,165c138
> <
> <       enum xtp-v4 {
> ---
> >       enum "xtp-v4" {
> 171,172c144
> <
> <       enum xtp-v6 {
> ---
> >       enum "xtp-v6" {
> 177,178c149
> <
> <       enum xtp-native {
> ---
> >       enum "xtp-native" {
> 183,184c154
> <
> <       enum fc-port {
> ---
> >       enum "fc-port" {
> 189c159
> <       enum fc-node {
> ---
> >       enum "fc-node" {
> 194,195c164
> <
> <       enum gwid {
> ---
> >       enum "gwid" {
> 200,201c169
> <
> <       enum l2vpn {
> ---
> >       enum "l2vpn" {
> 206,207c174
> <
> <       enum mpls-tp-section-eid {
> ---
> >       enum "mpls-tp-section-eid" {
> 213,214c180
> <
> <       enum mpls-tp-lsp-eid {
> ---
> >       enum "mpls-tp-lsp-eid" {
> 220,221c186
> <
> <       enum mpls-tp-pwe-eid {
> ---
> >       enum "mpls-tp-pwe-eid" {
> 226,227c191
> <
> <       enum mt-v4 {
> ---
> >       enum "mt-v4" {
> 232,237c196
> <
> <
> <
> <
> <
> <       enum mt-v6 {
> ---
> >       enum "mt-v6" {
> 242,243c201
> <
> <       enum eigrp-common-sf {
> ---
> >       enum "eigrp-common-sf" {
> 249,250c207
> <
> <       enum eigrp-v4-sf {
> ---
> >       enum "eigrp-v4-sf" {
> 255,256c212
> <
> <       enum eigrp-v6-sf {
> ---
> >       enum "eigrp-v6-sf" {
> 261,262c217
> <
> <       enum lcaf {
> ---
> >       enum "lcaf" {
> 268,269c223
> <
> <       enum bgp-ls {
> ---
> >       enum "bgp-ls" {
> 275,276c229
> <
> <       enum mac-48 {
> ---
> >       enum "mac-48" {
> 281,285c234
> <
> <
> <
> <
> <       enum mac-64 {
> ---
> >       enum "mac-64" {
> 290,291c239
> <
> <       enum trill-oui {
> ---
> >       enum "trill-oui" {
> 298,299c246
> <
> <       enum trill-mac-24 {
> ---
> >       enum "trill-mac-24" {
> 304,305c251
> <
> <       enum trill-mac-40 {
> ---
> >       enum "trill-mac-40" {
> 310,311c256
> <
> <       enum ipv6-64 {
> ---
> >       enum "ipv6-64" {
> 317,318c262
> <
> <       enum trill-rbridge-port-id {
> ---
> >       enum "trill-rbridge-port-id" {
> 323,324c267
> <
> <       enum trill-nickname {
> ---
> >       enum "trill-nickname" {
> 330,332d272
> <
> <
> <
> 336d275
> <
> 339,341d277
> <   /*** Subsequent Address Family Identifiers (SAFIs) ***/
> <   /*** for multiprotocol BGP enumeration ***/
> <
> 344c280
> <       enum unicast-safi {
> ---
> >       enum "unicast-safi" {
> 349,350c285
> <
> <       enum multicast-safi {
> ---
> >       enum "multicast-safi" {
> 355,356c290
> <
> <       enum labeled-unicast-safi {
> ---
> >       enum "labeled-unicast-safi" {
> 361,362c295
> <
> <       enum multicast-vpn-safi {
> ---
> >       enum "multicast-vpn-safi" {
> 367,368c300
> <
> <       enum pseudowire-safi {
> ---
> >       enum "pseudowire-safi" {
> 373,374c305
> <
> <       enum tunnel-encap-safi {
> ---
> >       enum "tunnel-encap-safi" {
> 379,381c310
> <
> <
> <       enum mcast-vpls-safi {
> ---
> >       enum "mcast-vpls-safi" {
> 386,387c315
> <
> <       enum tunnel-safi {
> ---
> >       enum "tunnel-safi" {
> 392,393c320
> <
> <       enum vpls-safi {
> ---
> >       enum "vpls-safi" {
> 398,399c325
> <
> <       enum mdt-safi {
> ---
> >       enum "mdt-safi" {
> 404,405c330
> <
> <       enum v4-over-v6-safi {
> ---
> >       enum "v4-over-v6-safi" {
> 410,411c335
> <
> <       enum v6-over-v4-safi {
> ---
> >       enum "v6-over-v4-safi" {
> 416,417c340
> <
> <       enum l1-vpn-auto-discovery-safi {
> ---
> >       enum "l1-vpn-auto-discovery-safi" {
> 422,423c345
> <
> <       enum evpn-safi {
> ---
> >       enum "evpn-safi" {
> 428,429c350
> <
> <       enum bgp-ls-safi {
> ---
> >       enum "bgp-ls-safi" {
> 434,435c355
> <
> <       enum bgp-ls-vpn-safi {
> ---
> >       enum "bgp-ls-vpn-safi" {
> 440,441c360
> <
> <       enum sr-te-safi {
> ---
> >       enum "sr-te-safi" {
> 446,447c365
> <
> <       enum labeled-vpn-safi {
> ---
> >       enum "labeled-vpn-safi" {
> 452,453c370
> <
> <       enum multicast-mpls-vpn-safi {
> ---
> >       enum "multicast-mpls-vpn-safi" {
> 458,459c375
> <
> <       enum route-target-safi {
> ---
> >       enum "route-target-safi" {
> 464,465c380
> <
> <       enum ipv4-flow-spec-safi {
> ---
> >       enum "ipv4-flow-spec-safi" {
> 470,471c385
> <
> <       enum vpnv4-flow-spec-safi {
> ---
> >       enum "vpnv4-flow-spec-safi" {
> 476,477c390
> <
> <       enum vpn-auto-discovery-safi {
> ---
> >       enum "vpn-auto-discovery-safi" {
> 485,486c398
> <     reference
> <       "RFC 4760: Multiprotocol Extensions for BGP-4.";
> ---
> >     reference "RFC 4760: Multiprotocol Extensions for BGP-4.";
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$
> 
> pyang -f yang does more than the formatting, it adds double quotes to enum,
> remove comments, and potentially does more (I don't know what I don't know).
> 
> So here is the question: do we agree that the IANA, as source of truth for
> YANG modules, should apply pyang -f format before posting a YANG module?
> 
> Bonus question: if the double quotes for enum is the best solution, should
> it be a warning in validators?
> 
> Regards, Benoit
> 
> 
> 
> 
> 
> 
> 

> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors


-- 
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/>


From nobody Thu Jan  4 04:53:48 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA3312751F for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 04:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, 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
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 U8xDiH-XoIOF for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 04:53:44 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D1B612702E for <yang-doctors@ietf.org>; Thu,  4 Jan 2018 04:53:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11432; q=dns/txt; s=iport; t=1515070424; x=1516280024; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=kpzV4Vi1krXrC/K8TyJD/pN7tS85dPq9FHmCG44gPTM=; b=Q7D3oSIFGg8I/9uSf3Ufx55noZZ1Jorrj3ue/NvvNhbqcpfWvGSjfQYZ lnXyRelwssIqALFgo6+9L86Z9BTUklLIdznXsNUhgijBVvU81llh+EQBc u7Z47b8oEqsbA4XOQWaCo9S3VEeq80lfANsMkiGVx70FWlIjhemZTuCHG U=;
X-IronPort-AV: E=Sophos;i="5.45,507,1508803200";  d="scan'208";a="1206861"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jan 2018 12:53:42 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w04Crgiu032192; Thu, 4 Jan 2018 12:53:42 GMT
To: YANG Doctors <yang-doctors@ietf.org>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, Michelle Cotton <michelle.cotton@icann.org>, sabrina.tanamal@iana.org, amanda.baber@iana.org
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <20180104120718.qs5ak4r4yvn52etf@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <b1822295-1cd0-5e8f-41bc-10ace94fd07a@cisco.com>
Date: Thu, 4 Jan 2018 13:53:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180104120718.qs5ak4r4yvn52etf@elstar.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/wXh3bCAK2cyj4kA4xK50-0w1p2g>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 12:53:46 -0000

Hi JÃ¼rgen,

There are multiple version control situations:
- IANA maintained YANG module, this is easy: there is a new revision. 
Ex: iana-routing-types
- YANG module bis + obsolete: the old YANG module should be hidden in 
IANA. Ex: ietf-l3vpn-svc
- YANG module bis + update: I don't believe faced the issue already.
- errata on the YANG module inside a RFC: this is looking for troubles 
IMO. To be decided on a case by case basis.

Regards, Benoit
> We never managed to get this working for MIB modules but perhaps
> things are working out this time. If you go for it, make sure there is
> proper version control behind the solution. You will have to deal with
> erratas that need to be applied etc. and clearly IANA needs to update
> their modules.
>
> /js
>
> On Thu, Jan 04, 2018 at 12:12:52PM +0100, Benoit Claise wrote:
>> Dear all,
>>
>> We can say that the RFC is the source of truth but devops people "play"
>> about YANG modules.
>> I'm trying to have a single source of truth for the repository of
>> RFC-produced YANG modules, while we have multiple ones now.
>>
>> IMO, it should be IANA.Â  We've discussing this option with RFC editor and
>> IANA: https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
>> is being transformed in that direction.
>> The end goal is that end users, wanted to be up-to-date with the latest
>> RFC-produced YANG modules, would perform a cron job such as:
>>  Â Â Â  rsync -avz --delete rsync.ietf.org::iana/yang-parameters .
>>
>> Note: especially interested for IANA-maintained YANG modules such as
>> iana-if-type
>>
>> Now the follow-up question from IANA:
>>
>>     We were working on the posting of the yang modules for
>>     _draft-ietf-rtgwg-routing-types
>>     <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/>_
>>     per our new process.Â  When requesting the final files from the
>>     RFC-Editor, the file they extracted using their tool and the yang
>>     modules appear to have a lot of blank space in them.Â  See attached
>>
>>     Is this OK?Â  Do we post it as it is in the provided file from the
>>     RFC-Editor?Â  We know that there is some sensitivity to spacing in
>>     these files so we want to make sure the correct thing is being posted.
>>
>> The solution should be: pyang -f yang ...
>> However, after some testing:
>>
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang -f yang
>> iana-routing-types@2017-12-04.yang > newfile.yang
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
>> iana-routing-types@2017-12-04.yang newfile.yang
>> 16d15
>> <
>> 35,39c34,39
>> <Â Â Â  revision 2017-12-04 {
>> <Â Â Â Â Â  description "Initial revision.";
>> <Â Â Â Â Â  reference
>> <Â Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.
>> <Â Â Â Â Â Â Â Â  Section 4.";
>> ---
>>>  Â Â  revision 2017-12-04 {
>>>  Â Â Â Â  description
>>>  Â Â Â Â Â Â  "Initial revision.";
>>>  Â Â Â Â  reference
>>>  Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.
>>>  Â Â Â Â Â Â Â  Section 4.";
>> 42,47d41
>> <
>> <
>> <
>> <Â Â  /*** Collection of IANA types related to routing ***/
>> <Â Â  /*** IANA Address Family enumeration ***/
>> <
>> 50c44
>> <Â Â Â Â Â Â  enum ipv4 {
>> ---
>>>  Â Â Â Â Â Â  enum "ipv4" {
>> 55,56c49
>> <
>> <Â Â Â Â Â Â  enum ipv6 {
>> ---
>>>  Â Â Â Â Â Â  enum "ipv6" {
>> 61,62c54
>> <
>> <Â Â Â Â Â Â  enum nsap {
>> ---
>>>  Â Â Â Â Â Â  enum "nsap" {
>> 67,68c59
>> <
>> <Â Â Â Â Â Â  enum hdlc {
>> ---
>>>  Â Â Â Â Â Â  enum "hdlc" {
>> 73,74c64
>> <
>> <Â Â Â Â Â Â  enum bbn1822 {
>> ---
>>>  Â Â Â Â Â Â  enum "bbn1822" {
>> 80,81c70
>> <
>> <Â Â Â Â Â Â  enum ieee802 {
>> ---
>>>  Â Â Â Â Â Â  enum "ieee802" {
>> 87,88c76
>> <
>> <Â Â Â Â Â Â  enum e163 {
>> ---
>>>  Â Â Â Â Â Â  enum "e163" {
>> 93c81
>> <Â Â Â Â Â Â  enum e164 {
>> ---
>>>  Â Â Â Â Â Â  enum "e164" {
>> 99,100c87
>> <
>> <Â Â Â Â Â Â  enum f69 {
>> ---
>>>  Â Â Â Â Â Â  enum "f69" {
>> 105,106c92
>> <
>> <Â Â Â Â Â Â  enum x121 {
>> ---
>>>  Â Â Â Â Â Â  enum "x121" {
>> 111,112c97
>> <
>> <Â Â Â Â Â Â  enum ipx {
>> ---
>>>  Â Â Â Â Â Â  enum "ipx" {
>> 118,119c103
>> <
>> <Â Â Â Â Â Â  enum appletalk {
>> ---
>>>  Â Â Â Â Â Â  enum "appletalk" {
>> 124,125c108
>> <
>> <Â Â Â Â Â Â  enum decnet-iv {
>> ---
>>>  Â Â Â Â Â Â  enum "decnet-iv" {
>> 130,131c113
>> <
>> <Â Â Â Â Â Â  enum vines {
>> ---
>>>  Â Â Â Â Â Â  enum "vines" {
>> 136,141c118
>> <
>> <
>> <
>> <
>> <
>> <Â Â Â Â Â Â  enum e164-nsap {
>> ---
>>>  Â Â Â Â Â Â  enum "e164-nsap" {
>> 146,147c123
>> <
>> <Â Â Â Â Â Â  enum dns {
>> ---
>>>  Â Â Â Â Â Â  enum "dns" {
>> 152,153c128
>> <
>> <Â Â Â Â Â Â  enum distinguished-name {
>> ---
>>>  Â Â Â Â Â Â  enum "distinguished-name" {
>> 158,159c133
>> <
>> <Â Â Â Â Â Â  enum as-num {
>> ---
>>>  Â Â Â Â Â Â  enum "as-num" {
>> 164,165c138
>> <
>> <Â Â Â Â Â Â  enum xtp-v4 {
>> ---
>>>  Â Â Â Â Â Â  enum "xtp-v4" {
>> 171,172c144
>> <
>> <Â Â Â Â Â Â  enum xtp-v6 {
>> ---
>>>  Â Â Â Â Â Â  enum "xtp-v6" {
>> 177,178c149
>> <
>> <Â Â Â Â Â Â  enum xtp-native {
>> ---
>>>  Â Â Â Â Â Â  enum "xtp-native" {
>> 183,184c154
>> <
>> <Â Â Â Â Â Â  enum fc-port {
>> ---
>>>  Â Â Â Â Â Â  enum "fc-port" {
>> 189c159
>> <Â Â Â Â Â Â  enum fc-node {
>> ---
>>>  Â Â Â Â Â Â  enum "fc-node" {
>> 194,195c164
>> <
>> <Â Â Â Â Â Â  enum gwid {
>> ---
>>>  Â Â Â Â Â Â  enum "gwid" {
>> 200,201c169
>> <
>> <Â Â Â Â Â Â  enum l2vpn {
>> ---
>>>  Â Â Â Â Â Â  enum "l2vpn" {
>> 206,207c174
>> <
>> <Â Â Â Â Â Â  enum mpls-tp-section-eid {
>> ---
>>>  Â Â Â Â Â Â  enum "mpls-tp-section-eid" {
>> 213,214c180
>> <
>> <Â Â Â Â Â Â  enum mpls-tp-lsp-eid {
>> ---
>>>  Â Â Â Â Â Â  enum "mpls-tp-lsp-eid" {
>> 220,221c186
>> <
>> <Â Â Â Â Â Â  enum mpls-tp-pwe-eid {
>> ---
>>>  Â Â Â Â Â Â  enum "mpls-tp-pwe-eid" {
>> 226,227c191
>> <
>> <Â Â Â Â Â Â  enum mt-v4 {
>> ---
>>>  Â Â Â Â Â Â  enum "mt-v4" {
>> 232,237c196
>> <
>> <
>> <
>> <
>> <
>> <Â Â Â Â Â Â  enum mt-v6 {
>> ---
>>>  Â Â Â Â Â Â  enum "mt-v6" {
>> 242,243c201
>> <
>> <Â Â Â Â Â Â  enum eigrp-common-sf {
>> ---
>>>  Â Â Â Â Â Â  enum "eigrp-common-sf" {
>> 249,250c207
>> <
>> <Â Â Â Â Â Â  enum eigrp-v4-sf {
>> ---
>>>  Â Â Â Â Â Â  enum "eigrp-v4-sf" {
>> 255,256c212
>> <
>> <Â Â Â Â Â Â  enum eigrp-v6-sf {
>> ---
>>>  Â Â Â Â Â Â  enum "eigrp-v6-sf" {
>> 261,262c217
>> <
>> <Â Â Â Â Â Â  enum lcaf {
>> ---
>>>  Â Â Â Â Â Â  enum "lcaf" {
>> 268,269c223
>> <
>> <Â Â Â Â Â Â  enum bgp-ls {
>> ---
>>>  Â Â Â Â Â Â  enum "bgp-ls" {
>> 275,276c229
>> <
>> <Â Â Â Â Â Â  enum mac-48 {
>> ---
>>>  Â Â Â Â Â Â  enum "mac-48" {
>> 281,285c234
>> <
>> <
>> <
>> <
>> <Â Â Â Â Â Â  enum mac-64 {
>> ---
>>>  Â Â Â Â Â Â  enum "mac-64" {
>> 290,291c239
>> <
>> <Â Â Â Â Â Â  enum trill-oui {
>> ---
>>>  Â Â Â Â Â Â  enum "trill-oui" {
>> 298,299c246
>> <
>> <Â Â Â Â Â Â  enum trill-mac-24 {
>> ---
>>>  Â Â Â Â Â Â  enum "trill-mac-24" {
>> 304,305c251
>> <
>> <Â Â Â Â Â Â  enum trill-mac-40 {
>> ---
>>>  Â Â Â Â Â Â  enum "trill-mac-40" {
>> 310,311c256
>> <
>> <Â Â Â Â Â Â  enum ipv6-64 {
>> ---
>>>  Â Â Â Â Â Â  enum "ipv6-64" {
>> 317,318c262
>> <
>> <Â Â Â Â Â Â  enum trill-rbridge-port-id {
>> ---
>>>  Â Â Â Â Â Â  enum "trill-rbridge-port-id" {
>> 323,324c267
>> <
>> <Â Â Â Â Â Â  enum trill-nickname {
>> ---
>>>  Â Â Â Â Â Â  enum "trill-nickname" {
>> 330,332d272
>> <
>> <
>> <
>> 336d275
>> <
>> 339,341d277
>> <Â Â  /*** Subsequent Address Family Identifiers (SAFIs) ***/
>> <Â Â  /*** for multiprotocol BGP enumeration ***/
>> <
>> 344c280
>> <Â Â Â Â Â Â  enum unicast-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "unicast-safi" {
>> 349,350c285
>> <
>> <Â Â Â Â Â Â  enum multicast-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "multicast-safi" {
>> 355,356c290
>> <
>> <Â Â Â Â Â Â  enum labeled-unicast-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "labeled-unicast-safi" {
>> 361,362c295
>> <
>> <Â Â Â Â Â Â  enum multicast-vpn-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "multicast-vpn-safi" {
>> 367,368c300
>> <
>> <Â Â Â Â Â Â  enum pseudowire-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "pseudowire-safi" {
>> 373,374c305
>> <
>> <Â Â Â Â Â Â  enum tunnel-encap-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "tunnel-encap-safi" {
>> 379,381c310
>> <
>> <
>> <Â Â Â Â Â Â  enum mcast-vpls-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "mcast-vpls-safi" {
>> 386,387c315
>> <
>> <Â Â Â Â Â Â  enum tunnel-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "tunnel-safi" {
>> 392,393c320
>> <
>> <Â Â Â Â Â Â  enum vpls-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "vpls-safi" {
>> 398,399c325
>> <
>> <Â Â Â Â Â Â  enum mdt-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "mdt-safi" {
>> 404,405c330
>> <
>> <Â Â Â Â Â Â  enum v4-over-v6-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "v4-over-v6-safi" {
>> 410,411c335
>> <
>> <Â Â Â Â Â Â  enum v6-over-v4-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "v6-over-v4-safi" {
>> 416,417c340
>> <
>> <Â Â Â Â Â Â  enum l1-vpn-auto-discovery-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "l1-vpn-auto-discovery-safi" {
>> 422,423c345
>> <
>> <Â Â Â Â Â Â  enum evpn-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "evpn-safi" {
>> 428,429c350
>> <
>> <Â Â Â Â Â Â  enum bgp-ls-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "bgp-ls-safi" {
>> 434,435c355
>> <
>> <Â Â Â Â Â Â  enum bgp-ls-vpn-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "bgp-ls-vpn-safi" {
>> 440,441c360
>> <
>> <Â Â Â Â Â Â  enum sr-te-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "sr-te-safi" {
>> 446,447c365
>> <
>> <Â Â Â Â Â Â  enum labeled-vpn-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "labeled-vpn-safi" {
>> 452,453c370
>> <
>> <Â Â Â Â Â Â  enum multicast-mpls-vpn-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "multicast-mpls-vpn-safi" {
>> 458,459c375
>> <
>> <Â Â Â Â Â Â  enum route-target-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "route-target-safi" {
>> 464,465c380
>> <
>> <Â Â Â Â Â Â  enum ipv4-flow-spec-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "ipv4-flow-spec-safi" {
>> 470,471c385
>> <
>> <Â Â Â Â Â Â  enum vpnv4-flow-spec-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "vpnv4-flow-spec-safi" {
>> 476,477c390
>> <
>> <Â Â Â Â Â Â  enum vpn-auto-discovery-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "vpn-auto-discovery-safi" {
>> 485,486c398
>> <Â Â Â Â  reference
>> <Â Â Â Â Â Â  "RFC 4760: Multiprotocol Extensions for BGP-4.";
>> ---
>>>  Â Â Â Â  reference "RFC 4760: Multiprotocol Extensions for BGP-4.";
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$
>>
>> pyang -f yang does more than the formatting, it adds double quotes to enum,
>> remove comments, and potentially does more (I don't know what I don't know).
>>
>> So here is the question: do we agree that the IANA, as source of truth for
>> YANG modules, should apply pyang -f format before posting a YANG module?
>>
>> Bonus question: if the double quotes for enum is the best solution, should
>> it be a warning in validators?
>>
>> Regards, Benoit
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> yang-doctors mailing list
>> yang-doctors@ietf.org
>> https://www.ietf.org/mailman/listinfo/yang-doctors
>


From nobody Thu Jan  4 05:29:11 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C57E12D7E5 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 05:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 pApzSja35kU7 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 05:29:05 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38BC2126CD6 for <yang-doctors@ietf.org>; Thu,  4 Jan 2018 05:29:05 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 073883D; Thu,  4 Jan 2018 14:29:04 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id XYVmCH6aQ6u7; Thu,  4 Jan 2018 14:29:03 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu,  4 Jan 2018 14:29:03 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id E5CFE2013D; Thu,  4 Jan 2018 14:29:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id pCQkdJBR2i7h; Thu,  4 Jan 2018 14:29:02 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 15FBE2013C; Thu,  4 Jan 2018 14:29:01 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 7FF7E4203D1E; Thu,  4 Jan 2018 14:29:01 +0100 (CET)
Date: Thu, 4 Jan 2018 14:29:01 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Cc: YANG Doctors <yang-doctors@ietf.org>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, Michelle Cotton <michelle.cotton@icann.org>, sabrina.tanamal@iana.org, amanda.baber@iana.org
Message-ID: <20180104132901.eskaiho5dvvmdenp@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, YANG Doctors <yang-doctors@ietf.org>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>,  "Joe Clarke (jclarke)" <jclarke@cisco.com>, Michelle Cotton <michelle.cotton@icann.org>, sabrina.tanamal@iana.org, amanda.baber@iana.org
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <20180104120718.qs5ak4r4yvn52etf@elstar.local> <b1822295-1cd0-5e8f-41bc-10ace94fd07a@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <b1822295-1cd0-5e8f-41bc-10ace94fd07a@cisco.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/QdYce0eRX7HrEx4H9ZyxlMOjnfw>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 13:29:08 -0000

I know that the IETF/IANA is resisting to adopt proper version control
systems in their official processes but having maintained a large
collection of RFC MIB modules over many years, I know that it is damn
good to be able to go back in order to understand why and when a
change was made. Perhaps IANA is able to track all this using whatever
databases they are using. If not, there are well known solutions out
there these days...

/js

On Thu, Jan 04, 2018 at 01:53:42PM +0100, Benoit Claise wrote:
> Hi Jürgen,
> 
> There are multiple version control situations:
> - IANA maintained YANG module, this is easy: there is a new revision. Ex:
> iana-routing-types
> - YANG module bis + obsolete: the old YANG module should be hidden in IANA.
> Ex: ietf-l3vpn-svc
> - YANG module bis + update: I don't believe faced the issue already.
> - errata on the YANG module inside a RFC: this is looking for troubles IMO.
> To be decided on a case by case basis.
> 
> Regards, Benoit
> > We never managed to get this working for MIB modules but perhaps
> > things are working out this time. If you go for it, make sure there is
> > proper version control behind the solution. You will have to deal with
> > erratas that need to be applied etc. and clearly IANA needs to update
> > their modules.
> > 
> > /js
> > 
> > On Thu, Jan 04, 2018 at 12:12:52PM +0100, Benoit Claise wrote:
> > > Dear all,
> > > 
> > > We can say that the RFC is the source of truth but devops people "play"
> > > about YANG modules.
> > > I'm trying to have a single source of truth for the repository of
> > > RFC-produced YANG modules, while we have multiple ones now.
> > > 
> > > IMO, it should be IANA.  We've discussing this option with RFC editor and
> > > IANA: https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
> > > is being transformed in that direction.
> > > The end goal is that end users, wanted to be up-to-date with the latest
> > > RFC-produced YANG modules, would perform a cron job such as:
> > >      rsync -avz --delete rsync.ietf.org::iana/yang-parameters .
> > > 
> > > Note: especially interested for IANA-maintained YANG modules such as
> > > iana-if-type
> > > 
> > > Now the follow-up question from IANA:
> > > 
> > >     We were working on the posting of the yang modules for
> > >     _draft-ietf-rtgwg-routing-types
> > >     <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/>_
> > >     per our new process.  When requesting the final files from the
> > >     RFC-Editor, the file they extracted using their tool and the yang
> > >     modules appear to have a lot of blank space in them.  See attached
> > > 
> > >     Is this OK?  Do we post it as it is in the provided file from the
> > >     RFC-Editor?  We know that there is some sensitivity to spacing in
> > >     these files so we want to make sure the correct thing is being posted.
> > > 
> > > The solution should be: pyang -f yang ...
> > > However, after some testing:
> > > 
> > > bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang -f yang
> > > iana-routing-types@2017-12-04.yang > newfile.yang
> > > bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
> > > iana-routing-types@2017-12-04.yang newfile.yang
> > > 16d15
> > > <
> > > 35,39c34,39
> > > <    revision 2017-12-04 {
> > > <      description "Initial revision.";
> > > <      reference
> > > <        "RFC 8294: Common YANG Data Types for the Routing Area.
> > > <         Section 4.";
> > > ---
> > > >     revision 2017-12-04 {
> > > >       description
> > > >         "Initial revision.";
> > > >       reference
> > > >         "RFC 8294: Common YANG Data Types for the Routing Area.
> > > >          Section 4.";
> > > 42,47d41
> > > <
> > > <
> > > <
> > > <   /*** Collection of IANA types related to routing ***/
> > > <   /*** IANA Address Family enumeration ***/
> > > <
> > > 50c44
> > > <       enum ipv4 {
> > > ---
> > > >         enum "ipv4" {
> > > 55,56c49
> > > <
> > > <       enum ipv6 {
> > > ---
> > > >         enum "ipv6" {
> > > 61,62c54
> > > <
> > > <       enum nsap {
> > > ---
> > > >         enum "nsap" {
> > > 67,68c59
> > > <
> > > <       enum hdlc {
> > > ---
> > > >         enum "hdlc" {
> > > 73,74c64
> > > <
> > > <       enum bbn1822 {
> > > ---
> > > >         enum "bbn1822" {
> > > 80,81c70
> > > <
> > > <       enum ieee802 {
> > > ---
> > > >         enum "ieee802" {
> > > 87,88c76
> > > <
> > > <       enum e163 {
> > > ---
> > > >         enum "e163" {
> > > 93c81
> > > <       enum e164 {
> > > ---
> > > >         enum "e164" {
> > > 99,100c87
> > > <
> > > <       enum f69 {
> > > ---
> > > >         enum "f69" {
> > > 105,106c92
> > > <
> > > <       enum x121 {
> > > ---
> > > >         enum "x121" {
> > > 111,112c97
> > > <
> > > <       enum ipx {
> > > ---
> > > >         enum "ipx" {
> > > 118,119c103
> > > <
> > > <       enum appletalk {
> > > ---
> > > >         enum "appletalk" {
> > > 124,125c108
> > > <
> > > <       enum decnet-iv {
> > > ---
> > > >         enum "decnet-iv" {
> > > 130,131c113
> > > <
> > > <       enum vines {
> > > ---
> > > >         enum "vines" {
> > > 136,141c118
> > > <
> > > <
> > > <
> > > <
> > > <
> > > <       enum e164-nsap {
> > > ---
> > > >         enum "e164-nsap" {
> > > 146,147c123
> > > <
> > > <       enum dns {
> > > ---
> > > >         enum "dns" {
> > > 152,153c128
> > > <
> > > <       enum distinguished-name {
> > > ---
> > > >         enum "distinguished-name" {
> > > 158,159c133
> > > <
> > > <       enum as-num {
> > > ---
> > > >         enum "as-num" {
> > > 164,165c138
> > > <
> > > <       enum xtp-v4 {
> > > ---
> > > >         enum "xtp-v4" {
> > > 171,172c144
> > > <
> > > <       enum xtp-v6 {
> > > ---
> > > >         enum "xtp-v6" {
> > > 177,178c149
> > > <
> > > <       enum xtp-native {
> > > ---
> > > >         enum "xtp-native" {
> > > 183,184c154
> > > <
> > > <       enum fc-port {
> > > ---
> > > >         enum "fc-port" {
> > > 189c159
> > > <       enum fc-node {
> > > ---
> > > >         enum "fc-node" {
> > > 194,195c164
> > > <
> > > <       enum gwid {
> > > ---
> > > >         enum "gwid" {
> > > 200,201c169
> > > <
> > > <       enum l2vpn {
> > > ---
> > > >         enum "l2vpn" {
> > > 206,207c174
> > > <
> > > <       enum mpls-tp-section-eid {
> > > ---
> > > >         enum "mpls-tp-section-eid" {
> > > 213,214c180
> > > <
> > > <       enum mpls-tp-lsp-eid {
> > > ---
> > > >         enum "mpls-tp-lsp-eid" {
> > > 220,221c186
> > > <
> > > <       enum mpls-tp-pwe-eid {
> > > ---
> > > >         enum "mpls-tp-pwe-eid" {
> > > 226,227c191
> > > <
> > > <       enum mt-v4 {
> > > ---
> > > >         enum "mt-v4" {
> > > 232,237c196
> > > <
> > > <
> > > <
> > > <
> > > <
> > > <       enum mt-v6 {
> > > ---
> > > >         enum "mt-v6" {
> > > 242,243c201
> > > <
> > > <       enum eigrp-common-sf {
> > > ---
> > > >         enum "eigrp-common-sf" {
> > > 249,250c207
> > > <
> > > <       enum eigrp-v4-sf {
> > > ---
> > > >         enum "eigrp-v4-sf" {
> > > 255,256c212
> > > <
> > > <       enum eigrp-v6-sf {
> > > ---
> > > >         enum "eigrp-v6-sf" {
> > > 261,262c217
> > > <
> > > <       enum lcaf {
> > > ---
> > > >         enum "lcaf" {
> > > 268,269c223
> > > <
> > > <       enum bgp-ls {
> > > ---
> > > >         enum "bgp-ls" {
> > > 275,276c229
> > > <
> > > <       enum mac-48 {
> > > ---
> > > >         enum "mac-48" {
> > > 281,285c234
> > > <
> > > <
> > > <
> > > <
> > > <       enum mac-64 {
> > > ---
> > > >         enum "mac-64" {
> > > 290,291c239
> > > <
> > > <       enum trill-oui {
> > > ---
> > > >         enum "trill-oui" {
> > > 298,299c246
> > > <
> > > <       enum trill-mac-24 {
> > > ---
> > > >         enum "trill-mac-24" {
> > > 304,305c251
> > > <
> > > <       enum trill-mac-40 {
> > > ---
> > > >         enum "trill-mac-40" {
> > > 310,311c256
> > > <
> > > <       enum ipv6-64 {
> > > ---
> > > >         enum "ipv6-64" {
> > > 317,318c262
> > > <
> > > <       enum trill-rbridge-port-id {
> > > ---
> > > >         enum "trill-rbridge-port-id" {
> > > 323,324c267
> > > <
> > > <       enum trill-nickname {
> > > ---
> > > >         enum "trill-nickname" {
> > > 330,332d272
> > > <
> > > <
> > > <
> > > 336d275
> > > <
> > > 339,341d277
> > > <   /*** Subsequent Address Family Identifiers (SAFIs) ***/
> > > <   /*** for multiprotocol BGP enumeration ***/
> > > <
> > > 344c280
> > > <       enum unicast-safi {
> > > ---
> > > >         enum "unicast-safi" {
> > > 349,350c285
> > > <
> > > <       enum multicast-safi {
> > > ---
> > > >         enum "multicast-safi" {
> > > 355,356c290
> > > <
> > > <       enum labeled-unicast-safi {
> > > ---
> > > >         enum "labeled-unicast-safi" {
> > > 361,362c295
> > > <
> > > <       enum multicast-vpn-safi {
> > > ---
> > > >         enum "multicast-vpn-safi" {
> > > 367,368c300
> > > <
> > > <       enum pseudowire-safi {
> > > ---
> > > >         enum "pseudowire-safi" {
> > > 373,374c305
> > > <
> > > <       enum tunnel-encap-safi {
> > > ---
> > > >         enum "tunnel-encap-safi" {
> > > 379,381c310
> > > <
> > > <
> > > <       enum mcast-vpls-safi {
> > > ---
> > > >         enum "mcast-vpls-safi" {
> > > 386,387c315
> > > <
> > > <       enum tunnel-safi {
> > > ---
> > > >         enum "tunnel-safi" {
> > > 392,393c320
> > > <
> > > <       enum vpls-safi {
> > > ---
> > > >         enum "vpls-safi" {
> > > 398,399c325
> > > <
> > > <       enum mdt-safi {
> > > ---
> > > >         enum "mdt-safi" {
> > > 404,405c330
> > > <
> > > <       enum v4-over-v6-safi {
> > > ---
> > > >         enum "v4-over-v6-safi" {
> > > 410,411c335
> > > <
> > > <       enum v6-over-v4-safi {
> > > ---
> > > >         enum "v6-over-v4-safi" {
> > > 416,417c340
> > > <
> > > <       enum l1-vpn-auto-discovery-safi {
> > > ---
> > > >         enum "l1-vpn-auto-discovery-safi" {
> > > 422,423c345
> > > <
> > > <       enum evpn-safi {
> > > ---
> > > >         enum "evpn-safi" {
> > > 428,429c350
> > > <
> > > <       enum bgp-ls-safi {
> > > ---
> > > >         enum "bgp-ls-safi" {
> > > 434,435c355
> > > <
> > > <       enum bgp-ls-vpn-safi {
> > > ---
> > > >         enum "bgp-ls-vpn-safi" {
> > > 440,441c360
> > > <
> > > <       enum sr-te-safi {
> > > ---
> > > >         enum "sr-te-safi" {
> > > 446,447c365
> > > <
> > > <       enum labeled-vpn-safi {
> > > ---
> > > >         enum "labeled-vpn-safi" {
> > > 452,453c370
> > > <
> > > <       enum multicast-mpls-vpn-safi {
> > > ---
> > > >         enum "multicast-mpls-vpn-safi" {
> > > 458,459c375
> > > <
> > > <       enum route-target-safi {
> > > ---
> > > >         enum "route-target-safi" {
> > > 464,465c380
> > > <
> > > <       enum ipv4-flow-spec-safi {
> > > ---
> > > >         enum "ipv4-flow-spec-safi" {
> > > 470,471c385
> > > <
> > > <       enum vpnv4-flow-spec-safi {
> > > ---
> > > >         enum "vpnv4-flow-spec-safi" {
> > > 476,477c390
> > > <
> > > <       enum vpn-auto-discovery-safi {
> > > ---
> > > >         enum "vpn-auto-discovery-safi" {
> > > 485,486c398
> > > <     reference
> > > <       "RFC 4760: Multiprotocol Extensions for BGP-4.";
> > > ---
> > > >       reference "RFC 4760: Multiprotocol Extensions for BGP-4.";
> > > bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$
> > > 
> > > pyang -f yang does more than the formatting, it adds double quotes to enum,
> > > remove comments, and potentially does more (I don't know what I don't know).
> > > 
> > > So here is the question: do we agree that the IANA, as source of truth for
> > > YANG modules, should apply pyang -f format before posting a YANG module?
> > > 
> > > Bonus question: if the double quotes for enum is the best solution, should
> > > it be a warning in validators?
> > > 
> > > Regards, Benoit
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > yang-doctors mailing list
> > > yang-doctors@ietf.org
> > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > 
> 
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

-- 
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/>


From nobody Thu Jan  4 06:10:23 2018
Return-Path: <rkrejci@cesnet.cz>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 832B512D86B; Thu,  4 Jan 2018 06:10:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?b?UmFkZWsgS3JlasSNw60=?= <rkrejci@cesnet.cz>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-netmod-entity.all@ietf.org, netmod@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151507502144.23798.1644071576333370968@ietfa.amsl.com>
Date: Thu, 04 Jan 2018 06:10:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/sOUKQS0aq__FQv-ml13wqULvXEE>
Subject: [yang-doctors] Yangdoctors last call review of draft-ietf-netmod-entity-07
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 14:10:21 -0000

Reviewer: Radek KrejÄ�Ã­
Review result: Ready with Issues

The document itself and normative parts seem fine to me, the only issue I see
is with the ietf-hardware-state module in non-normative appendix A. It seems to
me that this temporary non-NMDA module does not conform to its purpose as
described in RFC6087bis. According to guidelines, such a module is intended to
provide state (config false) data in case the server does not implement NMDA
(to bridge the time period until NMDA is implemented). So such a server is IMHO
intended to implement both modules, foo and foo-state. The foo-state contains
"the top-level config-false data nodes that would have been defined in a legacy
YANG module" - so it's only the ro mirror of data nodes. But
ietf-hardware-state contains notifications, which are not the data nodes as
defined in RFC7950. I understand why the notifications were placed also into
the ietf-hardware-state - the module's description states that "If a server
that implements this module but doesn't support NMDA also supports
configuration of hardware components, it SHOULD also implement the module
'ietf-hardware' ...", so it allows its standalone usage in case the server does
not support hw configuration. But in such a case, the server can implement
ietf-hardware with deviations on the config=true nodes. The same way it had to
implement the legacy YANG module (before NMDA).

So I think that the notifications should be removed from ietf-hardware-state
and the module's description should change this way:

OLD

  If a server that implements this module but doesn't support NMDA
  also supports configuration of hardware components, it SHOULD
  also implement the module 'ietf-hardware' in the configuration
  datastores. The corresponding state data is found in the
  '/hw-state:hardware' subtree.

NEW

  If a server that implements this module but doesn't support NMDA,
  it MUST also implement the module 'ietf-hardware' in the
  configuration datastores. The corresponding state data is found
  in the '/hw-state:hardware' subtree.



From nobody Thu Jan  4 08:40:58 2018
Return-Path: <mjethanandani@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97E112708C for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 08:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 u4OQtJrbLx36 for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 08:40:52 -0800 (PST)
Received: from mail-pl0-x232.google.com (mail-pl0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) (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 6197E126B7F for <yang-doctors@ietf.org>; Thu,  4 Jan 2018 08:40:52 -0800 (PST)
Received: by mail-pl0-x232.google.com with SMTP id g2so1317422pli.8 for <yang-doctors@ietf.org>; Thu, 04 Jan 2018 08:40:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=bi+1YsZphVggAdAOaD+IQi/o0x/77+iAcQVqIOoItQM=; b=V96+xdDRe5DXvuw8SFYNkMbWvUjl6Yfj+XlsOQMPgKKLc1RVrWR6Lzi7TDF5RpGJ5e 6VMY7uWd4v15ACCBSgbbsh+LRz0xEIfs1vDf3lpuwhdIWe0yp7+w2OCk3K2sOVjV+9Y0 xcxhfpkPK8zIkYuxuxy2mXv3jEaP/ecaXqgXBDIPyPW45CwduUaj2JAj50ZAlBbUNyrx d5J7dewgWv0HS0uqI5G9EMxm8GFRSEPIxlEv35OwmPzOCcwsChOhGD5dh2R7H1luWd40 phYWmmBhOgqlpL6hC5PFpSR/0MLRA1dB5EJ41Y5EGrzqRiERIqIiABu5KUCzFagXiT9p C45Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=bi+1YsZphVggAdAOaD+IQi/o0x/77+iAcQVqIOoItQM=; b=oTFoaDsl/a4eZcKCixRuZqdjHFQ2untVwO7YusaKDGmAYVx9uL21QYIHtw8IU/iLtM 9pURORqENcm0CUAzQjWZEt9Zbh7ADczgLWuTS9PDxxjS2c4zMwjpQutAq4Etq7tQvU0u nS5VE8U40sgeaGmLDn8Co3jMWTV21nTnwqJoNKwOj8aF+ms0u+SOO/D08omGShDQxE/a XGmh4sqLjGapzsYQNy0L7C9PL7BjHTDPt7mAcC7vJ6cAkdI2oDk6xP+ZKI0BuFX2ztCE JOmvQnPvO0A5icf5AMp+NRCAIRBd+1Vf514J/1qFPL+NObasHpJUsNdCobUhTxCkqdhx Nx3Q==
X-Gm-Message-State: AKGB3mLhW5F633IeFr/vVI8WFmadRUWAclXDBSQwwSNqL++I6F5jyjvK wU56PBUuKjw8OAIyaOqtjVc=
X-Google-Smtp-Source: ACJfBouYf48Ss+sqKKuRHbRVonnkq/lUlI6lcr8MMbXhYEUsj+90EZ6KJN2SqBH9Tf9VumRVXXgZBw==
X-Received: by 10.159.245.133 with SMTP id a5mr124839pls.251.1515084051889; Thu, 04 Jan 2018 08:40:51 -0800 (PST)
Received: from mahesh-m-m8d1.attlocal.net ([2600:1700:edb0:8fd0:8d20:c187:9df:3c3f]) by smtp.gmail.com with ESMTPSA id d68sm8941220pfl.38.2018.01.04.08.40.45 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Jan 2018 08:40:51 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_D7CAC8BA-B773-48F7-B93C-FD4FFD76A2C7"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
Date: Thu, 4 Jan 2018 07:35:08 -0800
Cc: YANG Doctors <yang-doctors@ietf.org>, "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, Michelle Cotton <michelle.cotton@icann.org>, sabrina.tanamal@iana.org, amanda.baber@iana.org
Message-Id: <0766646B-7D4C-4BA9-B4B0-CCB553D954CA@gmail.com>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/k-1fKw4nkHyjUZbyceMBvT_2Q0k>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 16:40:55 -0000

--Apple-Mail=_D7CAC8BA-B773-48F7-B93C-FD4FFD76A2C7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Benoit,

Agree that pyang -f should strip the whitespace and do pretty =
formatting. But none of the examples in RFC 7950 show enum with =
double-quotes.

> On Jan 4, 2018, at 3:12 AM, Benoit Claise <bclaise@cisco.com> wrote:
>=20
> Dear all,
>=20
> We can say that the RFC is the source of truth but devops people =
"play" about YANG modules.
> I'm trying to have a single source of truth for the repository of =
RFC-produced YANG modules, while we have multiple ones now.
>=20
> IMO, it should be IANA.  We've discussing this option with RFC editor =
and IANA: =
https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml =
<https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml> =
is being transformed in that direction.
> The end goal is that end users, wanted to be up-to-date with the =
latest RFC-produced YANG modules, would perform a cron job such as:
>     rsync -avz --delete rsync.ietf.org::iana/yang-parameters .
>=20
> Note: especially interested for IANA-maintained YANG modules such as =
iana-if-type
>=20
> Now the follow-up question from IANA:
> We were working on the posting of the yang modules for =
draft-ietf-rtgwg-routing-types =
<https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/> =
per our new process.  When requesting the final files from the =
RFC-Editor, the file they extracted using their tool and the yang =
modules appear to have a lot of blank space in them.  See attached
>=20
> Is this OK?  Do we post it as it is in the provided file from the =
RFC-Editor?  We know that there is some sensitivity to spacing in these =
files so we want to make sure the correct thing is being posted.
> The solution should be: pyang -f yang ...=20
> However, after some testing:
>=20
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang =
-f yang iana-routing-types@2017-12-04.yang =
<mailto:iana-routing-types@2017-12-04.yang> > newfile.yang
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff =
iana-routing-types@2017-12-04.yang =
<mailto:iana-routing-types@2017-12-04.yang> newfile.yang
> 16d15
> <=20
> 35,39c34,39
> <    revision 2017-12-04 {
> <      description "Initial revision.";
> <      reference
> <        "RFC 8294: Common YANG Data Types for the Routing Area.
> <         Section 4.";
> ---
> >   revision 2017-12-04 {
> >     description
> >       "Initial revision.";
> >     reference
> >       "RFC 8294: Common YANG Data Types for the Routing Area.
> >        Section 4.";
> 42,47d41
> <=20
> <=20
> <=20
> <   /*** Collection of IANA types related to routing ***/
> <   /*** IANA Address Family enumeration ***/
> <=20
> 50c44
> <       enum ipv4 {
> ---
> >       enum "ipv4" {
> 55,56c49
> <=20
> <       enum ipv6 {
> ---
> >       enum "ipv6" {
> 61,62c54
> <=20
> <       enum nsap {
> ---
> >       enum "nsap" {
> 67,68c59
> <=20
> <       enum hdlc {
> ---
> >       enum "hdlc" {
> 73,74c64
> <=20
> <       enum bbn1822 {
> ---
> >       enum "bbn1822" {
> 80,81c70
> <=20
> <       enum ieee802 {
> ---
> >       enum "ieee802" {
> 87,88c76
> <=20
> <       enum e163 {
> ---
> >       enum "e163" {
> 93c81
> <       enum e164 {
> ---
> >       enum "e164" {
> 99,100c87
> <=20
> <       enum f69 {
> ---
> >       enum "f69" {
> 105,106c92
> <=20
> <       enum x121 {
> ---
> >       enum "x121" {
> 111,112c97
> <=20
> <       enum ipx {
> ---
> >       enum "ipx" {
> 118,119c103
> <=20
> <       enum appletalk {
> ---
> >       enum "appletalk" {
> 124,125c108
> <=20
> <       enum decnet-iv {
> ---
> >       enum "decnet-iv" {
> 130,131c113
> <=20
> <       enum vines {
> ---
> >       enum "vines" {
> 136,141c118
> <=20
> <=20
> <=20
> <=20
> <=20
> <       enum e164-nsap {
> ---
> >       enum "e164-nsap" {
> 146,147c123
> <=20
> <       enum dns {
> ---
> >       enum "dns" {
> 152,153c128
> <=20
> <       enum distinguished-name {
> ---
> >       enum "distinguished-name" {
> 158,159c133
> <=20
> <       enum as-num {
> ---
> >       enum "as-num" {
> 164,165c138
> <=20
> <       enum xtp-v4 {
> ---
> >       enum "xtp-v4" {
> 171,172c144
> <=20
> <       enum xtp-v6 {
> ---
> >       enum "xtp-v6" {
> 177,178c149
> <=20
> <       enum xtp-native {
> ---
> >       enum "xtp-native" {
> 183,184c154
> <=20
> <       enum fc-port {
> ---
> >       enum "fc-port" {
> 189c159
> <       enum fc-node {
> ---
> >       enum "fc-node" {
> 194,195c164
> <=20
> <       enum gwid {
> ---
> >       enum "gwid" {
> 200,201c169
> <=20
> <       enum l2vpn {
> ---
> >       enum "l2vpn" {
> 206,207c174
> <=20
> <       enum mpls-tp-section-eid {
> ---
> >       enum "mpls-tp-section-eid" {
> 213,214c180
> <=20
> <       enum mpls-tp-lsp-eid {
> ---
> >       enum "mpls-tp-lsp-eid" {
> 220,221c186
> <=20
> <       enum mpls-tp-pwe-eid {
> ---
> >       enum "mpls-tp-pwe-eid" {
> 226,227c191
> <=20
> <       enum mt-v4 {
> ---
> >       enum "mt-v4" {
> 232,237c196
> <=20
> <=20
> <=20
> <=20
> <=20
> <       enum mt-v6 {
> ---
> >       enum "mt-v6" {
> 242,243c201
> <=20
> <       enum eigrp-common-sf {
> ---
> >       enum "eigrp-common-sf" {
> 249,250c207
> <=20
> <       enum eigrp-v4-sf {
> ---
> >       enum "eigrp-v4-sf" {
> 255,256c212
> <=20
> <       enum eigrp-v6-sf {
> ---
> >       enum "eigrp-v6-sf" {
> 261,262c217
> <=20
> <       enum lcaf {
> ---
> >       enum "lcaf" {
> 268,269c223
> <=20
> <       enum bgp-ls {
> ---
> >       enum "bgp-ls" {
> 275,276c229
> <=20
> <       enum mac-48 {
> ---
> >       enum "mac-48" {
> 281,285c234
> <=20
> <=20
> <=20
> <=20
> <       enum mac-64 {
> ---
> >       enum "mac-64" {
> 290,291c239
> <=20
> <       enum trill-oui {
> ---
> >       enum "trill-oui" {
> 298,299c246
> <=20
> <       enum trill-mac-24 {
> ---
> >       enum "trill-mac-24" {
> 304,305c251
> <=20
> <       enum trill-mac-40 {
> ---
> >       enum "trill-mac-40" {
> 310,311c256
> <=20
> <       enum ipv6-64 {
> ---
> >       enum "ipv6-64" {
> 317,318c262
> <=20
> <       enum trill-rbridge-port-id {
> ---
> >       enum "trill-rbridge-port-id" {
> 323,324c267
> <=20
> <       enum trill-nickname {
> ---
> >       enum "trill-nickname" {
> 330,332d272
> <=20
> <=20
> <=20
> 336d275
> <=20
> 339,341d277
> <   /*** Subsequent Address Family Identifiers (SAFIs) ***/
> <   /*** for multiprotocol BGP enumeration ***/
> <=20
> 344c280
> <       enum unicast-safi {
> ---
> >       enum "unicast-safi" {
> 349,350c285
> <=20
> <       enum multicast-safi {
> ---
> >       enum "multicast-safi" {
> 355,356c290
> <=20
> <       enum labeled-unicast-safi {
> ---
> >       enum "labeled-unicast-safi" {
> 361,362c295
> <=20
> <       enum multicast-vpn-safi {
> ---
> >       enum "multicast-vpn-safi" {
> 367,368c300
> <=20
> <       enum pseudowire-safi {
> ---
> >       enum "pseudowire-safi" {
> 373,374c305
> <=20
> <       enum tunnel-encap-safi {
> ---
> >       enum "tunnel-encap-safi" {
> 379,381c310
> <=20
> <=20
> <       enum mcast-vpls-safi {
> ---
> >       enum "mcast-vpls-safi" {
> 386,387c315
> <=20
> <       enum tunnel-safi {
> ---
> >       enum "tunnel-safi" {
> 392,393c320
> <=20
> <       enum vpls-safi {
> ---
> >       enum "vpls-safi" {
> 398,399c325
> <=20
> <       enum mdt-safi {
> ---
> >       enum "mdt-safi" {
> 404,405c330
> <=20
> <       enum v4-over-v6-safi {
> ---
> >       enum "v4-over-v6-safi" {
> 410,411c335
> <=20
> <       enum v6-over-v4-safi {
> ---
> >       enum "v6-over-v4-safi" {
> 416,417c340
> <=20
> <       enum l1-vpn-auto-discovery-safi {
> ---
> >       enum "l1-vpn-auto-discovery-safi" {
> 422,423c345
> <=20
> <       enum evpn-safi {
> ---
> >       enum "evpn-safi" {
> 428,429c350
> <=20
> <       enum bgp-ls-safi {
> ---
> >       enum "bgp-ls-safi" {
> 434,435c355
> <=20
> <       enum bgp-ls-vpn-safi {
> ---
> >       enum "bgp-ls-vpn-safi" {
> 440,441c360
> <=20
> <       enum sr-te-safi {
> ---
> >       enum "sr-te-safi" {
> 446,447c365
> <=20
> <       enum labeled-vpn-safi {
> ---
> >       enum "labeled-vpn-safi" {
> 452,453c370
> <=20
> <       enum multicast-mpls-vpn-safi {
> ---
> >       enum "multicast-mpls-vpn-safi" {
> 458,459c375
> <=20
> <       enum route-target-safi {
> ---
> >       enum "route-target-safi" {
> 464,465c380
> <=20
> <       enum ipv4-flow-spec-safi {
> ---
> >       enum "ipv4-flow-spec-safi" {
> 470,471c385
> <=20
> <       enum vpnv4-flow-spec-safi {
> ---
> >       enum "vpnv4-flow-spec-safi" {
> 476,477c390
> <=20
> <       enum vpn-auto-discovery-safi {
> ---
> >       enum "vpn-auto-discovery-safi" {
> 485,486c398
> <     reference
> <       "RFC 4760: Multiprotocol Extensions for BGP-4.";
> ---
> >     reference "RFC 4760: Multiprotocol Extensions for BGP-4.";
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$=20
>=20
> pyang -f yang does more than the formatting, it adds double quotes to =
enum, remove comments, and potentially does more (I don't know what I =
don't know).
>=20
> So here is the question: do we agree that the IANA, as source of truth =
for YANG modules, should apply pyang -f format before posting a YANG =
module?
>=20
> Bonus question: if the double quotes for enum is the best solution, =
should it be a warning in validators?
>=20
> Regards, Benoit
>    =20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

Mahesh Jethanandani
mjethanandani@gmail.com


--Apple-Mail=_D7CAC8BA-B773-48F7-B93C-FD4FFD76A2C7
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Benoit,<div class=""><br class=""></div><div class="">Agree that pyang -f should strip the whitespace and do pretty formatting. But none of the examples in RFC 7950 show enum with double-quotes.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 4, 2018, at 3:12 AM, Benoit Claise &lt;<a href="mailto:bclaise@cisco.com" class="">bclaise@cisco.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class="">
  

    <meta http-equiv="content-type" content="text/html; charset=utf-8" class="">
  
  <div text="#000000" bgcolor="#FFFFFF" class="">
    Dear all,<br class="">
    <br class="">
    We can say that the RFC is the source of truth but devops people
    "play" about YANG modules.<br class="">
    I'm trying to have a single source of truth for the repository of
    RFC-produced YANG modules, while we have multiple ones now.<br class="">
    <br class="">
    IMO, it should be IANA.&nbsp; We've discussing this option with RFC
    editor and IANA:
    <a class="moz-txt-link-freetext" href="https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml">https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml</a>
    is being transformed in that direction.<br class="">
    The end goal is that end users, wanted to be up-to-date with the
    latest RFC-produced YANG modules, would perform a cron job such as:<br class="">
    &nbsp;&nbsp;&nbsp; rsync -avz --delete <a href="http://rsync.ietf.org" class="">rsync.ietf.org</a>::iana/yang-parameters .<br class="">
    <br class="">
    Note: especially interested for IANA-maintained YANG modules such as
    iana-if-type<br class="">
    <br class="">
    Now the follow-up question from IANA:<br class="">
    <blockquote class=""><p class="MsoNormal"><span style="font-size:11.0pt" class="">We were
          working on the posting of the yang modules for <u class=""><a href="https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/" class="">draft-ietf-rtgwg-routing-types</a></u>
          per our new process.&nbsp; When requesting the final files from the
          RFC-Editor, the file they extracted using their tool and the
          yang modules appear to have a lot of blank space in them.&nbsp; See
          attached</span></p>
      <span style="font-size:11.0pt" class="">Is this OK?&nbsp; Do we post it as it is
        in the provided file from the RFC-Editor?&nbsp; We know that there is
        some sensitivity to spacing in these files so we want to make
        sure the correct thing is being posted.</span></blockquote>
    The solution should be: pyang -f yang ... <br class="">
    However, after some testing:<br class="">
    <br class="">
    bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang
    -f yang <a class="moz-txt-link-abbreviated" href="mailto:iana-routing-types@2017-12-04.yang">iana-routing-types@2017-12-04.yang</a> &gt; newfile.yang<br class="">
    bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
    <a class="moz-txt-link-abbreviated" href="mailto:iana-routing-types@2017-12-04.yang">iana-routing-types@2017-12-04.yang</a> newfile.yang<br class="">
    16d15<br class="">
    &lt; <br class="">
    35,39c34,39<br class="">
    &lt;&nbsp;&nbsp;&nbsp; revision 2017-12-04 {<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; description "Initial revision.";<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; reference<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "RFC 8294: Common YANG Data Types for the Routing Area.<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 4.";<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp; revision 2017-12-04 {<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp; description<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "Initial revision.";<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp; reference<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "RFC 8294: Common YANG Data Types for the Routing Area.<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 4.";<br class="">
    42,47d41<br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp; /*** Collection of IANA types related to routing ***/<br class="">
    &lt;&nbsp;&nbsp; /*** IANA Address Family enumeration ***/<br class="">
    &lt; <br class="">
    50c44<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum ipv4 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "ipv4" {<br class="">
    55,56c49<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum ipv6 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "ipv6" {<br class="">
    61,62c54<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum nsap {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "nsap" {<br class="">
    67,68c59<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum hdlc {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "hdlc" {<br class="">
    73,74c64<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum bbn1822 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "bbn1822" {<br class="">
    80,81c70<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum ieee802 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "ieee802" {<br class="">
    87,88c76<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum e163 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "e163" {<br class="">
    93c81<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum e164 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "e164" {<br class="">
    99,100c87<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum f69 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "f69" {<br class="">
    105,106c92<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum x121 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "x121" {<br class="">
    111,112c97<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum ipx {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "ipx" {<br class="">
    118,119c103<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum appletalk {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "appletalk" {<br class="">
    124,125c108<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum decnet-iv {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "decnet-iv" {<br class="">
    130,131c113<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum vines {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "vines" {<br class="">
    136,141c118<br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum e164-nsap {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "e164-nsap" {<br class="">
    146,147c123<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum dns {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "dns" {<br class="">
    152,153c128<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum distinguished-name {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "distinguished-name" {<br class="">
    158,159c133<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum as-num {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "as-num" {<br class="">
    164,165c138<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum xtp-v4 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "xtp-v4" {<br class="">
    171,172c144<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum xtp-v6 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "xtp-v6" {<br class="">
    177,178c149<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum xtp-native {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "xtp-native" {<br class="">
    183,184c154<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum fc-port {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "fc-port" {<br class="">
    189c159<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum fc-node {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "fc-node" {<br class="">
    194,195c164<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum gwid {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "gwid" {<br class="">
    200,201c169<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum l2vpn {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "l2vpn" {<br class="">
    206,207c174<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mpls-tp-section-eid {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mpls-tp-section-eid" {<br class="">
    213,214c180<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mpls-tp-lsp-eid {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mpls-tp-lsp-eid" {<br class="">
    220,221c186<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mpls-tp-pwe-eid {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mpls-tp-pwe-eid" {<br class="">
    226,227c191<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mt-v4 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mt-v4" {<br class="">
    232,237c196<br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mt-v6 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mt-v6" {<br class="">
    242,243c201<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum eigrp-common-sf {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "eigrp-common-sf" {<br class="">
    249,250c207<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum eigrp-v4-sf {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "eigrp-v4-sf" {<br class="">
    255,256c212<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum eigrp-v6-sf {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "eigrp-v6-sf" {<br class="">
    261,262c217<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum lcaf {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "lcaf" {<br class="">
    268,269c223<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum bgp-ls {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "bgp-ls" {<br class="">
    275,276c229<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mac-48 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mac-48" {<br class="">
    281,285c234<br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mac-64 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mac-64" {<br class="">
    290,291c239<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum trill-oui {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "trill-oui" {<br class="">
    298,299c246<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum trill-mac-24 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "trill-mac-24" {<br class="">
    304,305c251<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum trill-mac-40 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "trill-mac-40" {<br class="">
    310,311c256<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum ipv6-64 {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "ipv6-64" {<br class="">
    317,318c262<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum trill-rbridge-port-id {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "trill-rbridge-port-id" {<br class="">
    323,324c267<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum trill-nickname {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "trill-nickname" {<br class="">
    330,332d272<br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt; <br class="">
    336d275<br class="">
    &lt; <br class="">
    339,341d277<br class="">
    &lt;&nbsp;&nbsp; /*** Subsequent Address Family Identifiers (SAFIs) ***/<br class="">
    &lt;&nbsp;&nbsp; /*** for multiprotocol BGP enumeration ***/<br class="">
    &lt; <br class="">
    344c280<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum unicast-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "unicast-safi" {<br class="">
    349,350c285<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum multicast-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "multicast-safi" {<br class="">
    355,356c290<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum labeled-unicast-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "labeled-unicast-safi" {<br class="">
    361,362c295<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum multicast-vpn-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "multicast-vpn-safi" {<br class="">
    367,368c300<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum pseudowire-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "pseudowire-safi" {<br class="">
    373,374c305<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum tunnel-encap-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "tunnel-encap-safi" {<br class="">
    379,381c310<br class="">
    &lt; <br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mcast-vpls-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mcast-vpls-safi" {<br class="">
    386,387c315<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum tunnel-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "tunnel-safi" {<br class="">
    392,393c320<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum vpls-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "vpls-safi" {<br class="">
    398,399c325<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum mdt-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "mdt-safi" {<br class="">
    404,405c330<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum v4-over-v6-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "v4-over-v6-safi" {<br class="">
    410,411c335<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum v6-over-v4-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "v6-over-v4-safi" {<br class="">
    416,417c340<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum l1-vpn-auto-discovery-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "l1-vpn-auto-discovery-safi" {<br class="">
    422,423c345<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum evpn-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "evpn-safi" {<br class="">
    428,429c350<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum bgp-ls-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "bgp-ls-safi" {<br class="">
    434,435c355<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum bgp-ls-vpn-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "bgp-ls-vpn-safi" {<br class="">
    440,441c360<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum sr-te-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "sr-te-safi" {<br class="">
    446,447c365<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum labeled-vpn-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "labeled-vpn-safi" {<br class="">
    452,453c370<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum multicast-mpls-vpn-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "multicast-mpls-vpn-safi" {<br class="">
    458,459c375<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum route-target-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "route-target-safi" {<br class="">
    464,465c380<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum ipv4-flow-spec-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "ipv4-flow-spec-safi" {<br class="">
    470,471c385<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum vpnv4-flow-spec-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "vpnv4-flow-spec-safi" {<br class="">
    476,477c390<br class="">
    &lt; <br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum vpn-auto-discovery-safi {<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enum "vpn-auto-discovery-safi" {<br class="">
    485,486c398<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp; reference<br class="">
    &lt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "RFC 4760: Multiprotocol Extensions for BGP-4.";<br class="">
    ---<br class="">
    &gt;&nbsp;&nbsp;&nbsp;&nbsp; reference "RFC 4760: Multiprotocol Extensions for BGP-4.";<br class="">
    bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ <br class="">
    <br class="">
    pyang -f yang does more than the formatting, it adds double quotes
    to enum, remove comments, and potentially does more (I don't know
    what I don't know).<br class="">
    <br class="">
    So here is the question: do we agree that the IANA, as source of
    truth for YANG modules, should apply pyang -f format before posting
    a YANG module?<br class="">
    <br class="">
    Bonus question: if the double quotes for enum is the best solution,
    should it be a warning in validators?<br class="">
    <br class="">
    Regards, Benoit<br class="">
    &nbsp;&nbsp;&nbsp; <br class="">
    <br class="">
    <br class="">
    <br class="">
    <br class="">
    <br class="">
    <br class="">
  </div>

_______________________________________________<br class="">yang-doctors mailing list<br class=""><a href="mailto:yang-doctors@ietf.org" class="">yang-doctors@ietf.org</a><br class="">https://www.ietf.org/mailman/listinfo/yang-doctors<br class=""></div></blockquote></div><br class=""><div class="">
<div class="">Mahesh Jethanandani</div><div class=""><a href="mailto:mjethanandani@gmail.com" class="">mjethanandani@gmail.com</a></div>

</div>
<br class=""></div></div></body></html>
--Apple-Mail=_D7CAC8BA-B773-48F7-B93C-FD4FFD76A2C7--


From nobody Thu Jan  4 08:54:23 2018
Return-Path: <acee@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 792AA126B7F for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 08:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 TklIjbiNaVjh for <yang-doctors@ietfa.amsl.com>; Thu,  4 Jan 2018 08:54:18 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1132312711B for <yang-doctors@ietf.org>; Thu,  4 Jan 2018 08:54:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=45939; q=dns/txt; s=iport; t=1515084858; x=1516294458; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=LzbOv2wUR8IcnfCtYyBM/Anjiht997C3YI/PzVUgliE=; b=DLmgH3dH+Kn3DSh8NxMcONKO/bGtpjY2FqYwXDym426oeazYXbJoK+Ma sQ+fFixWttLbT+ozPB8VhYmdxsvQ28TtiY9eEsl/FRm/CxHVhzyTqc/gJ hjodrV5uZ7cT4EKRRIHKs+H5p4fyow2rta2SVfif2jUv50w9rjXULRzDL I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D8AACLW05a/5ldJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJKdGZ0JweEAIokjwiCAX2IC44iFIF+AwoYAQqFGAIahBo/GAE?= =?us-ascii?q?BAQEBAQEBAWsohSMBAQEBAwEBIUsLEAIBCA4DAwECIQEGAwICAh8GCxQJCAIEA?= =?us-ascii?q?Q0FG4kvTAMVELIDgicmhxoNgnABAQEBAQEBAQEBAQEBAQEBAQEBAQEdhBOCEoM?= =?us-ascii?q?/gng2gmtEAYE2WB6CWYJFIAWKboc1kHY9AogEiDWFAIJ8kQmNMT6IdAIRGQGBO?= =?us-ascii?q?wEPEDmBT28VPYIqCYJLBReBZ3gBhkosgQaBFgEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,314,1511827200";  d="scan'208,217";a="121282225"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Jan 2018 16:54:16 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w04GsFFZ002058 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Jan 2018 16:54:16 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 4 Jan 2018 11:54:11 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Thu, 4 Jan 2018 11:54:11 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
CC: "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, "sabrina.tanamal@iana.org" <sabrina.tanamal@iana.org>, "amanda.baber@iana.org" <amanda.baber@iana.org>, YANG Doctors <yang-doctors@ietf.org>, Michelle Cotton <michelle.cotton@icann.org>
Thread-Topic: [yang-doctors] YANG module & pyang -f yang & source of truth repository
Thread-Index: AQHThUz+DITYqtvd00SqlLtXxv7/KKNkLGsA///CPAA=
Date: Thu, 4 Jan 2018 16:54:11 +0000
Message-ID: <D673C621.E8591%acee@cisco.com>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <0766646B-7D4C-4BA9-B4B0-CCB553D954CA@gmail.com>
In-Reply-To: <0766646B-7D4C-4BA9-B4B0-CCB553D954CA@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_D673C621E8591aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/p8RRFbxO7MQPJ-pN4nwvhTBJMmg>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 16:54:21 -0000

--_000_D673C621E8591aceeciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgWUFORyBEb2N0b3JzLA0KDQpQZXJzb25hbGx5LCBJIGRvbuKAmXQgbGlrZSB0aGUgZG91Ymxl
IHF1b3Rpbmcgb2YgZW51bXMuDQoNClRoYW5rcywNCkFjZWUNCg0KRnJvbTogeWFuZy1kb2N0b3Jz
IDx5YW5nLWRvY3RvcnMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86eWFuZy1kb2N0b3JzLWJvdW5j
ZXNAaWV0Zi5vcmc+PiBvbiBiZWhhbGYgb2YgTWFoZXNoIEpldGhhbmFuZGFuaSA8bWpldGhhbmFu
ZGFuaUBnbWFpbC5jb208bWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tPj4NCkRhdGU6IFRo
dXJzZGF5LCBKYW51YXJ5IDQsIDIwMTggYXQgMTA6MzUgQU0NClRvOiAiQmVub2l0IENsYWlzZSAo
YmNsYWlzZSkiIDxiY2xhaXNlQGNpc2NvLmNvbTxtYWlsdG86YmNsYWlzZUBjaXNjby5jb20+Pg0K
Q2M6ICJNaXJvc2xhdiBLb3ZhYyAtWCAobWlya292YWMgLSBQQU5USEVPTiBURUNITk9MT0dJRVMg
YXQgQ2lzY28pIiA8bWlya292YWNAY2lzY28uY29tPG1haWx0bzptaXJrb3ZhY0BjaXNjby5jb20+
PiwgIkpvZSBDbGFya2UgKGpjbGFya2UpIiA8amNsYXJrZUBjaXNjby5jb208bWFpbHRvOmpjbGFy
a2VAY2lzY28uY29tPj4sICJzYWJyaW5hLnRhbmFtYWxAaWFuYS5vcmc8bWFpbHRvOnNhYnJpbmEu
dGFuYW1hbEBpYW5hLm9yZz4iIDxzYWJyaW5hLnRhbmFtYWxAaWFuYS5vcmc8bWFpbHRvOnNhYnJp
bmEudGFuYW1hbEBpYW5hLm9yZz4+LCAiYW1hbmRhLmJhYmVyQGlhbmEub3JnPG1haWx0bzphbWFu
ZGEuYmFiZXJAaWFuYS5vcmc+IiA8YW1hbmRhLmJhYmVyQGlhbmEub3JnPG1haWx0bzphbWFuZGEu
YmFiZXJAaWFuYS5vcmc+PiwgWUFORyBEb2N0b3JzIDx5YW5nLWRvY3RvcnNAaWV0Zi5vcmc8bWFp
bHRvOnlhbmctZG9jdG9yc0BpZXRmLm9yZz4+LCBNaWNoZWxsZSBDb3R0b24gPG1pY2hlbGxlLmNv
dHRvbkBpY2Fubi5vcmc8bWFpbHRvOm1pY2hlbGxlLmNvdHRvbkBpY2Fubi5vcmc+Pg0KU3ViamVj
dDogUmU6IFt5YW5nLWRvY3RvcnNdIFlBTkcgbW9kdWxlICYgcHlhbmcgLWYgeWFuZyAmIHNvdXJj
ZSBvZiB0cnV0aCByZXBvc2l0b3J5DQoNCkJlbm9pdCwNCg0KQWdyZWUgdGhhdCBweWFuZyAtZiBz
aG91bGQgc3RyaXAgdGhlIHdoaXRlc3BhY2UgYW5kIGRvIHByZXR0eSBmb3JtYXR0aW5nLiBCdXQg
bm9uZSBvZiB0aGUgZXhhbXBsZXMgaW4gUkZDIDc5NTAgc2hvdyBlbnVtIHdpdGggZG91YmxlLXF1
b3Rlcy4NCg0KT24gSmFuIDQsIDIwMTgsIGF0IDM6MTIgQU0sIEJlbm9pdCBDbGFpc2UgPGJjbGFp
c2VAY2lzY28uY29tPG1haWx0bzpiY2xhaXNlQGNpc2NvLmNvbT4+IHdyb3RlOg0KDQpEZWFyIGFs
bCwNCg0KV2UgY2FuIHNheSB0aGF0IHRoZSBSRkMgaXMgdGhlIHNvdXJjZSBvZiB0cnV0aCBidXQg
ZGV2b3BzIHBlb3BsZSAicGxheSIgYWJvdXQgWUFORyBtb2R1bGVzLg0KSSdtIHRyeWluZyB0byBo
YXZlIGEgc2luZ2xlIHNvdXJjZSBvZiB0cnV0aCBmb3IgdGhlIHJlcG9zaXRvcnkgb2YgUkZDLXBy
b2R1Y2VkIFlBTkcgbW9kdWxlcywgd2hpbGUgd2UgaGF2ZSBtdWx0aXBsZSBvbmVzIG5vdy4NCg0K
SU1PLCBpdCBzaG91bGQgYmUgSUFOQS4gIFdlJ3ZlIGRpc2N1c3NpbmcgdGhpcyBvcHRpb24gd2l0
aCBSRkMgZWRpdG9yIGFuZCBJQU5BOiBodHRwczovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy95
YW5nLXBhcmFtZXRlcnMveWFuZy1wYXJhbWV0ZXJzLnhodG1sIGlzIGJlaW5nIHRyYW5zZm9ybWVk
IGluIHRoYXQgZGlyZWN0aW9uLg0KVGhlIGVuZCBnb2FsIGlzIHRoYXQgZW5kIHVzZXJzLCB3YW50
ZWQgdG8gYmUgdXAtdG8tZGF0ZSB3aXRoIHRoZSBsYXRlc3QgUkZDLXByb2R1Y2VkIFlBTkcgbW9k
dWxlcywgd291bGQgcGVyZm9ybSBhIGNyb24gam9iIHN1Y2ggYXM6DQogICAgcnN5bmMgLWF2eiAt
LWRlbGV0ZSByc3luYy5pZXRmLm9yZzxodHRwOi8vcnN5bmMuaWV0Zi5vcmc+OjppYW5hL3lhbmct
cGFyYW1ldGVycyAuDQoNCk5vdGU6IGVzcGVjaWFsbHkgaW50ZXJlc3RlZCBmb3IgSUFOQS1tYWlu
dGFpbmVkIFlBTkcgbW9kdWxlcyBzdWNoIGFzIGlhbmEtaWYtdHlwZQ0KDQpOb3cgdGhlIGZvbGxv
dy11cCBxdWVzdGlvbiBmcm9tIElBTkE6DQpXZSB3ZXJlIHdvcmtpbmcgb24gdGhlIHBvc3Rpbmcg
b2YgdGhlIHlhbmcgbW9kdWxlcyBmb3IgZHJhZnQtaWV0Zi1ydGd3Zy1yb3V0aW5nLXR5cGVzPGh0
dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvaWR0cmFja2VyL2RyYWZ0LWlldGYtcnRnd2ctcm91
dGluZy10eXBlcy8+IHBlciBvdXIgbmV3IHByb2Nlc3MuICBXaGVuIHJlcXVlc3RpbmcgdGhlIGZp
bmFsIGZpbGVzIGZyb20gdGhlIFJGQy1FZGl0b3IsIHRoZSBmaWxlIHRoZXkgZXh0cmFjdGVkIHVz
aW5nIHRoZWlyIHRvb2wgYW5kIHRoZSB5YW5nIG1vZHVsZXMgYXBwZWFyIHRvIGhhdmUgYSBsb3Qg
b2YgYmxhbmsgc3BhY2UgaW4gdGhlbS4gIFNlZSBhdHRhY2hlZA0KSXMgdGhpcyBPSz8gIERvIHdl
IHBvc3QgaXQgYXMgaXQgaXMgaW4gdGhlIHByb3ZpZGVkIGZpbGUgZnJvbSB0aGUgUkZDLUVkaXRv
cj8gIFdlIGtub3cgdGhhdCB0aGVyZSBpcyBzb21lIHNlbnNpdGl2aXR5IHRvIHNwYWNpbmcgaW4g
dGhlc2UgZmlsZXMgc28gd2Ugd2FudCB0byBtYWtlIHN1cmUgdGhlIGNvcnJlY3QgdGhpbmcgaXMg
YmVpbmcgcG9zdGVkLg0KVGhlIHNvbHV0aW9uIHNob3VsZCBiZTogcHlhbmcgLWYgeWFuZyAuLi4N
Ckhvd2V2ZXIsIGFmdGVyIHNvbWUgdGVzdGluZzoNCg0KYmNsYWlzZUBiY2xhaXNlLVZpcnR1YWxC
b3g6L21lZGlhL3NmX3VidW50dS1zaGFyZS90b2JlcmVtb3ZlZCQgcHlhbmcgLWYgeWFuZyBpYW5h
LXJvdXRpbmctdHlwZXNAMjAxNy0xMi0wNC55YW5nPG1haWx0bzppYW5hLXJvdXRpbmctdHlwZXNA
MjAxNy0xMi0wNC55YW5nPiA+IG5ld2ZpbGUueWFuZw0KYmNsYWlzZUBiY2xhaXNlLVZpcnR1YWxC
b3g6L21lZGlhL3NmX3VidW50dS1zaGFyZS90b2JlcmVtb3ZlZCQgZGlmZiBpYW5hLXJvdXRpbmct
dHlwZXNAMjAxNy0xMi0wNC55YW5nPG1haWx0bzppYW5hLXJvdXRpbmctdHlwZXNAMjAxNy0xMi0w
NC55YW5nPiBuZXdmaWxlLnlhbmcNCjE2ZDE1DQo8DQozNSwzOWMzNCwzOQ0KPCAgICByZXZpc2lv
biAyMDE3LTEyLTA0IHsNCjwgICAgICBkZXNjcmlwdGlvbiAiSW5pdGlhbCByZXZpc2lvbi4iOw0K
PCAgICAgIHJlZmVyZW5jZQ0KPCAgICAgICAgIlJGQyA4Mjk0OiBDb21tb24gWUFORyBEYXRhIFR5
cGVzIGZvciB0aGUgUm91dGluZyBBcmVhLg0KPCAgICAgICAgIFNlY3Rpb24gNC4iOw0KLS0tDQo+
ICAgcmV2aXNpb24gMjAxNy0xMi0wNCB7DQo+ICAgICBkZXNjcmlwdGlvbg0KPiAgICAgICAiSW5p
dGlhbCByZXZpc2lvbi4iOw0KPiAgICAgcmVmZXJlbmNlDQo+ICAgICAgICJSRkMgODI5NDogQ29t
bW9uIFlBTkcgRGF0YSBUeXBlcyBmb3IgdGhlIFJvdXRpbmcgQXJlYS4NCj4gICAgICAgIFNlY3Rp
b24gNC4iOw0KNDIsNDdkNDENCjwNCjwNCjwNCjwgICAvKioqIENvbGxlY3Rpb24gb2YgSUFOQSB0
eXBlcyByZWxhdGVkIHRvIHJvdXRpbmcgKioqLw0KPCAgIC8qKiogSUFOQSBBZGRyZXNzIEZhbWls
eSBlbnVtZXJhdGlvbiAqKiovDQo8DQo1MGM0NA0KPCAgICAgICBlbnVtIGlwdjQgew0KLS0tDQo+
ICAgICAgIGVudW0gImlwdjQiIHsNCjU1LDU2YzQ5DQo8DQo8ICAgICAgIGVudW0gaXB2NiB7DQot
LS0NCj4gICAgICAgZW51bSAiaXB2NiIgew0KNjEsNjJjNTQNCjwNCjwgICAgICAgZW51bSBuc2Fw
IHsNCi0tLQ0KPiAgICAgICBlbnVtICJuc2FwIiB7DQo2Nyw2OGM1OQ0KPA0KPCAgICAgICBlbnVt
IGhkbGMgew0KLS0tDQo+ICAgICAgIGVudW0gImhkbGMiIHsNCjczLDc0YzY0DQo8DQo8ICAgICAg
IGVudW0gYmJuMTgyMiB7DQotLS0NCj4gICAgICAgZW51bSAiYmJuMTgyMiIgew0KODAsODFjNzAN
CjwNCjwgICAgICAgZW51bSBpZWVlODAyIHsNCi0tLQ0KPiAgICAgICBlbnVtICJpZWVlODAyIiB7
DQo4Nyw4OGM3Ng0KPA0KPCAgICAgICBlbnVtIGUxNjMgew0KLS0tDQo+ICAgICAgIGVudW0gImUx
NjMiIHsNCjkzYzgxDQo8ICAgICAgIGVudW0gZTE2NCB7DQotLS0NCj4gICAgICAgZW51bSAiZTE2
NCIgew0KOTksMTAwYzg3DQo8DQo8ICAgICAgIGVudW0gZjY5IHsNCi0tLQ0KPiAgICAgICBlbnVt
ICJmNjkiIHsNCjEwNSwxMDZjOTINCjwNCjwgICAgICAgZW51bSB4MTIxIHsNCi0tLQ0KPiAgICAg
ICBlbnVtICJ4MTIxIiB7DQoxMTEsMTEyYzk3DQo8DQo8ICAgICAgIGVudW0gaXB4IHsNCi0tLQ0K
PiAgICAgICBlbnVtICJpcHgiIHsNCjExOCwxMTljMTAzDQo8DQo8ICAgICAgIGVudW0gYXBwbGV0
YWxrIHsNCi0tLQ0KPiAgICAgICBlbnVtICJhcHBsZXRhbGsiIHsNCjEyNCwxMjVjMTA4DQo8DQo8
ICAgICAgIGVudW0gZGVjbmV0LWl2IHsNCi0tLQ0KPiAgICAgICBlbnVtICJkZWNuZXQtaXYiIHsN
CjEzMCwxMzFjMTEzDQo8DQo8ICAgICAgIGVudW0gdmluZXMgew0KLS0tDQo+ICAgICAgIGVudW0g
InZpbmVzIiB7DQoxMzYsMTQxYzExOA0KPA0KPA0KPA0KPA0KPA0KPCAgICAgICBlbnVtIGUxNjQt
bnNhcCB7DQotLS0NCj4gICAgICAgZW51bSAiZTE2NC1uc2FwIiB7DQoxNDYsMTQ3YzEyMw0KPA0K
PCAgICAgICBlbnVtIGRucyB7DQotLS0NCj4gICAgICAgZW51bSAiZG5zIiB7DQoxNTIsMTUzYzEy
OA0KPA0KPCAgICAgICBlbnVtIGRpc3Rpbmd1aXNoZWQtbmFtZSB7DQotLS0NCj4gICAgICAgZW51
bSAiZGlzdGluZ3Vpc2hlZC1uYW1lIiB7DQoxNTgsMTU5YzEzMw0KPA0KPCAgICAgICBlbnVtIGFz
LW51bSB7DQotLS0NCj4gICAgICAgZW51bSAiYXMtbnVtIiB7DQoxNjQsMTY1YzEzOA0KPA0KPCAg
ICAgICBlbnVtIHh0cC12NCB7DQotLS0NCj4gICAgICAgZW51bSAieHRwLXY0IiB7DQoxNzEsMTcy
YzE0NA0KPA0KPCAgICAgICBlbnVtIHh0cC12NiB7DQotLS0NCj4gICAgICAgZW51bSAieHRwLXY2
IiB7DQoxNzcsMTc4YzE0OQ0KPA0KPCAgICAgICBlbnVtIHh0cC1uYXRpdmUgew0KLS0tDQo+ICAg
ICAgIGVudW0gInh0cC1uYXRpdmUiIHsNCjE4MywxODRjMTU0DQo8DQo8ICAgICAgIGVudW0gZmMt
cG9ydCB7DQotLS0NCj4gICAgICAgZW51bSAiZmMtcG9ydCIgew0KMTg5YzE1OQ0KPCAgICAgICBl
bnVtIGZjLW5vZGUgew0KLS0tDQo+ICAgICAgIGVudW0gImZjLW5vZGUiIHsNCjE5NCwxOTVjMTY0
DQo8DQo8ICAgICAgIGVudW0gZ3dpZCB7DQotLS0NCj4gICAgICAgZW51bSAiZ3dpZCIgew0KMjAw
LDIwMWMxNjkNCjwNCjwgICAgICAgZW51bSBsMnZwbiB7DQotLS0NCj4gICAgICAgZW51bSAibDJ2
cG4iIHsNCjIwNiwyMDdjMTc0DQo8DQo8ICAgICAgIGVudW0gbXBscy10cC1zZWN0aW9uLWVpZCB7
DQotLS0NCj4gICAgICAgZW51bSAibXBscy10cC1zZWN0aW9uLWVpZCIgew0KMjEzLDIxNGMxODAN
CjwNCjwgICAgICAgZW51bSBtcGxzLXRwLWxzcC1laWQgew0KLS0tDQo+ICAgICAgIGVudW0gIm1w
bHMtdHAtbHNwLWVpZCIgew0KMjIwLDIyMWMxODYNCjwNCjwgICAgICAgZW51bSBtcGxzLXRwLXB3
ZS1laWQgew0KLS0tDQo+ICAgICAgIGVudW0gIm1wbHMtdHAtcHdlLWVpZCIgew0KMjI2LDIyN2Mx
OTENCjwNCjwgICAgICAgZW51bSBtdC12NCB7DQotLS0NCj4gICAgICAgZW51bSAibXQtdjQiIHsN
CjIzMiwyMzdjMTk2DQo8DQo8DQo8DQo8DQo8DQo8ICAgICAgIGVudW0gbXQtdjYgew0KLS0tDQo+
ICAgICAgIGVudW0gIm10LXY2IiB7DQoyNDIsMjQzYzIwMQ0KPA0KPCAgICAgICBlbnVtIGVpZ3Jw
LWNvbW1vbi1zZiB7DQotLS0NCj4gICAgICAgZW51bSAiZWlncnAtY29tbW9uLXNmIiB7DQoyNDks
MjUwYzIwNw0KPA0KPCAgICAgICBlbnVtIGVpZ3JwLXY0LXNmIHsNCi0tLQ0KPiAgICAgICBlbnVt
ICJlaWdycC12NC1zZiIgew0KMjU1LDI1NmMyMTINCjwNCjwgICAgICAgZW51bSBlaWdycC12Ni1z
ZiB7DQotLS0NCj4gICAgICAgZW51bSAiZWlncnAtdjYtc2YiIHsNCjI2MSwyNjJjMjE3DQo8DQo8
ICAgICAgIGVudW0gbGNhZiB7DQotLS0NCj4gICAgICAgZW51bSAibGNhZiIgew0KMjY4LDI2OWMy
MjMNCjwNCjwgICAgICAgZW51bSBiZ3AtbHMgew0KLS0tDQo+ICAgICAgIGVudW0gImJncC1scyIg
ew0KMjc1LDI3NmMyMjkNCjwNCjwgICAgICAgZW51bSBtYWMtNDggew0KLS0tDQo+ICAgICAgIGVu
dW0gIm1hYy00OCIgew0KMjgxLDI4NWMyMzQNCjwNCjwNCjwNCjwNCjwgICAgICAgZW51bSBtYWMt
NjQgew0KLS0tDQo+ICAgICAgIGVudW0gIm1hYy02NCIgew0KMjkwLDI5MWMyMzkNCjwNCjwgICAg
ICAgZW51bSB0cmlsbC1vdWkgew0KLS0tDQo+ICAgICAgIGVudW0gInRyaWxsLW91aSIgew0KMjk4
LDI5OWMyNDYNCjwNCjwgICAgICAgZW51bSB0cmlsbC1tYWMtMjQgew0KLS0tDQo+ICAgICAgIGVu
dW0gInRyaWxsLW1hYy0yNCIgew0KMzA0LDMwNWMyNTENCjwNCjwgICAgICAgZW51bSB0cmlsbC1t
YWMtNDAgew0KLS0tDQo+ICAgICAgIGVudW0gInRyaWxsLW1hYy00MCIgew0KMzEwLDMxMWMyNTYN
CjwNCjwgICAgICAgZW51bSBpcHY2LTY0IHsNCi0tLQ0KPiAgICAgICBlbnVtICJpcHY2LTY0IiB7
DQozMTcsMzE4YzI2Mg0KPA0KPCAgICAgICBlbnVtIHRyaWxsLXJicmlkZ2UtcG9ydC1pZCB7DQot
LS0NCj4gICAgICAgZW51bSAidHJpbGwtcmJyaWRnZS1wb3J0LWlkIiB7DQozMjMsMzI0YzI2Nw0K
PA0KPCAgICAgICBlbnVtIHRyaWxsLW5pY2tuYW1lIHsNCi0tLQ0KPiAgICAgICBlbnVtICJ0cmls
bC1uaWNrbmFtZSIgew0KMzMwLDMzMmQyNzINCjwNCjwNCjwNCjMzNmQyNzUNCjwNCjMzOSwzNDFk
Mjc3DQo8ICAgLyoqKiBTdWJzZXF1ZW50IEFkZHJlc3MgRmFtaWx5IElkZW50aWZpZXJzIChTQUZJ
cykgKioqLw0KPCAgIC8qKiogZm9yIG11bHRpcHJvdG9jb2wgQkdQIGVudW1lcmF0aW9uICoqKi8N
CjwNCjM0NGMyODANCjwgICAgICAgZW51bSB1bmljYXN0LXNhZmkgew0KLS0tDQo+ICAgICAgIGVu
dW0gInVuaWNhc3Qtc2FmaSIgew0KMzQ5LDM1MGMyODUNCjwNCjwgICAgICAgZW51bSBtdWx0aWNh
c3Qtc2FmaSB7DQotLS0NCj4gICAgICAgZW51bSAibXVsdGljYXN0LXNhZmkiIHsNCjM1NSwzNTZj
MjkwDQo8DQo8ICAgICAgIGVudW0gbGFiZWxlZC11bmljYXN0LXNhZmkgew0KLS0tDQo+ICAgICAg
IGVudW0gImxhYmVsZWQtdW5pY2FzdC1zYWZpIiB7DQozNjEsMzYyYzI5NQ0KPA0KPCAgICAgICBl
bnVtIG11bHRpY2FzdC12cG4tc2FmaSB7DQotLS0NCj4gICAgICAgZW51bSAibXVsdGljYXN0LXZw
bi1zYWZpIiB7DQozNjcsMzY4YzMwMA0KPA0KPCAgICAgICBlbnVtIHBzZXVkb3dpcmUtc2FmaSB7
DQotLS0NCj4gICAgICAgZW51bSAicHNldWRvd2lyZS1zYWZpIiB7DQozNzMsMzc0YzMwNQ0KPA0K
PCAgICAgICBlbnVtIHR1bm5lbC1lbmNhcC1zYWZpIHsNCi0tLQ0KPiAgICAgICBlbnVtICJ0dW5u
ZWwtZW5jYXAtc2FmaSIgew0KMzc5LDM4MWMzMTANCjwNCjwNCjwgICAgICAgZW51bSBtY2FzdC12
cGxzLXNhZmkgew0KLS0tDQo+ICAgICAgIGVudW0gIm1jYXN0LXZwbHMtc2FmaSIgew0KMzg2LDM4
N2MzMTUNCjwNCjwgICAgICAgZW51bSB0dW5uZWwtc2FmaSB7DQotLS0NCj4gICAgICAgZW51bSAi
dHVubmVsLXNhZmkiIHsNCjM5MiwzOTNjMzIwDQo8DQo8ICAgICAgIGVudW0gdnBscy1zYWZpIHsN
Ci0tLQ0KPiAgICAgICBlbnVtICJ2cGxzLXNhZmkiIHsNCjM5OCwzOTljMzI1DQo8DQo8ICAgICAg
IGVudW0gbWR0LXNhZmkgew0KLS0tDQo+ICAgICAgIGVudW0gIm1kdC1zYWZpIiB7DQo0MDQsNDA1
YzMzMA0KPA0KPCAgICAgICBlbnVtIHY0LW92ZXItdjYtc2FmaSB7DQotLS0NCj4gICAgICAgZW51
bSAidjQtb3Zlci12Ni1zYWZpIiB7DQo0MTAsNDExYzMzNQ0KPA0KPCAgICAgICBlbnVtIHY2LW92
ZXItdjQtc2FmaSB7DQotLS0NCj4gICAgICAgZW51bSAidjYtb3Zlci12NC1zYWZpIiB7DQo0MTYs
NDE3YzM0MA0KPA0KPCAgICAgICBlbnVtIGwxLXZwbi1hdXRvLWRpc2NvdmVyeS1zYWZpIHsNCi0t
LQ0KPiAgICAgICBlbnVtICJsMS12cG4tYXV0by1kaXNjb3Zlcnktc2FmaSIgew0KNDIyLDQyM2Mz
NDUNCjwNCjwgICAgICAgZW51bSBldnBuLXNhZmkgew0KLS0tDQo+ICAgICAgIGVudW0gImV2cG4t
c2FmaSIgew0KNDI4LDQyOWMzNTANCjwNCjwgICAgICAgZW51bSBiZ3AtbHMtc2FmaSB7DQotLS0N
Cj4gICAgICAgZW51bSAiYmdwLWxzLXNhZmkiIHsNCjQzNCw0MzVjMzU1DQo8DQo8ICAgICAgIGVu
dW0gYmdwLWxzLXZwbi1zYWZpIHsNCi0tLQ0KPiAgICAgICBlbnVtICJiZ3AtbHMtdnBuLXNhZmki
IHsNCjQ0MCw0NDFjMzYwDQo8DQo8ICAgICAgIGVudW0gc3ItdGUtc2FmaSB7DQotLS0NCj4gICAg
ICAgZW51bSAic3ItdGUtc2FmaSIgew0KNDQ2LDQ0N2MzNjUNCjwNCjwgICAgICAgZW51bSBsYWJl
bGVkLXZwbi1zYWZpIHsNCi0tLQ0KPiAgICAgICBlbnVtICJsYWJlbGVkLXZwbi1zYWZpIiB7DQo0
NTIsNDUzYzM3MA0KPA0KPCAgICAgICBlbnVtIG11bHRpY2FzdC1tcGxzLXZwbi1zYWZpIHsNCi0t
LQ0KPiAgICAgICBlbnVtICJtdWx0aWNhc3QtbXBscy12cG4tc2FmaSIgew0KNDU4LDQ1OWMzNzUN
CjwNCjwgICAgICAgZW51bSByb3V0ZS10YXJnZXQtc2FmaSB7DQotLS0NCj4gICAgICAgZW51bSAi
cm91dGUtdGFyZ2V0LXNhZmkiIHsNCjQ2NCw0NjVjMzgwDQo8DQo8ICAgICAgIGVudW0gaXB2NC1m
bG93LXNwZWMtc2FmaSB7DQotLS0NCj4gICAgICAgZW51bSAiaXB2NC1mbG93LXNwZWMtc2FmaSIg
ew0KNDcwLDQ3MWMzODUNCjwNCjwgICAgICAgZW51bSB2cG52NC1mbG93LXNwZWMtc2FmaSB7DQot
LS0NCj4gICAgICAgZW51bSAidnBudjQtZmxvdy1zcGVjLXNhZmkiIHsNCjQ3Niw0NzdjMzkwDQo8
DQo8ICAgICAgIGVudW0gdnBuLWF1dG8tZGlzY292ZXJ5LXNhZmkgew0KLS0tDQo+ICAgICAgIGVu
dW0gInZwbi1hdXRvLWRpc2NvdmVyeS1zYWZpIiB7DQo0ODUsNDg2YzM5OA0KPCAgICAgcmVmZXJl
bmNlDQo8ICAgICAgICJSRkMgNDc2MDogTXVsdGlwcm90b2NvbCBFeHRlbnNpb25zIGZvciBCR1At
NC4iOw0KLS0tDQo+ICAgICByZWZlcmVuY2UgIlJGQyA0NzYwOiBNdWx0aXByb3RvY29sIEV4dGVu
c2lvbnMgZm9yIEJHUC00LiI7DQpiY2xhaXNlQGJjbGFpc2UtVmlydHVhbEJveDovbWVkaWEvc2Zf
dWJ1bnR1LXNoYXJlL3RvYmVyZW1vdmVkJA0KDQpweWFuZyAtZiB5YW5nIGRvZXMgbW9yZSB0aGFu
IHRoZSBmb3JtYXR0aW5nLCBpdCBhZGRzIGRvdWJsZSBxdW90ZXMgdG8gZW51bSwgcmVtb3ZlIGNv
bW1lbnRzLCBhbmQgcG90ZW50aWFsbHkgZG9lcyBtb3JlIChJIGRvbid0IGtub3cgd2hhdCBJIGRv
bid0IGtub3cpLg0KDQpTbyBoZXJlIGlzIHRoZSBxdWVzdGlvbjogZG8gd2UgYWdyZWUgdGhhdCB0
aGUgSUFOQSwgYXMgc291cmNlIG9mIHRydXRoIGZvciBZQU5HIG1vZHVsZXMsIHNob3VsZCBhcHBs
eSBweWFuZyAtZiBmb3JtYXQgYmVmb3JlIHBvc3RpbmcgYSBZQU5HIG1vZHVsZT8NCg0KQm9udXMg
cXVlc3Rpb246IGlmIHRoZSBkb3VibGUgcXVvdGVzIGZvciBlbnVtIGlzIHRoZSBiZXN0IHNvbHV0
aW9uLCBzaG91bGQgaXQgYmUgYSB3YXJuaW5nIGluIHZhbGlkYXRvcnM/DQoNClJlZ2FyZHMsIEJl
bm9pdA0KDQoNCg0KDQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KeWFuZy1kb2N0b3JzIG1haWxpbmcgbGlzdA0KeWFuZy1kb2N0b3JzQGlldGYu
b3JnPG1haWx0bzp5YW5nLWRvY3RvcnNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3lhbmctZG9jdG9ycw0KDQpNYWhlc2ggSmV0aGFuYW5kYW5pDQptamV0
aGFuYW5kYW5pQGdtYWlsLmNvbTxtYWlsdG86bWpldGhhbmFuZGFuaUBnbWFpbC5jb20+DQoNCg==

--_000_D673C621E8591aceeciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <D2FA7597B2707D4A83126D1E61B598CD@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj5IaSBZQU5HIERv
Y3RvcnMsJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5QZXJzb25hbGx5LCBJ
IGRvbuKAmXQgbGlrZSB0aGUgZG91YmxlIHF1b3Rpbmcgb2YgZW51bXMuJm5ic3A7PC9kaXY+DQo8
ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5UaGFua3MsPC9kaXY+DQo8ZGl2PkFjZWU8L2Rpdj4NCjxk
aXY+PGJyPg0KPC9kaXY+DQo8c3BhbiBpZD0iT0xLX1NSQ19CT0RZX1NFQ1RJT04iPg0KPGRpdiBz
dHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTsgZm9udC1zaXplOjExcHQ7IHRleHQtYWxpZ246bGVm
dDsgY29sb3I6YmxhY2s7IEJPUkRFUi1CT1RUT006IG1lZGl1bSBub25lOyBCT1JERVItTEVGVDog
bWVkaXVtIG5vbmU7IFBBRERJTkctQk9UVE9NOiAwaW47IFBBRERJTkctTEVGVDogMGluOyBQQURE
SU5HLVJJR0hUOiAwaW47IEJPUkRFUi1UT1A6ICNiNWM0ZGYgMXB0IHNvbGlkOyBCT1JERVItUklH
SFQ6IG1lZGl1bSBub25lOyBQQURESU5HLVRPUDogM3B0Ij4NCjxzcGFuIHN0eWxlPSJmb250LXdl
aWdodDpib2xkIj5Gcm9tOiA8L3NwYW4+eWFuZy1kb2N0b3JzICZsdDs8YSBocmVmPSJtYWlsdG86
eWFuZy1kb2N0b3JzLWJvdW5jZXNAaWV0Zi5vcmciPnlhbmctZG9jdG9ycy1ib3VuY2VzQGlldGYu
b3JnPC9hPiZndDsgb24gYmVoYWxmIG9mIE1haGVzaCBKZXRoYW5hbmRhbmkgJmx0OzxhIGhyZWY9
Im1haWx0bzptamV0aGFuYW5kYW5pQGdtYWlsLmNvbSI+bWpldGhhbmFuZGFuaUBnbWFpbC5jb208
L2E+Jmd0Ozxicj4NCjxzcGFuIHN0eWxlPSJmb250LXdlaWdodDpib2xkIj5EYXRlOiA8L3NwYW4+
VGh1cnNkYXksIEphbnVhcnkgNCwgMjAxOCBhdCAxMDozNSBBTTxicj4NCjxzcGFuIHN0eWxlPSJm
b250LXdlaWdodDpib2xkIj5UbzogPC9zcGFuPiZxdW90O0Jlbm9pdCBDbGFpc2UgKGJjbGFpc2Up
JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86YmNsYWlzZUBjaXNjby5jb20iPmJjbGFpc2VAY2lz
Y28uY29tPC9hPiZndDs8YnI+DQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6Ym9sZCI+Q2M6IDwv
c3Bhbj4mcXVvdDtNaXJvc2xhdiBLb3ZhYyAtWCAobWlya292YWMgLSBQQU5USEVPTiBURUNITk9M
T0dJRVMgYXQgQ2lzY28pJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86bWlya292YWNAY2lzY28u
Y29tIj5taXJrb3ZhY0BjaXNjby5jb208L2E+Jmd0OywgJnF1b3Q7Sm9lIENsYXJrZSAoamNsYXJr
ZSkmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpqY2xhcmtlQGNpc2NvLmNvbSI+amNsYXJrZUBj
aXNjby5jb208L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOnNhYnJpbmEudGFuYW1hbEBp
YW5hLm9yZyI+c2FicmluYS50YW5hbWFsQGlhbmEub3JnPC9hPiZxdW90Ow0KICZsdDs8YSBocmVm
PSJtYWlsdG86c2FicmluYS50YW5hbWFsQGlhbmEub3JnIj5zYWJyaW5hLnRhbmFtYWxAaWFuYS5v
cmc8L2E+Jmd0OywgJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOmFtYW5kYS5iYWJlckBpYW5hLm9yZyI+
YW1hbmRhLmJhYmVyQGlhbmEub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFtYW5k
YS5iYWJlckBpYW5hLm9yZyI+YW1hbmRhLmJhYmVyQGlhbmEub3JnPC9hPiZndDssIFlBTkcgRG9j
dG9ycyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnlhbmctZG9jdG9yc0BpZXRmLm9yZyI+eWFuZy1kb2N0
b3JzQGlldGYub3JnPC9hPiZndDssDQogTWljaGVsbGUgQ290dG9uICZsdDs8YSBocmVmPSJtYWls
dG86bWljaGVsbGUuY290dG9uQGljYW5uLm9yZyI+bWljaGVsbGUuY290dG9uQGljYW5uLm9yZzwv
YT4mZ3Q7PGJyPg0KPHNwYW4gc3R5bGU9ImZvbnQtd2VpZ2h0OmJvbGQiPlN1YmplY3Q6IDwvc3Bh
bj5SZTogW3lhbmctZG9jdG9yc10gWUFORyBtb2R1bGUgJmFtcDsgcHlhbmcgLWYgeWFuZyAmYW1w
OyBzb3VyY2Ugb2YgdHJ1dGggcmVwb3NpdG9yeTxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIGlkPSJNQUNfT1VUTE9PS19BVFRSSUJVVElPTl9CTE9DS1FVT1RFIiBz
dHlsZT0iQk9SREVSLUxFRlQ6ICNiNWM0ZGYgNSBzb2xpZDsgUEFERElORzowIDAgMCA1OyBNQVJH
SU46MCAwIDAgNTsiPg0KPGRpdj4NCjxkaXYgc3R5bGU9IndvcmQtd3JhcDogYnJlYWstd29yZDsg
LXdlYmtpdC1uYnNwLW1vZGU6IHNwYWNlOyAtd2Via2l0LWxpbmUtYnJlYWs6IGFmdGVyLXdoaXRl
LXNwYWNlOyIgY2xhc3M9IiI+DQpCZW5vaXQsDQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4N
CjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5BZ3JlZSB0aGF0IHB5YW5nIC1mIHNob3VsZCBzdHJpcCB0
aGUgd2hpdGVzcGFjZSBhbmQgZG8gcHJldHR5IGZvcm1hdHRpbmcuIEJ1dCBub25lIG9mIHRoZSBl
eGFtcGxlcyBpbiBSRkMgNzk1MCBzaG93IGVudW0gd2l0aCBkb3VibGUtcXVvdGVzLg0KPGRpdiBj
bGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xh
c3M9IiI+DQo8ZGl2IGNsYXNzPSIiPk9uIEphbiA0LCAyMDE4LCBhdCAzOjEyIEFNLCBCZW5vaXQg
Q2xhaXNlICZsdDs8YSBocmVmPSJtYWlsdG86YmNsYWlzZUBjaXNjby5jb20iIGNsYXNzPSIiPmJj
bGFpc2VAY2lzY28uY29tPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWlu
dGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgdGV4dD0iIzAwMDAwMCIg
Ymdjb2xvcj0iI0ZGRkZGRiIgY2xhc3M9IiI+RGVhciBhbGwsPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KV2UgY2FuIHNheSB0aGF0IHRoZSBSRkMgaXMgdGhlIHNvdXJjZSBvZiB0cnV0aCBi
dXQgZGV2b3BzIHBlb3BsZSAmcXVvdDtwbGF5JnF1b3Q7IGFib3V0IFlBTkcgbW9kdWxlcy48YnIg
Y2xhc3M9IiI+DQpJJ20gdHJ5aW5nIHRvIGhhdmUgYSBzaW5nbGUgc291cmNlIG9mIHRydXRoIGZv
ciB0aGUgcmVwb3NpdG9yeSBvZiBSRkMtcHJvZHVjZWQgWUFORyBtb2R1bGVzLCB3aGlsZSB3ZSBo
YXZlIG11bHRpcGxlIG9uZXMgbm93LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCklNTywg
aXQgc2hvdWxkIGJlIElBTkEuJm5ic3A7IFdlJ3ZlIGRpc2N1c3NpbmcgdGhpcyBvcHRpb24gd2l0
aCBSRkMgZWRpdG9yIGFuZCBJQU5BOiA8YSBjbGFzcz0ibW96LXR4dC1saW5rLWZyZWV0ZXh0IiBo
cmVmPSJodHRwczovL3d3dy5pYW5hLm9yZy9hc3NpZ25tZW50cy95YW5nLXBhcmFtZXRlcnMveWFu
Zy1wYXJhbWV0ZXJzLnhodG1sIj4NCmh0dHBzOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3lh
bmctcGFyYW1ldGVycy95YW5nLXBhcmFtZXRlcnMueGh0bWw8L2E+IGlzIGJlaW5nIHRyYW5zZm9y
bWVkIGluIHRoYXQgZGlyZWN0aW9uLjxiciBjbGFzcz0iIj4NClRoZSBlbmQgZ29hbCBpcyB0aGF0
IGVuZCB1c2Vycywgd2FudGVkIHRvIGJlIHVwLXRvLWRhdGUgd2l0aCB0aGUgbGF0ZXN0IFJGQy1w
cm9kdWNlZCBZQU5HIG1vZHVsZXMsIHdvdWxkIHBlcmZvcm0gYSBjcm9uIGpvYiBzdWNoIGFzOjxi
ciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyByc3luYyAtYXZ6IC0tZGVsZXRlIDxhIGhy
ZWY9Imh0dHA6Ly9yc3luYy5pZXRmLm9yZyIgY2xhc3M9IiI+cnN5bmMuaWV0Zi5vcmc8L2E+Ojpp
YW5hL3lhbmctcGFyYW1ldGVycyAuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KTm90ZTog
ZXNwZWNpYWxseSBpbnRlcmVzdGVkIGZvciBJQU5BLW1haW50YWluZWQgWUFORyBtb2R1bGVzIHN1
Y2ggYXMgaWFuYS1pZi10eXBlPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KTm93IHRoZSBm
b2xsb3ctdXAgcXVlc3Rpb24gZnJvbSBJQU5BOjxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIGNs
YXNzPSIiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQiIGNsYXNzPSIiPldlIHdlcmUgd29ya2luZyBvbiB0aGUgcG9zdGluZyBvZiB0aGUgeWFuZyBt
b2R1bGVzIGZvcg0KPHUgY2xhc3M9IiI+PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRm
Lm9yZy9pZHRyYWNrZXIvZHJhZnQtaWV0Zi1ydGd3Zy1yb3V0aW5nLXR5cGVzLyIgY2xhc3M9IiI+
ZHJhZnQtaWV0Zi1ydGd3Zy1yb3V0aW5nLXR5cGVzPC9hPjwvdT4gcGVyIG91ciBuZXcgcHJvY2Vz
cy4mbmJzcDsgV2hlbiByZXF1ZXN0aW5nIHRoZSBmaW5hbCBmaWxlcyBmcm9tIHRoZSBSRkMtRWRp
dG9yLCB0aGUgZmlsZSB0aGV5IGV4dHJhY3RlZCB1c2luZyB0aGVpciB0b29sDQogYW5kIHRoZSB5
YW5nIG1vZHVsZXMgYXBwZWFyIHRvIGhhdmUgYSBsb3Qgb2YgYmxhbmsgc3BhY2UgaW4gdGhlbS4m
bmJzcDsgU2VlIGF0dGFjaGVkPC9zcGFuPjwvcD4NCjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0IiBjbGFzcz0iIj5JcyB0aGlzIE9LPyZuYnNwOyBEbyB3ZSBwb3N0IGl0IGFzIGl0IGlzIGlu
IHRoZSBwcm92aWRlZCBmaWxlIGZyb20gdGhlIFJGQy1FZGl0b3I/Jm5ic3A7IFdlIGtub3cgdGhh
dCB0aGVyZSBpcyBzb21lIHNlbnNpdGl2aXR5IHRvIHNwYWNpbmcgaW4gdGhlc2UgZmlsZXMgc28g
d2Ugd2FudCB0byBtYWtlIHN1cmUgdGhlIGNvcnJlY3QgdGhpbmcgaXMgYmVpbmcgcG9zdGVkLjwv
c3Bhbj48L2Jsb2NrcXVvdGU+DQpUaGUgc29sdXRpb24gc2hvdWxkIGJlOiBweWFuZyAtZiB5YW5n
IC4uLiA8YnIgY2xhc3M9IiI+DQpIb3dldmVyLCBhZnRlciBzb21lIHRlc3Rpbmc6PGJyIGNsYXNz
PSIiPg0KPGJyIGNsYXNzPSIiPg0KYmNsYWlzZUBiY2xhaXNlLVZpcnR1YWxCb3g6L21lZGlhL3Nm
X3VidW50dS1zaGFyZS90b2JlcmVtb3ZlZCQgcHlhbmcgLWYgeWFuZyA8YSBjbGFzcz0ibW96LXR4
dC1saW5rLWFiYnJldmlhdGVkIiBocmVmPSJtYWlsdG86aWFuYS1yb3V0aW5nLXR5cGVzQDIwMTct
MTItMDQueWFuZyI+DQppYW5hLXJvdXRpbmctdHlwZXNAMjAxNy0xMi0wNC55YW5nPC9hPiAmZ3Q7
IG5ld2ZpbGUueWFuZzxiciBjbGFzcz0iIj4NCmJjbGFpc2VAYmNsYWlzZS1WaXJ0dWFsQm94Oi9t
ZWRpYS9zZl91YnVudHUtc2hhcmUvdG9iZXJlbW92ZWQkIGRpZmYgPGEgY2xhc3M9Im1vei10eHQt
bGluay1hYmJyZXZpYXRlZCIgaHJlZj0ibWFpbHRvOmlhbmEtcm91dGluZy10eXBlc0AyMDE3LTEy
LTA0LnlhbmciPg0KaWFuYS1yb3V0aW5nLXR5cGVzQDIwMTctMTItMDQueWFuZzwvYT4gbmV3Zmls
ZS55YW5nPGJyIGNsYXNzPSIiPg0KMTZkMTU8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0i
Ij4NCjM1LDM5YzM0LDM5PGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyByZXZp
c2lvbiAyMDE3LTEyLTA0IHs8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7IGRlc2NyaXB0aW9uICZxdW90O0luaXRpYWwgcmV2aXNpb24uJnF1b3Q7OzxiciBj
bGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgcmVmZXJlbmNlPGJy
IGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyAmcXVvdDtSRkMgODI5NDogQ29tbW9uIFlBTkcgRGF0YSBUeXBlcyBmb3IgdGhlIFJvdXRpbmcg
QXJlYS48YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IFNlY3Rpb24gNC4mcXVvdDs7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNs
YXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyByZXZpc2lvbiAyMDE3LTEyLTA0IHs8YnIgY2xhc3M9
IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRlc2NyaXB0aW9uPGJyIGNsYXNzPSIi
Pg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmcXVvdDtJbml0aWFs
IHJldmlzaW9uLiZxdW90Ozs8YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IHJlZmVyZW5jZTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgJnF1b3Q7UkZDIDgyOTQ6IENvbW1vbiBZQU5HIERhdGEgVHlwZXMgZm9yIHRo
ZSBSb3V0aW5nIEFyZWEuPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyBTZWN0aW9uIDQuJnF1b3Q7OzxiciBjbGFzcz0iIj4NCjQyLDQ3
ZDQxPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4N
CiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyAvKioqIENvbGxlY3Rpb24gb2Yg
SUFOQSB0eXBlcyByZWxhdGVkIHRvIHJvdXRpbmcgKioqLzxiciBjbGFzcz0iIj4NCiZsdDsmbmJz
cDsmbmJzcDsgLyoqKiBJQU5BIEFkZHJlc3MgRmFtaWx5IGVudW1lcmF0aW9uICoqKi88YnIgY2xh
c3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4NCjUwYzQ0PGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIGlwdjQgezxiciBjbGFzcz0iIj4N
Ci0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgZW51bSAmcXVvdDtpcHY0JnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo1NSw1NmM0OTxiciBjbGFz
cz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBlbnVtIGlwdjYgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZn
dDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtpcHY2JnF1
b3Q7IHs8YnIgY2xhc3M9IiI+DQo2MSw2MmM1NDxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNz
PSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIG5zYXAg
ezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtuc2FwJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo2
Nyw2OGM1OTxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIGhkbGMgezxiciBjbGFzcz0iIj4NCi0tLTxi
ciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51
bSAmcXVvdDtoZGxjJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo3Myw3NGM2NDxiciBjbGFzcz0iIj4N
CiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBlbnVtIGJibjE4MjIgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtiYm4xODIyJnF1
b3Q7IHs8YnIgY2xhc3M9IiI+DQo4MCw4MWM3MDxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNz
PSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIGllZWU4
MDIgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtpZWVlODAyJnF1b3Q7IHs8YnIgY2xhc3M9
IiI+DQo4Nyw4OGM3NjxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIGUxNjMgezxiciBjbGFzcz0iIj4N
Ci0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgZW51bSAmcXVvdDtlMTYzJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo5M2M4MTxiciBjbGFzcz0i
Ij4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBlMTY0IHs8
YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7ZTE2NCZxdW90OyB7PGJyIGNsYXNzPSIiPg0KOTks
MTAwYzg3PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gZjY5IHs8YnIgY2xhc3M9IiI+DQotLS08YnIg
Y2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0g
JnF1b3Q7ZjY5JnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQoxMDUsMTA2YzkyPGJyIGNsYXNzPSIiPg0K
Jmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IGVudW0geDEyMSB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O3gxMjEmcXVvdDsgezxi
ciBjbGFzcz0iIj4NCjExMSwxMTJjOTc8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4N
CiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBpcHggezxiciBj
bGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgZW51bSAmcXVvdDtpcHgmcXVvdDsgezxiciBjbGFzcz0iIj4NCjExOCwxMTlj
MTAzPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gYXBwbGV0YWxrIHs8YnIgY2xhc3M9IiI+DQotLS08
YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVu
dW0gJnF1b3Q7YXBwbGV0YWxrJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQoxMjQsMTI1YzEwODxiciBj
bGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbnVtIGRlY25ldC1pdiB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNz
PSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90
O2RlY25ldC1pdiZxdW90OyB7PGJyIGNsYXNzPSIiPg0KMTMwLDEzMWMxMTM8YnIgY2xhc3M9IiI+
DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgZW51bSB2aW5lcyB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O3ZpbmVzJnF1b3Q7
IHs8YnIgY2xhc3M9IiI+DQoxMzYsMTQxYzExODxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNz
PSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNs
YXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGVudW0gZTE2NC1uc2FwIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9
IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7
ZTE2NC1uc2FwJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQoxNDYsMTQ3YzEyMzxiciBjbGFzcz0iIj4N
CiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBlbnVtIGRucyB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O2RucyZxdW90OyB7PGJy
IGNsYXNzPSIiPg0KMTUyLDE1M2MxMjg8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4N
CiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBkaXN0aW5ndWlz
aGVkLW5hbWUgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtkaXN0aW5ndWlzaGVkLW5hbWUm
cXVvdDsgezxiciBjbGFzcz0iIj4NCjE1OCwxNTljMTMzPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIg
Y2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0g
YXMtbnVtIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7YXMtbnVtJnF1b3Q7IHs8YnIgY2xh
c3M9IiI+DQoxNjQsMTY1YzEzODxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIHh0cC12NCB7PGJyIGNs
YXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBlbnVtICZxdW90O3h0cC12NCZxdW90OyB7PGJyIGNsYXNzPSIiPg0KMTcxLDE3
MmMxNDQ8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSB4dHAtdjYgezxiciBjbGFzcz0iIj4NCi0tLTxi
ciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51
bSAmcXVvdDt4dHAtdjYmcXVvdDsgezxiciBjbGFzcz0iIj4NCjE3NywxNzhjMTQ5PGJyIGNsYXNz
PSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7IGVudW0geHRwLW5hdGl2ZSB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIi
Pg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O3h0
cC1uYXRpdmUmcXVvdDsgezxiciBjbGFzcz0iIj4NCjE4MywxODRjMTU0PGJyIGNsYXNzPSIiPg0K
Jmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IGVudW0gZmMtcG9ydCB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O2ZjLXBvcnQmcXVv
dDsgezxiciBjbGFzcz0iIj4NCjE4OWMxNTk8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gZmMtbm9kZSB7PGJyIGNsYXNzPSIiPg0KLS0t
PGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBl
bnVtICZxdW90O2ZjLW5vZGUmcXVvdDsgezxiciBjbGFzcz0iIj4NCjE5NCwxOTVjMTY0PGJyIGNs
YXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGVudW0gZ3dpZCB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0K
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O2d3aWQm
cXVvdDsgezxiciBjbGFzcz0iIj4NCjIwMCwyMDFjMTY5PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIg
Y2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0g
bDJ2cG4gezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtsMnZwbiZxdW90OyB7PGJyIGNsYXNz
PSIiPg0KMjA2LDIwN2MxNzQ8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBtcGxzLXRwLXNlY3Rpb24t
ZWlkIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7bXBscy10cC1zZWN0aW9uLWVpZCZxdW90
OyB7PGJyIGNsYXNzPSIiPg0KMjEzLDIxNGMxODA8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFz
cz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBtcGxz
LXRwLWxzcC1laWQgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDttcGxzLXRwLWxzcC1laWQm
cXVvdDsgezxiciBjbGFzcz0iIj4NCjIyMCwyMjFjMTg2PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIg
Y2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0g
bXBscy10cC1wd2UtZWlkIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7bXBscy10cC1wd2Ut
ZWlkJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQoyMjYsMjI3YzE5MTxiciBjbGFzcz0iIj4NCiZsdDsg
PGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBl
bnVtIG10LXY0IHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7bXQtdjQmcXVvdDsgezxiciBj
bGFzcz0iIj4NCjIzMiwyMzdjMTk2PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQom
bHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+
DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgZW51bSBtdC12NiB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O210LXY2JnF1b3Q7
IHs8YnIgY2xhc3M9IiI+DQoyNDIsMjQzYzIwMTxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNz
PSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIGVpZ3Jw
LWNvbW1vbi1zZiB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O2VpZ3JwLWNvbW1vbi1zZiZx
dW90OyB7PGJyIGNsYXNzPSIiPg0KMjQ5LDI1MGMyMDc8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBj
bGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBl
aWdycC12NC1zZiB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O2VpZ3JwLXY0LXNmJnF1b3Q7
IHs8YnIgY2xhc3M9IiI+DQoyNTUsMjU2YzIxMjxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNz
PSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIGVpZ3Jw
LXY2LXNmIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7ZWlncnAtdjYtc2YmcXVvdDsgezxi
ciBjbGFzcz0iIj4NCjI2MSwyNjJjMjE3PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+
DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gbGNhZiB7PGJy
IGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O2xjYWYmcXVvdDsgezxiciBjbGFzcz0iIj4NCjI2OCwy
NjljMjIzPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gYmdwLWxzIHs8YnIgY2xhc3M9IiI+DQotLS08
YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVu
dW0gJnF1b3Q7YmdwLWxzJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQoyNzUsMjc2YzIyOTxiciBjbGFz
cz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBlbnVtIG1hYy00OCB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0K
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O21hYy00
OCZxdW90OyB7PGJyIGNsYXNzPSIiPg0KMjgxLDI4NWMyMzQ8YnIgY2xhc3M9IiI+DQombHQ7IDxi
ciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7
IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg
ZW51bSBtYWMtNjQgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDttYWMtNjQmcXVvdDsgezxi
ciBjbGFzcz0iIj4NCjI5MCwyOTFjMjM5PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+
DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gdHJpbGwtb3Vp
IHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7dHJpbGwtb3VpJnF1b3Q7IHs8YnIgY2xhc3M9
IiI+DQoyOTgsMjk5YzI0NjxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIHRyaWxsLW1hYy0yNCB7PGJy
IGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O3RyaWxsLW1hYy0yNCZxdW90OyB7PGJyIGNsYXNzPSIi
Pg0KMzA0LDMwNWMyNTE8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSB0cmlsbC1tYWMtNDAgezxiciBj
bGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgZW51bSAmcXVvdDt0cmlsbC1tYWMtNDAmcXVvdDsgezxiciBjbGFzcz0iIj4N
CjMxMCwzMTFjMjU2PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gaXB2Ni02NCB7PGJyIGNsYXNzPSIi
Pg0KLS0tPGJyIGNsYXNzPSIiPg0KJmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBlbnVtICZxdW90O2lwdjYtNjQmcXVvdDsgezxiciBjbGFzcz0iIj4NCjMxNywzMThjMjYy
PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gdHJpbGwtcmJyaWRnZS1wb3J0LWlkIHs8YnIgY2xhc3M9
IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IGVudW0gJnF1b3Q7dHJpbGwtcmJyaWRnZS1wb3J0LWlkJnF1b3Q7IHs8YnIgY2xhc3M9
IiI+DQozMjMsMzI0YzI2NzxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIHRyaWxsLW5pY2tuYW1lIHs8
YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7dHJpbGwtbmlja25hbWUmcXVvdDsgezxiciBjbGFz
cz0iIj4NCjMzMCwzMzJkMjcyPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7
IDxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KMzM2ZDI3NTxiciBjbGFzcz0iIj4N
CiZsdDsgPGJyIGNsYXNzPSIiPg0KMzM5LDM0MWQyNzc8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7
Jm5ic3A7IC8qKiogU3Vic2VxdWVudCBBZGRyZXNzIEZhbWlseSBJZGVudGlmaWVycyAoU0FGSXMp
ICoqKi88YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7IC8qKiogZm9yIG11bHRpcHJvdG9j
b2wgQkdQIGVudW1lcmF0aW9uICoqKi88YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4N
CjM0NGMyODA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IGVudW0gdW5pY2FzdC1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+
DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7dW5p
Y2FzdC1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQozNDksMzUwYzI4NTxiciBjbGFzcz0iIj4N
CiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBlbnVtIG11bHRpY2FzdC1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+
DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7bXVs
dGljYXN0LXNhZmkmcXVvdDsgezxiciBjbGFzcz0iIj4NCjM1NSwzNTZjMjkwPGJyIGNsYXNzPSIi
Pg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IGVudW0gbGFiZWxlZC11bmljYXN0LXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBj
bGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAm
cXVvdDtsYWJlbGVkLXVuaWNhc3Qtc2FmaSZxdW90OyB7PGJyIGNsYXNzPSIiPg0KMzYxLDM2MmMy
OTU8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBtdWx0aWNhc3QtdnBuLXNhZmkgezxiciBjbGFzcz0i
Ij4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgZW51bSAmcXVvdDttdWx0aWNhc3QtdnBuLXNhZmkmcXVvdDsgezxiciBjbGFzcz0iIj4N
CjM2NywzNjhjMzAwPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gcHNldWRvd2lyZS1zYWZpIHs8YnIg
Y2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7cHNldWRvd2lyZS1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9
IiI+DQozNzMsMzc0YzMwNTxiciBjbGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtIHR1bm5lbC1lbmNhcC1zYWZp
IHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7dHVubmVsLWVuY2FwLXNhZmkmcXVvdDsgezxi
ciBjbGFzcz0iIj4NCjM3OSwzODFjMzEwPGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+
DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgZW51bSBtY2FzdC12cGxzLXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0i
Ij4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtt
Y2FzdC12cGxzLXNhZmkmcXVvdDsgezxiciBjbGFzcz0iIj4NCjM4NiwzODdjMzE1PGJyIGNsYXNz
PSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7IGVudW0gdHVubmVsLXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0i
Ij4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDt0
dW5uZWwtc2FmaSZxdW90OyB7PGJyIGNsYXNzPSIiPg0KMzkyLDM5M2MzMjA8YnIgY2xhc3M9IiI+
DQombHQ7IDxiciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgZW51bSB2cGxzLXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZn
dDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDt2cGxzLXNh
ZmkmcXVvdDsgezxiciBjbGFzcz0iIj4NCjM5OCwzOTljMzI1PGJyIGNsYXNzPSIiPg0KJmx0OyA8
YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVu
dW0gbWR0LXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDttZHQtc2FmaSZxdW90OyB7
PGJyIGNsYXNzPSIiPg0KNDA0LDQwNWMzMzA8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0i
Ij4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSB2NC1vdmVy
LXY2LXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDt2NC1vdmVyLXY2LXNhZmkmcXVv
dDsgezxiciBjbGFzcz0iIj4NCjQxMCw0MTFjMzM1PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xh
c3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gdjYt
b3Zlci12NC1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7djYtb3Zlci12NC1zYWZp
JnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo0MTYsNDE3YzM0MDxiciBjbGFzcz0iIj4NCiZsdDsgPGJy
IGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVt
IGwxLXZwbi1hdXRvLWRpc2NvdmVyeS1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9
IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7
bDEtdnBuLWF1dG8tZGlzY292ZXJ5LXNhZmkmcXVvdDsgezxiciBjbGFzcz0iIj4NCjQyMiw0MjNj
MzQ1PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gZXZwbi1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08
YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVu
dW0gJnF1b3Q7ZXZwbi1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo0MjgsNDI5YzM1MDxiciBj
bGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbnVtIGJncC1scy1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xh
c3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1
b3Q7YmdwLWxzLXNhZmkmcXVvdDsgezxiciBjbGFzcz0iIj4NCjQzNCw0MzVjMzU1PGJyIGNsYXNz
PSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7IGVudW0gYmdwLWxzLXZwbi1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xh
c3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1
b3Q7YmdwLWxzLXZwbi1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo0NDAsNDQxYzM2MDxiciBj
bGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbnVtIHNyLXRlLXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFz
cz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVv
dDtzci10ZS1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo0NDYsNDQ3YzM2NTxiciBjbGFzcz0i
Ij4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyBlbnVtIGxhYmVsZWQtdnBuLXNhZmkgezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFz
cz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVv
dDtsYWJlbGVkLXZwbi1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo0NTIsNDUzYzM3MDxiciBj
bGFzcz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBlbnVtIG11bHRpY2FzdC1tcGxzLXZwbi1zYWZpIHs8YnIgY2xhc3M9IiI+
DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IGVudW0gJnF1b3Q7bXVsdGljYXN0LW1wbHMtdnBuLXNhZmkmcXVvdDsgezxiciBjbGFzcz0i
Ij4NCjQ1OCw0NTljMzc1PGJyIGNsYXNzPSIiPg0KJmx0OyA8YnIgY2xhc3M9IiI+DQombHQ7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gcm91dGUtdGFyZ2V0LXNhZmkg
ezxiciBjbGFzcz0iIj4NCi0tLTxiciBjbGFzcz0iIj4NCiZndDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsgZW51bSAmcXVvdDtyb3V0ZS10YXJnZXQtc2FmaSZxdW90OyB7PGJy
IGNsYXNzPSIiPg0KNDY0LDQ2NWMzODA8YnIgY2xhc3M9IiI+DQombHQ7IDxiciBjbGFzcz0iIj4N
CiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51bSBpcHY0LWZsb3ct
c3BlYy1zYWZpIHs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGVudW0gJnF1b3Q7aXB2NC1mbG93LXNwZWMtc2Fm
aSZxdW90OyB7PGJyIGNsYXNzPSIiPg0KNDcwLDQ3MWMzODU8YnIgY2xhc3M9IiI+DQombHQ7IDxi
ciBjbGFzcz0iIj4NCiZsdDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZW51
bSB2cG52NC1mbG93LXNwZWMtc2FmaSB7PGJyIGNsYXNzPSIiPg0KLS0tPGJyIGNsYXNzPSIiPg0K
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBlbnVtICZxdW90O3ZwbnY0
LWZsb3ctc3BlYy1zYWZpJnF1b3Q7IHs8YnIgY2xhc3M9IiI+DQo0NzYsNDc3YzM5MDxiciBjbGFz
cz0iIj4NCiZsdDsgPGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyBlbnVtIHZwbi1hdXRvLWRpc2NvdmVyeS1zYWZpIHs8YnIgY2xhc3M9IiI+DQot
LS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IGVudW0gJnF1b3Q7dnBuLWF1dG8tZGlzY292ZXJ5LXNhZmkmcXVvdDsgezxiciBjbGFzcz0iIj4N
CjQ4NSw0ODZjMzk4PGJyIGNsYXNzPSIiPg0KJmx0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBy
ZWZlcmVuY2U8YnIgY2xhc3M9IiI+DQombHQ7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7ICZxdW90O1JGQyA0NzYwOiBNdWx0aXByb3RvY29sIEV4dGVuc2lvbnMgZm9yIEJHUC00
LiZxdW90Ozs8YnIgY2xhc3M9IiI+DQotLS08YnIgY2xhc3M9IiI+DQomZ3Q7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IHJlZmVyZW5jZSAmcXVvdDtSRkMgNDc2MDogTXVsdGlwcm90b2NvbCBFeHRl
bnNpb25zIGZvciBCR1AtNC4mcXVvdDs7PGJyIGNsYXNzPSIiPg0KYmNsYWlzZUBiY2xhaXNlLVZp
cnR1YWxCb3g6L21lZGlhL3NmX3VidW50dS1zaGFyZS90b2JlcmVtb3ZlZCQgPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0KcHlhbmcgLWYgeWFuZyBkb2VzIG1vcmUgdGhhbiB0aGUgZm9ybWF0
dGluZywgaXQgYWRkcyBkb3VibGUgcXVvdGVzIHRvIGVudW0sIHJlbW92ZSBjb21tZW50cywgYW5k
IHBvdGVudGlhbGx5IGRvZXMgbW9yZSAoSSBkb24ndCBrbm93IHdoYXQgSSBkb24ndCBrbm93KS48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpTbyBoZXJlIGlzIHRoZSBxdWVzdGlvbjogZG8g
d2UgYWdyZWUgdGhhdCB0aGUgSUFOQSwgYXMgc291cmNlIG9mIHRydXRoIGZvciBZQU5HIG1vZHVs
ZXMsIHNob3VsZCBhcHBseSBweWFuZyAtZiBmb3JtYXQgYmVmb3JlIHBvc3RpbmcgYSBZQU5HIG1v
ZHVsZT88YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpCb251cyBxdWVzdGlvbjogaWYgdGhl
IGRvdWJsZSBxdW90ZXMgZm9yIGVudW0gaXMgdGhlIGJlc3Qgc29sdXRpb24sIHNob3VsZCBpdCBi
ZSBhIHdhcm5pbmcgaW4gdmFsaWRhdG9ycz88YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpS
ZWdhcmRzLCBCZW5vaXQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsgPGJyIGNsYXNz
PSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+DQpfX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxiciBjbGFzcz0iIj4NCnlhbmct
ZG9jdG9ycyBtYWlsaW5nIGxpc3Q8YnIgY2xhc3M9IiI+DQo8YSBocmVmPSJtYWlsdG86eWFuZy1k
b2N0b3JzQGlldGYub3JnIiBjbGFzcz0iIj55YW5nLWRvY3RvcnNAaWV0Zi5vcmc8L2E+PGJyIGNs
YXNzPSIiPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby95
YW5nLWRvY3RvcnMiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8veWFuZy1k
b2N0b3JzPC9hPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
YnIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5NYWhlc2ggSmV0aGFu
YW5kYW5pPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxhIGhyZWY9Im1haWx0bzptamV0aGFuYW5kYW5p
QGdtYWlsLmNvbSIgY2xhc3M9IiI+bWpldGhhbmFuZGFuaUBnbWFpbC5jb208L2E+PC9kaXY+DQo8
L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
bG9ja3F1b3RlPg0KPC9zcGFuPg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_D673C621E8591aceeciscocom_--


From nobody Fri Jan  5 00:59:37 2018
Return-Path: <rkrejci@cesnet.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3B9127136 for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 00:59:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level: 
X-Spam-Status: No, score=-4.309 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_MED=-2.3, T_RP_MATCHES_RCVD=-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=cesnet.cz
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 bc5OC2wUjUNe for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 00:59:33 -0800 (PST)
Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) (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 86C3D1242F5 for <yang-doctors@ietf.org>; Fri,  5 Jan 2018 00:59:32 -0800 (PST)
Received: from pckrejci.nat9.vcit.vutbr.net (unknown [IPv6:2001:67c:1220:80c:d0:552c:73a5:18da]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by office2.cesnet.cz (Postfix) with ESMTPSA id 5060940004E; Fri,  5 Jan 2018 09:59:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=office2; t=1515142768; bh=e0cLe1FYPOZd5xfqq0f2aymf19pbmGJnL02s6r1kRU8=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=m9M67I9LIuOvWg/xmSqTsyVluU9B+GdVg8xVT8CPwc5siy81/PFjCJCmlXKAJToFx r7d3jsrdLwoo7hYVJR4xi113Fr/GQT2JKodWBVNl1pxxMzixmnDpCAFIzBAvDBrrnR r+S5tWNxOgFRBWKVxEKjoYp4RFgo9J8uTf6pBqoA=
To: "Acee Lindem (acee)" <acee@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
Cc: "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, "sabrina.tanamal@iana.org" <sabrina.tanamal@iana.org>, "amanda.baber@iana.org" <amanda.baber@iana.org>, YANG Doctors <yang-doctors@ietf.org>, Michelle Cotton <michelle.cotton@icann.org>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <0766646B-7D4C-4BA9-B4B0-CCB553D954CA@gmail.com> <D673C621.E8591%acee@cisco.com>
From: =?UTF-8?B?UmFkZWsgS3JlasSNw60=?= <rkrejci@cesnet.cz>
Message-ID: <ca8dd36b-9d29-a468-b2dd-a7e7af51c288@cesnet.cz>
Date: Fri, 5 Jan 2018 09:59:26 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <D673C621.E8591%acee@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/ctj3U6eeeT7JHLBXUNzhExRQdgc>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 08:59:36 -0000

Hi,
not sure if it is the case of pyang, but with my experience with libyang,=
 it is not a problem to print enums without quotes, but it is a problem t=
o preserve what was in input file. enum can be written with or without qu=
otes and in some cases some quotes are necessary. Therefore, at least lib=
yang/yanglint, chooses consistency and always print double quotes around =
enums. And it is not only the case of enums, even one-word description is=
 always quoted. On the other hand, I don't think that the author should b=
e warned when there are no quotes. When the rules for the string content =
are not violated, the specs allows e.g. foo, "foo" and 'foo'.

Regards,
Radek


Dne 4.1.2018 v 17:54 Acee Lindem (acee) napsal(a):
> Hi YANG Doctors,=C2=A0
>
> Personally, I don=E2=80=99t like the double quoting of enums.=C2=A0
>
> Thanks,
> Acee
>
> From: yang-doctors <yang-doctors-bounces@ietf.org <mailto:yang-doctors-=
bounces@ietf.org>> on behalf of Mahesh Jethanandani <mjethanandani@gmail.=
com <mailto:mjethanandani@gmail.com>>
> Date: Thursday, January 4, 2018 at 10:35 AM
> To: "Benoit Claise (bclaise)" <bclaise@cisco.com <mailto:bclaise@cisco.=
com>>
> Cc: "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mi=
rkovac@cisco.com <mailto:mirkovac@cisco.com>>, "Joe Clarke (jclarke)" <jc=
larke@cisco.com <mailto:jclarke@cisco.com>>, "sabrina.tanamal@iana.org <m=
ailto:sabrina.tanamal@iana.org>" <sabrina.tanamal@iana.org <mailto:sabrin=
a.tanamal@iana.org>>, "amanda.baber@iana.org <mailto:amanda.baber@iana.or=
g>" <amanda.baber@iana.org <mailto:amanda.baber@iana.org>>, YANG Doctors =
<yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>>, Michelle Cotton <=
michelle.cotton@icann.org <mailto:michelle.cotton@icann.org>>
> Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of tru=
th repository
>
>     Benoit,
>
>     Agree that pyang -f should strip the whitespace and do pretty forma=
tting. But none of the examples in RFC 7950 show enum with double-quotes.=

>



From nobody Fri Jan  5 02:27:53 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78A65120721 for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 02:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 S2Z8JzZNqx7q for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 02:27:49 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id E40D7120227 for <yang-doctors@ietf.org>; Fri,  5 Jan 2018 02:27:48 -0800 (PST)
Received: from localhost (h-85-209.A165.priv.bahnhof.se [94.254.85.209]) by mail.tail-f.com (Postfix) with ESMTPSA id 144581AE00B6; Fri,  5 Jan 2018 11:27:46 +0100 (CET)
Date: Fri, 05 Jan 2018 11:27:45 +0100 (CET)
Message-Id: <20180105.112745.1361263416991396812.mbj@tail-f.com>
To: bclaise@cisco.com
Cc: yang-doctors@ietf.org, mirkovac@cisco.com, jclarke@cisco.com, michelle.cotton@icann.org, sabrina.tanamal@iana.org, amanda.baber@iana.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/hhbkKLM1z5A5A23f83l4JjVfbRY>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 10:27:51 -0000

Hi,

Benoit Claise <bclaise@cisco.com> wrote:
> Dear all,
> =

> We can say that the RFC is the source of truth but devops people
> "play" about YANG modules.
> I'm trying to have a single source of truth for the repository of
> RFC-produced YANG modules, while we have multiple ones now.
> =

> IMO, it should be IANA.=A0 We've discussing this option with RFC edit=
or
> and IANA:
> https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtm=
l
> is being transformed in that direction.
> The end goal is that end users, wanted to be up-to-date with the
> latest RFC-produced YANG modules, would perform a cron job such as:
> =A0=A0=A0 rsync -avz --delete rsync.ietf.org::iana/yang-parameters .
> =

> Note: especially interested for IANA-maintained YANG modules such as
> iana-if-type

Note that the IANA-maintained modules are already available there, e.g.=
:

  http://www.iana.org/assignments/yang-parameters/iana-if-type@2017-03-=
30.yang

> Now the follow-up question from IANA:
> =

>    We were working on the posting of the yang modules for
>    _draft-ietf-rtgwg-routing-types
>    <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-t=
ypes/>_
>    per our new process.=A0 When requesting the final files from the
>    RFC-Editor, the file they extracted using their tool and the yang
>    modules appear to have a lot of blank space in them.=A0 See attach=
ed
> =

>    Is this OK?=A0 Do we post it as it is in the provided file from th=
e
>    RFC-Editor?=A0 We know that there is some sensitivity to spacing i=
n
>    these files so we want to make sure the correct thing is being pos=
ted.

I agree that the additional whitespace is an issue.  In the pyang
repo, I store all IETF/IANA modules, and I first extract the modules
then manually go through them to remove extra newlines.  Not ideal.

> The solution should be: pyang -f yang ...

You can do pyang -f yang --keep-comments ...  to keep comments.

But I'm not sure that this is the correct solution.  I think the
stored modules should look the same (not just be semantially
equivalent) as the modules in the RFC.

This said, we should encourage people to use consistent formatting,
and run pyang -f yang or equivalent *before* putting the module into
the RFC.

> However, after some testing:
> =

> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang
> -f yang iana-routing-types@2017-12-04.yang > newfile.yang
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
> iana-routing-types@2017-12-04.yang newfile.yang
> 16d15
> <
> 35,39c34,39
> <=A0=A0=A0 revision 2017-12-04 {
> <=A0=A0=A0=A0=A0 description "Initial revision.";
> <=A0=A0=A0=A0=A0 reference
> <=A0=A0=A0=A0=A0=A0=A0 "RFC 8294: Common YANG Data Types for the Rout=
ing Area.
> <=A0=A0=A0=A0=A0=A0=A0=A0 Section 4.";
> ---
> >=A0=A0 revision 2017-12-04 {
> >=A0=A0=A0=A0 description
> >=A0=A0=A0=A0=A0=A0 "Initial revision.";
> >=A0=A0=A0=A0 reference
> >=A0=A0=A0=A0=A0=A0 "RFC 8294: Common YANG Data Types for the Routing=
 Area.
> >=A0=A0=A0=A0=A0=A0=A0 Section 4.";
> 42,47d41
> <
> <
> <
> <=A0=A0 /*** Collection of IANA types related to routing ***/
> <=A0=A0 /*** IANA Address Family enumeration ***/
> <
> 50c44
> <=A0=A0=A0=A0=A0=A0 enum ipv4 {
> ---
> >=A0=A0=A0=A0=A0=A0 enum "ipv4" {

[...]

> <=A0=A0=A0=A0=A0=A0 enum vpn-auto-discovery-safi {
> ---
> >=A0=A0=A0=A0=A0=A0 enum "vpn-auto-discovery-safi" {
> 485,486c398
> <=A0=A0=A0=A0 reference
> <=A0=A0=A0=A0=A0=A0 "RFC 4760: Multiprotocol Extensions for BGP-4.";
> ---
> >=A0=A0=A0=A0 reference "RFC 4760: Multiprotocol Extensions for BGP-4=
.";
> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$
> =

> pyang -f yang does more than the formatting, it adds double quotes to=

> enum, remove comments, and potentially does more (I don't know what I=

> don't know).

It does a bunch of things considered "best practise" (use single
quotes for XPath expressions, if possible for example), and it
formats everything consistently wrt. whitespaces and quotes.

> So here is the question: do we agree that the IANA, as source of trut=
h
> for YANG modules, should apply pyang -f format before posting a YANG
> module?

I don't think so, as I wrote above.  Ideally the author should somehow
give the module to IANA, but then the problem is that the RFC editor
often makes changes to the module, so we have a sync problem.  Extract
and manually fix newlines is probably the best solution currently.

> Bonus question: if the double quotes for enum is the best solution,
> should it be a warning in validators?

No.  The only reason pyang prints quotes around enums is that
sometimes the quotes are needed, and thus it always prints them, for
consistency.  I could certainly change this so that it prints q/o
quotes in the normal case, and w/ quotes only if it is needed.


/martin


From nobody Fri Jan  5 05:05:53 2018
Return-Path: <acee@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34934129C53 for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 05:05:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 G3PlCx9s_HOD for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 05:05:50 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3586F1200F1 for <yang-doctors@ietf.org>; Fri,  5 Jan 2018 05:05:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3244; q=dns/txt; s=iport; t=1515157550; x=1516367150; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=0oyn10FJKaWG9r0Boz8ASwgSiZNCVQniK85rbUnnukE=; b=mmyfrmC5dlQpycHtfSX/MtUo+Nohjvyd6IwEHZr+DHc8F1h1KevOwYa5 pdgG4Y5B3XddwKOdsPzIoxs+GKe2JwVz5IB1xyrxfgxS57umaLVl2iDED crB3Vp1amndnESXJOPkR8Q+jQoGmv509vNlokcl/TeVrmYWF9RvxHHD0p s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AwAwAId09a/5FdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM+gVonB4QAmSyCAokIjiKCFQqFOwIahBpAFwEBAQEBAQEBAWs?= =?us-ascii?q?ohSMBAQEBAyMRRRACAQYCEQMBAgMCIwMCAgIfERQBCAgCBAENBYoXAxWSZ51ug?= =?us-ascii?q?ieHPg2CcAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2BD4MFghWGbYJrRYFugxeCRSA?= =?us-ascii?q?FkiSQez0CkDqFAJQGjXCIdgIRGQGBOwEhATaBUG8VgmeEV3iIQ4EXAQEB?=
X-IronPort-AV: E=Sophos;i="5.46,318,1511827200"; d="scan'208";a="333341955"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Jan 2018 13:05:49 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w05D5muf007105 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 Jan 2018 13:05:49 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 5 Jan 2018 08:05:48 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Fri, 5 Jan 2018 08:05:47 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: =?utf-8?B?UmFkZWsgS3JlasSNw60=?= <rkrejci@cesnet.cz>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
CC: "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, "sabrina.tanamal@iana.org" <sabrina.tanamal@iana.org>, "amanda.baber@iana.org" <amanda.baber@iana.org>, YANG Doctors <yang-doctors@ietf.org>, Michelle Cotton <michelle.cotton@icann.org>
Thread-Topic: [yang-doctors] YANG module & pyang -f yang & source of truth repository
Thread-Index: AQHThUz+DITYqtvd00SqlLtXxv7/KKNkLGsA///CPACAAWGKAP//8PgA
Date: Fri, 5 Jan 2018 13:05:47 +0000
Message-ID: <D674E014.E87CB%acee@cisco.com>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <0766646B-7D4C-4BA9-B4B0-CCB553D954CA@gmail.com> <D673C621.E8591%acee@cisco.com> <ca8dd36b-9d29-a468-b2dd-a7e7af51c288@cesnet.cz>
In-Reply-To: <ca8dd36b-9d29-a468-b2dd-a7e7af51c288@cesnet.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F2B7B4CCE17F4A459234BE070C500109@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/obDl9Da0lk4xuJS_d89lVkdAdMU>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 13:05:52 -0000

SGkgUmFkZWssIA0KDQpPbiAxLzUvMTgsIDM6NTkgQU0sICJSYWRlayBLcmVqxI3DrSIgPHJrcmVq
Y2lAY2VzbmV0LmN6PiB3cm90ZToNCg0KPkhpLA0KPm5vdCBzdXJlIGlmIGl0IGlzIHRoZSBjYXNl
IG9mIHB5YW5nLCBidXQgd2l0aCBteSBleHBlcmllbmNlIHdpdGggbGlieWFuZywNCj5pdCBpcyBu
b3QgYSBwcm9ibGVtIHRvIHByaW50IGVudW1zIHdpdGhvdXQgcXVvdGVzLCBidXQgaXQgaXMgYSBw
cm9ibGVtIHRvDQo+cHJlc2VydmUgd2hhdCB3YXMgaW4gaW5wdXQgZmlsZS4gZW51bSBjYW4gYmUg
d3JpdHRlbiB3aXRoIG9yIHdpdGhvdXQNCj5xdW90ZXMgYW5kIGluIHNvbWUgY2FzZXMgc29tZSBx
dW90ZXMgYXJlIG5lY2Vzc2FyeS4NCg0KV2hpbGUgdGhlIGVudW0gbmFtZSBjYW4gYmUgYSBzdHJp
bmcgaW5jbHVkaW5nIGVtYmVkZGVkIHdoaXRlc3BhY2UsIEkgdGhpbmsNCnRoaXMgc2hvdWxkIGJl
IGRpc2NvdXJhZ2VkIGFuZCBvbmx5IHZhbHVlcyB0aGF0IHNhdGlzZnkgdGhlIGNvbnN0cmFpbnRz
DQpmb3IgYSBZQU5HIGlkZW50aWZpZXIgc2hvdWxkIGJlIHVzZWQuDQoNClRoYW5rcywNCkFjZWUg
DQoNCg0KDQo+VGhlcmVmb3JlLCBhdCBsZWFzdCBsaWJ5YW5nL3lhbmdsaW50LCBjaG9vc2VzIGNv
bnNpc3RlbmN5IGFuZCBhbHdheXMNCj5wcmludCBkb3VibGUgcXVvdGVzIGFyb3VuZCBlbnVtcy4g
QW5kIGl0IGlzIG5vdCBvbmx5IHRoZSBjYXNlIG9mIGVudW1zLA0KPmV2ZW4gb25lLXdvcmQgZGVz
Y3JpcHRpb24gaXMgYWx3YXlzIHF1b3RlZC4gT24gdGhlIG90aGVyIGhhbmQsIEkgZG9uJ3QNCj50
aGluayB0aGF0IHRoZSBhdXRob3Igc2hvdWxkIGJlIHdhcm5lZCB3aGVuIHRoZXJlIGFyZSBubyBx
dW90ZXMuIFdoZW4gdGhlDQo+cnVsZXMgZm9yIHRoZSBzdHJpbmcgY29udGVudCBhcmUgbm90IHZp
b2xhdGVkLCB0aGUgc3BlY3MgYWxsb3dzIGUuZy4gZm9vLA0KPiJmb28iIGFuZCAnZm9vJy4NCj4N
Cj5SZWdhcmRzLA0KPlJhZGVrDQo+DQo+DQo+RG5lIDQuMS4yMDE4IHYgMTc6NTQgQWNlZSBMaW5k
ZW0gKGFjZWUpIG5hcHNhbChhKToNCj4+IEhpIFlBTkcgRG9jdG9ycywNCj4+DQo+PiBQZXJzb25h
bGx5LCBJIGRvbuKAmXQgbGlrZSB0aGUgZG91YmxlIHF1b3Rpbmcgb2YgZW51bXMuDQo+Pg0KPj4g
VGhhbmtzLA0KPj4gQWNlZQ0KPj4NCj4+IEZyb206IHlhbmctZG9jdG9ycyA8eWFuZy1kb2N0b3Jz
LWJvdW5jZXNAaWV0Zi5vcmcNCj4+PG1haWx0bzp5YW5nLWRvY3RvcnMtYm91bmNlc0BpZXRmLm9y
Zz4+IG9uIGJlaGFsZiBvZiBNYWhlc2ggSmV0aGFuYW5kYW5pDQo+PjxtamV0aGFuYW5kYW5pQGdt
YWlsLmNvbSA8bWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tPj4NCj4+IERhdGU6IFRodXJz
ZGF5LCBKYW51YXJ5IDQsIDIwMTggYXQgMTA6MzUgQU0NCj4+IFRvOiAiQmVub2l0IENsYWlzZSAo
YmNsYWlzZSkiIDxiY2xhaXNlQGNpc2NvLmNvbQ0KPj48bWFpbHRvOmJjbGFpc2VAY2lzY28uY29t
Pj4NCj4+IENjOiAiTWlyb3NsYXYgS292YWMgLVggKG1pcmtvdmFjIC0gUEFOVEhFT04gVEVDSE5P
TE9HSUVTIGF0IENpc2NvKSINCj4+PG1pcmtvdmFjQGNpc2NvLmNvbSA8bWFpbHRvOm1pcmtvdmFj
QGNpc2NvLmNvbT4+LCAiSm9lIENsYXJrZSAoamNsYXJrZSkiDQo+PjxqY2xhcmtlQGNpc2NvLmNv
bSA8bWFpbHRvOmpjbGFya2VAY2lzY28uY29tPj4sDQo+PiJzYWJyaW5hLnRhbmFtYWxAaWFuYS5v
cmcgPG1haWx0bzpzYWJyaW5hLnRhbmFtYWxAaWFuYS5vcmc+Ig0KPj48c2FicmluYS50YW5hbWFs
QGlhbmEub3JnIDxtYWlsdG86c2FicmluYS50YW5hbWFsQGlhbmEub3JnPj4sDQo+PiJhbWFuZGEu
YmFiZXJAaWFuYS5vcmcgPG1haWx0bzphbWFuZGEuYmFiZXJAaWFuYS5vcmc+Ig0KPj48YW1hbmRh
LmJhYmVyQGlhbmEub3JnIDxtYWlsdG86YW1hbmRhLmJhYmVyQGlhbmEub3JnPj4sIFlBTkcgRG9j
dG9ycw0KPj48eWFuZy1kb2N0b3JzQGlldGYub3JnIDxtYWlsdG86eWFuZy1kb2N0b3JzQGlldGYu
b3JnPj4sIE1pY2hlbGxlIENvdHRvbg0KPj48bWljaGVsbGUuY290dG9uQGljYW5uLm9yZyA8bWFp
bHRvOm1pY2hlbGxlLmNvdHRvbkBpY2Fubi5vcmc+Pg0KPj4gU3ViamVjdDogUmU6IFt5YW5nLWRv
Y3RvcnNdIFlBTkcgbW9kdWxlICYgcHlhbmcgLWYgeWFuZyAmIHNvdXJjZSBvZg0KPj50cnV0aCBy
ZXBvc2l0b3J5DQo+Pg0KPj4gICAgIEJlbm9pdCwNCj4+DQo+PiAgICAgQWdyZWUgdGhhdCBweWFu
ZyAtZiBzaG91bGQgc3RyaXAgdGhlIHdoaXRlc3BhY2UgYW5kIGRvIHByZXR0eQ0KPj5mb3JtYXR0
aW5nLiBCdXQgbm9uZSBvZiB0aGUgZXhhbXBsZXMgaW4gUkZDIDc5NTAgc2hvdyBlbnVtIHdpdGgN
Cj4+ZG91YmxlLXF1b3Rlcy4NCj4+DQo+DQo+DQoNCg==


From nobody Fri Jan  5 07:38:44 2018
Return-Path: <rkrejci@cesnet.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69778126C2F for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 07:38:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level: 
X-Spam-Status: No, score=-4.309 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_MED=-2.3, T_RP_MATCHES_RCVD=-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=cesnet.cz
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 0YBP664h3QQv for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 07:38:41 -0800 (PST)
Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) (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 DE4A1124C27 for <yang-doctors@ietf.org>; Fri,  5 Jan 2018 07:38:40 -0800 (PST)
Received: from pckrejci.nat9.vcit.vutbr.net (unknown [IPv6:2001:67c:1220:80c:d0:552c:73a5:18da]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by office2.cesnet.cz (Postfix) with ESMTPSA id 79BC340004E; Fri,  5 Jan 2018 16:38:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=office2; t=1515166717; bh=CsAYy5ItQrM0EeovYXvem456c25l/M+WRmbDqaOQqPc=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=qGDgDR5Xrotrz01QQe++51rgnuVxCeyoKkk01axW+VdoDqL+q1iDuX6ylh/aEtJK3 s5StrHTem/8Z5LNj7WFuwMUYeutdCNEi3MIAHN2olCU4sugi3si+v0yRe9BLte5YdA 4VCW+slPsos4nOA66RlmX4d2bP/b11gA+9UPG/w4=
To: "Acee Lindem (acee)" <acee@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
Cc: "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)" <mirkovac@cisco.com>, "Joe Clarke (jclarke)" <jclarke@cisco.com>, "sabrina.tanamal@iana.org" <sabrina.tanamal@iana.org>, "amanda.baber@iana.org" <amanda.baber@iana.org>, YANG Doctors <yang-doctors@ietf.org>, Michelle Cotton <michelle.cotton@icann.org>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <0766646B-7D4C-4BA9-B4B0-CCB553D954CA@gmail.com> <D673C621.E8591%acee@cisco.com> <ca8dd36b-9d29-a468-b2dd-a7e7af51c288@cesnet.cz> <D674E014.E87CB%acee@cisco.com>
From: =?UTF-8?B?UmFkZWsgS3JlasSNw60=?= <rkrejci@cesnet.cz>
Message-ID: <0ae2f087-f003-eac9-a9e3-b842e86ee002@cesnet.cz>
Date: Fri, 5 Jan 2018 16:38:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <D674E014.E87CB%acee@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/WSHM3IbGoeYobpHY2vzjsQEWJbw>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 15:38:43 -0000

Hi Acee,

Dne 5.1.2018 v 14:05 Acee Lindem (acee) napsal(a):
> Hi Radek,=20
>
> On 1/5/18, 3:59 AM, "Radek Krej=C4=8D=C3=AD" <rkrejci@cesnet.cz> wrote:=

>
>> Hi,
>> not sure if it is the case of pyang, but with my experience with libya=
ng,
>> it is not a problem to print enums without quotes, but it is a problem=
 to
>> preserve what was in input file. enum can be written with or without
>> quotes and in some cases some quotes are necessary.
> While the enum name can be a string including embedded whitespace, I th=
ink
> this should be discouraged and only values that satisfy the constraints=

> for a YANG identifier should be used.

this can be said in guidelines (RFC6087bis), but from the YANG parsers an=
d validators perspective, these names (with whitespaces) are completely v=
alid and parsers have to accept them since they are allowed by the specif=
ication. libyang and pyang just decided to print all these names the same=
 way to be consistent.

Radek


> Thanks,
> Acee=20
>
>
>
>> Therefore, at least libyang/yanglint, chooses consistency and always
>> print double quotes around enums. And it is not only the case of enums=
,
>> even one-word description is always quoted. On the other hand, I don't=

>> think that the author should be warned when there are no quotes. When =
the
>> rules for the string content are not violated, the specs allows e.g. f=
oo,
>> "foo" and 'foo'.
>>
>> Regards,
>> Radek
>>
>>
>> Dne 4.1.2018 v 17:54 Acee Lindem (acee) napsal(a):
>>> Hi YANG Doctors,
>>>
>>> Personally, I don=E2=80=99t like the double quoting of enums.
>>>
>>> Thanks,
>>> Acee
>>>
>>> From: yang-doctors <yang-doctors-bounces@ietf.org
>>> <mailto:yang-doctors-bounces@ietf.org>> on behalf of Mahesh Jethanand=
ani
>>> <mjethanandani@gmail.com <mailto:mjethanandani@gmail.com>>
>>> Date: Thursday, January 4, 2018 at 10:35 AM
>>> To: "Benoit Claise (bclaise)" <bclaise@cisco.com
>>> <mailto:bclaise@cisco.com>>
>>> Cc: "Miroslav Kovac -X (mirkovac - PANTHEON TECHNOLOGIES at Cisco)"
>>> <mirkovac@cisco.com <mailto:mirkovac@cisco.com>>, "Joe Clarke (jclark=
e)"
>>> <jclarke@cisco.com <mailto:jclarke@cisco.com>>,
>>> "sabrina.tanamal@iana.org <mailto:sabrina.tanamal@iana.org>"
>>> <sabrina.tanamal@iana.org <mailto:sabrina.tanamal@iana.org>>,
>>> "amanda.baber@iana.org <mailto:amanda.baber@iana.org>"
>>> <amanda.baber@iana.org <mailto:amanda.baber@iana.org>>, YANG Doctors
>>> <yang-doctors@ietf.org <mailto:yang-doctors@ietf.org>>, Michelle Cott=
on
>>> <michelle.cotton@icann.org <mailto:michelle.cotton@icann.org>>
>>> Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of
>>> truth repository
>>>
>>>     Benoit,
>>>
>>>     Agree that pyang -f should strip the whitespace and do pretty
>>> formatting. But none of the examples in RFC 7950 show enum with
>>> double-quotes.
>>>
>>



From nobody Fri Jan  5 08:04:18 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DCA112D838 for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 08:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 Aa51ze8xHH1g for <yang-doctors@ietfa.amsl.com>; Fri,  5 Jan 2018 08:04:13 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id D8701124C27 for <yang-doctors@ietf.org>; Fri,  5 Jan 2018 08:04:12 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 6D89B1820414; Fri,  5 Jan 2018 17:03:57 +0100 (CET)
Received: from localhost (nat-2.nic.cz [217.31.205.2]) by trail.lhotka.name (Postfix) with ESMTPSA id 97A621820410; Fri,  5 Jan 2018 17:03:50 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>, bclaise@cisco.com
Cc: mirkovac@cisco.com, jclarke@cisco.com, sabrina.tanamal@iana.org, amanda.baber@iana.org, yang-doctors@ietf.org, michelle.cotton@icann.org
In-Reply-To: <20180105.112745.1361263416991396812.mbj@tail-f.com>
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <20180105.112745.1361263416991396812.mbj@tail-f.com>
Date: Fri, 05 Jan 2018 17:04:03 +0100
Message-ID: <87wp0w1edo.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/ulZjn0k7wNYKK9YUJjuxqamjhAw>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jan 2018 16:04:16 -0000

Martin Bjorklund <mbj@tail-f.com> writes:

> Hi,
>
> Benoit Claise <bclaise@cisco.com> wrote:
>> Dear all,
>>=20
>> We can say that the RFC is the source of truth but devops people
>> "play" about YANG modules.
>> I'm trying to have a single source of truth for the repository of
>> RFC-produced YANG modules, while we have multiple ones now.
>>=20
>> IMO, it should be IANA.=C2=A0 We've discussing this option with RFC edit=
or
>> and IANA:
>> https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
>> is being transformed in that direction.
>> The end goal is that end users, wanted to be up-to-date with the
>> latest RFC-produced YANG modules, would perform a cron job such as:
>> =C2=A0=C2=A0=C2=A0 rsync -avz --delete rsync.ietf.org::iana/yang-paramet=
ers .
>>=20
>> Note: especially interested for IANA-maintained YANG modules such as
>> iana-if-type
>
> Note that the IANA-maintained modules are already available there, e.g.:
>
>   http://www.iana.org/assignments/yang-parameters/iana-if-type@2017-03-30=
.yang
>
>> Now the follow-up question from IANA:
>>=20
>>    We were working on the posting of the yang modules for
>>    _draft-ietf-rtgwg-routing-types
>>    <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-type=
s/>_
>>    per our new process.=C2=A0 When requesting the final files from the
>>    RFC-Editor, the file they extracted using their tool and the yang
>>    modules appear to have a lot of blank space in them.=C2=A0 See attach=
ed
>>=20
>>    Is this OK?=C2=A0 Do we post it as it is in the provided file from the
>>    RFC-Editor?=C2=A0 We know that there is some sensitivity to spacing in
>>    these files so we want to make sure the correct thing is being posted.
>
> I agree that the additional whitespace is an issue.  In the pyang
> repo, I store all IETF/IANA modules, and I first extract the modules
> then manually go through them to remove extra newlines.  Not ideal.
>
>> The solution should be: pyang -f yang ...
>
> You can do pyang -f yang --keep-comments ...  to keep comments.

This fails for some legal comments:

$ cat triva.yang
module triva {
  namespace "http://example.com/ll/triva";
  prefix ta;

  leaf "foo" /* comment */ + "bar" {
    type string;
  }
}
$ pyang -f yang --keep-comments triva.yang
triva.yang:5: error: unterminated statement definition for keyword "leaf", =
looking at /

>
> But I'm not sure that this is the correct solution.  I think the
> stored modules should look the same (not just be semantially
> equivalent) as the modules in the RFC.
>
> This said, we should encourage people to use consistent formatting,
> and run pyang -f yang or equivalent *before* putting the module into
> the RFC.

We should agree on some rules and make sure our tools follow them. It
should be like

1. Statements are split into three categories: with unquoted,
double-quoted and single-quoted arguments.

2. Quoting is added where needed, and unquoted args are then transformed
preferably into double-quoted if possible.

BTW, another benefit of writing modules in the YIN syntax is that
one needn't care at all about quoting, breaking long arguments etc. My
XSLT stylesheet then I think does a very decent job in transforming it
to the YANG syntax:

https://github.com/CZ-NIC/yangson/blob/master/tools/xslt/yin2yang.xsl

And when I am at it, it would IMO be hugely beneficial to be able to
include YIN modules in the xml2rfc XML source (if the xml2rfc tool
supported it). We wouldn't then need <artwork>, <CODE BEGINS> lines
could be autogenerated so that they are never out of sync with the
module, and in HTML-rendered RFCs we could have pretty-printed modules
with cross-references appearing as active links.

Oh well ...

Lada

>
>> However, after some testing:
>>=20
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang
>> -f yang iana-routing-types@2017-12-04.yang > newfile.yang
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
>> iana-routing-types@2017-12-04.yang newfile.yang
>> 16d15
>> <
>> 35,39c34,39
>> <=C2=A0=C2=A0=C2=A0 revision 2017-12-04 {
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 description "Initial revision.";
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 reference
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "RFC 8294: Common YANG Data =
Types for the Routing Area.
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Section 4.";
>> ---
>> >=C2=A0=C2=A0 revision 2017-12-04 {
>> >=C2=A0=C2=A0=C2=A0=C2=A0 description
>> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "Initial revision.";
>> >=C2=A0=C2=A0=C2=A0=C2=A0 reference
>> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "RFC 8294: Common YANG Data Types =
for the Routing Area.
>> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Section 4.";
>> 42,47d41
>> <
>> <
>> <
>> <=C2=A0=C2=A0 /*** Collection of IANA types related to routing ***/
>> <=C2=A0=C2=A0 /*** IANA Address Family enumeration ***/
>> <
>> 50c44
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 enum ipv4 {
>> ---
>> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 enum "ipv4" {
>
> [...]
>
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 enum vpn-auto-discovery-safi {
>> ---
>> >=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 enum "vpn-auto-discovery-safi" {
>> 485,486c398
>> <=C2=A0=C2=A0=C2=A0=C2=A0 reference
>> <=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 "RFC 4760: Multiprotocol Extension=
s for BGP-4.";
>> ---
>> >=C2=A0=C2=A0=C2=A0=C2=A0 reference "RFC 4760: Multiprotocol Extensions =
for BGP-4.";
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$
>>=20
>> pyang -f yang does more than the formatting, it adds double quotes to
>> enum, remove comments, and potentially does more (I don't know what I
>> don't know).
>
> It does a bunch of things considered "best practise" (use single
> quotes for XPath expressions, if possible for example), and it
> formats everything consistently wrt. whitespaces and quotes.
>
>> So here is the question: do we agree that the IANA, as source of truth
>> for YANG modules, should apply pyang -f format before posting a YANG
>> module?
>
> I don't think so, as I wrote above.  Ideally the author should somehow
> give the module to IANA, but then the problem is that the RFC editor
> often makes changes to the module, so we have a sync problem.  Extract
> and manually fix newlines is probably the best solution currently.
>
>> Bonus question: if the double quotes for enum is the best solution,
>> should it be a warning in validators?
>
> No.  The only reason pyang prints quotes around enums is that
> sometimes the quotes are needed, and thus it always prints them, for
> consistency.  I could certainly change this so that it prints q/o
> quotes in the normal case, and w/ quotes only if it is needed.
>
>
> /martin
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

--=20
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan  8 07:23:44 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC64129C53; Mon,  8 Jan 2018 07:23:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 HBQgomRIrLpJ; Mon,  8 Jan 2018 07:23:37 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3B32912706D; Mon,  8 Jan 2018 07:23:37 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id CCE1C1AE0332; Mon,  8 Jan 2018 16:23:35 +0100 (CET)
Date: Mon, 08 Jan 2018 16:21:53 +0100 (CET)
Message-Id: <20180108.162153.18427707995478583.mbj@tail-f.com>
To: rkrejci@cesnet.cz
Cc: yang-doctors@ietf.org, draft-ietf-netmod-entity.all@ietf.org, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <151507502144.23798.1644071576333370968@ietfa.amsl.com>
References: <151507502144.23798.1644071576333370968@ietfa.amsl.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Pso9bZKaqnugFdAbnKkQUbagxeU>
Subject: Re: [yang-doctors] [netmod] Yangdoctors last call review of draft-ietf-netmod-entity-07
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 15:23:39 -0000

SGksDQoNClJhZGVrIEtyZWrEjcOtIDxya3JlamNpQGNlc25ldC5jej4gd3JvdGU6DQo+IFJldmll
d2VyOiBSYWRlayBLcmVqxI3DrQ0KPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0K
PiANCj4gVGhlIGRvY3VtZW50IGl0c2VsZiBhbmQgbm9ybWF0aXZlIHBhcnRzIHNlZW0gZmluZSB0
byBtZSwgdGhlIG9ubHkgaXNzdWUgSSBzZWUNCj4gaXMgd2l0aCB0aGUgaWV0Zi1oYXJkd2FyZS1z
dGF0ZSBtb2R1bGUgaW4gbm9uLW5vcm1hdGl2ZSBhcHBlbmRpeCBBLiBJdCBzZWVtcyB0bw0KPiBt
ZSB0aGF0IHRoaXMgdGVtcG9yYXJ5IG5vbi1OTURBIG1vZHVsZSBkb2VzIG5vdCBjb25mb3JtIHRv
IGl0cyBwdXJwb3NlIGFzDQo+IGRlc2NyaWJlZCBpbiBSRkM2MDg3YmlzLiBBY2NvcmRpbmcgdG8g
Z3VpZGVsaW5lcywgc3VjaCBhIG1vZHVsZSBpcyBpbnRlbmRlZCB0bw0KPiBwcm92aWRlIHN0YXRl
IChjb25maWcgZmFsc2UpIGRhdGEgaW4gY2FzZSB0aGUgc2VydmVyIGRvZXMgbm90IGltcGxlbWVu
dCBOTURBDQo+ICh0byBicmlkZ2UgdGhlIHRpbWUgcGVyaW9kIHVudGlsIE5NREEgaXMgaW1wbGVt
ZW50ZWQpLiBTbyBzdWNoIGEgc2VydmVyIGlzIElNSE8NCj4gaW50ZW5kZWQgdG8gaW1wbGVtZW50
IGJvdGggbW9kdWxlcywgZm9vIGFuZCBmb28tc3RhdGUuIFRoZSBmb28tc3RhdGUgY29udGFpbnMN
Cj4gInRoZSB0b3AtbGV2ZWwgY29uZmlnLWZhbHNlIGRhdGEgbm9kZXMgdGhhdCB3b3VsZCBoYXZl
IGJlZW4gZGVmaW5lZCBpbiBhIGxlZ2FjeQ0KPiBZQU5HIG1vZHVsZSIgLSBzbyBpdCdzIG9ubHkg
dGhlIHJvIG1pcnJvciBvZiBkYXRhIG5vZGVzLiBCdXQNCj4gaWV0Zi1oYXJkd2FyZS1zdGF0ZSBj
b250YWlucyBub3RpZmljYXRpb25zLCB3aGljaCBhcmUgbm90IHRoZSBkYXRhIG5vZGVzIGFzDQo+
IGRlZmluZWQgaW4gUkZDNzk1MC4gSSB1bmRlcnN0YW5kIHdoeSB0aGUgbm90aWZpY2F0aW9ucyB3
ZXJlIHBsYWNlZCBhbHNvIGludG8NCj4gdGhlIGlldGYtaGFyZHdhcmUtc3RhdGUgLSB0aGUgbW9k
dWxlJ3MgZGVzY3JpcHRpb24gc3RhdGVzIHRoYXQgIklmIGEgc2VydmVyDQo+IHRoYXQgaW1wbGVt
ZW50cyB0aGlzIG1vZHVsZSBidXQgZG9lc24ndCBzdXBwb3J0IE5NREEgYWxzbyBzdXBwb3J0cw0K
PiBjb25maWd1cmF0aW9uIG9mIGhhcmR3YXJlIGNvbXBvbmVudHMsIGl0IFNIT1VMRCBhbHNvIGlt
cGxlbWVudCB0aGUgbW9kdWxlDQo+ICdpZXRmLWhhcmR3YXJlJyAuLi4iLCBzbyBpdCBhbGxvd3Mg
aXRzIHN0YW5kYWxvbmUgdXNhZ2UgaW4gY2FzZSB0aGUgc2VydmVyIGRvZXMNCj4gbm90IHN1cHBv
cnQgaHcgY29uZmlndXJhdGlvbi4gQnV0IGluIHN1Y2ggYSBjYXNlLCB0aGUgc2VydmVyIGNhbiBp
bXBsZW1lbnQNCj4gaWV0Zi1oYXJkd2FyZSB3aXRoIGRldmlhdGlvbnMgb24gdGhlIGNvbmZpZz10
cnVlIG5vZGVzLg0KDQpUaGUgcHJvYmxlbSB3aXRoIHVzZWluZyB0aGUgbm90aWZjYXRpb25zIGRl
ZmluZWQgaW4gaWV0Zi1oYXJkd2FyZSBpbg0KdGhpcyBjYXNlIGlzIHRoYXQgYWxsIGxlYWZyZWZz
IHdvdWxkIGJlIHdyb25nOyB0aGV5J2QgcG9pbnQgaW50byBhDQpzY2hlbWEgdGhhdCBpcyBub3Qg
aW1wbGVtZW50ZWQuDQoNCj4gVGhlIHNhbWUgd2F5IGl0IGhhZCB0bw0KPiBpbXBsZW1lbnQgdGhl
IGxlZ2FjeSBZQU5HIG1vZHVsZSAoYmVmb3JlIE5NREEpLg0KDQpCZWZvcmUgTk1EQSB0aGUgbGVh
ZnJlZnMgaW4gdGhlIG5vdGlmY2F0aW9ucyBwb2ludGVkIHRvDQovaGFyZHdhcmUtc3RhdGUsIGFu
ZCBhbGwgY29uZmlnIHdhcyBkZWZpbmVkIHdpdGggYW4gaWYtZmVhdHVyZSwgc28gYQ0Kc2VydmVy
IGRpZCBub3QgaGF2ZSB0byB1c2UgYW55IGRldmlhdGlvbnMgaW4gdGhpcyBjYXNlLg0KDQoNCg0K
L21hcnRpbg0KDQoNCg0KPiANCj4gU28gSSB0aGluayB0aGF0IHRoZSBub3RpZmljYXRpb25zIHNo
b3VsZCBiZSByZW1vdmVkIGZyb20gaWV0Zi1oYXJkd2FyZS1zdGF0ZQ0KPiBhbmQgdGhlIG1vZHVs
ZSdzIGRlc2NyaXB0aW9uIHNob3VsZCBjaGFuZ2UgdGhpcyB3YXk6DQo+IA0KPiBPTEQNCj4gDQo+
ICAgSWYgYSBzZXJ2ZXIgdGhhdCBpbXBsZW1lbnRzIHRoaXMgbW9kdWxlIGJ1dCBkb2Vzbid0IHN1
cHBvcnQgTk1EQQ0KPiAgIGFsc28gc3VwcG9ydHMgY29uZmlndXJhdGlvbiBvZiBoYXJkd2FyZSBj
b21wb25lbnRzLCBpdCBTSE9VTEQNCj4gICBhbHNvIGltcGxlbWVudCB0aGUgbW9kdWxlICdpZXRm
LWhhcmR3YXJlJyBpbiB0aGUgY29uZmlndXJhdGlvbg0KPiAgIGRhdGFzdG9yZXMuIFRoZSBjb3Jy
ZXNwb25kaW5nIHN0YXRlIGRhdGEgaXMgZm91bmQgaW4gdGhlDQo+ICAgJy9ody1zdGF0ZTpoYXJk
d2FyZScgc3VidHJlZS4NCj4gDQo+IE5FVw0KPiANCj4gICBJZiBhIHNlcnZlciB0aGF0IGltcGxl
bWVudHMgdGhpcyBtb2R1bGUgYnV0IGRvZXNuJ3Qgc3VwcG9ydCBOTURBLA0KPiAgIGl0IE1VU1Qg
YWxzbyBpbXBsZW1lbnQgdGhlIG1vZHVsZSAnaWV0Zi1oYXJkd2FyZScgaW4gdGhlDQo+ICAgY29u
ZmlndXJhdGlvbiBkYXRhc3RvcmVzLiBUaGUgY29ycmVzcG9uZGluZyBzdGF0ZSBkYXRhIGlzIGZv
dW5kDQo+ICAgaW4gdGhlICcvaHctc3RhdGU6aGFyZHdhcmUnIHN1YnRyZWUuDQo+IA0KPiANCj4g
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gbmV0bW9k
IG1haWxpbmcgbGlzdA0KPiBuZXRtb2RAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9uZXRtb2QNCg==


From nobody Mon Jan  8 11:18:14 2018
Return-Path: <mersue@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5007512D7F7 for <yang-doctors@ietfa.amsl.com>; Mon,  8 Jan 2018 11:18:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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=gmail.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 lvCB8n_btsM5 for <yang-doctors@ietfa.amsl.com>; Mon,  8 Jan 2018 11:18:11 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 7830412D7E9 for <yang-doctors@ietf.org>; Mon,  8 Jan 2018 11:18:11 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id b141so16244769wme.1 for <yang-doctors@ietf.org>; Mon, 08 Jan 2018 11:18:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=sbdzczpGellesl5Yza/NCXDk8oQjYi9GEy6LkdI8OxI=; b=npAnN0HjrxApgh/5XjNJPa+fLAe3TajbnA6fMxuPip55xlKvNrBCxri2fWc92tkdTV 39u3X5aEQeepxrjhnhZVlWEzXfp4MOe/ota3fexMgjgUe2HM3arNE1e68Bj15VGBWrAH E/HhjQhiI1CobW+WaOf//BgiyfzRkviWG7Ct1dICLvKvfp/gtK4E8fGde/ghSmHu7lNg fm82/nJ2YVtqbj+sJsD/jadINmX2Jy953gCwCgEzpYhSGE4ggWCJ16oFHoLvi4zJNI8r 3+fRvp6Xlt5gIwEB0Lsx0/0THLjJ/1a4yjihQKQ6Z6mbkhCTYgRnIP4RVGFAv4+fEPKz q4ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=sbdzczpGellesl5Yza/NCXDk8oQjYi9GEy6LkdI8OxI=; b=C8zuk1yaXl2R4j8eKCpnV7Sw71EXDcxqBl6WiQNU+5dn/wEf3zaghJpEq/Dap2p/2W xS+vWeEWZ+7hGCrJNTalWA6aIqgN5LQp1yfd5ySCE6kb5vmxPjfwvUkq8LdVG2Hbr8ba iVqtHyqApiWWkbHofW95GjH29ifK9DoZ/REusbiylbyg/+CVB/q/e/CGSmiBciAmB9fC +YNyZs3iT/5JWcaAEiYyv6v+WxzJ+GRe/uLsNhzcqSzRpLZY+89/6oJ/WYkKlVVv9nWS rQfEOHF/0IENmNBwblavYi4A1mi9Hzjsnd8I3Z6wztIp8J4u0pUGvI8YoNpQlHLUkFkt Pajw==
X-Gm-Message-State: AKGB3mKeXFPf/7To7ln9uI1VN5nIhJTO72HHWgm9l8z3yaJMV89YYcNg +6yVP+5wF7bNhlo31Aua3ZOn8Pif
X-Google-Smtp-Source: ACJfBosvKRq/6WbX0ZVjwknVGEBXq6wNp7PvCaHC4BiPvUSqivcehyetf+PNMOjEJT5m24HLywgz+A==
X-Received: by 10.28.74.72 with SMTP id x69mr10459150wma.126.1515439089379; Mon, 08 Jan 2018 11:18:09 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([2001:16b8:2d4f:8c00:5537:d0a4:551e:41dc]) by smtp.gmail.com with ESMTPSA id n74sm16043703wmi.1.2018.01.08.11.18.08 for <yang-doctors@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jan 2018 11:18:08 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'YANG Doctors'" <yang-doctors@ietf.org>
References: 
In-Reply-To: 
Date: Mon, 8 Jan 2018 20:18:06 +0100
Message-ID: <016601d388b5$6a7de510$3f79af30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0167_01D388BD.CC429B30"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdNy1Mpv4ITy2qi/Rc2cRbbQ1AlWpwV306sg
Content-Language: de
X-MS-TNEF-Correlator: 00000000C69E16B615ED5F4C9AF09728F866A19A0700C3B68E10F77511CEB4CD00AA00BBB6E600000000000D00005F7FD4929BD1E24D8901915DC757ED0500000000885D0000
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/4rdKlPNk4rulNAIqRppJkXMGvic>
Subject: [yang-doctors] Summary of Open Review Assignments for YANG Doctors
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 19:18:13 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0167_01D388BD.CC429B30
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear YANG Doctors,

following is the list of YANG modules currently in review.


Reviewer               LC end     Draft
Jan Lindblad           2018-01-10 =
draft-ietf-netmod-revised-datastores-09=20

Early review requests:

Reviewer               Due        Draft
Ebben Aries            2018-01-04 draft-ietf-i2rs-rib-data-model-09=20
Carl Moberg            2018-01-10
draft-ietf-lime-yang-connection-oriented-oam-model-01=20
Reshad Rahman          2017-12-13 draft-ietf-pim-msdp-yang-01=20

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation (this is what the tools shows right now,=20
but it looks incorrect. I=E2=80=99ll check with the tool guys):

  Ladislav Lhotka
  Jan Lindblad
  Acee Lindem
  Carl Moberg
  Reshad Rahman
  J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
  Kent Watsen
  Ebben Aries
  Andy Bierman

Cheers,
Mehmet


------=_NextPart_000_0167_01D388BD.CC429B30
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="winmail.dat"

eJ8+IggTAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQgABQAEAAAAAAAAAAAAAQkABAACAAAAAAAAAAEDkAYASBYAACkA
AAALAAIAAQAAAAMAJgAAAAAACwApAAAAAAALACsAAAAAAAMALgAAAAAAHgBNAAEAAAABAAAAAAAA
AB4AcAABAAAANAAAAFN1bW1hcnkgb2YgT3BlbiBSZXZpZXcgQXNzaWdubWVudHMgZm9yIFlBTkcg
RG9jdG9ycwACAXEAAQAAABsAAAAB03LUym/ghPLaqL9FzZxFttDUCVanBXfTqyAACwAXDAAAAAAL
AAEOAQAAAAMAFA4BAAAAHgAoDgEAAAAgAAAAMDAwMDAwMDMBbWVyc3VlQGdtYWlsLmNvbQFHbWFp
bAAeACkOAQAAACAAAAAwMDAwMDAwMwFtZXJzdWVAZ21haWwuY29tAUdtYWlsAAIBCRABAAAAAxIA
AP8RAADDOAAATFpGdbCTXS4HAAYBAQtgbmcxMDJmNQBkAHJjcA3QDgAyHQxgYw1EATQBMXN0c+Jo
BXBiY2gQNQkAEMA0MzcQRGgOsBDWYmmTAUMNpDMzEvZmZRNz+HRoZQeAEzUAUBSnFD48Y3MN4gH3
AqQSwGRpjwM2AgAQwArAc2V0AtFQcHJxMgAAKgqhblpvGYAgDfAa0TYTgDA4NTA0G1EB0BtANH2/
B20Cgw8gGFYEZBktMRos+jcbMTka0xuiG4AcAAhV8weyAoMzNBhPGV8aaBuC7xtEGyIhASFQYQbQ
ByEF0P5hFKAiFBGgIpYD4yNvGjufATAbohriG4AmBmxpJpH9IhQxG2AYPyifGl8bbxx9/ywyAFAn
ry2vKckmAiq/BRDAIExpZ2h0K+cdaP8yjzOfNK81vywFE6Asnzhv/y6/L88w3yJ/PZ8+rz+/QM9/
RSAOEDdfQy8pzzqPK+c2/0d/SI9Jn0qvK9gnj01vRBneYkTRRUBPZE+DfQcTIhRsODhCD1JkMlXQ
UtQg0QdtIENFVYU5Vg9XFadB4lfPWNN5ciIUOTHouUKcMTYx4Vt/A4JHCdF+a1z1HWheDh1hXz8D
glTvCHBc9TyPXnY3UUFjHwOC2ChIZSaQB9ApXPVB//9mF1efZ7YHEAGgDrBolkdoXV4NOExRau8D
gkIHQHR/DrBc9UxYXg5lAW7/Z+NW2QiQdG4mcAeQZWiURUD3VfgeDVd2MVkAIXhZBkVAn1modg5b
NXd9XNU0MTHo/x4NXuZ3fGCIfFAdb2JOd3z/ZGZ8UGUIgM5mlXd8aCt8UP9pGIRfdx+GcmxKfFBH
aIDO/261d3xwSXxQTFiAz3K0hc3/dE4BwFX/Vw8malkGAcBZr/dav5V8XNU3FVGW/16dlXv/YIia
QGFPYl+Ve2RmmkBtL/9uP5V7cEmaQHEfci+Ve5IvfDc1k1hR7JTaO0SWRjX/ltiqLZhpq8WZ1l7y
rO+brv87RJ1ZYtKwL59eO0ShB3Ki/7OPZkw7Jmgrr9BpGLc+qy6/bDuv0Edvor87JqSaNkxf/6Z/
uLd0Tiwyk1+qn1vPWSX/LEGW363Pxz9c1ixAfGmbD//Kn2AvzJGeH7RvY29kdsyR/2UPt69zP2g7
zJFpH7s/1s//bEvMkaGvvs9vT3BZzJGlb//CP9r/w9/MkamPxi87K8gp3jGsv8n/563MGDKv/83f
++esz+sys1/R3+es0+nGkO/w77e/57vXzjK6L9nv9r2/3A0OAfjPvu/nyuAsMsEv/+Iv9r3kT+zB
5Y/mn+ev7Hb/6T/qT+tfK+aaWe2fCl/vv/+eCfF/Dh/znRZREG/1z/bf/9gZImn5TxW/+28MIvy/
/c///t/gWaVZAU8d3wNvC+bFH/8GD8sPyEddQCR/yg/LH8wn33xQKE/N787/0Ak00M8RX3vS79P4
NNSvFR/jP9fdNO/Y3xkvNh/cDTTdDx0/3y/94Ds04R8hLzpPIy8r4SRv9yV/Kl/IRzQoPylPRv/M
GP/MoEi/LT8uT9AJ7NBMnzE//zJPS+gz/zUPQo/X3SvwVH//OU86X9wcTGBYrz1/Po/gSv41QG9B
f1q/Q59MUQT/Re//q61MQgivSb+u3sTRr+9Nj/+yD2uUEE9Rn7V+a7IUD1V//7i/a3YYH1mvvE9r
dhwvXd+/v99rlCAfYe/DT8RZNmVPf2ZfZ29gwGifaa9qv8TgN/9r/20Pbh+IE29/cI9xn4gx/3Lf
c+90/4fmdo93n3ivh+b/ej97T3xfiAR9z37ff+/EWV9aIppvRhy80KfQbMgpN++FD4YfoEXMGDiI
b4l/oES9z+s4i++M/6BE0+k4j0/3kF+gRNfOOJL/lA+tVdwN/jiWr5e/oETgLJgyso9iHAetVZzr
xJFjb2xvciB0Ymw7XM/wZDA0XGfP8W66ILmwdWXqMLnfZfygNbsKvCG73/+86br0vRK7f79Pvw2+
j7y/9bsPZdCwOMTaxfHFr8a5/7r0xuLFT8kfyN3IX8aPylT+OVCAzaTPAccjzwDE07+F1jlIoM/E
M8CEM7ym0fH/xGPR8MpUSJHK46FBxyPTcA/E372AhpDYQipcZGU9pZFwtjLwwblwpaBcYUncsDcg
1gZwYdahcXuxINcQabogoFC6IKVAZGhjdGzYQHLZQNwQcNnWUWF14EDXYHPYQNmgo6Ww2qJudW3g
sGHaYAR0b9dgZGp1c3Q/oFAa0dkBuoGVMLqBaXSF2FAw17Bcbm9xlLFhW2BvdGUg4KDcYHnqbFrg
aPAQdOCg2J/Zr3/av9vP3N/UsOCg10GlkHP+MWFA13C6INdw1uKVIE1Q+GcxMPyg38HjgOU05NHv
1tTmgxPx5nJmx1Doc9cyOdeBXGj78NdSuiBkYp3qFWPK4GEQ6BNucOhpg+u0YUBzbmV4dOTRfnPe
ILmAW3AH0N7QlMBp67mA3YB53cBO7bK5wNYD3+Vx5NHjMGEg/+B23qDe0Px1bunw1lDjYLoA7gnl
kNJE4VQgUImQYcrg2FBAaCBGb2501fR0b+WATIDz0E0gd+tQ44BmxfPQV2EQdGhCVGDjgLvYQPAA
bOawRND1ZHL12FxmbPVG9LD3R2L3R3I/9UG5sNzwuhH5RN7wcGX99UFz8FC5kP/B88EXMPZgdfsG
bPsVYvsV4OD7JGS+Z/wG/YD9BtdQ+yR22H//4J/hr+K/48/k3+Xv5v/oD3/pH+ov6z/sT9Rw7OEj
oG3+afDB1lBbkPCL7tRi4BtA/98QE3IFUFzA/38AjwGfAq//A78EzQmRBdJMgAY/B0UJke8Hrwi2
Cu8L/WISULoA80DX7VIM4waxc90xa04A8Hz+UBcQ3PBi4O0h7zcd0e/4/xWfFqMXn9bCDTIcRe+y
HXT7HUPXMGsem5UApbHvN9eg3yAfBTcGzBIQuUBmJuIjq73wqUj6MfvwHZHvNzgnD78oHwc1KcFc
wKWg3zBkFzC9CsFoKcDYQO1AMDJiMIFPLLIjqw1/8OVVbk+wc/e5YPBQ8TBNunA/oPNA7zf+OSzf
Le8pKzWBMY8yn/Eh9fMwbLlwd7oAK6+GgDWf/wUuIi/WxCnAPJI4vznH7jhf7hH6sDQQZECxIEVb
cGnsbFPe8oaAMTwXBWI87/89/z8PQB9BL0I/Q03UcDwX/0bxRR9GL0c/SE9JX0pvQz7/0CA8JuzR
TV9Ob09/UI9Rn+9Sr0M+YJA8FzRVb1Z/V4//WJ9Zr1q/W89dgERIF4Fdz/de31/ra8AwtcFg72H/
Yw/HZBTe0G6gcGx57OHe8OuJoLYAMezAN2kQxLBDeu/EwLkS1jCLEHa5od6wM9Aaa94AdzTh1gNw
Z3D/b9Nw8t1wcQHdZRBn+zBy8bxhMG9FbbFv0nPTOLJAvDQ0qyFto8dwCEA5hPHLbap5sW3t0WhQ
EXB285XzMjOuwG2SEGtC3PJJeDVTdXMhbXPvAWz6RpWwY3ihthASYPIRpJCobWxNiZBneINyewfZ
1lFKY3rBEZJJ+YA0kQ3TcDR4oSWgdExpbVN4oUNAcnl94THWA3h9euBuFABxQ38TBWAUUHTgcDov
L3OloDmQHFC6LjmgY95QNBD0sC65UBRtL4GAZpXgZS93+bmAZC+GgAhAgmN64LkQ93Dw2FD6sHfH
YF2AuiCDo/5orpJ4oXsR9cBlIJDghSJv9nCFhn1BhZVi1HB4AWf7E4DekHLdERQQnWARIAeAHxDx
9FARIPvx9LBuYmq/12C6cPAA1zD0gXoAa95w//BQLyCKJO2kmXAXMdZA80DH3oF4MLoAc3lz7aB9
MffUsW0w80B2euAKMYwXFNHcZ2Tt4HNgytFmifFvsPs0kYrBdpUhjsHtIHrgpJCvL9D0UG0gegBl
kOBs9QDf7SLdcBrQuYA5kXi6ALlQ//NQNJFzMvBQJaCQA38RcvF/kOF/Efqw3lCpMKSQ3gB4UxcQ
gEBvebpwXO0gcP8v0LmQldDeABIR+/ASYIoQ9y/wuaF/QGIKUN3xEmGCQN/toSmR7aIv0BPAZQmw
uYD+eony/YCFIiWgmcEvwJgS8yywCjFndpqZmVEUMCWg/2jxmxKcFJvDkNKL4ZsxnaMuapXxFyAa
gHa4YHdr//lxslCfAoCgkBAI0YRBhzD9/pJlE8CgZe2g3oDuEW0w/nRwcCWgmTCJUaH3FFDt0P8T
gBJg3fF/MBRQE8G5oSmA/7jQtPAcQH8wFvGXQvlx1xD/ogCf8REgubD0YaHxuaG5kP/+MX8weEGY
cZkw3gB4QRGQ/3Ei7PHYUBOQGlIloIJAOyD/FvE7MYIgpMA58YyQpMARgfxwcPCgESASQa1wp3d1
Mm/eUN6AdcCC0TLTkO0Qd/+5oW1yEhC2oN4AyuD0UBNy/4IgEjA6sZIheYDe8O2hkCD3FADd8flx
bngx89Cx8KTAz6dxpMBvsN3xY3gSYN2Q/w+B3XD5gJbRO1CxUZXB3gD913Bjf0GkYtdwsUMTgCWg
/fwAaLKzocKAUHEQEWGMIf5jkACjo7mgeFCzcvkApkKDtcKQAHR4Ynhcp6B/GuB1MO0QEjCf8ICx
kqFs/6TxB4CWgYIw3mAwgQeB32DKMNYSd48hZm228EOwfYfRIF2AaQDd4gjA7eB1v8rw9RDeUIBA
oBHdcGztoO/t0J/wpgB/MHVyYvViu5D/3tCIYfExiCXdIu0gxSCJwf/wsPqwmTC+wxHkvdC+s3Uy
8DQ2NzgXUN7QiVPesf9w4X9AiGA0MJChEwGBQBMwv8Mx3ZCnEMOy+XE0kTfVwD/DIRKwFzBxYvNQ
7TBhIP4ucKXDRc8Qw9IuocQ/xU//xl/DkBlwEwDWUJmwyC/JP/3KT2yHgBMAZsDH78y/zcU+Kcas
EBDLj9B/zaViIP4odsHRr8NjaSDPT9Qf1S//1j/DgSGw15LEH9j/2g/SHf/2oNef3S/eP99Pw4Gt
INwv/+HP4t/j5YOR+1Bw8B7TvjX/D+8Q/xIPEx8UL3JD63F+UP1tsTnCEG4gdbAgrxaPX7//GK8Z
vxrPDHN20GasZ+70AL8h4YeAKcByEX9AbaQ5gsE/8oAvoX5Qbat6kL6BWUE8Tkf78AlA7bB1MCwN
egro0iD9JYtAOyKLsSDdr+Agd6BmcK/SIIGA/ETtioBkp8H+sGO8cLEwfcDvbTEloW+hnxEu/SXo
xOmP/+qf66/sv+3P7t91M3TQDJD/muH3P2ePLyTmwfn/+w4Br78CvwPPBN8F7wb/CA84rND+OGUR
CZ/4T/lfDL8Nzw7f/w/vEP8SDxMfFC8IiG32Fk/PF18Yb231Ge8gUgFDu4GxKExMQyCJwShDRHnw
+4GQ/SVK8kApIJ9Rs8AgMNMoSUQhOC1EMC1qcaFgbSoBLZ8QtvAtuHH/4S27ATJqIS2OwiBwkjFz
LFB7NYD9LEV+UG0xATQBIXF2dTQAsLA6/SwnzyhERGcxIDNXKflFYoxw6XBBb/WAADErbyxwMF2Q
LMlppjJ1MC3QaWIuUy3/4cukwC8JQzAxIE2oEIPQD9FgNg8sfpAgbWUteT3yQS2SsaJQHZBrsG4t
72vBAKEuMbNAbTjmI7Ax93OY8jJQYWh3gOlwOto33SyAMiyA9yAsyXB98DjgOHNkcD0EP0j9JSog
3k/+0buQLeM90SC4QAFBvZaQczBXuPBENkSgVGsAf/6wRSeQELEwIDBGT/0lTv+RsQDy/tJGZUUB
jhCO0D3R/3bBIy8kPyVPGqTjYHeg/qH9/qF3HyC6IP7SIAD+EP6wfZ2Sc0wfTS9OP09IIJMg33BR
Ub9Sz1PfbecsG2BWL39XP1hPGo5aD1sfXC9t9mL/H/D+kLogqfBeL18/YE9t53xva1AhqXCYYLEw
HZAu/CBJjSAxEI4R/wA6ILjR14sgUGByMGhQtyCHoIyw/9IQYo9jn2SvJj8nRjF9KRE3IDCv4PIw
dikgkWB0a+5hbscqqm7HQYJA/vAq4r+SUG7HOfluxz/rcEj8hyCFNXFTuND2bnfkqlHKcm7HSwCh
IFeO0K8R327HNUlxmJ9gAOBCnxCLYf9MD2p/a48ZX10fev8Kr/NU/5xx13AL/GzPGp8brxy/Hc//
Ht8f7yD/7717D3wffS9+P50nRkP+4JSw/QdNZUBw/7iAf8+N747/kA+EZfAmhWYEfQCZIAADAN4/
6f0AAAMA8T8HBAAAHgD6PwEAAAAGAAAAR21haWwAAAADAAlZAwAAAAMALoAIIAYAAAAAAMAAAAAA
AABGAAAAABCFAAAAAAAAAwBEgAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAHqACCAGAAAA
AADAAAAAAAAARgAAAAAGhQAAAAAAAAsAfIAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAAAwB9
gAggBgAAAAAAwAAAAAAAAEYAAAAAGIUAAAAAAAALAH6ACCAGAAAAAADAAAAAAAAARgAAAACChQAA
AAAAAB4Af4AIIAYAAAAAAMAAAAAAAABGAAAAANiFAAABAAAACQAAAElQTS5Ob3RlAAAAAAMAgIAI
IAYAAAAAAMAAAAAAAABGAAAAAOuFAAAHBAAACwAfDgEAAAACAfgPAQAAABAAAAAjs4acT/h2RboE
mno8EeQFAgH6DwEAAAAQAAAAxp4WthXtX0ya8Jco+GahmgMA/g8FAAAAAwANNP0/rQ4DAA80/T+t
DgIBFDQBAAAAEAAAAOkv63WWUESGg7h95SKqSUgCAeJlAQAAABQAAACEhcWYlzI7TJ1kInrBZjPL
AAyd0AIB42UBAAAAFQAAABSEhcWYlzI7TJ1kInrBZjPLAAyd0AAAAAIBfwABAAAAjQAAADAwMDAw
MDAwQzY5RTE2QjYxNUVENUY0QzlBRjA5NzI4Rjg2NkExOUEwNzAwQzNCNjhFMTBGNzc1MTFDRUI0
Q0QwMEFBMDBCQkI2RTYwMDAwMDAwMDAwMEQwMDAwNUY3RkQ0OTI5QkQxRTI0RDg5MDE5MTVEQzc1
N0VEMDUwMDAwMDAwMDg4NUQwMDAwAAAAAAMABhCL65eTAwAHEIACAAADABAQAAAAAAMAERAAAAAA
HgAIEAEAAABlAAAAREVBUllBTkdET0NUT1JTLEZPTExPV0lOR0lTVEhFTElTVE9GWUFOR01PRFVM
RVNDVVJSRU5UTFlJTlJFVklFV1JFVklFV0VSTENFTkREUkFGVEpBTkxJTkRCTEFEMjAxOC0wMQAA
AAC/mQ==

------=_NextPart_000_0167_01D388BD.CC429B30--


From nobody Mon Jan  8 11:29:08 2018
Return-Path: <acee@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 789F6124B18; Mon,  8 Jan 2018 11:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 hsQUcD4lwwsu; Mon,  8 Jan 2018 11:28:55 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 876CC12025C; Mon,  8 Jan 2018 11:28:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4348; q=dns/txt; s=iport; t=1515439735; x=1516649335; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=g/F43hSPIRkjFdMBYB1ANSNg5yCjUnK5+ymCJux/qB8=; b=m32tFCh395t0br7rk/cZI1KcrguuaG9CdQUhTGU70Cgco8LXwtuAbPL9 6Pxh9b2Qwm4HF2Z2s94/HdSGl9ST2NCJuB5wDv9B3tHU1RbEg3wN7rnWN fhRduPbJo4+iNTRa1aY/ugeK7znTSBeRzffIOXe/dd//XLnaq9FdNeOcw I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DrAwD+xVNa/4oNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM/gVonB4QAmH2ZLIIVCoU7AhqEHEEWAQEBAQEBAQEBayiFJAY?= =?us-ascii?q?jEUUQAgEIEggCJgICAjAVAg4CBAENBYoxryiCJ4o0AQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBHYEPgxGCFYM/gy6DMIFugxeCRSAFo14ClTyUCYdfjwsCERkBgTsBJgM?= =?us-ascii?q?vP4ERbxUZgk6EV3iJWIEXAQEB?=
X-IronPort-AV: E=Sophos;i="5.46,332,1511827200"; d="scan'208";a="53858357"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2018 19:28:54 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w08JSsBt016790 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Jan 2018 19:28:54 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 8 Jan 2018 14:28:53 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Mon, 8 Jan 2018 14:28:53 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "draft-ietf-ospf-yang.all@ietf.org" <draft-ietf-ospf-yang.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: Yangdoctors last call review of draft-ietf-ospf-yang-09
Thread-Index: AQHTboUcIbs87wVZj0yzoeuFibmmLKNqkMSA
Date: Mon, 8 Jan 2018 19:28:53 +0000
Message-ID: <D6792F3D.E8CD1%acee@cisco.com>
References: <151255960762.30655.17225294251460480729@ietfa.amsl.com>
In-Reply-To: <151255960762.30655.17225294251460480729@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <DC8D5954D55D6C449A602C6BBE04AC5D@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/KdnrqhYClT-fySpnA1ff2Opp4ws>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 19:28:57 -0000

SGkgTGFkYSwNCg0KQXBvbG9naWVzIGZvciB0aGUgZGVsYXkuIFdlIHNvbWV3aGF0IGdvdCBodW5n
IHVwIG9uIDQgYW5kIDYuIFNlZSBpbmxpbmUuDQoNCk9uIDEyLzYvMTcsIDY6MjYgQU0sICJMYWRp
c2xhdiBMaG90a2EiIDxsaG90a2FAbmljLmN6PiB3cm90ZToNCg0KPlJldmlld2VyOiBMYWRpc2xh
diBMaG90a2ENCj5SZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPg0KPlRoZSBkYXRh
IG1vZGVsIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCBpcyBhIG1hc3NpdmUgcGllY2Ugb2Ygd29y
azogaXQNCj5jb25zaXN0cyBvZiAxMSBZQU5HIG1vZHVsZXMgYW5kIGRlZmluZXMgYXJvdW5kIDEy
MDAgc2NoZW1hIG5vZGVzLiBUaGUNCj4iaWV0Zi1vc3BmQDIwMTctMTAtMzAiIG1vZHVsZSBpcyBj
b21wYXRpYmxlIHdpdGggdGhlIE5NREEgYXJjaGl0ZWN0dXJlLg0KPg0KPioqKiogQ29tbWVudHMN
Cj4NCj4xLiBVbmxlc3MgdGhlcmUgaXMgYSByZWFsbHkgY29tcGVsbGluZyByZWFzb24gbm90IHRv
IGRvIHNvLCB0aGUNCj4gICAiaWV0Zi1vc3BmIiBzaG91bGQgZGVjbGFyZSBZQU5HIHZlcnNpb24g
MS4xLiBGb3Igb25lLA0KPiAgICJpZXRmLXJvdXRpbmciIHRoYXQgaXMgYmVpbmcgYXVnbWVudGVk
IGJ5ICJpZXRmLW9zcGYiIGFscmVhZHkNCj4gICBkZWNsYXJlcyB0aGlzIHZlcnNpb24uIFNvbWUg
b2YgbXkgc3VnZ2VzdGlvbnMgYmVsb3cgYWxzbyBhc3N1bWUNCj4gICB2ZXJzaW9uIDEuMS4NCg0K
V2Ugd2lsbCBhZGQgdGhpcy4gDQoNCg0KPg0KPjIuIFRoZSAiaWV0Zi1vc3BmIiBjYW4gd29yayBv
bmx5IHdpdGggdGhlIG5ldyBOTURBLWNvbXBhdGlibGUNCj4gICByZXZpc2lvbnMgb2Ygc29tZSBt
b2R1bGVzLCBzdWNoIGFzICJpZXRmLWludGVyZmFjZXMiIGFuZA0KPiAgICJpZXRmLXJvdXRpbmci
LiBJIHVuZGVyc3RhbmQgaXQgaXMgbm90IGRlc2lyYWJsZSB0byBpbXBvcnQgc3VjaA0KPiAgIG1v
ZHVsZXMgYnkgcmV2aXNpb24sIGJ1dCBhdCBsZWFzdCBpdCBzaG91bGQgYmUgbWVudGlvbmVkIGlu
IGENCj4gICBkZXNjcmlwdGlvbiBhdHRhY2hlZCB0byBldmVyeSBzdWNoIGltcG9ydC4NCg0KV2Ug
d2lsbCBhZGQgY29tbWVudHMgdG8gdGhlIGRlc2NyaXB0aW9uLg0KPg0KPjMuIE1heWJlIHRoZSBk
cmFmdCBjb3VsZCBtZW50aW9uIHRoYXQgaW1wbGVtZW50YXRpb25zIHNob3VsZCBzdXBwbHkgYQ0K
PiAgIGRlZmF1bHQgcm91dGluZyBkb21haW4gYXMgYSBzeXN0ZW0tY29udHJvbGxlZCByZXNvdXJj
ZS4NCg0KSXNu4oCZdCB0aGlzIG1vcmUgb2YgYW4gUkZDODAyMkJJUyBzdGF0ZW1lbnQ/IEkgZ3Vl
c3Mgd2UgY291bGQgc3RhdGUgdGhpcyBhcw0KYW4gYXNzdW1wdGlvbi4gDQo+DQo+NC4gSW4gIndo
ZW4iIGV4cHJlc3Npb25zLCB0aGUgbW9kdWxlIHVzZXMgbGl0ZXJhbCBzdHJpbmdzIGZvcg0KPiAg
IGlkZW50aXRpZXMuIFRoaXMgaXMga25vd24gdG8gYmUgcHJvYmxlbWF0aWMsIHRoZSBYUGF0aCBm
dW5jdGlvbnMNCj4gICBkZXJpdmVkLWZyb20oKSBvciBkZXJpdmVkLWZyb20tb3Itc2VsZigpIHNo
b3VsZCBiZSB1c2VkIGluc3RlYWQuDQoNCldoeSBpcyB0aGlzIHByb2JsZW1hdGljPyBJcyBpdCBi
ZWNhdXNlIHRoZSB0eXBlcyBjYW4gYmUgZXh0ZW5kZWQ/DQoNCj4NCj41LiBTb21lIGVudW1lcmF0
aW9ucywgc3VjaCBhcyAicGFja2V0LXR5cGUiIGFuZCAiaWYtc3RhdGUtdHlwZSINCj4gICBkZWZp
bmUgZW51bSBpZGVudGlmaWVycyB3aXRoIHVwcGVyY2FzZSBsZXR0ZXJzIGFuZC9vciB1bmRlcnNj
b3JlcywNCj4gICBmb3IgZXhhbXBsZSAiRGF0YWJhc2UtRGVzY3JpcHRpb24iIG9yICJMT05HX1dB
SVQiLiBSRkM2MDg3YmlzDQo+ICAgcmVjb21tZW5kcyB0aGF0IG9ubHkgbG93ZXJjYXNlIGxldHRl
cnMsIG51bWJlcnMgYW5kIGRhc2hlcy4gSSB0aGluaw0KPiAgIHRoaXMgY29udmVudGlvbiBzaG91
bGQgYmUgb2JzZXJ2ZWQgZGVzcGl0ZSB0aGUgZmFjdCB0aGF0IHRoZQ0KPiAgIGN1cnJlbnQgbmFt
ZXMgYXJlIHRyYWRpdGlvbmFsbHkgdXNlZCBpbiBPU1BGIHNwZWNzLiBUaGUNCj4gICAiaWV0Zi1y
b3V0aW5nIiBtb2R1bGUgYWxzbyBkZWZpbmVzICJyb3V0ZXItaWQiIGV2ZW4gdGhvdWdoIHRoZQ0K
PiAgIGRvY3VtZW50cyB1c2UgIlJvdXRlciBJRCIuDQoNCkkgYWdyZWUgLSB3ZSB3aWxsIGZvbGxv
dyB0aGUgUkZDIDYwODdCSVMgZ3VpZGVsaW5lcy4NCg0KDQo+DQo+Ni4gVGhlIHR5cGVzIG9mIExT
QSBoZWFkZXJzIGFyZSBtb2RlbGxlZCBhcyBpbnRlZ2Vycy4gV2hpbGUgT1NQRiBndXJ1cw0KPiAg
IHByb2JhYmx5IGtub3cgdGhlc2UgbnVtYmVycyBieSBoZWFydCwgaXQgaXMgbm90IHZlcnkNCj4g
ICByZWFkZXItZnJpZW5seS4gU28gYXQgbGVhc3Qgc29tZSByZWZlcmVuY2VzIHRvIGRvY3VtZW50
cyBkZWZpbmluZw0KPiAgIHRoZXNlIG51bWJlcnMgc2hvdWxkIGJlIHByb3ZpZGVkLCBidXQgbXkg
c3VnZ2VzdGlvbiBpcyB0byBjb25zaWRlcg0KPiAgIGltcGxlbWVudGluZyB0aGVtIHdpdGggaWRl
bnRpdGllcy4gSXQgc2VlbXMgaXQgbWlnaHQgYWxzbyBiZSB1c2VmdWwNCj4gICB0byBkZWZpbmUg
c29tZSAiYWJzdHJhY3QiIGlkZW50aXRpZXMgZm9yIHRoZXNlIHR5cGVzLiBGb3IgZXhhbXBsZSwN
Cj4gICBpZiAib3BhcXVlLWxzYSIgaXMgZGVmaW5lZCwgdGhlbiB0aGUgZGVmaW5pdGlvbiBvZiBj
b250YWluZXINCj4gICAib3BhcXVlIiBjb3VsZCBzaW1wbHkgdXNlDQo+DQo+ICAgICB3aGVuICJk
ZXJpdmVkLWZyb20oLi4vLi4vaGVhZGVyL3R5cGUsICdvc3BmOm9wYXF1ZS1sc2EnKSI7DQo+DQo+
ICAgaW5zdGVhZCBvZg0KPg0KPiAgICAgIHdoZW4gIi4uLy4uL2hlYWRlci90eXBlID0gOSBvciAi
DQo+ICAgICAgICAgICAgICArICIuLi8uLi9oZWFkZXIvdHlwZSA9IDEwIG9yICINCj4gICAgICAg
ICAgICAgICsgIi4uLy4uL2hlYWRlci90eXBlID0gMTEiOw0KDQpJIGd1ZXNzIEkgZG9u4oCZdCBz
ZWUgdGhlIGlkZW50aXRpZXMgYXMgYWx3YXlzIGJlaW5nIGJldHRlci4gV2Ugd2lsbA0KY29uc2lk
ZXIgdGhpcyBvbmUuIA0KDQoNCj4NCj43LiBUaGUgdGl0bGUgb2Ygc2VjLiAyLjkgc2hvdWxkIGJl
ICJPU1BGIE5vdGlmaWNhdGlvbnMiIHJhdGhlciB0aGFuDQo+ICAgIk9TUEYgbm90aWZpY2F0aW9u
Ii4NCg0KU3VyZS4gDQoNClRoYW5rcywNCkFjZWUgDQo+DQo+DQoNCg==


From nobody Mon Jan  8 11:34:31 2018
Return-Path: <acee@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA66124B18; Mon,  8 Jan 2018 11:34:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 2TsBt5nfSASH; Mon,  8 Jan 2018 11:34:26 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8EAE12426E; Mon,  8 Jan 2018 11:34:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6348; q=dns/txt; s=iport; t=1515440066; x=1516649666; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=FX0fsNKz8etBTIQsrrFde8OW/Pyoapfq+ofazDQPe1M=; b=fA77LiWVA1LxzcfyaxW31EGzLbc02atmWBtpp6hnhRdMl9DL8oGLUr/F KNvrEe6fTCJhVDQXYdXDF8gaqwHgfWRJIlLVZRuKDib2LLEv8BXaw9Jf/ tBM91Njn2ZdnqqE1P9a4Ew+F9f5+1wWCsl4UJQZFVFkxlgjK/l5kJP65f 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DxAwBDxlNa/5pdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM/ZnQnB4QAmH2CApk/ChgLhRgCGoQcQxQBAQEBAQEBAQFrKIU?= =?us-ascii?q?kAQEBAwEBIRE6CxACAQgSBgICJgICAiULFQIOAgQBDQWKMRCvGIInijQBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEYBYEPgxGCFYM/gy6DLwGBboMXgkUgBaNeApU8lAm?= =?us-ascii?q?HX48LAhEZAYE7ATYiP4ERbxUZJIIqhFd4iViBFwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,332,1511827200"; d="scan'208";a="340468022"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2018 19:34:24 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w08JYOYD002745 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 8 Jan 2018 19:34:24 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 8 Jan 2018 14:34:23 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Mon, 8 Jan 2018 14:34:23 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ladislav Lhotka <lhotka@nic.cz>, Martin Bjorklund <mbj@tail-f.com>
CC: "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-ospf-yang.all@ietf.org" <draft-ietf-ospf-yang.all@ietf.org>
Thread-Topic: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
Thread-Index: AQHTboUcIbs87wVZj0yzoeuFibmmLKM2hmeAgAALVgCANACPAA==
Date: Mon, 8 Jan 2018 19:34:23 +0000
Message-ID: <D67931B0.E8CE1%acee@cisco.com>
References: <151255960762.30655.17225294251460480729@ietfa.amsl.com> <20171206.124611.1073986528289329597.mbj@tail-f.com> <1512563206.2653.32.camel@nic.cz>
In-Reply-To: <1512563206.2653.32.camel@nic.cz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6B7A81479B12A74C964C07F225A0A3E0@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/YVyW1almBuzgTGiDb10ZNNIzmYM>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 19:34:28 -0000

SGkgTWFydGluLCANCg0KV2Ugd2lsbCBpbmNvcnBvcmF0ZSB0aGVzZSBjb21tZW50cyBhcyB3ZWxs
LiBJIGFncmVlIHdlIGNvdWxkIHRha2UgYW5vdGhlcg0KcGFzcyBhdCB0aGUgZGVzY3JpcHRpb25z
Lg0KDQpUaGFua3MsDQpBY2VlIA0KDQpPbiAxMi82LzE3LCA3OjI2IEFNLCAiTGFkaXNsYXYgTGhv
dGthIiA8bGhvdGthQG5pYy5jej4gd3JvdGU6DQoNCj5PbiBXZWQsIDIwMTctMTItMDYgYXQgMTI6
NDYgKzAxMDAsIE1hcnRpbiBCam9ya2x1bmQgd3JvdGU6DQo+PiBMYWRpc2xhdiBMaG90a2EgPGxo
b3RrYUBuaWMuY3o+IHdyb3RlOg0KPj4gPiBSZXZpZXdlcjogTGFkaXNsYXYgTGhvdGthDQo+PiA+
IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggSXNzdWVzDQo+PiA+IA0KPj4gPiBUaGUgZGF0YSBt
b2RlbCBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQgaXMgYSBtYXNzaXZlIHBpZWNlIG9mIHdvcms6
IGl0DQo+PiA+IGNvbnNpc3RzIG9mIDExIFlBTkcgbW9kdWxlcyBhbmQgZGVmaW5lcyBhcm91bmQg
MTIwMCBzY2hlbWEgbm9kZXMuIFRoZQ0KPj4gDQo+PiAxMSBZQU5HIG1vZHVsZXM/ICBJc24ndCB0
aGVyZSBqdXN0IG9uZT8NCj4NCj5ZZXMsIGJ1dCBJIG1lYW50IHRoZSBjb21wbGV0ZSBkYXRhIG1v
ZGVsIGluY2x1ZGluZyB0aGUgZXhpc3RpbmcgbW9kdWxlcw0KPnRoYXQNCj5tdXN0IGJlIGltcGxl
bWVudGVkIGFsb25nIHdpdGggImlldGYtb3NwZiIsIHN1Y2ggYXMgImlldGYtaW50ZXJmYWNlIiwN
Cj4iaWV0Zi0NCj5yb3V0aW5nIiBhbmQgImlldGYta2V5Y2hhaW4iLiBJIHRoaW5rIGl0IGlzIGEg
aGlnaGVyIGxlYWd1ZSBvZiBkYXRhDQo+bW9kZWxsaW5nDQo+Y29tcGFyZWQgdG8gYSBzdGFuZC1h
bG9uZSBtb2R1bGUgLSBrdWRvcyB0byB0aGUgYXV0aG9ycy4NCj4NCj4+IA0KPj4gDQo+PiANCj4+
IEkgd291bGQgbGlrZSB0byBhZGQgdHdvIHF1aWNrIGNvbW1lbnRzIHRvIExhZGEncyByZXZpZXcu
DQo+PiANCj4+IG8gIFJlbW92ZSBhbGwgInJldmlzaW9uIiBzdGF0ZW1lbnRzIGV4Y2VwdCB0aGUg
b25lIHRoYXQgc2F5cyAiaW5pdGlhbA0KPj4gICAgcmV2aXNpb24iLiAgIFRoZSBpZGVhIGlzIHRv
IGhhdmUgb25lIHJldmlzaW9uIHN0YXRlbWVudCBwZXINCj4+ICAgIHB1Ymxpc2hlZCB2ZXJzaW9u
IChpLmUuLCBSRkMpLg0KPg0KPlJpZ2h0LCB0aGUgcmV2aXNpb25zIG1ha2UgdGhlIG1vZHVsZSBl
eGNlc3NpdmVseSBsb25nLg0KPg0KPj4gDQo+PiANCj4+IG8gIE1hbnkgb2YgdGhlIG5vZGVzIGhh
dmUgcXVpdGUgcnVkaW1lbnRhcnkgZGVzY3JpcHRpb25zLCBhbmQgdGhlDQo+PiAgICAicmVmZXJl
bmNlIiBzdGF0ZW1lbnQgaXMgcmFyZWx5IHVzZWQuICBGb3IgZXhhbXBsZToNCj4+IA0KPj4gICAg
ICAgICAgbGVhZiBsc2EtaWQgew0KPj4gICAgICAgICAgICB0eXBlIHlhbmc6ZG90dGVkLXF1YWQ7
DQo+PiAgICAgICAgICAgIG1hbmRhdG9yeSB0cnVlOw0KPj4gICAgICAgICAgICBkZXNjcmlwdGlv
biAiTFNBIElELiI7DQo+PiAgICAgICAgICB9DQo+PiANCj4+ICAgIEl0IHNlZW1zIGFzIHRoZSBk
ZXNjcmlwdGlvbiBpcyBwdXQgdGhlcmUganVzdCB0byBrZWVwIHRoZSB0b29scw0KPj4gICAgcXVp
ZXQuICBJIGtub3cgdGhhdCBpdCBpcyBwYWluZnVsIHRvIHdyaXRlIGdvb2QgZGVzY3JpcHRpb25z
LCBidXQNCj4+ICAgIGl0IGRvZXMgaGVscCB0aGUgY29uc3VtZXIgb2YgdGhlIGRhdGEgbW9kZWwu
DQo+DQo+QWdyZWVkLg0KPg0KPlRoYW5rcywgTGFkYQ0KPg0KPj4gDQo+PiANCj4+IC9tYXJ0aW4N
Cj4+IA0KPj4gDQo+PiA+ICJpZXRmLW9zcGZAMjAxNy0xMC0zMCIgbW9kdWxlIGlzIGNvbXBhdGli
bGUgd2l0aCB0aGUgTk1EQQ0KPj5hcmNoaXRlY3R1cmUuDQo+PiA+IA0KPj4gPiAqKioqIENvbW1l
bnRzDQo+PiA+IA0KPj4gPiAxLiBVbmxlc3MgdGhlcmUgaXMgYSByZWFsbHkgY29tcGVsbGluZyBy
ZWFzb24gbm90IHRvIGRvIHNvLCB0aGUNCj4+ID4gICAgImlldGYtb3NwZiIgc2hvdWxkIGRlY2xh
cmUgWUFORyB2ZXJzaW9uIDEuMS4gRm9yIG9uZSwNCj4+ID4gICAgImlldGYtcm91dGluZyIgdGhh
dCBpcyBiZWluZyBhdWdtZW50ZWQgYnkgImlldGYtb3NwZiIgYWxyZWFkeQ0KPj4gPiAgICBkZWNs
YXJlcyB0aGlzIHZlcnNpb24uIFNvbWUgb2YgbXkgc3VnZ2VzdGlvbnMgYmVsb3cgYWxzbyBhc3N1
bWUNCj4+ID4gICAgdmVyc2lvbiAxLjEuDQo+PiA+IA0KPj4gPiAyLiBUaGUgImlldGYtb3NwZiIg
Y2FuIHdvcmsgb25seSB3aXRoIHRoZSBuZXcgTk1EQS1jb21wYXRpYmxlDQo+PiA+ICAgIHJldmlz
aW9ucyBvZiBzb21lIG1vZHVsZXMsIHN1Y2ggYXMgImlldGYtaW50ZXJmYWNlcyIgYW5kDQo+PiA+
ICAgICJpZXRmLXJvdXRpbmciLiBJIHVuZGVyc3RhbmQgaXQgaXMgbm90IGRlc2lyYWJsZSB0byBp
bXBvcnQgc3VjaA0KPj4gPiAgICBtb2R1bGVzIGJ5IHJldmlzaW9uLCBidXQgYXQgbGVhc3QgaXQg
c2hvdWxkIGJlIG1lbnRpb25lZCBpbiBhDQo+PiA+ICAgIGRlc2NyaXB0aW9uIGF0dGFjaGVkIHRv
IGV2ZXJ5IHN1Y2ggaW1wb3J0Lg0KPj4gPiANCj4+ID4gMy4gTWF5YmUgdGhlIGRyYWZ0IGNvdWxk
IG1lbnRpb24gdGhhdCBpbXBsZW1lbnRhdGlvbnMgc2hvdWxkIHN1cHBseSBhDQo+PiA+ICAgIGRl
ZmF1bHQgcm91dGluZyBkb21haW4gYXMgYSBzeXN0ZW0tY29udHJvbGxlZCByZXNvdXJjZS4NCj4+
ID4gDQo+PiA+IDQuIEluICJ3aGVuIiBleHByZXNzaW9ucywgdGhlIG1vZHVsZSB1c2VzIGxpdGVy
YWwgc3RyaW5ncyBmb3INCj4+ID4gICAgaWRlbnRpdGllcy4gVGhpcyBpcyBrbm93biB0byBiZSBw
cm9ibGVtYXRpYywgdGhlIFhQYXRoIGZ1bmN0aW9ucw0KPj4gPiAgICBkZXJpdmVkLWZyb20oKSBv
ciBkZXJpdmVkLWZyb20tb3Itc2VsZigpIHNob3VsZCBiZSB1c2VkIGluc3RlYWQuDQo+PiA+IA0K
Pj4gPiA1LiBTb21lIGVudW1lcmF0aW9ucywgc3VjaCBhcyAicGFja2V0LXR5cGUiIGFuZCAiaWYt
c3RhdGUtdHlwZSINCj4+ID4gICAgZGVmaW5lIGVudW0gaWRlbnRpZmllcnMgd2l0aCB1cHBlcmNh
c2UgbGV0dGVycyBhbmQvb3IgdW5kZXJzY29yZXMsDQo+PiA+ICAgIGZvciBleGFtcGxlICJEYXRh
YmFzZS1EZXNjcmlwdGlvbiIgb3IgIkxPTkdfV0FJVCIuIFJGQzYwODdiaXMNCj4+ID4gICAgcmVj
b21tZW5kcyB0aGF0IG9ubHkgbG93ZXJjYXNlIGxldHRlcnMsIG51bWJlcnMgYW5kIGRhc2hlcy4g
SSB0aGluaw0KPj4gPiAgICB0aGlzIGNvbnZlbnRpb24gc2hvdWxkIGJlIG9ic2VydmVkIGRlc3Bp
dGUgdGhlIGZhY3QgdGhhdCB0aGUNCj4+ID4gICAgY3VycmVudCBuYW1lcyBhcmUgdHJhZGl0aW9u
YWxseSB1c2VkIGluIE9TUEYgc3BlY3MuIFRoZQ0KPj4gPiAgICAiaWV0Zi1yb3V0aW5nIiBtb2R1
bGUgYWxzbyBkZWZpbmVzICJyb3V0ZXItaWQiIGV2ZW4gdGhvdWdoIHRoZQ0KPj4gPiAgICBkb2N1
bWVudHMgdXNlICJSb3V0ZXIgSUQiLg0KPj4gPiANCj4+ID4gNi4gVGhlIHR5cGVzIG9mIExTQSBo
ZWFkZXJzIGFyZSBtb2RlbGxlZCBhcyBpbnRlZ2Vycy4gV2hpbGUgT1NQRiBndXJ1cw0KPj4gPiAg
ICBwcm9iYWJseSBrbm93IHRoZXNlIG51bWJlcnMgYnkgaGVhcnQsIGl0IGlzIG5vdCB2ZXJ5DQo+
PiA+ICAgIHJlYWRlci1mcmllbmx5LiBTbyBhdCBsZWFzdCBzb21lIHJlZmVyZW5jZXMgdG8gZG9j
dW1lbnRzIGRlZmluaW5nDQo+PiA+ICAgIHRoZXNlIG51bWJlcnMgc2hvdWxkIGJlIHByb3ZpZGVk
LCBidXQgbXkgc3VnZ2VzdGlvbiBpcyB0byBjb25zaWRlcg0KPj4gPiAgICBpbXBsZW1lbnRpbmcg
dGhlbSB3aXRoIGlkZW50aXRpZXMuIEl0IHNlZW1zIGl0IG1pZ2h0IGFsc28gYmUgdXNlZnVsDQo+
PiA+ICAgIHRvIGRlZmluZSBzb21lICJhYnN0cmFjdCIgaWRlbnRpdGllcyBmb3IgdGhlc2UgdHlw
ZXMuIEZvciBleGFtcGxlLA0KPj4gPiAgICBpZiAib3BhcXVlLWxzYSIgaXMgZGVmaW5lZCwgdGhl
biB0aGUgZGVmaW5pdGlvbiBvZiBjb250YWluZXINCj4+ID4gICAgIm9wYXF1ZSIgY291bGQgc2lt
cGx5IHVzZQ0KPj4gPiANCj4+ID4gICAgICB3aGVuICJkZXJpdmVkLWZyb20oLi4vLi4vaGVhZGVy
L3R5cGUsICdvc3BmOm9wYXF1ZS1sc2EnKSI7DQo+PiA+IA0KPj4gPiAgICBpbnN0ZWFkIG9mDQo+
PiA+IA0KPj4gPiAgICAgICB3aGVuICIuLi8uLi9oZWFkZXIvdHlwZSA9IDkgb3IgIg0KPj4gPiAg
ICAgICAgICAgICAgICsgIi4uLy4uL2hlYWRlci90eXBlID0gMTAgb3IgIg0KPj4gPiAgICAgICAg
ICAgICAgICsgIi4uLy4uL2hlYWRlci90eXBlID0gMTEiOw0KPj4gPiANCj4+ID4gNy4gVGhlIHRp
dGxlIG9mIHNlYy4gMi45IHNob3VsZCBiZSAiT1NQRiBOb3RpZmljYXRpb25zIiByYXRoZXIgdGhh
bg0KPj4gPiAgICAiT1NQRiBub3RpZmljYXRpb24iLg0KPj4gPiANCj4+ID4gDQo+PiA+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiA+IHlhbmctZG9j
dG9ycyBtYWlsaW5nIGxpc3QNCj4+ID4geWFuZy1kb2N0b3JzQGlldGYub3JnDQo+PiA+IGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8veWFuZy1kb2N0b3JzDQo+PiA+IA0KPi0t
IA0KPkxhZGlzbGF2IExob3RrYQ0KPkhlYWQsIENaLk5JQyBMYWJzDQo+UEdQIEtleSBJRDogMHhC
OEY5MkIwOEE5Rjc2QzY3DQoNCg==


From nobody Mon Jan  8 23:51:47 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2703E126C0F; Mon,  8 Jan 2018 23:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 kA0u_-GV1Y8b; Mon,  8 Jan 2018 23:51:39 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 B2F0A126B7F; Mon,  8 Jan 2018 23:51:39 -0800 (PST)
Received: from birdie (cst-prg-29-195.cust.vodafone.cz [46.135.29.195]) by mail.nic.cz (Postfix) with ESMTPSA id CFDA563A36; Tue,  9 Jan 2018 08:51:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1515484297; bh=gyFFYFbfilhKcWADNPrRmC52Ybx9yxsj71hhSfcvPPs=; h=From:To:Date; b=QeHshiUTt+PAxuH8ooibzfOiEPcowO2BppHW3gQ+wB1nGfuxdSd147fvz8reZlCxe 7WDwoOs/1ahXAOdoE5Of+CtLv64yM1pjAqO28/pQ+XuayvO83LOn6UchQcwoVzvgfn LPq8p1/ZcDQOf8YIVQB3gxOz3atjugsKdHkWzumM=
Message-ID: <1515484295.18448.9.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: "Acee Lindem (acee)" <acee@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Cc: "draft-ietf-ospf-yang.all@ietf.org" <draft-ietf-ospf-yang.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Date: Tue, 09 Jan 2018 08:51:35 +0100
In-Reply-To: <D6792F3D.E8CD1%acee@cisco.com>
References: <151255960762.30655.17225294251460480729@ietfa.amsl.com> <D6792F3D.E8CD1%acee@cisco.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/HKJolr7uBKEx9NqNZ63ePi3iMx8>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 07:51:42 -0000

Hi Acee,

please see inline.

On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> Hi Lada,
> 
> Apologies for the delay. We somewhat got hung up on 4 and 6. See inline.
> 
> On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> 
> > Reviewer: Ladislav Lhotka
> > Review result: Ready with Issues

...

> > 
> > 3. Maybe the draft could mention that implementations should supply a
> >   default routing domain as a system-controlled resource.
> 
> Isnâ€™t this more of an RFC8022BIS statement? I guess we could state this as
> an assumption.

Probably, but it is not a YANG issue, so I'd leave it to you routing folks to
decide.

>  
> 
> > 4. In "when" expressions, the module uses literal strings for
> >   identities. This is known to be problematic, the XPath functions
> >   derived-from() or derived-from-or-self() should be used instead.
> 
> Why is this problematic? Is it because the types can be extended?

That's one reason: derived identities should often also satisfy the constraint.

But the more serious problem is that things like

    when "../../../../../../../rt:type = 'ospf:ospfv3'"

rely on plain string comparison that depends od the actual prefix used for the
"rt:type" value. For one, according to RFC 7951 the JSON encoding of this value
would be "ietf-ospf:ospfv3" so the above expression is always false. 

> > 
> > 6. The types of LSA headers are modelled as integers. While OSPF gurus
> >   probably know these numbers by heart, it is not very
> >   reader-frienly. So at least some references to documents defining
> >   these numbers should be provided, but my suggestion is to consider
> >   implementing them with identities. It seems it might also be useful
> >   to define some "abstract" identities for these types. For example,
> >   if "opaque-lsa" is defined, then the definition of container
> >   "opaque" could simply use
> > 
> >     when "derived-from(../../header/type, 'ospf:opaque-lsa')";
> > 
> >   instead of
> > 
> >      when "../../header/type = 9 or "
> >              + "../../header/type = 10 or "
> >              + "../../header/type = 11";
> 
> I guess I donâ€™t see the identities as always being better. We will
> consider this one.

In what situations could the numbers be better?

...

Thanks, Lada

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Tue Jan  9 00:08:43 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A604126B7F; Tue,  9 Jan 2018 00:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 uOtn1UGnzIoB; Tue,  9 Jan 2018 00:08:32 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id EB737124E15; Tue,  9 Jan 2018 00:08:31 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 7BC521AE0144; Tue,  9 Jan 2018 09:08:30 +0100 (CET)
Date: Tue, 09 Jan 2018 09:06:48 +0100 (CET)
Message-Id: <20180109.090648.1082913423972100343.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: acee@cisco.com, yang-doctors@ietf.org, draft-ietf-ospf-yang.all@ietf.org, ietf@ietf.org, ospf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1515484295.18448.9.camel@nic.cz>
References: <151255960762.30655.17225294251460480729@ietfa.amsl.com> <D6792F3D.E8CD1%acee@cisco.com> <1515484295.18448.9.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/mnlxDxXrYzkSpiNO_2E6JjhzORs>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 08:08:34 -0000

SGksDQoNCkxhZGlzbGF2IExob3RrYSA8bGhvdGthQG5pYy5jej4gd3JvdGU6DQo+IEhpIEFjZWUs
DQo+IA0KPiBwbGVhc2Ugc2VlIGlubGluZS4NCj4gDQo+IE9uIE1vbiwgMjAxOC0wMS0wOCBhdCAx
OToyOCArMDAwMCwgQWNlZSBMaW5kZW0gKGFjZWUpIHdyb3RlOg0KPiA+IEhpIExhZGEsDQo+ID4g
DQo+ID4gQXBvbG9naWVzIGZvciB0aGUgZGVsYXkuIFdlIHNvbWV3aGF0IGdvdCBodW5nIHVwIG9u
IDQgYW5kIDYuIFNlZSBpbmxpbmUuDQo+ID4gDQo+ID4gT24gMTIvNi8xNywgNjoyNiBBTSwgIkxh
ZGlzbGF2IExob3RrYSIgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KPiA+IA0KPiA+ID4gUmV2aWV3
ZXI6IExhZGlzbGF2IExob3RrYQ0KPiA+ID4gUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBJc3N1
ZXMNCj4gDQo+IC4uLg0KPiANCj4gPiA+IA0KPiA+ID4gMy4gTWF5YmUgdGhlIGRyYWZ0IGNvdWxk
IG1lbnRpb24gdGhhdCBpbXBsZW1lbnRhdGlvbnMgc2hvdWxkIHN1cHBseSBhDQo+ID4gPiAgIGRl
ZmF1bHQgcm91dGluZyBkb21haW4gYXMgYSBzeXN0ZW0tY29udHJvbGxlZCByZXNvdXJjZS4NCj4g
PiANCj4gPiBJc27igJl0IHRoaXMgbW9yZSBvZiBhbiBSRkM4MDIyQklTIHN0YXRlbWVudD8gSSBn
dWVzcyB3ZSBjb3VsZCBzdGF0ZSB0aGlzIGFzDQo+ID4gYW4gYXNzdW1wdGlvbi4NCj4gDQo+IFBy
b2JhYmx5LCBidXQgaXQgaXMgbm90IGEgWUFORyBpc3N1ZSwgc28gSSdkIGxlYXZlIGl0IHRvIHlv
dSByb3V0aW5nIGZvbGtzIHRvDQo+IGRlY2lkZS4NCj4gDQo+ID4gIA0KPiA+IA0KPiA+ID4gNC4g
SW4gIndoZW4iIGV4cHJlc3Npb25zLCB0aGUgbW9kdWxlIHVzZXMgbGl0ZXJhbCBzdHJpbmdzIGZv
cg0KPiA+ID4gICBpZGVudGl0aWVzLiBUaGlzIGlzIGtub3duIHRvIGJlIHByb2JsZW1hdGljLCB0
aGUgWFBhdGggZnVuY3Rpb25zDQo+ID4gPiAgIGRlcml2ZWQtZnJvbSgpIG9yIGRlcml2ZWQtZnJv
bS1vci1zZWxmKCkgc2hvdWxkIGJlIHVzZWQgaW5zdGVhZC4NCj4gPiANCj4gPiBXaHkgaXMgdGhp
cyBwcm9ibGVtYXRpYz8gSXMgaXQgYmVjYXVzZSB0aGUgdHlwZXMgY2FuIGJlIGV4dGVuZGVkPw0K
PiANCj4gVGhhdCdzIG9uZSByZWFzb246IGRlcml2ZWQgaWRlbnRpdGllcyBzaG91bGQgb2Z0ZW4g
YWxzbyBzYXRpc2Z5IHRoZSBjb25zdHJhaW50Lg0KPiANCj4gQnV0IHRoZSBtb3JlIHNlcmlvdXMg
cHJvYmxlbSBpcyB0aGF0IHRoaW5ncyBsaWtlDQo+IA0KPiAgICAgd2hlbiAiLi4vLi4vLi4vLi4v
Li4vLi4vLi4vcnQ6dHlwZSA9ICdvc3BmOm9zcGZ2MyciDQo+IA0KPiByZWx5IG9uIHBsYWluIHN0
cmluZyBjb21wYXJpc29uIHRoYXQgZGVwZW5kcyBvZCB0aGUgYWN0dWFsIHByZWZpeCB1c2VkIGZv
ciB0aGUNCj4gInJ0OnR5cGUiIHZhbHVlLiBGb3Igb25lLCBhY2NvcmRpbmcgdG8gUkZDIDc5NTEg
dGhlIEpTT04gZW5jb2Rpbmcgb2YgdGhpcyB2YWx1ZQ0KPiB3b3VsZCBiZSAiaWV0Zi1vc3BmOm9z
cGZ2MyIgc28gdGhlIGFib3ZlIGV4cHJlc3Npb24gaXMgYWx3YXlzIGZhbHNlLiANCg0KVGhpcyBp
cyBub3QgY29ycmVjdDsgdGhlIHdoZW4gZXhwcmVzc2lvbiBpcyBub3QgZXZhbHVhdGVkIG9uIHRo
ZSBKU09ODQplbmNvZGluZy4gIFNlZSB0aGUgbGFzdCBwYXJhZ3JhcGggb2Ygc2VjdGlvbiA5LjEw
LjMgaW4gUkZDIDc5NTA6DQoNCiAgIFRoZSBzdHJpbmcgdmFsdWUgb2YgYSBub2RlIG9mIHR5cGUg
ImlkZW50aXR5cmVmIiBpbiBhICJtdXN0IiBvcg0KICAgIndoZW4iIFhQYXRoIGV4cHJlc3Npb24g
aXMgdGhlIHJlZmVycmVkIGlkZW50aXR5J3MgcXVhbGlmaWVkIG5hbWUNCiAgIHdpdGggdGhlIHBy
ZWZpeCBwcmVzZW50LiAgSWYgdGhlIHJlZmVycmVkIGlkZW50aXR5IGlzIGRlZmluZWQgaW4gYW4N
CiAgIGltcG9ydGVkIG1vZHVsZSwgdGhlIHByZWZpeCBpbiB0aGUgc3RyaW5nIHZhbHVlIGlzIHRo
ZSBwcmVmaXggZGVmaW5lZA0KICAgaW4gdGhlIGNvcnJlc3BvbmRpbmcgImltcG9ydCIgc3RhdGVt
ZW50LiAgT3RoZXJ3aXNlLCB0aGUgcHJlZml4IGluDQogICB0aGUgc3RyaW5nIHZhbHVlIGlzIHRo
ZSBwcmVmaXggZm9yIHRoZSBjdXJyZW50IG1vZHVsZS4NCg0KU28gdGhlIGVxdWFsaXR5IHRlc3Qg
b2YgdGhlIGlkZW50aXR5cmVmIGlzIGNvcnJlY3QuDQoNCkhvd2V2ZXIsIEkgYWdyZWUgdGhhdCBp
biBtb3N0IGNhc2VzICdkZXJpdmVkLWZyb20tb3Itc2VsZicgc2hvdWxkIGJlDQp1c2VkLCBpbiBv
cmRlciB0byBoYW5kbGUgZGVyaXZlZCBpZGVudGl0aWVzLg0KDQoNCi9tYXJ0aW4NCg==


From nobody Tue Jan  9 02:00:30 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631F7127011 for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 02:00:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, 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
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 iPvgpSyMuadd for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 02:00:27 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3368C1270AC for <yang-doctors@ietf.org>; Tue,  9 Jan 2018 02:00:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17; q=dns/txt; s=iport; t=1515492027; x=1516701627; h=to:cc:from:subject:message-id:date:mime-version: content-transfer-encoding; bh=/arwFErP0t6d5869rZT3o0Px8DsJ6PsqfbDRb8UlZTk=; b=Ubc3pAFOu113T2LLEKRI7MJ/Vsi3xXjtPAty6LnXQa5UoPTvR+tfEuik agz0qZwtmk2QjRFjqEXhGP7bQrwItAfWhVlIKv9WoglXiGLRif0zZpXP5 WG3qMo1jd5DDrT2t7Av5fU0EPJJN5jKjMtVkF63h0Z3nWbgN55nC1HJOa s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BfBAClkVRa/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYUahC6LGKkbEgqFMQqEfBMBAQEBAQEBAQFrKIVDChVBNQImAl8?= =?us-ascii?q?NCAEBii2vIYInikQBAQEBAQUBAQEBJIEPgxGDbIISizqCRSAFo1+BfpNDgX4BG?= =?us-ascii?q?IYZg2+Hao8SiAeBPDchgVAyGggbFYJohFdAizUBAQE?=
X-IronPort-AV: E=Sophos;i="5.46,335,1511827200";  d="scan'208";a="1346542"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jan 2018 10:00:25 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w09A0PMo004728; Tue, 9 Jan 2018 10:00:25 GMT
To: YANG Doctors <yang-doctors@ietf.org>
Cc: Christian Hopps <chopps@chopps.org>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <fe3f23cc-b5aa-8a5d-2e8f-20200c262abf@cisco.com>
Date: Tue, 9 Jan 2018 11:00:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/gz31nvpfU_uRVcl-rC1j2hMa8uc>
Subject: [yang-doctors] Please welcome Chris Hopps as YANG doctor
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 10:00:29 -0000

Regards, Benoit


From nobody Tue Jan  9 05:35:10 2018
Return-Path: <mersue@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4475912D855 for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 05:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Iwpl139c3hWt for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 05:35:02 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 EEBA1127873 for <yang-doctors@ietf.org>; Tue,  9 Jan 2018 05:35:01 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id b141so20575278wme.1 for <yang-doctors@ietf.org>; Tue, 09 Jan 2018 05:35:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=bvPzEORa3u50ve8k/8PktSGgg7g+4qcrkmjicK8doQM=; b=P4qRi9HawxLFrLbWVK5Hjd5HoJNTN5DRDSWZCvorjaXoaC4az9LsAwtOoIZC04w6NQ B2+7eBYky5HkKQ95KGmtlXh0exV4sq1xlWE2riQM18Adahcnj+i258sLccS7LL0jI7yz 535aPuFXhhM2zRcbPQnUWiuUD0qHS+cQm5pg6C2rZHRysnLmmaqEnbpRVq9plQFSzpj7 2sL9NHg5jxxG3+Tr+JsOWiB5cCMcVNGa9QEBoyxMcw22r7qmSMdZvVKf3ziDynLlMU7L Tfz1FlaPa7JdMS7kCgUOKttz5QqJwfXMqJtp6Kej3LmN9irR5mnJQXHYito6qBFZ7GcU xn1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=bvPzEORa3u50ve8k/8PktSGgg7g+4qcrkmjicK8doQM=; b=QOGk8M5TfLCWgn8JjSjjxysIJNrxdXxyUteVg/B4Wvok1rjLXb8vzmqP0aGUyeNfdp s9e3li7hPDRdRu/dqMqsvXhsvbMyQNmihYZJWIB3oq5p2RSqvQxUNdSn8t3npg/tB3SJ MWqfw89MBO3mg4kqYNMO4fL7liN2OP/uMiyspeXW3rDlXsadJyI2TnzQMAoHt+8KM2M8 zXlsyS851p4yhg0Ea/1dKseDv1zHbzekNrJfINlocbGW8g3wKZH+NMEGs49MJ9tHleV4 /wTd7ztCjNtBeBaeMulTRhJ8CFPiotlYWZvI5Y1Ayf6B2UThVQ6RAPJ/kyXg3CkIIB3I fugw==
X-Gm-Message-State: AKGB3mLDS9kko0lLZKijoFKy+r7xIS7uxciBont14X3xzGVjsUf7BWTI jEvqyqCoxIfl0h4bmuNEeig=
X-Google-Smtp-Source: ACJfBotR6wtR5DrEYAlWhtsgXGfhjWhURo9qI/xRhmAeT8ICGdCSl3+2UH4pNa+6wWsIQohx6ITc8g==
X-Received: by 10.28.125.210 with SMTP id y201mr13248162wmc.13.1515504900351;  Tue, 09 Jan 2018 05:35:00 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([2001:16b8:2dd1:600:98cd:bcb9:3503:bdeb]) by smtp.gmail.com with ESMTPSA id y44sm264672wrd.0.2018.01.09.05.34.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Jan 2018 05:34:59 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Benoit Claise'" <bclaise@cisco.com>, "'YANG Doctors'" <yang-doctors@ietf.org>
Cc: "'Christian Hopps'" <chopps@chopps.org>
References: <fe3f23cc-b5aa-8a5d-2e8f-20200c262abf@cisco.com>
In-Reply-To: <fe3f23cc-b5aa-8a5d-2e8f-20200c262abf@cisco.com>
Date: Tue, 9 Jan 2018 14:34:57 +0100
Message-ID: <009301d3894e$a55398d0$effaca70$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDy88KJG+8C/4moVQhCsax6oIRPB6UstZlQ
Content-Language: de
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/5SUOR9j3RlxbjNGZxdqnMlwqk9w>
Subject: Re: [yang-doctors] Please welcome Chris Hopps as YANG doctor
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 13:35:09 -0000

Welcome Christian!

I'll add you to the maillist.

Cheers,
Mehmet

> -----Original Message-----
> From: yang-doctors [mailto:yang-doctors-bounces@ietf.org] On Behalf Of
> Benoit Claise
> Sent: Tuesday, January 9, 2018 11:00 AM
> To: YANG Doctors <yang-doctors@ietf.org>
> Cc: Christian Hopps <chopps@chopps.org>
> Subject: [yang-doctors] Please welcome Chris Hopps as YANG doctor
> 
> Regards, Benoit
> 
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors


From nobody Tue Jan  9 07:02:06 2018
Return-Path: <rkrejci@cesnet.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B300012D86C; Tue,  9 Jan 2018 07:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level: 
X-Spam-Status: No, score=-4.309 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_MED=-2.3, T_RP_MATCHES_RCVD=-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=cesnet.cz
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 PPDYUnsAjhig; Tue,  9 Jan 2018 07:01:58 -0800 (PST)
Received: from office2.cesnet.cz (office2.cesnet.cz [IPv6:2001:718:1:101::144:244]) (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 F2EC3126C0F; Tue,  9 Jan 2018 07:01:57 -0800 (PST)
Received: from pckrejci.nat9.vcit.vutbr.net (unknown [IPv6:2001:67c:1220:80c:d0:552c:73a5:18da]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by office2.cesnet.cz (Postfix) with ESMTPSA id 5C3CE400065; Tue,  9 Jan 2018 16:01:54 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=office2; t=1515510114; bh=naClBdZvux3jD73SoAsAQEt7sy8R1v8aE0K+cZSeAJE=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=K+EcsZglGf3Tb/9GaZdOb4r8ptpDWnoah5e7JUBxQaF5wrRAJvm1K/apZibEHEvv7 3kOp49l2Zc975d2//0viBpA20d9EGRiX+14wHoNGT4Wtrj6wH01493oGXVg/eDuAym EG7eB6FEvDeemCgKS8zUSy146CRZN3M7Wn7dvSSg=
To: Martin Bjorklund <mbj@tail-f.com>
Cc: yang-doctors@ietf.org, draft-ietf-netmod-entity.all@ietf.org, netmod@ietf.org
References: <151507502144.23798.1644071576333370968@ietfa.amsl.com> <20180108.162153.18427707995478583.mbj@tail-f.com>
From: =?UTF-8?B?UmFkZWsgS3JlasSNw60=?= <rkrejci@cesnet.cz>
Message-ID: <08db428e-f9af-022d-0dc9-c14dbddcd745@cesnet.cz>
Date: Tue, 9 Jan 2018 16:01:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180108.162153.18427707995478583.mbj@tail-f.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/ftEbS46eRCjYlsc8TP7elQmYxa0>
Subject: Re: [yang-doctors] [netmod] Yangdoctors last call review of draft-ietf-netmod-entity-07
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 15:02:00 -0000

Hi Martin,
you are right, now I see it. So, to me, the document is Ready.

Andy, text in RFC6087bis (Temporary non-NMDA Modules) should be changed s=
ince it seems to limit the temporary module to contain data nodes only.

OLD
=C2=A0=C2=A0=C2=A0 It contains the top-level config=3Dfalse data nodes th=
at would have been defined in a legacy YANG module (before NMDA).

NEW
=C2=A0=C2=A0=C2=A0 It contains the top-level config=3Dfalse data nodes th=
at would have been defined in a legacy YANG module (before NMDA) as well =
as the notifications, RPCs and actions that would refer such nodes.


Regards,
Radek



Dne 8.1.2018 v 16:21 Martin Bjorklund napsal(a):
> Hi,
>
> Radek Krej=C4=8D=C3=AD <rkrejci@cesnet.cz> wrote:
>> Reviewer: Radek Krej=C4=8D=C3=AD
>> Review result: Ready with Issues
>>
>> The document itself and normative parts seem fine to me, the only issu=
e I see
>> is with the ietf-hardware-state module in non-normative appendix A. It=
 seems to
>> me that this temporary non-NMDA module does not conform to its purpose=
 as
>> described in RFC6087bis. According to guidelines, such a module is int=
ended to
>> provide state (config false) data in case the server does not implemen=
t NMDA
>> (to bridge the time period until NMDA is implemented). So such a serve=
r is IMHO
>> intended to implement both modules, foo and foo-state. The foo-state c=
ontains
>> "the top-level config-false data nodes that would have been defined in=
 a legacy
>> YANG module" - so it's only the ro mirror of data nodes. But
>> ietf-hardware-state contains notifications, which are not the data nod=
es as
>> defined in RFC7950. I understand why the notifications were placed als=
o into
>> the ietf-hardware-state - the module's description states that "If a s=
erver
>> that implements this module but doesn't support NMDA also supports
>> configuration of hardware components, it SHOULD also implement the mod=
ule
>> 'ietf-hardware' ...", so it allows its standalone usage in case the se=
rver does
>> not support hw configuration. But in such a case, the server can imple=
ment
>> ietf-hardware with deviations on the config=3Dtrue nodes.
> The problem with useing the notifcations defined in ietf-hardware in
> this case is that all leafrefs would be wrong; they'd point into a
> schema that is not implemented.
>
>> The same way it had to
>> implement the legacy YANG module (before NMDA).
> Before NMDA the leafrefs in the notifcations pointed to
> /hardware-state, and all config was defined with an if-feature, so a
> server did not have to use any deviations in this case.
>
>
>
> /martin
>
>
>
>> So I think that the notifications should be removed from ietf-hardware=
-state
>> and the module's description should change this way:
>>
>> OLD
>>
>>   If a server that implements this module but doesn't support NMDA
>>   also supports configuration of hardware components, it SHOULD
>>   also implement the module 'ietf-hardware' in the configuration
>>   datastores. The corresponding state data is found in the
>>   '/hw-state:hardware' subtree.
>>
>> NEW
>>
>>   If a server that implements this module but doesn't support NMDA,
>>   it MUST also implement the module 'ietf-hardware' in the
>>   configuration datastores. The corresponding state data is found
>>   in the '/hw-state:hardware' subtree.
>>
>>
>> _______________________________________________
>> netmod mailing list
>> netmod@ietf.org
>> https://www.ietf.org/mailman/listinfo/netmod



From nobody Tue Jan  9 07:20:59 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE462126C0F; Tue,  9 Jan 2018 07:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 YpKs4BVUxRJj; Tue,  9 Jan 2018 07:20:44 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 26F4B1205F0; Tue,  9 Jan 2018 07:20:43 -0800 (PST)
Received: from birdie (cst-prg-24-198.cust.vodafone.cz [46.135.24.198]) by mail.nic.cz (Postfix) with ESMTPSA id 1866C63DCE; Tue,  9 Jan 2018 16:20:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1515511241; bh=OU0uMU2VBsjX5vK2wtAuBGuHimdB28PQlgpZkHLMjws=; h=From:To:Date; b=b+RrffikV0hyjfgSPd7iE03rgpN/rhCX+XaU9n4NYtaWsmwtSnxUUnQqvAf0S2VfX DnJ3nEOWWGhPkMmnvfXSAxbVNfLOY2ErQ8rJpsxG9EqhPTHb2Zje5H23OlBcCiuro4 EGv8DFnKMSs7C0qM+hd3Q6NbXFo/DzGRK3Pl7BJ8=
Message-ID: <1515510536.26845.18.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: acee@cisco.com, yang-doctors@ietf.org, draft-ietf-ospf-yang.all@ietf.org,  ietf@ietf.org, ospf@ietf.org
In-Reply-To: <20180109.090648.1082913423972100343.mbj@tail-f.com>
References: <151255960762.30655.17225294251460480729@ietfa.amsl.com> <D6792F3D.E8CD1%acee@cisco.com> <1515484295.18448.9.camel@nic.cz> <20180109.090648.1082913423972100343.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 09 Jan 2018 16:08:56 +0100
Mime-Version: 1.0
X-Mailer: Evolution 3.26.3 
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/0had1Y72Qj2zsJrf08SIiaZQ3aw>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 15:20:47 -0000

On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> Hi,
> 
> Ladislav Lhotka <lhotka@nic.cz> wrote:
> > Hi Acee,
> 
> > 
> 
> > please see inline.
> 
> > 
> 
> > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> 
> > > Hi Lada,
> 
> > > 
> 
> > > Apologies for the delay. We somewhat got hung up on 4 and 6. See inline.
> 
> > > 
> 
> > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> 
> > > 
> 
> > > > Reviewer: Ladislav Lhotka
> 
> > > > Review result: Ready with Issues
> 
> > 
> 
> > ...
> 
> > 
> 
> > > > 
> 
> > > > 3. Maybe the draft could mention that implementations should supply a
> 
> > > >   default routing domain as a system-controlled resource.
> 
> > > 
> 
> > > Isnâ€™t this more of an RFC8022BIS statement? I guess we could state this as
> 
> > > an assumption.
> 
> > 
> 
> > Probably, but it is not a YANG issue, so I'd leave it to you routing folks
> to
> 
> > decide.
> 
> > 
> 
> > >  
> 
> > > 
> 
> > > > 4. In "when" expressions, the module uses literal strings for
> 
> > > >   identities. This is known to be problematic, the XPath functions
> 
> > > >   derived-from() or derived-from-or-self() should be used instead.
> 
> > > 
> 
> > > Why is this problematic? Is it because the types can be extended?
> 
> > 
> 
> > That's one reason: derived identities should often also satisfy the
> constraint.
> 
> > 
> 
> > But the more serious problem is that things like
> 
> > 
> 
> >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> 
> > 
> 
> > rely on plain string comparison that depends od the actual prefix used for
> the
> 
> > "rt:type" value. For one, according to RFC 7951 the JSON encoding of this
> value
> 
> > would be "ietf-ospf:ospfv3" so the above expression is always false. 
> 
> 
> This is not correct; the when expression is not evaluated on the JSON
> encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> 
>    The string value of a node of type "identityref" in a "must" or
>    "when" XPath expression is the referred identity's qualified name
>    with the prefix present.  If the referred identity is defined in an
>    imported module, the prefix in the string value is the prefix defined
>    in the corresponding "import" statement.  Otherwise, the prefix in
>    the string value is the prefix for the current module.

This is weird, to say the least. The leafref instance may have an identity value
that is defined in a module that (has to be implemented by the server but)
needn't be imported in the module that contains the XPath expression. So I don't
know what 'corresponding "import" statement' this paragraph is talking about.

Also, potentially there can be a collision in prefixes and then this also breaks
down.

A moral of the namespace/prefix story in XML was that relying of namespace
prefixes having a particular value is a really bad idea. I know that the cited
paragraph was intended to make such XPath string comparisons more deterministic,
but it is also problematic and should be avoided if possible. 

Lada

> 
> So the equality test of the identityref is correct.
> 
> However, I agree that in most cases 'derived-from-or-self' should be
> used, in order to handle derived identities.
> 
> 
> /martin
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Tue Jan  9 07:23:22 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 252D4126C0F; Tue,  9 Jan 2018 07:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 SzIEWrVq4Bh6; Tue,  9 Jan 2018 07:23:05 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 2000F1205F0; Tue,  9 Jan 2018 07:23:05 -0800 (PST)
Received: from birdie (cst-prg-24-198.cust.vodafone.cz [46.135.24.198]) by mail.nic.cz (Postfix) with ESMTPSA id A352D63DD6; Tue,  9 Jan 2018 16:23:03 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1515511383; bh=u1ZMqh+sPrDwrEWWUvhIqbOjCuh5NSgOvTGO0UfuA/k=; h=From:To:Date; b=HjQvQn7tmQQ54Q+0xNsJ0Uc78cJKFbaOoD9rbe/EQTt5IrTyd6cvlS0Sppmpzmnjr b9BWlAPErhAI89GVetE08OJQp+MBNPeZkxF61oQNydkhsX+I3MPbEGQcktsu9BNkB5 9ji3AkTTHcxuPou7fDHrndeHctsbbPYJqpd0rO2k=
Message-ID: <1515511383.26845.19.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: yang-doctors@ietf.org, ietf@ietf.org, ospf@ietf.org,  draft-ietf-ospf-yang.all@ietf.org
Date: Tue, 09 Jan 2018 16:23:03 +0100
In-Reply-To: <1515510536.26845.18.camel@nic.cz>
References: <151255960762.30655.17225294251460480729@ietfa.amsl.com> <D6792F3D.E8CD1%acee@cisco.com> <1515484295.18448.9.camel@nic.cz> <20180109.090648.1082913423972100343.mbj@tail-f.com> <1515510536.26845.18.camel@nic.cz>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/EkahzU3N1iOm5Nc2cqZH3gO_Zw4>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 15:23:07 -0000

On Tue, 2018-01-09 at 16:08 +0100, Ladislav Lhotka wrote:
> On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > Hi,
> > 
> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > Hi Acee,
> > > 
> > > please see inline.
> > > 
> > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> > > > Hi Lada,
> > > > 
> > > > Apologies for the delay. We somewhat got hung up on 4 and 6. See inline.
> > > > 
> > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> > > > 
> > > > > Reviewer: Ladislav Lhotka
> > > > > Review result: Ready with Issues
> > > 
> > > ...
> > > 
> > > > > 
> > > > > 3. Maybe the draft could mention that implementations should supply a
> > > > >   default routing domain as a system-controlled resource.
> > > > 
> > > > Isnâ€™t this more of an RFC8022BIS statement? I guess we could state this
> > > > as
> > > > an assumption.
> > > 
> > > Probably, but it is not a YANG issue, so I'd leave it to you routing folks
> > 
> > to
> > 
> > > decide.
> > > 
> > > >  
> > > > 
> > > > > 4. In "when" expressions, the module uses literal strings for
> > > > >   identities. This is known to be problematic, the XPath functions
> > > > >   derived-from() or derived-from-or-self() should be used instead.
> > > > 
> > > > Why is this problematic? Is it because the types can be extended?
> > > 
> > > That's one reason: derived identities should often also satisfy the
> > 
> > constraint.
> > 
> > > 
> > > But the more serious problem is that things like
> > > 
> > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > 
> > > rely on plain string comparison that depends od the actual prefix used for
> > 
> > the
> > 
> > > "rt:type" value. For one, according to RFC 7951 the JSON encoding of this
> > 
> > value
> > 
> > > would be "ietf-ospf:ospfv3" so the above expression is always false. 
> > 
> > 
> > This is not correct; the when expression is not evaluated on the JSON
> > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> > 
> >    The string value of a node of type "identityref" in a "must" or
> >    "when" XPath expression is the referred identity's qualified name
> >    with the prefix present.  If the referred identity is defined in an
> >    imported module, the prefix in the string value is the prefix defined
> >    in the corresponding "import" statement.  Otherwise, the prefix in
> >    the string value is the prefix for the current module.
> 
> This is weird, to say the least. The leafref instance may have an identity 

Sorry, I meant "identityref" here --------^

Lada

> value
> that is defined in a module that (has to be implemented by the server but)
> needn't be imported in the module that contains the XPath expression. So I
> don't
> know what 'corresponding "import" statement' this paragraph is talking about.
> 
> Also, potentially there can be a collision in prefixes and then this also
> breaks
> down.
> 
> A moral of the namespace/prefix story in XML was that relying of namespace
> prefixes having a particular value is a really bad idea. I know that the cited
> paragraph was intended to make such XPath string comparisons more
> deterministic,
> but it is also problematic and should be avoided if possible. 
> 
> Lada
> 
> > 
> > So the equality test of the identityref is correct.
> > 
> > However, I agree that in most cases 'derived-from-or-self' should be
> > used, in order to handle derived identities.
> > 
> > 
> > /martin
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Tue Jan  9 07:25:08 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A2D12895E; Tue,  9 Jan 2018 07:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 lW-tIlglgdci; Tue,  9 Jan 2018 07:24:55 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 2A21A1205F0; Tue,  9 Jan 2018 07:24:55 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id CDCD91AE0144; Tue,  9 Jan 2018 16:24:53 +0100 (CET)
Date: Tue, 09 Jan 2018 16:23:11 +0100 (CET)
Message-Id: <20180109.162311.49506989189385960.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: acee@cisco.com, yang-doctors@ietf.org, draft-ietf-ospf-yang.all@ietf.org, ietf@ietf.org, ospf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1515510536.26845.18.camel@nic.cz>
References: <1515484295.18448.9.camel@nic.cz> <20180109.090648.1082913423972100343.mbj@tail-f.com> <1515510536.26845.18.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/45tezvADxaojOFnXdN2nViyoMMk>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 15:24:58 -0000

TGFkaXNsYXYgTGhvdGthIDxsaG90a2FAbmljLmN6PiB3cm90ZToNCj4gT24gVHVlLCAyMDE4LTAx
LTA5IGF0IDA5OjA2ICswMTAwLCBNYXJ0aW4gQmpvcmtsdW5kIHdyb3RlOg0KPiA+IEhpLA0KPiA+
IA0KPiA+IExhZGlzbGF2IExob3RrYSA8bGhvdGthQG5pYy5jej4gd3JvdGU6DQo+ID4gPiBIaSBB
Y2VlLA0KPiA+IA0KPiA+ID4gDQo+ID4gDQo+ID4gPiBwbGVhc2Ugc2VlIGlubGluZS4NCj4gPiAN
Cj4gPiA+IA0KPiA+IA0KPiA+ID4gT24gTW9uLCAyMDE4LTAxLTA4IGF0IDE5OjI4ICswMDAwLCBB
Y2VlIExpbmRlbSAoYWNlZSkgd3JvdGU6DQo+ID4gDQo+ID4gPiA+IEhpIExhZGEsDQo+ID4gDQo+
ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiBBcG9sb2dpZXMgZm9yIHRoZSBkZWxheS4gV2Ugc29tZXdo
YXQgZ290IGh1bmcgdXAgb24gNCBhbmQgNi4gU2VlIGlubGluZS4NCj4gPiANCj4gPiA+ID4gDQo+
ID4gDQo+ID4gPiA+IE9uIDEyLzYvMTcsIDY6MjYgQU0sICJMYWRpc2xhdiBMaG90a2EiIDxsaG90
a2FAbmljLmN6PiB3cm90ZToNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gUmV2aWV3
ZXI6IExhZGlzbGF2IExob3RrYQ0KPiA+IA0KPiA+ID4gPiA+IFJldmlldyByZXN1bHQ6IFJlYWR5
IHdpdGggSXNzdWVzDQo+ID4gDQo+ID4gPiANCj4gPiANCj4gPiA+IC4uLg0KPiA+IA0KPiA+ID4g
DQo+ID4gDQo+ID4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gMy4gTWF5YmUgdGhlIGRyYWZ0IGNv
dWxkIG1lbnRpb24gdGhhdCBpbXBsZW1lbnRhdGlvbnMgc2hvdWxkIHN1cHBseSBhDQo+ID4gDQo+
ID4gPiA+ID4gICBkZWZhdWx0IHJvdXRpbmcgZG9tYWluIGFzIGEgc3lzdGVtLWNvbnRyb2xsZWQg
cmVzb3VyY2UuDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiBJc27igJl0IHRoaXMgbW9y
ZSBvZiBhbiBSRkM4MDIyQklTIHN0YXRlbWVudD8gSSBndWVzcyB3ZSBjb3VsZCBzdGF0ZSB0aGlz
IGFzDQo+ID4gDQo+ID4gPiA+IGFuIGFzc3VtcHRpb24uDQo+ID4gDQo+ID4gPiANCj4gPiANCj4g
PiA+IFByb2JhYmx5LCBidXQgaXQgaXMgbm90IGEgWUFORyBpc3N1ZSwgc28gSSdkIGxlYXZlIGl0
IHRvIHlvdSByb3V0aW5nIGZvbGtzDQo+ID4gdG8NCj4gPiANCj4gPiA+IGRlY2lkZS4NCj4gPiAN
Cj4gPiA+IA0KPiA+IA0KPiA+ID4gPiAgDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiA+
IDQuIEluICJ3aGVuIiBleHByZXNzaW9ucywgdGhlIG1vZHVsZSB1c2VzIGxpdGVyYWwgc3RyaW5n
cyBmb3INCj4gPiANCj4gPiA+ID4gPiAgIGlkZW50aXRpZXMuIFRoaXMgaXMga25vd24gdG8gYmUg
cHJvYmxlbWF0aWMsIHRoZSBYUGF0aCBmdW5jdGlvbnMNCj4gPiANCj4gPiA+ID4gPiAgIGRlcml2
ZWQtZnJvbSgpIG9yIGRlcml2ZWQtZnJvbS1vci1zZWxmKCkgc2hvdWxkIGJlIHVzZWQgaW5zdGVh
ZC4NCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+IFdoeSBpcyB0aGlzIHByb2JsZW1hdGlj
PyBJcyBpdCBiZWNhdXNlIHRoZSB0eXBlcyBjYW4gYmUgZXh0ZW5kZWQ/DQo+ID4gDQo+ID4gPiAN
Cj4gPiANCj4gPiA+IFRoYXQncyBvbmUgcmVhc29uOiBkZXJpdmVkIGlkZW50aXRpZXMgc2hvdWxk
IG9mdGVuIGFsc28gc2F0aXNmeSB0aGUNCj4gPiBjb25zdHJhaW50Lg0KPiA+IA0KPiA+ID4gDQo+
ID4gDQo+ID4gPiBCdXQgdGhlIG1vcmUgc2VyaW91cyBwcm9ibGVtIGlzIHRoYXQgdGhpbmdzIGxp
a2UNCj4gPiANCj4gPiA+IA0KPiA+IA0KPiA+ID4gICAgIHdoZW4gIi4uLy4uLy4uLy4uLy4uLy4u
Ly4uL3J0OnR5cGUgPSAnb3NwZjpvc3BmdjMnIg0KPiA+IA0KPiA+ID4gDQo+ID4gDQo+ID4gPiBy
ZWx5IG9uIHBsYWluIHN0cmluZyBjb21wYXJpc29uIHRoYXQgZGVwZW5kcyBvZCB0aGUgYWN0dWFs
IHByZWZpeCB1c2VkIGZvcg0KPiA+IHRoZQ0KPiA+IA0KPiA+ID4gInJ0OnR5cGUiIHZhbHVlLiBG
b3Igb25lLCBhY2NvcmRpbmcgdG8gUkZDIDc5NTEgdGhlIEpTT04gZW5jb2Rpbmcgb2YgdGhpcw0K
PiA+IHZhbHVlDQo+ID4gDQo+ID4gPiB3b3VsZCBiZSAiaWV0Zi1vc3BmOm9zcGZ2MyIgc28gdGhl
IGFib3ZlIGV4cHJlc3Npb24gaXMgYWx3YXlzIGZhbHNlLiANCj4gPiANCj4gPiANCj4gPiBUaGlz
IGlzIG5vdCBjb3JyZWN0OyB0aGUgd2hlbiBleHByZXNzaW9uIGlzIG5vdCBldmFsdWF0ZWQgb24g
dGhlIEpTT04NCj4gPiBlbmNvZGluZy4gIFNlZSB0aGUgbGFzdCBwYXJhZ3JhcGggb2Ygc2VjdGlv
biA5LjEwLjMgaW4gUkZDIDc5NTA6DQo+ID4gDQo+ID4gICAgVGhlIHN0cmluZyB2YWx1ZSBvZiBh
IG5vZGUgb2YgdHlwZSAiaWRlbnRpdHlyZWYiIGluIGEgIm11c3QiIG9yDQo+ID4gICAgIndoZW4i
IFhQYXRoIGV4cHJlc3Npb24gaXMgdGhlIHJlZmVycmVkIGlkZW50aXR5J3MgcXVhbGlmaWVkIG5h
bWUNCj4gPiAgICB3aXRoIHRoZSBwcmVmaXggcHJlc2VudC4gIElmIHRoZSByZWZlcnJlZCBpZGVu
dGl0eSBpcyBkZWZpbmVkIGluIGFuDQo+ID4gICAgaW1wb3J0ZWQgbW9kdWxlLCB0aGUgcHJlZml4
IGluIHRoZSBzdHJpbmcgdmFsdWUgaXMgdGhlIHByZWZpeCBkZWZpbmVkDQo+ID4gICAgaW4gdGhl
IGNvcnJlc3BvbmRpbmcgImltcG9ydCIgc3RhdGVtZW50LiAgT3RoZXJ3aXNlLCB0aGUgcHJlZml4
IGluDQo+ID4gICAgdGhlIHN0cmluZyB2YWx1ZSBpcyB0aGUgcHJlZml4IGZvciB0aGUgY3VycmVu
dCBtb2R1bGUuDQo+IA0KPiBUaGlzIGlzIHdlaXJkLCB0byBzYXkgdGhlIGxlYXN0LiBUaGUgbGVh
ZnJlZiBpbnN0YW5jZSBtYXkgaGF2ZSBhbiBpZGVudGl0eSB2YWx1ZQ0KPiB0aGF0IGlzIGRlZmlu
ZWQgaW4gYSBtb2R1bGUgdGhhdCAoaGFzIHRvIGJlIGltcGxlbWVudGVkIGJ5IHRoZSBzZXJ2ZXIg
YnV0KQ0KPiBuZWVkbid0IGJlIGltcG9ydGVkIGluIHRoZSBtb2R1bGUgdGhhdCBjb250YWlucyB0
aGUgWFBhdGggZXhwcmVzc2lvbi4gU28gSSBkb24ndA0KPiBrbm93IHdoYXQgJ2NvcnJlc3BvbmRp
bmcgImltcG9ydCIgc3RhdGVtZW50JyB0aGlzIHBhcmFncmFwaCBpcyB0YWxraW5nIGFib3V0Lg0K
DQpJdCBoYXMgdG8gaW1wb3J0IHRoZSBtb2R1bGUgaW4gb3JkZXIgdG8gZ2l2ZSBhIHByZWZpeCwg
d2hpY2ggdGhlbiBjYW4NCmJlIHVzZWQgaW4gdGhlIFhQYXRoIGV4cHJlc3Npb24uDQoNCj4gQWxz
bywgcG90ZW50aWFsbHkgdGhlcmUgY2FuIGJlIGEgY29sbGlzaW9uIGluIHByZWZpeGVzIGFuZCB0
aGVuIHRoaXMgYWxzbyBicmVha3MNCj4gZG93bi4NCg0KTm8sIHR3byBtb2R1bGVzIGNhbm5vdCBi
ZSBpbXBvcnRlZCB3aXRoIHRoZSBzYW1lIHByZWZpeC4NCg0KPiBBIG1vcmFsIG9mIHRoZSBuYW1l
c3BhY2UvcHJlZml4IHN0b3J5IGluIFhNTCB3YXMgdGhhdCByZWx5aW5nIG9mIG5hbWVzcGFjZQ0K
PiBwcmVmaXhlcyBoYXZpbmcgYSBwYXJ0aWN1bGFyIHZhbHVlIGlzIGEgcmVhbGx5IGJhZCBpZGVh
LiBJIGtub3cgdGhhdCB0aGUgY2l0ZWQNCj4gcGFyYWdyYXBoIHdhcyBpbnRlbmRlZCB0byBtYWtl
IHN1Y2ggWFBhdGggc3RyaW5nIGNvbXBhcmlzb25zIG1vcmUgZGV0ZXJtaW5pc3RpYywNCj4gYnV0
IGl0IGlzIGFsc28gcHJvYmxlbWF0aWMgYW5kIHNob3VsZCBiZSBhdm9pZGVkIGlmIHBvc3NpYmxl
Lg0KDQpOb3RlIHRoYXQgdGhpcyBwcmVmaXggaXMgdW5kZXIgdGhlIGNvbnRyb2wgb2YgdGhlIG1v
ZHVsZSBkZXNpZ25lcg0Kd3JpdGluZyB0aGUgWFBhdGggZXhwcmVzc2lvbi4gIFRoZSBzYW1lIGlk
ZW50aXR5cmVmIHZhbHVlIG1pZ2h0IHVzZSBhDQpkaWZmZXJlbnQgcHJlZml4IGluIHNvbWUgb3Ro
ZXIgbW9kdWxlLg0KDQoNCi9tYXJ0aW4NCg0KDQoNCj4gDQo+IExhZGENCj4gDQo+ID4gDQo+ID4g
U28gdGhlIGVxdWFsaXR5IHRlc3Qgb2YgdGhlIGlkZW50aXR5cmVmIGlzIGNvcnJlY3QuDQo+ID4g
DQo+ID4gSG93ZXZlciwgSSBhZ3JlZSB0aGF0IGluIG1vc3QgY2FzZXMgJ2Rlcml2ZWQtZnJvbS1v
ci1zZWxmJyBzaG91bGQgYmUNCj4gPiB1c2VkLCBpbiBvcmRlciB0byBoYW5kbGUgZGVyaXZlZCBp
ZGVudGl0aWVzLg0KPiA+IA0KPiA+IA0KPiA+IC9tYXJ0aW4NCj4gLS0gDQo+IExhZGlzbGF2IExo
b3RrYQ0KPiBIZWFkLCBDWi5OSUMgTGFicw0KPiBQR1AgS2V5IElEOiAweEI4RjkyQjA4QTlGNzZD
NjcNCj4gDQo=


From nobody Tue Jan  9 07:43:41 2018
Return-Path: <janl@tail-f.com>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C820B12D879; Tue,  9 Jan 2018 07:43:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Jan Lindblad <janl@tail-f.com>
To: <yang-doctors@ietf.org>
Cc: netmod@ietf.org, ietf@ietf.org, draft-ietf-netmod-revised-datastores.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151551261178.1806.130953175040927039@ietfa.amsl.com>
Date: Tue, 09 Jan 2018 07:43:31 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/JAYjbuZJHEdg0CYdJAQNLLEbt9A>
Subject: [yang-doctors] Yangdoctors early review of draft-ietf-netmod-revised-datastores-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 15:43:32 -0000

Reviewer: Jan Lindblad
Review result: Ready

Finally the NMDA datastores draft has reached WGLC, and I have been assigned as
YD reviewer; quite an honor ;-)

Because of the pretty fundamental importance of this document, I performed what
I consider myself a pretty thorough review. Since this work has been going on
for a very long time and with high intensity at times, I have not even tried to
keep up to date with all the discussions. So in order not to resurrect all the
beaten zombies that this spec has seen, I decided to let the document shepherd
and principal author Martin BjÃ¶rklund review my review.

The end result of which is that I withdraw every one of my comments and
proclaim review result Ready.

For full transparency (and to show that I wasn't lazy after all), I have
enclosed my initial review findings below. Note that I now feel that they are
either discussed enough already, addressed in a different document (e.g. YANG
library), or misunderstandings/proposals on my part that do not necessarily
merit further discussion or clarification. Finally I will add that no blackmail
or bribery ;-) was involved in me reaching this conclusion; merely a good
discussion.

/jan

Topic #1: Loss of operational stringency

According to RFC 6020 tradition, config false data returned from <get>
operations MUST adhere to the constraints declared in the YANG modules;
max-elements, must statements, unique keys, etc. This is obviously a high
standard to live up to for server implementors. With NMDA, the situation
reverses so that <get> operations will return data from <operational> where no
semantic guarantees apply. This moves the burden of managing flux and
inconsistency from the servers to the clients.

Now each client has to be able to deal with potentially duplicate keys,
violated constraints and generally that any YANG model semantic guarantee is a
mere recommendation.

Personally I find this rather shocking. One of the core values in NETCONF/YANG
has always been that it sides with the "operator" or "client" view of the
world. Decades ago we had SNMP (Simple ...) -- which in practice meant simple
to *implement*, not simple to use. NC/Y is supposed to be the other way around.
Hard to implement, but easy to use.

If we feel strict adherence to the YANG declaration is a bar too high for
operational data, maybe we could find some middle ground? Just giving up and
saying that anything anywhere may be violated anytime is to make it too easy
for implementors and too hard for clients, IMHO.

If I'm beating on a dead horse here, I apologize ;-) I just want to ensure that
if this is what we want, it should be an informed decision.

Topic #2: Actions live in <operational>

NMDA says actions are always invoked in context of the <operational> data
store. In many cases I agree this makes good sense. But there are a couple of
catches here.

The first catch relates to timing. As the server is not obliged to make an
element committed in <intended> immediately available in <operational>, a
client that creates a bit of configuration and is interested to execute an
action on it will not know when to fire the action. Should it poll for the
object creation? Keep retrying? I sense the creation of Heisenbugs and interop
issues.

The second catch relates to structure translation between <running> and
<intended>. If the configuration committed to <running> by the client has no
direct counterpart in <intended> and <operational>, there is nothing to invoke
the action on. Say I used a templating feature in <running> to define a bit of
configuration, and now I want to execute a check-sync action on that piece of
config to see that the config has propagated properly. There is no context to
invoke the action on in <operational>.

Similarly, for actions that update <running> (e.g. config wizards), executing
in <running> would make sense. Maybe an ability to specify the context
datastore in the rpc would be enough to fix this. Or better perhaps, the target
datastore should be formally declared by the action/rpc?

Such a declaration would solve another issue that exists today. A client needs
to parse English to know if an action changes <running>. Any configuration data
cached by the client would need to be invalidated iff so. With a formal
mechanism to declare which datastores are (not) affected, clients could be a
lot more efficient. This is a real issue.

Topic #3: Datastore specific deviations

How would I express a deviation that applies to one datastore but not another?
Say, for example, that I have a deviate not-implemented on an object in
<running> but I support it in <operational>.

Topic #4: NMDA compliance declaration

How would a client know that a server works according to NMDA principles? I
suppose the intent is that there is no need to know because things are
"backwards compatible", and that for a given server the answer may vary
depending on which data model we're talking about. But as discussed in topic
#1, #2, #3 above (and more below), significant semantic differences are
introduced by NMDA. As client implementor, I would want to know what to expect
from a server.

Topic #5: Origin of unset values

When the operational view is constructed, the draft describes situations where
the operational value may be taken in some cases from or:intended and in other
from or:learned. While it would be valuable for clients to understand what the
precedence rule is, this may be a bit too complex to declare formally, since it
is quite possible that the mechanics of which value shows up isn't always
simple and may depend on other leaf values.

In the example with a DHCP learned address trumping an intended address, it
could be that the DHCP server specifies only an IPv6 address. In which case the
device policy might be to override the IPv4 address in intended with no value.
In this situation, there is no way for the server to communicate why there is
no IPv4 address (it was or:learned), since the origin attribute cannot live on
a non-existent XML element.

So the origin mechanism does not work well for optional elements.

Topic #6: Datastore and origin identity trees

Why are there two trees with identities, one for datastores and one with
origins? Most values seems to be the same, with the origins being a superset of
the datastores. By organizing them into a single tree with all the datastores
as one branch of the origins tree, we could get something simpler.

moduel ietf-origin {
    identity origin;

    identity unknown { base origin; }
    identity system { base origin; }
    identity learned { base origin; }
    identity default { base origin; }
    identity datastore { base origin; }

    identity conventional { base datastore; }
    identity running { base conventional; }
    identity candidate { base conventional; }
    identity startup { base conventional; }
    identity intended { base conventional; }
    identity dynamic { base datastore; }
    identity operational { base datastore; }

    /*
     * Type definitions
     */

    typedef origin-ref {
      type identityref {
        base origin;
      }
    }

    typedef datastore-ref {
      type identityref {
        base datastore;
      }
    }

Topic #7: Editorial

Below are a few details about the wording:

On pages 3 and 4, it is said that
"These datastores share a common datastore schema"
and
"""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."""

If we have a device that support macros/templates/services in <running>, which
expands into concrete configuration in <intended>, I don't suppose the
macro/template/service instances would be part of <intended>? If so, I guess
the schemas are not exactly the same? Maybe we can say that <intended> is a
subset of the <running> schemas (plus all the config false data)?

p15: Maybe we could point out that learned values etc MUST NOT update
<running>/<intended> to make this entirely clear.

p24: Juergen Schoenwaelder's funding is mentioned, but not his participation

p27: what's <get-data> ?

p28: ds-ephemeral and or-ephemeral are not great names. Will be referred to as
ds:ds-ephemeral and or:or-ephemeral. Would prefer ds:ephemeral and or:ephemeral.

/jan



From nobody Tue Jan  9 08:08:39 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F27126D0C; Tue,  9 Jan 2018 08:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 VSm3R9w-_Hmg; Tue,  9 Jan 2018 08:08:25 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 EA2381200C5; Tue,  9 Jan 2018 08:08:24 -0800 (PST)
Received: from birdie (cst-prg-24-76.cust.vodafone.cz [46.135.24.76]) by mail.nic.cz (Postfix) with ESMTPSA id 1EBB363E14; Tue,  9 Jan 2018 17:08:22 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1515514102; bh=ly1CH8aeMsyyFOsKAKDcLZj1irekzLP3dExIKhZa0NY=; h=From:To:Date; b=BNpt3mx2RkQGhOzL60punU9Xq+5aIXmNgtaozhvl4w30nkbAM0DPgUQJecIWWK99R o4WrD0eyA2tYQHAEHAwqRFA3HNMDXSNoDXR/tDFGCPveNz1okXQU5JHWAAUVolGGMB oynsK5c1YTlgyC5FVb0I1Q1WEO7k+39Un8pujmr8=
Message-ID: <1515514101.26845.52.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: acee@cisco.com, yang-doctors@ietf.org, draft-ietf-ospf-yang.all@ietf.org,  ietf@ietf.org, ospf@ietf.org
Date: Tue, 09 Jan 2018 17:08:21 +0100
In-Reply-To: <20180109.162311.49506989189385960.mbj@tail-f.com>
References: <1515484295.18448.9.camel@nic.cz> <20180109.090648.1082913423972100343.mbj@tail-f.com> <1515510536.26845.18.camel@nic.cz> <20180109.162311.49506989189385960.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/eEMbVcDLIjOjLBW4QpOlY4MdwuQ>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 16:08:29 -0000

On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka <lhotka@nic.cz> wrote:
> > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> 
> > > Hi,
> 
> > > 
> 
> > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> 
> > > > Hi Acee,
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > please see inline.
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> 
> > > 
> 
> > > > > Hi Lada,
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > Apologies for the delay. We somewhat got hung up on 4 and 6. See
> inline.
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > > Reviewer: Ladislav Lhotka
> 
> > > 
> 
> > > > > > Review result: Ready with Issues
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > ...
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > > > 
> 
> > > 
> 
> > > > > > 3. Maybe the draft could mention that implementations should supply
> a
> 
> > > 
> 
> > > > > >   default routing domain as a system-controlled resource.
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > Isnâ€™t this more of an RFC8022BIS statement? I guess we could state
> this as
> 
> > > 
> 
> > > > > an assumption.
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > Probably, but it is not a YANG issue, so I'd leave it to you routing
> folks
> 
> > > to
> 
> > > 
> 
> > > > decide.
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > >  
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > > 4. In "when" expressions, the module uses literal strings for
> 
> > > 
> 
> > > > > >   identities. This is known to be problematic, the XPath functions
> 
> > > 
> 
> > > > > >   derived-from() or derived-from-or-self() should be used instead.
> 
> > > 
> 
> > > > > 
> 
> > > 
> 
> > > > > Why is this problematic? Is it because the types can be extended?
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > That's one reason: derived identities should often also satisfy the
> 
> > > constraint.
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > But the more serious problem is that things like
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> 
> > > 
> 
> > > > 
> 
> > > 
> 
> > > > rely on plain string comparison that depends od the actual prefix used
> for
> 
> > > the
> 
> > > 
> 
> > > > "rt:type" value. For one, according to RFC 7951 the JSON encoding of
> this
> 
> > > value
> 
> > > 
> 
> > > > would be "ietf-ospf:ospfv3" so the above expression is always false. 
> 
> > > 
> 
> > > 
> 
> > > This is not correct; the when expression is not evaluated on the JSON
> 
> > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> 
> > > 
> 
> > >    The string value of a node of type "identityref" in a "must" or
> 
> > >    "when" XPath expression is the referred identity's qualified name
> 
> > >    with the prefix present.  If the referred identity is defined in an
> 
> > >    imported module, the prefix in the string value is the prefix defined
> 
> > >    in the corresponding "import" statement.  Otherwise, the prefix in
> 
> > >    the string value is the prefix for the current module.
> 
> > 
> 
> > This is weird, to say the least. The leafref instance may have an identity
> value
> 
> > that is defined in a module that (has to be implemented by the server but)
> 
> > needn't be imported in the module that contains the XPath expression. So I
> don't
> 
> > know what 'corresponding "import" statement' this paragraph is talking
> about.
> 
> 
> It has to import the module in order to give a prefix, which then can
> be used in the XPath expression.

In the XPath expression above, do you mean the "rt" prefix of "rt:type"? If so,
it is irrelevant for the string comparison, what's important is the *value* of
the "rt:type" instance, which can be an identity defined in a module that
needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:

   On a particular server, the valid values are further restricted to the set of
     identities defined in the modules implemented by the server.

> 
> > Also, potentially there can be a collision in prefixes and then this also
> breaks
> 
> > down.
> 
> 
> No, two modules cannot be imported with the same prefix.

I have to disagree. An identity derived from the "ietf-routing:control-protocol-
type" base identity can be defined in a module that is not imported anywhere. If
a server declares such a module as implemented, then "rt:type" may have this
value per sec. 9.10.2.

And, consequently, there may be two different modules with conflicting prefixes
defining identities that are derived from "ietf-routing:control-protocol-type". 

> 
> > A moral of the namespace/prefix story in XML was that relying of namespace
> 
> > prefixes having a particular value is a really bad idea. I know that the
> cited
> 
> > paragraph was intended to make such XPath string comparisons more
> deterministic,
> 
> > but it is also problematic and should be avoided if possible.
> 
> 
> Note that this prefix is under the control of the module designer
> writing the XPath expression.  The same identityref value might use a

No, it is not. The prefixes appear in instance data.

Lada

> different prefix in some other module.
> 
> 
> /martin
> 
> 
> 
> > 
> 
> > Lada
> 
> > 
> 
> > > 
> 
> > > So the equality test of the identityref is correct.
> 
> > > 
> 
> > > However, I agree that in most cases 'derived-from-or-self' should be
> 
> > > used, in order to handle derived identities.
> 
> > > 
> 
> > > 
> 
> > > /martin
> 
> > -- 
> 
> > Ladislav Lhotka
> 
> > Head, CZ.NIC Labs
> 
> > PGP Key ID: 0xB8F92B08A9F76C67
> 
> > 
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Tue Jan  9 09:00:31 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566EC12D885 for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 09:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 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, T_RP_MATCHES_RCVD=-0.01, 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
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 BFOCsLdngCVB for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 09:00:23 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8EE312D865 for <yang-doctors@ietf.org>; Tue,  9 Jan 2018 09:00:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5905; q=dns/txt; s=iport; t=1515517222; x=1516726822; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=hEE3WTASmmM+QfKe21zfuOfmmYueoYvp8cjsvqzyrbc=; b=XjZdpKzb0E15Z0+c+fncEM3kXCBylxMcFBexrRGEaJweMnqGNLvX0S/u NShGj98M59hqT96l/AUrH00EdjOx0WPRBOyy9pRiKdCJ72F9NQ5dxwmnT Lq0FrlSQfJYqRXRRj1Lur74ElAnmvNVPLBSRzPfIQT5Uxjo98kUah3tsN g=;
X-IronPort-AV: E=Sophos;i="5.46,336,1511827200";  d="scan'208";a="1311721"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jan 2018 17:00:21 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w09H0KAv018438; Tue, 9 Jan 2018 17:00:20 GMT
To: Martin Bjorklund <mbj@tail-f.com>
Cc: yang-doctors@ietf.org, mirkovac@cisco.com, jclarke@cisco.com, michelle.cotton@icann.org, sabrina.tanamal@iana.org, amanda.baber@iana.org
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <20180105.112745.1361263416991396812.mbj@tail-f.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <7aad99fd-7a29-d197-5e5c-67be7791fe5d@cisco.com>
Date: Tue, 9 Jan 2018 18:00:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180105.112745.1361263416991396812.mbj@tail-f.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/nvaWCm2aAZvnSgyCBrEfoeUXMjY>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 17:00:26 -0000

On 1/5/2018 11:27 AM, Martin Bjorklund wrote:
> Hi,
>
> Benoit Claise <bclaise@cisco.com> wrote:
>> Dear all,
>>
>> We can say that the RFC is the source of truth but devops people
>> "play" about YANG modules.
>> I'm trying to have a single source of truth for the repository of
>> RFC-produced YANG modules, while we have multiple ones now.
>>
>> IMO, it should be IANA.Â  We've discussing this option with RFC editor
>> and IANA:
>> https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml
>> is being transformed in that direction.
>> The end goal is that end users, wanted to be up-to-date with the
>> latest RFC-produced YANG modules, would perform a cron job such as:
>>  Â Â Â  rsync -avz --delete rsync.ietf.org::iana/yang-parameters .
>>
>> Note: especially interested for IANA-maintained YANG modules such as
>> iana-if-type
> Note that the IANA-maintained modules are already available there, e.g.:
>
>    http://www.iana.org/assignments/yang-parameters/iana-if-type@2017-03-30.yang
Sure. The point is that, in a local toolchain, if you don't get the most 
up-to-date IANA maintained YANG module, a YANG module that augment the 
latest assignment will produce an error. Been there, done that. So a 
rsync-like cronjob is required.
>
>> Now the follow-up question from IANA:
>>
>>     We were working on the posting of the yang modules for
>>     _draft-ietf-rtgwg-routing-types
>>     <https://datatracker.ietf.org/idtracker/draft-ietf-rtgwg-routing-types/>_
>>     per our new process.Â  When requesting the final files from the
>>     RFC-Editor, the file they extracted using their tool and the yang
>>     modules appear to have a lot of blank space in them.Â  See attached
>>
>>     Is this OK?Â  Do we post it as it is in the provided file from the
>>     RFC-Editor?Â  We know that there is some sensitivity to spacing in
>>     these files so we want to make sure the correct thing is being posted.
> I agree that the additional whitespace is an issue.  In the pyang
> repo, I store all IETF/IANA modules, and I first extract the modules
> then manually go through them to remove extra newlines.  Not ideal.
>
>> The solution should be: pyang -f yang ...
> You can do pyang -f yang --keep-comments ...  to keep comments.
>
> But I'm not sure that this is the correct solution.  I think the
> stored modules should look the same (not just be semantially
> equivalent) as the modules in the RFC.
>
> This said, we should encourage people to use consistent formatting,
> and run pyang -f yang or equivalent *before* putting the module into
> the RFC.
Ideally, yes, but I have no way to enforce that.
>
>> However, after some testing:
>>
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ pyang
>> -f yang iana-routing-types@2017-12-04.yang > newfile.yang
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$ diff
>> iana-routing-types@2017-12-04.yang newfile.yang
>> 16d15
>> <
>> 35,39c34,39
>> <Â Â Â  revision 2017-12-04 {
>> <Â Â Â Â Â  description "Initial revision.";
>> <Â Â Â Â Â  reference
>> <Â Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.
>> <Â Â Â Â Â Â Â Â  Section 4.";
>> ---
>>>  Â Â  revision 2017-12-04 {
>>>  Â Â Â Â  description
>>>  Â Â Â Â Â Â  "Initial revision.";
>>>  Â Â Â Â  reference
>>>  Â Â Â Â Â Â  "RFC 8294: Common YANG Data Types for the Routing Area.
>>>  Â Â Â Â Â Â Â  Section 4.";
>> 42,47d41
>> <
>> <
>> <
>> <Â Â  /*** Collection of IANA types related to routing ***/
>> <Â Â  /*** IANA Address Family enumeration ***/
>> <
>> 50c44
>> <Â Â Â Â Â Â  enum ipv4 {
>> ---
>>>  Â Â Â Â Â Â  enum "ipv4" {
> [...]
>
>> <Â Â Â Â Â Â  enum vpn-auto-discovery-safi {
>> ---
>>>  Â Â Â Â Â Â  enum "vpn-auto-discovery-safi" {
>> 485,486c398
>> <Â Â Â Â  reference
>> <Â Â Â Â Â Â  "RFC 4760: Multiprotocol Extensions for BGP-4.";
>> ---
>>>  Â Â Â Â  reference "RFC 4760: Multiprotocol Extensions for BGP-4.";
>> bclaise@bclaise-VirtualBox:/media/sf_ubuntu-share/toberemoved$
>>
>> pyang -f yang does more than the formatting, it adds double quotes to
>> enum, remove comments, and potentially does more (I don't know what I
>> don't know).
> It does a bunch of things considered "best practise" (use single
> quotes for XPath expressions, if possible for example), and it
> formats everything consistently wrt. whitespaces and quotes.
>
>> So here is the question: do we agree that the IANA, as source of truth
>> for YANG modules, should apply pyang -f format before posting a YANG
>> module?
> I don't think so, as I wrote above.  Ideally the author should somehow
> give the module to IANA, but then the problem is that the RFC editor
> often makes changes to the module, so we have a sync problem.  Extract
> and manually fix newlines is probably the best solution currently.
Well...
This doesn't work from a RFC editor process point of view. We need a 
clear procedure.
YANG doctors should not have to do that, but it could be recommended.
I will not fix line manually.
Educating all authors to do it will most likely not work, even if a 
RFC6087bis recommendation makes sense.

See next.

>
>> Bonus question: if the double quotes for enum is the best solution,
>> should it be a warning in validators?
> No.  The only reason pyang prints quotes around enums is that
> sometimes the quotes are needed, and thus it always prints them, for
> consistency.  I could certainly change this so that it prints q/o
> quotes in the normal case, and w/ quotes only if it is needed.
I believe the only option is around tooling, i.e. pyang that would only 
take care of the formatting.

	pyang -f yang --keep-comments --only-change-quotes-when-it-s-necessary

Or the reverse option: only-take-care-of-formatting

Regards, Benoit

>
>
> /martin
> .
>


From nobody Tue Jan  9 09:09:59 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEB10129966 for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 09:09:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 vrCvuTEj0EOk for <yang-doctors@ietfa.amsl.com>; Tue,  9 Jan 2018 09:09:55 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 501F8127871 for <yang-doctors@ietf.org>; Tue,  9 Jan 2018 09:09:55 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 1E3A4EFF; Tue,  9 Jan 2018 18:09:54 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id CHN7bWg7GUla; Tue,  9 Jan 2018 18:09:50 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Tue,  9 Jan 2018 18:09:54 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 063D22013D; Tue,  9 Jan 2018 18:09:54 +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 AmwYXi5TJOPO; Tue,  9 Jan 2018 18:09:53 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id BF6152013C; Tue,  9 Jan 2018 18:09:52 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 8C2C54208801; Tue,  9 Jan 2018 18:09:52 +0100 (CET)
Date: Tue, 9 Jan 2018 18:09:52 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, mirkovac@cisco.com, jclarke@cisco.com, sabrina.tanamal@iana.org, amanda.baber@iana.org, yang-doctors@ietf.org, michelle.cotton@icann.org
Message-ID: <20180109170952.rty7sly5ekirfzyp@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, Martin Bjorklund <mbj@tail-f.com>, mirkovac@cisco.com, jclarke@cisco.com, sabrina.tanamal@iana.org, amanda.baber@iana.org, yang-doctors@ietf.org, michelle.cotton@icann.org
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <20180105.112745.1361263416991396812.mbj@tail-f.com> <7aad99fd-7a29-d197-5e5c-67be7791fe5d@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7aad99fd-7a29-d197-5e5c-67be7791fe5d@cisco.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/UWBuQe5j66DmGRnLRc5Ujkt7nPU>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jan 2018 17:09:58 -0000

On Tue, Jan 09, 2018 at 06:00:20PM +0100, Benoit Claise wrote:
> > I don't think so, as I wrote above.  Ideally the author should somehow
> > give the module to IANA, but then the problem is that the RFC editor
> > often makes changes to the module, so we have a sync problem.  Extract
> > and manually fix newlines is probably the best solution currently.
> Well...
> This doesn't work from a RFC editor process point of view. We need a clear
> procedure.
> YANG doctors should not have to do that, but it could be recommended.
> I will not fix line manually.
> Educating all authors to do it will most likely not work, even if a
> RFC6087bis recommendation makes sense.

Look at RFC 6557 (BCP 175). They introduce the role of a TZ
Coordinator.  And then they post a versioned tar archive. (I am sure
the TZ maintainers have a version controlled repository somewhere but
this at the end does not matter.)

So the key is to find a volunteer "YANG Module Coordinator" and money
to invite him/her for a few beers or dinner.

/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/>


From nobody Wed Jan 10 01:36:26 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3804126B7F; Wed, 10 Jan 2018 01:36:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 GfLMLobHpLEB; Wed, 10 Jan 2018 01:36:12 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8E58E1241F8; Wed, 10 Jan 2018 01:36:12 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 4F3AE1AE0118; Wed, 10 Jan 2018 10:36:10 +0100 (CET)
Date: Wed, 10 Jan 2018 10:34:28 +0100 (CET)
Message-Id: <20180110.103428.251892557297447292.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: acee@cisco.com, yang-doctors@ietf.org, draft-ietf-ospf-yang.all@ietf.org, ietf@ietf.org, ospf@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1515514101.26845.52.camel@nic.cz>
References: <1515510536.26845.18.camel@nic.cz> <20180109.162311.49506989189385960.mbj@tail-f.com> <1515514101.26845.52.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/j9Zz4JORLGQuu7nsWEB_OKB38lU>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 09:36:15 -0000

SGksDQoNCkkgdGhpbmsgd2UgY2FuIGFncmVlIHRoYXQgdGhlIG1vZGVsIGluIHRoaXMgSS1EIHNo
b3VsZCB1c2UNCmRlcml2ZWQtZnJvbS1vci1zZWxmKCkgaW5zdGVhZCBvZiBzdHJpbmcgY29tcGFy
aXNvbiwgYW5kIGNvbmNsdWRlIHRoaXMNCmRpc2N1c3Npb24gaGVyZS4gIEkgc3VnZ2VzdCB0aGF0
IGlmIHdlIG5lZWQgdG8gZnVydGhlciBkaXNjdXNzIHRoZQ0KcmVwcmVzZW50YXRpb24gb2YgaWRl
bnRpdHlyZWZzLCB0aGVuIHdlIHN0YXJ0IGEgbmV3IHRocmVkIG9uIHRoZQ0KTkVUTU9EIE1MLg0K
DQoNCi9tYXJ0aW4NCg0KDQoNCkxhZGlzbGF2IExob3RrYSA8bGhvdGthQG5pYy5jej4gd3JvdGU6
DQo+IE9uIFR1ZSwgMjAxOC0wMS0wOSBhdCAxNjoyMyArMDEwMCwgTWFydGluIEJqb3JrbHVuZCB3
cm90ZToNCj4gPiBMYWRpc2xhdiBMaG90a2EgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KPiA+ID4g
T24gVHVlLCAyMDE4LTAxLTA5IGF0IDA5OjA2ICswMTAwLCBNYXJ0aW4gQmpvcmtsdW5kIHdyb3Rl
Og0KPiA+IA0KPiA+ID4gPiBIaSwNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+IExhZGlz
bGF2IExob3RrYSA8bGhvdGthQG5pYy5jej4gd3JvdGU6DQo+ID4gDQo+ID4gPiA+ID4gSGkgQWNl
ZSwNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+IA0KPiA+
IA0KPiA+ID4gPiA+IHBsZWFzZSBzZWUgaW5saW5lLg0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4g
PiA+ID4gPiANCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gT24gTW9uLCAyMDE4LTAx
LTA4IGF0IDE5OjI4ICswMDAwLCBBY2VlIExpbmRlbSAoYWNlZSkgd3JvdGU6DQo+ID4gDQo+ID4g
PiA+IA0KPiA+IA0KPiA+ID4gPiA+ID4gSGkgTGFkYSwNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+
ID4gPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiBBcG9sb2dpZXMg
Zm9yIHRoZSBkZWxheS4gV2Ugc29tZXdoYXQgZ290IGh1bmcgdXAgb24gNCBhbmQgNi4gU2VlDQo+
ID4gaW5saW5lLg0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiA+IA0KPiA+IA0KPiA+
ID4gPiANCj4gPiANCj4gPiA+ID4gPiA+IE9uIDEyLzYvMTcsIDY6MjYgQU0sICJMYWRpc2xhdiBM
aG90a2EiIDxsaG90a2FAbmljLmN6PiB3cm90ZToNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4g
PiA+ID4gPiANCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiA+IFJldmlld2VyOiBM
YWRpc2xhdiBMaG90a2ENCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiA+IFJldmll
dyByZXN1bHQ6IFJlYWR5IHdpdGggSXNzdWVzDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4g
PiA+IA0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiAuLi4NCj4gPiANCj4gPiA+ID4g
DQo+ID4gDQo+ID4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiA+ID4gPiAN
Cj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiA+IDMuIE1heWJlIHRoZSBkcmFmdCBj
b3VsZCBtZW50aW9uIHRoYXQgaW1wbGVtZW50YXRpb25zIHNob3VsZCBzdXBwbHkNCj4gPiBhDQo+
ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiA+ID4gPiAgIGRlZmF1bHQgcm91dGluZyBkb21h
aW4gYXMgYSBzeXN0ZW0tY29udHJvbGxlZCByZXNvdXJjZS4NCj4gPiANCj4gPiA+ID4gDQo+ID4g
DQo+ID4gPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiBJc27igJl0
IHRoaXMgbW9yZSBvZiBhbiBSRkM4MDIyQklTIHN0YXRlbWVudD8gSSBndWVzcyB3ZSBjb3VsZCBz
dGF0ZQ0KPiA+IHRoaXMgYXMNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiBhbiBh
c3N1bXB0aW9uLg0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiANCj4gPiANCj4gPiA+
ID4gDQo+ID4gDQo+ID4gPiA+ID4gUHJvYmFibHksIGJ1dCBpdCBpcyBub3QgYSBZQU5HIGlzc3Vl
LCBzbyBJJ2QgbGVhdmUgaXQgdG8geW91IHJvdXRpbmcNCj4gPiBmb2xrcw0KPiA+IA0KPiA+ID4g
PiB0bw0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiBkZWNpZGUuDQo+ID4gDQo+ID4g
PiA+IA0KPiA+IA0KPiA+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiA+
ICANCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gDQo+
ID4gDQo+ID4gPiA+ID4gPiA+IDQuIEluICJ3aGVuIiBleHByZXNzaW9ucywgdGhlIG1vZHVsZSB1
c2VzIGxpdGVyYWwgc3RyaW5ncyBmb3INCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4g
PiA+ICAgaWRlbnRpdGllcy4gVGhpcyBpcyBrbm93biB0byBiZSBwcm9ibGVtYXRpYywgdGhlIFhQ
YXRoIGZ1bmN0aW9ucw0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiA+ID4gICBkZXJp
dmVkLWZyb20oKSBvciBkZXJpdmVkLWZyb20tb3Itc2VsZigpIHNob3VsZCBiZSB1c2VkIGluc3Rl
YWQuDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+IA0K
PiA+IA0KPiA+ID4gPiA+ID4gV2h5IGlzIHRoaXMgcHJvYmxlbWF0aWM/IElzIGl0IGJlY2F1c2Ug
dGhlIHR5cGVzIGNhbiBiZSBleHRlbmRlZD8NCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+
ID4gDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiA+IFRoYXQncyBvbmUgcmVhc29uOiBk
ZXJpdmVkIGlkZW50aXRpZXMgc2hvdWxkIG9mdGVuIGFsc28gc2F0aXNmeSB0aGUNCj4gPiANCj4g
PiA+ID4gY29uc3RyYWludC4NCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gDQo+ID4g
DQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiA+IEJ1dCB0aGUgbW9yZSBzZXJpb3VzIHByb2JsZW0g
aXMgdGhhdCB0aGluZ3MgbGlrZQ0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gPiANCj4g
PiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gICAgIHdoZW4gIi4uLy4uLy4uLy4uLy4uLy4u
Ly4uL3J0OnR5cGUgPSAnb3NwZjpvc3BmdjMnIg0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+
ID4gPiANCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4gcmVseSBvbiBwbGFpbiBzdHJp
bmcgY29tcGFyaXNvbiB0aGF0IGRlcGVuZHMgb2QgdGhlIGFjdHVhbCBwcmVmaXggdXNlZA0KPiA+
IGZvcg0KPiA+IA0KPiA+ID4gPiB0aGUNCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+ID4g
InJ0OnR5cGUiIHZhbHVlLiBGb3Igb25lLCBhY2NvcmRpbmcgdG8gUkZDIDc5NTEgdGhlIEpTT04g
ZW5jb2Rpbmcgb2YNCj4gPiB0aGlzDQo+ID4gDQo+ID4gPiA+IHZhbHVlDQo+ID4gDQo+ID4gPiA+
IA0KPiA+IA0KPiA+ID4gPiA+IHdvdWxkIGJlICJpZXRmLW9zcGY6b3NwZnYzIiBzbyB0aGUgYWJv
dmUgZXhwcmVzc2lvbiBpcyBhbHdheXMgZmFsc2UuIA0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4g
PiA+ID4gDQo+ID4gDQo+ID4gPiA+IFRoaXMgaXMgbm90IGNvcnJlY3Q7IHRoZSB3aGVuIGV4cHJl
c3Npb24gaXMgbm90IGV2YWx1YXRlZCBvbiB0aGUgSlNPTg0KPiA+IA0KPiA+ID4gPiBlbmNvZGlu
Zy4gIFNlZSB0aGUgbGFzdCBwYXJhZ3JhcGggb2Ygc2VjdGlvbiA5LjEwLjMgaW4gUkZDIDc5NTA6
DQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiAgICBUaGUgc3RyaW5nIHZhbHVlIG9mIGEg
bm9kZSBvZiB0eXBlICJpZGVudGl0eXJlZiIgaW4gYSAibXVzdCIgb3INCj4gPiANCj4gPiA+ID4g
ICAgIndoZW4iIFhQYXRoIGV4cHJlc3Npb24gaXMgdGhlIHJlZmVycmVkIGlkZW50aXR5J3MgcXVh
bGlmaWVkIG5hbWUNCj4gPiANCj4gPiA+ID4gICAgd2l0aCB0aGUgcHJlZml4IHByZXNlbnQuICBJ
ZiB0aGUgcmVmZXJyZWQgaWRlbnRpdHkgaXMgZGVmaW5lZCBpbiBhbg0KPiA+IA0KPiA+ID4gPiAg
ICBpbXBvcnRlZCBtb2R1bGUsIHRoZSBwcmVmaXggaW4gdGhlIHN0cmluZyB2YWx1ZSBpcyB0aGUg
cHJlZml4IGRlZmluZWQNCj4gPiANCj4gPiA+ID4gICAgaW4gdGhlIGNvcnJlc3BvbmRpbmcgImlt
cG9ydCIgc3RhdGVtZW50LiAgT3RoZXJ3aXNlLCB0aGUgcHJlZml4IGluDQo+ID4gDQo+ID4gPiA+
ICAgIHRoZSBzdHJpbmcgdmFsdWUgaXMgdGhlIHByZWZpeCBmb3IgdGhlIGN1cnJlbnQgbW9kdWxl
Lg0KPiA+IA0KPiA+ID4gDQo+ID4gDQo+ID4gPiBUaGlzIGlzIHdlaXJkLCB0byBzYXkgdGhlIGxl
YXN0LiBUaGUgbGVhZnJlZiBpbnN0YW5jZSBtYXkgaGF2ZSBhbiBpZGVudGl0eQ0KPiA+IHZhbHVl
DQo+ID4gDQo+ID4gPiB0aGF0IGlzIGRlZmluZWQgaW4gYSBtb2R1bGUgdGhhdCAoaGFzIHRvIGJl
IGltcGxlbWVudGVkIGJ5IHRoZSBzZXJ2ZXIgYnV0KQ0KPiA+IA0KPiA+ID4gbmVlZG4ndCBiZSBp
bXBvcnRlZCBpbiB0aGUgbW9kdWxlIHRoYXQgY29udGFpbnMgdGhlIFhQYXRoIGV4cHJlc3Npb24u
IFNvIEkNCj4gPiBkb24ndA0KPiA+IA0KPiA+ID4ga25vdyB3aGF0ICdjb3JyZXNwb25kaW5nICJp
bXBvcnQiIHN0YXRlbWVudCcgdGhpcyBwYXJhZ3JhcGggaXMgdGFsa2luZw0KPiA+IGFib3V0Lg0K
PiA+IA0KPiA+IA0KPiA+IEl0IGhhcyB0byBpbXBvcnQgdGhlIG1vZHVsZSBpbiBvcmRlciB0byBn
aXZlIGEgcHJlZml4LCB3aGljaCB0aGVuIGNhbg0KPiA+IGJlIHVzZWQgaW4gdGhlIFhQYXRoIGV4
cHJlc3Npb24uDQo+IA0KPiBJbiB0aGUgWFBhdGggZXhwcmVzc2lvbiBhYm92ZSwgZG8geW91IG1l
YW4gdGhlICJydCIgcHJlZml4IG9mICJydDp0eXBlIj8gSWYgc28sDQo+IGl0IGlzIGlycmVsZXZh
bnQgZm9yIHRoZSBzdHJpbmcgY29tcGFyaXNvbiwgd2hhdCdzIGltcG9ydGFudCBpcyB0aGUgKnZh
bHVlKiBvZg0KPiB0aGUgInJ0OnR5cGUiIGluc3RhbmNlLCB3aGljaCBjYW4gYmUgYW4gaWRlbnRp
dHkgZGVmaW5lZCBpbiBhIG1vZHVsZSB0aGF0DQo+IG5lZWRuJ3QgYmUgaW1wb3J0ZWQgYnkgaWV0
Zi1yb3V0aW5nLCBpZXRmLW9zcGYgb3Igd2hhdGV2ZXIuIFNlYy4gOS4xMC4yOg0KPiANCj4gICAg
T24gYSBwYXJ0aWN1bGFyIHNlcnZlciwgdGhlIHZhbGlkIHZhbHVlcyBhcmUgZnVydGhlciByZXN0
cmljdGVkIHRvIHRoZSBzZXQgb2YNCj4gICAgICBpZGVudGl0aWVzIGRlZmluZWQgaW4gdGhlIG1v
ZHVsZXMgaW1wbGVtZW50ZWQgYnkgdGhlIHNlcnZlci4NCj4gDQo+ID4gDQo+ID4gPiBBbHNvLCBw
b3RlbnRpYWxseSB0aGVyZSBjYW4gYmUgYSBjb2xsaXNpb24gaW4gcHJlZml4ZXMgYW5kIHRoZW4g
dGhpcyBhbHNvDQo+ID4gYnJlYWtzDQo+ID4gDQo+ID4gPiBkb3duLg0KPiA+IA0KPiA+IA0KPiA+
IE5vLCB0d28gbW9kdWxlcyBjYW5ub3QgYmUgaW1wb3J0ZWQgd2l0aCB0aGUgc2FtZSBwcmVmaXgu
DQo+IA0KPiBJIGhhdmUgdG8gZGlzYWdyZWUuIEFuIGlkZW50aXR5IGRlcml2ZWQgZnJvbSB0aGUg
ImlldGYtcm91dGluZzpjb250cm9sLXByb3RvY29sLQ0KPiB0eXBlIiBiYXNlIGlkZW50aXR5IGNh
biBiZSBkZWZpbmVkIGluIGEgbW9kdWxlIHRoYXQgaXMgbm90IGltcG9ydGVkIGFueXdoZXJlLiBJ
Zg0KPiBhIHNlcnZlciBkZWNsYXJlcyBzdWNoIGEgbW9kdWxlIGFzIGltcGxlbWVudGVkLCB0aGVu
ICJydDp0eXBlIiBtYXkgaGF2ZSB0aGlzDQo+IHZhbHVlIHBlciBzZWMuIDkuMTAuMi4NCj4gDQo+
IEFuZCwgY29uc2VxdWVudGx5LCB0aGVyZSBtYXkgYmUgdHdvIGRpZmZlcmVudCBtb2R1bGVzIHdp
dGggY29uZmxpY3RpbmcgcHJlZml4ZXMNCj4gZGVmaW5pbmcgaWRlbnRpdGllcyB0aGF0IGFyZSBk
ZXJpdmVkIGZyb20gImlldGYtcm91dGluZzpjb250cm9sLXByb3RvY29sLXR5cGUiLiANCj4gDQo+
ID4gDQo+ID4gPiBBIG1vcmFsIG9mIHRoZSBuYW1lc3BhY2UvcHJlZml4IHN0b3J5IGluIFhNTCB3
YXMgdGhhdCByZWx5aW5nIG9mIG5hbWVzcGFjZQ0KPiA+IA0KPiA+ID4gcHJlZml4ZXMgaGF2aW5n
IGEgcGFydGljdWxhciB2YWx1ZSBpcyBhIHJlYWxseSBiYWQgaWRlYS4gSSBrbm93IHRoYXQgdGhl
DQo+ID4gY2l0ZWQNCj4gPiANCj4gPiA+IHBhcmFncmFwaCB3YXMgaW50ZW5kZWQgdG8gbWFrZSBz
dWNoIFhQYXRoIHN0cmluZyBjb21wYXJpc29ucyBtb3JlDQo+ID4gZGV0ZXJtaW5pc3RpYywNCj4g
PiANCj4gPiA+IGJ1dCBpdCBpcyBhbHNvIHByb2JsZW1hdGljIGFuZCBzaG91bGQgYmUgYXZvaWRl
ZCBpZiBwb3NzaWJsZS4NCj4gPiANCj4gPiANCj4gPiBOb3RlIHRoYXQgdGhpcyBwcmVmaXggaXMg
dW5kZXIgdGhlIGNvbnRyb2wgb2YgdGhlIG1vZHVsZSBkZXNpZ25lcg0KPiA+IHdyaXRpbmcgdGhl
IFhQYXRoIGV4cHJlc3Npb24uICBUaGUgc2FtZSBpZGVudGl0eXJlZiB2YWx1ZSBtaWdodCB1c2Ug
YQ0KPiANCj4gTm8sIGl0IGlzIG5vdC4gVGhlIHByZWZpeGVzIGFwcGVhciBpbiBpbnN0YW5jZSBk
YXRhLg0KPiANCj4gTGFkYQ0KPiANCj4gPiBkaWZmZXJlbnQgcHJlZml4IGluIHNvbWUgb3RoZXIg
bW9kdWxlLg0KPiA+IA0KPiA+IA0KPiA+IC9tYXJ0aW4NCj4gPiANCj4gPiANCj4gPiANCj4gPiA+
IA0KPiA+IA0KPiA+ID4gTGFkYQ0KPiA+IA0KPiA+ID4gDQo+ID4gDQo+ID4gPiA+IA0KPiA+IA0K
PiA+ID4gPiBTbyB0aGUgZXF1YWxpdHkgdGVzdCBvZiB0aGUgaWRlbnRpdHlyZWYgaXMgY29ycmVj
dC4NCj4gPiANCj4gPiA+ID4gDQo+ID4gDQo+ID4gPiA+IEhvd2V2ZXIsIEkgYWdyZWUgdGhhdCBp
biBtb3N0IGNhc2VzICdkZXJpdmVkLWZyb20tb3Itc2VsZicgc2hvdWxkIGJlDQo+ID4gDQo+ID4g
PiA+IHVzZWQsIGluIG9yZGVyIHRvIGhhbmRsZSBkZXJpdmVkIGlkZW50aXRpZXMuDQo+ID4gDQo+
ID4gPiA+IA0KPiA+IA0KPiA+ID4gPiANCj4gPiANCj4gPiA+ID4gL21hcnRpbg0KPiA+IA0KPiA+
ID4gLS0gDQo+ID4gDQo+ID4gPiBMYWRpc2xhdiBMaG90a2ENCj4gPiANCj4gPiA+IEhlYWQsIENa
Lk5JQyBMYWJzDQo+ID4gDQo+ID4gPiBQR1AgS2V5IElEOiAweEI4RjkyQjA4QTlGNzZDNjcNCj4g
PiANCj4gPiA+IA0KPiA+IA0KPiAtLSANCj4gTGFkaXNsYXYgTGhvdGthDQo+IEhlYWQsIENaLk5J
QyBMYWJzDQo+IFBHUCBLZXkgSUQ6IDB4QjhGOTJCMDhBOUY3NkM2Nw0KPiANCg==


From nobody Wed Jan 10 01:37:35 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6852C1270A0 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 01:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 x_Wq3MvgsB8Q for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 01:37:32 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id A4889127077 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 01:37:32 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 8862B1AE0118; Wed, 10 Jan 2018 10:37:31 +0100 (CET)
Date: Wed, 10 Jan 2018 10:35:50 +0100 (CET)
Message-Id: <20180110.103550.378781807177809788.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1515514101.26845.52.camel@nic.cz>
References: <1515510536.26845.18.camel@nic.cz> <20180109.162311.49506989189385960.mbj@tail-f.com> <1515514101.26845.52.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/atJFYaEmxOkdij17HBjPtybylJ0>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 09:37:34 -0000

Hi,

Replying to this only on yang-doctors, since this is mostly a
discussion about the interpretation of RFC 7950.


Ladislav Lhotka <lhotka@nic.cz> wrote:
> On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:

[...]

> > > > > > > 4. In "when" expressions, the module uses literal strings for
> > > > > > >   identities. This is known to be problematic, the XPath functions
> > > > > > >   derived-from() or derived-from-or-self() should be used instead.
> > > > > > >
> > > > > > Why is this problematic? Is it because the types can be extended?
> > > > > 
> > > > > That's one reason: derived identities should often also satisfy the
> > > > > constraint.
> > > > > 
> > > > > But the more serious problem is that things like
> > > > > 
> > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > > > 
> > > > > rely on plain string comparison that depends od the actual prefix used
> > > > 
> > > > > "rt:type" value. For one, according to RFC 7951 the JSON encoding of
> > > > > this value
> > > > > would be "ietf-ospf:ospfv3" so the above expression is always false. 
> > > > 
> > > > This is not correct; the when expression is not evaluated on the JSON
> > > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> > > > 
> > > >    The string value of a node of type "identityref" in a "must" or
> > > >    "when" XPath expression is the referred identity's qualified name
> > > >    with the prefix present.  If the referred identity is defined in an
> > > >    imported module, the prefix in the string value is the prefix defined
> > > >    in the corresponding "import" statement.  Otherwise, the prefix in
> > > >    the string value is the prefix for the current module.
> > > 
> > > This is weird, to say the least. The leafref instance may have an identity
> > > value
> > > that is defined in a module that (has to be implemented by the server but)
> > > needn't be imported in the module that contains the XPath expression. So I
> > > don't
> > > know what 'corresponding "import" statement' this paragraph is talking
> > > about.
> > 
> > It has to import the module in order to give a prefix, which then can
> > be used in the XPath expression.
> 
> In the XPath expression above, do you mean the "rt" prefix of
> "rt:type"?

No, I meant the "ospf" prefix for the module "ietf-ospf".

> If so,
> it is irrelevant for the string comparison, what's important is the *value* of
> the "rt:type" instance, which can be an identity defined in a module that
> needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:
> 
>    On a particular server, the valid values are further restricted
>    to the set of identities defined in the modules implemented by
>    the server.

Because of the way the representation of identities work in must/when
expressions, you *must* import the module where the identity is
define, if you want to use the identity for equality comparision like
in the example.

You may have:

  module a {
    ...
    import ietf-ospf {
      prefix x;
    }
    ...
    leaf foo {
      when "../type = 'x:ospfv3'";
      ...
    }
  }

and

  module b {
    ...
    import ietf-ospf {
      prefix y;
    }
    ...
    leaf bar {
      when "../type = 'y:ospfv3'";
      ...
    }
  }

You may not like it, but these two modules are both correct according
to the rules defined in RFC 7950.  The string value of the "type" leaf
*when evaluating the when expression* is different in the different
modules.  See the last paragraph of section 9.10.3 in RFC 7950.
    
> > > Also, potentially there can be a collision in prefixes and then this also
> > > breaks down.
> > 
> > 
> > No, two modules cannot be imported with the same prefix.
> 
> I have to disagree. An identity derived from the
> "ietf-routing:control-protocol-type" base identity can be defined
> in a module that is not imported anywhere. If a server declares such
> a module as implemented, then "rt:type" may have this value per
> sec. 9.10.2.
> 
> And, consequently, there may be two different modules with
> conflicting prefixes defining identities that are derived from
> "ietf-routing:control-protocol-type".

Sure, but this is not the point.

> > > A moral of the namespace/prefix story in XML was that relying of
> > > namespace prefixes having a particular value is a really bad
> > > idea. I know that the cited paragraph was intended to make such
> > > XPath string comparisons more deterministic, but it is also
> > > problematic and should be avoided if possible.
> > 
> > Note that this prefix is under the control of the module designer
> > writing the XPath expression.  The same identityref value might use a
> 
> No, it is not. The prefixes appear in instance data.

The prefix *in the when expression* is under the control of the module
designer, as explained above.

You are correct that the prefix in an XML encoding is not under
control of the module designer, but noone has claimed that.

I agree that it is unfortunate that context-specific prefixes are used
for the identityref values.  It would have been better if we used a
context free representation, e.g. "<module-name>:<identity>".  But
that's another discussion.



/martin


From nobody Wed Jan 10 02:17:56 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79E65124D85 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 02:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 BJcj9j5DCKOz for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 02:17:52 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 C9C6C1205F1 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 02:17:51 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id AB3D262636; Wed, 10 Jan 2018 11:17:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1515579468; bh=Ke50Oxqqwx+w9WEZsn69cNvA9wyXzQXprOWMAgkpvuU=; h=From:To:Date; b=KIqRjb23JfdEMb8Ip1QuKSXn4EbWiZXWFF+6jRmKtUoGQ6XMR7pJmhZpqXT6zD8uW TNk84gzE9R+Ppakl4j1lB6HHRaSVyI9Q64rnb0rvmpyBfjvagCGtgKi3BrSTITfNtI kLtKWw41EIgYjblqKBswvjF+ZkrQ4kV5SYTEY5GU=
Message-ID: <1515579468.6095.29.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: yang-doctors@ietf.org
Date: Wed, 10 Jan 2018 11:17:48 +0100
In-Reply-To: <20180110.103550.378781807177809788.mbj@tail-f.com>
References: <1515510536.26845.18.camel@nic.cz> <20180109.162311.49506989189385960.mbj@tail-f.com> <1515514101.26845.52.camel@nic.cz> <20180110.103550.378781807177809788.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/vqRMc6ZJXFXgD1lvpfKdc7d-3ng>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 10:17:55 -0000

On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> Hi,
> 
> Replying to this only on yang-doctors, since this is mostly a
> discussion about the interpretation of RFC 7950.
> 
> 
> Ladislav Lhotka <lhotka@nic.cz> wrote:
> > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> 
> [...]
> 
> > > > > > > > 4. In "when" expressions, the module uses literal strings for
> > > > > > > >   identities. This is known to be problematic, the XPath
> functions
> > > > > > > >   derived-from() or derived-from-or-self() should be used
> instead.
> > > > > > > >
> > > > > > > Why is this problematic? Is it because the types can be extended?
> > > > > > 
> > > > > > That's one reason: derived identities should often also satisfy the
> > > > > > constraint.
> > > > > > 
> > > > > > But the more serious problem is that things like
> > > > > > 
> > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > > > > 
> > > > > > rely on plain string comparison that depends od the actual prefix
> used
> > > > > 
> > > > > > "rt:type" value. For one, according to RFC 7951 the JSON encoding of
> > > > > > this value
> > > > > > would be "ietf-ospf:ospfv3" so the above expression is always
> false. 
> > > > > 
> > > > > This is not correct; the when expression is not evaluated on the JSON
> > > > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> > > > > 
> > > > >    The string value of a node of type "identityref" in a "must" or
> > > > >    "when" XPath expression is the referred identity's qualified name
> > > > >    with the prefix present.  If the referred identity is defined in an
> > > > >    imported module, the prefix in the string value is the prefix
> defined
> > > > >    in the corresponding "import" statement.  Otherwise, the prefix in
> > > > >    the string value is the prefix for the current module.
> > > > 
> > > > This is weird, to say the least. The leafref instance may have an
> identity
> > > > value
> > > > that is defined in a module that (has to be implemented by the server
> but)
> > > > needn't be imported in the module that contains the XPath expression. So
> I
> > > > don't
> > > > know what 'corresponding "import" statement' this paragraph is talking
> > > > about.
> > > 
> > > It has to import the module in order to give a prefix, which then can
> > > be used in the XPath expression.
> > 
> > In the XPath expression above, do you mean the "rt" prefix of
> > "rt:type"?
> 
> No, I meant the "ospf" prefix for the module "ietf-ospf".
> 
> > If so,
> > it is irrelevant for the string comparison, what's important is the *value*
> of
> > the "rt:type" instance, which can be an identity defined in a module that
> > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:
> > 
> >    On a particular server, the valid values are further restricted
> >    to the set of identities defined in the modules implemented by
> >    the server.
> 
> Because of the way the representation of identities work in must/when
> expressions, you *must* import the module where the identity is
> define, if you want to use the identity for equality comparision like
> in the example.
> 
> You may have:
> 
>   module a {
>     ...
>     import ietf-ospf {
>       prefix x;
>     }
>     ...
>     leaf foo {
>       when "../type = 'x:ospfv3'";
>       ...
>     }
>   }

The problem here is not with the literal 'x:ospf' but rather with the string
value of the leafref node instance ("../type" here), and clearly it is what sec.
9.10.3 talks about ("string value of a [leafref] node").

I can define a module like

module foo-ospf {
  namespace "http://example.com/foo-ospf";
  prefix ospf;
  import ietf-routing {
    prefix rt;
  }
  identity ospfv3 {
    base "rt:routing-protocol";
  }
  ...
}

Now, if the server advertizes both ietf-ospf and foo-ospf as implemented (which
is legal), the module foo-ospf needn't be imported anywhere and still the "type"
leaf instance can have both values "ietf-ospf:ospfv3" and "foo-ospf:ospfv3",
provided that it is defined as

leaf type {
  type identityref {
    base rt:routing-protocol;
  }
}

And I wonder what the last paragraph in sec. 9.10.3 means in this situation,
i.e. what string value of "type" is used in the evaluation of the XPath
expression in your module "a", if the value-space value of 'type' instance in a
datastore is either of the two '...:ospfv3' identities.

Do you see what I mean?

Lada 
  

> 
> and
> 
>   module b {
>     ...
>     import ietf-ospf {
>       prefix y;
>     }
>     ...
>     leaf bar {
>       when "../type = 'y:ospfv3'";
>       ...
>     }
>   }
> 
> You may not like it, but these two modules are both correct according
> to the rules defined in RFC 7950.  The string value of the "type" leaf
> *when evaluating the when expression* is different in the different
> modules.  See the last paragraph of section 9.10.3 in RFC 7950.
>     
> > > > Also, potentially there can be a collision in prefixes and then this
> also
> > > > breaks down.
> > > 
> > > 
> > > No, two modules cannot be imported with the same prefix.
> > 
> > I have to disagree. An identity derived from the
> > "ietf-routing:control-protocol-type" base identity can be defined
> > in a module that is not imported anywhere. If a server declares such
> > a module as implemented, then "rt:type" may have this value per
> > sec. 9.10.2.
> > 
> > And, consequently, there may be two different modules with
> > conflicting prefixes defining identities that are derived from
> > "ietf-routing:control-protocol-type".
> 
> Sure, but this is not the point.
> 
> > > > A moral of the namespace/prefix story in XML was that relying of
> > > > namespace prefixes having a particular value is a really bad
> > > > idea. I know that the cited paragraph was intended to make such
> > > > XPath string comparisons more deterministic, but it is also
> > > > problematic and should be avoided if possible.
> > > 
> > > Note that this prefix is under the control of the module designer
> > > writing the XPath expression.  The same identityref value might use a
> > 
> > No, it is not. The prefixes appear in instance data.
> 
> The prefix *in the when expression* is under the control of the module
> designer, as explained above.
> 
> You are correct that the prefix in an XML encoding is not under
> control of the module designer, but noone has claimed that.
> 
> I agree that it is unfortunate that context-specific prefixes are used
> for the identityref values.  It would have been better if we used a
> context free representation, e.g. "<module-name>:<identity>".  But
> that's another discussion.
> 
> 
> 
> /martin
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Wed Jan 10 04:00:36 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8172E126DFF for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 04:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 bnxUWgJ7cG9A for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 04:00:28 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB1C1200B9 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 04:00:28 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 4D44F1AE0118; Wed, 10 Jan 2018 13:00:23 +0100 (CET)
Date: Wed, 10 Jan 2018 12:58:41 +0100 (CET)
Message-Id: <20180110.125841.1275902835172392300.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1515579468.6095.29.camel@nic.cz>
References: <1515514101.26845.52.camel@nic.cz> <20180110.103550.378781807177809788.mbj@tail-f.com> <1515579468.6095.29.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/C95EH05Xt6uVrE_dDhSBCSpEC2A>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 12:00:35 -0000

Ladislav Lhotka <lhotka@nic.cz> wrote:
> On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> > Hi,
> > 
> > Replying to this only on yang-doctors, since this is mostly a
> > discussion about the interpretation of RFC 7950.
> > 
> > 
> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> > 
> > [...]
> > 
> > > > > > > > > 4. In "when" expressions, the module uses literal strings for
> > > > > > > > >   identities. This is known to be problematic, the XPath
> > functions
> > > > > > > > >   derived-from() or derived-from-or-self() should be used
> > instead.
> > > > > > > > >
> > > > > > > > Why is this problematic? Is it because the types can be extended?
> > > > > > > 
> > > > > > > That's one reason: derived identities should often also satisfy the
> > > > > > > constraint.
> > > > > > > 
> > > > > > > But the more serious problem is that things like
> > > > > > > 
> > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > > > > > 
> > > > > > > rely on plain string comparison that depends od the actual prefix
> > used
> > > > > > 
> > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON encoding of
> > > > > > > this value
> > > > > > > would be "ietf-ospf:ospfv3" so the above expression is always
> > false. 
> > > > > > 
> > > > > > This is not correct; the when expression is not evaluated on the JSON
> > > > > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> > > > > > 
> > > > > >    The string value of a node of type "identityref" in a "must" or
> > > > > >    "when" XPath expression is the referred identity's qualified name
> > > > > >    with the prefix present.  If the referred identity is defined in an
> > > > > >    imported module, the prefix in the string value is the prefix
> > defined
> > > > > >    in the corresponding "import" statement.  Otherwise, the prefix in
> > > > > >    the string value is the prefix for the current module.
> > > > > 
> > > > > This is weird, to say the least. The leafref instance may have an
> > identity
> > > > > value
> > > > > that is defined in a module that (has to be implemented by the server
> > but)
> > > > > needn't be imported in the module that contains the XPath expression. So
> > I
> > > > > don't
> > > > > know what 'corresponding "import" statement' this paragraph is talking
> > > > > about.
> > > > 
> > > > It has to import the module in order to give a prefix, which then can
> > > > be used in the XPath expression.
> > > 
> > > In the XPath expression above, do you mean the "rt" prefix of
> > > "rt:type"?
> > 
> > No, I meant the "ospf" prefix for the module "ietf-ospf".
> > 
> > > If so,
> > > it is irrelevant for the string comparison, what's important is the *value*
> > of
> > > the "rt:type" instance, which can be an identity defined in a module that
> > > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:
> > > 
> > >    On a particular server, the valid values are further restricted
> > >    to the set of identities defined in the modules implemented by
> > >    the server.
> > 
> > Because of the way the representation of identities work in must/when
> > expressions, you *must* import the module where the identity is
> > define, if you want to use the identity for equality comparision like
> > in the example.
> > 
> > You may have:
> > 
> >   module a {
> >     ...
> >     import ietf-ospf {
> >       prefix x;
> >     }
> >     ...
> >     leaf foo {
> >       when "../type = 'x:ospfv3'";
> >       ...
> >     }
> >   }
> 
> The problem here is not with the literal 'x:ospf' but rather with the string
> value of the leafref node instance ("../type" here), and clearly it is what sec.
> 9.10.3 talks about ("string value of a [leafref] node").
> 
> I can define a module like
> 
> module foo-ospf {
>   namespace "http://example.com/foo-ospf";
>   prefix ospf;
>   import ietf-routing {
>     prefix rt;
>   }
>   identity ospfv3 {
>     base "rt:routing-protocol";
>   }
>   ...
> }
> 
> Now, if the server advertizes both ietf-ospf and foo-ospf as implemented (which
> is legal), the module foo-ospf needn't be imported anywhere and still the "type"
> leaf instance can have both values "ietf-ospf:ospfv3" and "foo-ospf:ospfv3",
> provided that it is defined as
> 
> leaf type {
>   type identityref {
>     base rt:routing-protocol;
>   }
> }
> 
> And I wonder what the last paragraph in sec. 9.10.3 means in this situation,
> i.e. what string value of "type" is used in the evaluation of the XPath
> expression in your module "a", if the value-space value of 'type' instance in a
> datastore is either of the two '...:ospfv3' identities.
> 
> Do you see what I mean?

Do you mean that the problem is that the spec does not define what the
string value is if the module where the identity is defined is not
imported?

I agree that this is an issue.

BUT, actually, if you look the text in the spec:

   The string value of a node of type "identityref" in a "must" or
   "when" XPath expression is the referred identity's qualified name
   with the prefix present.  If the referred identity is defined in an
   imported module, the prefix in the string value is the prefix defined
   in the corresponding "import" statement.  Otherwise, the prefix in
   the string value is the prefix for the current module.

If you blindly follow this, the last sentence would have to apply, and
the string would be "a:ospfv3", which clearly is broken.

For all practical purposes, I think the string value can be "" if the
identity is defined in a module that is not imported, and is not
defined in the current module.


/martin




> 
> Lada 
>   
> 
> > 
> > and
> > 
> >   module b {
> >     ...
> >     import ietf-ospf {
> >       prefix y;
> >     }
> >     ...
> >     leaf bar {
> >       when "../type = 'y:ospfv3'";
> >       ...
> >     }
> >   }
> > 
> > You may not like it, but these two modules are both correct according
> > to the rules defined in RFC 7950.  The string value of the "type" leaf
> > *when evaluating the when expression* is different in the different
> > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> >     
> > > > > Also, potentially there can be a collision in prefixes and then this
> > also
> > > > > breaks down.
> > > > 
> > > > 
> > > > No, two modules cannot be imported with the same prefix.
> > > 
> > > I have to disagree. An identity derived from the
> > > "ietf-routing:control-protocol-type" base identity can be defined
> > > in a module that is not imported anywhere. If a server declares such
> > > a module as implemented, then "rt:type" may have this value per
> > > sec. 9.10.2.
> > > 
> > > And, consequently, there may be two different modules with
> > > conflicting prefixes defining identities that are derived from
> > > "ietf-routing:control-protocol-type".
> > 
> > Sure, but this is not the point.
> > 
> > > > > A moral of the namespace/prefix story in XML was that relying of
> > > > > namespace prefixes having a particular value is a really bad
> > > > > idea. I know that the cited paragraph was intended to make such
> > > > > XPath string comparisons more deterministic, but it is also
> > > > > problematic and should be avoided if possible.
> > > > 
> > > > Note that this prefix is under the control of the module designer
> > > > writing the XPath expression.  The same identityref value might use a
> > > 
> > > No, it is not. The prefixes appear in instance data.
> > 
> > The prefix *in the when expression* is under the control of the module
> > designer, as explained above.
> > 
> > You are correct that the prefix in an XML encoding is not under
> > control of the module designer, but noone has claimed that.
> > 
> > I agree that it is unfortunate that context-specific prefixes are used
> > for the identityref values.  It would have been better if we used a
> > context free representation, e.g. "<module-name>:<identity>".  But
> > that's another discussion.
> > 
> > 
> > 
> > /martin
> -- 
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 


From nobody Wed Jan 10 05:10:18 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0B67124234 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 05:10:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, 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
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 52l1mV9PfRXq for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 05:10:15 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C712B12420B for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 05:10:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1266; q=dns/txt; s=iport; t=1515589815; x=1516799415; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=5t11in4l84ZbaoiE7o//YzOroc49tCqoN6c32xvFLNY=; b=j6sDzmyNi2LpyYewDvlDZCA/7M5Ylr3IiAMf6Niw4fyNYrEf0NZBBBz+ Xx+9qXDfwr87T2jK7y/QDJANa0Yv2t6xlIfSlLQ9BrPxpEppwbE/rbINV by6bWCGI869b8y0qO9R0rxEBh1gbjaQBbVi4SvGkZ2M9U5vhwCFNWPrrF w=;
X-IronPort-AV: E=Sophos;i="5.46,340,1511827200";  d="scan'208";a="1323727"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 13:10:13 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0ADACWd028347; Wed, 10 Jan 2018 13:10:12 GMT
To: Martin Bjorklund <mbj@tail-f.com>, mirkovac@cisco.com, jclarke@cisco.com,  sabrina.tanamal@iana.org, amanda.baber@iana.org, yang-doctors@ietf.org, michelle.cotton@icann.org
References: <ac8345fb-5cd5-dc76-6b96-b5f57a62d53a@cisco.com> <20180105.112745.1361263416991396812.mbj@tail-f.com> <7aad99fd-7a29-d197-5e5c-67be7791fe5d@cisco.com> <20180109170952.rty7sly5ekirfzyp@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <9c39f08d-b373-c256-b8ca-5710eed49fca@cisco.com>
Date: Wed, 10 Jan 2018 14:10:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180109170952.rty7sly5ekirfzyp@elstar.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/9mNqzaExGVgd1mtIiIHccGXAq34>
Subject: Re: [yang-doctors] YANG module & pyang -f yang & source of truth repository
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 13:10:17 -0000

On 1/9/2018 6:09 PM, Juergen Schoenwaelder wrote:
> On Tue, Jan 09, 2018 at 06:00:20PM +0100, Benoit Claise wrote:
>>> I don't think so, as I wrote above.  Ideally the author should somehow
>>> give the module to IANA, but then the problem is that the RFC editor
>>> often makes changes to the module, so we have a sync problem.  Extract
>>> and manually fix newlines is probably the best solution currently.
>> Well...
>> This doesn't work from a RFC editor process point of view. We need a clear
>> procedure.
>> YANG doctors should not have to do that, but it could be recommended.
>> I will not fix line manually.
>> Educating all authors to do it will most likely not work, even if a
>> RFC6087bis recommendation makes sense.
> Look at RFC 6557 (BCP 175). They introduce the role of a TZ
> Coordinator.  And then they post a versioned tar archive. (I am sure
> the TZ maintainers have a version controlled repository somewhere but
> this at the end does not matter.)
>
> So the key is to find a volunteer "YANG Module Coordinator" and money
> to invite him/her for a few beers or dinner.
Do I feel (a start of) a sense of potential ownership on your side, 
assuming I would provide the beers or dinner? :-)

Regards, Benoit
>
> /js
>


From nobody Wed Jan 10 08:06:33 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 430F812D94C for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 08:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 Ch-lQj0N_ero for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 08:06:29 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 37B8612D949 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 08:06:26 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id 8D1D262ED6 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 17:06:24 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1515600384; bh=FNJh4u7+XUPvE4gQgsQbzseO/+x+AcPoxGuMveGqhlI=; h=From:To:Date; b=YsCv0u4128BzYWFIc4MjdgCC54uvFMYF3YRBvPahHjQn6uvo1Qa1rru3N+kqsQflE AAQjzzdB1O+8tyET/QTTwdfWxMcj64sTWX0JPOY07ri7fjHbyfaPVErzy4l73CyjMb xF1je9LNwylSqm3tTEJ7JPsB7oSDpPuTHpgRZiy8=
Message-ID: <1515600384.11767.48.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Benoit Claise <yang-doctors@ietf.org>
Date: Wed, 10 Jan 2018 17:06:24 +0100
In-Reply-To: <20180110.125841.1275902835172392300.mbj@tail-f.com>
References: <1515514101.26845.52.camel@nic.cz> <20180110.103550.378781807177809788.mbj@tail-f.com> <1515579468.6095.29.camel@nic.cz> <20180110.125841.1275902835172392300.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.3 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/cQCOH5DoSMv2Nxlln5UNy_zmSRY>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 16:06:32 -0000

On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka <lhotka@nic.cz> wrote:
> > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> > > Hi,
> > > 
> > > Replying to this only on yang-doctors, since this is mostly a
> > > discussion about the interpretation of RFC 7950.
> > > 
> > > 
> > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> > > 
> > > [...]
> > > 
> > > > > > > > > > 4. In "when" expressions, the module uses literal strings
> 
> for
> > > > > > > > > >   identities. This is known to be problematic, the XPath
> > > 
> > > functions
> > > > > > > > > >   derived-from() or derived-from-or-self() should be used
> > > 
> > > instead.
> > > > > > > > > > 
> > > > > > > > > 
> > > > > > > > > Why is this problematic? Is it because the types can be
> 
> extended?
> > > > > > > > 
> > > > > > > > That's one reason: derived identities should often also satisfy
> 
> the
> > > > > > > > constraint.
> > > > > > > > 
> > > > > > > > But the more serious problem is that things like
> > > > > > > > 
> > > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > > > > > > 
> > > > > > > > rely on plain string comparison that depends od the actual
> 
> prefix
> > > used
> > > > > > > 
> > > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON
> 
> encoding of
> > > > > > > > this value
> > > > > > > > would be "ietf-ospf:ospfv3" so the above expression is always
> > > 
> > > false. 
> > > > > > > 
> > > > > > > This is not correct; the when expression is not evaluated on the
> 
> JSON
> > > > > > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> > > > > > > 
> > > > > > >    The string value of a node of type "identityref" in a "must" or
> > > > > > >    "when" XPath expression is the referred identity's qualified
> 
> name
> > > > > > >    with the prefix present.  If the referred identity is defined
> 
> in an
> > > > > > >    imported module, the prefix in the string value is the prefix
> > > 
> > > defined
> > > > > > >    in the corresponding "import" statement.  Otherwise, the prefix
> 
> in
> > > > > > >    the string value is the prefix for the current module.
> > > > > > 
> > > > > > This is weird, to say the least. The leafref instance may have an
> > > 
> > > identity
> > > > > > value
> > > > > > that is defined in a module that (has to be implemented by the
> 
> server
> > > but)
> > > > > > needn't be imported in the module that contains the XPath
> 
> expression. So
> > > I
> > > > > > don't
> > > > > > know what 'corresponding "import" statement' this paragraph is
> 
> talking
> > > > > > about.
> > > > > 
> > > > > It has to import the module in order to give a prefix, which then can
> > > > > be used in the XPath expression.
> > > > 
> > > > In the XPath expression above, do you mean the "rt" prefix of
> > > > "rt:type"?
> > > 
> > > No, I meant the "ospf" prefix for the module "ietf-ospf".
> > > 
> > > > If so,
> > > > it is irrelevant for the string comparison, what's important is the
> 
> *value*
> > > of
> > > > the "rt:type" instance, which can be an identity defined in a module
> 
> that
> > > > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:
> > > > 
> > > >    On a particular server, the valid values are further restricted
> > > >    to the set of identities defined in the modules implemented by
> > > >    the server.
> > > 
> > > Because of the way the representation of identities work in must/when
> > > expressions, you *must* import the module where the identity is
> > > define, if you want to use the identity for equality comparision like
> > > in the example.
> > > 
> > > You may have:
> > > 
> > >   module a {
> > >     ...
> > >     import ietf-ospf {
> > >       prefix x;
> > >     }
> > >     ...
> > >     leaf foo {
> > >       when "../type = 'x:ospfv3'";
> > >       ...
> > >     }
> > >   }
> > 
> > The problem here is not with the literal 'x:ospf' but rather with the string
> > value of the leafref node instance ("../type" here), and clearly it is what
> 
> sec.
> > 9.10.3 talks about ("string value of a [leafref] node").
> > 
> > I can define a module like
> > 
> > module foo-ospf {
> >   namespace "http://example.com/foo-ospf";
> >   prefix ospf;
> >   import ietf-routing {
> >     prefix rt;
> >   }
> >   identity ospfv3 {
> >     base "rt:routing-protocol";
> >   }
> >   ...
> > }
> > 
> > Now, if the server advertizes both ietf-ospf and foo-ospf as implemented
> 
> (which
> > is legal), the module foo-ospf needn't be imported anywhere and still the
> 
> "type"
> > leaf instance can have both values "ietf-ospf:ospfv3" and "foo-ospf:ospfv3",
> > provided that it is defined as
> > 
> > leaf type {
> >   type identityref {
> >     base rt:routing-protocol;
> >   }
> > }
> > 
> > And I wonder what the last paragraph in sec. 9.10.3 means in this situation,
> > i.e. what string value of "type" is used in the evaluation of the XPath
> > expression in your module "a", if the value-space value of 'type' instance
> 
> in a
> > datastore is either of the two '...:ospfv3' identities.
> > 
> > Do you see what I mean?
> 
> Do you mean that the problem is that the spec does not define what the
> string value is if the module where the identity is defined is not
> imported?
> 
> I agree that this is an issue.
> 
> BUT, actually, if you look the text in the spec:
> 
>    The string value of a node of type "identityref" in a "must" or
>    "when" XPath expression is the referred identity's qualified name
>    with the prefix present.  If the referred identity is defined in an
>    imported module, the prefix in the string value is the prefix defined
>    in the corresponding "import" statement.  Otherwise, the prefix in
>    the string value is the prefix for the current module.
> 
> If you blindly follow this, the last sentence would have to apply, and
> the string would be "a:ospfv3", which clearly is broken.

It depends on what "current module" means. It could also be interpreted as the
module in which the identity is defined, but then we can get the collision of
prefixes as in my example.

> 
> For all practical purposes, I think the string value can be "" if the
> identity is defined in a module that is not imported, and is not
> defined in the current module.

I think a better solution would be to avoid prefixes in lexical-space identity
values altogether and use the same string as in JSON encoding (RFC 7951). The
XPath expression from your example would become

    "../type = 'ietf-ospf:ospfv3'"

Everything would then be straightforward and non-ambiguous.

Lada

> 
> 
> /martin
> 
> 
> 
> 
> > 
> > Lada 
> >   
> > 
> > > 
> > > and
> > > 
> > >   module b {
> > >     ...
> > >     import ietf-ospf {
> > >       prefix y;
> > >     }
> > >     ...
> > >     leaf bar {
> > >       when "../type = 'y:ospfv3'";
> > >       ...
> > >     }
> > >   }
> > > 
> > > You may not like it, but these two modules are both correct according
> > > to the rules defined in RFC 7950.  The string value of the "type" leaf
> > > *when evaluating the when expression* is different in the different
> > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> > >     
> > > > > > Also, potentially there can be a collision in prefixes and then this
> > > 
> > > also
> > > > > > breaks down.
> > > > > 
> > > > > 
> > > > > No, two modules cannot be imported with the same prefix.
> > > > 
> > > > I have to disagree. An identity derived from the
> > > > "ietf-routing:control-protocol-type" base identity can be defined
> > > > in a module that is not imported anywhere. If a server declares such
> > > > a module as implemented, then "rt:type" may have this value per
> > > > sec. 9.10.2.
> > > > 
> > > > And, consequently, there may be two different modules with
> > > > conflicting prefixes defining identities that are derived from
> > > > "ietf-routing:control-protocol-type".
> > > 
> > > Sure, but this is not the point.
> > > 
> > > > > > A moral of the namespace/prefix story in XML was that relying of
> > > > > > namespace prefixes having a particular value is a really bad
> > > > > > idea. I know that the cited paragraph was intended to make such
> > > > > > XPath string comparisons more deterministic, but it is also
> > > > > > problematic and should be avoided if possible.
> > > > > 
> > > > > Note that this prefix is under the control of the module designer
> > > > > writing the XPath expression.  The same identityref value might use a
> > > > 
> > > > No, it is not. The prefixes appear in instance data.
> > > 
> > > The prefix *in the when expression* is under the control of the module
> > > designer, as explained above.
> > > 
> > > You are correct that the prefix in an XML encoding is not under
> > > control of the module designer, but noone has claimed that.
> > > 
> > > I agree that it is unfortunate that context-specific prefixes are used
> > > for the identityref values.  It would have been better if we used a
> > > context free representation, e.g. "<module-name>:<identity>".  But
> > > that's another discussion.
> > > 
> > > 
> > > 
> > > /martin
> > 
> > -- 
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> > 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Wed Jan 10 08:18:19 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6077712D945 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 08:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 VWi2VYuXxYjP for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 08:18:14 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id D5E3E12421A for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 08:18:13 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 3C5B51AE0118; Wed, 10 Jan 2018 17:18:12 +0100 (CET)
Date: Wed, 10 Jan 2018 17:18:11 +0100 (CET)
Message-Id: <20180110.171811.858477092972700390.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1515600384.11767.48.camel@nic.cz>
References: <1515579468.6095.29.camel@nic.cz> <20180110.125841.1275902835172392300.mbj@tail-f.com> <1515600384.11767.48.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/aoSGgNFp6Nov4adJoCcE_r7VCeE>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 16:18:17 -0000

Ladislav Lhotka <lhotka@nic.cz> wrote:
> On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> > > > Hi,
> > > > 
> > > > Replying to this only on yang-doctors, since this is mostly a
> > > > discussion about the interpretation of RFC 7950.
> > > > 
> > > > 
> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
> > > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
> > > > 
> > > > [...]
> > > > 
> > > > > > > > > > > 4. In "when" expressions, the module uses literal strings
> > 
> > for
> > > > > > > > > > >   identities. This is known to be problematic, the XPath
> > > > 
> > > > functions
> > > > > > > > > > >   derived-from() or derived-from-or-self() should be used
> > > > 
> > > > instead.
> > > > > > > > > > > 
> > > > > > > > > > 
> > > > > > > > > > Why is this problematic? Is it because the types can be
> > 
> > extended?
> > > > > > > > > 
> > > > > > > > > That's one reason: derived identities should often also satisfy
> > 
> > the
> > > > > > > > > constraint.
> > > > > > > > > 
> > > > > > > > > But the more serious problem is that things like
> > > > > > > > > 
> > > > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > > > > > > > 
> > > > > > > > > rely on plain string comparison that depends od the actual
> > 
> > prefix
> > > > used
> > > > > > > > 
> > > > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON
> > 
> > encoding of
> > > > > > > > > this value
> > > > > > > > > would be "ietf-ospf:ospfv3" so the above expression is always
> > > > 
> > > > false. 
> > > > > > > > 
> > > > > > > > This is not correct; the when expression is not evaluated on the
> > 
> > JSON
> > > > > > > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
> > > > > > > > 
> > > > > > > >    The string value of a node of type "identityref" in a "must" or
> > > > > > > >    "when" XPath expression is the referred identity's qualified
> > 
> > name
> > > > > > > >    with the prefix present.  If the referred identity is defined
> > 
> > in an
> > > > > > > >    imported module, the prefix in the string value is the prefix
> > > > 
> > > > defined
> > > > > > > >    in the corresponding "import" statement.  Otherwise, the prefix
> > 
> > in
> > > > > > > >    the string value is the prefix for the current module.
> > > > > > > 
> > > > > > > This is weird, to say the least. The leafref instance may have an
> > > > 
> > > > identity
> > > > > > > value
> > > > > > > that is defined in a module that (has to be implemented by the
> > 
> > server
> > > > but)
> > > > > > > needn't be imported in the module that contains the XPath
> > 
> > expression. So
> > > > I
> > > > > > > don't
> > > > > > > know what 'corresponding "import" statement' this paragraph is
> > 
> > talking
> > > > > > > about.
> > > > > > 
> > > > > > It has to import the module in order to give a prefix, which then can
> > > > > > be used in the XPath expression.
> > > > > 
> > > > > In the XPath expression above, do you mean the "rt" prefix of
> > > > > "rt:type"?
> > > > 
> > > > No, I meant the "ospf" prefix for the module "ietf-ospf".
> > > > 
> > > > > If so,
> > > > > it is irrelevant for the string comparison, what's important is the
> > 
> > *value*
> > > > of
> > > > > the "rt:type" instance, which can be an identity defined in a module
> > 
> > that
> > > > > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:
> > > > > 
> > > > >    On a particular server, the valid values are further restricted
> > > > >    to the set of identities defined in the modules implemented by
> > > > >    the server.
> > > > 
> > > > Because of the way the representation of identities work in must/when
> > > > expressions, you *must* import the module where the identity is
> > > > define, if you want to use the identity for equality comparision like
> > > > in the example.
> > > > 
> > > > You may have:
> > > > 
> > > >   module a {
> > > >     ...
> > > >     import ietf-ospf {
> > > >       prefix x;
> > > >     }
> > > >     ...
> > > >     leaf foo {
> > > >       when "../type = 'x:ospfv3'";
> > > >       ...
> > > >     }
> > > >   }
> > > 
> > > The problem here is not with the literal 'x:ospf' but rather with the string
> > > value of the leafref node instance ("../type" here), and clearly it is what
> > 
> > sec.
> > > 9.10.3 talks about ("string value of a [leafref] node").
> > > 
> > > I can define a module like
> > > 
> > > module foo-ospf {
> > >   namespace "http://example.com/foo-ospf";
> > >   prefix ospf;
> > >   import ietf-routing {
> > >     prefix rt;
> > >   }
> > >   identity ospfv3 {
> > >     base "rt:routing-protocol";
> > >   }
> > >   ...
> > > }
> > > 
> > > Now, if the server advertizes both ietf-ospf and foo-ospf as implemented
> > 
> > (which
> > > is legal), the module foo-ospf needn't be imported anywhere and still the
> > 
> > "type"
> > > leaf instance can have both values "ietf-ospf:ospfv3" and "foo-ospf:ospfv3",
> > > provided that it is defined as
> > > 
> > > leaf type {
> > >   type identityref {
> > >     base rt:routing-protocol;
> > >   }
> > > }
> > > 
> > > And I wonder what the last paragraph in sec. 9.10.3 means in this situation,
> > > i.e. what string value of "type" is used in the evaluation of the XPath
> > > expression in your module "a", if the value-space value of 'type' instance
> > 
> > in a
> > > datastore is either of the two '...:ospfv3' identities.
> > > 
> > > Do you see what I mean?
> > 
> > Do you mean that the problem is that the spec does not define what the
> > string value is if the module where the identity is defined is not
> > imported?
> > 
> > I agree that this is an issue.
> > 
> > BUT, actually, if you look the text in the spec:
> > 
> >    The string value of a node of type "identityref" in a "must" or
> >    "when" XPath expression is the referred identity's qualified name
> >    with the prefix present.  If the referred identity is defined in an
> >    imported module, the prefix in the string value is the prefix defined
> >    in the corresponding "import" statement.  Otherwise, the prefix in
> >    the string value is the prefix for the current module.
> > 
> > If you blindly follow this, the last sentence would have to apply, and
> > the string would be "a:ospfv3", which clearly is broken.
> 
> It depends on what "current module" means.

"current module" and "local module" means the module where the "must"
or "when" expression is defined.  There was a separate thread about
this as well.

> It could also be interpreted as the
> module in which the identity is defined, but then we can get the collision of
> prefixes as in my example.
> 
> > 
> > For all practical purposes, I think the string value can be "" if the
> > identity is defined in a module that is not imported, and is not
> > defined in the current module.
> 
> I think a better solution would be to avoid prefixes in lexical-space identity
> values altogether and use the same string as in JSON encoding (RFC 7951). The
> XPath expression from your example would become
> 
>     "../type = 'ietf-ospf:ospfv3'"
> 
> Everything would then be straightforward and non-ambiguous.

Yes, as I wrote in my previous email, I agree, this would be better.
But that's for YANG 2.0, unfortunately.


/martin




> 
> Lada
> 
> > 
> > 
> > /martin
> > 
> > 
> > 
> > 
> > > 
> > > Lada 
> > >   
> > > 
> > > > 
> > > > and
> > > > 
> > > >   module b {
> > > >     ...
> > > >     import ietf-ospf {
> > > >       prefix y;
> > > >     }
> > > >     ...
> > > >     leaf bar {
> > > >       when "../type = 'y:ospfv3'";
> > > >       ...
> > > >     }
> > > >   }
> > > > 
> > > > You may not like it, but these two modules are both correct according
> > > > to the rules defined in RFC 7950.  The string value of the "type" leaf
> > > > *when evaluating the when expression* is different in the different
> > > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> > > >     
> > > > > > > Also, potentially there can be a collision in prefixes and then this
> > > > 
> > > > also
> > > > > > > breaks down.
> > > > > > 
> > > > > > 
> > > > > > No, two modules cannot be imported with the same prefix.
> > > > > 
> > > > > I have to disagree. An identity derived from the
> > > > > "ietf-routing:control-protocol-type" base identity can be defined
> > > > > in a module that is not imported anywhere. If a server declares such
> > > > > a module as implemented, then "rt:type" may have this value per
> > > > > sec. 9.10.2.
> > > > > 
> > > > > And, consequently, there may be two different modules with
> > > > > conflicting prefixes defining identities that are derived from
> > > > > "ietf-routing:control-protocol-type".
> > > > 
> > > > Sure, but this is not the point.
> > > > 
> > > > > > > A moral of the namespace/prefix story in XML was that relying of
> > > > > > > namespace prefixes having a particular value is a really bad
> > > > > > > idea. I know that the cited paragraph was intended to make such
> > > > > > > XPath string comparisons more deterministic, but it is also
> > > > > > > problematic and should be avoided if possible.
> > > > > > 
> > > > > > Note that this prefix is under the control of the module designer
> > > > > > writing the XPath expression.  The same identityref value might use a
> > > > > 
> > > > > No, it is not. The prefixes appear in instance data.
> > > > 
> > > > The prefix *in the when expression* is under the control of the module
> > > > designer, as explained above.
> > > > 
> > > > You are correct that the prefix in an XML encoding is not under
> > > > control of the module designer, but noone has claimed that.
> > > > 
> > > > I agree that it is unfortunate that context-specific prefixes are used
> > > > for the identityref values.  It would have been better if we used a
> > > > context free representation, e.g. "<module-name>:<identity>".  But
> > > > that's another discussion.
> > > > 
> > > > 
> > > > 
> > > > /martin
> > > 
> > > -- 
> > > Ladislav Lhotka
> > > Head, CZ.NIC Labs
> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > 
> -- 
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
> 


From nobody Wed Jan 10 13:04:30 2018
Return-Path: <rrahman@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBBB12D950 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:04:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 xHqP8eJAqRjg for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:04:26 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83A341273E2 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 13:04:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10108; q=dns/txt; s=iport; t=1515618266; x=1516827866; h=from:to:subject:date:message-id:mime-version; bh=L2g7a+IHtuydoODYDjugBbmJTAAl1mtkzfzI+KOJmDY=; b=GnVWGjadJWAPRftD6Bt3t6LPR8rnv9oVyF2MinC35io2YCZsoUW+0aBc H6fG7qQX0v436aI0c/FQ+Vm2Nb70JXMn069luRXPkIB8MWkR5jrVRUlMp 5ih5Wc5JxdSaBkCfJiigEtQO8Oj9kYu+d+Aaj5frCgjxy+jD+4FvIrvuc g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AEAgBzflZa/51dJa1eGgEBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYJKd2Z0LoQAiiSOXpNghVGCFgqFV4QsPxgBAQEBAQEBAQFrHQuFTWg?= =?us-ascii?q?BSgIEMCcEiWJkr1eCJyaKGQEBAQEBAQQBAQEBAQEBAQEfhCCCFYFXghKLPjGCN?= =?us-ascii?q?AWZcolyAoF8k0eUDpZ0AhEZAYE7AR85JYErbxVnAYIAhFaLQQGBFgEBAQ?=
X-IronPort-AV: E=Sophos; i="5.46,342,1511827200"; d="scan'208,217"; a="54946390"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 21:04:25 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id w0AL4PiJ028724 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 21:04:25 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 10 Jan 2018 15:04:24 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Wed, 10 Jan 2018 15:04:25 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: Features and must-condition
Thread-Index: AQHTilaYFa81RoW2ZUea0h9DxiIyiQ==
Date: Wed, 10 Jan 2018 21:04:25 +0000
Message-ID: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.183]
Content-Type: multipart/alternative; boundary="_000_9E242E7EE87D41C7BFEDEB8185195F26ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/QGerwNLiuzmE-GU2bToF7CJYcF8>
Subject: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 21:04:28 -0000

--_000_9E242E7EE87D41C7BFEDEB8185195F26ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCkkgYW0gZG9pbmcgWUQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcGltLW1zZHAteWFuZy0w
MS4gVGhlIFlBTkcgbW9kdWxlIGlzIHNtYWxsIGJ1dCByZWxhdGl2ZWx5IHNwZWFraW5nIHRoZXJl
4oCZcyBhIGJpZyBudW1iZXIgb2YgZmVhdHVyZXMgMTcuIEJhc2ljYWxseSBlYWNoIGNvbmZpZyBr
bm9iIGhhcyBhbiBpZi1mZWF0dXJlLg0KDQpIb3dldmVyIGtlZXBhbGl2ZS1pbnRlcnZhbCBoYXMg
IGEgZGVwZW5kZW5jeSBvbiBob2xkdGltZS1pbnRlcnZhbCB2aWEgbXVzdCBzdGF0ZW1lbnQuIElz
IHRoZSBvbmx5IHdheSB0byBlbmZvcmNlIHRoaXMgdG8gYWRkIOKAnGlmLWZlYXR1cmUgcGVlci10
aW1lci1ob2xkdGltZeKAnSB0byBsZWFmIGtlZXBhbGl2ZS1pbnRlcm5hbD8NCg0KUmVnYXJkcywN
ClJlc2hhZC4NCg0KICAgICAgICAgbGVhZiBob2xkdGltZS1pbnRlcnZhbCB7DQogICAgICAgICAg
IGlmLWZlYXR1cmUgcGVlci10aW1lci1ob2xkdGltZTsNCiAgICAgICAgICAgdHlwZSB1aW50MTY7
DQogICAgICAgICAgIHVuaXRzIHNlY29uZHM7DQogICAgICAgICAgIG11c3QgIi4gPiAzIjsNCiAg
ICAgICAgICAgZGVmYXVsdCA3NTsNCiAgICAgICAgICAgZGVzY3JpcHRpb24gIlRoZSBTQS1Ib2xk
LURvd24tUGVyaW9kIG9mIHRoaXMgbXNkcCBwZWVyLiI7DQogICAgICAgICB9DQogICAgICAgICBs
ZWFmIGtlZXBhbGl2ZS1pbnRlcnZhbCB7DQogICAgICAgICAgIGlmLWZlYXR1cmUgcGVlci10aW1l
ci1rZWVwYWxpdmU7DQogICAgICAgICAgIHR5cGUgdWludDE2Ow0KICAgICAgICAgICB1bml0cyBz
ZWNvbmRzOw0KICAgICAgICAgICBtdXN0ICIuID4gMSBhbmQgLiA8IC4uL2hvbGR0aW1lLWludGVy
dmFsIjsNCiAgICAgICAgICAgZGVmYXVsdCA2MDsNCiAgICAgICAgICAgZGVzY3JpcHRpb24gIlRo
ZSBrZWVwYWxpdmUgdGltZXIgb2YgdGhpcyBtc2RwIHBlZXIuIjsNCiAgICAgICAgIH0NCg0KDQo=

--_000_9E242E7EE87D41C7BFEDEB8185195F26ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <787045C68AF4C14FB09388386466DDDC@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojOTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29t
cG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0
ZXh0Ow0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0eWxlOm5vcm1hbDt9DQpzcGFuLm1z
b0lucw0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUtbmFtZToiIjsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1zb0NocERlZmF1
bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0
Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9u
MQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgYmdj
b2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tQ0EiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5IaSw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1DQSIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLUNBIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+SSBh
bSBkb2luZyBZRCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1waW0tbXNkcC15YW5nLTAxLiBUaGUgWUFO
RyBtb2R1bGUgaXMgc21hbGwgYnV0IHJlbGF0aXZlbHkgc3BlYWtpbmcgdGhlcmXigJlzIGEgYmln
IG51bWJlciBvZiBmZWF0dXJlcyAxNy4gQmFzaWNhbGx5IGVhY2ggY29uZmlnIGtub2IgaGFzIGFu
IGlmLWZlYXR1cmUuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1DQSIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLUNB
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+SG93ZXZlciBrZWVwYWxpdmUtaW50ZXJ2YWwgaGFz
Jm5ic3A7IGEgZGVwZW5kZW5jeSBvbiBob2xkdGltZS1pbnRlcnZhbCB2aWEgbXVzdCBzdGF0ZW1l
bnQuIElzIHRoZSBvbmx5IHdheSB0byBlbmZvcmNlIHRoaXMgdG8gYWRkIOKAnGlmLWZlYXR1cmUg
cGVlci10aW1lci1ob2xkdGltZeKAnSB0byBsZWFmIGtlZXBhbGl2ZS1pbnRlcm5hbD88bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1DQSIg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLUNBIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdCI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1DQSIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPlJlc2hhZC48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1D
QSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciZxdW90
OyxzZXJpZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IGxlYWYgaG9sZHRpbWUtaW50ZXJ2YWwgezxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBpZi1mZWF0dXJlIHBlZXItdGltZXItaG9sZHRp
bWU7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciZxdW90OyxzZXJp
ZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7IHR5cGUgdWludDE2OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB1bml0cyBzZWNvbmRzOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NvdXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBtdXN0ICZxdW90Oy4gJmd0
OyAzJnF1b3Q7OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXImcXVv
dDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBkZWZhdWx0IDc1OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBkZXNjcmlwdGlvbiAmcXVvdDtUaGUgU0EtSG9s
ZC1Eb3duLVBlcmlvZCBvZiB0aGlzIG1zZHAgcGVlci4mcXVvdDs7PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciZxdW90OyxzZXJpZiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IH08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyJnF1b3Q7LHNlcmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgbGVhZiBrZWVwYWxpdmUtaW50ZXJ2YWwgezxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBpZi1m
ZWF0dXJlIHBlZXItdGltZXIta2VlcGFsaXZlOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0eXBlIHVpbnQxNjs8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyJnF1b3Q7LHNlcmlmIj4mbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdW5pdHMgc2Vj
b25kczs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyJnF1b3Q7LHNl
cmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsgbXVzdCAmcXVvdDsuICZndDsgMSBhbmQgLiAmbHQ7IC4uL2hvbGR0aW1lLWludGVy
dmFsJnF1b3Q7OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXImcXVv
dDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyBkZWZhdWx0IDYwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NvdXJpZXImcXVvdDssc2VyaWYiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBkZXNjcmlwdGlvbiAmcXVvdDtUaGUga2VlcGFs
aXZlIHRpbWVyIG9mIHRoaXMgbXNkcCBwZWVyLiZxdW90Ozs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyJnF1b3Q7LHNlcmlmIj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgfTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NvdXJpZXImcXVvdDssc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLUNBIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_9E242E7EE87D41C7BFEDEB8185195F26ciscocom_--


From nobody Wed Jan 10 13:33:21 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B11129C6C for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:33:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 IGOtyC9-lkrL for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:33:18 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id EB9F1120725 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 13:33:17 -0800 (PST)
Received: from localhost (h-85-209.A165.priv.bahnhof.se [94.254.85.209]) by mail.tail-f.com (Postfix) with ESMTPSA id 2519E1AE0118; Wed, 10 Jan 2018 22:33:17 +0100 (CET)
Date: Wed, 10 Jan 2018 22:33:16 +0100 (CET)
Message-Id: <20180110.223316.2175524120457720164.mbj@tail-f.com>
To: rrahman@cisco.com
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/vAp8cn_ldqqoJvlk0daz6kzS8uc>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 21:33:19 -0000

SGksDQoNCiJSZXNoYWQgUmFobWFuIChycmFobWFuKSIgPHJyYWhtYW5AY2lzY28uY29tPiB3cm90
ZToNCj4gSGksDQo+IA0KPiBJIGFtIGRvaW5nIFlEIHJldmlldyBvZiBkcmFmdC1pZXRmLXBpbS1t
c2RwLXlhbmctMDEuIFRoZSBZQU5HIG1vZHVsZQ0KPiBpcyBzbWFsbCBidXQgcmVsYXRpdmVseSBz
cGVha2luZyB0aGVyZeKAmXMgYSBiaWcgbnVtYmVyIG9mIGZlYXR1cmVzDQo+IDE3LiBCYXNpY2Fs
bHkgZWFjaCBjb25maWcga25vYiBoYXMgYW4gaWYtZmVhdHVyZS4NCj4gDQo+IEhvd2V2ZXIga2Vl
cGFsaXZlLWludGVydmFsIGhhcyBhIGRlcGVuZGVuY3kgb24gaG9sZHRpbWUtaW50ZXJ2YWwgdmlh
DQo+IG11c3Qgc3RhdGVtZW50LiBJcyB0aGUgb25seSB3YXkgdG8gZW5mb3JjZSB0aGlzIHRvIGFk
ZCDigJxpZi1mZWF0dXJlDQo+IHBlZXItdGltZXItaG9sZHRpbWXigJ0gdG8gbGVhZiBrZWVwYWxp
dmUtaW50ZXJuYWw/DQoNCkVpdGhlciB0aGF0LCBvciBkbzoNCg0KICAgICAgbXVzdCAiKG5vdCAu
Li9ob2xkdGltZS1pbnRlcnZhbCkiDQogICAgICAgICArICIgb3IgKC4gPiAxIGFuZCAuIDwgLi4v
aG9sZHRpbWUtaW50ZXJ2YWwpIjsNCg0KZGVwZW5kaW5nIG9uIHdoaWNoIGNvbWJpbmF0aW9ucyB0
aGV5IHdhbnQgdG8gc3VwcG9ydC4NCg0KMTcgZmVhdHVyZXMgc2VlbXMgcXVpdGUgYSBsb3QuLi4N
Cg0KDQoNCj4gDQo+IFJlZ2FyZHMsDQo+IFJlc2hhZC4NCj4gDQo+ICAgICAgICAgIGxlYWYgaG9s
ZHRpbWUtaW50ZXJ2YWwgew0KPiAgICAgICAgICAgIGlmLWZlYXR1cmUgcGVlci10aW1lci1ob2xk
dGltZTsNCj4gICAgICAgICAgICB0eXBlIHVpbnQxNjsNCj4gICAgICAgICAgICB1bml0cyBzZWNv
bmRzOw0KPiAgICAgICAgICAgIG11c3QgIi4gPiAzIjsNCj4gICAgICAgICAgICBkZWZhdWx0IDc1
Ow0KPiAgICAgICAgICAgIGRlc2NyaXB0aW9uICJUaGUgU0EtSG9sZC1Eb3duLVBlcmlvZCBvZiB0
aGlzIG1zZHAgcGVlci4iOw0KPiAgICAgICAgICB9DQo+ICAgICAgICAgIGxlYWYga2VlcGFsaXZl
LWludGVydmFsIHsNCj4gICAgICAgICAgICBpZi1mZWF0dXJlIHBlZXItdGltZXIta2VlcGFsaXZl
Ow0KPiAgICAgICAgICAgIHR5cGUgdWludDE2Ow0KPiAgICAgICAgICAgIHVuaXRzIHNlY29uZHM7
DQo+ICAgICAgICAgICAgbXVzdCAiLiA+IDEgYW5kIC4gPCAuLi9ob2xkdGltZS1pbnRlcnZhbCI7
DQo+ICAgICAgICAgICAgZGVmYXVsdCA2MDsNCj4gICAgICAgICAgICBkZXNjcmlwdGlvbiAiVGhl
IGtlZXBhbGl2ZSB0aW1lciBvZiB0aGlzIG1zZHAgcGVlci4iOw0KPiAgICAgICAgICB9DQo+IA0K
PiANCg0KDQovbWFydGluDQo=


From nobody Wed Jan 10 13:51:16 2018
Return-Path: <rrahman@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D278E126BF0 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 gG169r1v7Xo2 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:51:13 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5318B120725 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 13:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2484; q=dns/txt; s=iport; t=1515621073; x=1516830673; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SOSUrFUALfrOxLED6GWbOpSqfyp7xqL9tOiAiVUVX+Y=; b=dRIBBZsswGKVrBQOkM7CEo7xwhNh66BE4lsWbtJjz3c/Z05/tO9NdKHK ZdZVez8oftnvm3q97bUHr6s5on5ssOctb9Fj0BNmGrXcWgOMSnXPVV+VF a1j92kyUIOTInxgoBieh9aS7QUAUQCfPiWspUfk2KIhpO7TMrj1Er1KXb s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BYAQBrilZa/5RdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNBgVonB4QAiiSOXoFbJ5cwghYKhTsCGoQsPxgBAQEBAQEBAQF?= =?us-ascii?q?rKIUjAQEBAQIBIxFFEAIBCA4KAgImAgICMBUQAgQOBYorCK9YgieKPwEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAR2BD4MRghWBV4ISDIJ5gy8EgW8XgwAxghQgBaNkApV?= =?us-ascii?q?DlA6WdAIRGQGBOwEfOYFQbxVnAYF/hFd4ikkBgRYBAQE?=
X-IronPort-AV: E=Sophos;i="5.46,342,1511827200"; d="scan'208";a="54411213"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 21:51:12 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w0ALpCds010643 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Jan 2018 21:51:12 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 10 Jan 2018 15:51:11 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Wed, 10 Jan 2018 15:51:12 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>
CC: "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] Features and must-condition
Thread-Index: AQHTilaYFa81RoW2ZUea0h9DxiIyiaNuBSgAgAAFAAA=
Date: Wed, 10 Jan 2018 21:51:12 +0000
Message-ID: <54D46590-633D-4936-AFDF-C6BDE9F43968@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com>
In-Reply-To: <20180110.223316.2175524120457720164.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.183]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8E798E2EE64FC441A883E3B78DD326AE@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/hw8I_JLUy2KjkTVVCEUi5TZ3d5w>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 21:51:15 -0000

VGhhbmtzIE1hcnRpbi4gDQoNClllcyAxNyBmZWF0dXJlcyBpcyBhIGxvdCBmb3Igc3VjaCBhIHNt
YWxsIG1vZHVsZS4gSSByZWNhbGwgd2UgaGFkIHRoZSBwZXItY291bnRlciBmZWF0dXJlIGEgZmV3
IG1vbnRocyBhZ28sIHRoYXTigJlzIHdoYXQgYmFzaWNhbGx5IHRoaXMgbW9kZWwgaXMgZG9pbmcg
YnV0IHBlciBjb25maWcuDQoNClJlZ2FyZHMsDQpSZXNoYWQuDQoNCk9uIDIwMTgtMDEtMTAsIDQ6
MzMgUE0sICJNYXJ0aW4gQmpvcmtsdW5kIiA8bWJqQHRhaWwtZi5jb20+IHdyb3RlOg0KDQogICAg
SGksDQogICAgDQogICAgIlJlc2hhZCBSYWhtYW4gKHJyYWhtYW4pIiA8cnJhaG1hbkBjaXNjby5j
b20+IHdyb3RlOg0KICAgID4gSGksDQogICAgPiANCiAgICA+IEkgYW0gZG9pbmcgWUQgcmV2aWV3
IG9mIGRyYWZ0LWlldGYtcGltLW1zZHAteWFuZy0wMS4gVGhlIFlBTkcgbW9kdWxlDQogICAgPiBp
cyBzbWFsbCBidXQgcmVsYXRpdmVseSBzcGVha2luZyB0aGVyZeKAmXMgYSBiaWcgbnVtYmVyIG9m
IGZlYXR1cmVzDQogICAgPiAxNy4gQmFzaWNhbGx5IGVhY2ggY29uZmlnIGtub2IgaGFzIGFuIGlm
LWZlYXR1cmUuDQogICAgPiANCiAgICA+IEhvd2V2ZXIga2VlcGFsaXZlLWludGVydmFsIGhhcyBh
IGRlcGVuZGVuY3kgb24gaG9sZHRpbWUtaW50ZXJ2YWwgdmlhDQogICAgPiBtdXN0IHN0YXRlbWVu
dC4gSXMgdGhlIG9ubHkgd2F5IHRvIGVuZm9yY2UgdGhpcyB0byBhZGQg4oCcaWYtZmVhdHVyZQ0K
ICAgID4gcGVlci10aW1lci1ob2xkdGltZeKAnSB0byBsZWFmIGtlZXBhbGl2ZS1pbnRlcm5hbD8N
CiAgICANCiAgICBFaXRoZXIgdGhhdCwgb3IgZG86DQogICAgDQogICAgICAgICAgbXVzdCAiKG5v
dCAuLi9ob2xkdGltZS1pbnRlcnZhbCkiDQogICAgICAgICAgICAgKyAiIG9yICguID4gMSBhbmQg
LiA8IC4uL2hvbGR0aW1lLWludGVydmFsKSI7DQogICAgDQogICAgZGVwZW5kaW5nIG9uIHdoaWNo
IGNvbWJpbmF0aW9ucyB0aGV5IHdhbnQgdG8gc3VwcG9ydC4NCiAgICANCiAgICAxNyBmZWF0dXJl
cyBzZWVtcyBxdWl0ZSBhIGxvdC4uLg0KICAgIA0KICAgIA0KICAgIA0KICAgID4gDQogICAgPiBS
ZWdhcmRzLA0KICAgID4gUmVzaGFkLg0KICAgID4gDQogICAgPiAgICAgICAgICBsZWFmIGhvbGR0
aW1lLWludGVydmFsIHsNCiAgICA+ICAgICAgICAgICAgaWYtZmVhdHVyZSBwZWVyLXRpbWVyLWhv
bGR0aW1lOw0KICAgID4gICAgICAgICAgICB0eXBlIHVpbnQxNjsNCiAgICA+ICAgICAgICAgICAg
dW5pdHMgc2Vjb25kczsNCiAgICA+ICAgICAgICAgICAgbXVzdCAiLiA+IDMiOw0KICAgID4gICAg
ICAgICAgICBkZWZhdWx0IDc1Ow0KICAgID4gICAgICAgICAgICBkZXNjcmlwdGlvbiAiVGhlIFNB
LUhvbGQtRG93bi1QZXJpb2Qgb2YgdGhpcyBtc2RwIHBlZXIuIjsNCiAgICA+ICAgICAgICAgIH0N
CiAgICA+ICAgICAgICAgIGxlYWYga2VlcGFsaXZlLWludGVydmFsIHsNCiAgICA+ICAgICAgICAg
ICAgaWYtZmVhdHVyZSBwZWVyLXRpbWVyLWtlZXBhbGl2ZTsNCiAgICA+ICAgICAgICAgICAgdHlw
ZSB1aW50MTY7DQogICAgPiAgICAgICAgICAgIHVuaXRzIHNlY29uZHM7DQogICAgPiAgICAgICAg
ICAgIG11c3QgIi4gPiAxIGFuZCAuIDwgLi4vaG9sZHRpbWUtaW50ZXJ2YWwiOw0KICAgID4gICAg
ICAgICAgICBkZWZhdWx0IDYwOw0KICAgID4gICAgICAgICAgICBkZXNjcmlwdGlvbiAiVGhlIGtl
ZXBhbGl2ZSB0aW1lciBvZiB0aGlzIG1zZHAgcGVlci4iOw0KICAgID4gICAgICAgICAgfQ0KICAg
ID4gDQogICAgPiANCiAgICANCiAgICANCiAgICAvbWFydGluDQogICAgDQoNCg==


From nobody Wed Jan 10 13:56:19 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6701E12D848 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:56:17 -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 b72sy4HZ4RSC for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 13:56:15 -0800 (PST)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 CF7D9120725 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 13:56:14 -0800 (PST)
Received: by mail-lf0-x22b.google.com with SMTP id j143so527007lfg.0 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 13:56:14 -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=ak7uQ03MvwvIx4i0vyoo5Z5kco065FzAKzRd2Y7QuS8=; b=jJAbIK0hVDevBQhKPi6dBiPvolUE+4UVlQgsGRlkCI3YNaINcf65x8dguZzIaQghpo kIOwTMEyPHuADPwxZz3F30ks8mC4p9tNS3CF/CG9IWvNuIX3qaA/+Ay9txbbOUIMkIrE QP5MnOvGPOsDPazLhUhWbcifs5WuwkvBjPdwyQjT+Y6P7AafIIS6yh6XuXLs/OQpRES6 Feb2UZqwcqGZyD/he16pgKhYTIIMpbb6MOE0U2FOpWTymKfbZ6A34vn2r0Vmn/gruzTR RUTf3j4ftt6syb60J1WmRE24oqBU1UnWQOwrHHMD9DQc0gxROu7V5naaJJWjF4Xf5wYV 7Heg==
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=ak7uQ03MvwvIx4i0vyoo5Z5kco065FzAKzRd2Y7QuS8=; b=ONY5WD9OF2QrfhieK1wLbPCXz/C/RGriiOQaP5cq/wNAoOy4Q5Z3t/iUnbCrOUKkfB tG590+ZovXP26OA1e84s/0y6s8JJ7MQBIocMGhBO2iLI1cToa10SFfwyK3P/x5KgWyh4 CeFyOW5H1UU6yXFy4G7xMM46uMFNlo0f1q6fvdEaxbfREVgYQoOOOMp1bTl9G+3PVZYE CaR7dLRZc2wDH1TaboglzyURjCKqEzMMcXYnyoyk73CwqMO2qj+2Bk9tbKN9iSMMXU+2 e+P5zmQnYdsS0w0LcFqB4Nuyg2EbMJTrBagPoZV0fGDHLcMsT3+7i/zkAKjfUpg109BE OGGg==
X-Gm-Message-State: AKGB3mIXxKbWz4rhC1bWTeN4SvQeNdm+ZyFSiaD5vLtrWsov5PQ70mQn S8YZ2uGk+y1IeDzPpzn58cFtmghNVE+pPdu8eJPoQA==
X-Google-Smtp-Source: ACJfBotUrSQb6QTeyl3aR37KR0zXttGqTYT2iJtEop3i09gakx8Ca2edP8mGeak1hfW1qdsIZ1jFtwqJQfY+joBKjTs=
X-Received: by 10.46.82.133 with SMTP id n5mr12319992lje.47.1515621373049; Wed, 10 Jan 2018 13:56:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.162.1 with HTTP; Wed, 10 Jan 2018 13:56:12 -0800 (PST)
In-Reply-To: <54D46590-633D-4936-AFDF-C6BDE9F43968@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <54D46590-633D-4936-AFDF-C6BDE9F43968@cisco.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 10 Jan 2018 13:56:12 -0800
Message-ID: <CABCOCHT7iUJ1t+FH1UqK8Bvq3Q4TS4pQ0GsMc706uNZVEcgjBw@mail.gmail.com>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="001a113bd35a8e11e80562731977"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/1vuP1hjSVByOTxdgearRFYkVNlk>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 21:56:17 -0000

--001a113bd35a8e11e80562731977
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 10, 2018 at 1:51 PM, Reshad Rahman (rrahman) <rrahman@cisco.com=
>
wrote:

> Thanks Martin.
>
> Yes 17 features is a lot for such a small module. I recall we had the
> per-counter feature a few months ago, that=E2=80=99s what basically this =
model is
> doing but per config.
>
>
Seems the concepts and guidelines for YANG conformance are still very
unclear.
Are WGs thinking about the utility to the client developer,
or the ability for a server developer to claim conformance no matter what
they implement?

It seems unlikely that each leaf is completely independent of all others
wrt/ functionality.



> Regards,
> Reshad.
>
>

Andy



> On 2018-01-10, 4:33 PM, "Martin Bjorklund" <mbj@tail-f.com> wrote:
>
>     Hi,
>
>     "Reshad Rahman (rrahman)" <rrahman@cisco.com> wrote:
>     > Hi,
>     >
>     > I am doing YD review of draft-ietf-pim-msdp-yang-01. The YANG modul=
e
>     > is small but relatively speaking there=E2=80=99s a big number of fe=
atures
>     > 17. Basically each config knob has an if-feature.
>     >
>     > However keepalive-interval has a dependency on holdtime-interval vi=
a
>     > must statement. Is the only way to enforce this to add =E2=80=9Cif-=
feature
>     > peer-timer-holdtime=E2=80=9D to leaf keepalive-internal?
>
>     Either that, or do:
>
>           must "(not ../holdtime-interval)"
>              + " or (. > 1 and . < ../holdtime-interval)";
>
>     depending on which combinations they want to support.
>
>     17 features seems quite a lot...
>
>
>
>     >
>     > Regards,
>     > Reshad.
>     >
>     >          leaf holdtime-interval {
>     >            if-feature peer-timer-holdtime;
>     >            type uint16;
>     >            units seconds;
>     >            must ". > 3";
>     >            default 75;
>     >            description "The SA-Hold-Down-Period of this msdp peer."=
;
>     >          }
>     >          leaf keepalive-interval {
>     >            if-feature peer-timer-keepalive;
>     >            type uint16;
>     >            units seconds;
>     >            must ". > 1 and . < ../holdtime-interval";
>     >            default 60;
>     >            description "The keepalive timer of this msdp peer.";
>     >          }
>     >
>     >
>
>
>     /martin
>
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
>

--001a113bd35a8e11e80562731977
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jan 10, 2018 at 1:51 PM, Reshad Rahman (rrahman) <span dir=3D"l=
tr">&lt;<a href=3D"mailto:rrahman@cisco.com" target=3D"_blank">rrahman@cisc=
o.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Martin=
.<br>
<br>
Yes 17 features is a lot for such a small module. I recall we had the per-c=
ounter feature a few months ago, that=E2=80=99s what basically this model i=
s doing but per config.<br>
<br></blockquote><div><br></div><div>Seems the concepts and guidelines for =
YANG conformance are still very unclear.</div><div>Are WGs thinking about t=
he utility to the client developer,</div><div>or the ability for a server d=
eveloper to claim conformance no matter what they implement?</div><div><br>=
</div><div>It seems unlikely that each leaf is completely independent of al=
l others wrt/ functionality.</div><div><br></div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
Regards,<br>
Reshad.<br>
<br></blockquote><div><br></div><div><br></div><div>Andy</div><div><br></di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2018-01-10, 4:33 PM, &quot;Martin Bjorklund&quot; &lt;<a href=3D"mailto:=
mbj@tail-f.com">mbj@tail-f.com</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 Hi,<br>
<br>
=C2=A0 =C2=A0 &quot;Reshad Rahman (rrahman)&quot; &lt;<a href=3D"mailto:rra=
hman@cisco.com">rrahman@cisco.com</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; Hi,<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; I am doing YD review of draft-ietf-pim-msdp-yang-01. The=
 YANG module<br>
=C2=A0 =C2=A0 &gt; is small but relatively speaking there=E2=80=99s a big n=
umber of features<br>
=C2=A0 =C2=A0 &gt; 17. Basically each config knob has an if-feature.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; However keepalive-interval has a dependency on holdtime-=
interval via<br>
=C2=A0 =C2=A0 &gt; must statement. Is the only way to enforce this to add =
=E2=80=9Cif-feature<br>
=C2=A0 =C2=A0 &gt; peer-timer-holdtime=E2=80=9D to leaf keepalive-internal?=
<br>
<br>
=C2=A0 =C2=A0 Either that, or do:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 must &quot;(not ../holdtime-interval)&qu=
ot;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0+ &quot; or (. &gt; 1 and .=
 &lt; ../holdtime-interval)&quot;;<br>
<br>
=C2=A0 =C2=A0 depending on which combinations they want to support.<br>
<br>
=C2=A0 =C2=A0 17 features seems quite a lot...<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; Regards,<br>
=C2=A0 =C2=A0 &gt; Reshad.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 leaf holdtime-interval=
 {<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if-feature peer=
-timer-holdtime;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 type uint16;<br=
>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 units seconds;<=
br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 must &quot;. &g=
t; 3&quot;;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 default 75;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 description &qu=
ot;The SA-Hold-Down-Period of this msdp peer.&quot;;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 leaf keepalive-interva=
l {<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if-feature peer=
-timer-keepalive;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 type uint16;<br=
>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 units seconds;<=
br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 must &quot;. &g=
t; 1 and . &lt; ../holdtime-interval&quot;;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 default 60;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 description &qu=
ot;The keepalive timer of this msdp peer.&quot;;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
<br>
<br>
=C2=A0 =C2=A0 /martin<br>
<br>
<br>
______________________________<wbr>_________________<br>
yang-doctors mailing list<br>
<a href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/yang-do=
ctors</a><br>
</blockquote></div><br></div></div>

--001a113bd35a8e11e80562731977--


From nobody Wed Jan 10 14:01:45 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B280E127241 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 NDHG6c8q7nhS for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:01:41 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 7AA57126C0F for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:01:41 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0ALxqmM007520; Wed, 10 Jan 2018 14:01:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to; s=PPS1017; bh=kfiYj/fkygBzC7NkRbOTj6nFFDEMaHn05oYKiAL8tzo=; b=NpyoNjEsdJSzbJwJM86VfM8n58TMbjvto/hvMcBrEIcn2+0h6AjGqhZtTmpMGbSIDxi4 vWIRPSh0adTnWN6p/BRGpTX4PnrUCqKMz5e9BhcI9Kdi3WUEUurifUep2WfNTuBAPTGK Y8Q9VcLYlzrBkBZ4UkJY6Jpd+p7Ch+YzlBaLc/mXtqRYvVKK7IBQ05K2GIqhZaPeFmb6 RoVc4+/Z8QRWe/VNiO/y5scFMWp1L33UYZQ1q5mnXM8TAudc4KBFjepIvwxKfcVhj4SD 3N1yo1AA+nXU2+uRGmXN/8bo4M9q7+sFNxikZ9V5Zv3a9bbQGUGKWBC2BsE0lz/1F6wo mg== 
Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp0175.outbound.protection.outlook.com [216.32.181.175]) by mx0a-00273201.pphosted.com with ESMTP id 2fds2ggbsc-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Jan 2018 14:01:38 -0800
Received: from SN1PR0501CA0029.namprd05.prod.outlook.com (10.163.126.167) by BY2PR0501MB2072.namprd05.prod.outlook.com (10.163.197.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.1; Wed, 10 Jan 2018 22:01:37 +0000
Received: from DM3NAM05FT052.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::207) by SN1PR0501CA0029.outlook.office365.com (2a01:111:e400:52fe::39) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.407.1 via Frontend Transport; Wed, 10 Jan 2018 22:01:37 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT052.mail.protection.outlook.com (10.152.98.166) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.345.12 via Frontend Transport; Wed, 10 Jan 2018 22:01:37 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 10 Jan 2018 14:01:35 -0800
Date: Wed, 10 Jan 2018 15:01:31 -0700
From: Ebben Aries <exa@juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>
CC: <rrahman@cisco.com>, <yang-doctors@ietf.org>
Message-ID: <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20180110.223316.2175524120457720164.mbj@tail-f.com>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(979002)(39380400002)(376002)(346002)(396003)(39860400002)(2980300002)(189003)(199004)(24454002)(23676004)(2870700001)(68736007)(4326008)(2906002)(5660300001)(53936002)(76176011)(478600001)(575784001)(54906003)(6306002)(356003)(86362001)(7696005)(55016002)(316002)(2486003)(59450400001)(1076002)(47776003)(97736004)(6246003)(69596002)(106466001)(81166006)(229853002)(77096006)(50466002)(8676002)(6916009)(53416004)(966005)(81156014)(8936002)(2950100002)(104016004)(6666003)(305945005)(105596002)(42262002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0501MB2072; H:P-EMFE01C-SAC.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT052; 1:8/C8osaHzZTTaG/Hji3LLUCpJd+xTXbmKfn79vK17P5EI0HvY23yqGOFwzNsPdJIh0lScb8AVYrGcpQ/dq3CR8VOM81icqGYojPk9m1F5ylKkLLzFToug2LfIsx0fwaL
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 62e13318-c33a-4262-fcbb-08d55875b8ab
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:BY2PR0501MB2072; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 3:VKa0Q0bGdb0hMEe2snM+x+YDNOIOyg4OjGqJg9rNrSp3mQqXt3jpGq7kocSKldKh3Z3odQMhFxHkjvG9ZNRdG/75yfZETm4eaqiGRU4tq8K3Oa/bn9qDkcAvBfy+rzAmrgb4yiMyjmGbRZZdhLsRff6OrE5JW6hHh0dZUV76O6nOcw9nTM/ypdj2um7P3X4wxF2KXJ3F1YATY/glohg9G1GdlN75emNCTypHXjFevlnYHxqH931A9csc7J7y1L2QZoGMcCLX+LPCRW0AWfrqaGRpVZZbZDqGWHgfDYyI919Q4BuzEAeJPHe7gAYHZ6UgExUOa8x/7RSk5pZNcH4fHWWCtKFIJ4CYcDBwvogariA=; 25:cGPX7i/EKXpciDgFvVnK/AKZuABm/yfqZrWJIj5owSufJjBuUKrtVr8VHAwTHnHmlvGIUkJfyGPoJ+Mcv8R5q65rZV40EUg+uemRYelSLZr3104DFu584PUI0lLHtJA883VXlQodREvHMOKVxWMOJHOSfQE4SGoXZ1lqXwUX8chpylDnVIOn3jDMiiJtvwp6Bp0HwfWP9qJN43xgb8fUReHegBHt8lB2MlTks8oM4nsJSLbwZYy5dFyknvQdLjDP6tL2n8sdDIDpLWsFdzofjGiAcVlxeW5D/rMGzvlbnR+Iv6UAAULS+e00II3aaBAxhBx8r7iP1bLzjz1QC3wmOA==
X-MS-TrafficTypeDiagnostic: BY2PR0501MB2072:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 31:Cl47YN5cGisoYvHhZ65eYCLaM+mN3giLl/fU57k9vja2wiSABYCmsuEvuwrHdLkV/mri+BPFF9plEBRd3N8mixf8QBghQZOGAJka41kvOnM77mfguaZPuGqkRlpeBhw/kUzrO9KUgZtAcXJI3w5iu0ijmrNvzWywVSn0aZAhkLjXU7l2e1l+7UhiJ7McMZoM+CVMlAtL9PX3gYOifujIECDcq3ebfd6ndO09NNMRVno=; 20:pfHnxrcfA2H35Pekt1YcWk5RAOhI8/X/rJdLird/nzxfYywhSiK7/uB39ZvAt6qXUfU/biDU/J+1JfEtMjcy0j/+y5UXbg1shIFpOzUbRDt6gyKzggxtRT+72+2mUfccNJLzejzepf3CCdxj6TKPge+bnoN5EFqOnvAFqxeK1wZkz9B8OOBWfRlMCfFLE6oYHzT91UJhmGwJXHxZXwbpDlsykLA80143dMKycL33XYROz9sn5kE/MB+lujx17wbUJJjilm5kzfj5Kp0c3zwYOHnzdv9m7KSC1qyOguBI8B0Fk0OKGbQ+C+BYZg3R/ckhKjgKEQSROU2tgMn0NY6tN79Wi9+nWO1qLHZZN/7HedtLvjaQtJ6skCgxLdkRxw7rp9LU3mRaxghJS9M2w8FE2A7Y27JLALuSgrBdPLqxHYRns8+6k1yHRWIcooCZVaMYNzI8lLRoH2vxIS6BH/g69SXClNCxuBqh5mvEog8S8rd/RK8wcnpgLJBCf1R5bJj8
X-Microsoft-Antispam-PRVS: <BY2PR0501MB2072D07C7BC0BCA90D266F8DA8110@BY2PR0501MB2072.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(10436049006162)(95692535739014);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(10201501046)(3231023)(944501075)(3002001)(93006095)(93001095)(6055026)(6041268)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123564045)(6072148)(201708071742011); SRVR:BY2PR0501MB2072; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BY2PR0501MB2072; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 4:3V3oU88dHjoPStszMLbTCfw+sRIb3LFnUmXKHwjoX17ybtySoSkHGJcpIA4qFWxv7b3oUeVW2ePQxdDkPSMebqCYedMqxWvMYrAs7LDplJkY0HrqBX/UQkY+1TrFQoafH07nL3u/BLum9Xsoqvd26aAeXaY8DQPyV0coxmc9Ily6PlDx19n5UxtOPdjdunt8PcipWSmbUiqJyJckfcKAeBFp8hZMqMihqjnrwTcaRi4Cxb7N6Ol16Jwp4Z3DOwpEAqz6AJGOo5cGQgJKK8yn+Yak7gjr2VJC9lH6agOHUY2VQZAabVD37hNGoZnIklzoi1Une6FOmzwhHadBRsS1Aw==
X-Forefront-PRVS: 0548586081
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1MDFNQjIwNzI7MjM6cHBzZGZLR2hCa2RYM0RGQm9Nczg1TitI?= =?utf-8?B?SXNndjhuTGtYUXllV0FZc1hzSmJSVml0NVUraENxeEVOZWFCUHQwNGJBL0U5?= =?utf-8?B?ZnhPQlE2N285N0kyNkNVbzBFV2pEaDRrMEdUMGFKdHZOS2Zaay9BbjNFdmNz?= =?utf-8?B?UUx2c2ZJb2Y4dnNYUDdZY1dSZHRmSDVGN3NDaXJ0Q3lDN2NQSjdnM3VJMElS?= =?utf-8?B?OG5MUUR3RVJkdlg4c3d4L3JwWG5UWHVITVRZN1YrbHlTMUJPSDgzZ1IvNnNL?= =?utf-8?B?KzVyYmpCemZkblJUZVRpL1FoNzZVVXNGZHVPNEpYZmRhQThxRG5IakFXR3Nz?= =?utf-8?B?eThtbW9rYXBNckpIWlozNmRUQXZhUDFJNnRtQlJKcGUyZU5MUVo2STYycERE?= =?utf-8?B?aGZXNk93cG9ZMFpPRytUN3E0Nmp5QmltM1RHb2tIVkFtbkZUWm1qczIwQWY1?= =?utf-8?B?cCt0cTFwOEt0K25xMmNROE1PTml3UEx0WDZnckFaVlpXQ1cwbkpaNThYaUNp?= =?utf-8?B?MGg0U3pycUVoT1ptV0dxbm94S2RIRy9ISXQzR1dHa1UzOFV6bEpJdWJ0SzRV?= =?utf-8?B?R1ZqUkJnZmkwaHZxb3dlWFhtaGp6eUhvc0hYRWp0SFJEMVBmc3Jkb3JMbGVM?= =?utf-8?B?YjRXd0NwLzFNVnkyd3ZUSTh4SUF5WTJCTDZWUUhvc09VdVJ5ODBGSjlWdW9u?= =?utf-8?B?NmpwWmRLRHVIYmFvSFRpOFZ3cXgySXVRL1dkdjkwVVJqdkJpOUI2bWdtd3RD?= =?utf-8?B?S2diSC9zT0pWSDJ4WFVyQTZOMHJIMXBYemFkcU1FM1c0d3dONU5oTTJneUNV?= =?utf-8?B?WUIzSlR3K213ejFkY1ZpeldKNkJLcTB6NDkxVGM0L0IvUmVWWEc0ZVJ3Wm1Y?= =?utf-8?B?eWo3d00yNThDZ1dNZStFbTFESUdvZWo0MXE5UzU5b1F5SEpkNlBTSnBlbi91?= =?utf-8?B?cHkzbU5jQkJwR0w1cFhmOVF0bkFKY1ZlWTlRcmlpV05OcHh6UzNNbmhteXJt?= =?utf-8?B?dFA0NXZmT1VxRVdUQ01NUGJmMEVzdml4cUp3MkpMeUNuZWV0UTJtOEtNRUFi?= =?utf-8?B?eTlzcTIwU0NhbG9DeVRUNko1NXUvZEYvWE1OaUdwdXFQaTk5NFdXTnVQd0hL?= =?utf-8?B?d1VGREo5eWRpQUpXTlZrenJ0UmRqUGRMcTk4OVVsbGJLbEw4MlE0d3k1a2lJ?= =?utf-8?B?bUJucHF0YVY1emFOVHJUUS9zZFhrdWlFcVd4eGx0YW5pcmt1QmVra0ZZSzc2?= =?utf-8?B?NlJ6RXk0WjA3cW1wVDBQbkhGTHY0K2UzTjR5VUVwaC96d3NjTGt1QXRZK2J1?= =?utf-8?B?SDkyaG5BUWF0ck52OHF0TjJ0L0FSQTQrVjZURWtvVXpnbjJDcy9QUzltbWs0?= =?utf-8?B?amIzMlhyZkNPd0FiZTkzam1JTHBpMElJR0hZY09oYnRIbVZVMEZFcWVkbWhs?= =?utf-8?B?bHd6ZWt3NkUwM0VHdkhjMjcraWIyVnBsMHJGaEQ1ZHovRTgyTEw0UlB0VTU5?= =?utf-8?B?dHliZE1TV1pVUTFYNEtjTGhKc3hkM1RRV2NLTE9nYTFjZGhvVHlvZlJzeC9l?= =?utf-8?B?MEdqQ1NSc1oxMkQyQVE0Z2F5SmNOSzQ2MEl5bEhNUDVqWFBWdGQ3dG44RkVw?= =?utf-8?B?WTg3Tmg5T1NaOWQyNjdkTlZBcU1EV2lYYkF0Z2FwZUJYb0lHNGRsNHMwVVNI?= =?utf-8?Q?JgWtV8uFrKW+l1MGO80EeNt8yvLIQMVuiTvFmCLV6?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 6:+kaiJVrmJ16BE8M2mBbWLYOiitGVyNcmYrzZF/cYJl4GX6kmeB5WVizppvkypg9HJPLcT72GaED0cLo3rxwge5QW53EF5RkXLYD9u2pPFWxJ+WmnfbtpygZEJOdRCtzswSOl68oGxoWuHd/7lNDiOA98swxO6b7u8Xz24gylo3lAjfv8VWOzSmpzMRnkBuNH990phevLVlZWbhzqIAweKzp24YeR1TI7/jYZwqjjMebtVzcYDWC9j7LvGkKtYOUgPG5rY9S1PsgzJ2anCdxKK/6D59zIER8v5R6bhjvtmuke5IAnzP0A9qdNbOWPKzqh+hWX1Dy9KuFe8Z5SwsEKAOBU7DH82sXTTQ4p0qJBVYE=; 5:W+1nc+Vy4EY/v2ybuQlWcjtFvv8TieqKz+XJ7DK241Kz/hX2JB2bDoyr+MMTJI1sBlh2i0q1y89spoVsipd4W/PhPhGayxnAh6ZnBaMQi1Oqvsn8sWr21RBeyx/p5LKoMhTe3kWeppDwvwmm4FdvK+ED06oop109hxnTlH8RaFo=; 24:VcaSlKKRiR8mbxkSb/26AnZpzkS3vrXwUvJKeBjJnA2NPRSmCd6aq6JUA5c8SXegsfAsWvNDsvKreLBaL+6ogvlqhOraW8eS3dOesnBdf9o=; 7:Yydl8N34mfGNkn290laNjlTS6folMqNvxwAWkNhDZXP4ZIGAOPwuBGb30H2eWUn3k3WXG8/wWWknFbFiD9y3zJF32MnIgoy0yOlicnzpnU8nZItGMpygNevFTCVtDMOPMN0atvK2kw4UVz5tMEWz2RrKMdiugH+WGjRQ5xJNLe6Vo5/wyXiJBA4BSKrUC7SopNDvha6XZSgCvFUI1ZvyTjvcwAOe3KT6ZQnQG4MwDN3JaZe6LBZiQvLOVd9Rj3Tr
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Jan 2018 22:01:37.2208 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 62e13318-c33a-4262-fcbb-08d55875b8ab
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0501MB2072
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-10_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=736 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801100301
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/pBduD6XJjREgM8gpt3YkQMUxA3Q>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 22:01:44 -0000

Maybe this is a simple question but looking at these features, is this
really the intended proper use of 'feature'?

if-feature global-connect-source;
if-feature global-default-peer-policy;
if-feature global-default-peer;
if-feature global-sa-filter;
if-feature global-sa-limit;
if-feature global-ttl-threshold;
if-feature peer-admin-enable;
if-feature peer-as;
if-feature peer-connect-source;
if-feature peer-description;
if-feature peer-key-chain;
if-feature peer-sa-limit;
if-feature peer-timer-connect-retry;
if-feature peer-timer-holdtime;
if-feature peer-timer-keepalive;
if-feature rpc-clear-sa-cache;

Is it really expected that a network-element advertise features to this
degree (either capabilities/library) that a client now needs to handle a
complex matrix of feature/element mappings in order to generate specific
schemas that may wildly branch?

Multiply this by total quantity of modules on the network-element and we
could be potentially dealing w/ a large amount of features.  Based off
my experience, I don't think many folks are aware that common models
diverge into "vendor/platform" specific w/ things such as this

On Jan 10 22:33 PM, Martin Bjorklund wrote:
> Hi,
> 
> "Reshad Rahman (rrahman)" <rrahman@cisco.com> wrote:
> > Hi,
> > 
> > I am doing YD review of draft-ietf-pim-msdp-yang-01. The YANG module
> > is small but relatively speaking thereâ€™s a big number of features
> > 17. Basically each config knob has an if-feature.
> > 
> > However keepalive-interval has a dependency on holdtime-interval via
> > must statement. Is the only way to enforce this to add â€œif-feature
> > peer-timer-holdtimeâ€� to leaf keepalive-internal?
> 
> Either that, or do:
> 
>       must "(not ../holdtime-interval)"
>          + " or (. > 1 and . < ../holdtime-interval)";
> 
> depending on which combinations they want to support.
> 
> 17 features seems quite a lot...
> 
> 
> 
> > 
> > Regards,
> > Reshad.
> > 
> >          leaf holdtime-interval {
> >            if-feature peer-timer-holdtime;
> >            type uint16;
> >            units seconds;
> >            must ". > 3";
> >            default 75;
> >            description "The SA-Hold-Down-Period of this msdp peer.";
> >          }
> >          leaf keepalive-interval {
> >            if-feature peer-timer-keepalive;
> >            type uint16;
> >            units seconds;
> >            must ". > 1 and . < ../holdtime-interval";
> >            default 60;
> >            description "The keepalive timer of this msdp peer.";
> >          }
> > 
> > 
> 
> 
> /martin
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwIGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aBisJd_9YYzR6N5-pRltfnJc9N2zHuiK6-TK5W-dx1I&s=qT9UUmnJuEAZgPli4oUG-SDeE8bzhSWR5TPTwsboSKU&e=


From nobody Wed Jan 10 14:04:44 2018
Return-Path: <rrahman@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB54126C0F for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:04:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 K759CaKVkAQA for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:04:41 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E83C126B72 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:04:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14986; q=dns/txt; s=iport; t=1515621881; x=1516831481; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=QiiL8R0Azkr151G9W4CCRaJcWfr8hB4puCeUl8okiiA=; b=EF7JMEmsJySZ93asaq1Ij1Z3sas1H0Myy/53i38MBtaiJXFdOM7k/1Mt 9UJ7ncn1eZ5tAtfMyoivxCq8J4QhtBwKkvOYpHsR0WohlShJBF4h2XH7C SwTgSW7EFmLEMwoRhRoAWOAboXcMcTE0VAoQOY6CxzkD4lz1nLk5oDJVy k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BbAQC5jVZa/5pdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJKd2Z0JweEAIokjl6BWyeRX4VRghYKGAEKhRgCGoQsPxgBAQE?= =?us-ascii?q?BAQEBAQFrKIUjAQEBAQIBAQEhSwsQAgEIEQMBAgEnAwICAiULFAkIAgQOBYlPX?= =?us-ascii?q?AgQry2CJyaKGQEBAQEBAQEBAQEBAQEBAQEBAQEBARgFhCCCFYFXghIMgnmDLwE?= =?us-ascii?q?BAoFZLQkWgmExghQgBZlyiXIClUOUDpZ0AhEZAYE7AR85JYErbxU9KgGBf4RXe?= =?us-ascii?q?IpJAYEWAQEB?=
X-IronPort-AV: E=Sophos; i="5.46,342,1511827200"; d="scan'208,217"; a="54436672"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 22:04:35 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w0AM4ZNJ018082 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Jan 2018 22:04:35 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 10 Jan 2018 16:04:34 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Wed, 10 Jan 2018 16:04:34 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Andy Bierman <andy@yumaworks.com>
CC: Martin Bjorklund <mbj@tail-f.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] Features and must-condition
Thread-Index: AQHTilaYFa81RoW2ZUea0h9DxiIyiaNuBSgAgAAFAACAAAFoAIAAAlWA
Date: Wed, 10 Jan 2018 22:04:34 +0000
Message-ID: <4AFD7535-B614-4190-B43D-88D75ED18D6A@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <54D46590-633D-4936-AFDF-C6BDE9F43968@cisco.com> <CABCOCHT7iUJ1t+FH1UqK8Bvq3Q4TS4pQ0GsMc706uNZVEcgjBw@mail.gmail.com>
In-Reply-To: <CABCOCHT7iUJ1t+FH1UqK8Bvq3Q4TS4pQ0GsMc706uNZVEcgjBw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.183]
Content-Type: multipart/alternative; boundary="_000_4AFD7535B6144190B43D88D75ED18D6Aciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/LhJfEw263qsfH2Pez0jW5-5gNUQ>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 22:04:44 -0000

--_000_4AFD7535B6144190B43D88D75ED18D6Aciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RXZlbiBpZiBjb21wbGV0ZWx5IGluZGVwZW5kZW50LCBpdCBpcyB2ZXJ5IG1lc3N5IGZvciB0aGUg
Y2xpZW50IGFzIHlvdSBtZW50aW9uZWQuDQoNCkZyb206ICdBbmR5IEJpZXJtYW4nIDxhbmR5QHl1
bWF3b3Jrcy5jb20+DQpEYXRlOiBXZWRuZXNkYXksIEphbnVhcnkgMTAsIDIwMTggYXQgNDo1NiBQ
TQ0KVG86ICJSZXNoYWQgUmFobWFuIChycmFobWFuKSIgPHJyYWhtYW5AY2lzY28uY29tPg0KQ2M6
IE1hcnRpbiBCam9ya2x1bmQgPG1iakB0YWlsLWYuY29tPiwgInlhbmctZG9jdG9yc0BpZXRmLm9y
ZyIgPHlhbmctZG9jdG9yc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBbeWFuZy1kb2N0b3JzXSBG
ZWF0dXJlcyBhbmQgbXVzdC1jb25kaXRpb24NCg0KDQoNCk9uIFdlZCwgSmFuIDEwLCAyMDE4IGF0
IDE6NTEgUE0sIFJlc2hhZCBSYWhtYW4gKHJyYWhtYW4pIDxycmFobWFuQGNpc2NvLmNvbTxtYWls
dG86cnJhaG1hbkBjaXNjby5jb20+PiB3cm90ZToNClRoYW5rcyBNYXJ0aW4uDQoNClllcyAxNyBm
ZWF0dXJlcyBpcyBhIGxvdCBmb3Igc3VjaCBhIHNtYWxsIG1vZHVsZS4gSSByZWNhbGwgd2UgaGFk
IHRoZSBwZXItY291bnRlciBmZWF0dXJlIGEgZmV3IG1vbnRocyBhZ28sIHRoYXTigJlzIHdoYXQg
YmFzaWNhbGx5IHRoaXMgbW9kZWwgaXMgZG9pbmcgYnV0IHBlciBjb25maWcuDQoNClNlZW1zIHRo
ZSBjb25jZXB0cyBhbmQgZ3VpZGVsaW5lcyBmb3IgWUFORyBjb25mb3JtYW5jZSBhcmUgc3RpbGwg
dmVyeSB1bmNsZWFyLg0KQXJlIFdHcyB0aGlua2luZyBhYm91dCB0aGUgdXRpbGl0eSB0byB0aGUg
Y2xpZW50IGRldmVsb3BlciwNCm9yIHRoZSBhYmlsaXR5IGZvciBhIHNlcnZlciBkZXZlbG9wZXIg
dG8gY2xhaW0gY29uZm9ybWFuY2Ugbm8gbWF0dGVyIHdoYXQgdGhleSBpbXBsZW1lbnQ/DQoNCkl0
IHNlZW1zIHVubGlrZWx5IHRoYXQgZWFjaCBsZWFmIGlzIGNvbXBsZXRlbHkgaW5kZXBlbmRlbnQg
b2YgYWxsIG90aGVycyB3cnQvIGZ1bmN0aW9uYWxpdHkuDQoNCg0KUmVnYXJkcywNClJlc2hhZC4N
Cg0KDQpBbmR5DQoNCg0KT24gMjAxOC0wMS0xMCwgNDozMyBQTSwgIk1hcnRpbiBCam9ya2x1bmQi
IDxtYmpAdGFpbC1mLmNvbTxtYWlsdG86bWJqQHRhaWwtZi5jb20+PiB3cm90ZToNCg0KICAgIEhp
LA0KDQogICAgIlJlc2hhZCBSYWhtYW4gKHJyYWhtYW4pIiA8cnJhaG1hbkBjaXNjby5jb208bWFp
bHRvOnJyYWhtYW5AY2lzY28uY29tPj4gd3JvdGU6DQogICAgPiBIaSwNCiAgICA+DQogICAgPiBJ
IGFtIGRvaW5nIFlEIHJldmlldyBvZiBkcmFmdC1pZXRmLXBpbS1tc2RwLXlhbmctMDEuIFRoZSBZ
QU5HIG1vZHVsZQ0KICAgID4gaXMgc21hbGwgYnV0IHJlbGF0aXZlbHkgc3BlYWtpbmcgdGhlcmXi
gJlzIGEgYmlnIG51bWJlciBvZiBmZWF0dXJlcw0KICAgID4gMTcuIEJhc2ljYWxseSBlYWNoIGNv
bmZpZyBrbm9iIGhhcyBhbiBpZi1mZWF0dXJlLg0KICAgID4NCiAgICA+IEhvd2V2ZXIga2VlcGFs
aXZlLWludGVydmFsIGhhcyBhIGRlcGVuZGVuY3kgb24gaG9sZHRpbWUtaW50ZXJ2YWwgdmlhDQog
ICAgPiBtdXN0IHN0YXRlbWVudC4gSXMgdGhlIG9ubHkgd2F5IHRvIGVuZm9yY2UgdGhpcyB0byBh
ZGQg4oCcaWYtZmVhdHVyZQ0KICAgID4gcGVlci10aW1lci1ob2xkdGltZeKAnSB0byBsZWFmIGtl
ZXBhbGl2ZS1pbnRlcm5hbD8NCg0KICAgIEVpdGhlciB0aGF0LCBvciBkbzoNCg0KICAgICAgICAg
IG11c3QgIihub3QgLi4vaG9sZHRpbWUtaW50ZXJ2YWwpIg0KICAgICAgICAgICAgICsgIiBvciAo
LiA+IDEgYW5kIC4gPCAuLi9ob2xkdGltZS1pbnRlcnZhbCkiOw0KDQogICAgZGVwZW5kaW5nIG9u
IHdoaWNoIGNvbWJpbmF0aW9ucyB0aGV5IHdhbnQgdG8gc3VwcG9ydC4NCg0KICAgIDE3IGZlYXR1
cmVzIHNlZW1zIHF1aXRlIGEgbG90Li4uDQoNCg0KDQogICAgPg0KICAgID4gUmVnYXJkcywNCiAg
ICA+IFJlc2hhZC4NCiAgICA+DQogICAgPiAgICAgICAgICBsZWFmIGhvbGR0aW1lLWludGVydmFs
IHsNCiAgICA+ICAgICAgICAgICAgaWYtZmVhdHVyZSBwZWVyLXRpbWVyLWhvbGR0aW1lOw0KICAg
ID4gICAgICAgICAgICB0eXBlIHVpbnQxNjsNCiAgICA+ICAgICAgICAgICAgdW5pdHMgc2Vjb25k
czsNCiAgICA+ICAgICAgICAgICAgbXVzdCAiLiA+IDMiOw0KICAgID4gICAgICAgICAgICBkZWZh
dWx0IDc1Ow0KICAgID4gICAgICAgICAgICBkZXNjcmlwdGlvbiAiVGhlIFNBLUhvbGQtRG93bi1Q
ZXJpb2Qgb2YgdGhpcyBtc2RwIHBlZXIuIjsNCiAgICA+ICAgICAgICAgIH0NCiAgICA+ICAgICAg
ICAgIGxlYWYga2VlcGFsaXZlLWludGVydmFsIHsNCiAgICA+ICAgICAgICAgICAgaWYtZmVhdHVy
ZSBwZWVyLXRpbWVyLWtlZXBhbGl2ZTsNCiAgICA+ICAgICAgICAgICAgdHlwZSB1aW50MTY7DQog
ICAgPiAgICAgICAgICAgIHVuaXRzIHNlY29uZHM7DQogICAgPiAgICAgICAgICAgIG11c3QgIi4g
PiAxIGFuZCAuIDwgLi4vaG9sZHRpbWUtaW50ZXJ2YWwiOw0KICAgID4gICAgICAgICAgICBkZWZh
dWx0IDYwOw0KICAgID4gICAgICAgICAgICBkZXNjcmlwdGlvbiAiVGhlIGtlZXBhbGl2ZSB0aW1l
ciBvZiB0aGlzIG1zZHAgcGVlci4iOw0KICAgID4gICAgICAgICAgfQ0KICAgID4NCiAgICA+DQoN
Cg0KICAgIC9tYXJ0aW4NCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KeWFuZy1kb2N0b3JzIG1haWxpbmcgbGlzdA0KeWFuZy1kb2N0b3JzQGlldGYu
b3JnPG1haWx0bzp5YW5nLWRvY3RvcnNAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL3lhbmctZG9jdG9ycw0KDQo=

--_000_4AFD7535B6144190B43D88D75ED18D6Aciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <7FADB778A738EC40BB1665690FAEB36D@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0Ow0K
CWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0eWxlOm5vcm1hbDt9DQpzcGFuLm1zb0lucw0K
CXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUtbmFtZToiIjsNCgl0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7
bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBX
b3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4w
cHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0iRU4t
VVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24x
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkV2ZW4gaWYgY29tcGxldGVseSBpbmRlcGVuZGVudCwg
aXQgaXMgdmVyeSBtZXNzeSBmb3IgdGhlIGNsaWVudCBhcyB5b3UgbWVudGlvbmVkLjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGlu
ZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+RnJvbTogPC9zcGFuPjwvYj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+J0FuZHkgQmllcm1hbicgJmx0O2Fu
ZHlAeXVtYXdvcmtzLmNvbSZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+V2VkbmVzZGF5LCBKYW51YXJ5
IDEwLCAyMDE4IGF0IDQ6NTYgUE08YnI+DQo8Yj5UbzogPC9iPiZxdW90O1Jlc2hhZCBSYWhtYW4g
KHJyYWhtYW4pJnF1b3Q7ICZsdDtycmFobWFuQGNpc2NvLmNvbSZndDs8YnI+DQo8Yj5DYzogPC9i
Pk1hcnRpbiBCam9ya2x1bmQgJmx0O21iakB0YWlsLWYuY29tJmd0OywgJnF1b3Q7eWFuZy1kb2N0
b3JzQGlldGYub3JnJnF1b3Q7ICZsdDt5YW5nLWRvY3RvcnNAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+
U3ViamVjdDogPC9iPlJlOiBbeWFuZy1kb2N0b3JzXSBGZWF0dXJlcyBhbmQgbXVzdC1jb25kaXRp
b248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFdl
ZCwgSmFuIDEwLCAyMDE4IGF0IDE6NTEgUE0sIFJlc2hhZCBSYWhtYW4gKHJyYWhtYW4pICZsdDs8
YSBocmVmPSJtYWlsdG86cnJhaG1hbkBjaXNjby5jb20iIHRhcmdldD0iX2JsYW5rIj5ycmFobWFu
QGNpc2NvLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+VGhhbmtzIE1h
cnRpbi48YnI+DQo8YnI+DQpZZXMgMTcgZmVhdHVyZXMgaXMgYSBsb3QgZm9yIHN1Y2ggYSBzbWFs
bCBtb2R1bGUuIEkgcmVjYWxsIHdlIGhhZCB0aGUgcGVyLWNvdW50ZXIgZmVhdHVyZSBhIGZldyBt
b250aHMgYWdvLCB0aGF04oCZcyB3aGF0IGJhc2ljYWxseSB0aGlzIG1vZGVsIGlzIGRvaW5nIGJ1
dCBwZXIgY29uZmlnLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+U2VlbXMgdGhlIGNvbmNlcHRzIGFuZCBndWlkZWxpbmVzIGZvciBZ
QU5HIGNvbmZvcm1hbmNlIGFyZSBzdGlsbCB2ZXJ5IHVuY2xlYXIuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcmUgV0dzIHRoaW5raW5nIGFib3V0
IHRoZSB1dGlsaXR5IHRvIHRoZSBjbGllbnQgZGV2ZWxvcGVyLDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+b3IgdGhlIGFiaWxpdHkgZm9yIGEgc2Vy
dmVyIGRldmVsb3BlciB0byBjbGFpbSBjb25mb3JtYW5jZSBubyBtYXR0ZXIgd2hhdCB0aGV5IGlt
cGxlbWVudD88bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SXQgc2VlbXMgdW5saWtlbHkgdGhhdCBlYWNoIGxlYWYgaXMgY29tcGxldGVseSBpbmRl
cGVuZGVudCBvZiBhbGwgb3RoZXJzIHdydC8gZnVuY3Rpb25hbGl0eS48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luLWJvdHRvbToxMi4wcHQiPlJlZ2FyZHMsPGJyPg0KUmVzaGFkLjxvOnA+PC9vOnA+PC9wPg0K
PC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbmR5PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21h
cmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
T24gMjAxOC0wMS0xMCwgNDozMyBQTSwgJnF1b3Q7TWFydGluIEJqb3JrbHVuZCZxdW90OyAmbHQ7
PGEgaHJlZj0ibWFpbHRvOm1iakB0YWlsLWYuY29tIj5tYmpAdGFpbC1mLmNvbTwvYT4mZ3Q7IHdy
b3RlOjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgSGksPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNw
OyAmcXVvdDtSZXNoYWQgUmFobWFuIChycmFobWFuKSZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRv
OnJyYWhtYW5AY2lzY28uY29tIj5ycmFobWFuQGNpc2NvLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4N
CiZuYnNwOyAmbmJzcDsgJmd0OyBIaSw8YnI+DQombmJzcDsgJm5ic3A7ICZndDs8YnI+DQombmJz
cDsgJm5ic3A7ICZndDsgSSBhbSBkb2luZyBZRCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1waW0tbXNk
cC15YW5nLTAxLiBUaGUgWUFORyBtb2R1bGU8YnI+DQombmJzcDsgJm5ic3A7ICZndDsgaXMgc21h
bGwgYnV0IHJlbGF0aXZlbHkgc3BlYWtpbmcgdGhlcmXigJlzIGEgYmlnIG51bWJlciBvZiBmZWF0
dXJlczxicj4NCiZuYnNwOyAmbmJzcDsgJmd0OyAxNy4gQmFzaWNhbGx5IGVhY2ggY29uZmlnIGtu
b2IgaGFzIGFuIGlmLWZlYXR1cmUuPGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7PGJyPg0KJm5ic3A7
ICZuYnNwOyAmZ3Q7IEhvd2V2ZXIga2VlcGFsaXZlLWludGVydmFsIGhhcyBhIGRlcGVuZGVuY3kg
b24gaG9sZHRpbWUtaW50ZXJ2YWwgdmlhPGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7IG11c3Qgc3Rh
dGVtZW50LiBJcyB0aGUgb25seSB3YXkgdG8gZW5mb3JjZSB0aGlzIHRvIGFkZCDigJxpZi1mZWF0
dXJlPGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7IHBlZXItdGltZXItaG9sZHRpbWXigJ0gdG8gbGVh
ZiBrZWVwYWxpdmUtaW50ZXJuYWw/PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBFaXRoZXIgdGhh
dCwgb3IgZG86PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBt
dXN0ICZxdW90Oyhub3QgLi4vaG9sZHRpbWUtaW50ZXJ2YWwpJnF1b3Q7PGJyPg0KJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7JiM0MzsgJnF1b3Q7IG9yICgu
ICZndDsgMSBhbmQgLiAmbHQ7IC4uL2hvbGR0aW1lLWludGVydmFsKSZxdW90Ozs8YnI+DQo8YnI+
DQombmJzcDsgJm5ic3A7IGRlcGVuZGluZyBvbiB3aGljaCBjb21iaW5hdGlvbnMgdGhleSB3YW50
IHRvIHN1cHBvcnQuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAxNyBmZWF0dXJlcyBzZWVtcyBx
dWl0ZSBhIGxvdC4uLjxicj4NCjxicj4NCjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJmd0Ozxi
cj4NCiZuYnNwOyAmbmJzcDsgJmd0OyBSZWdhcmRzLDxicj4NCiZuYnNwOyAmbmJzcDsgJmd0OyBS
ZXNoYWQuPGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7PGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBsZWFmIGhvbGR0aW1lLWludGVydmFsIHs8
YnI+DQombmJzcDsgJm5ic3A7ICZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBpZi1mZWF0dXJlIHBlZXItdGltZXItaG9sZHRpbWU7PGJyPg0KJm5ic3A7ICZuYnNw
OyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgdHlwZSB1aW50
MTY7PGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgdW5pdHMgc2Vjb25kczs8YnI+DQombmJzcDsgJm5ic3A7ICZndDsmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBtdXN0ICZxdW90Oy4gJmd0OyAzJnF1
b3Q7Ozxicj4NCiZuYnNwOyAmbmJzcDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7IGRlZmF1bHQgNzU7PGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgZGVzY3JpcHRpb24gJnF1b3Q7VGhlIFNB
LUhvbGQtRG93bi1QZXJpb2Qgb2YgdGhpcyBtc2RwIHBlZXIuJnF1b3Q7Ozxicj4NCiZuYnNwOyAm
bmJzcDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfTxicj4NCiZuYnNw
OyAmbmJzcDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgbGVhZiBrZWVw
YWxpdmUtaW50ZXJ2YWwgezxicj4NCiZuYnNwOyAmbmJzcDsgJmd0OyZuYnNwOyAmbmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IGlmLWZlYXR1cmUgcGVlci10aW1lci1rZWVwYWxpdmU7
PGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgdHlwZSB1aW50MTY7PGJyPg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgdW5pdHMgc2Vjb25kczs8YnI+DQombmJzcDsg
Jm5ic3A7ICZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBtdXN0
ICZxdW90Oy4gJmd0OyAxIGFuZCAuICZsdDsgLi4vaG9sZHRpbWUtaW50ZXJ2YWwmcXVvdDs7PGJy
Pg0KJm5ic3A7ICZuYnNwOyAmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgZGVmYXVsdCA2MDs8YnI+DQombmJzcDsgJm5ic3A7ICZndDsmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBkZXNjcmlwdGlvbiAmcXVvdDtUaGUga2VlcGFsaXZl
IHRpbWVyIG9mIHRoaXMgbXNkcCBwZWVyLiZxdW90Ozs8YnI+DQombmJzcDsgJm5ic3A7ICZndDsm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IH08YnI+DQombmJzcDsgJm5ic3A7ICZn
dDs8YnI+DQombmJzcDsgJm5ic3A7ICZndDs8YnI+DQo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
IC9tYXJ0aW48YnI+DQo8YnI+DQo8YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXzxicj4NCnlhbmctZG9jdG9ycyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBo
cmVmPSJtYWlsdG86eWFuZy1kb2N0b3JzQGlldGYub3JnIj55YW5nLWRvY3RvcnNAaWV0Zi5vcmc8
L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby95
YW5nLWRvY3RvcnMiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3lhbmctZG9jdG9yczwvYT48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_4AFD7535B6144190B43D88D75ED18D6Aciscocom_--


From nobody Wed Jan 10 14:06:05 2018
Return-Path: <rrahman@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDE0126C0F for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:06:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 ZpESirgSVSbM for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:06:01 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC811126B72 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:06:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4874; q=dns/txt; s=iport; t=1515621961; x=1516831561; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4E9588HWSLurKg9vqZ81i+rnAXZzGxUKM2aq1mA/u54=; b=BH6wPzVZPQYDyyXnljpRte88BQjcuHnr2xEWbbC7USODZHgXfidhUmpr dttwP5K62mZq062RmZiSmIVKomzR6/1RN+3oPgyjOd64cQnicDTqEYT6D 7Q3YPdDdnj2jzrdAS0rPOi6lPHLlCslUlJWod+O0WODZLujiDDcJqeQcF c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AoAQC5jVZa/4ENJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNBZnQnB4QAiiSOXoIClzCCFgofhRwCGoQsPxgBAQEBAQEBAQF?= =?us-ascii?q?rKIUkAQUjEToLEAIBCA4KAgImAgICMBUQAgQBDQWKM689gieKPwEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAR2BD4MRghWBV4ISgwWDLwSBSSYXgwAxghQgBaNkAogJg3a?= =?us-ascii?q?JRIJ/kQ+WdAIRGQGBOwEfOYFQbxU9KgGBfwmETniJFoEzAYEWAQEB?=
X-IronPort-AV: E=Sophos;i="5.46,342,1511827200"; d="scan'208";a="54437166"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 22:06:01 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id w0AM60Bw022819 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Jan 2018 22:06:01 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 10 Jan 2018 16:06:00 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Wed, 10 Jan 2018 16:06:00 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Ebben Aries <exa@juniper.net>, Martin Bjorklund <mbj@tail-f.com>
CC: "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] Features and must-condition
Thread-Index: AQHTilaYFa81RoW2ZUea0h9DxiIyiaNuBSgAgAAH5ICAAAFAgA==
Date: Wed, 10 Jan 2018 22:06:00 +0000
Message-ID: <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net>
In-Reply-To: <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.183]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E04560D0B7475C49B06DB9179FD11E21@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/hn0s-vmzHl0S80TVqXWy2N9pueA>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 22:06:03 -0000

SSBkb27igJl0IGJlbGlldmUgdGhpcyB3YXMgdGhlIGludGVudCwgYnV0IHRoaXMgaXMgaG93IGl0
4oCZcyBiZWluZyB1c2VkIHNvIHRoYXQgaW1wbGVtZW50YXRpb25zIGNhbiBjbGFpbSBjb21wYXRp
YmlsaXR54oCmLg0KDQoNCk9uIDIwMTgtMDEtMTAsIDU6MDEgUE0sICJFYmJlbiBBcmllcyIgPGV4
YUBqdW5pcGVyLm5ldD4gd3JvdGU6DQoNCiAgICBNYXliZSB0aGlzIGlzIGEgc2ltcGxlIHF1ZXN0
aW9uIGJ1dCBsb29raW5nIGF0IHRoZXNlIGZlYXR1cmVzLCBpcyB0aGlzDQogICAgcmVhbGx5IHRo
ZSBpbnRlbmRlZCBwcm9wZXIgdXNlIG9mICdmZWF0dXJlJz8NCiAgICANCiAgICBpZi1mZWF0dXJl
IGdsb2JhbC1jb25uZWN0LXNvdXJjZTsNCiAgICBpZi1mZWF0dXJlIGdsb2JhbC1kZWZhdWx0LXBl
ZXItcG9saWN5Ow0KICAgIGlmLWZlYXR1cmUgZ2xvYmFsLWRlZmF1bHQtcGVlcjsNCiAgICBpZi1m
ZWF0dXJlIGdsb2JhbC1zYS1maWx0ZXI7DQogICAgaWYtZmVhdHVyZSBnbG9iYWwtc2EtbGltaXQ7
DQogICAgaWYtZmVhdHVyZSBnbG9iYWwtdHRsLXRocmVzaG9sZDsNCiAgICBpZi1mZWF0dXJlIHBl
ZXItYWRtaW4tZW5hYmxlOw0KICAgIGlmLWZlYXR1cmUgcGVlci1hczsNCiAgICBpZi1mZWF0dXJl
IHBlZXItY29ubmVjdC1zb3VyY2U7DQogICAgaWYtZmVhdHVyZSBwZWVyLWRlc2NyaXB0aW9uOw0K
ICAgIGlmLWZlYXR1cmUgcGVlci1rZXktY2hhaW47DQogICAgaWYtZmVhdHVyZSBwZWVyLXNhLWxp
bWl0Ow0KICAgIGlmLWZlYXR1cmUgcGVlci10aW1lci1jb25uZWN0LXJldHJ5Ow0KICAgIGlmLWZl
YXR1cmUgcGVlci10aW1lci1ob2xkdGltZTsNCiAgICBpZi1mZWF0dXJlIHBlZXItdGltZXIta2Vl
cGFsaXZlOw0KICAgIGlmLWZlYXR1cmUgcnBjLWNsZWFyLXNhLWNhY2hlOw0KICAgIA0KICAgIElz
IGl0IHJlYWxseSBleHBlY3RlZCB0aGF0IGEgbmV0d29yay1lbGVtZW50IGFkdmVydGlzZSBmZWF0
dXJlcyB0byB0aGlzDQogICAgZGVncmVlIChlaXRoZXIgY2FwYWJpbGl0aWVzL2xpYnJhcnkpIHRo
YXQgYSBjbGllbnQgbm93IG5lZWRzIHRvIGhhbmRsZSBhDQogICAgY29tcGxleCBtYXRyaXggb2Yg
ZmVhdHVyZS9lbGVtZW50IG1hcHBpbmdzIGluIG9yZGVyIHRvIGdlbmVyYXRlIHNwZWNpZmljDQog
ICAgc2NoZW1hcyB0aGF0IG1heSB3aWxkbHkgYnJhbmNoPw0KICAgIA0KICAgIE11bHRpcGx5IHRo
aXMgYnkgdG90YWwgcXVhbnRpdHkgb2YgbW9kdWxlcyBvbiB0aGUgbmV0d29yay1lbGVtZW50IGFu
ZCB3ZQ0KICAgIGNvdWxkIGJlIHBvdGVudGlhbGx5IGRlYWxpbmcgdy8gYSBsYXJnZSBhbW91bnQg
b2YgZmVhdHVyZXMuICBCYXNlZCBvZmYNCiAgICBteSBleHBlcmllbmNlLCBJIGRvbid0IHRoaW5r
IG1hbnkgZm9sa3MgYXJlIGF3YXJlIHRoYXQgY29tbW9uIG1vZGVscw0KICAgIGRpdmVyZ2UgaW50
byAidmVuZG9yL3BsYXRmb3JtIiBzcGVjaWZpYyB3LyB0aGluZ3Mgc3VjaCBhcyB0aGlzDQogICAg
DQogICAgT24gSmFuIDEwIDIyOjMzIFBNLCBNYXJ0aW4gQmpvcmtsdW5kIHdyb3RlOg0KICAgID4g
SGksDQogICAgPiANCiAgICA+ICJSZXNoYWQgUmFobWFuIChycmFobWFuKSIgPHJyYWhtYW5AY2lz
Y28uY29tPiB3cm90ZToNCiAgICA+ID4gSGksDQogICAgPiA+IA0KICAgID4gPiBJIGFtIGRvaW5n
IFlEIHJldmlldyBvZiBkcmFmdC1pZXRmLXBpbS1tc2RwLXlhbmctMDEuIFRoZSBZQU5HIG1vZHVs
ZQ0KICAgID4gPiBpcyBzbWFsbCBidXQgcmVsYXRpdmVseSBzcGVha2luZyB0aGVyZeKAmXMgYSBi
aWcgbnVtYmVyIG9mIGZlYXR1cmVzDQogICAgPiA+IDE3LiBCYXNpY2FsbHkgZWFjaCBjb25maWcg
a25vYiBoYXMgYW4gaWYtZmVhdHVyZS4NCiAgICA+ID4gDQogICAgPiA+IEhvd2V2ZXIga2VlcGFs
aXZlLWludGVydmFsIGhhcyBhIGRlcGVuZGVuY3kgb24gaG9sZHRpbWUtaW50ZXJ2YWwgdmlhDQog
ICAgPiA+IG11c3Qgc3RhdGVtZW50LiBJcyB0aGUgb25seSB3YXkgdG8gZW5mb3JjZSB0aGlzIHRv
IGFkZCDigJxpZi1mZWF0dXJlDQogICAgPiA+IHBlZXItdGltZXItaG9sZHRpbWXigJ0gdG8gbGVh
ZiBrZWVwYWxpdmUtaW50ZXJuYWw/DQogICAgPiANCiAgICA+IEVpdGhlciB0aGF0LCBvciBkbzoN
CiAgICA+IA0KICAgID4gICAgICAgbXVzdCAiKG5vdCAuLi9ob2xkdGltZS1pbnRlcnZhbCkiDQog
ICAgPiAgICAgICAgICArICIgb3IgKC4gPiAxIGFuZCAuIDwgLi4vaG9sZHRpbWUtaW50ZXJ2YWwp
IjsNCiAgICA+IA0KICAgID4gZGVwZW5kaW5nIG9uIHdoaWNoIGNvbWJpbmF0aW9ucyB0aGV5IHdh
bnQgdG8gc3VwcG9ydC4NCiAgICA+IA0KICAgID4gMTcgZmVhdHVyZXMgc2VlbXMgcXVpdGUgYSBs
b3QuLi4NCiAgICA+IA0KICAgID4gDQogICAgPiANCiAgICA+ID4gDQogICAgPiA+IFJlZ2FyZHMs
DQogICAgPiA+IFJlc2hhZC4NCiAgICA+ID4gDQogICAgPiA+ICAgICAgICAgIGxlYWYgaG9sZHRp
bWUtaW50ZXJ2YWwgew0KICAgID4gPiAgICAgICAgICAgIGlmLWZlYXR1cmUgcGVlci10aW1lci1o
b2xkdGltZTsNCiAgICA+ID4gICAgICAgICAgICB0eXBlIHVpbnQxNjsNCiAgICA+ID4gICAgICAg
ICAgICB1bml0cyBzZWNvbmRzOw0KICAgID4gPiAgICAgICAgICAgIG11c3QgIi4gPiAzIjsNCiAg
ICA+ID4gICAgICAgICAgICBkZWZhdWx0IDc1Ow0KICAgID4gPiAgICAgICAgICAgIGRlc2NyaXB0
aW9uICJUaGUgU0EtSG9sZC1Eb3duLVBlcmlvZCBvZiB0aGlzIG1zZHAgcGVlci4iOw0KICAgID4g
PiAgICAgICAgICB9DQogICAgPiA+ICAgICAgICAgIGxlYWYga2VlcGFsaXZlLWludGVydmFsIHsN
CiAgICA+ID4gICAgICAgICAgICBpZi1mZWF0dXJlIHBlZXItdGltZXIta2VlcGFsaXZlOw0KICAg
ID4gPiAgICAgICAgICAgIHR5cGUgdWludDE2Ow0KICAgID4gPiAgICAgICAgICAgIHVuaXRzIHNl
Y29uZHM7DQogICAgPiA+ICAgICAgICAgICAgbXVzdCAiLiA+IDEgYW5kIC4gPCAuLi9ob2xkdGlt
ZS1pbnRlcnZhbCI7DQogICAgPiA+ICAgICAgICAgICAgZGVmYXVsdCA2MDsNCiAgICA+ID4gICAg
ICAgICAgICBkZXNjcmlwdGlvbiAiVGhlIGtlZXBhbGl2ZSB0aW1lciBvZiB0aGlzIG1zZHAgcGVl
ci4iOw0KICAgID4gPiAgICAgICAgICB9DQogICAgPiA+IA0KICAgID4gPiANCiAgICA+IA0KICAg
ID4gDQogICAgPiAvbWFydGluDQogICAgPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXw0KICAgID4geWFuZy1kb2N0b3JzIG1haWxpbmcgbGlzdA0KICAgID4g
eWFuZy1kb2N0b3JzQGlldGYub3JnDQogICAgPiBodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2lu
dC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3d3dy5pZXRmLm9yZ19tYWlsbWFuX2xpc3RpbmZvX3lh
bmctMkRkb2N0b3JzJmQ9RHdJR2FRJmM9SEFrWXVoNjNyc3VocjZTY2JmaDBVakJYZU1LLW5kYjN2
b0RUWGNXem9DSSZyPUdJZWhiRHBRbG8zMWxTaTZXYm5Fa0EmbT1hQmlzSmRfOVlZelI2TjUtcFJs
dGZuSmM5TjJ6SHVpSzYtVEs1Vy1keDFJJnM9cVQ5VVVtbkp1RUFaZ1BsaTRvVUctU0RlRThiemhT
V1I1VFBUd3Nib1NLVSZlPQ0KICAgIA0KDQo=


From nobody Wed Jan 10 14:26:29 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D5B126BF6 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 jcOTnrLxmloM for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:26:24 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 B006F127241 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:26:18 -0800 (PST)
Received: from pps.filterd (m0108159.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0AMOMRN027401; Wed, 10 Jan 2018 14:26:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to; s=PPS1017; bh=X2c1x/F+zt48ayob/WD0HjHRywsuk4KHOOQPnw+MWBE=; b=mYUsg7GBv6POMK0IDjwWi5UmqQnYA6pF+G6HyQ0UdrU2qWeDqBHDCdhamdyCbZ4rJpHv 82EZXuDT/wARKT/4pHjUDsRW1TluilJj+Sg0oWRCMocsS+Wx78OYa1FrlHUjCnjnwE08 MTWeMAMZ+h0LFqKkTNI5KZbc+BnAkhvB06OLGhzJBnN5iQA8tvE/mIrMb8MFHURFuPCT ex23ZjtRF8bLFlU32jWxa3ExqiRRDCObNPLpe+V9MkidfF3JfWu9meIpVOEp5FWt7+v7 fO41doKC4UH2yrXJDJDB2osaKfcyVyP+QnctX0CDJos89bYUNssRJvP4XTsFc/VtRbfy lA== 
Received: from nam01-bn3-obe.outbound.protection.outlook.com (mail-bn3nam01lp0180.outbound.protection.outlook.com [216.32.180.180]) by mx0a-00273201.pphosted.com with ESMTP id 2fds2ggdad-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 10 Jan 2018 14:26:17 -0800
Received: from SN1PR0501CA0003.namprd05.prod.outlook.com (10.163.126.141) by SN1PR0501MB2078.namprd05.prod.outlook.com (10.163.227.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.1; Wed, 10 Jan 2018 22:26:15 +0000
Received: from DM3NAM05FT054.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::205) by SN1PR0501CA0003.outlook.office365.com (2a01:111:e400:52fe::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.407.1 via Frontend Transport; Wed, 10 Jan 2018 22:26:15 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT054.mail.protection.outlook.com (10.152.98.168) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.345.12 via Frontend Transport; Wed, 10 Jan 2018 22:26:15 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 10 Jan 2018 14:26:11 -0800
Date: Wed, 10 Jan 2018 15:26:10 -0700
From: Ebben Aries <exa@juniper.net>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
CC: Martin Bjorklund <mbj@tail-f.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(346002)(39380400002)(396003)(39860400002)(376002)(2980300002)(189003)(199004)(377424004)(24454002)(575784001)(6246003)(356003)(53936002)(105596002)(77096006)(6306002)(2906002)(2870700001)(55016002)(305945005)(106466001)(47776003)(93886005)(4326008)(86362001)(104016004)(316002)(1076002)(229853002)(5660300001)(7696005)(59450400001)(50466002)(68736007)(2486003)(23676004)(69596002)(6916009)(2950100002)(76176011)(53416004)(97736004)(53546011)(54906003)(966005)(478600001)(8676002)(81156014)(8936002)(81166006)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0501MB2078; H:P-EMFE01C-SAC.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT054; 1:bD+agb7v4mvHbnbQNsN+vKmJbWLuMBmIOOP4XDUXvlFOJ0kxw25zt7zk4JQHMHslC3ujcT5lt4oJs3o4tp4vDo1JlzrOkLwy4p/YaHrHdzJwyumIy3j85m40z3C69n/A
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 016e8124-d0b8-482f-2b5f-08d5587929a4
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:SN1PR0501MB2078; 
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0501MB2078; 3:O/v74FbQMwKzYPn8ZDTJ6EN8eVU3CneoakW/qX8uU6/IKTvWFN2QfKdmEHQzJe8XXGWzKgavcLPgjI8upBYbDVp0SmhKZZEjqefzNcYz0pDgWCTemBJQk6pvlZ8XdTIIfNe5c//0bsb3Af6IBQ31V14rzifrQ41J3agqdBfjpWM/kdNvMf0YmDZQK+3/FALPnfzJr6FmRPiWJrAUzj4xjVO+W9tHcgp8apRjYRk0G+Ctt+l1oqs6DtzeoWBAzPbYYJSXhcfa2mBYtSS6GSbvt/uxvnoj8gojuRESoYmBxqsRfv5COR4iiEtDAdklN+btT54P1Q4qAR4Kb5Grq4s7TWiZXKeCReG9tGS8qkBd/1Q=; 25:xkg/60g9ECoi3zz00RgLi/81vtZnr2bW/OjZI3vvakwZnSVZ77vZG7/E0DMziWT8bsaYFJz+yLPFdQt6TNliggFpbu89+mRAvVC9umquod8ZLR6ap8PzpcsA01TS8o2IVzxJLckJ5EkIF+V5b3dH2+8k/TNdkszhpdRPy4UE8eQsvPWdfvVNsWPZPSpvM835UnXTeqXaLGT/wAe/jf6d7l4zOwL98Pb0aucFRVOMJGOPwsD7wiiCVcOStbryxBtQLBqzQXAV+gQ2Iq3SrMtxbB0paGcUkl0tg2LUvtev1BzU5PaL68D3uoD22hs2DuflfpQjyTn7OdjHWx5L301n5A==
X-MS-TrafficTypeDiagnostic: SN1PR0501MB2078:
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0501MB2078; 31:w3HseEm0W/zPn8lhSBDSuUJUWRvdEDeIKlA/EqP3msTlyIAKMqknKMbsoVexCCWV952BRz1IAJeUNinwpwfIG4yfgEj1dj2NYAggGumcZH9g9tMzD8Eb/CX6hKkZcDcw3ZB3b36tlQxEqI7g1uSg1UOCbB40kMfBK/N3Sd6JboEc8x7tl8h/O9KaBOtRgqOUibxeezw1DSoo6XjW/aTrJ1F2u1I+vS0IzoLkBGmudgo=; 20:xnLOUkKVazivik7Fr8kvbRvGFfCF4s+gl742arQBgINfcdDFF5+yC9opC2w9YDuAUcs5AsMPOS6q+Qh5zzaEoPsKke9Qfcq3Xq/tnr0AxK7twbmfzq3DFC2ut3CojYnA6xjw1uilDvuR2F0v+gYdaUQfFGwQrEFG7zg7789fiKq0sj99GpYOk/zK/Q0ievd6SYfNeyVc4SgnYYWg0K4cZmEXdhdF9hEbrTEGPahBTvozNCf+8L2QB3E7fzvaO23gxJNznobMbrZY4oIsDxgPNx6UJBXnoZA5AA6sZeG7UQWBOWfnESORvwAPVvDm6eMaOzJouwS08C4021V9/lbQHkXB2wq9dwMLYKWIFQhZ7ZlxWc5kp5nq2TTZjlcFadljM47NjQKzwRYpqBfyGi7SGE14sajrJvTO4xPnqXHwZo1Gvgyb8gDCXQ1j8K6fjIZVimm5HL6C6mZTKrDmHlLxehEg2xyJaYVO6Ha60rl0Rl1DqMsaPOqJiXbHum4ziZ+R
X-Microsoft-Antispam-PRVS: <SN1PR0501MB2078EA7552E57A6C8731387CA8110@SN1PR0501MB2078.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(10436049006162)(138986009662008)(95692535739014); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(10201501046)(3231023)(944501075)(93006095)(93001095)(3002001)(6055026)(6041268)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(20161123560045)(6072148)(201708071742011); SRVR:SN1PR0501MB2078; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:SN1PR0501MB2078; 
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0501MB2078; 4:2DVxLyMEyPpv7jejSc5rSWtAzo/ZZ6zN3yFGOanOgq6CJXCwIPN7ASb+//2Ol65Ov01+q9jRad2wwn8WcFMexyZ8xSxWeGy7gJNP1xgZW/rRyAHTuEp6s3PGWyRBX/bjvr2Grpi4z58fRJOSCaQu2BFNppzUfmPVe6KJA3Wlhx2pwDkKpFb36WfHnjxLgurSfObpor0Zu3FpprYWVTYeDMWKMQyy4ohzJHkIQq4afeCIf20GPV9ujGuUSB3vXTpAhz16GVOr3tD6SEU62k5z7VcGOK1FKqXH1ClPRX/XxZwFuvAOY3gE43V1yh+BnDRjsYiKAULxHG94i3gU1ehK6SInPd5qgVIaVsYCVaDnQuAeht9KzJykFEX5pwe/rN0z
X-Forefront-PRVS: 0548586081
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtTTjFQUjA1MDFNQjIwNzg7MjM6VmRyTXIzMG9qeCs5em1UME9ZMWlMcFBr?= =?utf-8?B?ZUNFRWRBdVlGLzkwUzY3aktmR2Q4d0JiZTlOajNUKytxTkdtMEJZeEdIUUs2?= =?utf-8?B?aU40WVpkTTVnNVZNdFY1THRib1JJTk5oSE91MStoTHRHL3VkUkd2RkY4RFVy?= =?utf-8?B?bFVKVGtIVGN2QjNCMzVsdThyRXhnOTFjVWUyb2xkS2RsdnVZczd0bDBvZ1NZ?= =?utf-8?B?azZvejZtL2VwNjNQa1BQSHdWSjVrTWgwTHRYS0I1QmdMZ3Bvd2tTRGgyY3Zx?= =?utf-8?B?bnRBWjc1SFJwMGw1cWM1dTJna3psQWNRRUU4M3JUVEtiWnV6UVphVk1ldHYw?= =?utf-8?B?b2JsTlJnWStRZGF5UXFObVVkK3VUbzA2S2YvY2NKQ2xOM1JkeUNzWi9SakRB?= =?utf-8?B?VXNkWUpRMGVPR3NOM1JuaXJNRGtaL3NrY0owcWxNK2lzMEk4dVNoaDdaeklQ?= =?utf-8?B?UEZsNlVPcVA4aWZwRElNb2pFOGd6OWlFVzB2ZDVENVIzandJWXhWeEx0REVJ?= =?utf-8?B?eGorMm81eVlmekpQazUrcXpqRlFmZjBpSVhucDZBVG9tN01HbDgvRWpORE5I?= =?utf-8?B?RDVDdGEzK05lM0VsSXdpdTh0ZU5nazRoMXgzdVNWVFMwdkRPQi9tdzVzSm9n?= =?utf-8?B?bU15a2N5M21mVm1BYStoTjl3b1lFUmRvbG0xN3cwb3hVUktubXVhb0xQZ1BG?= =?utf-8?B?eldZcmhsVmh6anV1WVpmUkcxUnhHRGpVWURjQmxBVjc1TmNGVmZXU3hVbkE5?= =?utf-8?B?WUhZRzlJWmpXK01mVkd2dXhTbjBUK0NLTWQyc25aNU1XNHBpZGVsdlkwaDdD?= =?utf-8?B?RnlrZ01RTzgwWXFGbUdJV3lGRHZGTEVBNVFPSWM1ZUhxTlIvbkJBaG9KdWI3?= =?utf-8?B?OU5ST0o3dzBDSmN2R3JYT0l1bXVzeTRFNCt6TkhHeG1BdjdCNXNsT1Z4ZFFq?= =?utf-8?B?YWhyaEh6bUdXQXdpamRnR0NDWEtOdzhXN0hTREdmRTQ1MUpkWEJRWjBXZ0gr?= =?utf-8?B?bVNRVnUzcXFod2Erek8xN2dTYWw1eG5NWGxDbTZZM0pUNjVwbGI5alZtWDB6?= =?utf-8?B?YmVLa3o1QWhHQTBYcTQ3QldmK0ZvVUNweTlUSmpPU2VraW1qYzBJc25KSWpU?= =?utf-8?B?WEhNWmZXb2xXZ0lPYjlJdWEzTDlUVk45cnl2VDNmTENjNWdKekVzN1lrYXg5?= =?utf-8?B?R2czMWh0REF0eXV5T0RPZGVRVXhPVE9RRHJZM3l3ZGZ4THgrMURMN210aFZB?= =?utf-8?B?a3pmVW1WczJFV1BENkJvellJTnZMdHl1TzNoNWUvN055UzBGNDJhYVZtTjU1?= =?utf-8?B?NS9mVThTSlI5eUhjTTdDSlVXMFN4YzhaZEV3bUcxRkZVZE9Rd0h4RUhlWnBp?= =?utf-8?B?bXI0ZkwzbXVxZTBuVFN0UXQ0a04xVWUweGJsSHlhM292QlM0cXUwRTFnVUxN?= =?utf-8?B?Y3R5WHlRc0d2bXdvaHFTaytidnI2WDlKaHUza2JqekxGYjllQnBYa0lzdE1S?= =?utf-8?B?MjJienBxeVBZREdtbVR0V2NEYXBYa3BhOGF2TWtLRzJBSEcySU1BaDFEVHRa?= =?utf-8?B?OXZ2WUxsVnhIYmVlckZtaVQwdGZKK1pNTm44UXpPTFA1K1VaVStpSTF2OE93?= =?utf-8?B?U1lndTBuY2FTTlk4Rys0V0tHQmdvMkVHQXdQak0rRFRYeWpSNEwvRnVBZ3c9?= =?utf-8?Q?=3D?=
X-Microsoft-Exchange-Diagnostics: 1; SN1PR0501MB2078; 6:LZtj4u4U06MuughWYu5YKv3wlyvszh0g4sUjRYmM4gwg1aBI7CD/obRNta5bd8r2Ii0P5mMiQcBpGfyGVRWW63BvCBwzHrLQvuJAuZUdeZ2Zy2vVm6O8XZdg1F4YjPvOltE9Kqv1SKsAFAIzYbP1qwKjo97uV31Y5dA8fZGYrHvJaNHEKYrt7rIcxc3e7tWSNU57Ay7bsezPCIcPKZMelQDlS89Q1JNPUECd4LkYlqZtQAAlZ8VMDSQG9UuXfWeQ6f7wM9TMaH2RXteA0bkb02LtHsuO9OMbx2niULashv6/uFT/sih5aCcCB/0D7yTyQGrr+ZM9fWmTvbas648G+IaCBmxqjjK/aWBZ9fYA+Q4=; 5:w4uJCNAaJgr2x1gEoTTCZ3aDAYLjAFJFBzr/QhLVh2WDSIZ45TbhgfDKuIQUYEZ9On8zD9BT9MZB4AeWOPbiL2b9zdOpJtAgBVcmupMsz3x6dfcutqwTQ2DSLwyGtMotuCFrLz9ttPRe+CaSAjEpHrA1M48oqUYUAeTPKvZaU1E=; 24:bK5UKtevx4Sgy+J11RNgqP7411mOJEdaBkT3zKAtfv7v18ytkvDLOfDJH/FN1gNou23RFtkqDa3J0qy7yR0TDMEFRrzbI2XdSj4n5jST7Ig=; 7:wVgN9ySpAiXIRHRy+p5ba2JWGdqai8hmjHG9z0WpdKekavyf7joeRtMEWCUUDG+TEKfwTxTH8ignPrWyCht4v+bhYqBZ/CjpbpBe13pMJ/ZWWNFf0CN6ca/S9VbRfYLgu9PWt1av4/54RBFt9MwN7GFAytoWR5KapMZxq0lJG8C3lmCmctDITtjrSIIBZ+/t1yrqXC7hpPSXVIbwoyP7EZ/yhL4ZMTpEGdht5EjvIjh4C1ywJnrNAjy1eXwOtRfx
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Jan 2018 22:26:15.1955 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 016e8124-d0b8-482f-2b5f-08d5587929a4
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0501MB2078
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-10_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=874 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801100307
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/4ahcgPhMtYq94xXllVzPgBAkdjI>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 22:26:28 -0000

Claiming compatibility does not mean consumers will want or adopt imo.

So far, I've noticed that each set of authors can tackle what they can
and can't support via multiple techniques (obviously bound to their
respective organizations implementations)

- feature/if-feature
- shallow base models that call for augments
- deeper base models that require deviations
- probably a few others I can't think of off the top of my head

If one model implements a heavy feature based technique, this diverges
from the design of another model that implements another technique.  If
we look at an entire collection that would comprise the network-element,
we'll find that we have all techniques in use which lead to more pain
and an inconsistent design from what is generally looked at as a single
organization to a consumer.

Apologies if this has been brought up before and am beating something
into the ground...

On Jan 10 22:06 PM, Reshad Rahman (rrahman) wrote:
> I donâ€™t believe this was the intent, but this is how itâ€™s being used so that implementations can claim compatibilityâ€¦.
> 
> 
> On 2018-01-10, 5:01 PM, "Ebben Aries" <exa@juniper.net> wrote:
> 
>     Maybe this is a simple question but looking at these features, is this
>     really the intended proper use of 'feature'?
>     
>     if-feature global-connect-source;
>     if-feature global-default-peer-policy;
>     if-feature global-default-peer;
>     if-feature global-sa-filter;
>     if-feature global-sa-limit;
>     if-feature global-ttl-threshold;
>     if-feature peer-admin-enable;
>     if-feature peer-as;
>     if-feature peer-connect-source;
>     if-feature peer-description;
>     if-feature peer-key-chain;
>     if-feature peer-sa-limit;
>     if-feature peer-timer-connect-retry;
>     if-feature peer-timer-holdtime;
>     if-feature peer-timer-keepalive;
>     if-feature rpc-clear-sa-cache;
>     
>     Is it really expected that a network-element advertise features to this
>     degree (either capabilities/library) that a client now needs to handle a
>     complex matrix of feature/element mappings in order to generate specific
>     schemas that may wildly branch?
>     
>     Multiply this by total quantity of modules on the network-element and we
>     could be potentially dealing w/ a large amount of features.  Based off
>     my experience, I don't think many folks are aware that common models
>     diverge into "vendor/platform" specific w/ things such as this
>     
>     On Jan 10 22:33 PM, Martin Bjorklund wrote:
>     > Hi,
>     > 
>     > "Reshad Rahman (rrahman)" <rrahman@cisco.com> wrote:
>     > > Hi,
>     > > 
>     > > I am doing YD review of draft-ietf-pim-msdp-yang-01. The YANG module
>     > > is small but relatively speaking thereâ€™s a big number of features
>     > > 17. Basically each config knob has an if-feature.
>     > > 
>     > > However keepalive-interval has a dependency on holdtime-interval via
>     > > must statement. Is the only way to enforce this to add â€œif-feature
>     > > peer-timer-holdtimeâ€� to leaf keepalive-internal?
>     > 
>     > Either that, or do:
>     > 
>     >       must "(not ../holdtime-interval)"
>     >          + " or (. > 1 and . < ../holdtime-interval)";
>     > 
>     > depending on which combinations they want to support.
>     > 
>     > 17 features seems quite a lot...
>     > 
>     > 
>     > 
>     > > 
>     > > Regards,
>     > > Reshad.
>     > > 
>     > >          leaf holdtime-interval {
>     > >            if-feature peer-timer-holdtime;
>     > >            type uint16;
>     > >            units seconds;
>     > >            must ". > 3";
>     > >            default 75;
>     > >            description "The SA-Hold-Down-Period of this msdp peer.";
>     > >          }
>     > >          leaf keepalive-interval {
>     > >            if-feature peer-timer-keepalive;
>     > >            type uint16;
>     > >            units seconds;
>     > >            must ". > 1 and . < ../holdtime-interval";
>     > >            default 60;
>     > >            description "The keepalive timer of this msdp peer.";
>     > >          }
>     > > 
>     > > 
>     > 
>     > 
>     > /martin
>     > _______________________________________________
>     > yang-doctors mailing list
>     > yang-doctors@ietf.org
>     > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwIGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aBisJd_9YYzR6N5-pRltfnJc9N2zHuiK6-TK5W-dx1I&s=qT9UUmnJuEAZgPli4oUG-SDeE8bzhSWR5TPTwsboSKU&e=
>     
> 


From nobody Wed Jan 10 14:38:08 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D69E1275F4 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 Gb9zCCJqZUqg for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:38:04 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5923B127369 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:38:04 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 1EDE2F38; Wed, 10 Jan 2018 23:38:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id S1KiTKo1nZUj; Wed, 10 Jan 2018 23:38:02 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Wed, 10 Jan 2018 23:38:02 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id DCD962013E; Wed, 10 Jan 2018 23:38:02 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id t00pDv_KiZMu; Wed, 10 Jan 2018 23:38:02 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id E81382013D; Wed, 10 Jan 2018 23:38:01 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 2A2DC420ACAD; Wed, 10 Jan 2018 23:38:01 +0100 (CET)
Date: Wed, 10 Jan 2018 23:38:01 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Ebben Aries <exa@juniper.net>
Cc: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180110223801.hx23svra4xpuww2i@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/yr1hFHv4nzVhfPPL2lxfiwNQYtM>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 22:38:07 -0000

On Wed, Jan 10, 2018 at 03:26:10PM -0700, Ebben Aries wrote:

> So far, I've noticed that each set of authors can tackle what they can
> and can't support via multiple techniques (obviously bound to their
> respective organizations implementations)
> 
> - feature/if-feature
> - shallow base models that call for augments
> - deeper base models that require deviations
> - probably a few others I can't think of off the top of my head
> 
> If one model implements a heavy feature based technique, this diverges
> from the design of another model that implements another technique.  If
> we look at an entire collection that would comprise the network-element,
> we'll find that we have all techniques in use which lead to more pain
> and an inconsistent design from what is generally looked at as a single
> organization to a consumer.
> 
> Apologies if this has been brought up before and am beating something
> into the ground...

There is no tight coordination how we do things across areas and
working groups, the best we can do is to write BCPs after having
gained experience (we react with years of delay to things that went
wrong) and to ask questions as part of the review procedures. All we
have here is the text in 4.17. of draft-ietf-netmod-rfc6087bis-15.txt
and perhaps we have better text in a future update of this BCP.

/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/>


From nobody Wed Jan 10 14:49:55 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC80127698 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:49:53 -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 pDE41lFw4aR0 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 14:49:51 -0800 (PST)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 07B321275F4 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:49:51 -0800 (PST)
Received: by mail-lf0-x22f.google.com with SMTP id e27so628962lfb.9 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 14:49:50 -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; bh=kPt8YnvXWiqsNpb2l13q3KFBa/FOekSpMk1kTIG1ZQw=; b=XfWNgZiE2koC0fdnFG+6bWZjN5mUVOxXJGcHBdMbXKiTxq4CQScL1JeJUtNYy2E9XF mH8BAF8p339pXkG37XbpQvP6OJeHTHOoIV5Cp/WN4GWYQCucqMD5duSLJg35Lz3Qwz76 k0X9NHAjnyikMzJyJFbfTIGXp0P6XCGwQYKE37XC6hawmGi8/GOaPE1qJ1m+URQEiWpE n+HydUdJx11IGIIum9+S3AinGpd/cM3HSHgOnurNW/TvgsD+vV2bXLINv6YBLUZ2j2TT dfztjFYupcXXnAX4g2zIoirwZLkXiGJHx4OJS90seO7CA5ywvdJhlPvoJCBIvUDdIFDd GkxA==
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; bh=kPt8YnvXWiqsNpb2l13q3KFBa/FOekSpMk1kTIG1ZQw=; b=HY4CIbdcQZ2nXO3vtNj9WDJ9xPgCspFtxDY17WYY9RAxuNNgKGlTlBbwQT28bRFORP 21laTDsU6Awg29oyb7shrMDaBAsUvuVORC/qGiSzlyzCocQtWxYCJtGiDMRfq/vEYNLO Jz3N7lMvEuQ3Cq9PHxWyAggIvP5xnsvb2KFVq0CFtfpY8RjgopDA/vuV5fLqnL4vA3bu di3ZlgVJhQbp8f1ZsrRwzAZS5YAVtWo/h/GPlUa2qf/UxAoWK6IS9jjCDdKqKZz0CjCf DFl1nvvvM86DeyAv06U8u7p1m6h1TTh+2wkVPrHM3hb52S8sK1oSiyrNgeqF7+Lxx7Wv A4EQ==
X-Gm-Message-State: AKwxytdWIT+YLuv5FsBajIxlpXP3u3oVFdQ/hBL4Idu0WdIf8IEyWyV1 kUsLFvm3AQlgEbBCKJLGdnuCVib7GdjpBY1bB8bE/g==
X-Google-Smtp-Source: ACJfBosJhiUyHVb1s492KeJyzqbbo7uQTyLw+r1bOCbyy708h81xH++77tPXCsbqYxkd2cPn/n/mr4aVq20RGEXB47w=
X-Received: by 10.25.20.168 with SMTP id 40mr5260542lfu.23.1515624589172; Wed, 10 Jan 2018 14:49:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.162.1 with HTTP; Wed, 10 Jan 2018 14:49:48 -0800 (PST)
In-Reply-To: <20180110223801.hx23svra4xpuww2i@elstar.local>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 10 Jan 2018 14:49:48 -0800
Message-ID: <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Ebben Aries <exa@juniper.net>,  "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="001a113fb118403c30056273d9d2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Bb7uItS6_h_eOJeVEw2asVza2DI>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 22:49:53 -0000

--001a113fb118403c30056273d9d2
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 10, 2018 at 2:38 PM, Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> On Wed, Jan 10, 2018 at 03:26:10PM -0700, Ebben Aries wrote:
>
> > So far, I've noticed that each set of authors can tackle what they can
> > and can't support via multiple techniques (obviously bound to their
> > respective organizations implementations)
> >
> > - feature/if-feature
> > - shallow base models that call for augments
> > - deeper base models that require deviations
> > - probably a few others I can't think of off the top of my head
> >
> > If one model implements a heavy feature based technique, this diverges
> > from the design of another model that implements another technique.  If
> > we look at an entire collection that would comprise the network-element,
> > we'll find that we have all techniques in use which lead to more pain
> > and an inconsistent design from what is generally looked at as a single
> > organization to a consumer.
> >
> > Apologies if this has been brought up before and am beating something
> > into the ground...
>
> There is no tight coordination how we do things across areas and
> working groups, the best we can do is to write BCPs after having
> gained experience (we react with years of delay to things that went
> wrong) and to ask questions as part of the review procedures. All we
> have here is the text in 4.17. of draft-ietf-netmod-rfc6087bis-15.txt
> and perhaps we have better text in a future update of this BCP.
>
>

The feature-per-leaf approach should not be approved by YD.
The intent of if-feature, and usage in most cases, is less granular.
It may never be easy to decide what should be bundled as a feature,
but making every leaf a feature is no decision at all.

The use of deviate not-supported should be encouraged instead of
if-feature on every leaf.

IMO the conformance leaf in the YANG library should be kept,
and expanded.  I lobbied for 'other' and it never got added.
What about 'partial-implement'?  IMO it is better to tell the client
some objects are implemented, rather than ignore the module
unless it is fully implemented,






/js
>
>
Andy


> --
> 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/>
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
>

--001a113fb118403c30056273d9d2
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jan 10, 2018 at 2:38 PM, Juergen Schoenwaelder <span dir=3D"ltr=
">&lt;<a href=3D"mailto:j.schoenwaelder@jacobs-university.de" target=3D"_bl=
ank">j.schoenwaelder@jacobs-university.de</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">On Wed, Jan 10, 2018 at 03:26:10PM -0700, Ebben Arie=
s wrote:<br>
<br>
&gt; So far, I&#39;ve noticed that each set of authors can tackle what they=
 can<br>
&gt; and can&#39;t support via multiple techniques (obviously bound to thei=
r<br>
&gt; respective organizations implementations)<br>
&gt;<br>
&gt; - feature/if-feature<br>
&gt; - shallow base models that call for augments<br>
&gt; - deeper base models that require deviations<br>
&gt; - probably a few others I can&#39;t think of off the top of my head<br=
>
&gt;<br>
&gt; If one model implements a heavy feature based technique, this diverges=
<br>
&gt; from the design of another model that implements another technique.=C2=
=A0 If<br>
&gt; we look at an entire collection that would comprise the network-elemen=
t,<br>
&gt; we&#39;ll find that we have all techniques in use which lead to more p=
ain<br>
&gt; and an inconsistent design from what is generally looked at as a singl=
e<br>
&gt; organization to a consumer.<br>
&gt;<br>
&gt; Apologies if this has been brought up before and am beating something<=
br>
&gt; into the ground...<br>
<br>
There is no tight coordination how we do things across areas and<br>
working groups, the best we can do is to write BCPs after having<br>
gained experience (we react with years of delay to things that went<br>
wrong) and to ask questions as part of the review procedures. All we<br>
have here is the text in 4.17. of draft-ietf-netmod-rfc6087bis-<wbr>15.txt<=
br>
and perhaps we have better text in a future update of this BCP.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div><br></div><div>The feature-per-leaf approach should =
not be approved by YD.</div><div>The intent of if-feature, and usage in mos=
t cases, is less granular.<br></div><div>It may never be easy to decide wha=
t should be bundled as a feature,</div><div>but making every leaf a feature=
 is no decision at all.</div><div><br></div><div>The use of deviate not-sup=
ported should be encouraged instead of</div><div>if-feature on every leaf.<=
/div><div><br></div><div>IMO the conformance leaf in the YANG library shoul=
d be kept,</div><div>and expanded.=C2=A0 I lobbied for &#39;other&#39; and =
it never got added.</div><div>What about &#39;partial-implement&#39;?=C2=A0=
 IMO it is better to tell the client</div><div>some objects are implemented=
, rather than ignore the module</div><div>unless it is fully implemented,</=
div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></=
div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><f=
ont color=3D"#888888">
/js<br>
<br></font></span></blockquote><div><br></div><div>Andy</div><div>=C2=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=3D"#88=
8888">
--<br>
Juergen Schoenwaelder=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Jacobs Univer=
sity Bremen gGmbH<br>
Phone: +49 421 200 3587=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Campus Ring 1 | 28=
759 Bremen | Germany<br>
Fax:=C2=A0 =C2=A0+49 421 200 3103=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&lt;<a h=
ref=3D"http://www.jacobs-university.de/" rel=3D"noreferrer" target=3D"_blan=
k">http://www.jacobs-university.<wbr>de/</a>&gt;<br>
<br>
______________________________<wbr>_________________<br>
yang-doctors mailing list<br>
<a href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/yang-do=
ctors</a><br>
</font></span></blockquote></div><br></div></div>

--001a113fb118403c30056273d9d2--


From nobody Wed Jan 10 15:28:39 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FBA128954 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 15:28:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 nJXTJChNm511 for <yang-doctors@ietfa.amsl.com>; Wed, 10 Jan 2018 15:28:35 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2CC1120726 for <yang-doctors@ietf.org>; Wed, 10 Jan 2018 15:28:34 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id AE0BDF38; Thu, 11 Jan 2018 00:28:33 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id G9jl7q3I6XzQ; Thu, 11 Jan 2018 00:28:32 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 11 Jan 2018 00:28:33 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6476A2013D; Thu, 11 Jan 2018 00:28:33 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id DAPOL1y9W7vx; Thu, 11 Jan 2018 00:28:32 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 489CE2013C; Thu, 11 Jan 2018 00:28:32 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 579D7420AE38; Thu, 11 Jan 2018 00:28:30 +0100 (CET)
Date: Thu, 11 Jan 2018 00:28:30 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Andy Bierman <andy@yumaworks.com>
Cc: Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180110232830.6rqbhpw5s55kx6zo@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/vMxr7XVA6Jl4iZxDBjJISho6Jsk>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jan 2018 23:28:37 -0000

On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
> 
> The feature-per-leaf approach should not be approved by YD.
> The intent of if-feature, and usage in most cases, is less granular.
> It may never be easy to decide what should be bundled as a feature,
> but making every leaf a feature is no decision at all.
>

Well, likely a WG trying to avoid the painful process to come to hard
decisions.

> The use of deviate not-supported should be encouraged instead of
> if-feature on every leaf.

I think there is no general and simple answer. While if-feature on
every leaf is likely a failure, less extreme cases may still hide
failures to find agreement and generally are difficult to spot. (We
all know that a strong participant can find ways to push a feature
even if the vast majority of implementations would not need it.)  The
yang doctors can't help with this since we are typically not familiar
with the details of the technology being modeled. So at the end, it is
the WGs that are responsible for the YANG modules they produce and
ultimately the market will decide whether a module is usable or not.

> IMO the conformance leaf in the YANG library should be kept,
> and expanded.  I lobbied for 'other' and it never got added.
> What about 'partial-implement'?  IMO it is better to tell the client
> some objects are implemented, rather than ignore the module
> unless it is fully implemented,

We do have deviations but some organizations do not like using them.
I am not sure inventing something less explicit will be much more
successful. What does a client do with 'partial-implement'?

I really like packages: I like the idea of creating meaningful bundles
of modules and features that allows human operators to determine
relatively easily whether clients and servers can work together
without having to understand hundreds of modules and their
feartures.

/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/>


From nobody Thu Jan 11 08:14:58 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C8C12D88F; Thu, 11 Jan 2018 08:14:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 9sesEXiU6Gx8; Thu, 11 Jan 2018 08:14:46 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69AC112D860; Thu, 11 Jan 2018 08:14:46 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 31C7EFBA; Thu, 11 Jan 2018 17:14:45 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id sYkAloZvGGeO; Thu, 11 Jan 2018 17:14:44 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 11 Jan 2018 17:14:44 +0100 (CET)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 565C02013E; Thu, 11 Jan 2018 17:14:44 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id x-ohmLO0y_DX; Thu, 11 Jan 2018 17:14:43 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id F173E2013D; Thu, 11 Jan 2018 17:14:42 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 74DB1420C8FE; Thu, 11 Jan 2018 17:14:43 +0100 (CET)
Date: Thu, 11 Jan 2018 17:14:43 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Jan Lindblad <janl@tail-f.com>
Cc: yang-doctors@ietf.org, netmod@ietf.org, ietf@ietf.org, draft-ietf-netmod-revised-datastores.all@ietf.org
Message-ID: <20180111161443.6l5jgzzjg77d6v5r@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Jan Lindblad <janl@tail-f.com>, yang-doctors@ietf.org, netmod@ietf.org, ietf@ietf.org, draft-ietf-netmod-revised-datastores.all@ietf.org
References: <151551261178.1806.130953175040927039@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <151551261178.1806.130953175040927039@ietfa.amsl.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/llWn4OMMOuBq_HBluHjXVXTmlwo>
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-netmod-revised-datastores-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 16:14:49 -0000

Jan,

thanks for sharing your review - an interesting read. Many of the
issues you have touched upon have kept us quite busy during 2017, both
on the mailing list and during the regular webex calls of the main
contributors. Thanks for actually sharing your notes.

/js

On Tue, Jan 09, 2018 at 07:43:31AM -0800, Jan Lindblad wrote:
> Reviewer: Jan Lindblad
> Review result: Ready
> 
> Finally the NMDA datastores draft has reached WGLC, and I have been assigned as
> YD reviewer; quite an honor ;-)
> 
> Because of the pretty fundamental importance of this document, I performed what
> I consider myself a pretty thorough review. Since this work has been going on
> for a very long time and with high intensity at times, I have not even tried to
> keep up to date with all the discussions. So in order not to resurrect all the
> beaten zombies that this spec has seen, I decided to let the document shepherd
> and principal author Martin Björklund review my review.
> 
> The end result of which is that I withdraw every one of my comments and
> proclaim review result Ready.
> 
> For full transparency (and to show that I wasn't lazy after all), I have
> enclosed my initial review findings below. Note that I now feel that they are
> either discussed enough already, addressed in a different document (e.g. YANG
> library), or misunderstandings/proposals on my part that do not necessarily
> merit further discussion or clarification. Finally I will add that no blackmail
> or bribery ;-) was involved in me reaching this conclusion; merely a good
> discussion.
> 
> /jan
> 
> Topic #1: Loss of operational stringency
> 
> According to RFC 6020 tradition, config false data returned from <get>
> operations MUST adhere to the constraints declared in the YANG modules;
> max-elements, must statements, unique keys, etc. This is obviously a high
> standard to live up to for server implementors. With NMDA, the situation
> reverses so that <get> operations will return data from <operational> where no
> semantic guarantees apply. This moves the burden of managing flux and
> inconsistency from the servers to the clients.
> 
> Now each client has to be able to deal with potentially duplicate keys,
> violated constraints and generally that any YANG model semantic guarantee is a
> mere recommendation.
> 
> Personally I find this rather shocking. One of the core values in NETCONF/YANG
> has always been that it sides with the "operator" or "client" view of the
> world. Decades ago we had SNMP (Simple ...) -- which in practice meant simple
> to *implement*, not simple to use. NC/Y is supposed to be the other way around.
> Hard to implement, but easy to use.
> 
> If we feel strict adherence to the YANG declaration is a bar too high for
> operational data, maybe we could find some middle ground? Just giving up and
> saying that anything anywhere may be violated anytime is to make it too easy
> for implementors and too hard for clients, IMHO.
> 
> If I'm beating on a dead horse here, I apologize ;-) I just want to ensure that
> if this is what we want, it should be an informed decision.
> 
> Topic #2: Actions live in <operational>
> 
> NMDA says actions are always invoked in context of the <operational> data
> store. In many cases I agree this makes good sense. But there are a couple of
> catches here.
> 
> The first catch relates to timing. As the server is not obliged to make an
> element committed in <intended> immediately available in <operational>, a
> client that creates a bit of configuration and is interested to execute an
> action on it will not know when to fire the action. Should it poll for the
> object creation? Keep retrying? I sense the creation of Heisenbugs and interop
> issues.
> 
> The second catch relates to structure translation between <running> and
> <intended>. If the configuration committed to <running> by the client has no
> direct counterpart in <intended> and <operational>, there is nothing to invoke
> the action on. Say I used a templating feature in <running> to define a bit of
> configuration, and now I want to execute a check-sync action on that piece of
> config to see that the config has propagated properly. There is no context to
> invoke the action on in <operational>.
> 
> Similarly, for actions that update <running> (e.g. config wizards), executing
> in <running> would make sense. Maybe an ability to specify the context
> datastore in the rpc would be enough to fix this. Or better perhaps, the target
> datastore should be formally declared by the action/rpc?
> 
> Such a declaration would solve another issue that exists today. A client needs
> to parse English to know if an action changes <running>. Any configuration data
> cached by the client would need to be invalidated iff so. With a formal
> mechanism to declare which datastores are (not) affected, clients could be a
> lot more efficient. This is a real issue.
> 
> Topic #3: Datastore specific deviations
> 
> How would I express a deviation that applies to one datastore but not another?
> Say, for example, that I have a deviate not-implemented on an object in
> <running> but I support it in <operational>.
> 
> Topic #4: NMDA compliance declaration
> 
> How would a client know that a server works according to NMDA principles? I
> suppose the intent is that there is no need to know because things are
> "backwards compatible", and that for a given server the answer may vary
> depending on which data model we're talking about. But as discussed in topic
> #1, #2, #3 above (and more below), significant semantic differences are
> introduced by NMDA. As client implementor, I would want to know what to expect
> from a server.
> 
> Topic #5: Origin of unset values
> 
> When the operational view is constructed, the draft describes situations where
> the operational value may be taken in some cases from or:intended and in other
> from or:learned. While it would be valuable for clients to understand what the
> precedence rule is, this may be a bit too complex to declare formally, since it
> is quite possible that the mechanics of which value shows up isn't always
> simple and may depend on other leaf values.
> 
> In the example with a DHCP learned address trumping an intended address, it
> could be that the DHCP server specifies only an IPv6 address. In which case the
> device policy might be to override the IPv4 address in intended with no value.
> In this situation, there is no way for the server to communicate why there is
> no IPv4 address (it was or:learned), since the origin attribute cannot live on
> a non-existent XML element.
> 
> So the origin mechanism does not work well for optional elements.
> 
> Topic #6: Datastore and origin identity trees
> 
> Why are there two trees with identities, one for datastores and one with
> origins? Most values seems to be the same, with the origins being a superset of
> the datastores. By organizing them into a single tree with all the datastores
> as one branch of the origins tree, we could get something simpler.
> 
> moduel ietf-origin {
>     identity origin;
> 
>     identity unknown { base origin; }
>     identity system { base origin; }
>     identity learned { base origin; }
>     identity default { base origin; }
>     identity datastore { base origin; }
> 
>     identity conventional { base datastore; }
>     identity running { base conventional; }
>     identity candidate { base conventional; }
>     identity startup { base conventional; }
>     identity intended { base conventional; }
>     identity dynamic { base datastore; }
>     identity operational { base datastore; }
> 
>     /*
>      * Type definitions
>      */
> 
>     typedef origin-ref {
>       type identityref {
>         base origin;
>       }
>     }
> 
>     typedef datastore-ref {
>       type identityref {
>         base datastore;
>       }
>     }
> 
> Topic #7: Editorial
> 
> Below are a few details about the wording:
> 
> On pages 3 and 4, it is said that
> "These datastores share a common datastore schema"
> and
> """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."""
> 
> If we have a device that support macros/templates/services in <running>, which
> expands into concrete configuration in <intended>, I don't suppose the
> macro/template/service instances would be part of <intended>? If so, I guess
> the schemas are not exactly the same? Maybe we can say that <intended> is a
> subset of the <running> schemas (plus all the config false data)?
> 
> p15: Maybe we could point out that learned values etc MUST NOT update
> <running>/<intended> to make this entirely clear.
> 
> p24: Juergen Schoenwaelder's funding is mentioned, but not his participation
> 
> p27: what's <get-data> ?
> 
> p28: ds-ephemeral and or-ephemeral are not great names. Will be referred to as
> ds:ds-ephemeral and or:or-ephemeral. Would prefer ds:ephemeral and or:ephemeral.
> 
> /jan
> 
> 

-- 
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/>


From nobody Thu Jan 11 12:04:07 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D27412DB71 for <yang-doctors@ietfa.amsl.com>; Thu, 11 Jan 2018 12:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 OdQ2y3gdT4P9 for <yang-doctors@ietfa.amsl.com>; Thu, 11 Jan 2018 12:04:02 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 B0C4812DB70 for <yang-doctors@ietf.org>; Thu, 11 Jan 2018 12:04:02 -0800 (PST)
Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0BJrsGQ028647 for <yang-doctors@ietf.org>; Thu, 11 Jan 2018 12:04:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : subject : message-id : mime-version : content-type; s=PPS1017; bh=P+j2yi2Y+p71WS0zZdXvt2GjW6mH18ntfbP4msAbdRU=; b=NSCyBNqUL2Zznmj8VJQktXRslhBpeUboCq5T2Lpu9QRm0y4wW9TnDLLqAdQ3F8N87OvD x1Z3CqQXlk4a9hQZa1juaj2myK+BUi185RnRGXO1XXBS15vefi9wh9CirIZDvdX3c8c5 zNgx6NsE2q7+fo1sV7KrVwG74s5K+EeEeuXbqnkYur5AI7Zir31mETSxGYbk7MH+h65p lmkDB2U7JDMfh1UDXtbsZkPCmZW9RfC54SPRabrHMuvCaGsVu4mmO/zXssG88glVKD8K xjJOAbQ52sjSzOBJd+4o/yngVW/XyPsez5kmEMF4wD/5s0qSMbpWAE+HKrozDfEEyaZv EQ== 
Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp0175.outbound.protection.outlook.com [216.32.181.175]) by mx0a-00273201.pphosted.com with ESMTP id 2feeesg130-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <yang-doctors@ietf.org>; Thu, 11 Jan 2018 12:04:00 -0800
Received: from SN1PR05CA0034.namprd05.prod.outlook.com (10.163.68.172) by BY2PR0501MB2072.namprd05.prod.outlook.com (10.163.197.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.407.1; Thu, 11 Jan 2018 20:03:59 +0000
Received: from BY2NAM05FT021.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::209) by SN1PR05CA0034.outlook.office365.com (2a01:111:e400:5197::44) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.407.1 via Frontend Transport; Thu, 11 Jan 2018 20:03:58 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by BY2NAM05FT021.mail.protection.outlook.com (10.152.100.158) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.345.12 via Frontend Transport; Thu, 11 Jan 2018 20:03:57 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 11 Jan 2018 12:03:57 -0800
Date: Thu, 11 Jan 2018 13:03:56 -0700
From: Ebben Aries <exa@juniper.net>
To: <yang-doctors@ietf.org>
Message-ID: <20180111200356.i2pyyqgh455lxfe6@smtp.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(396003)(39860400002)(376002)(346002)(39380400002)(2980300002)(189003)(199004)(50466002)(478600001)(8676002)(86362001)(68736007)(6916009)(2351001)(305945005)(966005)(81166006)(55016002)(81156014)(97756001)(7696005)(47776003)(53936002)(69596002)(6306002)(356003)(5660300001)(8936002)(23726003)(16586007)(53416004)(105596002)(316002)(97736004)(2906002)(46406003)(106466001)(1076002)(104016004)(77096006)(558084003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0501MB2072; H:P-EMFE01C-SAC.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; BY2NAM05FT021; 1:VQcM+iyCHOmBceDtLbtKq28yEOHkA3g5i0x3A0rjYqmXmlH9HvjALglWZiQVfWmcj6q5WMst7krmBCCTV3E3gZ7krrUhfc8AzOsEAAEUpOpH5VYnyMgpk7vtE4Enu5bl
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 69aecf61-37d9-4390-c8d9-08d5592e7369
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:BY2PR0501MB2072; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 3:oi4svAnQ/yCen3sOxjTCS3ISo4eBkqdudk5XHW+ZpeZYepfXKtKH6UFHeuiQp/8pdZwAgVyKUk9FydyzatQGh1Bb/bM6uRaebsB48vd3qnDtpPbEAWRI3fx+7IkswgQH/iuraHgzxdhOxf8OIj4NwUOK5asGyQcDL6kDTtz9yiSVUNfmIcurD2fH2MEwA3fD8HB2hcD/1EO2TKBJ1ZJkMRB72QK3DO5mqSFhAQkuO47CHAh8RCMV/wKRCWLvc+GvfXNc1De9QrW+Saccb9TejJLcSBLUB4k0PL2+7he0Pyu9LRugUqfQJJsa4dHHQWDp7hwU4MHVePm7jKztBugDq9QYht3dA+b+kVqrBBrcSCg=; 25:XvKit/ieyTU5u9IK1Jc9gaZuZbji69P4GFx54OyW7HDoZjzgq51lpUVniEpowDQ5O28PurajI3CkPSquU3zpVpmoHGw97WATFHSipuCg0hUe4mqV0icz7vdiCBziWR6lEXOFL2SHZafiK1rs/AQwrFFf0X7bDGb1qWQfLO0z294yOWN6hj7ssz8cHLoqti5fAiKx4QAPKgJNb+4aNfwBM65Wa/dHYDlFkLXZiCS/bcVqZlcyM86eMkYmgP+utXXBIsK3Sck9eHb0LMhkJvBIsyldSk7iT6pUJ2VjKQYra1B711DwqocGDpdLurqp+MfWEIivsfh4B8O2d+88qZhDAg==
X-MS-TrafficTypeDiagnostic: BY2PR0501MB2072:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 31:hWA4dY9YLYBo15q7DafxZZkZd03JB40jJ6uXoXXFRDAmewg/jsIf8zXWVbJ9myqHkZnSD1KwV+Jl7SYT+I2jppN62mZ/YE3WJ3vhY3hu3tOWwG2xDxRKKc/4XFkhSxqghqRcCmPxl8AfH20AZwC83L7XzyXbVYXF7GsMzJZd6ZCxU2EgyRWXVC8TIxEnmgEz/Uak4GCrvRAlwjX0NtX0X+TkvPRXWTWoqsYeNNUQaoE=; 20:ataHBurkEdbSv7/z0urBDDv5Gqrcjx8AF0jaA1zlCMkmkmkoL/knUGhcLnfMzuR6jL5pt79U8WHU95SJibABpLzhn4zslHhD/EFu6wjd5ZoYsf1hTJUlgveQH1GIWXERc8148seSWlOO8znUNXokkMixX+U85Wb0bLdL6CWaXtYYvUIEfoG/yTweQNVVkuYfoHKMmelh+ZYhk8vjWsIOEMrUKdKTcYVctETD5kvU6LwOF1qBYAA/f5pCLldK6TCtKGaTs/R60X1/uo4zUpc803qTi3mcVKslC3tOvvZoTTVu2hkB487n3jJ7lNO9++R1jYacS7k/GcXR2eqFXQRvZ2CVhDAZxnEgsrzQt2wjYWXg4RRmeVdYKbgPDUo0AA6iFa5bYR8WGKIOSXbP5mcshwRS5lFI6B7KhfXFjUEIRGEvbuYJWUc3HlQUKVJ+RSxxt4/M29IqifIt4Cf8bdKZ+kehj7tE3U4jyQAarc0U9m54q8ag1a4+3gWieEo0igJ9
X-Microsoft-Antispam-PRVS: <BY2PR0501MB20720948F3E5AD017C9F655BA8160@BY2PR0501MB2072.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231023)(944501075)(6055026)(6041268)(20161123564045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123560045)(6072148)(201708071742011); SRVR:BY2PR0501MB2072; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BY2PR0501MB2072; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 4:+plA0vEiRdUHDRPELO1RaWASwashrjevHjvm5uaFznEXslX6eQmbu8XFwEsRxVWnj/utYtH2RDchy/O8unmYhn3M4AaxWyno9sxM7ukfa5WFzHvsvRCFLH6xhwd2Qxv+9rdCrW78NaKV74tEDJPVL3ArbyT2jMhZVMugGflt6HJ5EDEFseM3SdmVAwomwdiB8RWaf8PLosv8VJ5ipzEdg5tC1Xy84ActCOwAHB37q736uP8GY1KOBMgN7BQi5nAl5oS94VwNxGy+FnOy/Cx6xA==
X-Forefront-PRVS: 0549E6FD50
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY2PR0501MB2072; 23:BYFYsHLro76WNhJ9rBkXAECX86lebEfznFQdLpw?= =?us-ascii?Q?L4k8CaM26GrhlS3wOux1WebG3ySzG8Rr6L4hMd1nulDvGoUR5u91y4MGstwN?= =?us-ascii?Q?PI4MHFFpfdrsqU1uhr3hFN2Cijd9tcqBBLmVGQ14vfoGqlo055ryd8O3Y6hK?= =?us-ascii?Q?lmmpg6drj7ZVuz+48DOSm73Nf2XYwoAyeO+QijN6C0YrIr4HC86JI22LqU67?= =?us-ascii?Q?i10e+CZZbGW7LDznFUXbvUtNq7WqiimGYn+Ub1L+24gOP+Q5F0yVHmqJAZJI?= =?us-ascii?Q?sPKniZSQmPhwr8qeYPfrC++vPcrM8LfHI66nc7+0X7EqkI2TJHqeWPkK9WlB?= =?us-ascii?Q?wneJtolNuz7NddtliMTskoDHEVuEopT12MJHjnkJYM7FkgvunQAt5ErORbL3?= =?us-ascii?Q?KeE7uxLufxCxFI/PaYNFRGPdBiSM7Q7YtkOxldjzb/kVI063KI+S7NWF94fe?= =?us-ascii?Q?aOgkdrrFYTYiSL5SCHXhpBmCw584yAnCTAO9sfcsut1dBD7JCKP9t1qEYy27?= =?us-ascii?Q?0cr8sy5SSaq16s/l3idZq89I8/9IJaU6law+aQdew7TJhGYvNkYEZrs2/LM9?= =?us-ascii?Q?SE6AwevZr5WkhnlO82iVXo15ZiJ/gHLcmogFs/lSmyB2JpzvnBD66khJ9Q2F?= =?us-ascii?Q?ehCJ0lOdbKd/JU8XwpAdQIpL0Vs4TOFLr1BsFNTjEvgt7iaA4plbanBTuzlt?= =?us-ascii?Q?cb3etrmZNrPu9oxhtzKpsLT08qKVbyKj3iP50oMv7pPML7tJsy/YHLtCsepK?= =?us-ascii?Q?Ut42iu7zPhRj5blFQBQaw2MWFn/poI5u8/nHXzkIZR7StxdPEnUm+P02Kwns?= =?us-ascii?Q?SCLb6lKXHm6xyEwXXAFJf3rMei+yjcIXBYB6lMuFpqQNF/ZZj5mdAPRMVddx?= =?us-ascii?Q?6boTfXrhtZSk/Jz9LLTFupcLK9F5fzPuPsNqCGUcTlgAtpgA0SIndP/rIPna?= =?us-ascii?Q?Fw6LbMx0O3ar+aUeKiIFNGCtEncsYsyyxwpyvaal3bH9mouS2JnIc79aI34H?= =?us-ascii?Q?Qh7fO1uElRU5j/MmLuxmOWWHg?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2072; 6:uzXV+fKo154+II0AMTaXnpdAckB6w/fVQ0AZRfvqzDBA97Vxcz2ktYAF9wOjGpIbV8BDrVgFlXEdn54CxOUYw+rrSK/ormTTjpfYJk7yEuUBK7x62vafbzoguP+/bwdAF/Ay1UYb8PbwOHGUt3oEqpKTeJhn9xHlCbEwaJ1elW5dSsaWm1Y5cDgowqCu5fKsWXcnjYGf3KQxTTqHaOGf8Og9q8FzCEu+EYUr0wzuVMs3FXUyJqiMeTOWzOEjnm7Rkq5SpNNzqd+VIVAQsTIvs8i3dSr+dD0ZObXpWwUHWrdCXT7G34KsAbJgy8NfsBAvE9cppB2YPQvxOLyo3J6WXCYnldm8G2iLQnhfGrDdX/c=; 5:1YiKO1TEmD2wQnOX5E29y5hjk9n/v5gX7+9ZQ6VBFt24xNPhIZuzZaCwtcqurQWAOJnXf1m1dqGQaZ4IWL7jp0AxOIcmtlhgnqBTKKBXoSfY0ff+oP92oe6AvLXA5KzrpVfWuTP0ogpg620Bn8nX2V6TmPH8TrEWV1WXrbLGU+8=; 24:zVat5Az5EgOcIT92aBaz47YPWQDJfh6lSqLfn5ERcSP1zTuZuR1sOkeMuk4Eb20AC6rj+q0i5TjMQZaErP4FRAeXfkEo5CmPlfflzqYt0Ts=; 7:LKho45GobuR8b0d2K6Mdb66jPmJKkHnE8SsamzFx5N6FHPIUio5/PZ+pg6SxIJVGEiWb5LHzR2hqOcMc6XNgSXBiOeaMUytmanYttCSGknfgSyvwvwDZw0mJCjvYdBRcv5wq7GVo04fzDmJwi6KiWV6qHp47qcDTKwViyqXDNVUoQuxBeO8gjfLb/aX32xHmEV/zuwAqhAw0tuZJm4kdu357Ej4PM5dzXGxRjljn/fCUslVJj6l4/WitMZzqMnAn
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Jan 2018 20:03:57.9817 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 69aecf61-37d9-4390-c8d9-08d5592e7369
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0501MB2072
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-11_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=2 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=492 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801110272
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/vixhRfRVO-4Fn7uI26PzXUWYDWs>
Subject: [yang-doctors] yang-version in module template/rfc6087bis
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Jan 2018 20:04:05 -0000

I noticed yang-version is missing from the template and doesn't appear
to be any reference in these guidelines.  Is this intentional?

https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C

I'll assume that anything going through review right now should carry
1.1?


From nobody Fri Jan 12 02:13:38 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C907124E15 for <yang-doctors@ietfa.amsl.com>; Fri, 12 Jan 2018 02:13:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 uIsw6dRli27b for <yang-doctors@ietfa.amsl.com>; Fri, 12 Jan 2018 02:13:34 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4CB124D6C for <yang-doctors@ietf.org>; Fri, 12 Jan 2018 02:13:34 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id CFEEC1820412; Fri, 12 Jan 2018 11:13:16 +0100 (CET)
Received: from localhost (unknown [195.113.220.121]) by trail.lhotka.name (Postfix) with ESMTPSA id B49EB182040D; Fri, 12 Jan 2018 11:13:13 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: yang-doctors@ietf.org
In-Reply-To: <20180110.171811.858477092972700390.mbj@tail-f.com>
References: <1515579468.6095.29.camel@nic.cz> <20180110.125841.1275902835172392300.mbj@tail-f.com> <1515600384.11767.48.camel@nic.cz> <20180110.171811.858477092972700390.mbj@tail-f.com>
Date: Fri, 12 Jan 2018 11:13:28 +0100
Message-ID: <87po6fmlkn.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/6cunFYzaaNZIeeUjgzZabmRBr8o>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2018 10:13:37 -0000

Martin Bjorklund <mbj@tail-f.com> writes:

> Ladislav Lhotka <lhotka@nic.cz> wrote:
>> On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
>> > Ladislav Lhotka <lhotka@nic.cz> wrote:
>> > > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
>> > > > Hi,
>> > > > 
>> > > > Replying to this only on yang-doctors, since this is mostly a
>> > > > discussion about the interpretation of RFC 7950.
>> > > > 
>> > > > 
>> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
>> > > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
>> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
>> > > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
>> > > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
>> > > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee) wrote:
>> > > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>> > > > 
>> > > > [...]
>> > > > 
>> > > > > > > > > > > 4. In "when" expressions, the module uses literal strings
>> > 
>> > for
>> > > > > > > > > > >   identities. This is known to be problematic, the XPath
>> > > > 
>> > > > functions
>> > > > > > > > > > >   derived-from() or derived-from-or-self() should be used
>> > > > 
>> > > > instead.
>> > > > > > > > > > > 
>> > > > > > > > > > 
>> > > > > > > > > > Why is this problematic? Is it because the types can be
>> > 
>> > extended?
>> > > > > > > > > 
>> > > > > > > > > That's one reason: derived identities should often also satisfy
>> > 
>> > the
>> > > > > > > > > constraint.
>> > > > > > > > > 
>> > > > > > > > > But the more serious problem is that things like
>> > > > > > > > > 
>> > > > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
>> > > > > > > > > 
>> > > > > > > > > rely on plain string comparison that depends od the actual
>> > 
>> > prefix
>> > > > used
>> > > > > > > > 
>> > > > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON
>> > 
>> > encoding of
>> > > > > > > > > this value
>> > > > > > > > > would be "ietf-ospf:ospfv3" so the above expression is always
>> > > > 
>> > > > false. 
>> > > > > > > > 
>> > > > > > > > This is not correct; the when expression is not evaluated on the
>> > 
>> > JSON
>> > > > > > > > encoding.  See the last paragraph of section 9.10.3 in RFC 7950:
>> > > > > > > > 
>> > > > > > > >    The string value of a node of type "identityref" in a "must" or
>> > > > > > > >    "when" XPath expression is the referred identity's qualified
>> > 
>> > name
>> > > > > > > >    with the prefix present.  If the referred identity is defined
>> > 
>> > in an
>> > > > > > > >    imported module, the prefix in the string value is the prefix
>> > > > 
>> > > > defined
>> > > > > > > >    in the corresponding "import" statement.  Otherwise, the prefix
>> > 
>> > in
>> > > > > > > >    the string value is the prefix for the current module.
>> > > > > > > 
>> > > > > > > This is weird, to say the least. The leafref instance may have an
>> > > > 
>> > > > identity
>> > > > > > > value
>> > > > > > > that is defined in a module that (has to be implemented by the
>> > 
>> > server
>> > > > but)
>> > > > > > > needn't be imported in the module that contains the XPath
>> > 
>> > expression. So
>> > > > I
>> > > > > > > don't
>> > > > > > > know what 'corresponding "import" statement' this paragraph is
>> > 
>> > talking
>> > > > > > > about.
>> > > > > > 
>> > > > > > It has to import the module in order to give a prefix, which then can
>> > > > > > be used in the XPath expression.
>> > > > > 
>> > > > > In the XPath expression above, do you mean the "rt" prefix of
>> > > > > "rt:type"?
>> > > > 
>> > > > No, I meant the "ospf" prefix for the module "ietf-ospf".
>> > > > 
>> > > > > If so,
>> > > > > it is irrelevant for the string comparison, what's important is the
>> > 
>> > *value*
>> > > > of
>> > > > > the "rt:type" instance, which can be an identity defined in a module
>> > 
>> > that
>> > > > > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec. 9.10.2:
>> > > > > 
>> > > > >    On a particular server, the valid values are further restricted
>> > > > >    to the set of identities defined in the modules implemented by
>> > > > >    the server.
>> > > > 
>> > > > Because of the way the representation of identities work in must/when
>> > > > expressions, you *must* import the module where the identity is
>> > > > define, if you want to use the identity for equality comparision like
>> > > > in the example.
>> > > > 
>> > > > You may have:
>> > > > 
>> > > >   module a {
>> > > >     ...
>> > > >     import ietf-ospf {
>> > > >       prefix x;
>> > > >     }
>> > > >     ...
>> > > >     leaf foo {
>> > > >       when "../type = 'x:ospfv3'";
>> > > >       ...
>> > > >     }
>> > > >   }
>> > > 
>> > > The problem here is not with the literal 'x:ospf' but rather with the string
>> > > value of the leafref node instance ("../type" here), and clearly it is what
>> > 
>> > sec.
>> > > 9.10.3 talks about ("string value of a [leafref] node").
>> > > 
>> > > I can define a module like
>> > > 
>> > > module foo-ospf {
>> > >   namespace "http://example.com/foo-ospf";
>> > >   prefix ospf;
>> > >   import ietf-routing {
>> > >     prefix rt;
>> > >   }
>> > >   identity ospfv3 {
>> > >     base "rt:routing-protocol";
>> > >   }
>> > >   ...
>> > > }
>> > > 
>> > > Now, if the server advertizes both ietf-ospf and foo-ospf as implemented
>> > 
>> > (which
>> > > is legal), the module foo-ospf needn't be imported anywhere and still the
>> > 
>> > "type"
>> > > leaf instance can have both values "ietf-ospf:ospfv3" and "foo-ospf:ospfv3",
>> > > provided that it is defined as
>> > > 
>> > > leaf type {
>> > >   type identityref {
>> > >     base rt:routing-protocol;
>> > >   }
>> > > }
>> > > 
>> > > And I wonder what the last paragraph in sec. 9.10.3 means in this situation,
>> > > i.e. what string value of "type" is used in the evaluation of the XPath
>> > > expression in your module "a", if the value-space value of 'type' instance
>> > 
>> > in a
>> > > datastore is either of the two '...:ospfv3' identities.
>> > > 
>> > > Do you see what I mean?
>> > 
>> > Do you mean that the problem is that the spec does not define what the
>> > string value is if the module where the identity is defined is not
>> > imported?
>> > 
>> > I agree that this is an issue.
>> > 
>> > BUT, actually, if you look the text in the spec:
>> > 
>> >    The string value of a node of type "identityref" in a "must" or
>> >    "when" XPath expression is the referred identity's qualified name
>> >    with the prefix present.  If the referred identity is defined in an
>> >    imported module, the prefix in the string value is the prefix defined
>> >    in the corresponding "import" statement.  Otherwise, the prefix in
>> >    the string value is the prefix for the current module.
>> > 
>> > If you blindly follow this, the last sentence would have to apply, and
>> > the string would be "a:ospfv3", which clearly is broken.
>> 
>> It depends on what "current module" means.
>
> "current module" and "local module" means the module where the "must"
> or "when" expression is defined.  There was a separate thread about
> this as well.

OK, then it really makes no sense to add the local prefix. 

>
>> It could also be interpreted as the
>> module in which the identity is defined, but then we can get the collision of
>> prefixes as in my example.
>> 
>> > 
>> > For all practical purposes, I think the string value can be "" if the
>> > identity is defined in a module that is not imported, and is not
>> > defined in the current module.
>> 
>> I think a better solution would be to avoid prefixes in lexical-space identity
>> values altogether and use the same string as in JSON encoding (RFC 7951). The
>> XPath expression from your example would become
>> 
>>     "../type = 'ietf-ospf:ospfv3'"
>> 
>> Everything would then be straightforward and non-ambiguous.
>
> Yes, as I wrote in my previous email, I agree, this would be better.
> But that's for YANG 2.0, unfortunately.

Maybe not. If we agree that the last paragraph in 9.10.3 is wrong ang
needs an erratum, then I think instead of saying that the XPath string
value is the empty string as you suggested (which is weird and
non-intuitive), this paragraph can say that the value (only for XPath!)
is as in RFC 7951.

In fact, after re-reading sec. 9.10, I believe it is even not required
to import the module in order to be able to use the prefix in a string
literal, as "x" in

    "../type = 'x:ospfv3'"

because it is just an XPath 1.0 string with no additional semantics, so
module authors can equally well write 

    "../type = 'ietf-ospf:ospfv3'"

without importing "ietf-ospf".

Of course, we could also replace the paragraph with a statement that the
result of using bare identityref string values in XPath is undefined and
thus force everybody to use the XPath functions.

Lada

>
>
> /martin
>
>
>
>
>> 
>> Lada
>> 
>> > 
>> > 
>> > /martin
>> > 
>> > 
>> > 
>> > 
>> > > 
>> > > Lada 
>> > >   
>> > > 
>> > > > 
>> > > > and
>> > > > 
>> > > >   module b {
>> > > >     ...
>> > > >     import ietf-ospf {
>> > > >       prefix y;
>> > > >     }
>> > > >     ...
>> > > >     leaf bar {
>> > > >       when "../type = 'y:ospfv3'";
>> > > >       ...
>> > > >     }
>> > > >   }
>> > > > 
>> > > > You may not like it, but these two modules are both correct according
>> > > > to the rules defined in RFC 7950.  The string value of the "type" leaf
>> > > > *when evaluating the when expression* is different in the different
>> > > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
>> > > >     
>> > > > > > > Also, potentially there can be a collision in prefixes and then this
>> > > > 
>> > > > also
>> > > > > > > breaks down.
>> > > > > > 
>> > > > > > 
>> > > > > > No, two modules cannot be imported with the same prefix.
>> > > > > 
>> > > > > I have to disagree. An identity derived from the
>> > > > > "ietf-routing:control-protocol-type" base identity can be defined
>> > > > > in a module that is not imported anywhere. If a server declares such
>> > > > > a module as implemented, then "rt:type" may have this value per
>> > > > > sec. 9.10.2.
>> > > > > 
>> > > > > And, consequently, there may be two different modules with
>> > > > > conflicting prefixes defining identities that are derived from
>> > > > > "ietf-routing:control-protocol-type".
>> > > > 
>> > > > Sure, but this is not the point.
>> > > > 
>> > > > > > > A moral of the namespace/prefix story in XML was that relying of
>> > > > > > > namespace prefixes having a particular value is a really bad
>> > > > > > > idea. I know that the cited paragraph was intended to make such
>> > > > > > > XPath string comparisons more deterministic, but it is also
>> > > > > > > problematic and should be avoided if possible.
>> > > > > > 
>> > > > > > Note that this prefix is under the control of the module designer
>> > > > > > writing the XPath expression.  The same identityref value might use a
>> > > > > 
>> > > > > No, it is not. The prefixes appear in instance data.
>> > > > 
>> > > > The prefix *in the when expression* is under the control of the module
>> > > > designer, as explained above.
>> > > > 
>> > > > You are correct that the prefix in an XML encoding is not under
>> > > > control of the module designer, but noone has claimed that.
>> > > > 
>> > > > I agree that it is unfortunate that context-specific prefixes are used
>> > > > for the identityref values.  It would have been better if we used a
>> > > > context free representation, e.g. "<module-name>:<identity>".  But
>> > > > that's another discussion.
>> > > > 
>> > > > 
>> > > > 
>> > > > /martin
>> > > 
>> > > -- 
>> > > Ladislav Lhotka
>> > > Head, CZ.NIC Labs
>> > > PGP Key ID: 0xB8F92B08A9F76C67
>> > > 
>> -- 
>> Ladislav Lhotka
>> Head, CZ.NIC Labs
>> PGP Key ID: 0xB8F92B08A9F76C67
>> 
>> _______________________________________________
>> yang-doctors mailing list
>> yang-doctors@ietf.org
>> https://www.ietf.org/mailman/listinfo/yang-doctors
>> 

-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Fri Jan 12 09:45:44 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77E6012D7F5 for <yang-doctors@ietfa.amsl.com>; Fri, 12 Jan 2018 09:45:42 -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 2zzf9CeD8odw for <yang-doctors@ietfa.amsl.com>; Fri, 12 Jan 2018 09:45:38 -0800 (PST)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 47132129C6E for <yang-doctors@ietf.org>; Fri, 12 Jan 2018 09:45:37 -0800 (PST)
Received: by mail-lf0-x22b.google.com with SMTP id e203so6801627lfg.3 for <yang-doctors@ietf.org>; Fri, 12 Jan 2018 09:45:37 -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=l3acFpzji/iFpTlvwPXzZszbdFB2y/8fC6kOLlNDWG8=; b=1ScyTbACsccjbiuGaJ6Ssaz6CM6iLFVkfHPdrcuAKOJYpTaHmx/2HpjwAq430cHc8D 1UlRQH3pWmaYOIZjYNCWmIRInQ/i41tesusrQHh6D81ZY3l8ia8tcD36X54PvJEcO5+E S3KQKtFv9gWGJvl7jIahQf5ZcfrvEgYkF6HXwuLeyaMzMnkWBQIM4GmMtHsUFJDcQ3CB qMXphyhD80Yct0pi3ialCq7wTYP2rWduPrj9lBc8sWbbAxIWhvcBJNp4ZmeGfdEwaJFw oGCM/0lenMBy0V+A65cxA8vSUt6E08l3xaI6rlAM5E5mhvUClsTSJ0QGKxMSMGNiv3J1 8fWg==
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=l3acFpzji/iFpTlvwPXzZszbdFB2y/8fC6kOLlNDWG8=; b=XBtrlG2xSfxxV5SOkk0vJJTzOCmQV0enOO9yQHaulPcrorHEuXFhnKccbexvtNwi7O hmq6FsFUOqAvqMJ/bX1om0gAXeKSAJ8XjE+2NPX0qBegQP5quIT73aZRQgTLUZJOKSRD 5Yo5I9s/rcN0Pv2iZL75x6+6Px6IYjuPbxLNjgVbiFe1tR3ihEU59xcBgKmIy57p5X0Y gfUANKjChwkori9sMc1oSKGrl+/typYPttLjIqWw72PKMiyieBh5LzGzXEuUBIyDdsWr VoAAdE4qpNDdFMUSa8QgvcBSQJ/SMJSCbcCGyDEzbzydQPq4h9hPF3xmlMXtU++Pvv86 Eacw==
X-Gm-Message-State: AKwxytfwm1pvcQhi/JhDvSTVQdQLssZ6VUl+xFxoxOZ6YmM+yIftqA1B 8DaQWSk9cTYgDcLvI3FbA5YkblkPU95NxYGJVlFk5g==
X-Google-Smtp-Source: ACJfBotqSFbXzgl6CfLSBRHyMG5aYzlzhMTG+E5L1EGQEqUPkj6Y/8Yb5F08Ctsm8DoB8Zgyq+BZmKf+cFU3cxPexcY=
X-Received: by 10.25.201.81 with SMTP id z78mr2924689lff.74.1515779135445; Fri, 12 Jan 2018 09:45:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.162.1 with HTTP; Fri, 12 Jan 2018 09:45:34 -0800 (PST)
In-Reply-To: <87po6fmlkn.fsf@nic.cz>
References: <1515579468.6095.29.camel@nic.cz> <20180110.125841.1275902835172392300.mbj@tail-f.com> <1515600384.11767.48.camel@nic.cz> <20180110.171811.858477092972700390.mbj@tail-f.com> <87po6fmlkn.fsf@nic.cz>
From: Andy Bierman <andy@yumaworks.com>
Date: Fri, 12 Jan 2018 09:45:34 -0800
Message-ID: <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: Martin Bjorklund <mbj@tail-f.com>, YANG Doctors <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b798ced4c23056297d4e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/xM91vd7l2Xj92RRcIXzwnfcpiVk>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2018 17:45:42 -0000

--001a114b798ced4c23056297d4e4
Content-Type: text/plain; charset="UTF-8"

On Fri, Jan 12, 2018 at 2:13 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:

> Martin Bjorklund <mbj@tail-f.com> writes:
>
> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> >> On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
> >> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> >> > > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> >> > > > Hi,
> >> > > >
> >> > > > Replying to this only on yang-doctors, since this is mostly a
> >> > > > discussion about the interpretation of RFC 7950.
> >> > > >
> >> > > >
> >> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> >> > > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> >> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> >> > > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> >> > > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> >> > > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee)
> wrote:
> >> > > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz>
> wrote:
> >> > > >
> >> > > > [...]
> >> > > >
> >> > > > > > > > > > > 4. In "when" expressions, the module uses literal
> strings
> >> >
> >> > for
> >> > > > > > > > > > >   identities. This is known to be problematic, the
> XPath
> >> > > >
> >> > > > functions
> >> > > > > > > > > > >   derived-from() or derived-from-or-self() should
> be used
> >> > > >
> >> > > > instead.
> >> > > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > > Why is this problematic? Is it because the types can
> be
> >> >
> >> > extended?
> >> > > > > > > > >
> >> > > > > > > > > That's one reason: derived identities should often also
> satisfy
> >> >
> >> > the
> >> > > > > > > > > constraint.
> >> > > > > > > > >
> >> > > > > > > > > But the more serious problem is that things like
> >> > > > > > > > >
> >> > > > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> >> > > > > > > > >
> >> > > > > > > > > rely on plain string comparison that depends od the
> actual
> >> >
> >> > prefix
> >> > > > used
> >> > > > > > > >
> >> > > > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON
> >> >
> >> > encoding of
> >> > > > > > > > > this value
> >> > > > > > > > > would be "ietf-ospf:ospfv3" so the above expression is
> always
> >> > > >
> >> > > > false.
> >> > > > > > > >
> >> > > > > > > > This is not correct; the when expression is not evaluated
> on the
> >> >
> >> > JSON
> >> > > > > > > > encoding.  See the last paragraph of section 9.10.3 in
> RFC 7950:
> >> > > > > > > >
> >> > > > > > > >    The string value of a node of type "identityref" in a
> "must" or
> >> > > > > > > >    "when" XPath expression is the referred identity's
> qualified
> >> >
> >> > name
> >> > > > > > > >    with the prefix present.  If the referred identity is
> defined
> >> >
> >> > in an
> >> > > > > > > >    imported module, the prefix in the string value is the
> prefix
> >> > > >
> >> > > > defined
> >> > > > > > > >    in the corresponding "import" statement.  Otherwise,
> the prefix
> >> >
> >> > in
> >> > > > > > > >    the string value is the prefix for the current module.
> >> > > > > > >
> >> > > > > > > This is weird, to say the least. The leafref instance may
> have an
> >> > > >
> >> > > > identity
> >> > > > > > > value
> >> > > > > > > that is defined in a module that (has to be implemented by
> the
> >> >
> >> > server
> >> > > > but)
> >> > > > > > > needn't be imported in the module that contains the XPath
> >> >
> >> > expression. So
> >> > > > I
> >> > > > > > > don't
> >> > > > > > > know what 'corresponding "import" statement' this paragraph
> is
> >> >
> >> > talking
> >> > > > > > > about.
> >> > > > > >
> >> > > > > > It has to import the module in order to give a prefix, which
> then can
> >> > > > > > be used in the XPath expression.
> >> > > > >
> >> > > > > In the XPath expression above, do you mean the "rt" prefix of
> >> > > > > "rt:type"?
> >> > > >
> >> > > > No, I meant the "ospf" prefix for the module "ietf-ospf".
> >> > > >
> >> > > > > If so,
> >> > > > > it is irrelevant for the string comparison, what's important is
> the
> >> >
> >> > *value*
> >> > > > of
> >> > > > > the "rt:type" instance, which can be an identity defined in a
> module
> >> >
> >> > that
> >> > > > > needn't be imported by ietf-routing, ietf-ospf or whatever.
> Sec. 9.10.2:
> >> > > > >
> >> > > > >    On a particular server, the valid values are further
> restricted
> >> > > > >    to the set of identities defined in the modules implemented
> by
> >> > > > >    the server.
> >> > > >
> >> > > > Because of the way the representation of identities work in
> must/when
> >> > > > expressions, you *must* import the module where the identity is
> >> > > > define, if you want to use the identity for equality comparision
> like
> >> > > > in the example.
> >> > > >
> >> > > > You may have:
> >> > > >
> >> > > >   module a {
> >> > > >     ...
> >> > > >     import ietf-ospf {
> >> > > >       prefix x;
> >> > > >     }
> >> > > >     ...
> >> > > >     leaf foo {
> >> > > >       when "../type = 'x:ospfv3'";
> >> > > >       ...
> >> > > >     }
> >> > > >   }
> >> > >
> >> > > The problem here is not with the literal 'x:ospf' but rather with
> the string
> >> > > value of the leafref node instance ("../type" here), and clearly it
> is what
> >> >
> >> > sec.
> >> > > 9.10.3 talks about ("string value of a [leafref] node").
> >> > >
> >> > > I can define a module like
> >> > >
> >> > > module foo-ospf {
> >> > >   namespace "http://example.com/foo-ospf";
> >> > >   prefix ospf;
> >> > >   import ietf-routing {
> >> > >     prefix rt;
> >> > >   }
> >> > >   identity ospfv3 {
> >> > >     base "rt:routing-protocol";
> >> > >   }
> >> > >   ...
> >> > > }
> >> > >
> >> > > Now, if the server advertizes both ietf-ospf and foo-ospf as
> implemented
> >> >
> >> > (which
> >> > > is legal), the module foo-ospf needn't be imported anywhere and
> still the
> >> >
> >> > "type"
> >> > > leaf instance can have both values "ietf-ospf:ospfv3" and
> "foo-ospf:ospfv3",
> >> > > provided that it is defined as
> >> > >
> >> > > leaf type {
> >> > >   type identityref {
> >> > >     base rt:routing-protocol;
> >> > >   }
> >> > > }
> >> > >
> >> > > And I wonder what the last paragraph in sec. 9.10.3 means in this
> situation,
> >> > > i.e. what string value of "type" is used in the evaluation of the
> XPath
> >> > > expression in your module "a", if the value-space value of 'type'
> instance
> >> >
> >> > in a
> >> > > datastore is either of the two '...:ospfv3' identities.
> >> > >
> >> > > Do you see what I mean?
> >> >
> >> > Do you mean that the problem is that the spec does not define what the
> >> > string value is if the module where the identity is defined is not
> >> > imported?
> >> >
> >> > I agree that this is an issue.
> >> >
> >> > BUT, actually, if you look the text in the spec:
> >> >
> >> >    The string value of a node of type "identityref" in a "must" or
> >> >    "when" XPath expression is the referred identity's qualified name
> >> >    with the prefix present.  If the referred identity is defined in an
> >> >    imported module, the prefix in the string value is the prefix
> defined
> >> >    in the corresponding "import" statement.  Otherwise, the prefix in
> >> >    the string value is the prefix for the current module.
> >> >
> >> > If you blindly follow this, the last sentence would have to apply, and
> >> > the string would be "a:ospfv3", which clearly is broken.
> >>
> >> It depends on what "current module" means.
> >
> > "current module" and "local module" means the module where the "must"
> > or "when" expression is defined.  There was a separate thread about
> > this as well.
>
> OK, then it really makes no sense to add the local prefix.
>
> >
> >> It could also be interpreted as the
> >> module in which the identity is defined, but then we can get the
> collision of
> >> prefixes as in my example.
> >>
> >> >
> >> > For all practical purposes, I think the string value can be "" if the
> >> > identity is defined in a module that is not imported, and is not
> >> > defined in the current module.
> >>
> >> I think a better solution would be to avoid prefixes in lexical-space
> identity
> >> values altogether and use the same string as in JSON encoding (RFC
> 7951). The
> >> XPath expression from your example would become
> >>
> >>     "../type = 'ietf-ospf:ospfv3'"
> >>
> >> Everything would then be straightforward and non-ambiguous.
> >
> > Yes, as I wrote in my previous email, I agree, this would be better.
> > But that's for YANG 2.0, unfortunately.
>
> Maybe not. If we agree that the last paragraph in 9.10.3 is wrong ang
> needs an erratum, then I think instead of saying that the XPath string
> value is the empty string as you suggested (which is weird and
> non-intuitive), this paragraph can say that the value (only for XPath!)
> is as in RFC 7951.
>
> In fact, after re-reading sec. 9.10, I believe it is even not required
> to import the module in order to be able to use the prefix in a string
> literal, as "x" in
>
>     "../type = 'x:ospfv3'"
>
> because it is just an XPath 1.0 string with no additional semantics, so
> module authors can equally well write
>
>     "../type = 'ietf-ospf:ospfv3'"
>
> without importing "ietf-ospf".
>
> Of course, we could also replace the paragraph with a statement that the
> result of using bare identityref string values in XPath is undefined and
> thus force everybody to use the XPath functions.
>
>

I do not agree with this interpretation.
The term "prefix" is used 10 times in that section.
It is clear that the WG meant "prefix" not "module name".
This cannot be changed by an errata.



> Lada
>


Andy


>
> >
> >
> > /martin
> >
> >
> >
> >
> >>
> >> Lada
> >>
> >> >
> >> >
> >> > /martin
> >> >
> >> >
> >> >
> >> >
> >> > >
> >> > > Lada
> >> > >
> >> > >
> >> > > >
> >> > > > and
> >> > > >
> >> > > >   module b {
> >> > > >     ...
> >> > > >     import ietf-ospf {
> >> > > >       prefix y;
> >> > > >     }
> >> > > >     ...
> >> > > >     leaf bar {
> >> > > >       when "../type = 'y:ospfv3'";
> >> > > >       ...
> >> > > >     }
> >> > > >   }
> >> > > >
> >> > > > You may not like it, but these two modules are both correct
> according
> >> > > > to the rules defined in RFC 7950.  The string value of the "type"
> leaf
> >> > > > *when evaluating the when expression* is different in the
> different
> >> > > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> >> > > >
> >> > > > > > > Also, potentially there can be a collision in prefixes and
> then this
> >> > > >
> >> > > > also
> >> > > > > > > breaks down.
> >> > > > > >
> >> > > > > >
> >> > > > > > No, two modules cannot be imported with the same prefix.
> >> > > > >
> >> > > > > I have to disagree. An identity derived from the
> >> > > > > "ietf-routing:control-protocol-type" base identity can be
> defined
> >> > > > > in a module that is not imported anywhere. If a server declares
> such
> >> > > > > a module as implemented, then "rt:type" may have this value per
> >> > > > > sec. 9.10.2.
> >> > > > >
> >> > > > > And, consequently, there may be two different modules with
> >> > > > > conflicting prefixes defining identities that are derived from
> >> > > > > "ietf-routing:control-protocol-type".
> >> > > >
> >> > > > Sure, but this is not the point.
> >> > > >
> >> > > > > > > A moral of the namespace/prefix story in XML was that
> relying of
> >> > > > > > > namespace prefixes having a particular value is a really bad
> >> > > > > > > idea. I know that the cited paragraph was intended to make
> such
> >> > > > > > > XPath string comparisons more deterministic, but it is also
> >> > > > > > > problematic and should be avoided if possible.
> >> > > > > >
> >> > > > > > Note that this prefix is under the control of the module
> designer
> >> > > > > > writing the XPath expression.  The same identityref value
> might use a
> >> > > > >
> >> > > > > No, it is not. The prefixes appear in instance data.
> >> > > >
> >> > > > The prefix *in the when expression* is under the control of the
> module
> >> > > > designer, as explained above.
> >> > > >
> >> > > > You are correct that the prefix in an XML encoding is not under
> >> > > > control of the module designer, but noone has claimed that.
> >> > > >
> >> > > > I agree that it is unfortunate that context-specific prefixes are
> used
> >> > > > for the identityref values.  It would have been better if we used
> a
> >> > > > context free representation, e.g. "<module-name>:<identity>".  But
> >> > > > that's another discussion.
> >> > > >
> >> > > >
> >> > > >
> >> > > > /martin
> >> > >
> >> > > --
> >> > > Ladislav Lhotka
> >> > > Head, CZ.NIC Labs
> >> > > PGP Key ID: 0xB8F92B08A9F76C67
> >> > >
> >> --
> >> Ladislav Lhotka
> >> Head, CZ.NIC Labs
> >> PGP Key ID: 0xB8F92B08A9F76C67
> >>
> >> _______________________________________________
> >> yang-doctors mailing list
> >> yang-doctors@ietf.org
> >> https://www.ietf.org/mailman/listinfo/yang-doctors
> >>
>
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
>

--001a114b798ced4c23056297d4e4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Jan 12, 2018 at 2:13 AM, Ladislav Lhotka <span dir=3D"ltr">&lt;=
<a href=3D"mailto:lhotka@nic.cz" target=3D"_blank">lhotka@nic.cz</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Martin Bjorklund &lt;<a href=
=3D"mailto:mbj@tail-f.com">mbj@tail-f.com</a>&gt; writes:<br>
<br>
&gt; Ladislav Lhotka &lt;<a href=3D"mailto:lhotka@nic.cz">lhotka@nic.cz</a>=
&gt; wrote:<br>
&gt;&gt; On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:<br>
&gt;&gt; &gt; Ladislav Lhotka &lt;<a href=3D"mailto:lhotka@nic.cz">lhotka@n=
ic.cz</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrot=
e:<br>
&gt;&gt; &gt; &gt; &gt; Hi,<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; Replying to this only on yang-doctors, since this i=
s mostly a<br>
&gt;&gt; &gt; &gt; &gt; discussion about the interpretation of RFC 7950.<br=
>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; Ladislav Lhotka &lt;<a href=3D"mailto:lhotka@nic.cz=
">lhotka@nic.cz</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; On Tue, 2018-01-09 at 16:23 +0100, Martin Bjor=
klund wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; Ladislav Lhotka &lt;<a href=3D"mailto:lho=
tka@nic.cz">lhotka@nic.cz</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; On Tue, 2018-01-09 at 09:06 +0100, M=
artin Bjorklund wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Ladislav Lhotka &lt;<a href=3D"=
mailto:lhotka@nic.cz">lhotka@nic.cz</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; On Mon, 2018-01-08 at 19:2=
8 +0000, Acee Lindem (acee) wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; On 12/6/17, 6:26 AM, =
&quot;Ladislav Lhotka&quot; &lt;<a href=3D"mailto:lhotka@nic.cz">lhotka@nic=
.cz</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; [...]<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; 4. In &quot;when=
&quot; expressions, the module uses literal strings<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; for<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0iden=
tities. This is known to be problematic, the XPath<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; functions<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0deri=
ved-from() or derived-from-or-self() should be used<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; instead.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Why is this problemat=
ic? Is it because the types can be<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; extended?<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; That&#39;s one reason: der=
ived identities should often also satisfy<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; constraint.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; But the more serious probl=
em is that things like<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0when &q=
uot;../../../../../../../rt:type =3D &#39;ospf:ospfv3&#39;&quot;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; rely on plain string compa=
rison that depends od the actual<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; prefix<br>
&gt;&gt; &gt; &gt; &gt; used<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &quot;rt:type&quot; value.=
 For one, according to RFC 7951 the JSON<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; encoding of<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; this value<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; would be &quot;ietf-ospf:o=
spfv3&quot; so the above expression is always<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; false.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; This is not correct; the when e=
xpression is not evaluated on the<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; JSON<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; encoding.=C2=A0 See the last pa=
ragraph of section 9.10.3 in RFC 7950:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 The string value o=
f a node of type &quot;identityref&quot; in a &quot;must&quot; or<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 &quot;when&quot; X=
Path expression is the referred identity&#39;s qualified<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; name<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 with the prefix pr=
esent.=C2=A0 If the referred identity is defined<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; in an<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 imported module, t=
he prefix in the string value is the prefix<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; defined<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 in the correspondi=
ng &quot;import&quot; statement.=C2=A0 Otherwise, the prefix<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; in<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 the string value i=
s the prefix for the current module.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; This is weird, to say the least. The=
 leafref instance may have an<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; identity<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; value<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; that is defined in a module that (ha=
s to be implemented by the<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; server<br>
&gt;&gt; &gt; &gt; &gt; but)<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; needn&#39;t be imported in the modul=
e that contains the XPath<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; expression. So<br>
&gt;&gt; &gt; &gt; &gt; I<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; don&#39;t<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; know what &#39;corresponding &quot;i=
mport&quot; statement&#39; this paragraph is<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; talking<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; about.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; It has to import the module in order to g=
ive a prefix, which then can<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; be used in the XPath expression.<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; In the XPath expression above, do you mean the=
 &quot;rt&quot; prefix of<br>
&gt;&gt; &gt; &gt; &gt; &gt; &quot;rt:type&quot;?<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; No, I meant the &quot;ospf&quot; prefix for the mod=
ule &quot;ietf-ospf&quot;.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; If so,<br>
&gt;&gt; &gt; &gt; &gt; &gt; it is irrelevant for the string comparison, wh=
at&#39;s important is the<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; *value*<br>
&gt;&gt; &gt; &gt; &gt; of<br>
&gt;&gt; &gt; &gt; &gt; &gt; the &quot;rt:type&quot; instance, which can be=
 an identity defined in a module<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; that<br>
&gt;&gt; &gt; &gt; &gt; &gt; needn&#39;t be imported by ietf-routing, ietf-=
ospf or whatever. Sec. 9.10.2:<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 On a particular server, the valid=
 values are further restricted<br>
&gt;&gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 to the set of identities defined =
in the modules implemented by<br>
&gt;&gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 the server.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; Because of the way the representation of identities=
 work in must/when<br>
&gt;&gt; &gt; &gt; &gt; expressions, you *must* import the module where the=
 identity is<br>
&gt;&gt; &gt; &gt; &gt; define, if you want to use the identity for equalit=
y comparision like<br>
&gt;&gt; &gt; &gt; &gt; in the example.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; You may have:<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0module a {<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0import ietf-ospf {<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0prefix x;<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0leaf foo {<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0when &quot;../type =3D &#=
39;x:ospfv3&#39;&quot;;<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; The problem here is not with the literal &#39;x:ospf&#39=
; but rather with the string<br>
&gt;&gt; &gt; &gt; value of the leafref node instance (&quot;../type&quot; =
here), and clearly it is what<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; sec.<br>
&gt;&gt; &gt; &gt; 9.10.3 talks about (&quot;string value of a [leafref] no=
de&quot;).<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; I can define a module like<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; module foo-ospf {<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0namespace &quot;<a href=3D"http://example.co=
m/foo-ospf" rel=3D"noreferrer" target=3D"_blank">http://example.com/foo-osp=
f</a>&quot;;<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0prefix ospf;<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0import ietf-routing {<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0prefix rt;<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0identity ospfv3 {<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0base &quot;rt:routing-protocol&quot;;=
<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; }<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; Now, if the server advertizes both ietf-ospf and foo-osp=
f as implemented<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; (which<br>
&gt;&gt; &gt; &gt; is legal), the module foo-ospf needn&#39;t be imported a=
nywhere and still the<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &quot;type&quot;<br>
&gt;&gt; &gt; &gt; leaf instance can have both values &quot;ietf-ospf:ospfv=
3&quot; and &quot;foo-ospf:ospfv3&quot;,<br>
&gt;&gt; &gt; &gt; provided that it is defined as<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; leaf type {<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0type identityref {<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0base rt:routing-protocol;<br>
&gt;&gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; }<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; And I wonder what the last paragraph in sec. 9.10.3 mean=
s in this situation,<br>
&gt;&gt; &gt; &gt; i.e. what string value of &quot;type&quot; is used in th=
e evaluation of the XPath<br>
&gt;&gt; &gt; &gt; expression in your module &quot;a&quot;, if the value-sp=
ace value of &#39;type&#39; instance<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; in a<br>
&gt;&gt; &gt; &gt; datastore is either of the two &#39;...:ospfv3&#39; iden=
tities.<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; Do you see what I mean?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Do you mean that the problem is that the spec does not define=
 what the<br>
&gt;&gt; &gt; string value is if the module where the identity is defined i=
s not<br>
&gt;&gt; &gt; imported?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; I agree that this is an issue.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; BUT, actually, if you look the text in the spec:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;=C2=A0 =C2=A0 The string value of a node of type &quot;identit=
yref&quot; in a &quot;must&quot; or<br>
&gt;&gt; &gt;=C2=A0 =C2=A0 &quot;when&quot; XPath expression is the referre=
d identity&#39;s qualified name<br>
&gt;&gt; &gt;=C2=A0 =C2=A0 with the prefix present.=C2=A0 If the referred i=
dentity is defined in an<br>
&gt;&gt; &gt;=C2=A0 =C2=A0 imported module, the prefix in the string value =
is the prefix defined<br>
&gt;&gt; &gt;=C2=A0 =C2=A0 in the corresponding &quot;import&quot; statemen=
t.=C2=A0 Otherwise, the prefix in<br>
&gt;&gt; &gt;=C2=A0 =C2=A0 the string value is the prefix for the current m=
odule.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; If you blindly follow this, the last sentence would have to a=
pply, and<br>
&gt;&gt; &gt; the string would be &quot;a:ospfv3&quot;, which clearly is br=
oken.<br>
&gt;&gt;<br>
&gt;&gt; It depends on what &quot;current module&quot; means.<br>
&gt;<br>
&gt; &quot;current module&quot; and &quot;local module&quot; means the modu=
le where the &quot;must&quot;<br>
&gt; or &quot;when&quot; expression is defined.=C2=A0 There was a separate =
thread about<br>
&gt; this as well.<br>
<br>
OK, then it really makes no sense to add the local prefix.<br>
<br>
&gt;<br>
&gt;&gt; It could also be interpreted as the<br>
&gt;&gt; module in which the identity is defined, but then we can get the c=
ollision of<br>
&gt;&gt; prefixes as in my example.<br>
&gt;&gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; For all practical purposes, I think the string value can be &=
quot;&quot; if the<br>
&gt;&gt; &gt; identity is defined in a module that is not imported, and is =
not<br>
&gt;&gt; &gt; defined in the current module.<br>
&gt;&gt;<br>
&gt;&gt; I think a better solution would be to avoid prefixes in lexical-sp=
ace identity<br>
&gt;&gt; values altogether and use the same string as in JSON encoding (RFC=
 7951). The<br>
&gt;&gt; XPath expression from your example would become<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0&quot;../type =3D &#39;ietf-ospf:ospfv3&#39;&qu=
ot;<br>
&gt;&gt;<br>
&gt;&gt; Everything would then be straightforward and non-ambiguous.<br>
&gt;<br>
&gt; Yes, as I wrote in my previous email, I agree, this would be better.<b=
r>
&gt; But that&#39;s for YANG 2.0, unfortunately.<br>
<br>
Maybe not. If we agree that the last paragraph in 9.10.3 is wrong ang<br>
needs an erratum, then I think instead of saying that the XPath string<br>
value is the empty string as you suggested (which is weird and<br>
non-intuitive), this paragraph can say that the value (only for XPath!)<br>
is as in RFC 7951.<br>
<br>
In fact, after re-reading sec. 9.10, I believe it is even not required<br>
to import the module in order to be able to use the prefix in a string<br>
literal, as &quot;x&quot; in<br>
<br>
=C2=A0 =C2=A0 &quot;../type =3D &#39;x:ospfv3&#39;&quot;<br>
<br>
because it is just an XPath 1.0 string with no additional semantics, so<br>
module authors can equally well write<br>
<br>
=C2=A0 =C2=A0 &quot;../type =3D &#39;ietf-ospf:ospfv3&#39;&quot;<br>
<br>
without importing &quot;ietf-ospf&quot;.<br>
<br>
Of course, we could also replace the paragraph with a statement that the<br=
>
result of using bare identityref string values in XPath is undefined and<br=
>
thus force everybody to use the XPath functions.<br>
<br></blockquote><div><br></div><div><br></div><div>I do not agree with thi=
s interpretation.</div><div>The term &quot;prefix&quot; is used 10 times in=
 that section.</div><div>It is clear that the WG meant &quot;prefix&quot; n=
ot &quot;module name&quot;.</div><div>This cannot be changed by an errata.<=
/div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Lada<br></blockquote><div><br></div><div><br></div><div>Andy</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
&gt;<br>
&gt;<br>
&gt; /martin<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Lada<br>
&gt;&gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; /martin<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; Lada<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; and<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0module b {<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0import ietf-ospf {<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0prefix y;<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0leaf bar {<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0when &quot;../type =3D &#=
39;y:ospfv3&#39;&quot;;<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0...<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; You may not like it, but these two modules are both=
 correct according<br>
&gt;&gt; &gt; &gt; &gt; to the rules defined in RFC 7950.=C2=A0 The string =
value of the &quot;type&quot; leaf<br>
&gt;&gt; &gt; &gt; &gt; *when evaluating the when expression* is different =
in the different<br>
&gt;&gt; &gt; &gt; &gt; modules.=C2=A0 See the last paragraph of section 9.=
10.3 in RFC 7950.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; Also, potentially there can be a col=
lision in prefixes and then this<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; also<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; breaks down.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; No, two modules cannot be imported with t=
he same prefix.<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; I have to disagree. An identity derived from t=
he<br>
&gt;&gt; &gt; &gt; &gt; &gt; &quot;ietf-routing:control-<wbr>protocol-type&=
quot; base identity can be defined<br>
&gt;&gt; &gt; &gt; &gt; &gt; in a module that is not imported anywhere. If =
a server declares such<br>
&gt;&gt; &gt; &gt; &gt; &gt; a module as implemented, then &quot;rt:type&qu=
ot; may have this value per<br>
&gt;&gt; &gt; &gt; &gt; &gt; sec. 9.10.2.<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; And, consequently, there may be two different =
modules with<br>
&gt;&gt; &gt; &gt; &gt; &gt; conflicting prefixes defining identities that =
are derived from<br>
&gt;&gt; &gt; &gt; &gt; &gt; &quot;ietf-routing:control-<wbr>protocol-type&=
quot;.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; Sure, but this is not the point.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; A moral of the namespace/prefix stor=
y in XML was that relying of<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; namespace prefixes having a particul=
ar value is a really bad<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; idea. I know that the cited paragrap=
h was intended to make such<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; XPath string comparisons more determ=
inistic, but it is also<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; problematic and should be avoided if=
 possible.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; Note that this prefix is under the contro=
l of the module designer<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; writing the XPath expression.=C2=A0 The s=
ame identityref value might use a<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; No, it is not. The prefixes appear in instance=
 data.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; The prefix *in the when expression* is under the co=
ntrol of the module<br>
&gt;&gt; &gt; &gt; &gt; designer, as explained above.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; You are correct that the prefix in an XML encoding =
is not under<br>
&gt;&gt; &gt; &gt; &gt; control of the module designer, but noone has claim=
ed that.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; I agree that it is unfortunate that context-specifi=
c prefixes are used<br>
&gt;&gt; &gt; &gt; &gt; for the identityref values.=C2=A0 It would have bee=
n better if we used a<br>
&gt;&gt; &gt; &gt; &gt; context free representation, e.g. &quot;&lt;module-=
name&gt;:&lt;identity&gt;&quot;.=C2=A0 But<br>
&gt;&gt; &gt; &gt; &gt; that&#39;s another discussion.<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; /martin<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; --<br>
&gt;&gt; &gt; &gt; Ladislav Lhotka<br>
&gt;&gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt;&gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt;&gt; &gt; &gt;<br>
<span class=3D"HOEnZb"><font color=3D"#888888">&gt;&gt; --<br>
&gt;&gt; Ladislav Lhotka<br>
&gt;&gt; Head, CZ.NIC Labs<br>
&gt;&gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; yang-doctors mailing list<br>
&gt;&gt; <a href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a>=
<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinf=
o/yang-doctors</a><br>
&gt;&gt;<br>
<br>
--<br>
Ladislav Lhotka<br>
Head, CZ.NIC Labs<br>
PGP Key ID: 0xB8F92B08A9F76C67<br>
<br>
______________________________<wbr>_________________<br>
yang-doctors mailing list<br>
<a href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors" rel=3D"noref=
errer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/yang-do=
ctors</a><br>
</font></span></blockquote></div><br></div></div>

--001a114b798ced4c23056297d4e4--


From nobody Fri Jan 12 09:56:16 2018
Return-Path: <rrahman@cisco.com>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D244912D851; Fri, 12 Jan 2018 09:56:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Reshad Rahman <rrahman@cisco.com>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-pim-msdp-yang.all@ietf.org, pim@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151577977482.18634.14740634433873272656@ietfa.amsl.com>
Date: Fri, 12 Jan 2018 09:56:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/o3GzmpDV9DO513il5mbP2Vcf0JI>
Subject: [yang-doctors] Yangdoctors early review of draft-ietf-pim-msdp-yang-01
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jan 2018 17:56:15 -0000

Reviewer: Reshad Rahman
Review result: On the Right Track

YANG Doctor review of draft-ietf-pim-msdp-yang-01 by Reshad Rahman

1 module in this draft:
- ietf-msdp@2017-08-30.yang

No YANG validation errors or warnings (from pyang 1.7.3 and yanglint 0.14.53).

0 examples are provided in this draft (section 3.12 of
draft-ietf-netmod-rfc6087bis-15)

Module ietf-msdp@2017-08-30.yang:
- Too many features (17)! Every piece of config has an if-feature statement.
Some of the configs (timers?) should be part of most/basic implementations, for
other config (e.g. authentication) I can see why a feature would be used. -
â€œimport ietf-yang-typesâ€� should have a reference to RFC6991 (see section 4.7 of
rfc6087bis-15) - â€œimport ietf-inet-typesâ€� should have a reference to RFC6991 -
â€œimport ietf-routingâ€� should have a reference to RFC8022 - â€œimport
ietf-interfacesâ€� should have a reference to RFC7223 - "import ietf-ip" should
have a reference to RFC7277 - "import ietf-key-chain" should have a reference
to RFC8177 - organization s/"...PIM( Protocols for IP Multicast ) Working
Group"/"...PIM (Protocols for IP Multicast) Working Group"? - Remove WG Chairs
from contact information as per Appendix C of rfc6087bis-15 - No copyright in
the module description, see Appendix of 6087bis-15 for a module description
example - Module description must contain reference to RFC, see Appendix C of
rfc6087bis-15 - grouping authentication-container. key-chain and password both
use if-feature peer-key-chain. - grouping connect-source. The name is not very
descriptive. Should this be something along the lines of tcp-connection-source?
- grouping global-state-attributes has nothing - Some of the descriptions are
pretty terse. e.g. for rpf-peer it says "RPF peer.". In a case like this
consider adding more descriptive text or a reference to the proper section in
RFC3618 - peer-as (Autonomous System Number) is defined as type string, should
be of type as-number in ietf-inet-types? - Not sure why peer-as is needed.
Don't see it in RFC3618. - keepalive-interval depends on holdtime-interval.
There should be "if-feature peer-timer-holdtime" under leaf keepalive-interval
or change the must statement to (assuming we keep the 2 features):
  must "(not ../holdtime-interval) or (. > 1 and . < ../holdtime-interval)".
- leaf up-time: s/sa cache/SA cache/
- leaf up-time, what's meant by "up time" in the description? Is it time it's
been created? - description for leaf expire seems wrong. - leaf
peer-learned-from, change description from "The address of peer that we learned
this SA from ." to "The address of the peer that we learned this SA from." -
Groupings are used for data which is used only once. Is this done on purpose or
was the intention to use those groupings more than once? - augment of
control-plane-protocols is incorrect. There should be an identity msdp with
base "rt:routing-protocol" and then augment
"/rt:routing/rt:control-plane-protocols/rt:control-plane-protocol" with a when
statement. Take a look at OSPF YANG for an example. - RPC leaf group, I thought
we had a type for IP multicast address? If not, it should be done? -
s/msdp/MSDP/ - In rpc msdp-clear-peer, s/Clears the session to the peer./Clears
the TCP connection to the peer./ - In rpc msdp-clear-sa-cache, why have the
enum '*' for source-addr. Can't the same technique as for peer-address be used?
- msdp prefix not needed in rpc names - MSDP peers are configured in a
mesh-group, did the authors consider adding state per mesh-group, e.g. all the
peers in a particular mesh-group?

General:
- Per Appendix B of rfc6087bis-15: "that all YANG modules containing
imported items are cited as normative reference". So RFCs 6991, 7223,
7277, 8022 and 8177 should be included in the normative reference
section.
- Section 3 "the irrelevant information", add a reference/explanation for what
the irrelevant information is. s/the irrelevant information/irrelevant
information/? - Section 5 should give a brief description of what the RPCs do.
- Section 6 any plans for notifications? If not, just say so. - Need Security
Considerations, see sections 3.7 and 6 of rfc6087bis-15 - Need IANA
Considerations, see section 3.8 of rfc6087bis-15 - Need license in YANG module,
see appendix B of rfc6087bis-15

Nits:
- Section 4 s/Sa-cache/SA-cache/



From nobody Fri Jan 12 16:34:52 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0E4A1241FC for <yang-doctors@ietfa.amsl.com>; Fri, 12 Jan 2018 16:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 sA534Dk5fG7Y for <yang-doctors@ietfa.amsl.com>; Fri, 12 Jan 2018 16:34:48 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 566FF126BF3 for <yang-doctors@ietf.org>; Fri, 12 Jan 2018 16:34:48 -0800 (PST)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0D0Yj2a005923; Fri, 12 Jan 2018 16:34:45 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to; s=PPS1017; bh=t3aQ2nU749E4maBAGysq7vCnrnuhPLttmmZ9yENL9J8=; b=djIXU7cEh0S8pQlKCqldD5ij1vt8qDRyBfmYLx4Cjf3DgZIAm/2sl20yZpKjvrTMbku+ 5HOEbWDfDs+UQE633Bk/UIk9koXWyP4Vl5C5oJrwJRIyAgkAE6oiA6qirTTZkDGSPJOn mbSx85SxH4CNXhFXh99IroEu0KryrDbiL8Hi4C/42mOwiZK8pxH3+NGsGiQe1HPelx5+ ewD84POEG0Mp8WuFcPP02Cus9/zSZfct1QhJpuxA6BPNWLuBzVjtzbKIQJ/aZxOgEzF2 Eb+txzwubhwZdM92SrlSV3IkWiyGV5FCFKO/Re8z0hzVVxzppL1yogmPLvbXwv+Z96Aw tg== 
Received: from nam03-dm3-obe.outbound.protection.outlook.com (mail-dm3nam03lp0016.outbound.protection.outlook.com [207.46.163.16]) by mx0b-00273201.pphosted.com with ESMTP id 2ff7jvr0am-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 12 Jan 2018 16:34:45 -0800
Received: from SN1PR0501CA0006.namprd05.prod.outlook.com (10.163.126.144) by CY4PR05MB3608.namprd05.prod.outlook.com (10.171.244.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.9; Sat, 13 Jan 2018 00:34:44 +0000
Received: from DM3NAM05FT005.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::205) by SN1PR0501CA0006.outlook.office365.com (2a01:111:e400:52fe::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.428.9 via Frontend Transport; Sat, 13 Jan 2018 00:34:44 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT005.mail.protection.outlook.com (10.152.98.110) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.20.428.12 via Frontend Transport; Sat, 13 Jan 2018 00:34:43 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 12 Jan 2018 16:34:42 -0800
Date: Fri, 12 Jan 2018 17:34:41 -0700
From: Ebben Aries <exa@juniper.net>
To: Andy Bierman <andy@yumaworks.com>
CC: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180113003441.3skhw7aytcme5gdt@smtp.juniper.net>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <54D46590-633D-4936-AFDF-C6BDE9F43968@cisco.com> <CABCOCHT7iUJ1t+FH1UqK8Bvq3Q4TS4pQ0GsMc706uNZVEcgjBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CABCOCHT7iUJ1t+FH1UqK8Bvq3Q4TS4pQ0GsMc706uNZVEcgjBw@mail.gmail.com>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(39860400002)(39380400002)(2980300002)(189003)(377424004)(24454002)(199004)(5660300001)(6246003)(8936002)(2950100002)(7696005)(106466001)(69596002)(105596002)(53936002)(2486003)(23676004)(47776003)(53416004)(97736004)(6916009)(86362001)(55016002)(229853002)(575784001)(6306002)(104016004)(77096006)(966005)(305945005)(53546011)(356003)(81156014)(93886005)(316002)(1076002)(76176011)(2906002)(54906003)(478600001)(81166006)(8676002)(4326008)(68736007)(2870700001)(50466002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR05MB3608; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT005; 1:lzSjyJCmcl9HK+TubhMGj8ULlOxeq49WJmvKkXZMPSQAFSSGRxcgSPSknGS6DeCxhPFFlqtY48RazNnxb0ffRlZSWka+5tQa5K6gDtBGSOpaE+XKzgJAj87LKtm5NorU
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 2de31688-8bb5-4672-fcea-08d55a1d70eb
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020089)(4652020)(4534119)(4602075)(4627215)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:CY4PR05MB3608; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 3:QX3xgypJF6oeJeRfhIvinRaGZhEoeFTf1Q/vML4LsfzL7yfG1G52wc3ZACd3yFm3g3jiMMD4MQpprk2ng5eUg2KiKyKtME2b7+Yajj1Xj6+9VfkYYMcQKAuLhQqEFJIc92nzrsRc8HPPNyPqpiXN1aVZC74yHXjeWjP+K4CinGYkaIFG6nlvio/jkZw4uf8m+Ft6aCGy8s07WxByscsmqq0IueUFPRPq9aatD6zQaVEYCfwSC+NkGxjH4wKXVWM0lHYc/vV9DHBp/1MfS3C8mQBa9ZEEeE8GLAgCUaFO+kqB9ufAjCDI86p1onhKrKGP9dFKZs1vPoVIlwDW4f1870GZ+gCaDkICDPWdX2VRSgs=; 25:6Y/n1R7pa0wskM/lRK2DIbwyA8sWfWVsDm9RI6ElXUPaKOJhr2ZJikCrhxs5HLKmqLQAyc1PJXK1Jo9pvN25zJ8hE+vMwdIZ4kxVypxeyXrlia95zkR8Y74oVtaMPlvWiJAh87ZBbQ5B+pBcCxFlP2FdDBcz8FqJK7tQj0a+wor3IsOsLj6lftUKYzisulN43dQxzoJqbuHHG3n0BFRgLufrVG9pfls6T4+FF9MBn/KD7uTz3Lh3hsas5+MxzL+iQsJYScQM+0jVUr+IK7zlRh1jPekGvEOyBasK6N5PF+OqE/NOSVKpWFBD44thJq/PB+Fhyp8ppFHpi6plPdVF8A==
X-MS-TrafficTypeDiagnostic: CY4PR05MB3608:
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 31:1oXm5oSXb8vvbrDh5VDCLhOms1BZdeB9Ko2UtOZYrNgo2DJre+CElMMM6XrheKtdnGFcpSCSXswa8xwEw/iqbYV/eVSYyIuKQi6Abrr7ZXuL6gREMkFOMA1JEICcoKrNa7Jst5x+ZAXgqHIgVucHs3JKktkZXEHosmTThg/nuyDQ8BSBfJWkmYhtVZKwvKFOA+bVR5efM2FZHQgPBLBHp76ipmLf/DY2mC1/26HgGvY=; 20:eD3UHpOZzlLFdrjMmbzZ0NOXgkdOqeNrMT8SHPLpJwzT46Gvv4kDvpgVZhmbHrDXYipN4p0KdafzZV14X3a76WY2YqusbT0rRjxZlGCQdje4A4k9zKDPYS+6Qx+uFUdKbMUwaL9SXoYTB+/FqiNYErLWfLhWAqUzf/b+n0hNXez7M/EI2zRLAUCqCmnbyql2zMOmCtmw2DPzIqmMWBtompzW3hsMUrUS0wxw7q8weXdQDbJz/1T3PQj+eLEgDGh/Fz13Qbvyva5fj3vClj0MlWPdNXOt2U1PBnFoJDaIHLrSwwTDByO4/9ZD4DW/ugY9oPqY0WlSCfP+IHkm5Np9NewdsLQ2+8wffUA8GYH4uYCbQ1khL0JnCF+KXPyn5diHZgWY0dn9VjD5V5FdIeEGSbFd5s10oD+K6TR5n1lHaZT9rxtRF73pfVkqC9OKJL9a1FqTgrC5giv8B5vEJMoZ5+CtFm3zpS7SAdMYhQwyEV1bxLv/jeHjWUobwV4E0DiD
X-Microsoft-Antispam-PRVS: <CY4PR05MB36083DC62C56252922EEFE3BA8140@CY4PR05MB3608.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(10436049006162)(271806183753584)(95692535739014); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(5005006)(8121501046)(3231023)(944501149)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041268)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:CY4PR05MB3608; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CY4PR05MB3608; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 4:csjDOtPbCxY/P4NImgwRbj/SDK00+p77RmaVbHGsfdxbQWpN2bMlttzXrsofytW3WhybLEw9+frFZnZKNAD129fgIIHZ7XWFUeFZ49j8cIgpaDjv88cwJCnA1YH50Pgj8SrYkZXIUTWgjlCgon1aNmy5E5TwzAsEqFBumA7x8Tep8ZioOIjdfPUnUhp+wTxjNNkBTYfajzQpZhXGTnTIH/pP0U+cPznLminKA/9Aad7xiQAgalo+MgSc7aXRRFQu3uHCW7WseFpA7o5WloKx7TYQ84Khp4pL8RRNB2yyponFJx28KWGLk/dsy//1z58BSz20EHavXeVB14annIAIBiseIYvM31P5S2LvgdoY3C2nmpAB4F3dPSRcW2j90R/GBHQRNhHzJqoLNTSkzP/ZlV3+OdtxRJlcRudptAPZYgQ=
X-Forefront-PRVS: 05514B7026
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtDWTRQUjA1TUIzNjA4OzIzOk9laGJKdDc5a2h3NVk3QkZLSmZUL05wRjhx?= =?utf-8?B?amxVSlJlcytmcTkzZkQ3b3Z3V0VFVWJkcTQ0Y1lEdDlZQ1JiR21wSWJ4Tmxv?= =?utf-8?B?QkM2REpxaklsb0k2Rk5LdXg2RmNzVlNZbFdONzVFckI4UDJPZnZ6djJWWVVH?= =?utf-8?B?QjJLSU5BU1RIRkRZNDgrL3hPLy9tTE5Ma3pSQTljVExBN0ZiYzQwY2VKYm9t?= =?utf-8?B?ZUo4NmY4ZERkQUsyVE10d1JGOTJtYWpFU05PNnRaSC9xZVE0U3ljTE5rWVVV?= =?utf-8?B?ek96NW9sT01sL1U1RzlweGtWYnE5UVdWaGN6Rit4d1VJeFVYam9UU0lDOWo5?= =?utf-8?B?VnlBVnl3S1BubW8vQ1I1bXdpOTJkbmpwYkpBdGNkMURBYUNJa1NlNzBaQTdq?= =?utf-8?B?TGNsL2lnaEEweFk2UE1jTC83NDgvODdKMUR6bzRLUTg5bS9TSjhvd09QUFlo?= =?utf-8?B?ZWc0RzRoRjhPeEZPdU1KMkJMWVlyOG5vM2NMcjNZZU11c1RsU1ZaRzdjNHAr?= =?utf-8?B?TjJiYXlJN1llSklUMkt5VWRYZlRzYXFKNkN1L084RGxpdC9wUWJVS0s1L1A1?= =?utf-8?B?RXVMbHlNRU1COXp0UjJmMjdWbUh4WVRLRFRmU3JWeWtKcGVzTjBZanN3UGJn?= =?utf-8?B?dXI5U1d6akhoYmlYbzFYVlpUcnZGRW9SMEhycS9SWWlnNnhZSmgxU0FIdkl0?= =?utf-8?B?ZHJLNU80U0MzRTNEWEpJMU5hOXJ6Z3RSbHpDYUc2RjhtTklhaUpXR0VlS1pP?= =?utf-8?B?dFlXOWNBeHA1Qyt3cStwdEJsMWJXalppOEN5OUxvZmhYRStZdW0rWWM3eHIy?= =?utf-8?B?V1FOc2pXZGpsRndhMjJzL1djZjc1SEFTTTFTYnU5cWxyc1ZpVzJPSjZtNS9w?= =?utf-8?B?dndLOVEyelpqZDFnZElnNkM0NDRrcm1VdmRuZmRhaFJKZXhabDVQb3BIUnRI?= =?utf-8?B?UG9XQ3A2aXpYM0RnL2dpM0g3cVRvOU83M1ozeHZpcHR1TW1DT1VoakJhR3lI?= =?utf-8?B?Q3E1WS90WFpHQUk4RlVNOGNRNHdHQkpveDBsTERsZzM2eDY2a0pjMFM5TE90?= =?utf-8?B?ZmtjajNZQ0dpaWxaQW5mRUZGYVhJUU5xTlFTMEVEYys1OTh5ckp2RjEyWXBu?= =?utf-8?B?b2RwUnpwOVY5ai9kMmU1Z1lRdnNqNjJkZERlQ2s5OWVGVTE2V2xvdUVOZDJR?= =?utf-8?B?RXBVYVlzVVgwcU90WEN1cmxvWXRPeThlTk11VGZ2VndDMlc1NHd6YzJtNHpy?= =?utf-8?B?UlFVUFhlMVFxNlFweGZmMitqOGRvNy9UUW5vTUpCTVBCWUJwS1VTU0VDcnMw?= =?utf-8?B?Yk5CMGF6elJxcm1hbk1JOWo0dnd2UktqZ3JKNlQ1cS9La2d1RFprc21SQmZ2?= =?utf-8?B?eXdDN3VLaFowejR5ZEFFYVVJSW12VmRiOUpVNWFqNWU1TkhWb3JkTndVcEFB?= =?utf-8?B?SGYvUXFDaGVhTHk2bnduN2ExcE82Wkc3VEhyNGYrNVROYzB3dGtLZEZ4NUtx?= =?utf-8?B?cURPdGxDZXRpNzMvV3pkcURiZURwQ09aalBuODhrTnhsczdzd2FXUzZvd3lm?= =?utf-8?B?T3ZhUS9TYVExZEdSVmRvU251TjZIcXFUQlpDSWFLY1dPQ0V3b3kvelAzTS9Y?= =?utf-8?Q?Do7P2GFoRPQAnLgOvubu?=
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 6:y2RfozDC6dmteAA29f3MqRs0kdmPg0Nt/cfsKYMO7YT7sl6UQkAtotGwLfGekKe19L8iOclOuqg4t5PRQZl+x9G8fa2Vrx0/9dlRbz92JjT1n6UT1g0/4J7aNP1qYnySg+GC9EbaGTf4emOcCL/b81iGfsY27zPcJczLm5XCqjIkqB90xaVpodO5CZ3MT4GQKMT3hNx29yHiAmKaGo12M1tuq3ILcynKgOpsXjn9MsnwTgnlFEp6nOu5g816z09TmDaKzQpKZSV+VM/j5id7YKH8c6b93jrnWWtkueSuSqpFQ4lh8wQUANdhOWmpBqONJtBWydpVbNH2ubxpbeDA+KVv9vXLpCz91fb5S+ZC2RE=; 5:v2bybgzm8MpfpKgjnFtZcvv1rv2mFo0YjsPFQDrBl9QUUAvcK/diWpa1dQzorzKOo9xWaubiQ3+xoYG+rxvhyP8oK3c9Imk1T/SanJkZZSmTiJonIvi8f+Z5XiykOg3w5Ywq9ZlOc0JpOoyzQAGo0TzCT5RrKtWfpsu4+JlTf8s=; 24:PwyVwwmudFrWqqjlUd5bgpTCKk9OE6RRrVTBsTO8gllb/z2Z7WhmN9fcgZ8E3z8OSGEiZvEJpXyp05gOeCCyRCzQHC9LoU4xwXAgzDLZksE=; 7:NX+XlrJfFVUxrzjerxJqoT24/KHlAkDLj2uQzMMECZNdFsPIHEowWumuosA38c+NGcYwhnC7bXBPKAPfgvBVbn0vitOri1D0U6F/fnn+MM63285dxewWsDfadxkMXgP5GYVIoTSdqfAir9MEBuSrlT/jC+u9coyDXufIF2g1cnWQ2uSCM57J32mTFqYBVB5viFDxyVjsubCvtxwrgGNB0iRmfhA4xFKh0kIGTUad48+l/Xb4GoPZi3Hv4o7fs/Rg
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Jan 2018 00:34:43.4108 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 2de31688-8bb5-4672-fcea-08d55a1d70eb
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR05MB3608
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-12_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801130006
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/sbirqZFaYUNcpDS7Qie4NnVtAFk>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Jan 2018 00:34:52 -0000

On Jan 10 13:56 PM, Andy Bierman wrote:
> On Wed, Jan 10, 2018 at 1:51 PM, Reshad Rahman (rrahman) <rrahman@cisco.com>
> wrote:
> 
> > Thanks Martin.
> >
> > Yes 17 features is a lot for such a small module. I recall we had the
> > per-counter feature a few months ago, thatâ€™s what basically this model is
> > doing but per config.
> >
> >
> Seems the concepts and guidelines for YANG conformance are still very
> unclear.
> Are WGs thinking about the utility to the client developer,
> or the ability for a server developer to claim conformance no matter what
> they implement?
> 
> It seems unlikely that each leaf is completely independent of all others
> wrt/ functionality.
> 

Note, that looking through some published models, we already have a few
cases w/ single modules that contain up to 20 features (a few examples)

RFC8049 - ietf-l3vpn-svc@2017-01-27.yang
RFC6728 - ietf-ipfix-psamp@2012-09-05.yang

So I know for the module Reshad is talking about here, we are telling
the module writers that 17 is too many (and the way they are using such)
but it sounds like we need to have folks focus on the usability aspects
a bit more.  If we consider a client workflow that doesn't reach out to
the network-elements/library to discover features, the client needs a
way to absorb a fully populated list per platform/version out of band to
feed into compilation of what will be potentially greatly differing
trees.

I think it's difficult to put a number against this and tell the module
writer some amount is too many but rather consider the usability beyond
your specific focus model.

The aim should be for adoption but at certain points as a consumer I
would question common model usability in this fashion vs.
vendor/platform specific models that will theoritically have 100%
coverage.

> 
> 
> > Regards,
> > Reshad.
> >
> >
> 
> Andy
> 
> 
> 
> > On 2018-01-10, 4:33 PM, "Martin Bjorklund" <mbj@tail-f.com> wrote:
> >
> >     Hi,
> >
> >     "Reshad Rahman (rrahman)" <rrahman@cisco.com> wrote:
> >     > Hi,
> >     >
> >     > I am doing YD review of draft-ietf-pim-msdp-yang-01. The YANG module
> >     > is small but relatively speaking thereâ€™s a big number of features
> >     > 17. Basically each config knob has an if-feature.
> >     >
> >     > However keepalive-interval has a dependency on holdtime-interval via
> >     > must statement. Is the only way to enforce this to add â€œif-feature
> >     > peer-timer-holdtimeâ€� to leaf keepalive-internal?
> >
> >     Either that, or do:
> >
> >           must "(not ../holdtime-interval)"
> >              + " or (. > 1 and . < ../holdtime-interval)";
> >
> >     depending on which combinations they want to support.
> >
> >     17 features seems quite a lot...
> >
> >
> >
> >     >
> >     > Regards,
> >     > Reshad.
> >     >
> >     >          leaf holdtime-interval {
> >     >            if-feature peer-timer-holdtime;
> >     >            type uint16;
> >     >            units seconds;
> >     >            must ". > 3";
> >     >            default 75;
> >     >            description "The SA-Hold-Down-Period of this msdp peer.";
> >     >          }
> >     >          leaf keepalive-interval {
> >     >            if-feature peer-timer-keepalive;
> >     >            type uint16;
> >     >            units seconds;
> >     >            must ". > 1 and . < ../holdtime-interval";
> >     >            default 60;
> >     >            description "The keepalive timer of this msdp peer.";
> >     >          }
> >     >
> >     >
> >
> >
> >     /martin
> >
> >
> > _______________________________________________
> > yang-doctors mailing list
> > yang-doctors@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=Jl7tZIAix_56L5WitYmizrVtr4lri1GbY_gryWn2Zw4&s=-d8gjIFa6ZWhaMxzPnGU2M3QQbXsGpEJ9E7s5VdLuBU&e=
> >

> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=Jl7tZIAix_56L5WitYmizrVtr4lri1GbY_gryWn2Zw4&s=-d8gjIFa6ZWhaMxzPnGU2M3QQbXsGpEJ9E7s5VdLuBU&e=


From nobody Mon Jan 15 00:49:24 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD9D7127011 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 00:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 vlB2Iy5sr2Wd for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 00:49:19 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 633E4126DEE for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 00:49:18 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:68c6:92ff:fe01:2298]) by mail.nic.cz (Postfix) with ESMTPSA id 935DA63EAA; Mon, 15 Jan 2018 09:49:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1516006155; bh=jfIQ/l3aVmTa8H3EyZhC/oGGoIDlAq8pgqcHyveVIu8=; h=From:To:Date; b=g1sOWg7bkfheZyIOa+7ES2P+SODRvQe3edD3hLo+uG/bPZ1z/7GvBpelRbB8Rbewj 7UC2K4uwnNWOiHr1G4UKJQSj11Ilc+YB9Jxkp/teQ7J45beaVsLSK2wWde88xxOWPC uUmpwytK/+5JNxQVcyj7lMzrPRgtwGZL6smnayZ0=
Message-ID: <1516006155.5426.3.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Andy Bierman <andy@yumaworks.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, YANG Doctors <yang-doctors@ietf.org>
Date: Mon, 15 Jan 2018 09:49:15 +0100
In-Reply-To: <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com>
References: <1515579468.6095.29.camel@nic.cz> <20180110.125841.1275902835172392300.mbj@tail-f.com> <1515600384.11767.48.camel@nic.cz> <20180110.171811.858477092972700390.mbj@tail-f.com> <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/W3M6lV5DWrBYE3-tfRHv0YIlbUM>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 08:49:23 -0000

On Fri, 2018-01-12 at 09:45 -0800, Andy Bierman wrote:
> 
> 
> On Fri, Jan 12, 2018 at 2:13 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
> > Martin Bjorklund <mbj@tail-f.com> writes:
> > 
> > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > >> On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
> > >> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > >> > > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> > >> > > > Hi,
> > >> > > >
> > >> > > > Replying to this only on yang-doctors, since this is mostly a
> > >> > > > discussion about the interpretation of RFC 7950.
> > >> > > >
> > >> > > >
> > >> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > >> > > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > >> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > >> > > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > >> > > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > >> > > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee)
> > wrote:
> > >> > > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz>
> > wrote:
> > >> > > >
> > >> > > > [...]
> > >> > > >
> > >> > > > > > > > > > > 4. In "when" expressions, the module uses literal
> > strings
> > >> >
> > >> > for
> > >> > > > > > > > > > >   identities. This is known to be problematic, the
> > XPath
> > >> > > >
> > >> > > > functions
> > >> > > > > > > > > > >   derived-from() or derived-from-or-self() should be
> > used
> > >> > > >
> > >> > > > instead.
> > >> > > > > > > > > > >
> > >> > > > > > > > > >
> > >> > > > > > > > > > Why is this problematic? Is it because the types can be
> > >> >
> > >> > extended?
> > >> > > > > > > > >
> > >> > > > > > > > > That's one reason: derived identities should often also
> > satisfy
> > >> >
> > >> > the
> > >> > > > > > > > > constraint.
> > >> > > > > > > > >
> > >> > > > > > > > > But the more serious problem is that things like
> > >> > > > > > > > >
> > >> > > > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > >> > > > > > > > >
> > >> > > > > > > > > rely on plain string comparison that depends od the
> > actual
> > >> >
> > >> > prefix
> > >> > > > used
> > >> > > > > > > >
> > >> > > > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON
> > >> >
> > >> > encoding of
> > >> > > > > > > > > this value
> > >> > > > > > > > > would be "ietf-ospf:ospfv3" so the above expression is
> > always
> > >> > > >
> > >> > > > false.
> > >> > > > > > > >
> > >> > > > > > > > This is not correct; the when expression is not evaluated
> > on the
> > >> >
> > >> > JSON
> > >> > > > > > > > encoding.  See the last paragraph of section 9.10.3 in RFC
> > 7950:
> > >> > > > > > > >
> > >> > > > > > > >    The string value of a node of type "identityref" in a
> > "must" or
> > >> > > > > > > >    "when" XPath expression is the referred identity's
> > qualified
> > >> >
> > >> > name
> > >> > > > > > > >    with the prefix present.  If the referred identity is
> > defined
> > >> >
> > >> > in an
> > >> > > > > > > >    imported module, the prefix in the string value is the
> > prefix
> > >> > > >
> > >> > > > defined
> > >> > > > > > > >    in the corresponding "import" statement.  Otherwise, the
> > prefix
> > >> >
> > >> > in
> > >> > > > > > > >    the string value is the prefix for the current module.
> > >> > > > > > >
> > >> > > > > > > This is weird, to say the least. The leafref instance may
> > have an
> > >> > > >
> > >> > > > identity
> > >> > > > > > > value
> > >> > > > > > > that is defined in a module that (has to be implemented by
> > the
> > >> >
> > >> > server
> > >> > > > but)
> > >> > > > > > > needn't be imported in the module that contains the XPath
> > >> >
> > >> > expression. So
> > >> > > > I
> > >> > > > > > > don't
> > >> > > > > > > know what 'corresponding "import" statement' this paragraph
> > is
> > >> >
> > >> > talking
> > >> > > > > > > about.
> > >> > > > > >
> > >> > > > > > It has to import the module in order to give a prefix, which
> > then can
> > >> > > > > > be used in the XPath expression.
> > >> > > > >
> > >> > > > > In the XPath expression above, do you mean the "rt" prefix of
> > >> > > > > "rt:type"?
> > >> > > >
> > >> > > > No, I meant the "ospf" prefix for the module "ietf-ospf".
> > >> > > >
> > >> > > > > If so,
> > >> > > > > it is irrelevant for the string comparison, what's important is
> > the
> > >> >
> > >> > *value*
> > >> > > > of
> > >> > > > > the "rt:type" instance, which can be an identity defined in a
> > module
> > >> >
> > >> > that
> > >> > > > > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec.
> > 9.10.2:
> > >> > > > >
> > >> > > > >    On a particular server, the valid values are further
> > restricted
> > >> > > > >    to the set of identities defined in the modules implemented by
> > >> > > > >    the server.
> > >> > > >
> > >> > > > Because of the way the representation of identities work in
> > must/when
> > >> > > > expressions, you *must* import the module where the identity is
> > >> > > > define, if you want to use the identity for equality comparision
> > like
> > >> > > > in the example.
> > >> > > >
> > >> > > > You may have:
> > >> > > >
> > >> > > >   module a {
> > >> > > >     ...
> > >> > > >     import ietf-ospf {
> > >> > > >       prefix x;
> > >> > > >     }
> > >> > > >     ...
> > >> > > >     leaf foo {
> > >> > > >       when "../type = 'x:ospfv3'";
> > >> > > >       ...
> > >> > > >     }
> > >> > > >   }
> > >> > >
> > >> > > The problem here is not with the literal 'x:ospf' but rather with the
> > string
> > >> > > value of the leafref node instance ("../type" here), and clearly it
> > is what
> > >> >
> > >> > sec.
> > >> > > 9.10.3 talks about ("string value of a [leafref] node").
> > >> > >
> > >> > > I can define a module like
> > >> > >
> > >> > > module foo-ospf {
> > >> > >   namespace "http://example.com/foo-ospf";
> > >> > >   prefix ospf;
> > >> > >   import ietf-routing {
> > >> > >     prefix rt;
> > >> > >   }
> > >> > >   identity ospfv3 {
> > >> > >     base "rt:routing-protocol";
> > >> > >   }
> > >> > >   ...
> > >> > > }
> > >> > >
> > >> > > Now, if the server advertizes both ietf-ospf and foo-ospf as
> > implemented
> > >> >
> > >> > (which
> > >> > > is legal), the module foo-ospf needn't be imported anywhere and still
> > the
> > >> >
> > >> > "type"
> > >> > > leaf instance can have both values "ietf-ospf:ospfv3" and "foo-
> > ospf:ospfv3",
> > >> > > provided that it is defined as
> > >> > >
> > >> > > leaf type {
> > >> > >   type identityref {
> > >> > >     base rt:routing-protocol;
> > >> > >   }
> > >> > > }
> > >> > >
> > >> > > And I wonder what the last paragraph in sec. 9.10.3 means in this
> > situation,
> > >> > > i.e. what string value of "type" is used in the evaluation of the
> > XPath
> > >> > > expression in your module "a", if the value-space value of 'type'
> > instance
> > >> >
> > >> > in a
> > >> > > datastore is either of the two '...:ospfv3' identities.
> > >> > >
> > >> > > Do you see what I mean?
> > >> >
> > >> > Do you mean that the problem is that the spec does not define what the
> > >> > string value is if the module where the identity is defined is not
> > >> > imported?
> > >> >
> > >> > I agree that this is an issue.
> > >> >
> > >> > BUT, actually, if you look the text in the spec:
> > >> >
> > >> >    The string value of a node of type "identityref" in a "must" or
> > >> >    "when" XPath expression is the referred identity's qualified name
> > >> >    with the prefix present.  If the referred identity is defined in an
> > >> >    imported module, the prefix in the string value is the prefix
> > defined
> > >> >    in the corresponding "import" statement.  Otherwise, the prefix in
> > >> >    the string value is the prefix for the current module.
> > >> >
> > >> > If you blindly follow this, the last sentence would have to apply, and
> > >> > the string would be "a:ospfv3", which clearly is broken.
> > >>
> > >> It depends on what "current module" means.
> > >
> > > "current module" and "local module" means the module where the "must"
> > > or "when" expression is defined.  There was a separate thread about
> > > this as well.
> > 
> > OK, then it really makes no sense to add the local prefix.
> > 
> > >
> > >> It could also be interpreted as the
> > >> module in which the identity is defined, but then we can get the
> > collision of
> > >> prefixes as in my example.
> > >>
> > >> >
> > >> > For all practical purposes, I think the string value can be "" if the
> > >> > identity is defined in a module that is not imported, and is not
> > >> > defined in the current module.
> > >>
> > >> I think a better solution would be to avoid prefixes in lexical-space
> > identity
> > >> values altogether and use the same string as in JSON encoding (RFC 7951).
> > The
> > >> XPath expression from your example would become
> > >>
> > >>     "../type = 'ietf-ospf:ospfv3'"
> > >>
> > >> Everything would then be straightforward and non-ambiguous.
> > >
> > > Yes, as I wrote in my previous email, I agree, this would be better.
> > > But that's for YANG 2.0, unfortunately.
> > 
> > Maybe not. If we agree that the last paragraph in 9.10.3 is wrong ang
> > needs an erratum, then I think instead of saying that the XPath string
> > value is the empty string as you suggested (which is weird and
> > non-intuitive), this paragraph can say that the value (only for XPath!)
> > is as in RFC 7951.
> > 
> > In fact, after re-reading sec. 9.10, I believe it is even not required
> > to import the module in order to be able to use the prefix in a string
> > literal, as "x" in
> > 
> >     "../type = 'x:ospfv3'"
> > 
> > because it is just an XPath 1.0 string with no additional semantics, so
> > module authors can equally well write
> > 
> >     "../type = 'ietf-ospf:ospfv3'"
> > 
> > without importing "ietf-ospf".
> > 
> > Of course, we could also replace the paragraph with a statement that the
> > result of using bare identityref string values in XPath is undefined and
> > thus force everybody to use the XPath functions.
> > 
> 
> 
> I do not agree with this interpretation.
> The term "prefix" is used 10 times in that section.
> It is clear that the WG meant "prefix" not "module name".
> This cannot be changed by an errata.

So what do you suggest? The last paragraph in sec. 9.10.3 is clearly wrong.

Note also that this paragraphs tries to define the string value of an
identityref node instance for any XPath expression, which needn't necessarily be
a simple EqualityExpr.

Lada

> 
>  
> > Lada
> 
> 
> Andy
>  
> > >
> > >
> > > /martin
> > >
> > >
> > >
> > >
> > >>
> > >> Lada
> > >>
> > >> >
> > >> >
> > >> > /martin
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > >
> > >> > > Lada
> > >> > >
> > >> > >
> > >> > > >
> > >> > > > and
> > >> > > >
> > >> > > >   module b {
> > >> > > >     ...
> > >> > > >     import ietf-ospf {
> > >> > > >       prefix y;
> > >> > > >     }
> > >> > > >     ...
> > >> > > >     leaf bar {
> > >> > > >       when "../type = 'y:ospfv3'";
> > >> > > >       ...
> > >> > > >     }
> > >> > > >   }
> > >> > > >
> > >> > > > You may not like it, but these two modules are both correct
> > according
> > >> > > > to the rules defined in RFC 7950.  The string value of the "type"
> > leaf
> > >> > > > *when evaluating the when expression* is different in the different
> > >> > > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> > >> > > >
> > >> > > > > > > Also, potentially there can be a collision in prefixes and
> > then this
> > >> > > >
> > >> > > > also
> > >> > > > > > > breaks down.
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > No, two modules cannot be imported with the same prefix.
> > >> > > > >
> > >> > > > > I have to disagree. An identity derived from the
> > >> > > > > "ietf-routing:control-protocol-type" base identity can be defined
> > >> > > > > in a module that is not imported anywhere. If a server declares
> > such
> > >> > > > > a module as implemented, then "rt:type" may have this value per
> > >> > > > > sec. 9.10.2.
> > >> > > > >
> > >> > > > > And, consequently, there may be two different modules with
> > >> > > > > conflicting prefixes defining identities that are derived from
> > >> > > > > "ietf-routing:control-protocol-type".
> > >> > > >
> > >> > > > Sure, but this is not the point.
> > >> > > >
> > >> > > > > > > A moral of the namespace/prefix story in XML was that relying
> > of
> > >> > > > > > > namespace prefixes having a particular value is a really bad
> > >> > > > > > > idea. I know that the cited paragraph was intended to make
> > such
> > >> > > > > > > XPath string comparisons more deterministic, but it is also
> > >> > > > > > > problematic and should be avoided if possible.
> > >> > > > > >
> > >> > > > > > Note that this prefix is under the control of the module
> > designer
> > >> > > > > > writing the XPath expression.  The same identityref value might
> > use a
> > >> > > > >
> > >> > > > > No, it is not. The prefixes appear in instance data.
> > >> > > >
> > >> > > > The prefix *in the when expression* is under the control of the
> > module
> > >> > > > designer, as explained above.
> > >> > > >
> > >> > > > You are correct that the prefix in an XML encoding is not under
> > >> > > > control of the module designer, but noone has claimed that.
> > >> > > >
> > >> > > > I agree that it is unfortunate that context-specific prefixes are
> > used
> > >> > > > for the identityref values.  It would have been better if we used a
> > >> > > > context free representation, e.g. "<module-name>:<identity>".  But
> > >> > > > that's another discussion.
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > /martin
> > >> > >
> > >> > > --
> > >> > > Ladislav Lhotka
> > >> > > Head, CZ.NIC Labs
> > >> > > PGP Key ID: 0xB8F92B08A9F76C67
> > >> > >
> > >> --
> > >> Ladislav Lhotka
> > >> Head, CZ.NIC Labs
> > >> PGP Key ID: 0xB8F92B08A9F76C67
> > >>
> > >> _______________________________________________
> > >> yang-doctors mailing list
> > >> yang-doctors@ietf.org
> > >> https://www.ietf.org/mailman/listinfo/yang-doctors
> > >>
> > 
> > --
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> > 
> > _______________________________________________
> > yang-doctors mailing list
> > yang-doctors@ietf.org
> > https://www.ietf.org/mailman/listinfo/yang-doctors
> 
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan 15 00:59:49 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD0A912D942 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 00:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 VxUleAsZG6Zl for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 00:59:44 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id CEF02126D45 for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 00:59:43 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id AE0DB1AE0144; Mon, 15 Jan 2018 09:59:41 +0100 (CET)
Date: Mon, 15 Jan 2018 09:59:41 +0100 (CET)
Message-Id: <20180115.095941.341257692373089671.mbj@tail-f.com>
To: lhotka@nic.cz
Cc: andy@yumaworks.com, yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <1516006155.5426.3.camel@nic.cz>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/EoP3XfP8hfDR4vikto1ZDTJv7YE>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 08:59:48 -0000

Ladislav Lhotka <lhotka@nic.cz> wrote:
> On Fri, 2018-01-12 at 09:45 -0800, Andy Bierman wrote:
> > 
> > 
> > On Fri, Jan 12, 2018 at 2:13 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > Martin Bjorklund <mbj@tail-f.com> writes:
> > > 
> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > >> On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
> > > >> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > >> > > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> > > >> > > > Hi,
> > > >> > > >
> > > >> > > > Replying to this only on yang-doctors, since this is mostly a
> > > >> > > > discussion about the interpretation of RFC 7950.
> > > >> > > >
> > > >> > > >
> > > >> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > >> > > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > > >> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > >> > > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund wrote:
> > > >> > > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > >> > > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee)
> > > wrote:
> > > >> > > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.cz>
> > > wrote:
> > > >> > > >
> > > >> > > > [...]
> > > >> > > >
> > > >> > > > > > > > > > > 4. In "when" expressions, the module uses literal
> > > strings
> > > >> >
> > > >> > for
> > > >> > > > > > > > > > >   identities. This is known to be problematic, the
> > > XPath
> > > >> > > >
> > > >> > > > functions
> > > >> > > > > > > > > > >   derived-from() or derived-from-or-self() should be
> > > used
> > > >> > > >
> > > >> > > > instead.
> > > >> > > > > > > > > > >
> > > >> > > > > > > > > >
> > > >> > > > > > > > > > Why is this problematic? Is it because the types can be
> > > >> >
> > > >> > extended?
> > > >> > > > > > > > >
> > > >> > > > > > > > > That's one reason: derived identities should often also
> > > satisfy
> > > >> >
> > > >> > the
> > > >> > > > > > > > > constraint.
> > > >> > > > > > > > >
> > > >> > > > > > > > > But the more serious problem is that things like
> > > >> > > > > > > > >
> > > >> > > > > > > > >     when "../../../../../../../rt:type = 'ospf:ospfv3'"
> > > >> > > > > > > > >
> > > >> > > > > > > > > rely on plain string comparison that depends od the
> > > actual
> > > >> >
> > > >> > prefix
> > > >> > > > used
> > > >> > > > > > > >
> > > >> > > > > > > > > "rt:type" value. For one, according to RFC 7951 the JSON
> > > >> >
> > > >> > encoding of
> > > >> > > > > > > > > this value
> > > >> > > > > > > > > would be "ietf-ospf:ospfv3" so the above expression is
> > > always
> > > >> > > >
> > > >> > > > false.
> > > >> > > > > > > >
> > > >> > > > > > > > This is not correct; the when expression is not evaluated
> > > on the
> > > >> >
> > > >> > JSON
> > > >> > > > > > > > encoding.  See the last paragraph of section 9.10.3 in RFC
> > > 7950:
> > > >> > > > > > > >
> > > >> > > > > > > >    The string value of a node of type "identityref" in a
> > > "must" or
> > > >> > > > > > > >    "when" XPath expression is the referred identity's
> > > qualified
> > > >> >
> > > >> > name
> > > >> > > > > > > >    with the prefix present.  If the referred identity is
> > > defined
> > > >> >
> > > >> > in an
> > > >> > > > > > > >    imported module, the prefix in the string value is the
> > > prefix
> > > >> > > >
> > > >> > > > defined
> > > >> > > > > > > >    in the corresponding "import" statement.  Otherwise, the
> > > prefix
> > > >> >
> > > >> > in
> > > >> > > > > > > >    the string value is the prefix for the current module.
> > > >> > > > > > >
> > > >> > > > > > > This is weird, to say the least. The leafref instance may
> > > have an
> > > >> > > >
> > > >> > > > identity
> > > >> > > > > > > value
> > > >> > > > > > > that is defined in a module that (has to be implemented by
> > > the
> > > >> >
> > > >> > server
> > > >> > > > but)
> > > >> > > > > > > needn't be imported in the module that contains the XPath
> > > >> >
> > > >> > expression. So
> > > >> > > > I
> > > >> > > > > > > don't
> > > >> > > > > > > know what 'corresponding "import" statement' this paragraph
> > > is
> > > >> >
> > > >> > talking
> > > >> > > > > > > about.
> > > >> > > > > >
> > > >> > > > > > It has to import the module in order to give a prefix, which
> > > then can
> > > >> > > > > > be used in the XPath expression.
> > > >> > > > >
> > > >> > > > > In the XPath expression above, do you mean the "rt" prefix of
> > > >> > > > > "rt:type"?
> > > >> > > >
> > > >> > > > No, I meant the "ospf" prefix for the module "ietf-ospf".
> > > >> > > >
> > > >> > > > > If so,
> > > >> > > > > it is irrelevant for the string comparison, what's important is
> > > the
> > > >> >
> > > >> > *value*
> > > >> > > > of
> > > >> > > > > the "rt:type" instance, which can be an identity defined in a
> > > module
> > > >> >
> > > >> > that
> > > >> > > > > needn't be imported by ietf-routing, ietf-ospf or whatever. Sec.
> > > 9.10.2:
> > > >> > > > >
> > > >> > > > >    On a particular server, the valid values are further
> > > restricted
> > > >> > > > >    to the set of identities defined in the modules implemented by
> > > >> > > > >    the server.
> > > >> > > >
> > > >> > > > Because of the way the representation of identities work in
> > > must/when
> > > >> > > > expressions, you *must* import the module where the identity is
> > > >> > > > define, if you want to use the identity for equality comparision
> > > like
> > > >> > > > in the example.
> > > >> > > >
> > > >> > > > You may have:
> > > >> > > >
> > > >> > > >   module a {
> > > >> > > >     ...
> > > >> > > >     import ietf-ospf {
> > > >> > > >       prefix x;
> > > >> > > >     }
> > > >> > > >     ...
> > > >> > > >     leaf foo {
> > > >> > > >       when "../type = 'x:ospfv3'";
> > > >> > > >       ...
> > > >> > > >     }
> > > >> > > >   }
> > > >> > >
> > > >> > > The problem here is not with the literal 'x:ospf' but rather with the
> > > string
> > > >> > > value of the leafref node instance ("../type" here), and clearly it
> > > is what
> > > >> >
> > > >> > sec.
> > > >> > > 9.10.3 talks about ("string value of a [leafref] node").
> > > >> > >
> > > >> > > I can define a module like
> > > >> > >
> > > >> > > module foo-ospf {
> > > >> > >   namespace "http://example.com/foo-ospf";
> > > >> > >   prefix ospf;
> > > >> > >   import ietf-routing {
> > > >> > >     prefix rt;
> > > >> > >   }
> > > >> > >   identity ospfv3 {
> > > >> > >     base "rt:routing-protocol";
> > > >> > >   }
> > > >> > >   ...
> > > >> > > }
> > > >> > >
> > > >> > > Now, if the server advertizes both ietf-ospf and foo-ospf as
> > > implemented
> > > >> >
> > > >> > (which
> > > >> > > is legal), the module foo-ospf needn't be imported anywhere and still
> > > the
> > > >> >
> > > >> > "type"
> > > >> > > leaf instance can have both values "ietf-ospf:ospfv3" and "foo-
> > > ospf:ospfv3",
> > > >> > > provided that it is defined as
> > > >> > >
> > > >> > > leaf type {
> > > >> > >   type identityref {
> > > >> > >     base rt:routing-protocol;
> > > >> > >   }
> > > >> > > }
> > > >> > >
> > > >> > > And I wonder what the last paragraph in sec. 9.10.3 means in this
> > > situation,
> > > >> > > i.e. what string value of "type" is used in the evaluation of the
> > > XPath
> > > >> > > expression in your module "a", if the value-space value of 'type'
> > > instance
> > > >> >
> > > >> > in a
> > > >> > > datastore is either of the two '...:ospfv3' identities.
> > > >> > >
> > > >> > > Do you see what I mean?
> > > >> >
> > > >> > Do you mean that the problem is that the spec does not define what the
> > > >> > string value is if the module where the identity is defined is not
> > > >> > imported?
> > > >> >
> > > >> > I agree that this is an issue.
> > > >> >
> > > >> > BUT, actually, if you look the text in the spec:
> > > >> >
> > > >> >    The string value of a node of type "identityref" in a "must" or
> > > >> >    "when" XPath expression is the referred identity's qualified name
> > > >> >    with the prefix present.  If the referred identity is defined in an
> > > >> >    imported module, the prefix in the string value is the prefix
> > > defined
> > > >> >    in the corresponding "import" statement.  Otherwise, the prefix in
> > > >> >    the string value is the prefix for the current module.
> > > >> >
> > > >> > If you blindly follow this, the last sentence would have to apply, and
> > > >> > the string would be "a:ospfv3", which clearly is broken.
> > > >>
> > > >> It depends on what "current module" means.
> > > >
> > > > "current module" and "local module" means the module where the "must"
> > > > or "when" expression is defined.  There was a separate thread about
> > > > this as well.
> > > 
> > > OK, then it really makes no sense to add the local prefix.
> > > 
> > > >
> > > >> It could also be interpreted as the
> > > >> module in which the identity is defined, but then we can get the
> > > collision of
> > > >> prefixes as in my example.
> > > >>
> > > >> >
> > > >> > For all practical purposes, I think the string value can be "" if the
> > > >> > identity is defined in a module that is not imported, and is not
> > > >> > defined in the current module.
> > > >>
> > > >> I think a better solution would be to avoid prefixes in lexical-space
> > > identity
> > > >> values altogether and use the same string as in JSON encoding (RFC 7951).
> > > The
> > > >> XPath expression from your example would become
> > > >>
> > > >>     "../type = 'ietf-ospf:ospfv3'"
> > > >>
> > > >> Everything would then be straightforward and non-ambiguous.
> > > >
> > > > Yes, as I wrote in my previous email, I agree, this would be better.
> > > > But that's for YANG 2.0, unfortunately.
> > > 
> > > Maybe not. If we agree that the last paragraph in 9.10.3 is wrong ang
> > > needs an erratum, then I think instead of saying that the XPath string
> > > value is the empty string as you suggested (which is weird and
> > > non-intuitive), this paragraph can say that the value (only for XPath!)
> > > is as in RFC 7951.
> > > 
> > > In fact, after re-reading sec. 9.10, I believe it is even not required
> > > to import the module in order to be able to use the prefix in a string
> > > literal, as "x" in
> > > 
> > >     "../type = 'x:ospfv3'"
> > > 
> > > because it is just an XPath 1.0 string with no additional semantics, so
> > > module authors can equally well write
> > > 
> > >     "../type = 'ietf-ospf:ospfv3'"
> > > 
> > > without importing "ietf-ospf".
> > > 
> > > Of course, we could also replace the paragraph with a statement that the
> > > result of using bare identityref string values in XPath is undefined and
> > > thus force everybody to use the XPath functions.
> > > 
> > 
> > 
> > I do not agree with this interpretation.
> > The term "prefix" is used 10 times in that section.
> > It is clear that the WG meant "prefix" not "module name".
> > This cannot be changed by an errata.
> 
> So what do you suggest? The last paragraph in sec. 9.10.3 is clearly wrong.

I agree it is wrong, but only for identityref values that are defined
in a module that has not been imported.  I stronlgy agree w/ Andy that
this does NOT mean that we should change *working* and defined
behaviour in an errata.

The intention (for better or worse) was that the value would use the
prefix used in imports.  This means that if you want to do any kind of
comparision of the string value to some known identities, then you
must import that module so that there is a prefix defined.  This was
the intention.

>From this follows that (for all practical matters), the string value
of an identity defined in a module that is not imported doesn't really
matter.

> Note also that this paragraphs tries to define the string value of an
> identityref node instance for any XPath expression, which needn't necessarily be
> a simple EqualityExpr.



/martin



> 
> Lada
> 
> > 
> >  
> > > Lada
> > 
> > 
> > Andy
> >  
> > > >
> > > >
> > > > /martin
> > > >
> > > >
> > > >
> > > >
> > > >>
> > > >> Lada
> > > >>
> > > >> >
> > > >> >
> > > >> > /martin
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > >
> > > >> > > Lada
> > > >> > >
> > > >> > >
> > > >> > > >
> > > >> > > > and
> > > >> > > >
> > > >> > > >   module b {
> > > >> > > >     ...
> > > >> > > >     import ietf-ospf {
> > > >> > > >       prefix y;
> > > >> > > >     }
> > > >> > > >     ...
> > > >> > > >     leaf bar {
> > > >> > > >       when "../type = 'y:ospfv3'";
> > > >> > > >       ...
> > > >> > > >     }
> > > >> > > >   }
> > > >> > > >
> > > >> > > > You may not like it, but these two modules are both correct
> > > according
> > > >> > > > to the rules defined in RFC 7950.  The string value of the "type"
> > > leaf
> > > >> > > > *when evaluating the when expression* is different in the different
> > > >> > > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> > > >> > > >
> > > >> > > > > > > Also, potentially there can be a collision in prefixes and
> > > then this
> > > >> > > >
> > > >> > > > also
> > > >> > > > > > > breaks down.
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > > > No, two modules cannot be imported with the same prefix.
> > > >> > > > >
> > > >> > > > > I have to disagree. An identity derived from the
> > > >> > > > > "ietf-routing:control-protocol-type" base identity can be defined
> > > >> > > > > in a module that is not imported anywhere. If a server declares
> > > such
> > > >> > > > > a module as implemented, then "rt:type" may have this value per
> > > >> > > > > sec. 9.10.2.
> > > >> > > > >
> > > >> > > > > And, consequently, there may be two different modules with
> > > >> > > > > conflicting prefixes defining identities that are derived from
> > > >> > > > > "ietf-routing:control-protocol-type".
> > > >> > > >
> > > >> > > > Sure, but this is not the point.
> > > >> > > >
> > > >> > > > > > > A moral of the namespace/prefix story in XML was that relying
> > > of
> > > >> > > > > > > namespace prefixes having a particular value is a really bad
> > > >> > > > > > > idea. I know that the cited paragraph was intended to make
> > > such
> > > >> > > > > > > XPath string comparisons more deterministic, but it is also
> > > >> > > > > > > problematic and should be avoided if possible.
> > > >> > > > > >
> > > >> > > > > > Note that this prefix is under the control of the module
> > > designer
> > > >> > > > > > writing the XPath expression.  The same identityref value might
> > > use a
> > > >> > > > >
> > > >> > > > > No, it is not. The prefixes appear in instance data.
> > > >> > > >
> > > >> > > > The prefix *in the when expression* is under the control of the
> > > module
> > > >> > > > designer, as explained above.
> > > >> > > >
> > > >> > > > You are correct that the prefix in an XML encoding is not under
> > > >> > > > control of the module designer, but noone has claimed that.
> > > >> > > >
> > > >> > > > I agree that it is unfortunate that context-specific prefixes are
> > > used
> > > >> > > > for the identityref values.  It would have been better if we used a
> > > >> > > > context free representation, e.g. "<module-name>:<identity>".  But
> > > >> > > > that's another discussion.
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > /martin
> > > >> > >
> > > >> > > --
> > > >> > > Ladislav Lhotka
> > > >> > > Head, CZ.NIC Labs
> > > >> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > >> > >
> > > >> --
> > > >> Ladislav Lhotka
> > > >> Head, CZ.NIC Labs
> > > >> PGP Key ID: 0xB8F92B08A9F76C67
> > > >>
> > > >> _______________________________________________
> > > >> yang-doctors mailing list
> > > >> yang-doctors@ietf.org
> > > >> https://www.ietf.org/mailman/listinfo/yang-doctors
> > > >>
> > > 
> > > --
> > > Ladislav Lhotka
> > > Head, CZ.NIC Labs
> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > 
> > > _______________________________________________
> > > yang-doctors mailing list
> > > yang-doctors@ietf.org
> > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > 
> > 
> -- 
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
> 


From nobody Mon Jan 15 01:38:27 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15E19126CD6 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 01:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 gpoZisL73lVR for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 01:38:21 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 56E5C12D86B for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 01:38:21 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:68c6:92ff:fe01:2298]) by mail.nic.cz (Postfix) with ESMTPSA id 6616663F3A; Mon, 15 Jan 2018 10:38:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1516009099; bh=XqQJ88Mi6rDMqap3fJljjhrR8jHBmJJOv2XNWoAqrkU=; h=From:To:Date; b=pgS/kauGglZc5OMlyu4mYQebQpGcqrMZCLzmslsI0PuNDFXPG8bI7IELTMCV+ShFu 9VtqBGn+cn2LttTsUloDNkyibaZmyh/IxMcQiR3Of3tyV+HIxdLP/2H0hQQImO9tFG kpuZuuo04HXVaK6c1efruLWSoeW5u5ZT27ODPDhc=
Message-ID: <1516009099.5426.13.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: andy@yumaworks.com, yang-doctors@ietf.org
Date: Mon, 15 Jan 2018 10:38:19 +0100
In-Reply-To: <20180115.095941.341257692373089671.mbj@tail-f.com>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/VMiUJzP2HxH94UmQfd4DAqSX1OQ>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 09:38:26 -0000

On Mon, 2018-01-15 at 09:59 +0100, Martin Bjorklund wrote:
> Ladislav Lhotka <lhotka@nic.cz> wrote:
> > On Fri, 2018-01-12 at 09:45 -0800, Andy Bierman wrote:
> > > 
> > > 
> > > On Fri, Jan 12, 2018 at 2:13 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > Martin Bjorklund <mbj@tail-f.com> writes:
> > > > 
> > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > >> On Wed, 2018-01-10 at 12:58 +0100, Martin Bjorklund wrote:
> > > > >> > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > >> > > On Wed, 2018-01-10 at 10:35 +0100, Martin Bjorklund wrote:
> > > > >> > > > Hi,
> > > > >> > > >
> > > > >> > > > Replying to this only on yang-doctors, since this is mostly a
> > > > >> > > > discussion about the interpretation of RFC 7950.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > >> > > > > On Tue, 2018-01-09 at 16:23 +0100, Martin Bjorklund wrote:
> > > > >> > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > >> > > > > > > On Tue, 2018-01-09 at 09:06 +0100, Martin Bjorklund
> wrote:
> > > > >> > > > > > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> > > > >> > > > > > > > > On Mon, 2018-01-08 at 19:28 +0000, Acee Lindem (acee)
> > > > wrote:
> > > > >> > > > > > > > > > On 12/6/17, 6:26 AM, "Ladislav Lhotka" <lhotka@nic.
> cz>
> > > > wrote:
> > > > >> > > >
> > > > >> > > > [...]
> > > > >> > > >
> > > > >> > > > > > > > > > > 4. In "when" expressions, the module uses literal
> > > > strings
> > > > >> >
> > > > >> > for
> > > > >> > > > > > > > > > >   identities. This is known to be problematic,
> the
> > > > XPath
> > > > >> > > >
> > > > >> > > > functions
> > > > >> > > > > > > > > > >   derived-from() or derived-from-or-self() should
> be
> > > > used
> > > > >> > > >
> > > > >> > > > instead.
> > > > >> > > > > > > > > > >
> > > > >> > > > > > > > > >
> > > > >> > > > > > > > > > Why is this problematic? Is it because the types
> can be
> > > > >> >
> > > > >> > extended?
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > That's one reason: derived identities should often
> also
> > > > satisfy
> > > > >> >
> > > > >> > the
> > > > >> > > > > > > > > constraint.
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > But the more serious problem is that things like
> > > > >> > > > > > > > >
> > > > >> > > > > > > > >     when "../../../../../../../rt:type =
> 'ospf:ospfv3'"
> > > > >> > > > > > > > >
> > > > >> > > > > > > > > rely on plain string comparison that depends od the
> > > > actual
> > > > >> >
> > > > >> > prefix
> > > > >> > > > used
> > > > >> > > > > > > >
> > > > >> > > > > > > > > "rt:type" value. For one, according to RFC 7951 the
> JSON
> > > > >> >
> > > > >> > encoding of
> > > > >> > > > > > > > > this value
> > > > >> > > > > > > > > would be "ietf-ospf:ospfv3" so the above expression
> is
> > > > always
> > > > >> > > >
> > > > >> > > > false.
> > > > >> > > > > > > >
> > > > >> > > > > > > > This is not correct; the when expression is not
> evaluated
> > > > on the
> > > > >> >
> > > > >> > JSON
> > > > >> > > > > > > > encoding.  See the last paragraph of section 9.10.3 in
> RFC
> > > > 7950:
> > > > >> > > > > > > >
> > > > >> > > > > > > >    The string value of a node of type "identityref" in
> a
> > > > "must" or
> > > > >> > > > > > > >    "when" XPath expression is the referred identity's
> > > > qualified
> > > > >> >
> > > > >> > name
> > > > >> > > > > > > >    with the prefix present.  If the referred identity
> is
> > > > defined
> > > > >> >
> > > > >> > in an
> > > > >> > > > > > > >    imported module, the prefix in the string value is
> the
> > > > prefix
> > > > >> > > >
> > > > >> > > > defined
> > > > >> > > > > > > >    in the corresponding "import" statement.  Otherwise,
> the
> > > > prefix
> > > > >> >
> > > > >> > in
> > > > >> > > > > > > >    the string value is the prefix for the current
> module.
> > > > >> > > > > > >
> > > > >> > > > > > > This is weird, to say the least. The leafref instance may
> > > > have an
> > > > >> > > >
> > > > >> > > > identity
> > > > >> > > > > > > value
> > > > >> > > > > > > that is defined in a module that (has to be implemented
> by
> > > > the
> > > > >> >
> > > > >> > server
> > > > >> > > > but)
> > > > >> > > > > > > needn't be imported in the module that contains the XPath
> > > > >> >
> > > > >> > expression. So
> > > > >> > > > I
> > > > >> > > > > > > don't
> > > > >> > > > > > > know what 'corresponding "import" statement' this
> paragraph
> > > > is
> > > > >> >
> > > > >> > talking
> > > > >> > > > > > > about.
> > > > >> > > > > >
> > > > >> > > > > > It has to import the module in order to give a prefix,
> which
> > > > then can
> > > > >> > > > > > be used in the XPath expression.
> > > > >> > > > >
> > > > >> > > > > In the XPath expression above, do you mean the "rt" prefix of
> > > > >> > > > > "rt:type"?
> > > > >> > > >
> > > > >> > > > No, I meant the "ospf" prefix for the module "ietf-ospf".
> > > > >> > > >
> > > > >> > > > > If so,
> > > > >> > > > > it is irrelevant for the string comparison, what's important
> is
> > > > the
> > > > >> >
> > > > >> > *value*
> > > > >> > > > of
> > > > >> > > > > the "rt:type" instance, which can be an identity defined in a
> > > > module
> > > > >> >
> > > > >> > that
> > > > >> > > > > needn't be imported by ietf-routing, ietf-ospf or whatever.
> Sec.
> > > > 9.10.2:
> > > > >> > > > >
> > > > >> > > > >    On a particular server, the valid values are further
> > > > restricted
> > > > >> > > > >    to the set of identities defined in the modules
> implemented by
> > > > >> > > > >    the server.
> > > > >> > > >
> > > > >> > > > Because of the way the representation of identities work in
> > > > must/when
> > > > >> > > > expressions, you *must* import the module where the identity is
> > > > >> > > > define, if you want to use the identity for equality
> comparision
> > > > like
> > > > >> > > > in the example.
> > > > >> > > >
> > > > >> > > > You may have:
> > > > >> > > >
> > > > >> > > >   module a {
> > > > >> > > >     ...
> > > > >> > > >     import ietf-ospf {
> > > > >> > > >       prefix x;
> > > > >> > > >     }
> > > > >> > > >     ...
> > > > >> > > >     leaf foo {
> > > > >> > > >       when "../type = 'x:ospfv3'";
> > > > >> > > >       ...
> > > > >> > > >     }
> > > > >> > > >   }
> > > > >> > >
> > > > >> > > The problem here is not with the literal 'x:ospf' but rather with
> the
> > > > string
> > > > >> > > value of the leafref node instance ("../type" here), and clearly
> it
> > > > is what
> > > > >> >
> > > > >> > sec.
> > > > >> > > 9.10.3 talks about ("string value of a [leafref] node").
> > > > >> > >
> > > > >> > > I can define a module like
> > > > >> > >
> > > > >> > > module foo-ospf {
> > > > >> > >   namespace "http://example.com/foo-ospf";
> > > > >> > >   prefix ospf;
> > > > >> > >   import ietf-routing {
> > > > >> > >     prefix rt;
> > > > >> > >   }
> > > > >> > >   identity ospfv3 {
> > > > >> > >     base "rt:routing-protocol";
> > > > >> > >   }
> > > > >> > >   ...
> > > > >> > > }
> > > > >> > >
> > > > >> > > Now, if the server advertizes both ietf-ospf and foo-ospf as
> > > > implemented
> > > > >> >
> > > > >> > (which
> > > > >> > > is legal), the module foo-ospf needn't be imported anywhere and
> still
> > > > the
> > > > >> >
> > > > >> > "type"
> > > > >> > > leaf instance can have both values "ietf-ospf:ospfv3" and "foo-
> > > > ospf:ospfv3",
> > > > >> > > provided that it is defined as
> > > > >> > >
> > > > >> > > leaf type {
> > > > >> > >   type identityref {
> > > > >> > >     base rt:routing-protocol;
> > > > >> > >   }
> > > > >> > > }
> > > > >> > >
> > > > >> > > And I wonder what the last paragraph in sec. 9.10.3 means in this
> > > > situation,
> > > > >> > > i.e. what string value of "type" is used in the evaluation of the
> > > > XPath
> > > > >> > > expression in your module "a", if the value-space value of 'type'
> > > > instance
> > > > >> >
> > > > >> > in a
> > > > >> > > datastore is either of the two '...:ospfv3' identities.
> > > > >> > >
> > > > >> > > Do you see what I mean?
> > > > >> >
> > > > >> > Do you mean that the problem is that the spec does not define what
> the
> > > > >> > string value is if the module where the identity is defined is not
> > > > >> > imported?
> > > > >> >
> > > > >> > I agree that this is an issue.
> > > > >> >
> > > > >> > BUT, actually, if you look the text in the spec:
> > > > >> >
> > > > >> >    The string value of a node of type "identityref" in a "must" or
> > > > >> >    "when" XPath expression is the referred identity's qualified
> name
> > > > >> >    with the prefix present.  If the referred identity is defined in
> an
> > > > >> >    imported module, the prefix in the string value is the prefix
> > > > defined
> > > > >> >    in the corresponding "import" statement.  Otherwise, the prefix
> in
> > > > >> >    the string value is the prefix for the current module.
> > > > >> >
> > > > >> > If you blindly follow this, the last sentence would have to apply,
> and
> > > > >> > the string would be "a:ospfv3", which clearly is broken.
> > > > >>
> > > > >> It depends on what "current module" means.
> > > > >
> > > > > "current module" and "local module" means the module where the "must"
> > > > > or "when" expression is defined.  There was a separate thread about
> > > > > this as well.
> > > > 
> > > > OK, then it really makes no sense to add the local prefix.
> > > > 
> > > > >
> > > > >> It could also be interpreted as the
> > > > >> module in which the identity is defined, but then we can get the
> > > > collision of
> > > > >> prefixes as in my example.
> > > > >>
> > > > >> >
> > > > >> > For all practical purposes, I think the string value can be "" if
> the
> > > > >> > identity is defined in a module that is not imported, and is not
> > > > >> > defined in the current module.
> > > > >>
> > > > >> I think a better solution would be to avoid prefixes in lexical-space
> > > > identity
> > > > >> values altogether and use the same string as in JSON encoding (RFC
> 7951).
> > > > The
> > > > >> XPath expression from your example would become
> > > > >>
> > > > >>     "../type = 'ietf-ospf:ospfv3'"
> > > > >>
> > > > >> Everything would then be straightforward and non-ambiguous.
> > > > >
> > > > > Yes, as I wrote in my previous email, I agree, this would be better.
> > > > > But that's for YANG 2.0, unfortunately.
> > > > 
> > > > Maybe not. If we agree that the last paragraph in 9.10.3 is wrong ang
> > > > needs an erratum, then I think instead of saying that the XPath string
> > > > value is the empty string as you suggested (which is weird and
> > > > non-intuitive), this paragraph can say that the value (only for XPath!)
> > > > is as in RFC 7951.
> > > > 
> > > > In fact, after re-reading sec. 9.10, I believe it is even not required
> > > > to import the module in order to be able to use the prefix in a string
> > > > literal, as "x" in
> > > > 
> > > >     "../type = 'x:ospfv3'"
> > > > 
> > > > because it is just an XPath 1.0 string with no additional semantics, so
> > > > module authors can equally well write
> > > > 
> > > >     "../type = 'ietf-ospf:ospfv3'"
> > > > 
> > > > without importing "ietf-ospf".
> > > > 
> > > > Of course, we could also replace the paragraph with a statement that the
> > > > result of using bare identityref string values in XPath is undefined and
> > > > thus force everybody to use the XPath functions.
> > > > 
> > > 
> > > 
> > > I do not agree with this interpretation.
> > > The term "prefix" is used 10 times in that section.
> > > It is clear that the WG meant "prefix" not "module name".
> > > This cannot be changed by an errata.
> > 
> > So what do you suggest? The last paragraph in sec. 9.10.3 is clearly wrong.
> 
> I agree it is wrong, but only for identityref values that are defined
> in a module that has not been imported.  I stronlgy agree w/ Andy that
> this does NOT mean that we should change *working* and defined
> behaviour in an errata.

A more serious problem is that this text mixes up the prefix as defined in the
YANG module with the prefix that applies to instance values. A newcomer that
reads this text may wonder why an identity value is combined with a prefix of a
module in which the identity is NOT defined.

> 
> The intention (for better or worse) was that the value would use the
> prefix used in imports.  This means that if you want to do any kind of
> comparision of the string value to some known identities, then you
> must import that module so that there is a prefix defined.  This was

This is IMO not true. As I already wrote, for using a when expression like

   when "../type = 'ospf:ospfv3'"

it is not necessary to import the "ietf-ospf" module and thus have the "ospf"
prefix defined. If you think it is necessary, then point me to the relevant
text.

Lada


> the intention.
> 
> From this follows that (for all practical matters), the string value
> of an identity defined in a module that is not imported doesn't really
> matter.
> 
> > Note also that this paragraphs tries to define the string value of an
> > identityref node instance for any XPath expression, which needn't
> necessarily be
> > a simple EqualityExpr.
> 
> 
> 
> /martin
> 
> 
> 
> > 
> > Lada
> > 
> > > 
> > >  
> > > > Lada
> > > 
> > > 
> > > Andy
> > >  
> > > > >
> > > > >
> > > > > /martin
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> Lada
> > > > >>
> > > > >> >
> > > > >> >
> > > > >> > /martin
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > >
> > > > >> > > Lada
> > > > >> > >
> > > > >> > >
> > > > >> > > >
> > > > >> > > > and
> > > > >> > > >
> > > > >> > > >   module b {
> > > > >> > > >     ...
> > > > >> > > >     import ietf-ospf {
> > > > >> > > >       prefix y;
> > > > >> > > >     }
> > > > >> > > >     ...
> > > > >> > > >     leaf bar {
> > > > >> > > >       when "../type = 'y:ospfv3'";
> > > > >> > > >       ...
> > > > >> > > >     }
> > > > >> > > >   }
> > > > >> > > >
> > > > >> > > > You may not like it, but these two modules are both correct
> > > > according
> > > > >> > > > to the rules defined in RFC 7950.  The string value of the
> "type"
> > > > leaf
> > > > >> > > > *when evaluating the when expression* is different in the
> different
> > > > >> > > > modules.  See the last paragraph of section 9.10.3 in RFC 7950.
> > > > >> > > >
> > > > >> > > > > > > Also, potentially there can be a collision in prefixes
> and
> > > > then this
> > > > >> > > >
> > > > >> > > > also
> > > > >> > > > > > > breaks down.
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > No, two modules cannot be imported with the same prefix.
> > > > >> > > > >
> > > > >> > > > > I have to disagree. An identity derived from the
> > > > >> > > > > "ietf-routing:control-protocol-type" base identity can be
> defined
> > > > >> > > > > in a module that is not imported anywhere. If a server
> declares
> > > > such
> > > > >> > > > > a module as implemented, then "rt:type" may have this value
> per
> > > > >> > > > > sec. 9.10.2.
> > > > >> > > > >
> > > > >> > > > > And, consequently, there may be two different modules with
> > > > >> > > > > conflicting prefixes defining identities that are derived
> from
> > > > >> > > > > "ietf-routing:control-protocol-type".
> > > > >> > > >
> > > > >> > > > Sure, but this is not the point.
> > > > >> > > >
> > > > >> > > > > > > A moral of the namespace/prefix story in XML was that
> relying
> > > > of
> > > > >> > > > > > > namespace prefixes having a particular value is a really
> bad
> > > > >> > > > > > > idea. I know that the cited paragraph was intended to
> make
> > > > such
> > > > >> > > > > > > XPath string comparisons more deterministic, but it is
> also
> > > > >> > > > > > > problematic and should be avoided if possible.
> > > > >> > > > > >
> > > > >> > > > > > Note that this prefix is under the control of the module
> > > > designer
> > > > >> > > > > > writing the XPath expression.  The same identityref value
> might
> > > > use a
> > > > >> > > > >
> > > > >> > > > > No, it is not. The prefixes appear in instance data.
> > > > >> > > >
> > > > >> > > > The prefix *in the when expression* is under the control of the
> > > > module
> > > > >> > > > designer, as explained above.
> > > > >> > > >
> > > > >> > > > You are correct that the prefix in an XML encoding is not under
> > > > >> > > > control of the module designer, but noone has claimed that.
> > > > >> > > >
> > > > >> > > > I agree that it is unfortunate that context-specific prefixes
> are
> > > > used
> > > > >> > > > for the identityref values.  It would have been better if we
> used a
> > > > >> > > > context free representation, e.g. "<module-name>:<identity>". 
> But
> > > > >> > > > that's another discussion.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > /martin
> > > > >> > >
> > > > >> > > --
> > > > >> > > Ladislav Lhotka
> > > > >> > > Head, CZ.NIC Labs
> > > > >> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > >> > >
> > > > >> --
> > > > >> Ladislav Lhotka
> > > > >> Head, CZ.NIC Labs
> > > > >> PGP Key ID: 0xB8F92B08A9F76C67
> > > > >>
> > > > >> _______________________________________________
> > > > >> yang-doctors mailing list
> > > > >> yang-doctors@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/yang-doctors
> > > > >>
> > > > 
> > > > --
> > > > Ladislav Lhotka
> > > > Head, CZ.NIC Labs
> > > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > 
> > > > _______________________________________________
> > > > yang-doctors mailing list
> > > > yang-doctors@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > > 
> > > 
> > -- 
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> > 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan 15 01:53:15 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E6B127076 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 01:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 5mCYVwF89GQY for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 01:53:10 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 272A2126B6D for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 01:53:10 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 012843B; Mon, 15 Jan 2018 10:53:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id ko8ISP8rwn_V; Mon, 15 Jan 2018 10:53:06 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Mon, 15 Jan 2018 10:53:07 +0100 (CET)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id DC1CF2013F; Mon, 15 Jan 2018 10:53:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id mnRzH64wkRhc; Mon, 15 Jan 2018 10:53:07 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5E4FD2013E; Mon, 15 Jan 2018 10:53:07 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 1E293420FF8C; Mon, 15 Jan 2018 10:53:06 +0100 (CET)
Date: Mon, 15 Jan 2018 10:53:06 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org
Message-ID: <20180115095306.3m657hzwjemogqah@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Ladislav Lhotka <lhotka@nic.cz>, Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com> <1516009099.5426.13.camel@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1516009099.5426.13.camel@nic.cz>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/btFuAiVUyrcTur9aIoglW6oKzho>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 09:53:14 -0000

On Mon, Jan 15, 2018 at 10:38:19AM +0100, Ladislav Lhotka wrote:
> > 
> > The intention (for better or worse) was that the value would use the
> > prefix used in imports.  This means that if you want to do any kind of
> > comparision of the string value to some known identities, then you
> > must import that module so that there is a prefix defined.  This was
> 
> This is IMO not true. As I already wrote, for using a when expression like
> 
>    when "../type = 'ospf:ospfv3'"
> 
> it is not necessary to import the "ietf-ospf" module and thus have the "ospf"
> prefix defined. If you think it is necessary, then point me to the relevant
> text.

Prefixes assigned to modules using the prefix statement are not
guaranteed to be globally unique. It is possible to have multiple
modules defining the prefix 'ospf', e.g.:

 module ietf-ospf {
   prefix ospf;
 }

 module acme-ospf {
   prefix ospf;
 }

Note that this is not a problem since YANG allows to redefine the
prefix in an import statement in case a prefix clash occurs. Hence,
the 'ospf' prefix in the when statement has to refer to the prefix
that is used in the module where the when statement is defined. And
because of that it is necessary to import a module that defines the
prefix 'ospf'. Any other interpretation would be ambiguous I think.

/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/>


From nobody Mon Jan 15 02:10:21 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1525512DA06 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 02:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 zVk_HnKbvCwY for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 02:10:18 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 994BB12DA0A for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 02:10:16 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:68c6:92ff:fe01:2298]) by mail.nic.cz (Postfix) with ESMTPSA id 3FA9963F6A; Mon, 15 Jan 2018 11:10:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1516011013; bh=4ncPXzOr+o+QUBJVoYuuzDuh/9jIexZDVQ/rIy02A64=; h=From:To:Date; b=wbi9GxP+WHYOpUWn9gHWRbWAoum4lDHCoSNjQK5hkzAbywTuKDEg2ebOKP4XanaAP JG//6Ip2o82sOQcLE7P1BKKe+g1AGtnr2V7fl4CwiPHIJ0Fm/wYiOflRg+/rf1PMAM xc5abe3cXvuPHmQoOvj3oeebehBCZWZ6jWuPvhR4=
Message-ID: <1516011013.5426.25.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org
Date: Mon, 15 Jan 2018 11:10:13 +0100
In-Reply-To: <20180115095306.3m657hzwjemogqah@elstar.local>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com> <1516009099.5426.13.camel@nic.cz> <20180115095306.3m657hzwjemogqah@elstar.local>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/YlVLow_fHLTlRaYGkBWYH-PXiUU>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 10:10:20 -0000

On Mon, 2018-01-15 at 10:53 +0100, Juergen Schoenwaelder wrote:
> On Mon, Jan 15, 2018 at 10:38:19AM +0100, Ladislav Lhotka wrote:
> > > 
> > > The intention (for better or worse) was that the value would use the
> > > prefix used in imports.  This means that if you want to do any kind of
> > > comparision of the string value to some known identities, then you
> > > must import that module so that there is a prefix defined.  This was
> > 
> > This is IMO not true. As I already wrote, for using a when expression like
> > 
> >    when "../type = 'ospf:ospfv3'"
> > 
> > it is not necessary to import the "ietf-ospf" module and thus have the
> > "ospf"
> > prefix defined. If you think it is necessary, then point me to the relevant
> > text.
> 
> Prefixes assigned to modules using the prefix statement are not
> guaranteed to be globally unique. It is possible to have multiple
> modules defining the prefix 'ospf', e.g.:
> 
>  module ietf-ospf {
>    prefix ospf;
>  }
> 
>  module acme-ospf {
>    prefix ospf;
>  }
> 
> Note that this is not a problem since YANG allows to redefine the
> prefix in an import statement in case a prefix clash occurs. Hence,
> the 'ospf' prefix in the when statement has to refer to the prefix
> that is used in the module where the when statement is defined. And

In my example, the prefix is used inside an XPath string, and XPath 1.0 doesn't
allow for adding any structure or semantics to the string type. So even if RFC
7950 stated that such an import was necessary (which it doesn't), it would be an
improper use of XPath.

YANG can define the string value of a node instance in the conceptual data tree
but a literal XPath string is just that.

Lada


> because of that it is necessary to import a module that defines the
> prefix 'ospf'. Any other interpretation would be ambiguous I think.
> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan 15 02:20:20 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB2B812DA13 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 02:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 Xoo469lMGBqy for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 02:20:17 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D197012DA27 for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 02:20:12 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 99A5F3B; Mon, 15 Jan 2018 11:20:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id rkHFlY6u3kix; Mon, 15 Jan 2018 11:20:09 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Mon, 15 Jan 2018 11:20:11 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 767672013F; Mon, 15 Jan 2018 11:20:11 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id 4XdXaHMU1VDi; Mon, 15 Jan 2018 11:20:11 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id ECB642013E; Mon, 15 Jan 2018 11:20:10 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id E1B5B42100E0; Mon, 15 Jan 2018 11:20:09 +0100 (CET)
Date: Mon, 15 Jan 2018 11:20:09 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org
Message-ID: <20180115102009.aai3jetqsx3tgevw@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Ladislav Lhotka <lhotka@nic.cz>, Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com> <1516009099.5426.13.camel@nic.cz> <20180115095306.3m657hzwjemogqah@elstar.local> <1516011013.5426.25.camel@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1516011013.5426.25.camel@nic.cz>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/aJxAddOv7-EB7KjiPJJFTFsfW3E>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 10:20:19 -0000

On Mon, Jan 15, 2018 at 11:10:13AM +0100, Ladislav Lhotka wrote:
> On Mon, 2018-01-15 at 10:53 +0100, Juergen Schoenwaelder wrote:
> > On Mon, Jan 15, 2018 at 10:38:19AM +0100, Ladislav Lhotka wrote:
> > > > 
> > > > The intention (for better or worse) was that the value would use the
> > > > prefix used in imports.  This means that if you want to do any kind of
> > > > comparision of the string value to some known identities, then you
> > > > must import that module so that there is a prefix defined.  This was
> > > 
> > > This is IMO not true. As I already wrote, for using a when expression like
> > > 
> > >    when "../type = 'ospf:ospfv3'"
> > > 
> > > it is not necessary to import the "ietf-ospf" module and thus have the
> > > "ospf"
> > > prefix defined. If you think it is necessary, then point me to the relevant
> > > text.
> > 
> > Prefixes assigned to modules using the prefix statement are not
> > guaranteed to be globally unique. It is possible to have multiple
> > modules defining the prefix 'ospf', e.g.:
> > 
> >  module ietf-ospf {
> >    prefix ospf;
> >  }
> > 
> >  module acme-ospf {
> >    prefix ospf;
> >  }
> > 
> > Note that this is not a problem since YANG allows to redefine the
> > prefix in an import statement in case a prefix clash occurs. Hence,
> > the 'ospf' prefix in the when statement has to refer to the prefix
> > that is used in the module where the when statement is defined. And
> 
> In my example, the prefix is used inside an XPath string, and XPath 1.0 doesn't
> allow for adding any structure or semantics to the string type. So even if RFC
> 7950 stated that such an import was necessary (which it doesn't), it would be an
> improper use of XPath.
> 
> YANG can define the string value of a node instance in the conceptual data tree
> but a literal XPath string is just that.
> 
> Lada
> 
> 
> > because of that it is necessary to import a module that defines the
> > prefix 'ospf'. Any other interpretation would be ambiguous I think.

Fine, so this construction should be avoided since it is ambiguous.

/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/>


From nobody Mon Jan 15 02:28:52 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D3512DA21 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 02:28:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level: 
X-Spam-Status: No, score=-7.01 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 6Ox9qFyIeHw8 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 02:28:50 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 ED13712DA1C for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 02:28:49 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:68c6:92ff:fe01:2298]) by mail.nic.cz (Postfix) with ESMTPSA id 9504063F7C; Mon, 15 Jan 2018 11:28:48 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1516012128; bh=Dy3qa0Ix71XV+IFHa1KvsuWGZ5UarJvL2BB+Xt4Aw9g=; h=From:To:Date; b=EZ2QrE+EWCL4om/P5RW4QTn9DoLGUoCnWJcq7WqYhlDwYdBk1C3tv712WpqtbeR09 99dReTqlSznsixgtFc6GEt07rOf+X8qHDDqV5BdYHg/CPDS036fFr49tP7OHEDeXEy twyFgZpE1LeUfn16uEitkc4qb405skJD0YL0T0pg=
Message-ID: <1516012128.5426.28.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org
Date: Mon, 15 Jan 2018 11:28:48 +0100
In-Reply-To: <20180115102009.aai3jetqsx3tgevw@elstar.local>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com> <1516009099.5426.13.camel@nic.cz> <20180115095306.3m657hzwjemogqah@elstar.local> <1516011013.5426.25.camel@nic.cz> <20180115102009.aai3jetqsx3tgevw@elstar.local>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/U3_jpA16Tg__9ohdLc1R89aT5UI>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 10:28:51 -0000

On Mon, 2018-01-15 at 11:20 +0100, Juergen Schoenwaelder wrote:
> On Mon, Jan 15, 2018 at 11:10:13AM +0100, Ladislav Lhotka wrote:
> > On Mon, 2018-01-15 at 10:53 +0100, Juergen Schoenwaelder wrote:
> > > On Mon, Jan 15, 2018 at 10:38:19AM +0100, Ladislav Lhotka wrote:
> > > > > 
> > > > > The intention (for better or worse) was that the value would use the
> > > > > prefix used in imports.  This means that if you want to do any kind of
> > > > > comparision of the string value to some known identities, then you
> > > > > must import that module so that there is a prefix defined.  This was
> > > > 
> > > > This is IMO not true. As I already wrote, for using a when expression
> > > > like
> > > > 
> > > >    when "../type = 'ospf:ospfv3'"
> > > > 
> > > > it is not necessary to import the "ietf-ospf" module and thus have the
> > > > "ospf"
> > > > prefix defined. If you think it is necessary, then point me to the
> > > > relevant
> > > > text.
> > > 
> > > Prefixes assigned to modules using the prefix statement are not
> > > guaranteed to be globally unique. It is possible to have multiple
> > > modules defining the prefix 'ospf', e.g.:
> > > 
> > >  module ietf-ospf {
> > >    prefix ospf;
> > >  }
> > > 
> > >  module acme-ospf {
> > >    prefix ospf;
> > >  }
> > > 
> > > Note that this is not a problem since YANG allows to redefine the
> > > prefix in an import statement in case a prefix clash occurs. Hence,
> > > the 'ospf' prefix in the when statement has to refer to the prefix
> > > that is used in the module where the when statement is defined. And
> > 
> > In my example, the prefix is used inside an XPath string, and XPath 1.0
> > doesn't
> > allow for adding any structure or semantics to the string type. So even if
> > RFC
> > 7950 stated that such an import was necessary (which it doesn't), it would
> > be an
> > improper use of XPath.
> > 
> > YANG can define the string value of a node instance in the conceptual data
> > tree
> > but a literal XPath string is just that.
> > 
> > Lada
> > 
> > 
> > > because of that it is necessary to import a module that defines the
> > > prefix 'ospf'. Any other interpretation would be ambiguous I think.
> 
> Fine, so this construction should be avoided since it is ambiguous.

Yes, so I think the erratum should say just this. New modules should by all
means use the XPath functions.

Lada

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan 15 08:24:44 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD25127775 for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 08:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 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, URIBL_BLOCKED=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 xBW5nrzmVUyN for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 08:24:40 -0800 (PST)
Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::234]) (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 CD4D8126DFB for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 08:24:39 -0800 (PST)
Received: by mail-lf0-x234.google.com with SMTP id h137so14019198lfe.8 for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 08:24:39 -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=wwe40pVEqGgYwtmCXzdxygPGKYvmqLG2+tA6EXcVzoI=; b=W4abyxw4NL3IwHlMziXIop1gC7B6AyYz22m15O5IucYLVv/LnGDUIhZ+xfU8vcqzPN iqc08bBY4FuLx4NGitaSM0KpVitdGKlVIAXBVKtdyO5HOGdDam2QdEjqnpyukt5P3hnw S9XtVVOxYehUBlVc7ygqrM+XhBcRbAyQq3TIRcz8UDLbRFjktTjAjzd75Wd2seVQdEmp 0E3rWRUM+K+idC+Crz9R0toijzL96gOuqaPQp4dpJ22NSRnPez2rZFtg7QXvmhXAmwEX q1SUhilf0POkdgu+Igi4YupmtXiuWRYsD2QrlHEgjxSeSnlgvr5gfMgULWjNfN3v0paa rQKQ==
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=wwe40pVEqGgYwtmCXzdxygPGKYvmqLG2+tA6EXcVzoI=; b=ACFFJKfkoJLrGRAsN+Re57jjbYhkcGE8i+wj+y6NHqQAN1Pc5+eJEnydPqqU8Pb6d4 ySMYFvlMvGDksoOmI/AOdciXCrM+pe3T4tDLTea+d6POM0TpRr9Tblp8NqvNoounUd26 LvajJUHbd560lGuhRDGG/KNvHjXBiWcDJ3MYWiyiKaatko+3SdoXDX8yEEULEayNrcsl HlnFikEgtCDai/HI3ovbpJMmSyMbQ1xMKiGz5zYiEKQ28D+yvf9DB/EnqKNQNWS2T6Sh jgNJxWLBg5xlXgvycmT3pR99eBZB2lRNZAsMRwz5scypZPE+5t6eJKbtWgWScREM/iym e3dA==
X-Gm-Message-State: AKGB3mIYeS4ij8bmAo2AKBrYS4uVUyjiOrLimkvOkxVa0xXfZOV0xVAh ALD299EzxIvIWLnHdt8dyxWKpqwrXYO8b9UMcB5hPg==
X-Google-Smtp-Source: ACJfBotqPRUQklbaNGEwWMmU1X/B3jyBLBHLUWyBQUAQbZwXBGtiEIMBdBcUCA6opOFrmT3FdYLN1tWLUBWDv8YiMAI=
X-Received: by 10.46.23.24 with SMTP id l24mr19582711lje.146.1516033478018; Mon, 15 Jan 2018 08:24:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.196.65 with HTTP; Mon, 15 Jan 2018 08:24:36 -0800 (PST)
In-Reply-To: <20180115.095941.341257692373089671.mbj@tail-f.com>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 15 Jan 2018 08:24:36 -0800
Message-ID: <CABCOCHQBwsi7WiUZw5V0QQ-t2n9Yy=nY_dWzyaixsrXwmo4k=w@mail.gmail.com>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: Ladislav Lhotka <lhotka@nic.cz>, YANG Doctors <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1c016aed24c80562d30c65"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/60FkViVo4GL72koeaFSQ5CykjSM>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 16:24:43 -0000

--94eb2c1c016aed24c80562d30c65
Content-Type: text/plain; charset="UTF-8"

>
> ....




> > So what do you suggest? The last paragraph in sec. 9.10.3 is clearly
> wrong.
>
> I agree it is wrong, but only for identityref values that are defined
> in a module that has not been imported.  I stronlgy agree w/ Andy that
> this does NOT mean that we should change *working* and defined
> behaviour in an errata.
>


I think there is other text in the RFC that says a prefix is resolved in
the local module.
This is the only design that makes any sense, and the only design that
could ever work.
The module author has no control over prefix usage and imports in other
modules.



> The intention (for better or worse) was that the value would use the
> prefix used in imports.  This means that if you want to do any kind of
> comparision of the string value to some known identities, then you
> must import that module so that there is a prefix defined.  This was
> the intention.
>
> From this follows that (for all practical matters), the string value
> of an identity defined in a module that is not imported doesn't really
> matter.
>
> > Note also that this paragraphs tries to define the string value of an
> > identityref node instance for any XPath expression, which needn't
> necessarily be
> > a simple EqualityExpr.
>
>

The derived-from and derived-from-or-self functions are flawed
because they use prefixes instead of module names and a missing
prefix means the current module instead of the local module.
I don't see how using derived-from-or-self(type, "foo") is any better
than type="foo".  The latter is being used a lot and the XPath functions
are not being used (by our customers).

Seems new XPath functions are needed, like
   derived-from2(type, "iana-if-type", "ethernetCsmacd")




>
>
> /martin
>
>
Andy


>
>
> >
> > Lada
> >
> > >
> > >
> > > > Lada
> > >
> > >
> > > Andy
> > >
> > > > >
> > > > >
> > > > > /martin
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >>
> > > > >> Lada
> > > > >>
> > > > >> >
> > > > >> >
> > > > >> > /martin
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> > >
> > > > >> > > Lada
> > > > >> > >
> > > > >> > >
> > > > >> > > >
> > > > >> > > > and
> > > > >> > > >
> > > > >> > > >   module b {
> > > > >> > > >     ...
> > > > >> > > >     import ietf-ospf {
> > > > >> > > >       prefix y;
> > > > >> > > >     }
> > > > >> > > >     ...
> > > > >> > > >     leaf bar {
> > > > >> > > >       when "../type = 'y:ospfv3'";
> > > > >> > > >       ...
> > > > >> > > >     }
> > > > >> > > >   }
> > > > >> > > >
> > > > >> > > > You may not like it, but these two modules are both correct
> > > > according
> > > > >> > > > to the rules defined in RFC 7950.  The string value of the
> "type"
> > > > leaf
> > > > >> > > > *when evaluating the when expression* is different in the
> different
> > > > >> > > > modules.  See the last paragraph of section 9.10.3 in RFC
> 7950.
> > > > >> > > >
> > > > >> > > > > > > Also, potentially there can be a collision in
> prefixes and
> > > > then this
> > > > >> > > >
> > > > >> > > > also
> > > > >> > > > > > > breaks down.
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > > > No, two modules cannot be imported with the same prefix.
> > > > >> > > > >
> > > > >> > > > > I have to disagree. An identity derived from the
> > > > >> > > > > "ietf-routing:control-protocol-type" base identity can
> be defined
> > > > >> > > > > in a module that is not imported anywhere. If a server
> declares
> > > > such
> > > > >> > > > > a module as implemented, then "rt:type" may have this
> value per
> > > > >> > > > > sec. 9.10.2.
> > > > >> > > > >
> > > > >> > > > > And, consequently, there may be two different modules with
> > > > >> > > > > conflicting prefixes defining identities that are derived
> from
> > > > >> > > > > "ietf-routing:control-protocol-type".
> > > > >> > > >
> > > > >> > > > Sure, but this is not the point.
> > > > >> > > >
> > > > >> > > > > > > A moral of the namespace/prefix story in XML was that
> relying
> > > > of
> > > > >> > > > > > > namespace prefixes having a particular value is a
> really bad
> > > > >> > > > > > > idea. I know that the cited paragraph was intended to
> make
> > > > such
> > > > >> > > > > > > XPath string comparisons more deterministic, but it
> is also
> > > > >> > > > > > > problematic and should be avoided if possible.
> > > > >> > > > > >
> > > > >> > > > > > Note that this prefix is under the control of the module
> > > > designer
> > > > >> > > > > > writing the XPath expression.  The same identityref
> value might
> > > > use a
> > > > >> > > > >
> > > > >> > > > > No, it is not. The prefixes appear in instance data.
> > > > >> > > >
> > > > >> > > > The prefix *in the when expression* is under the control of
> the
> > > > module
> > > > >> > > > designer, as explained above.
> > > > >> > > >
> > > > >> > > > You are correct that the prefix in an XML encoding is not
> under
> > > > >> > > > control of the module designer, but noone has claimed that.
> > > > >> > > >
> > > > >> > > > I agree that it is unfortunate that context-specific
> prefixes are
> > > > used
> > > > >> > > > for the identityref values.  It would have been better if
> we used a
> > > > >> > > > context free representation, e.g.
> "<module-name>:<identity>".  But
> > > > >> > > > that's another discussion.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > > > /martin
> > > > >> > >
> > > > >> > > --
> > > > >> > > Ladislav Lhotka
> > > > >> > > Head, CZ.NIC Labs
> > > > >> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > >> > >
> > > > >> --
> > > > >> Ladislav Lhotka
> > > > >> Head, CZ.NIC Labs
> > > > >> PGP Key ID: 0xB8F92B08A9F76C67
> > > > >>
> > > > >> _______________________________________________
> > > > >> yang-doctors mailing list
> > > > >> yang-doctors@ietf.org
> > > > >> https://www.ietf.org/mailman/listinfo/yang-doctors
> > > > >>
> > > >
> > > > --
> > > > Ladislav Lhotka
> > > > Head, CZ.NIC Labs
> > > > PGP Key ID: 0xB8F92B08A9F76C67
> > > >
> > > > _______________________________________________
> > > > yang-doctors mailing list
> > > > yang-doctors@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > >
> > >
> > --
> > Ladislav Lhotka
> > Head, CZ.NIC Labs
> > PGP Key ID: 0xB8F92B08A9F76C67
> >
>

--94eb2c1c016aed24c80562d30c65
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">....</blockquote><div><br></div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">&gt; So what do you suggest? The last parag=
raph in sec. 9.10.3 is clearly wrong.<br>
<br>
I agree it is wrong, but only for identityref values that are defined<br>
in a module that has not been imported.=C2=A0 I stronlgy agree w/ Andy that=
<br>
this does NOT mean that we should change *working* and defined<br>
behaviour in an errata.<br></blockquote><div><br></div><div><br></div><div>=
I think there is other text in the RFC that says a prefix is resolved in th=
e local module.</div><div>This is the only design that makes any sense, and=
 the only design that could ever work.</div><div>The module author has no c=
ontrol over prefix usage and imports in other modules.</div><div><br></div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<br>
The intention (for better or worse) was that the value would use the<br>
prefix used in imports.=C2=A0 This means that if you want to do any kind of=
<br>
comparision of the string value to some known identities, then you<br>
must import that module so that there is a prefix defined.=C2=A0 This was<b=
r>
the intention.<br>
<br>
>From this follows that (for all practical matters), the string value<br>
of an identity defined in a module that is not imported doesn&#39;t really<=
br>
matter.<br>
<br>
&gt; Note also that this paragraphs tries to define the string value of an<=
br>
&gt; identityref node instance for any XPath expression, which needn&#39;t =
necessarily be<br>
&gt; a simple EqualityExpr.<br>
<br></blockquote><div><br></div><div><br></div><div>The derived-from and de=
rived-from-or-self functions are flawed</div><div>because they use prefixes=
 instead of module names and a missing</div><div>prefix means the current m=
odule instead of the local module.</div><div>I don&#39;t see how using deri=
ved-from-or-self(type, &quot;foo&quot;) is any better</div><div>than type=
=3D&quot;foo&quot;.=C2=A0 The latter is being used a lot and the XPath func=
tions</div><div>are not being used (by our customers).</div><div><br></div>=
<div>Seems new XPath functions are needed, like</div><div>=C2=A0 =C2=A0deri=
ved-from2(type, &quot;iana-if-type&quot;, &quot;ethernetCsmacd&quot;)</div>=
<div><br></div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<br>
<br>
/martin<br>
<br></blockquote><div><br></div><div>Andy</div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
<br>
<br>
&gt;<br>
&gt; Lada<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &gt; Lada<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Andy<br>
&gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; /martin<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; Lada<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; /martin<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; Lada<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; and<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0module b {<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0import ietf-ospf =
{<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0prefix y;<=
br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0leaf bar {<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0when &quot=
;../type =3D &#39;y:ospfv3&#39;&quot;;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0...<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; You may not like it, but these two m=
odules are both correct<br>
&gt; &gt; &gt; according<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; to the rules defined in RFC 7950.=C2=
=A0 The string value of the &quot;type&quot;<br>
&gt; &gt; &gt; leaf<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; *when evaluating the when expression=
* is different in the different<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; modules.=C2=A0 See the last paragrap=
h of section 9.10.3 in RFC 7950.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; Also, potentially the=
re can be a collision in prefixes and<br>
&gt; &gt; &gt; then this<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; also<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; breaks down.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; No, two modules cannot be =
imported with the same prefix.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; I have to disagree. An identity=
 derived from the<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &quot;ietf-routing:control-<wbr=
>protocol-type&quot; base identity can be defined<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; in a module that is not importe=
d anywhere. If a server declares<br>
&gt; &gt; &gt; such<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; a module as implemented, then &=
quot;rt:type&quot; may have this value per<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; sec. 9.10.2.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; And, consequently, there may be=
 two different modules with<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; conflicting prefixes defining i=
dentities that are derived from<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &quot;ietf-routing:control-<wbr=
>protocol-type&quot;.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; Sure, but this is not the point.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; A moral of the namesp=
ace/prefix story in XML was that relying<br>
&gt; &gt; &gt; of<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; namespace prefixes ha=
ving a particular value is a really bad<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; idea. I know that the=
 cited paragraph was intended to make<br>
&gt; &gt; &gt; such<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; XPath string comparis=
ons more deterministic, but it is also<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; problematic and shoul=
d be avoided if possible.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; Note that this prefix is u=
nder the control of the module<br>
&gt; &gt; &gt; designer<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; writing the XPath expressi=
on.=C2=A0 The same identityref value might<br>
&gt; &gt; &gt; use a<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; No, it is not. The prefixes app=
ear in instance data.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; The prefix *in the when expression* =
is under the control of the<br>
&gt; &gt; &gt; module<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; designer, as explained above.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; You are correct that the prefix in a=
n XML encoding is not under<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; control of the module designer, but =
noone has claimed that.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; I agree that it is unfortunate that =
context-specific prefixes are<br>
&gt; &gt; &gt; used<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; for the identityref values.=C2=A0 It=
 would have been better if we used a<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; context free representation, e.g. &q=
uot;&lt;module-name&gt;:&lt;identity&gt;&quot;.=C2=A0 But<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; that&#39;s another discussion.<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; /martin<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; --<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; Ladislav Lhotka<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;&gt; --<br>
&gt; &gt; &gt; &gt;&gt; Ladislav Lhotka<br>
&gt; &gt; &gt; &gt;&gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; &gt;&gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt;&gt; ______________________________<wbr>________________=
_<br>
&gt; &gt; &gt; &gt;&gt; yang-doctors mailing list<br>
&gt; &gt; &gt; &gt;&gt; <a href=3D"mailto:yang-doctors@ietf.org">yang-docto=
rs@ietf.org</a><br>
&gt; &gt; &gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ya=
ng-doctors" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailm=
an/<wbr>listinfo/yang-doctors</a><br>
&gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; --<br>
&gt; &gt; &gt; Ladislav Lhotka<br>
&gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; ______________________________<wbr>_________________<br>
&gt; &gt; &gt; yang-doctors mailing list<br>
&gt; &gt; &gt; <a href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.o=
rg</a><br>
&gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctor=
s" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>l=
istinfo/yang-doctors</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
<span class=3D"HOEnZb"><font color=3D"#888888">&gt; --<br>
&gt; Ladislav Lhotka<br>
&gt; Head, CZ.NIC Labs<br>
&gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt;<br>
</font></span></blockquote></div><br></div></div>

--94eb2c1c016aed24c80562d30c65--


From nobody Mon Jan 15 09:17:17 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1E112EADE for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 09:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 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, T_RP_MATCHES_RCVD=-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=nic.cz
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 2JgoZtQU2CcY for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 09:17:13 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (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 CB40212EAC2 for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 09:14:29 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:68c6:92ff:fe01:2298]) by mail.nic.cz (Postfix) with ESMTPSA id E9C5E6425D; Mon, 15 Jan 2018 18:14:27 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1516036468; bh=xevlaUrG1WAwLHDhNEHq/9Yr1fkKKb+uBf39n8KBTts=; h=From:To:Date; b=TS1lI2OXHTgzzZy9bAZmyNWewQ3E36wr2bfPCJc4EwtL5amBSyuSI/OUYSVpRdf/+ 8Xq4EoAFh0g0yb2iXs0AXhkDIQVJaemK8iwiffh0YhTcV4uTESPo14r48kYInCAyTK dhM2ujXS5e1kIPiVCdOL3sN9/WKAHj/QwoUH0XhY=
Message-ID: <1516036467.5426.90.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Andy Bierman <andy@yumaworks.com>, Martin Bjorklund <mbj@tail-f.com>
Cc: YANG Doctors <yang-doctors@ietf.org>
Date: Mon, 15 Jan 2018 18:14:27 +0100
In-Reply-To: <CABCOCHQBwsi7WiUZw5V0QQ-t2n9Yy=nY_dWzyaixsrXwmo4k=w@mail.gmail.com>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com> <CABCOCHQBwsi7WiUZw5V0QQ-t2n9Yy=nY_dWzyaixsrXwmo4k=w@mail.gmail.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.4 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/p-fO85gYArqZLt_Y-ARR_lW21cc>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 17:17:16 -0000

On Mon, 2018-01-15 at 08:24 -0800, Andy Bierman wrote:
> > ....
> 
>  
> > > So what do you suggest? The last paragraph in sec. 9.10.3 is clearly
> > wrong.
> > 
> > I agree it is wrong, but only for identityref values that are defined
> > in a module that has not been imported.  I stronlgy agree w/ Andy that
> > this does NOT mean that we should change *working* and defined
> > behaviour in an errata.
> 
> 
> I think there is other text in the RFC that says a prefix is resolved in the
> local module.
> This is the only design that makes any sense, and the only design that could
> ever work.
> The module author has no control over prefix usage and imports in other
> modules.
> 
> 
> > The intention (for better or worse) was that the value would use the
> > prefix used in imports.  This means that if you want to do any kind of
> > comparision of the string value to some known identities, then you
> > must import that module so that there is a prefix defined.  This was
> > the intention.
> > 
> > From this follows that (for all practical matters), the string value
> > of an identity defined in a module that is not imported doesn't really
> > matter.
> > 
> > > Note also that this paragraphs tries to define the string value of an
> > > identityref node instance for any XPath expression, which needn't
> > necessarily be
> > > a simple EqualityExpr.
> > 
> 
> 
> The derived-from and derived-from-or-self functions are flawed
> because they use prefixes instead of module names and a missing
> prefix means the current module instead of the local module.
> I don't see how using derived-from-or-self(type, "foo") is any better
> than type="foo".  The latter is being used a lot and the XPath functions
> are not being used (by our customers).

Although I tend to agree that using module name as a parameter would be better
(it was I believe the original proposal), it is IMO not as flawed as the string
equality test because the semantics of the latter is defined by the XPath 1.0
spec. In contrast, the derived-from(-or-self) functions are defined in YANG, so
it is possible to specify additional semantics for its parameters.

I don't see any compelling reason why your customers couldn't use the functions.
The problem of sec. 9.10.3 is that it gives an excuse for using the plain string
test.

Lada

> 
> Seems new XPath functions are needed, like
>    derived-from2(type, "iana-if-type", "ethernetCsmacd")
> 
> 
>  
> > 
> > /martin
> > 
> 
> Andy
>  
> > 
> > >
> > > Lada
> > >
> > > >
> > > >
> > > > > Lada
> > > >
> > > >
> > > > Andy
> > > >
> > > > > >
> > > > > >
> > > > > > /martin
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >>
> > > > > >> Lada
> > > > > >>
> > > > > >> >
> > > > > >> >
> > > > > >> > /martin
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > >
> > > > > >> > > Lada
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > >
> > > > > >> > > > and
> > > > > >> > > >
> > > > > >> > > >   module b {
> > > > > >> > > >     ...
> > > > > >> > > >     import ietf-ospf {
> > > > > >> > > >       prefix y;
> > > > > >> > > >     }
> > > > > >> > > >     ...
> > > > > >> > > >     leaf bar {
> > > > > >> > > >       when "../type = 'y:ospfv3'";
> > > > > >> > > >       ...
> > > > > >> > > >     }
> > > > > >> > > >   }
> > > > > >> > > >
> > > > > >> > > > You may not like it, but these two modules are both correct
> > > > > according
> > > > > >> > > > to the rules defined in RFC 7950.  The string value of the
> > "type"
> > > > > leaf
> > > > > >> > > > *when evaluating the when expression* is different in the
> > different
> > > > > >> > > > modules.  See the last paragraph of section 9.10.3 in RFC
> > 7950.
> > > > > >> > > >
> > > > > >> > > > > > > Also, potentially there can be a collision in prefixes
> > and
> > > > > then this
> > > > > >> > > >
> > > > > >> > > > also
> > > > > >> > > > > > > breaks down.
> > > > > >> > > > > >
> > > > > >> > > > > >
> > > > > >> > > > > > No, two modules cannot be imported with the same prefix.
> > > > > >> > > > >
> > > > > >> > > > > I have to disagree. An identity derived from the
> > > > > >> > > > > "ietf-routing:control-protocol-type" base identity can be
> > defined
> > > > > >> > > > > in a module that is not imported anywhere. If a server
> > declares
> > > > > such
> > > > > >> > > > > a module as implemented, then "rt:type" may have this value
> > per
> > > > > >> > > > > sec. 9.10.2.
> > > > > >> > > > >
> > > > > >> > > > > And, consequently, there may be two different modules with
> > > > > >> > > > > conflicting prefixes defining identities that are derived
> > from
> > > > > >> > > > > "ietf-routing:control-protocol-type".
> > > > > >> > > >
> > > > > >> > > > Sure, but this is not the point.
> > > > > >> > > >
> > > > > >> > > > > > > A moral of the namespace/prefix story in XML was that
> > relying
> > > > > of
> > > > > >> > > > > > > namespace prefixes having a particular value is a
> > really bad
> > > > > >> > > > > > > idea. I know that the cited paragraph was intended to
> > make
> > > > > such
> > > > > >> > > > > > > XPath string comparisons more deterministic, but it is
> > also
> > > > > >> > > > > > > problematic and should be avoided if possible.
> > > > > >> > > > > >
> > > > > >> > > > > > Note that this prefix is under the control of the module
> > > > > designer
> > > > > >> > > > > > writing the XPath expression.  The same identityref value
> > might
> > > > > use a
> > > > > >> > > > >
> > > > > >> > > > > No, it is not. The prefixes appear in instance data.
> > > > > >> > > >
> > > > > >> > > > The prefix *in the when expression* is under the control of
> > the
> > > > > module
> > > > > >> > > > designer, as explained above.
> > > > > >> > > >
> > > > > >> > > > You are correct that the prefix in an XML encoding is not
> > under
> > > > > >> > > > control of the module designer, but noone has claimed that.
> > > > > >> > > >
> > > > > >> > > > I agree that it is unfortunate that context-specific prefixes
> > are
> > > > > used
> > > > > >> > > > for the identityref values.  It would have been better if we
> > used a
> > > > > >> > > > context free representation, e.g. "<module-
> > name>:<identity>".  But
> > > > > >> > > > that's another discussion.
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > > > /martin
> > > > > >> > >
> > > > > >> > > --
> > > > > >> > > Ladislav Lhotka
> > > > > >> > > Head, CZ.NIC Labs
> > > > > >> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > > >> > >
> > > > > >> --
> > > > > >> Ladislav Lhotka
> > > > > >> Head, CZ.NIC Labs
> > > > > >> PGP Key ID: 0xB8F92B08A9F76C67
> > > > > >>
> > > > > >> _______________________________________________
> > > > > >> yang-doctors mailing list
> > > > > >> yang-doctors@ietf.org
> > > > > >> https://www.ietf.org/mailman/listinfo/yang-doctors
> > > > > >>
> > > > >
> > > > > --
> > > > > Ladislav Lhotka
> > > > > Head, CZ.NIC Labs
> > > > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > >
> > > > > _______________________________________________
> > > > > yang-doctors mailing list
> > > > > yang-doctors@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > > >
> > > >
> > > --
> > > Ladislav Lhotka
> > > Head, CZ.NIC Labs
> > > PGP Key ID: 0xB8F92B08A9F76C67
> > >
> 
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan 15 09:31:59 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A5012E89F for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 09:31:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 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, URIBL_BLOCKED=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 G8GEYPPeGaBz for <yang-doctors@ietfa.amsl.com>; Mon, 15 Jan 2018 09:31:53 -0800 (PST)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 7AB2A12EA9E for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 09:31:42 -0800 (PST)
Received: by mail-lf0-x229.google.com with SMTP id o89so10141509lfg.10 for <yang-doctors@ietf.org>; Mon, 15 Jan 2018 09:31:42 -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=Sd6RjXlkUa4Oou9ZBnsQUi9gScNeRdugYj0tqsOkheU=; b=flEcx6wufplP7ufvcmFoLMtu8wIZc+xHaUCq4aGbrXhSF+NBgwYgjh68efHhw294Fw kpriZi2h09QMUsqLdVaWUx4vt6frCf1E4TDdQ1y5ZdeaGdITG3oqW1705ouHydnT2hr/ 4KtPL8+F4gQ05i+t8g3OFjHsJPUAadB5dlHhI/qIezM8PSlubNctXlSRklOZ5QN2AwV6 vZtGv82+NMiv30qwOzmMYH0VYVyZqT2+If5etFk2Qw8FR0RMx9C1wz5adCc35iCG2H8+ iSHGy1clx3uP4Am30SxW3+50O9aLT0MDaugKeTW4mnBopfr5JuQVblpjskzVZFP2l585 d82g==
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=Sd6RjXlkUa4Oou9ZBnsQUi9gScNeRdugYj0tqsOkheU=; b=hiT4Q4zwkUbeOwufPDMidrUKpUfPZKkIzx2xs5vW3LutugGanx8Kpo0gAA4Z0nz34A fpJqwToVl+jYMJmPZIQr2mtB8aQk5tMKLBqmbHBh9JBlGkGuo/zXaChWryRJA1RXAOjK 0hDQSS3T685/1yjx4jtxcIvTm3jVXwtv0INAFvMyNygCgWJykYNbqL9rvkC0VevmFZN0 LXehz+vpwW+34hNVnEDRb22n3al9KIImTWCC6wiBOskpptRu7+NtDw2i8eb28pgWl2rq XP5U6D6k66htXg2+c6OffL8QKo9jV59lENVpA86UtKlYpfO5g/LfZU1c6li2gnWtXIDh nBgg==
X-Gm-Message-State: AKGB3mI9h0VBKn1qXMLMDlGs6md9MhJ93w3gyUtyQyF/3RFi7e2UaWld +V4gh4VILK1PHBuNMNsZs/WSCZICKYr/jqmhYPkftQ==
X-Google-Smtp-Source: ACJfBov/PI8rkRtVIr/xt+tw13LkvmwcB6kezquqttpu/nYSQAePEDyY60b2Yv3Akp6G/XvT/zv5Bh3m3MBFMKz3dXI=
X-Received: by 10.46.41.23 with SMTP id u23mr20107180lje.15.1516037500518; Mon, 15 Jan 2018 09:31:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.196.65 with HTTP; Mon, 15 Jan 2018 09:31:39 -0800 (PST)
In-Reply-To: <1516036467.5426.90.camel@nic.cz>
References: <87po6fmlkn.fsf@nic.cz> <CABCOCHSFfgjVS58S0po-9yEUZw=cjzG6k_LY8V9NSdy+kHQvLg@mail.gmail.com> <1516006155.5426.3.camel@nic.cz> <20180115.095941.341257692373089671.mbj@tail-f.com> <CABCOCHQBwsi7WiUZw5V0QQ-t2n9Yy=nY_dWzyaixsrXwmo4k=w@mail.gmail.com> <1516036467.5426.90.camel@nic.cz>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 15 Jan 2018 09:31:39 -0800
Message-ID: <CABCOCHSWsptUT_riewt3fY74EmSnZF70uQf=5tLFjy9maaYNMQ@mail.gmail.com>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: Martin Bjorklund <mbj@tail-f.com>, YANG Doctors <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1c0694afa5430562d3fce5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/6lla_TwB2cSVLB8tlDTj94eGkXY>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jan 2018 17:31:57 -0000

--94eb2c1c0694afa5430562d3fce5
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 15, 2018 at 9:14 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:

> On Mon, 2018-01-15 at 08:24 -0800, Andy Bierman wrote:
> > > ....
> >
> >
> > > > So what do you suggest? The last paragraph in sec. 9.10.3 is clearly
> > > wrong.
> > >
> > > I agree it is wrong, but only for identityref values that are defined
> > > in a module that has not been imported.  I stronlgy agree w/ Andy that
> > > this does NOT mean that we should change *working* and defined
> > > behaviour in an errata.
> >
> >
> > I think there is other text in the RFC that says a prefix is resolved in
> the
> > local module.
> > This is the only design that makes any sense, and the only design that
> could
> > ever work.
> > The module author has no control over prefix usage and imports in other
> > modules.
> >
> >
> > > The intention (for better or worse) was that the value would use the
> > > prefix used in imports.  This means that if you want to do any kind of
> > > comparision of the string value to some known identities, then you
> > > must import that module so that there is a prefix defined.  This was
> > > the intention.
> > >
> > > From this follows that (for all practical matters), the string value
> > > of an identity defined in a module that is not imported doesn't really
> > > matter.
> > >
> > > > Note also that this paragraphs tries to define the string value of an
> > > > identityref node instance for any XPath expression, which needn't
> > > necessarily be
> > > > a simple EqualityExpr.
> > >
> >
> >
> > The derived-from and derived-from-or-self functions are flawed
> > because they use prefixes instead of module names and a missing
> > prefix means the current module instead of the local module.
> > I don't see how using derived-from-or-self(type, "foo") is any better
> > than type="foo".  The latter is being used a lot and the XPath functions
> > are not being used (by our customers).
>
> Although I tend to agree that using module name as a parameter would be
> better
> (it was I believe the original proposal), it is IMO not as flawed as the
> string
> equality test because the semantics of the latter is defined by the XPath
> 1.0
> spec. In contrast, the derived-from(-or-self) functions are defined in
> YANG, so
> it is possible to specify additional semantics for its parameters.
>
>

This sort of distinction is not relevant to engineers writing YANG modules.


> I don't see any compelling reason why your customers couldn't use the
> functions.
> The problem of sec. 9.10.3 is that it gives an excuse for using the plain
> string
> test.
>
>
The <node> = <value> construct is quite familiar and intuitive to people.
A good API avoids confusion instead of promoting it.
The XPath function should have used a module-name parameter
or made the module name a mandatory prefix in the identity string.

The best-case for API stability is where the canonical representation is
also
the only representation. The worst-case (current prefix) is where the
representation
has a different interpretation everywhere it is used. Context-free value
comparison is
kind of useful.


Lada
>

Andy


>
> >
> > Seems new XPath functions are needed, like
> >    derived-from2(type, "iana-if-type", "ethernetCsmacd")
> >
> >
> >
> > >
> > > /martin
> > >
> >
> > Andy
> >
> > >
> > > >
> > > > Lada
> > > >
> > > > >
> > > > >
> > > > > > Lada
> > > > >
> > > > >
> > > > > Andy
> > > > >
> > > > > > >
> > > > > > >
> > > > > > > /martin
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >>
> > > > > > >> Lada
> > > > > > >>
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > /martin
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> >
> > > > > > >> > >
> > > > > > >> > > Lada
> > > > > > >> > >
> > > > > > >> > >
> > > > > > >> > > >
> > > > > > >> > > > and
> > > > > > >> > > >
> > > > > > >> > > >   module b {
> > > > > > >> > > >     ...
> > > > > > >> > > >     import ietf-ospf {
> > > > > > >> > > >       prefix y;
> > > > > > >> > > >     }
> > > > > > >> > > >     ...
> > > > > > >> > > >     leaf bar {
> > > > > > >> > > >       when "../type = 'y:ospfv3'";
> > > > > > >> > > >       ...
> > > > > > >> > > >     }
> > > > > > >> > > >   }
> > > > > > >> > > >
> > > > > > >> > > > You may not like it, but these two modules are both
> correct
> > > > > > according
> > > > > > >> > > > to the rules defined in RFC 7950.  The string value of
> the
> > > "type"
> > > > > > leaf
> > > > > > >> > > > *when evaluating the when expression* is different in
> the
> > > different
> > > > > > >> > > > modules.  See the last paragraph of section 9.10.3 in
> RFC
> > > 7950.
> > > > > > >> > > >
> > > > > > >> > > > > > > Also, potentially there can be a collision in
> prefixes
> > > and
> > > > > > then this
> > > > > > >> > > >
> > > > > > >> > > > also
> > > > > > >> > > > > > > breaks down.
> > > > > > >> > > > > >
> > > > > > >> > > > > >
> > > > > > >> > > > > > No, two modules cannot be imported with the same
> prefix.
> > > > > > >> > > > >
> > > > > > >> > > > > I have to disagree. An identity derived from the
> > > > > > >> > > > > "ietf-routing:control-protocol-type" base identity
> can be
> > > defined
> > > > > > >> > > > > in a module that is not imported anywhere. If a server
> > > declares
> > > > > > such
> > > > > > >> > > > > a module as implemented, then "rt:type" may have this
> value
> > > per
> > > > > > >> > > > > sec. 9.10.2.
> > > > > > >> > > > >
> > > > > > >> > > > > And, consequently, there may be two different modules
> with
> > > > > > >> > > > > conflicting prefixes defining identities that are
> derived
> > > from
> > > > > > >> > > > > "ietf-routing:control-protocol-type".
> > > > > > >> > > >
> > > > > > >> > > > Sure, but this is not the point.
> > > > > > >> > > >
> > > > > > >> > > > > > > A moral of the namespace/prefix story in XML was
> that
> > > relying
> > > > > > of
> > > > > > >> > > > > > > namespace prefixes having a particular value is a
> > > really bad
> > > > > > >> > > > > > > idea. I know that the cited paragraph was
> intended to
> > > make
> > > > > > such
> > > > > > >> > > > > > > XPath string comparisons more deterministic, but
> it is
> > > also
> > > > > > >> > > > > > > problematic and should be avoided if possible.
> > > > > > >> > > > > >
> > > > > > >> > > > > > Note that this prefix is under the control of the
> module
> > > > > > designer
> > > > > > >> > > > > > writing the XPath expression.  The same identityref
> value
> > > might
> > > > > > use a
> > > > > > >> > > > >
> > > > > > >> > > > > No, it is not. The prefixes appear in instance data.
> > > > > > >> > > >
> > > > > > >> > > > The prefix *in the when expression* is under the
> control of
> > > the
> > > > > > module
> > > > > > >> > > > designer, as explained above.
> > > > > > >> > > >
> > > > > > >> > > > You are correct that the prefix in an XML encoding is
> not
> > > under
> > > > > > >> > > > control of the module designer, but noone has claimed
> that.
> > > > > > >> > > >
> > > > > > >> > > > I agree that it is unfortunate that context-specific
> prefixes
> > > are
> > > > > > used
> > > > > > >> > > > for the identityref values.  It would have been better
> if we
> > > used a
> > > > > > >> > > > context free representation, e.g. "<module-
> > > name>:<identity>".  But
> > > > > > >> > > > that's another discussion.
> > > > > > >> > > >
> > > > > > >> > > >
> > > > > > >> > > >
> > > > > > >> > > > /martin
> > > > > > >> > >
> > > > > > >> > > --
> > > > > > >> > > Ladislav Lhotka
> > > > > > >> > > Head, CZ.NIC Labs
> > > > > > >> > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > > > >> > >
> > > > > > >> --
> > > > > > >> Ladislav Lhotka
> > > > > > >> Head, CZ.NIC Labs
> > > > > > >> PGP Key ID: 0xB8F92B08A9F76C67
> > > > > > >>
> > > > > > >> _______________________________________________
> > > > > > >> yang-doctors mailing list
> > > > > > >> yang-doctors@ietf.org
> > > > > > >> https://www.ietf.org/mailman/listinfo/yang-doctors
> > > > > > >>
> > > > > >
> > > > > > --
> > > > > > Ladislav Lhotka
> > > > > > Head, CZ.NIC Labs
> > > > > > PGP Key ID: 0xB8F92B08A9F76C67
> > > > > >
> > > > > > _______________________________________________
> > > > > > yang-doctors mailing list
> > > > > > yang-doctors@ietf.org
> > > > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> > > > >
> > > > >
> > > > --
> > > > Ladislav Lhotka
> > > > Head, CZ.NIC Labs
> > > > PGP Key ID: 0xB8F92B08A9F76C67
> > > >
> >
> >
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>

--94eb2c1c0694afa5430562d3fce5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Jan 15, 2018 at 9:14 AM, Ladislav Lhotka <span dir=3D"ltr">&lt;=
<a href=3D"mailto:lhotka@nic.cz" target=3D"_blank">lhotka@nic.cz</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">On Mon, 2018-01-15 at 08:24 -=
0800, Andy Bierman wrote:<br>
&gt; &gt; ....<br>
&gt;<br>
&gt;<br>
&gt; &gt; &gt; So what do you suggest? The last paragraph in sec. 9.10.3 is=
 clearly<br>
&gt; &gt; wrong.<br>
&gt; &gt;<br>
&gt; &gt; I agree it is wrong, but only for identityref values that are def=
ined<br>
&gt; &gt; in a module that has not been imported.=C2=A0 I stronlgy agree w/=
 Andy that<br>
&gt; &gt; this does NOT mean that we should change *working* and defined<br=
>
&gt; &gt; behaviour in an errata.<br>
&gt;<br>
&gt;<br>
&gt; I think there is other text in the RFC that says a prefix is resolved =
in the<br>
&gt; local module.<br>
&gt; This is the only design that makes any sense, and the only design that=
 could<br>
&gt; ever work.<br>
&gt; The module author has no control over prefix usage and imports in othe=
r<br>
&gt; modules.<br>
&gt;<br>
&gt;<br>
&gt; &gt; The intention (for better or worse) was that the value would use =
the<br>
&gt; &gt; prefix used in imports.=C2=A0 This means that if you want to do a=
ny kind of<br>
&gt; &gt; comparision of the string value to some known identities, then yo=
u<br>
&gt; &gt; must import that module so that there is a prefix defined.=C2=A0 =
This was<br>
&gt; &gt; the intention.<br>
&gt; &gt;<br>
&gt; &gt; From this follows that (for all practical matters), the string va=
lue<br>
&gt; &gt; of an identity defined in a module that is not imported doesn&#39=
;t really<br>
&gt; &gt; matter.<br>
&gt; &gt;<br>
&gt; &gt; &gt; Note also that this paragraphs tries to define the string va=
lue of an<br>
&gt; &gt; &gt; identityref node instance for any XPath expression, which ne=
edn&#39;t<br>
&gt; &gt; necessarily be<br>
&gt; &gt; &gt; a simple EqualityExpr.<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; The derived-from and derived-from-or-self functions are flawed<br>
&gt; because they use prefixes instead of module names and a missing<br>
&gt; prefix means the current module instead of the local module.<br>
&gt; I don&#39;t see how using derived-from-or-self(type, &quot;foo&quot;) =
is any better<br>
&gt; than type=3D&quot;foo&quot;.=C2=A0 The latter is being used a lot and =
the XPath functions<br>
&gt; are not being used (by our customers).<br>
<br>
Although I tend to agree that using module name as a parameter would be bet=
ter<br>
(it was I believe the original proposal), it is IMO not as flawed as the st=
ring<br>
equality test because the semantics of the latter is defined by the XPath 1=
.0<br>
spec. In contrast, the derived-from(-or-self) functions are defined in YANG=
, so<br>
it is possible to specify additional semantics for its parameters.<br>
<br></blockquote><div><br></div><div><br></div><div>This sort of distinctio=
n is not relevant to engineers writing YANG modules.</div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I don&#39;t see any compelling reason why your customers couldn&#39;t use t=
he functions.<br>
The problem of sec. 9.10.3 is that it gives an excuse for using the plain s=
tring<br>
test.<br>
<br></blockquote><div><br></div><div>The &lt;node&gt; =3D &lt;value&gt; con=
struct is quite familiar and intuitive to people.</div><div>A good API avoi=
ds confusion instead of promoting it.</div><div>The XPath function should h=
ave used a module-name parameter</div><div>or made the module name a mandat=
ory prefix in the identity string.</div><div><br></div><div>The best-case f=
or API stability is where the canonical representation is also</div><div>th=
e only representation. The worst-case (current prefix) is where the represe=
ntation</div><div>has a different interpretation everywhere it is used. Con=
text-free value comparison is</div><div>kind of useful.</div><div><br></div=
><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
Lada<br></blockquote><div><br></div><div>Andy</div><div>=C2=A0</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<br>
&gt;<br>
&gt; Seems new XPath functions are needed, like<br>
&gt;=C2=A0 =C2=A0 derived-from2(type, &quot;iana-if-type&quot;, &quot;ether=
netCsmacd&quot;)<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; /martin<br>
&gt; &gt;<br>
&gt;<br>
&gt; Andy<br>
&gt;<br>
&gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Lada<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; Lada<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; Andy<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt; /martin<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; Lada<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; /martin<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; Lada<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; and<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0module b {<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0import =
ietf-ospf {<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
prefix y;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0...<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0leaf ba=
r {<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
when &quot;../type =3D &#39;y:ospfv3&#39;&quot;;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
...<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; You may not like it, but t=
hese two modules are both correct<br>
&gt; &gt; &gt; &gt; &gt; according<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; to the rules defined in RF=
C 7950.=C2=A0 The string value of the<br>
&gt; &gt; &quot;type&quot;<br>
&gt; &gt; &gt; &gt; &gt; leaf<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; *when evaluating the when =
expression* is different in the<br>
&gt; &gt; different<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; modules.=C2=A0 See the las=
t paragraph of section 9.10.3 in RFC<br>
&gt; &gt; 7950.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; Also, poten=
tially there can be a collision in prefixes<br>
&gt; &gt; and<br>
&gt; &gt; &gt; &gt; &gt; then this<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; also<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; breaks down=
.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; No, two modules =
cannot be imported with the same prefix.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; I have to disagree. A=
n identity derived from the<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &quot;ietf-routing:co=
ntrol-<wbr>protocol-type&quot; base identity can be<br>
&gt; &gt; defined<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; in a module that is n=
ot imported anywhere. If a server<br>
&gt; &gt; declares<br>
&gt; &gt; &gt; &gt; &gt; such<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; a module as implement=
ed, then &quot;rt:type&quot; may have this value<br>
&gt; &gt; per<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; sec. 9.10.2.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; And, consequently, th=
ere may be two different modules with<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; conflicting prefixes =
defining identities that are derived<br>
&gt; &gt; from<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &quot;ietf-routing:co=
ntrol-<wbr>protocol-type&quot;.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; Sure, but this is not the =
point.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; A moral of =
the namespace/prefix story in XML was that<br>
&gt; &gt; relying<br>
&gt; &gt; &gt; &gt; &gt; of<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; namespace p=
refixes having a particular value is a<br>
&gt; &gt; really bad<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; idea. I kno=
w that the cited paragraph was intended to<br>
&gt; &gt; make<br>
&gt; &gt; &gt; &gt; &gt; such<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; XPath strin=
g comparisons more deterministic, but it is<br>
&gt; &gt; also<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; problematic=
 and should be avoided if possible.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; Note that this p=
refix is under the control of the module<br>
&gt; &gt; &gt; &gt; &gt; designer<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; writing the XPat=
h expression.=C2=A0 The same identityref value<br>
&gt; &gt; might<br>
&gt; &gt; &gt; &gt; &gt; use a<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; No, it is not. The pr=
efixes appear in instance data.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; The prefix *in the when ex=
pression* is under the control of<br>
&gt; &gt; the<br>
&gt; &gt; &gt; &gt; &gt; module<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; designer, as explained abo=
ve.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; You are correct that the p=
refix in an XML encoding is not<br>
&gt; &gt; under<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; control of the module desi=
gner, but noone has claimed that.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; I agree that it is unfortu=
nate that context-specific prefixes<br>
&gt; &gt; are<br>
&gt; &gt; &gt; &gt; &gt; used<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; for the identityref values=
.=C2=A0 It would have been better if we<br>
&gt; &gt; used a<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; context free representatio=
n, e.g. &quot;&lt;module-<br>
&gt; &gt; name&gt;:&lt;identity&gt;&quot;.=C2=A0 But<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; that&#39;s another discuss=
ion.<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; &gt; /martin<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; --<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; Ladislav Lhotka<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<=
br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; --<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; Ladislav Lhotka<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; ______________________________<wbr>______=
___________<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; yang-doctors mailing list<br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; <a href=3D"mailto:yang-doctors@ietf.org">=
yang-doctors@ietf.org</a><br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt; <a href=3D"https://www.ietf.org/mailman/l=
istinfo/yang-doctors" rel=3D"noreferrer" target=3D"_blank">https://www.ietf=
.org/mailman/<wbr>listinfo/yang-doctors</a><br>
&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; --<br>
&gt; &gt; &gt; &gt; &gt; Ladislav Lhotka<br>
&gt; &gt; &gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; ______________________________<wbr>_______________=
__<br>
&gt; &gt; &gt; &gt; &gt; yang-doctors mailing list<br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"mailto:yang-doctors@ietf.org">yang-doct=
ors@ietf.org</a><br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/y=
ang-doctors" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mail=
man/<wbr>listinfo/yang-doctors</a><br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; --<br>
&gt; &gt; &gt; Ladislav Lhotka<br>
&gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt; &gt; &gt;<br>
&gt;<br>
&gt;<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Ladislav Lhotka<br>
Head, CZ.NIC Labs<br>
PGP Key ID: 0xB8F92B08A9F76C67<br>
</font></span></blockquote></div><br></div></div>

--94eb2c1c0694afa5430562d3fce5--


From nobody Tue Jan 16 08:56:26 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00009131604 for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 08:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Ig903beIGH_i for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 08:56:24 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 108FF12FB12 for <yang-doctors@ietf.org>; Tue, 16 Jan 2018 08:46:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=652; q=dns/txt; s=iport; t=1516121219; x=1517330819; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=lCxelgqf4Lp3RorQW1I1XA13FXmolXBDXtA5O3p5+0Y=; b=UM1N1qz270mqV2bR7dIGy+o8Of0GPkiN0lWlSpJQTs1VJwwT9Wj1WHmG 4e7pcHCjrk22kD+yyCLkD8G2SVtt7DCy93bhSeowAhqOFnVDaeiuwFfTB /JHHSybMhlMszpkKIR/Wrz9ZiyJT56JAnZphBzjaLlxQx3k+6rKMZPjCr 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B2AQABLF5a/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYQndCeEE4sYjzyZdAoYC4UYAoUfFAEBAQEBAQEBAWsohSQCBAE?= =?us-ascii?q?BIRU2GwsODAImAgInMAYBDAYCAQGKLxClMYIniUsBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEbBYEPhxmCEoMFgy8BAQIBhQWCRSABBKNkiAyNP4IAiiWHa40+gV6ICYE8NiK?= =?us-ascii?q?BUDIaCBsVPYIqhFhAN4xQAQEB?=
X-IronPort-AV: E=Sophos;i="5.46,369,1511827200";  d="scan'208";a="1431454"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2018 16:46:55 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w0GGktYH019094; Tue, 16 Jan 2018 16:46:55 GMT
To: Ebben Aries <exa@juniper.net>, yang-doctors@ietf.org
References: <20180111200356.i2pyyqgh455lxfe6@smtp.juniper.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <3b94ff67-16e7-99c3-25a0-6ed7ed5b4ac2@cisco.com>
Date: Tue, 16 Jan 2018 17:46:55 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180111200356.i2pyyqgh455lxfe6@smtp.juniper.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/WocJwX8E_6GdfVdN_FVNtG9IHTA>
Subject: Re: [yang-doctors] yang-version in module template/rfc6087bis
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 16:56:25 -0000

Hi Ebben,
> I noticed yang-version is missing from the template and doesn't appear
> to be any reference in these guidelines.  Is this intentional?
>
> https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
>
> I'll assume that anything going through review right now should carry
> 1.1?
Since some of the core YANG module (ex: rfc7223bis) requires YANG 1.1, I 
believe it makes sense.
I thing the template should be changed in RFC6087bis.

Regards, B.
>
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
> .
>


From nobody Tue Jan 16 09:03:11 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E62113160B for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 09:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, 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
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 DXMJIiOeYORf for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 09:03:08 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F44113160C for <yang-doctors@ietf.org>; Tue, 16 Jan 2018 09:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=382; q=dns/txt; s=iport; t=1516122187; x=1517331787; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=IDJWOdcR7GHA5OYyOdyHyaMavBECs5zQuS0wc94DpJ8=; b=fo6jPquY1Y1SLWo3QCAbYnUrLbbIHNBIATRG+BEayoRPB+ih+BRzLC3Q hcZcO3YEoxBlB4KV8r7CzMb9K9ZGh5ZiCBoYQuU+3zrPq/aqjmqAbdBuu ZJAK7uYACKlFYXZF3fDoon5G0HN96qTfxpYSExLtwrI44/ogr76NIKMV/ o=;
X-IronPort-AV: E=Sophos;i="5.46,369,1511827200";  d="scan'208";a="1484557"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2018 17:03:06 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id w0GH350D023323; Tue, 16 Jan 2018 17:03:05 GMT
To: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com>
Date: Tue, 16 Jan 2018 18:03:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180110232830.6rqbhpw5s55kx6zo@elstar.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/OaWgvPZrvCe2X83w9r-f0g9xivw>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 17:03:09 -0000

On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:
> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
>> The feature-per-leaf approach should not be approved by YD.
Do we want to add a sentence in 
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17, 
expressing that a feature-per-leaf is most likely the wrong approach?

Regards, Benoit


From nobody Tue Jan 16 09:36:35 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 127F01315ED for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 09:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 aCJZ4kV6kJ4A for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 09:36:31 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 5F6CE12D72F for <yang-doctors@ietf.org>; Tue, 16 Jan 2018 09:26:19 -0800 (PST)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0GHQHmL024041; Tue, 16 Jan 2018 09:26:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=PPS1017; bh=JV0mW9eH0TiBR3TAP2znvpC26k7U9NF5ZNHyU2P55T4=; b=zn7v2ceyk7czAMxDtUbDv52jKIglrkNfPHtRM8TM3tMd5HngyXhbIYuIp7YumUHEszOm SO1yNSUo19u3Az6o3ay7aXW6fe/MmsPuzHItUjDVdsHz8M0i0nErBR1IQQr1/5a5smqy u8ecDzb89j6pc43WqgkMKTYy4aIh7cjOh/o0XWGNwWFz7MAjYtN3dfX5I5TQ8PymICkn 7j9zsd7niko5UkEmdlJnxDcy90JgHC2tlKcD64cM1UL2TDpY0KtpXIzhLaa/o089vhn3 4lNRNNVyVm34KcGljEIOkAGSqsVWZom11If6EORzTpcMtW6OOKUkP+LESMhSkbdS5K3X aw== 
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0022.outbound.protection.outlook.com [216.32.180.22]) by mx0a-00273201.pphosted.com with ESMTP id 2fhnstg006-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 16 Jan 2018 09:26:10 -0800
Received: from SN4PR0501CA0069.namprd05.prod.outlook.com (10.167.112.174) by DM5PR05MB3611.namprd05.prod.outlook.com (10.174.243.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.9; Tue, 16 Jan 2018 17:26:05 +0000
Received: from BY2NAM05FT063.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e52::206) by SN4PR0501CA0069.outlook.office365.com (2603:10b6:803:41::46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.428.9 via Frontend Transport; Tue, 16 Jan 2018 17:26:05 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by BY2NAM05FT063.mail.protection.outlook.com (10.152.100.200) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.428.12 via Frontend Transport; Tue, 16 Jan 2018 17:26:05 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Tue, 16 Jan 2018 09:25:57 -0800
Date: Tue, 16 Jan 2018 10:25:56 -0700
From: Ebben Aries <exa@juniper.net>
To: Benoit Claise <bclaise@cisco.com>
CC: Andy Bierman <andy@yumaworks.com>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180116172556.7xgbtplfgyziedxj@smtp.juniper.net>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(39860400002)(39380400002)(346002)(376002)(396003)(2980300002)(24454002)(189003)(199004)(966005)(69596002)(1076002)(97736004)(7696005)(8936002)(46406003)(6246003)(53936002)(6306002)(59450400001)(305945005)(26005)(54906003)(2906002)(4326008)(50466002)(55016002)(8676002)(81166006)(81156014)(356003)(76176011)(575784001)(86362001)(23726003)(478600001)(105596002)(6916009)(2950100002)(53546011)(16586007)(97756001)(47776003)(104016004)(106466001)(5660300001)(77096006)(93886005)(68736007)(229853002)(53416004)(316002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3611; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; BY2NAM05FT063; 1:sbsdODl+kkDPSGCmc7E1rRRrsDJryca0v5BSMexgTJ/hTm1YxOchDPOrzotGGubxotNJgYxcqN8Ymlysk8RNLEyOOT0VsPQD9zDHVdsJ26c7am5fXfNQ5STuNeHFJ14z
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 768c0087-7152-48e4-dfc9-08d55d063950
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534125)(4602075)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:DM5PR05MB3611; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3611; 3:dWD+1BqG6mRJkiwQJh96dclWpDxK9jD9/cbJsWUTF3lFuLoSUuLtdTrM0XBwcV8nf3+XtEvXfzhv4dQ92uh4zqyIalLz485csblREtcly7tOnmXRtXI6dcuGYtBJMSY4ubLEX+qHZt/IC4NA9jXCpbQXIv52dxGetxntNTXQVXSZdBqkyCbzo1rYiRiudpk2KlbrcwMSPDDaxURvE9gL2joxED0FYt3Cmk+az2bmr0tovtB827/g95Rzw/xeQ3vbOgT8XbYOtpjYW/6ObFBEniOg04QpkqujVtCF2fXZ6gsQEyEiKc4wqY8FHvfolUqXgYrtwp0fLSwFoHbwnI0yXiaL2ncIfrX+9TnG3cFt7jM=; 25:3O0MENPA4KtVIjM2mj870sqIBL2wHTuvI8bmEWtFcHqi2kKYnQjeA5v4Kqb+aeS0lX8/qK7ap7XqJft1EaGuC3BzmvcVn9BggpvsZQUVyFnJvNhnJIDN4eDd8Bc+7A1h7/XLssdlfcMs83xCTEni7FKRUFC8gTGlQdPTWBERqwdR98/XT9V6+XDyItjnP0Y+OCYDrH7C28BjPdUW7lZOuYsfww7wzB0KUiXnWFN8XtLdW3n/bZt5XTWJY04lTAZVASmQFVXQiNG9qKrV1rI46NRHQzddCZ8Zs9Ewqb/PytQFGc/w2DKKOh7sOyFAecRNSZ5XKvGQXRvANuRUNhWG9Q==
X-MS-TrafficTypeDiagnostic: DM5PR05MB3611:
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3611; 31:BnxUi2Gr4lHBxtU/pwzinP0J+EHQ9C6cxyZii63GeP1PCt11FO49+8w//744xjMxA0Zug9AyRD37ud7hK06ZuzJjK78gMm9HbAAoop2Pg3G50vnY/yLF6tkYRvTeeMWBm0Y5isSDQ+VHlQlgE1zB+idXBbcN8mVFj44ZUssPxg7yAg8GctDwHRQehx+Mso6TBw+cKx2PkkyRpQaOkcCz1yxCy2RP/FIY4qJocQm8d54=; 20:ERUS9QuxikoSGRo8K0NprU2APatElDBOZBezNZfEIsSpj0REGTjg6UtbmLnRmzAqvp8wu5RrMyfiYvnx0UYH8/360cGuUdQHkSiJt9jq7fuza8/bCJbvSqeiVCNi/6dQVwjzbZNDYabC6Yi+LFnZA+qS5nVkhbBH+MOFML8GXOcby6zhokjKFjAdINGrlwzVQmwb56zkab5MQKFUmgu6MJMyxjrcoSQFrdBImsLHHU5xnXamkf3tNmGyb/afYAQhwGIig2NT2aA6RzfZEywU/1dKu7kI2yjIkGm66VylS1Bbu2JtUEHJfkRxyuz+a3acyggvezmNtsKMCkCyfbgfz/fgmN4OTgeu2NTL8e03eQLyZPZnACHrDfWC0egv8m/IHdRobP5SLegM6Hf/q6JAbDZWGjfMtPq07eCx5WG08k3NDojdCZGQ09seF0Wpn8hbmsdlcypMuIZRV2Dn7FNKWT4ZrIhm7dhKTfSSQ9ZNyKj2WCsi4Zht1BI+Yq0cWJln
X-Microsoft-Antispam-PRVS: <DM5PR05MB361194DEFE1EFCB5B8222D01A8EA0@DM5PR05MB3611.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(10436049006162);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040470)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(3231023)(944501161)(10201501046)(6055026)(6041268)(20161123560045)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011); SRVR:DM5PR05MB3611; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:DM5PR05MB3611; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3611; 4:yQLt6NWN6MbBwAJ5ekUn13UfEff2NhKCkOAwL3ub3IfWSrFh51xlci+cdoZF/XpZUIWL7evNV67x5G1ob06LscYu1gXu3cvs6iUrC5L2bjDMMbnzOJRCzgMVIyZ4e1z+MWIsJbn2Kzc+t/I5CSHDEZRXQPbwB/w274SIDv3U51j3uodV0qaDNAZjDvvOxToIrXhuCCKF5HHM/nmnsyEuWsTJVWUB44TwZ+l1tLR/Jxn5njRgQIbsXUkKQAmlqCnQhG7NQbPRGUhzMzwxC5tJ0vlZM/J1NIy3+HrwV75nlYy44cd0+V3bxuRK720DKcj6
X-Forefront-PRVS: 0554B1F54F
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM5PR05MB3611; 23:0lHJCr4xKNowTjezoKDnchf/btZjpi5UhK00B0dNE?= =?us-ascii?Q?phWHe4/6XkTYYPNi2FnsVf6lILGCSz5KTIOCuomz2lClUsY1VP+Eo8RH5ylF?= =?us-ascii?Q?LXkBhSX81Sk/5mFtJp6czQUwsjVsilTk6dF2czz6X9djOiYgFZWhgJCU4e3o?= =?us-ascii?Q?u3bOawmwTI32RoeDoOlpfhbhD/gCiG6S4ksZ86ejAaaXv98fMH5lnk4lSm0O?= =?us-ascii?Q?HPcwzmjcUnN2jxYfQYZ9DYnv3uy/PI7y8tJql0YtnCUmIgo3G0rBJc5THOvj?= =?us-ascii?Q?3n0qKXu8zjBmeepVyICo0ZeNVZMve7wZa8NA9VrMm1Uiv2q3CvKlTof3VPlh?= =?us-ascii?Q?40dbq9JR0I4J3JkpNGea6ffZsz6Ddn3FpuENdbq5JLt1JPRIaxnXHtgyCRxe?= =?us-ascii?Q?92kzrvrnn+Sqf7Mc0wWL+PDcLoO2uwP9AitH3xaqb72DO2Ts8FDj2Obgne9p?= =?us-ascii?Q?gYU5ZXTbTt5KwCeAoJ1pNwcwm5ajJ4qjOVvFJYmHkQyJWQdWhPIJFAefm1tE?= =?us-ascii?Q?/XTfG1TdA3qkQLeJsI0KlIbzX3OUPdWEUi6352rroQLhYhvRzKY+0vJv3cGX?= =?us-ascii?Q?KWKNtj3t81/AIXsoXtKrG3z2db8yBByzSPZaBvueQUFqKaNB6N2m2aQdOv21?= =?us-ascii?Q?y02HQ3Dsd2Rv8vIISaeO9LZFd6BLxJHf+ycDl9+K6zLxht4bT3b97Zj3bsXu?= =?us-ascii?Q?ezzfStzzzvMRTGnZ1GCHkz7yDETFyooc4ICqtVshdfoztmTQh/8fMZOMN58v?= =?us-ascii?Q?haaefeRGftNOJjNmVH8nfCOlboicTPvv9Qq9eNNzxkNGqvxySwdLpRpftwCQ?= =?us-ascii?Q?H4hv2s6UoSoeM0U8F+eKECaU705amQELwEg7WW/YvgctzxhBX6qryRLIvYx9?= =?us-ascii?Q?y2ae4sVlMwfqbBmuSQeednCl97T4MlYcUYqHK85ZmSPDFCdbnwCxWrqzO51+?= =?us-ascii?Q?yKG9rE3B2mJ7oL5WcAc4bYNdUupkK4bzNX49z8wp4TPBW5WqsilpQBRELBDC?= =?us-ascii?Q?HBI7izdduLZccmd0ob7EwAFPWS7tGYcX05/ezCInksj8SRublpLIZEkWqTpb?= =?us-ascii?Q?Vr6BI2dtCLDhLc7oxTY6LuarmwdLtoKB0YuZ6PA3lWMM79ACvksZP9yqu6t6?= =?us-ascii?Q?SSbQqsFwQ/l7hZANfLmRPqCxoSDiqEvTGX7bthlDEXMfUzMnNNS5ocrLk22l?= =?us-ascii?Q?GmDii2bhJXG+LBNTDZm5bZm8QBbbgk7gnYfbmzTE6JM8nEmKC6rSuuSZQ=3D?= =?us-ascii?Q?=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3611; 6:wIwJtxwnmGGp8Vmjn4DsuY/YFRuWv4ArM5P32Up3lq2NBIyzXaxZ8zZqALU+QNpec6O1XhU/53J5ndcHx4yT9lmQ5mqq/5oe3E943fKd+cXiYwqOGrY9LAeebUNZogjLXmSYzBVT/Q0bqcjoCvq1VH3FB/mZUkfXBGPEm77chQ9QtH4Mr6oETooO8N1iNd0lXV4x7uDOpr4hboCJoddQk779QTxukhYaVH8htVWn+TdV6ZowUKiVYatb2WpR7xHP3aT0GNiIa4PA6l6lpasdFu07goGFPtxfBjY44C7F66fVQJe2Qy8PD2qBRfjYICalaWW9bU9RlUbSU44+2LuZ6XCccSukwQgUbUhFW6RUUhA=; 5:BvsCyllRU8y5mCzgQzPmKZxJX6lGU8Zy7gZ0DTzQBvyqH/NMMj88zQMzawrzoh684nBvsNTv+w1O49Vhkcu1vwbn9/2in+ivRy4wScxhHYvBHJ1Kv3TJPgCOz/tQPQXFVGPOjoW8lmAbXsneon9kydS6qqnMnslhi4D8TwR3Pe4=; 24:MI1W0huVXkz3JNTrbmup2eFHLaejl3VF6T9m93QfpNZjRu6Nah1WUqQEYYMkJIoWHufBZVhdusRq3eR8bDceJ0ZINdcrQTpIyVuOL+HSRVY=; 7:7X1MPJjhqZ3RSw5WZqdZkvsednmaKVXsZovqXNB2pLnHeucSkUSKkDlfwRedwOgmqfxBlTXqUFanH9Cg+e0ysGMoJg99sqnWpMATo5UHlDzW6kx+RtyWYRwMZzJVSLIFdY/vv4VBmP+LucWhiW2ZXSBDrLPNQgAA47G4BBvKacEZ+Pe82eaUKolf1ZwTTqpb8ENN5z084IxYlvyZ948DTGjoFkuDOGA5Z7TH0TOV2XHE3c7maxNV0Pfs9ok3couY
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 16 Jan 2018 17:26:05.3394 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 768c0087-7152-48e4-dfc9-08d55d063950
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3611
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-16_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=665 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801160238
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/26jS-CoIhFbh8gD9gUrLqWb9E3I>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 17:36:34 -0000

On Jan 16 18:03 PM, Benoit Claise wrote:
> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:
> > On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
> > > The feature-per-leaf approach should not be approved by YD.
> Do we want to add a sentence in https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=DwICaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=nQGeE0OfNIkUQ28OwBMtTNK_yfuu6lvybq_d4HmVgcQ&s=-Fcnf3yjcv4zOig-zswod3QT1HuorecwuFZpuT0VJm4&e=,
> expressing that a feature-per-leaf is most likely the wrong approach?
>

There likely needs to be some wording around using good judgement while
taking into account how this will be consumed and used.  A feature per
container can also be a bad idea if this turns out to be excessive.  How
many is too many?

If we fast fwd a few yrs and assume we cover the entire network-element,
are we going to end up w/ 1000s of possible features that need to be
conveyed and handled?

Thx

/ebben


From nobody Tue Jan 16 09:43:31 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4B512E049 for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 09:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] 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 dHU0bu_wBRdl for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 09:43:26 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8308C12E868 for <yang-doctors@ietf.org>; Tue, 16 Jan 2018 09:43:26 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 82572EAF; Tue, 16 Jan 2018 18:43:24 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id U66IA9Bmpm9r; Tue, 16 Jan 2018 18:43:24 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Tue, 16 Jan 2018 18:43:24 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 5E14D2013F; Tue, 16 Jan 2018 18:43:24 +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 bA1psY1iKjsj; Tue, 16 Jan 2018 18:43:23 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id E23EB2013E; Tue, 16 Jan 2018 18:43:23 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id A1ED5421215A; Tue, 16 Jan 2018 18:43:23 +0100 (CET)
Date: Tue, 16 Jan 2018 18:43:23 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Cc: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180116174323.e2b4zr5ffgrycnei@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/D8uD4giqqhwyIhrgYqs8DSE8POM>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 17:43:29 -0000

On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote:
> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:
> > On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
> > > The feature-per-leaf approach should not be approved by YD.
> Do we want to add a sentence in
> https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17,
> expressing that a feature-per-leaf is most likely the wrong approach?

This is difficult to describe. Perhaps something like this is a
reasonably small change to the existing text (which only talks about
too big features but not about too small features).

OLD

   The YANG "feature" statement is used to define a label for a set of
   optional functionality within a module.  The "if-feature" statement
   is used in the YANG statements associated with a feature.

   The set of YANG features available in a module should be considered
   carefully.  The description-stmt within a feature-stmt MUST specify
   any interactions with other features.

   If there is a large set of objects...

NEW

   The YANG "feature" statement is used to define a label for a set of
   optional functionality within a module.  The "if-feature" statement
   is used in the YANG statements associated with a feature.  The
   description-stmt within a feature-stmt MUST specify any
   interactions with other features.

   The set of YANG features defined in a module should be considered
   carefully. Very fine granular features increase interoperability
   complexity and should be avoided. A likely misuse of the feature
   mechanism is the tagging of individual leafs (e.g., counters) with
   separate features.

   If there is a large set of objects...

/js

-- 
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/>


From nobody Tue Jan 16 10:26:54 2018
Return-Path: <rrahman@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72382127286 for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 10:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 i7vJYtQIfTcn for <yang-doctors@ietfa.amsl.com>; Tue, 16 Jan 2018 10:26:51 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A440612D858 for <yang-doctors@ietf.org>; Tue, 16 Jan 2018 10:26:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3138; q=dns/txt; s=iport; t=1516127211; x=1517336811; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=cOYYwyGNLkJinzJGjJxQSFWJnPCsHhKFgDuqUpYgmgo=; b=H/EZDAboNKUoXoIPv2MNMQiSO7poiaWWwP/cJ1Fxwc4vr1hvTA8SCZVD 8laQ4vcKRhIr/1po7MHzH0V2c/aJXbT+xCC0ZaMlRyaCXXAihr7HxJI4u seFAFX9AKysRjCICcbS0Oy02Qw3oAZi20mtvdthebzGEqVY8/D6z9GSaz E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AXAQDVQl5a/4YNJK1YAxkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDQWZ0JweEDIokjmCBWyeXLIIWCiWFFgIahEI/GAEBAQEBAQE?= =?us-ascii?q?BAWsohSQBBSMRRQ4CAgEIDgIIAgImAgICGRcVEAIEAQ0FijMQpRuCJ4lLAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBGAUFgQqFQoFXgWkpDIJ5gy8BAQIBgW4XCiaCUDG?= =?us-ascii?q?CFCAFo2QCiAqNP5QQjT6JOgIRGQGBOwEfOYE5DwhvFWcBgX+EV3gBizgBgRYBA?= =?us-ascii?q?QE?=
X-IronPort-AV: E=Sophos;i="5.46,369,1511827200"; d="scan'208";a="56875637"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jan 2018 18:26:51 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w0GIQoXS020906 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 16 Jan 2018 18:26:50 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 16 Jan 2018 12:26:50 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Tue, 16 Jan 2018 12:26:50 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
CC: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] Features and must-condition
Thread-Index: AQHTilaYFa81RoW2ZUea0h9DxiIyiaNuBSgAgAAH5ICAAAFAgIAABaMAgAADUICAAANLAIAACtAAgAkCTYCAAAtDgIAADCYA
Date: Tue, 16 Jan 2018 18:26:50 +0000
Message-ID: <30BB5605-4584-4D05-B7ED-1E93765419CD@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local>
In-Reply-To: <20180116174323.e2b4zr5ffgrycnei@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.212.60]
Content-Type: text/plain; charset="utf-8"
Content-ID: <034CE901131B75439900E1DC093ACAEA@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/bIIMAtfHpFovUw406Yfms91Pk9s>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jan 2018 18:26:53 -0000

VGhpcyBjaGFuZ2Ugc2VlbXMgcmVhc29uYWJsZSB0byBtZS4NCg0KDQpPbiAyMDE4LTAxLTE2LCAx
Mjo0MyBQTSwgIkp1ZXJnZW4gU2Nob2Vud2FlbGRlciIgPGouc2Nob2Vud2FlbGRlckBqYWNvYnMt
dW5pdmVyc2l0eS5kZT4gd3JvdGU6DQoNCiAgICBPbiBUdWUsIEphbiAxNiwgMjAxOCBhdCAwNjow
MzowNVBNICswMTAwLCBCZW5vaXQgQ2xhaXNlIHdyb3RlOg0KICAgID4gT24gMS8xMS8yMDE4IDEy
OjI4IEFNLCBKdWVyZ2VuIFNjaG9lbndhZWxkZXIgd3JvdGU6DQogICAgPiA+IE9uIFdlZCwgSmFu
IDEwLCAyMDE4IGF0IDAyOjQ5OjQ4UE0gLTA4MDAsIEFuZHkgQmllcm1hbiB3cm90ZToNCiAgICA+
ID4gPiBUaGUgZmVhdHVyZS1wZXItbGVhZiBhcHByb2FjaCBzaG91bGQgbm90IGJlIGFwcHJvdmVk
IGJ5IFlELg0KICAgID4gRG8gd2Ugd2FudCB0byBhZGQgYSBzZW50ZW5jZSBpbg0KICAgID4gaHR0
cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0bW9kLXJmYzYwODdiaXMtMTUj
c2VjdGlvbi00LjE3LA0KICAgID4gZXhwcmVzc2luZyB0aGF0IGEgZmVhdHVyZS1wZXItbGVhZiBp
cyBtb3N0IGxpa2VseSB0aGUgd3JvbmcgYXBwcm9hY2g/DQogICAgDQogICAgVGhpcyBpcyBkaWZm
aWN1bHQgdG8gZGVzY3JpYmUuIFBlcmhhcHMgc29tZXRoaW5nIGxpa2UgdGhpcyBpcyBhDQogICAg
cmVhc29uYWJseSBzbWFsbCBjaGFuZ2UgdG8gdGhlIGV4aXN0aW5nIHRleHQgKHdoaWNoIG9ubHkg
dGFsa3MgYWJvdXQNCiAgICB0b28gYmlnIGZlYXR1cmVzIGJ1dCBub3QgYWJvdXQgdG9vIHNtYWxs
IGZlYXR1cmVzKS4NCiAgICANCiAgICBPTEQNCiAgICANCiAgICAgICBUaGUgWUFORyAiZmVhdHVy
ZSIgc3RhdGVtZW50IGlzIHVzZWQgdG8gZGVmaW5lIGEgbGFiZWwgZm9yIGEgc2V0IG9mDQogICAg
ICAgb3B0aW9uYWwgZnVuY3Rpb25hbGl0eSB3aXRoaW4gYSBtb2R1bGUuICBUaGUgImlmLWZlYXR1
cmUiIHN0YXRlbWVudA0KICAgICAgIGlzIHVzZWQgaW4gdGhlIFlBTkcgc3RhdGVtZW50cyBhc3Nv
Y2lhdGVkIHdpdGggYSBmZWF0dXJlLg0KICAgIA0KICAgICAgIFRoZSBzZXQgb2YgWUFORyBmZWF0
dXJlcyBhdmFpbGFibGUgaW4gYSBtb2R1bGUgc2hvdWxkIGJlIGNvbnNpZGVyZWQNCiAgICAgICBj
YXJlZnVsbHkuICBUaGUgZGVzY3JpcHRpb24tc3RtdCB3aXRoaW4gYSBmZWF0dXJlLXN0bXQgTVVT
VCBzcGVjaWZ5DQogICAgICAgYW55IGludGVyYWN0aW9ucyB3aXRoIG90aGVyIGZlYXR1cmVzLg0K
ICAgIA0KICAgICAgIElmIHRoZXJlIGlzIGEgbGFyZ2Ugc2V0IG9mIG9iamVjdHMuLi4NCiAgICAN
CiAgICBORVcNCiAgICANCiAgICAgICBUaGUgWUFORyAiZmVhdHVyZSIgc3RhdGVtZW50IGlzIHVz
ZWQgdG8gZGVmaW5lIGEgbGFiZWwgZm9yIGEgc2V0IG9mDQogICAgICAgb3B0aW9uYWwgZnVuY3Rp
b25hbGl0eSB3aXRoaW4gYSBtb2R1bGUuICBUaGUgImlmLWZlYXR1cmUiIHN0YXRlbWVudA0KICAg
ICAgIGlzIHVzZWQgaW4gdGhlIFlBTkcgc3RhdGVtZW50cyBhc3NvY2lhdGVkIHdpdGggYSBmZWF0
dXJlLiAgVGhlDQogICAgICAgZGVzY3JpcHRpb24tc3RtdCB3aXRoaW4gYSBmZWF0dXJlLXN0bXQg
TVVTVCBzcGVjaWZ5IGFueQ0KICAgICAgIGludGVyYWN0aW9ucyB3aXRoIG90aGVyIGZlYXR1cmVz
Lg0KICAgIA0KICAgICAgIFRoZSBzZXQgb2YgWUFORyBmZWF0dXJlcyBkZWZpbmVkIGluIGEgbW9k
dWxlIHNob3VsZCBiZSBjb25zaWRlcmVkDQogICAgICAgY2FyZWZ1bGx5LiBWZXJ5IGZpbmUgZ3Jh
bnVsYXIgZmVhdHVyZXMgaW5jcmVhc2UgaW50ZXJvcGVyYWJpbGl0eQ0KICAgICAgIGNvbXBsZXhp
dHkgYW5kIHNob3VsZCBiZSBhdm9pZGVkLiBBIGxpa2VseSBtaXN1c2Ugb2YgdGhlIGZlYXR1cmUN
CiAgICAgICBtZWNoYW5pc20gaXMgdGhlIHRhZ2dpbmcgb2YgaW5kaXZpZHVhbCBsZWFmcyAoZS5n
LiwgY291bnRlcnMpIHdpdGgNCiAgICAgICBzZXBhcmF0ZSBmZWF0dXJlcy4NCiAgICANCiAgICAg
ICBJZiB0aGVyZSBpcyBhIGxhcmdlIHNldCBvZiBvYmplY3RzLi4uDQogICAgDQogICAgL2pzDQog
ICAgDQogICAgLS0gDQogICAgSnVlcmdlbiBTY2hvZW53YWVsZGVyICAgICAgICAgICBKYWNvYnMg
VW5pdmVyc2l0eSBCcmVtZW4gZ0dtYkgNCiAgICBQaG9uZTogKzQ5IDQyMSAyMDAgMzU4NyAgICAg
ICAgIENhbXB1cyBSaW5nIDEgfCAyODc1OSBCcmVtZW4gfCBHZXJtYW55DQogICAgRmF4OiAgICs0
OSA0MjEgMjAwIDMxMDMgICAgICAgICA8aHR0cHM6Ly93d3cuamFjb2JzLXVuaXZlcnNpdHkuZGUv
Pg0KICAgIA0KDQo=


From nobody Tue Jan 16 17:13:34 2018
Return-Path: <zhang.zheng@zte.com.cn>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7762212D84F; Tue, 16 Jan 2018 17:13:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level: 
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 LIkbwnwZ_c93; Tue, 16 Jan 2018 17:13:29 -0800 (PST)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 A501112D88F; Tue, 16 Jan 2018 17:13:24 -0800 (PST)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id F2B944EB12791CDB457C; Wed, 17 Jan 2018 09:13:22 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Forcepoint Email with ESMTPS id E043F13BD1FBC47E6A60; Wed, 17 Jan 2018 09:13:22 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse01.zte.com.cn with SMTP id w0H1DFL8035268; Wed, 17 Jan 2018 09:13:15 +0800 (GMT-8) (envelope-from zhang.zheng@zte.com.cn)
Received: from mapi (njxapp04[null]) by mapi (Zmail) with MAPI id mid203; Wed, 17 Jan 2018 09:13:15 +0800 (CST)
Date: Wed, 17 Jan 2018 09:13:15 +0800 (CST)
X-Zmail-TransId: 2afc5a5ea32b14f-b3f9c
X-Mailer: Zmail v1.0
Message-ID: <201801170913159333192@zte.com.cn>
In-Reply-To: <151577977482.18634.14740634433873272656@ietfa.amsl.com>
References: 151577977482.18634.14740634433873272656@ietfa.amsl.com
Mime-Version: 1.0
From: <zhang.zheng@zte.com.cn>
To: <rrahman@cisco.com>
Cc: <yang-doctors@ietf.org>, <draft-ietf-pim-msdp-yang.all@ietf.org>, <pim@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse01.zte.com.cn w0H1DFL8035268
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/5nLIB9sqtqhULwX5f7mnowvUJjs>
Subject: Re: [yang-doctors]  =?utf-8?q?Yangdoctors_early_review_of_draft-ietf-?= =?utf-8?q?pim-msdp-yang-01?=
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2018 01:13:33 -0000

--=====_001_next=====
Content-Type: multipart/related;
	boundary="=====_002_next====="


--=====_002_next=====
Content-Type: multipart/alternative;
	boundary="=====_003_next====="


--=====_003_next=====
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64 

SGkgUmVzaGFkLA0KDQoNCg0KDQoNCg0KDQpUaGFuayB5b3UgdmVyeSBtdWNoIGZvciB5b3VyIGVh
cmx5IHJldmlldy4gV2Ugd2lsbCBkaXNjdXNzIGhvdyB0byBtb2RpZnkgaXQgYWNjb3JkaW5nIHRv
IHlvdXIgc3VnZ2VzdGlvbi4NCg0KDQoNCg0KDQoNClRoYW5rcywNCg0KDQpTYW5keQ0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCuWOn+Wni+mCruS7tg0KDQoNCg0K5Y+R5Lu25Lq677yaIDxycmFobWFu
QGNpc2NvLmNvbT47DQrmlLbku7bkurrvvJogPHlhbmctZG9jdG9yc0BpZXRmLm9yZz47DQrmioTp
gIHkurrvvJogPGRyYWZ0LWlldGYtcGltLW1zZHAteWFuZy5hbGxAaWV0Zi5vcmc+OyA8cGltQGll
dGYub3JnPjsNCuaXpSDmnJ8g77yaMjAxOOW5tDAx5pyIMTPml6UgMDE6NTQNCuS4uyDpopgg77ya
WWFuZ2RvY3RvcnMgZWFybHkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcGltLW1zZHAteWFuZy0wMQ0K
DQoNClJldmlld2VyOiBSZXNoYWQgUmFobWFuDQpSZXZpZXcgcmVzdWx0OiBPbiB0aGUgUmlnaHQg
VHJhY2sNCg0KWUFORyBEb2N0b3IgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcGltLW1zZHAteWFuZy0w
MSBieSBSZXNoYWQgUmFobWFuDQoNCjEgbW9kdWxlIGluIHRoaXMgZHJhZnQ6DQotIGlldGYtbXNk
cEAyMDE3LTA4LTMwLnlhbmcNCg0KTm8gWUFORyB2YWxpZGF0aW9uIGVycm9ycyBvciB3YXJuaW5n
cyAoZnJvbSBweWFuZyAxLjcuMyBhbmQgeWFuZ2xpbnQgMC4xNC4uNTMpLg0KDQowIGV4YW1wbGVz
IGFyZSBwcm92aWRlZCBpbiB0aGlzIGRyYWZ0IChzZWN0aW9uIDMuMTIgb2YNCmRyYWZ0LWlldGYt
bmV0bW9kLXJmYzYwODdiaXMtMTUpDQoNCk1vZHVsZSBpZXRmLW1zZHBAMjAxNy0wOC0zMC55YW5n
Og0KLSBUb28gbWFueSBmZWF0dXJlcyAoMTcpISBFdmVyeSBwaWVjZSBvZiBjb25maWcgaGFzIGFu
IGlmLWZlYXR1cmUgc3RhdGVtZW50Lg0KU29tZSBvZiB0aGUgY29uZmlncyAodGltZXJzPykgc2hv
dWxkIGJlIHBhcnQgb2YgbW9zdC9iYXNpYyBpbXBsZW1lbnRhdGlvbnMsIGZvcg0Kb3RoZXIgY29u
ZmlnIChlLmcuIGF1dGhlbnRpY2F0aW9uKSBJIGNhbiBzZWUgd2h5IGEgZmVhdHVyZSB3b3VsZCBi
ZSB1c2VkLiAtDQrigJxpbXBvcnQgaWV0Zi15YW5nLXR5cGVz4oCdIHNob3VsZCBoYXZlIGEgcmVm
ZXJlbmNlIHRvIFJGQzY5OTEgKHNlZSBzZWN0aW9uIDQuNyBvZg0KcmZjNjA4N2Jpcy0xNSkgLSDi
gJxpbXBvcnQgaWV0Zi1pbmV0LXR5cGVz4oCdIHNob3VsZCBoYXZlIGEgcmVmZXJlbmNlIHRvIFJG
QzY5OTEgLQ0K4oCcaW1wb3J0IGlldGYtcm91dGluZ+KAnSBzaG91bGQgaGF2ZSBhIHJlZmVyZW5j
ZSB0byBSRkM4MDIyIC0g4oCcaW1wb3J0DQppZXRmLWludGVyZmFjZXPigJ0gc2hvdWxkIGhhdmUg
YSByZWZlcmVuY2UgdG8gUkZDNzIyMyAtICJpbXBvcnQgaWV0Zi1pcCIgc2hvdWxkDQpoYXZlIGEg
cmVmZXJlbmNlIHRvIFJGQzcyNzcgLSAiaW1wb3J0IGlldGYta2V5LWNoYWluIiBzaG91bGQgaGF2
ZSBhIHJlZmVyZW5jZQ0KdG8gUkZDODE3NyAtIG9yZ2FuaXphdGlvbiBzLyIuLi5QSU0oIFByb3Rv
Y29scyBmb3IgSVAgTXVsdGljYXN0ICkgV29ya2luZw0KR3JvdXAiLyIuLi5QSU0gKFByb3RvY29s
cyBmb3IgSVAgTXVsdGljYXN0KSBXb3JraW5nIEdyb3VwIj8gLSBSZW1vdmUgV0cgQ2hhaXJzDQpm
cm9tIGNvbnRhY3QgaW5mb3JtYXRpb24gYXMgcGVyIEFwcGVuZGl4IEMgb2YgcmZjNjA4N2Jpcy0x
NSAtIE5vIGNvcHlyaWdodCBpbg0KdGhlIG1vZHVsZSBkZXNjcmlwdGlvbiwgc2VlIEFwcGVuZGl4
IG9mIDYwODdiaXMtMTUgZm9yIGEgbW9kdWxlIGRlc2NyaXB0aW9uDQpleGFtcGxlIC0gTW9kdWxl
IGRlc2NyaXB0aW9uIG11c3QgY29udGFpbiByZWZlcmVuY2UgdG8gUkZDLCBzZWUgQXBwZW5kaXgg
QyBvZg0KcmZjNjA4N2Jpcy0xNSAtIGdyb3VwaW5nIGF1dGhlbnRpY2F0aW9uLWNvbnRhaW5lci4g
a2V5LWNoYWluIGFuZCBwYXNzd29yZCBib3RoDQp1c2UgaWYtZmVhdHVyZSBwZWVyLWtleS1jaGFp
bi4gLSBncm91cGluZyBjb25uZWN0LXNvdXJjZS4gVGhlIG5hbWUgaXMgbm90IHZlcnkNCmRlc2Ny
aXB0aXZlLiBTaG91bGQgdGhpcyBiZSBzb21ldGhpbmcgYWxvbmcgdGhlIGxpbmVzIG9mIHRjcC1j
b25uZWN0aW9uLXNvdXJjZT8NCi0gZ3JvdXBpbmcgZ2xvYmFsLXN0YXRlLWF0dHJpYnV0ZXMgaGFz
IG5vdGhpbmcgLSBTb21lIG9mIHRoZSBkZXNjcmlwdGlvbnMgYXJlDQpwcmV0dHkgdGVyc2UuIGUu
Zy4gZm9yIHJwZi1wZWVyIGl0IHNheXMgIlJQRiBwZWVyLiIuIEluIGEgY2FzZSBsaWtlIHRoaXMN
CmNvbnNpZGVyIGFkZGluZyBtb3JlIGRlc2NyaXB0aXZlIHRleHQgb3IgYSByZWZlcmVuY2UgdG8g
dGhlIHByb3BlciBzZWN0aW9uIGluDQpSRkMzNjE4IC0gcGVlci1hcyAoQXV0b25vbW91cyBTeXN0
ZW0gTnVtYmVyKSBpcyBkZWZpbmVkIGFzIHR5cGUgc3RyaW5nLCBzaG91bGQNCmJlIG9mIHR5cGUg
YXMtbnVtYmVyIGluIGlldGYtaW5ldC10eXBlcz8gLSBOb3Qgc3VyZSB3aHkgcGVlci1hcyBpcyBu
ZWVkZWQuLg0KRG9uJ3Qgc2VlIGl0IGluIFJGQzM2MTguIC0ga2VlcGFsaXZlLWludGVydmFsIGRl
cGVuZHMgb24gaG9sZHRpbWUtaW50ZXJ2YWwuDQpUaGVyZSBzaG91bGQgYmUgImlmLWZlYXR1cmUg
cGVlci10aW1lci1ob2xkdGltZSIgdW5kZXIgbGVhZiBrZWVwYWxpdmUtaW50ZXJ2YWwNCm9yIGNo
YW5nZSB0aGUgbXVzdCBzdGF0ZW1lbnQgdG8gKGFzc3VtaW5nIHdlIGtlZXAgdGhlIDIgZmVhdHVy
ZXMpOg0KICBtdXN0ICIobm90IC4uL2hvbGR0aW1lLWludGVydmFsKSBvciAoLiA+IDEgYW5kIC4g
PCAuLi9ob2xkdGltZS1pbnRlcnZhbCkiLg0KLSBsZWFmIHVwLXRpbWU6IHMvc2EgY2FjaGUvU0Eg
Y2FjaGUvDQotIGxlYWYgdXAtdGltZSwgd2hhdCdzIG1lYW50IGJ5ICJ1cCB0aW1lIiBpbiB0aGUg
ZGVzY3JpcHRpb24/IElzIGl0IHRpbWUgaXQncw0KYmVlbiBjcmVhdGVkPyAtIGRlc2NyaXB0aW9u
IGZvciBsZWFmIGV4cGlyZSBzZWVtcyB3cm9uZy4gLSBsZWFmDQpwZWVyLWxlYXJuZWQtZnJvbSwg
Y2hhbmdlIGRlc2NyaXB0aW9uIGZyb20gIlRoZSBhZGRyZXNzIG9mIHBlZXIgdGhhdCB3ZSBsZWFy
bmVkDQp0aGlzIFNBIGZyb20gLiIgdG8gIlRoZSBhZGRyZXNzIG9mIHRoZSBwZWVyIHRoYXQgd2Ug
bGVhcm5lZCB0aGlzIFNBIGZyb20uIiAtDQpHcm91cGluZ3MgYXJlIHVzZWQgZm9yIGRhdGEgd2hp
Y2ggaXMgdXNlZCBvbmx5IG9uY2UuIElzIHRoaXMgZG9uZSBvbiBwdXJwb3NlIG9yDQp3YXMgdGhl
IGludGVudGlvbiB0byB1c2UgdGhvc2UgZ3JvdXBpbmdzIG1vcmUgdGhhbiBvbmNlPyAtIGF1Z21l
bnQgb2YNCmNvbnRyb2wtcGxhbmUtcHJvdG9jb2xzIGlzIGluY29ycmVjdC4gVGhlcmUgc2hvdWxk
IGJlIGFuIGlkZW50aXR5IG1zZHAgd2l0aA0KYmFzZSAicnQ6cm91dGluZy1wcm90b2NvbCIgYW5k
IHRoZW4gYXVnbWVudA0KIi9ydDpyb3V0aW5nL3J0OmNvbnRyb2wtcGxhbmUtcHJvdG9jb2xzL3J0
OmNvbnRyb2wtcGxhbmUtcHJvdG9jb2wiIHdpdGggYSB3aGVuDQpzdGF0ZW1lbnQuIFRha2UgYSBs
b29rIGF0IE9TUEYgWUFORyBmb3IgYW4gZXhhbXBsZS4gLSBSUEMgbGVhZiBncm91cCwgSSB0aG91
Z2h0DQp3ZSBoYWQgYSB0eXBlIGZvciBJUCBtdWx0aWNhc3QgYWRkcmVzcz8gSWYgbm90LCBpdCBz
aG91bGQgYmUgZG9uZT8gLQ0Kcy9tc2RwL01TRFAvIC0gSW4gcnBjIG1zZHAtY2xlYXItcGVlciwg
cy9DbGVhcnMgdGhlIHNlc3Npb24gdG8gdGhlIHBlZXIuL0NsZWFycw0KdGhlIFRDUCBjb25uZWN0
aW9uIHRvIHRoZSBwZWVyLi8gLSBJbiBycGMgbXNkcC1jbGVhci1zYS1jYWNoZSwgd2h5IGhhdmUg
dGhlDQplbnVtICcqJyBmb3Igc291cmNlLWFkZHIuIENhbid0IHRoZSBzYW1lIHRlY2huaXF1ZSBh
cyBmb3IgcGVlci1hZGRyZXNzIGJlIHVzZWQ/DQotIG1zZHAgcHJlZml4IG5vdCBuZWVkZWQgaW4g
cnBjIG5hbWVzIC0gTVNEUCBwZWVycyBhcmUgY29uZmlndXJlZCBpbiBhDQptZXNoLWdyb3VwLCBk
aWQgdGhlIGF1dGhvcnMgY29uc2lkZXIgYWRkaW5nIHN0YXRlIHBlciBtZXNoLWdyb3VwLCBlLmcu
IGFsbCB0aGUNCnBlZXJzIGluIGEgcGFydGljdWxhciBtZXNoLWdyb3VwPw0KDQpHZW5lcmFsOg0K
LSBQZXIgQXBwZW5kaXggQiBvZiByZmM2MDg3YmlzLTE1OiAidGhhdCBhbGwgWUFORyBtb2R1bGVz
IGNvbnRhaW5pbmcNCmltcG9ydGVkIGl0ZW1zIGFyZSBjaXRlZCBhcyBub3JtYXRpdmUgcmVmZXJl
bmNlIi4gU28gUkZDcyA2OTkxLCA3MjIzLA0KNzI3NywgODAyMiBhbmQgODE3NyBzaG91bGQgYmUg
aW5jbHVkZWQgaW4gdGhlIG5vcm1hdGl2ZSByZWZlcmVuY2UNCnNlY3Rpb24uDQotIFNlY3Rpb24g
MyAidGhlIGlycmVsZXZhbnQgaW5mb3JtYXRpb24iLCBhZGQgYSByZWZlcmVuY2UvZXhwbGFuYXRp
b24gZm9yIHdoYXQNCnRoZSBpcnJlbGV2YW50IGluZm9ybWF0aW9uIGlzLiBzL3RoZSBpcnJlbGV2
YW50IGluZm9ybWF0aW9uL2lycmVsZXZhbnQNCmluZm9ybWF0aW9uLz8gLSBTZWN0aW9uIDUgc2hv
dWxkIGdpdmUgYSBicmllZiBkZXNjcmlwdGlvbiBvZiB3aGF0IHRoZSBSUENzIGRvLg0KLSBTZWN0
aW9uIDYgYW55IHBsYW5zIGZvciBub3RpZmljYXRpb25zPyBJZiBub3QsIGp1c3Qgc2F5IHNvLiAt
IE5lZWQgU2VjdXJpdHkNCkNvbnNpZGVyYXRpb25zLCBzZWUgc2VjdGlvbnMgMy43IGFuZCA2IG9m
IHJmYzYwODdiaXMtMTUgLSBOZWVkIElBTkENCkNvbnNpZGVyYXRpb25zLCBzZWUgc2VjdGlvbiAz
Ljggb2YgcmZjNjA4N2Jpcy0xNSAtIE5lZWQgbGljZW5zZSBpbiBZQU5HIG1vZHVsZSwNCnNlZSBh
cHBlbmRpeCBCIG9mIHJmYzYwODdiaXMtMTUNCg0KTml0czoNCi0gU2VjdGlvbiA0IHMvU2EtY2Fj
aGUvU0EtY2FjaGUv


--=====_003_next=====
Content-Type: text/html ;
	charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iemNvbnRlbnRSb3ciPjxwIHN0eWxlPSJmb250LXNpemU6MTRweDtmb250LWZh
bWlseTphcmlhbDsiPkhpIFJlc2hhZCw8YnI+PC9wPjxwIHN0eWxlPSJmb250LXNpemU6MTRweDtm
b250LWZhbWlseTphcmlhbDsiPjxicj48L3A+PHAgc3R5bGU9ImZvbnQtc2l6ZToxNHB4O2ZvbnQt
ZmFtaWx5OmFyaWFsOyI+VGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgeW91ciBlYXJseSByZXZpZXcu
IFdlIHdpbGwgZGlzY3VzcyBob3cgdG8gbW9kaWZ5IGl0IGFjY29yZGluZyB0byB5b3VyIHN1Z2dl
c3Rpb24uPC9wPjxwIHN0eWxlPSJmb250LXNpemU6MTRweDtmb250LWZhbWlseTphcmlhbDsiPjxi
cj48L3A+PHAgc3R5bGU9ImZvbnQtc2l6ZToxNHB4O2ZvbnQtZmFtaWx5OmFyaWFsOyI+VGhhbmtz
LDwvcD48cCBzdHlsZT0iZm9udC1zaXplOjE0cHg7Zm9udC1mYW1pbHk6YXJpYWw7Ij5TYW5keTwv
cD48cCBzdHlsZT0iZm9udC1zaXplOjE0cHg7Zm9udC1mYW1pbHk6YXJpYWw7Ij48YnI+PC9wPjxk
aXYgY2xhc3M9InpNYWlsU2lnbiI+PC9kaXY+PGRpdiBjbGFzcz0iek1haWxGcm9tIj48L2Rpdj48
ZGl2PjxkaXYgY2xhc3M9InpoaXN0b3J5Um93IiBzdHlsZT0iZGlzcGxheTpibG9jayI+PGRpdiBj
bGFzcz0iemhpc3RvcnlEZXMiIHN0eWxlPSJ3aWR0aDogMTAwJTsgaGVpZ2h0OiAyOHB4OyBsaW5l
LWhlaWdodDogMjhweDsgYmFja2dyb3VuZC1jb2xvcjogI0UwRTVFOTsgY29sb3I6ICMxMzg4RkY7
IHRleHQtYWxpZ246IGNlbnRlcjsiIGxhbmd1YWdlLWRhdGE9Ikhpc3RvcnlPcmdUeHQiPuWOn+Wn
i+mCruS7tjwvZGl2PjxkaXYgaWQ9Inp3cml0ZUhpc3RvcnlDb250YWluZXIiPjxkaXYgY2xhc3M9
ImNvbnRyb2wtZ3JvdXAgemhpc3RvcnlQYW5lbCI+PGRpdiBjbGFzcz0iemhpc3RvcnlIZWFkZXIi
IHN0eWxlPSJwYWRkaW5nOiA4cHg7IGJhY2tncm91bmQtY29sb3I6ICNGNUY2Rjg7Ij48ZGl2Pjxz
dHJvbmcgbGFuZ3VhZ2UtZGF0YT0iSGlzdG9yeVNlbmRlclR4dCI+5Y+R5Lu25Lq677yaPC9zdHJv
bmc+PHNwYW4gY2xhc3M9InpyZWFkVXNlck5hbWUiPiAmbHQ7cnJhaG1hbkBjaXNjby5jb20mZ3Q7
Ozwvc3Bhbj48L2Rpdj48ZGl2PjxzdHJvbmcgbGFuZ3VhZ2UtZGF0YT0iSGlzdG9yeVRPVHh0Ij7m
lLbku7bkurrvvJo8L3N0cm9uZz48c3BhbiBjbGFzcz0ienJlYWRVc2VyTmFtZSIgc3R5bGU9ImRp
c3BsYXk6IGlubGluZTsiPiAmbHQ7eWFuZy1kb2N0b3JzQGlldGYub3JnJmd0Ozs8L3NwYW4+PC9k
aXY+PGRpdj48c3Ryb25nIGxhbmd1YWdlLWRhdGE9Ikhpc3RvcnlDQ1R4dCI+5oqE6YCB5Lq677ya
PC9zdHJvbmc+PHNwYW4gY2xhc3M9InpyZWFkVXNlck5hbWUiIHN0eWxlPSJkaXNwbGF5OiBpbmxp
bmU7Ij4gJmx0O2RyYWZ0LWlldGYtcGltLW1zZHAteWFuZy5hbGxAaWV0Zi5vcmcmZ3Q7Ozwvc3Bh
bj48c3BhbiBjbGFzcz0ienJlYWRVc2VyTmFtZSIgc3R5bGU9ImRpc3BsYXk6IGlubGluZTsiPiAm
bHQ7cGltQGlldGYub3JnJmd0Ozs8L3NwYW4+PC9kaXY+PGRpdj48c3Ryb25nIGxhbmd1YWdlLWRh
dGE9Ikhpc3RvcnlEYXRlVHh0Ij7ml6Ug5pyfIO+8mjwvc3Ryb25nPjxzcGFuIGNsYXNzPSIiPjIw
MTjlubQwMeaciDEz5pelIDAxOjU0PC9zcGFuPjwvZGl2PjxkaXY+PHN0cm9uZyBsYW5ndWFnZS1k
YXRhPSJIaXN0b3J5U3ViamVjdFR4dCI+5Li7IOmimCDvvJo8L3N0cm9uZz48c3BhbiBjbGFzcz0i
enJlYWRUaXRsZSI+PHN0cm9uZz5ZYW5nZG9jdG9ycyBlYXJseSByZXZpZXcgb2YgZHJhZnQtaWV0
Zi1waW0tbXNkcC15YW5nLTAxPC9zdHJvbmc+PC9zcGFuPjwvZGl2PjwvZGl2PjxkaXYgY2xhc3M9
InpoaXN0b3J5Q29udGVudCI+PGRpdj5SZXZpZXdlcjombmJzcDtSZXNoYWQmbmJzcDtSYWhtYW48
YnI+UmV2aWV3Jm5ic3A7cmVzdWx0OiZuYnNwO09uJm5ic3A7dGhlJm5ic3A7UmlnaHQmbmJzcDtU
cmFjazxicj48YnI+WUFORyZuYnNwO0RvY3RvciZuYnNwO3JldmlldyZuYnNwO29mJm5ic3A7ZHJh
ZnQtaWV0Zi1waW0tbXNkcC15YW5nLTAxJm5ic3A7YnkmbmJzcDtSZXNoYWQmbmJzcDtSYWhtYW48
YnI+PGJyPjEmbmJzcDttb2R1bGUmbmJzcDtpbiZuYnNwO3RoaXMmbmJzcDtkcmFmdDo8YnI+LSZu
YnNwO2lldGYtbXNkcEAyMDE3LTA4LTMwLnlhbmc8YnI+PGJyPk5vJm5ic3A7WUFORyZuYnNwO3Zh
bGlkYXRpb24mbmJzcDtlcnJvcnMmbmJzcDtvciZuYnNwO3dhcm5pbmdzJm5ic3A7KGZyb20mbmJz
cDtweWFuZyZuYnNwOzEuNy4zJm5ic3A7YW5kJm5ic3A7eWFuZ2xpbnQmbmJzcDswLjE0Li41Myku
PGJyPjxicj4wJm5ic3A7ZXhhbXBsZXMmbmJzcDthcmUmbmJzcDtwcm92aWRlZCZuYnNwO2luJm5i
c3A7dGhpcyZuYnNwO2RyYWZ0Jm5ic3A7KHNlY3Rpb24mbmJzcDszLjEyJm5ic3A7b2Y8YnI+ZHJh
ZnQtaWV0Zi1uZXRtb2QtcmZjNjA4N2Jpcy0xNSk8YnI+PGJyPk1vZHVsZSZuYnNwO2lldGYtbXNk
cEAyMDE3LTA4LTMwLnlhbmc6PGJyPi0mbmJzcDtUb28mbmJzcDttYW55Jm5ic3A7ZmVhdHVyZXMm
bmJzcDsoMTcpISZuYnNwO0V2ZXJ5Jm5ic3A7cGllY2UmbmJzcDtvZiZuYnNwO2NvbmZpZyZuYnNw
O2hhcyZuYnNwO2FuJm5ic3A7aWYtZmVhdHVyZSZuYnNwO3N0YXRlbWVudC48YnI+U29tZSZuYnNw
O29mJm5ic3A7dGhlJm5ic3A7Y29uZmlncyZuYnNwOyh0aW1lcnM/KSZuYnNwO3Nob3VsZCZuYnNw
O2JlJm5ic3A7cGFydCZuYnNwO29mJm5ic3A7bW9zdC9iYXNpYyZuYnNwO2ltcGxlbWVudGF0aW9u
cywmbmJzcDtmb3I8YnI+b3RoZXImbmJzcDtjb25maWcmbmJzcDsoZS5nLiZuYnNwO2F1dGhlbnRp
Y2F0aW9uKSZuYnNwO0kmbmJzcDtjYW4mbmJzcDtzZWUmbmJzcDt3aHkmbmJzcDthJm5ic3A7ZmVh
dHVyZSZuYnNwO3dvdWxkJm5ic3A7YmUmbmJzcDt1c2VkLiZuYnNwOy08YnI+4oCcaW1wb3J0Jm5i
c3A7aWV0Zi15YW5nLXR5cGVz4oCdJm5ic3A7c2hvdWxkJm5ic3A7aGF2ZSZuYnNwO2EmbmJzcDty
ZWZlcmVuY2UmbmJzcDt0byZuYnNwO1JGQzY5OTEmbmJzcDsoc2VlJm5ic3A7c2VjdGlvbiZuYnNw
OzQuNyZuYnNwO29mPGJyPnJmYzYwODdiaXMtMTUpJm5ic3A7LSZuYnNwO+KAnGltcG9ydCZuYnNw
O2lldGYtaW5ldC10eXBlc+KAnSZuYnNwO3Nob3VsZCZuYnNwO2hhdmUmbmJzcDthJm5ic3A7cmVm
ZXJlbmNlJm5ic3A7dG8mbmJzcDtSRkM2OTkxJm5ic3A7LTxicj7igJxpbXBvcnQmbmJzcDtpZXRm
LXJvdXRpbmfigJ0mbmJzcDtzaG91bGQmbmJzcDtoYXZlJm5ic3A7YSZuYnNwO3JlZmVyZW5jZSZu
YnNwO3RvJm5ic3A7UkZDODAyMiZuYnNwOy0mbmJzcDvigJxpbXBvcnQ8YnI+aWV0Zi1pbnRlcmZh
Y2Vz4oCdJm5ic3A7c2hvdWxkJm5ic3A7aGF2ZSZuYnNwO2EmbmJzcDtyZWZlcmVuY2UmbmJzcDt0
byZuYnNwO1JGQzcyMjMmbmJzcDstJm5ic3A7ImltcG9ydCZuYnNwO2lldGYtaXAiJm5ic3A7c2hv
dWxkPGJyPmhhdmUmbmJzcDthJm5ic3A7cmVmZXJlbmNlJm5ic3A7dG8mbmJzcDtSRkM3Mjc3Jm5i
c3A7LSZuYnNwOyJpbXBvcnQmbmJzcDtpZXRmLWtleS1jaGFpbiImbmJzcDtzaG91bGQmbmJzcDto
YXZlJm5ic3A7YSZuYnNwO3JlZmVyZW5jZTxicj50byZuYnNwO1JGQzgxNzcmbmJzcDstJm5ic3A7
b3JnYW5pemF0aW9uJm5ic3A7cy8iLi4uUElNKCZuYnNwO1Byb3RvY29scyZuYnNwO2ZvciZuYnNw
O0lQJm5ic3A7TXVsdGljYXN0Jm5ic3A7KSZuYnNwO1dvcmtpbmc8YnI+R3JvdXAiLyIuLi5QSU0m
bmJzcDsoUHJvdG9jb2xzJm5ic3A7Zm9yJm5ic3A7SVAmbmJzcDtNdWx0aWNhc3QpJm5ic3A7V29y
a2luZyZuYnNwO0dyb3VwIj8mbmJzcDstJm5ic3A7UmVtb3ZlJm5ic3A7V0cmbmJzcDtDaGFpcnM8
YnI+ZnJvbSZuYnNwO2NvbnRhY3QmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2FzJm5ic3A7cGVyJm5i
c3A7QXBwZW5kaXgmbmJzcDtDJm5ic3A7b2YmbmJzcDtyZmM2MDg3YmlzLTE1Jm5ic3A7LSZuYnNw
O05vJm5ic3A7Y29weXJpZ2h0Jm5ic3A7aW48YnI+dGhlJm5ic3A7bW9kdWxlJm5ic3A7ZGVzY3Jp
cHRpb24sJm5ic3A7c2VlJm5ic3A7QXBwZW5kaXgmbmJzcDtvZiZuYnNwOzYwODdiaXMtMTUmbmJz
cDtmb3ImbmJzcDthJm5ic3A7bW9kdWxlJm5ic3A7ZGVzY3JpcHRpb248YnI+ZXhhbXBsZSZuYnNw
Oy0mbmJzcDtNb2R1bGUmbmJzcDtkZXNjcmlwdGlvbiZuYnNwO211c3QmbmJzcDtjb250YWluJm5i
c3A7cmVmZXJlbmNlJm5ic3A7dG8mbmJzcDtSRkMsJm5ic3A7c2VlJm5ic3A7QXBwZW5kaXgmbmJz
cDtDJm5ic3A7b2Y8YnI+cmZjNjA4N2Jpcy0xNSZuYnNwOy0mbmJzcDtncm91cGluZyZuYnNwO2F1
dGhlbnRpY2F0aW9uLWNvbnRhaW5lci4mbmJzcDtrZXktY2hhaW4mbmJzcDthbmQmbmJzcDtwYXNz
d29yZCZuYnNwO2JvdGg8YnI+dXNlJm5ic3A7aWYtZmVhdHVyZSZuYnNwO3BlZXIta2V5LWNoYWlu
LiZuYnNwOy0mbmJzcDtncm91cGluZyZuYnNwO2Nvbm5lY3Qtc291cmNlLiZuYnNwO1RoZSZuYnNw
O25hbWUmbmJzcDtpcyZuYnNwO25vdCZuYnNwO3Zlcnk8YnI+ZGVzY3JpcHRpdmUuJm5ic3A7U2hv
dWxkJm5ic3A7dGhpcyZuYnNwO2JlJm5ic3A7c29tZXRoaW5nJm5ic3A7YWxvbmcmbmJzcDt0aGUm
bmJzcDtsaW5lcyZuYnNwO29mJm5ic3A7dGNwLWNvbm5lY3Rpb24tc291cmNlPzxicj4tJm5ic3A7
Z3JvdXBpbmcmbmJzcDtnbG9iYWwtc3RhdGUtYXR0cmlidXRlcyZuYnNwO2hhcyZuYnNwO25vdGhp
bmcmbmJzcDstJm5ic3A7U29tZSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7ZGVzY3JpcHRpb25zJm5i
c3A7YXJlPGJyPnByZXR0eSZuYnNwO3RlcnNlLiZuYnNwO2UuZy4mbmJzcDtmb3ImbmJzcDtycGYt
cGVlciZuYnNwO2l0Jm5ic3A7c2F5cyZuYnNwOyJSUEYmbmJzcDtwZWVyLiIuJm5ic3A7SW4mbmJz
cDthJm5ic3A7Y2FzZSZuYnNwO2xpa2UmbmJzcDt0aGlzPGJyPmNvbnNpZGVyJm5ic3A7YWRkaW5n
Jm5ic3A7bW9yZSZuYnNwO2Rlc2NyaXB0aXZlJm5ic3A7dGV4dCZuYnNwO29yJm5ic3A7YSZuYnNw
O3JlZmVyZW5jZSZuYnNwO3RvJm5ic3A7dGhlJm5ic3A7cHJvcGVyJm5ic3A7c2VjdGlvbiZuYnNw
O2luPGJyPlJGQzM2MTgmbmJzcDstJm5ic3A7cGVlci1hcyZuYnNwOyhBdXRvbm9tb3VzJm5ic3A7
U3lzdGVtJm5ic3A7TnVtYmVyKSZuYnNwO2lzJm5ic3A7ZGVmaW5lZCZuYnNwO2FzJm5ic3A7dHlw
ZSZuYnNwO3N0cmluZywmbmJzcDtzaG91bGQ8YnI+YmUmbmJzcDtvZiZuYnNwO3R5cGUmbmJzcDth
cy1udW1iZXImbmJzcDtpbiZuYnNwO2lldGYtaW5ldC10eXBlcz8mbmJzcDstJm5ic3A7Tm90Jm5i
c3A7c3VyZSZuYnNwO3doeSZuYnNwO3BlZXItYXMmbmJzcDtpcyZuYnNwO25lZWRlZC4uPGJyPkRv
bid0Jm5ic3A7c2VlJm5ic3A7aXQmbmJzcDtpbiZuYnNwO1JGQzM2MTguJm5ic3A7LSZuYnNwO2tl
ZXBhbGl2ZS1pbnRlcnZhbCZuYnNwO2RlcGVuZHMmbmJzcDtvbiZuYnNwO2hvbGR0aW1lLWludGVy
dmFsLjxicj5UaGVyZSZuYnNwO3Nob3VsZCZuYnNwO2JlJm5ic3A7ImlmLWZlYXR1cmUmbmJzcDtw
ZWVyLXRpbWVyLWhvbGR0aW1lIiZuYnNwO3VuZGVyJm5ic3A7bGVhZiZuYnNwO2tlZXBhbGl2ZS1p
bnRlcnZhbDxicj5vciZuYnNwO2NoYW5nZSZuYnNwO3RoZSZuYnNwO211c3QmbmJzcDtzdGF0ZW1l
bnQmbmJzcDt0byZuYnNwOyhhc3N1bWluZyZuYnNwO3dlJm5ic3A7a2VlcCZuYnNwO3RoZSZuYnNw
OzImbmJzcDtmZWF0dXJlcyk6PGJyPiZuYnNwOyZuYnNwO211c3QmbmJzcDsiKG5vdCZuYnNwOy4u
L2hvbGR0aW1lLWludGVydmFsKSZuYnNwO29yJm5ic3A7KC4mbmJzcDsmZ3Q7Jm5ic3A7MSZuYnNw
O2FuZCZuYnNwOy4mbmJzcDsmbHQ7Jm5ic3A7Li4vaG9sZHRpbWUtaW50ZXJ2YWwpIi48YnI+LSZu
YnNwO2xlYWYmbmJzcDt1cC10aW1lOiZuYnNwO3Mvc2EmbmJzcDtjYWNoZS9TQSZuYnNwO2NhY2hl
Lzxicj4tJm5ic3A7bGVhZiZuYnNwO3VwLXRpbWUsJm5ic3A7d2hhdCdzJm5ic3A7bWVhbnQmbmJz
cDtieSZuYnNwOyJ1cCZuYnNwO3RpbWUiJm5ic3A7aW4mbmJzcDt0aGUmbmJzcDtkZXNjcmlwdGlv
bj8mbmJzcDtJcyZuYnNwO2l0Jm5ic3A7dGltZSZuYnNwO2l0J3M8YnI+YmVlbiZuYnNwO2NyZWF0
ZWQ/Jm5ic3A7LSZuYnNwO2Rlc2NyaXB0aW9uJm5ic3A7Zm9yJm5ic3A7bGVhZiZuYnNwO2V4cGly
ZSZuYnNwO3NlZW1zJm5ic3A7d3JvbmcuJm5ic3A7LSZuYnNwO2xlYWY8YnI+cGVlci1sZWFybmVk
LWZyb20sJm5ic3A7Y2hhbmdlJm5ic3A7ZGVzY3JpcHRpb24mbmJzcDtmcm9tJm5ic3A7IlRoZSZu
YnNwO2FkZHJlc3MmbmJzcDtvZiZuYnNwO3BlZXImbmJzcDt0aGF0Jm5ic3A7d2UmbmJzcDtsZWFy
bmVkPGJyPnRoaXMmbmJzcDtTQSZuYnNwO2Zyb20mbmJzcDsuIiZuYnNwO3RvJm5ic3A7IlRoZSZu
YnNwO2FkZHJlc3MmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO3BlZXImbmJzcDt0aGF0Jm5ic3A7d2Um
bmJzcDtsZWFybmVkJm5ic3A7dGhpcyZuYnNwO1NBJm5ic3A7ZnJvbS4iJm5ic3A7LTxicj5Hcm91
cGluZ3MmbmJzcDthcmUmbmJzcDt1c2VkJm5ic3A7Zm9yJm5ic3A7ZGF0YSZuYnNwO3doaWNoJm5i
c3A7aXMmbmJzcDt1c2VkJm5ic3A7b25seSZuYnNwO29uY2UuJm5ic3A7SXMmbmJzcDt0aGlzJm5i
c3A7ZG9uZSZuYnNwO29uJm5ic3A7cHVycG9zZSZuYnNwO29yPGJyPndhcyZuYnNwO3RoZSZuYnNw
O2ludGVudGlvbiZuYnNwO3RvJm5ic3A7dXNlJm5ic3A7dGhvc2UmbmJzcDtncm91cGluZ3MmbmJz
cDttb3JlJm5ic3A7dGhhbiZuYnNwO29uY2U/Jm5ic3A7LSZuYnNwO2F1Z21lbnQmbmJzcDtvZjxi
cj5jb250cm9sLXBsYW5lLXByb3RvY29scyZuYnNwO2lzJm5ic3A7aW5jb3JyZWN0LiZuYnNwO1Ro
ZXJlJm5ic3A7c2hvdWxkJm5ic3A7YmUmbmJzcDthbiZuYnNwO2lkZW50aXR5Jm5ic3A7bXNkcCZu
YnNwO3dpdGg8YnI+YmFzZSZuYnNwOyJydDpyb3V0aW5nLXByb3RvY29sIiZuYnNwO2FuZCZuYnNw
O3RoZW4mbmJzcDthdWdtZW50PGJyPiIvcnQ6cm91dGluZy9ydDpjb250cm9sLXBsYW5lLXByb3Rv
Y29scy9ydDpjb250cm9sLXBsYW5lLXByb3RvY29sIiZuYnNwO3dpdGgmbmJzcDthJm5ic3A7d2hl
bjxicj5zdGF0ZW1lbnQuJm5ic3A7VGFrZSZuYnNwO2EmbmJzcDtsb29rJm5ic3A7YXQmbmJzcDtP
U1BGJm5ic3A7WUFORyZuYnNwO2ZvciZuYnNwO2FuJm5ic3A7ZXhhbXBsZS4mbmJzcDstJm5ic3A7
UlBDJm5ic3A7bGVhZiZuYnNwO2dyb3VwLCZuYnNwO0kmbmJzcDt0aG91Z2h0PGJyPndlJm5ic3A7
aGFkJm5ic3A7YSZuYnNwO3R5cGUmbmJzcDtmb3ImbmJzcDtJUCZuYnNwO211bHRpY2FzdCZuYnNw
O2FkZHJlc3M/Jm5ic3A7SWYmbmJzcDtub3QsJm5ic3A7aXQmbmJzcDtzaG91bGQmbmJzcDtiZSZu
YnNwO2RvbmU/Jm5ic3A7LTxicj5zL21zZHAvTVNEUC8mbmJzcDstJm5ic3A7SW4mbmJzcDtycGMm
bmJzcDttc2RwLWNsZWFyLXBlZXIsJm5ic3A7cy9DbGVhcnMmbmJzcDt0aGUmbmJzcDtzZXNzaW9u
Jm5ic3A7dG8mbmJzcDt0aGUmbmJzcDtwZWVyLi9DbGVhcnM8YnI+dGhlJm5ic3A7VENQJm5ic3A7
Y29ubmVjdGlvbiZuYnNwO3RvJm5ic3A7dGhlJm5ic3A7cGVlci4vJm5ic3A7LSZuYnNwO0luJm5i
c3A7cnBjJm5ic3A7bXNkcC1jbGVhci1zYS1jYWNoZSwmbmJzcDt3aHkmbmJzcDtoYXZlJm5ic3A7
dGhlPGJyPmVudW0mbmJzcDsnKicmbmJzcDtmb3ImbmJzcDtzb3VyY2UtYWRkci4mbmJzcDtDYW4n
dCZuYnNwO3RoZSZuYnNwO3NhbWUmbmJzcDt0ZWNobmlxdWUmbmJzcDthcyZuYnNwO2ZvciZuYnNw
O3BlZXItYWRkcmVzcyZuYnNwO2JlJm5ic3A7dXNlZD88YnI+LSZuYnNwO21zZHAmbmJzcDtwcmVm
aXgmbmJzcDtub3QmbmJzcDtuZWVkZWQmbmJzcDtpbiZuYnNwO3JwYyZuYnNwO25hbWVzJm5ic3A7
LSZuYnNwO01TRFAmbmJzcDtwZWVycyZuYnNwO2FyZSZuYnNwO2NvbmZpZ3VyZWQmbmJzcDtpbiZu
YnNwO2E8YnI+bWVzaC1ncm91cCwmbmJzcDtkaWQmbmJzcDt0aGUmbmJzcDthdXRob3JzJm5ic3A7
Y29uc2lkZXImbmJzcDthZGRpbmcmbmJzcDtzdGF0ZSZuYnNwO3BlciZuYnNwO21lc2gtZ3JvdXAs
Jm5ic3A7ZS5nLiZuYnNwO2FsbCZuYnNwO3RoZTxicj5wZWVycyZuYnNwO2luJm5ic3A7YSZuYnNw
O3BhcnRpY3VsYXImbmJzcDttZXNoLWdyb3VwPzxicj48YnI+R2VuZXJhbDo8YnI+LSZuYnNwO1Bl
ciZuYnNwO0FwcGVuZGl4Jm5ic3A7QiZuYnNwO29mJm5ic3A7cmZjNjA4N2Jpcy0xNTombmJzcDsi
dGhhdCZuYnNwO2FsbCZuYnNwO1lBTkcmbmJzcDttb2R1bGVzJm5ic3A7Y29udGFpbmluZzxicj5p
bXBvcnRlZCZuYnNwO2l0ZW1zJm5ic3A7YXJlJm5ic3A7Y2l0ZWQmbmJzcDthcyZuYnNwO25vcm1h
dGl2ZSZuYnNwO3JlZmVyZW5jZSIuJm5ic3A7U28mbmJzcDtSRkNzJm5ic3A7Njk5MSwmbmJzcDs3
MjIzLDxicj43Mjc3LCZuYnNwOzgwMjImbmJzcDthbmQmbmJzcDs4MTc3Jm5ic3A7c2hvdWxkJm5i
c3A7YmUmbmJzcDtpbmNsdWRlZCZuYnNwO2luJm5ic3A7dGhlJm5ic3A7bm9ybWF0aXZlJm5ic3A7
cmVmZXJlbmNlPGJyPnNlY3Rpb24uPGJyPi0mbmJzcDtTZWN0aW9uJm5ic3A7MyZuYnNwOyJ0aGUm
bmJzcDtpcnJlbGV2YW50Jm5ic3A7aW5mb3JtYXRpb24iLCZuYnNwO2FkZCZuYnNwO2EmbmJzcDty
ZWZlcmVuY2UvZXhwbGFuYXRpb24mbmJzcDtmb3ImbmJzcDt3aGF0PGJyPnRoZSZuYnNwO2lycmVs
ZXZhbnQmbmJzcDtpbmZvcm1hdGlvbiZuYnNwO2lzLiZuYnNwO3MvdGhlJm5ic3A7aXJyZWxldmFu
dCZuYnNwO2luZm9ybWF0aW9uL2lycmVsZXZhbnQ8YnI+aW5mb3JtYXRpb24vPyZuYnNwOy0mbmJz
cDtTZWN0aW9uJm5ic3A7NSZuYnNwO3Nob3VsZCZuYnNwO2dpdmUmbmJzcDthJm5ic3A7YnJpZWYm
bmJzcDtkZXNjcmlwdGlvbiZuYnNwO29mJm5ic3A7d2hhdCZuYnNwO3RoZSZuYnNwO1JQQ3MmbmJz
cDtkby48YnI+LSZuYnNwO1NlY3Rpb24mbmJzcDs2Jm5ic3A7YW55Jm5ic3A7cGxhbnMmbmJzcDtm
b3ImbmJzcDtub3RpZmljYXRpb25zPyZuYnNwO0lmJm5ic3A7bm90LCZuYnNwO2p1c3QmbmJzcDtz
YXkmbmJzcDtzby4mbmJzcDstJm5ic3A7TmVlZCZuYnNwO1NlY3VyaXR5PGJyPkNvbnNpZGVyYXRp
b25zLCZuYnNwO3NlZSZuYnNwO3NlY3Rpb25zJm5ic3A7My43Jm5ic3A7YW5kJm5ic3A7NiZuYnNw
O29mJm5ic3A7cmZjNjA4N2Jpcy0xNSZuYnNwOy0mbmJzcDtOZWVkJm5ic3A7SUFOQTxicj5Db25z
aWRlcmF0aW9ucywmbmJzcDtzZWUmbmJzcDtzZWN0aW9uJm5ic3A7My44Jm5ic3A7b2YmbmJzcDty
ZmM2MDg3YmlzLTE1Jm5ic3A7LSZuYnNwO05lZWQmbmJzcDtsaWNlbnNlJm5ic3A7aW4mbmJzcDtZ
QU5HJm5ic3A7bW9kdWxlLDxicj5zZWUmbmJzcDthcHBlbmRpeCZuYnNwO0ImbmJzcDtvZiZuYnNw
O3JmYzYwODdiaXMtMTU8YnI+PGJyPk5pdHM6PGJyPi0mbmJzcDtTZWN0aW9uJm5ic3A7NCZuYnNw
O3MvU2EtY2FjaGUvU0EtY2FjaGUvPGJyPjxicj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rpdj48L2Rp
dj48L2Rpdj48cD48YnI+PC9wPjwvZGl2Pg==


--=====_003_next=====--

--=====_002_next=====--

--=====_001_next=====--


From nobody Wed Jan 17 06:52:02 2018
Return-Path: <mersue@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8661277BB for <yang-doctors@ietfa.amsl.com>; Wed, 17 Jan 2018 06:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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=gmail.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 F_Dx7WZP4L9l for <yang-doctors@ietfa.amsl.com>; Wed, 17 Jan 2018 06:51:59 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 6932A12773A for <yang-doctors@ietf.org>; Wed, 17 Jan 2018 06:51:59 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id t74so15849245wme.3 for <yang-doctors@ietf.org>; Wed, 17 Jan 2018 06:51:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-language:thread-index; bh=YBixQh/9T7tpko8GXVa0hNTEfhUU+keXJ8HLN2y4BDI=; b=ZuGcW/nADJxkQyq0AJX4aXWnczxEikqP/6PY95JILeo8p8VhqSS/4VzRTuZSMIQOnL Ra3hG5L5r7XAXXkvoSd2XlGGnjo8t3eOb92mlY0G1aJeuCySst2PIP4v8fsMfOVl5S3/ h7naYQZKPnFQ1/slve/xt5fMqEFC9beVqruLNufWYQs6z97cG+mnXLVJlRSLgdP4uY1V mF93xnDE5m4y9SS8cVHHUluCAlbPAM6ifQS6r8dRcijPe+AxJL5a3oelEZLYIWH9iTGR hsh/T8QaK8AA0Kp+nN1WBqTYNFMJa20QW1mp21heP/7f2RxAvbxwPNMW6PzPGa3zCAp4 emgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-language:thread-index; bh=YBixQh/9T7tpko8GXVa0hNTEfhUU+keXJ8HLN2y4BDI=; b=YEahE6xB4y3srzUx457NEdFLT2a5+n0Ahbo3N5AtSoYRcI1uVyv3WysWw5+SkuNxkf vUAXZztWP53m9Ko458pBCvpEYbnseKT6D6S5ld2ZvkpuBuQCpcQioryePt1uLgYThIzx zjSRsgGj7a2zl112bJuekkCF6gFM7/wcs2swZY2tLnBYZB05/qQf+nDJ3lIuc9kiX0/3 qFts5CjWCjlQrvaJt8VYIK+7S1rVWHrxsxsn3PeepDpQnAFY/jDAFtrGghftzah9zNzL e6ks39DGZf1rONhEOcNHPpKUY8MJgogN9BlWub5K6/sqyK3WyVCoZRw3PtPHy+tmWV1Z 8nPw==
X-Gm-Message-State: AKwxytdnzUhegtp+CAkAL71YaTw71V7xprqNHaXiweXolNm8EV3W3mrx oMUiPvKk6lz1SlXzUaqGdFcTFQ==
X-Google-Smtp-Source: ACJfBoubaLUXYr6FZh0FIDP1l2gL8lmJ459v1uQ/VrL4gxs3chva+/t7+3hj132Uw6/Tqch/MUDNsg==
X-Received: by 10.80.136.15 with SMTP id b15mr3264303edb.64.1516200717583; Wed, 17 Jan 2018 06:51:57 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([2001:16b8:2dcb:b800:edf8:9118:4795:f16f]) by smtp.gmail.com with ESMTPSA id b27sm3586212edc.28.2018.01.17.06.51.55 for <yang-doctors@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Jan 2018 06:51:56 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'YANG Doctors'" <yang-doctors@ietf.org>
References: 
In-Reply-To: 
Date: Wed, 17 Jan 2018 15:51:56 +0100
Message-ID: <010901d38fa2$b8dc8510$2a958f30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_010A_01D38FAB.1AA1FE80"
X-Mailer: Microsoft Outlook 16.0
Content-Language: de
Thread-Index: AdNy1Mpv4ITy2qi/Rc2cRbbQ1AlWpwV306sgAbtp1cA=
X-MS-TNEF-Correlator: 00000000C69E16B615ED5F4C9AF09728F866A19A0700C3B68E10F77511CEB4CD00AA00BBB6E600000000000D00005F7FD4929BD1E24D8901915DC757ED050000000088620000
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/CjEJaieYe8iUi8eRwpyNxpt2o2E>
Subject: [yang-doctors] Summary of Open Review Assignments for YANG Doctors
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2018 14:52:01 -0000

This is a multipart message in MIME format.

------=_NextPart_000_010A_01D38FAB.1AA1FE80
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear YANG Doctors,

following is the list of YANG modules currently in review.
Two reviews are a bit old. Please give it a chance to satisfy the need =
of
the WGs.


Early review requests:

Reviewer               Due        Draft
Ebben Aries            2018-01-04 draft-ietf-i2rs-rib-data-model-09=20
Carl Moberg            2018-01-10
draft-ietf-lime-yang-connection-oriented-oam-model-01=20
Ladislav Lhotka        2018-01-31 draft-ietf-l2sm-l2vpn-service-model-05 =



Next in the reviewer rotation (hope this is correct now):

  Acee Lindem
  Carl Moberg
  Reshad Rahman
  J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
  Ebben Aries
  Andy Bierman
  Martin Bjorklund
  Christian Hopps
  Jan Lindblad
  Ladislaw Lhotka
  Kent Watsen

Thanks,
Mehmet


------=_NextPart_000_010A_01D38FAB.1AA1FE80
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="winmail.dat"

eJ8+IjkOAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQgABQAEAAAAAAAAAAAAAQkABAACAAAAAAAAAAEDkAYAqBYAACkA
AAALAAIAAQAAAAMAJgAAAAAACwApAAAAAAALACsAAAAAAAMALgAAAAAAHgBNAAEAAAABAAAAAAAA
AB4AcAABAAAANAAAAFN1bW1hcnkgb2YgT3BlbiBSZXZpZXcgQXNzaWdubWVudHMgZm9yIFlBTkcg
RG9jdG9ycwACAXEAAQAAACAAAAAB03LUym/ghPLaqL9FzZxFttDUCVanBXfTqyABu2nVwAsAFwwA
AAAACwABDgEAAAADABQOAQAAAB4AKA4BAAAAIAAAADAwMDAwMDAzAW1lcnN1ZUBnbWFpbC5jb20B
R21haWwAHgApDgEAAAAgAAAAMDAwMDAwMDMBbWVyc3VlQGdtYWlsLmNvbQFHbWFpbAACAQkQAQAA
AGASAABcEgAASDwAAExaRnWVMHtmBwAGAQELYG5nMTAyZjUAZAByY3AN0A4AMh0MYGMNRAE0ATFz
dHPiaAVwYmNoEDUJABDANDM3EERoDrAQ1mJpkwFDDaQzMxL2ZmUTc/h0aGUHgBM1AFAUpxQ+PGNz
DeIB9wKkEsBkaY8DNgIAEMAKwHNldALRUHBycTIAACoKoW5abxmAIA3wGtE2E4AwODUwNBtRAdAb
QDR9vwdtAoMPIBhWBGQZLTEaLPo3GzE5GtMbohuAHAAIVfMHsgKDMzQYTxlfGmgbgu8bRBsiIQEh
UGEG0AchBdD+YRSgIhQRoCKWA+Mjbxo7nwEwG6Ia4huAJgZsaSaR/SIUMRtgGD8onxpfG28cff8s
MgBQJ68trynJJgIqvwUQwCBMaWdodCvnHWj/Mo8znzSvNb8sBROgLJ84b/8uvy/PMN8ifz2fPq8/
v0DPf0UgDhA3X0MvKc86jyvnNv9Hf0iPSZ9KryvYJ49Nb0QZ3mJE0UVAT2RPg30HEyIUtjhMWEKc
MlXQUtQgB234IENFVYVRSFadQeJXz2lY03lyVYU5Wb9SZDGuNjHhW38DgkcJ0WsiFL8ggF1/XoYd
YV8/A4JUCHB3YNUx6F4NN1FBYx8DgijsSGUmkAfQKWDVHWhlrv9Xn2e2BxABoA6waJY8j15211Xi
au8DgkIHQHQOsGDVX0H/XndtIW7/Z+NWCJB09m4mcAeQZWiUJcEdf1cN/jFZACF4WQZFQFFIdg5b
Nf93fVzVRUBdaB4NXuZ3fGCI/jQN4HyPYl13fGRmgAAx6P+AzmaVd3xoK4AAHW9qHoXN/2xKgABt
KIDObrV3fHBJgAD/cRiAz3K0hc10TgHAVf9XD/8malkGAcBZr1q/lXxc1QHA711vXn+Ve2CIN0UA
mn9ibv+Ve2RmnfBtL24/lXtwSZ3wz3Efci+Ve5IvNzVMX5RvezsmlkY1UU+X76unmdY1/5poUeyb
6jtEnVlE4LAPnz//OzWhB17ys49mTDsmaCuzMP83P2ovuLdsSrMwoaiwnaM5+ztEpJo2pWiwnqcI
uNV0Tv8sMmqxpZ9XP1hPLAWab63P/8c/XNYsQIOpmw/Kn2AvzJH/aR+0b2NvZHbMkaGvt69zP/9o
O8yRpW+7P9bPbEvMkUdo/6JP2o9v78yCk1/CP9r/w9+/zJHFGKovqz02U8gpMa//98n/563MGDK2
n83f56zP6/4yui/R3+es0+nGkPDvt7/757vXzjLBL9nv9r3cDQ4B//jPvu/nyuAsk0nBz/5v91P/
5E/sweWP5p/nr+x26T/qT//rXyvmFVEIz+4v7z8L1/Df//Hv8v8L1/Sf9a/2v9f7pVn/+U8Vv/tv
DCL8v/3P/t/gWf4zAK8BvwLPA9/GouFPxl//x28L9cjvCb8mj8wYgAAoT/fN787/0Ak00M8RX9Lv
0/jeNNSvFR/jP9fdNNjfGS97Nh/cDTTdDx0/3y/gOzT/4R8hLzpPIy8r4SRvJX8qX/3IRzQoPylP
Rv/MGMygSL//LT8uT9AJ7NBMnzE/Mk9L6P8z/zUPQo/X3SvwVH85Tzpf/9wcTGBYrz1/Po/gSql5
QQ//Xn9DL1f4BP9F76utTEIIr/9Jv67exNG2j02Psg9rlBBP/1GftX5rshQPVX+4v2t2GB//Wa+8
T2t2HC9d37/fa5QgH/dh78NPxFk2ZU9mX2dvqXDvaJ9pr2q/xOA3a/9tD24f/4gTb39wj3GfiDFy
33PvdP//h+Z2j3efeK+H5no/e098X/+IBH3Pft9/78RZWiKab0Yc67zQp9BsyCk3hQ+GH6BFvcwY
OIhviX+gRM/rOIvv94z/oETT6TiPT5BfoETXzt44kv+UD61V3A04lq+Xv/+gROAsmDKyj2IcrVWc
68SRAGNvbG9ydGJshDtcz/BkMFxnz/FGbrogubB1ZTC532X9/KA1uwq8IbvfvOm69L0Sv7t/v0+/
Db6PvL+7D2XQsP44xNrF8cWvxrm69MbixU/fyR/I3chfxo/KVDlQgM2k388BxyPPAMTTv4U5SKDP
xPozwIQzvKbR8cRj0fDKVP9IkcrjoUHHI9NwxN+9gIaQodhCKlxkZaWRcLYyJ/DBuXCloFxh3LA3
IGnWBnBh1qFxsSDXEGkPuiCgULogpUBkY3RsLdhActlA3BBw1lFhdXvgQNdgc9hA2aClsNqibpR1
beCwYdpgdG/XYOBkanVzdKBQGtHZAae6gZUwuoFpdNhQMNewMFxub3GUsVtgb3RMZSDgoNxgeWxa
4Gj98BB04KDYn9mv2r/bz9zfz9Sw4KDXQaWQczFhQNdwH7og13DW4pUgTVBnMTD//KDfweOA5TTk
0dbU5oMT8T3mcmbHUOhz1zLXgVxop/vw11K6IGRi6hVjyuBzYRDoE25w6GnrtGFAc9BuZXh05NFz
3iC5gG9bcAfQ3tCUwGm5gN2Aef3dwE7tsrnA1gPlceTR4zCbYSD/4HbeoN7QdW7p8F/WUONgugDu
CeWQROFUIBpQiZBhyuDYUGggRuhvbnTV9HTlgEyA89CtTSB361DjgGbz0FdhEHh0aEJUYOOA2EDw
AGyX5rBaMPVkcvXYZmz1Ruv0sPdHYvdHcvVBubDc8Ke6EflE3vBwZfVBc/BQv7mQ/8HzwRcw9mD7
Bmz7Fc5i+xXg4PskZGf8Bv2A9/0G11D7JHbYf+Cf4a/iv//jz+Tf5e/m/+gP6R/qL+s/z+xP1HDs
4SOgbWnwwdZQ/1uQ8Ivu1GLgG0DfEBNyBVD/XMD/fwCPAZ8CrwO/BM0Jkf8F0kyABj8HRQmRB68I
tgrv/Qv9YhJQugDzQO1SDOMGsdpz3TFrTgDwfFAXENzw/2Lg7SHvNx3R7/gVnxajF59/1sINMhxF
77IddB1D1zBr/x6blQClse8316AgHwU3Bsy7EhC5QGYm4iOr8KlI+jH3+/Adke83OCcPKB8HNSnB
t1zApaDfMGQXMArBaCnA99hA7UAwMmIwgSyyI6sNf+nw5VVuT7BzuWDwUPEw3k26cD+g80DvNzks
3y3vvykrNYExjzKf8SHzMGy5cP53ugArr4aANZ8FLiIv1sT/KcA8kji/OcfuOO4R+rA0EItkQLEg
RVtwaWxT3vL/hoA8FwViPO89/z8PQB9BL/tCP0NNMTwXRuFFD0YfRy//SD9JT0pfQz5MWezRTT9O
T39PX1BvUX9Sj0M+0YA8JjT/VV9Wb1d/WI9Zn1qvW79dYP88FxeBXa9ev1/PYN9h72L/fUM+NUxo
H/9mv2fOcqAw37XBaP9qD2sfbC82PBcm//9u/3APcR9yL3M/dEne0LlQ+G1wb4Dw7OHe8ImgtgCz
03CPMDEzlPBDiTe5A7vWMIsQdrmh3rAz0GveAMZ3NOHWA3BncIBTgXI/3XCBgd1lEGf7MINxYTC/
f8V+QYBShFN+dYRTOLJAPDQ0qyF+M8dwCEA5Nso5i2Ft7dFoUBFwh2OV8zIzrsBtkhBrQtzySYil
U3WDoW1z7wFs+kaVsGOJEbYQEmDyEaSQqG1sTakgZ4jzcot32dZRSmOLMRGSSfmANJEN03A0iREl
oHRMaW1TiRFDQHJ5jlEx1gN4fYtQbhQAgcOPgwVgFFB0cHA6Ly99YN9A7dBzui45oGPeUDQQ9LAu
fXGKL5HwZpXgZS93uYD8ZC9EIAhAktOLULkQgXB72FD6sHfHYF1guiCUE2jvrpKJEYuB9cA0sECV
g/Zwt5X2jbGWBWLUcIhxZxOA/d6Qct0RFBCdYBEgB4AQ8Y/0UBEg+/H0sG5iatdg37pw8ADXMPSB
inBr3nDwUP8vIJqU7aS1ABcx1kDzQN6B44igugBzeXPtoI2h1LH0bHnzQHaLUAoxnIcU0dxnZO3g
g+DK0WaaYYAw+zSRmzF2iiC2AO3g7SCLUHekkC/Q9FBwFxCSsKFQbL/1AO0i3XAa0LmAOZF4ugD/
uVDzUDSRg7LwUCWgoHOPgf+DcaFRj4H6sN5QqTCLMN4ApngXEJCwb3m6cFztIP5wL9C5kKZA3gAS
EfvwEmDvmoAv8Lmhj7BiClDd8RJhv5Kw7aEpke2iL9ATwGUJsP25gHqaYv2AlZIloKoxL8DnqIIs
sAoxZ3arCanBFDD/JaB5YauCrISsM6FCnFGroV2uE2qmYRcgGoB2uGB3/mv5cbJQr3J9YIogCNGU
sfuXoP6SZRPAsNXtoN6A7hH9ncB0gPAloKmgmcGyZxRQ/+3QE4ASYN3xj6AUUBPBuaH/KYC40C6g
HECPoBbxp7L5cf/XELJwsGERILmw9GGyYbmh/7mQ/jGPoIixqOGpoN4AiLH/EZCBouzx2FATkBpS
JaCSsP87IBbxOzGSkJ2wOfGdAJ2wuRGBcHDwoBEgEkFpFyC/t/aGct5Q3oCHAJNBMtOQ3e0Qd7TR
fgISEHPd8crg//RQE3KSkBIwOrGikYnw3vDf7aEU0BQA3fH5cW6IofPQPyLwnbC34Z2wgDDd8WN4
/xJg3ZAPgd1w+YCnQTtQwcH3pjHeANdwY4+xtNLXcMGz9xOAJaD8AGjDI7IykMCBkPsRYZyRY6Bw
tBO00IjAw+IP+QC2ssYyoHB0eGJ4/ly4EBrghnDtEBIwsGCRIf2jEWy1YQeApvGSoH2B7eKXCMDt
QNYSd5+RZm3HYPtDsJhBIF1geXDd4gjA7eB+ddUg9RDeUJCwsIHdcGzf7aDt0LBgtnCPoHWC4vVi
/8wA3tCY0fExmJXdIqDg1PD/mjHwsPqwqaDPMxHkzkDPI+GGcjQ2NzgXUN7QmcP/3rGBYY+wmNA0
MKEREwGRsH8TMNOh3ZC3gNQi+XE0kTd/RCDTkRKwFzCB4vNQ7TBh/CAugSXTtRjg1EIuodSv/9W/
1s/UABlwEwB7oKog2J/72a/av2yX8BMAdzDYX90vfd41KdccEBDb/+Dv3hVi/CAohzHiH9PTeZDf
v+SP/+Wf5q/T8SMg6ALUj+lv6n//4o32oOgP7Z/ur++/0/G9kP/sn/I/80/0VZQB+1CBcB7T/86l
D+8Q/xIPEx8UL4LD++H7jsB+QTnSgHmAhvAgrxaP/2fPGK8ZvxrPDHOHQHcceF7fBHAh4ZfwegLC
sXPSQ0QgP71xMLKOwH46iwDO8VlBPE5HDFAlEP4ghnAsDXoK+UIgDYWbsDsinCEg3YrQIIgQduDA
QiCR8Ayk7ZrwZLgxDxBjzODBoI4w353ADvAlsIAhr4EuDYX5NP/5//sP/B/9L/4//0+Fs71Afjhd
YCFQB78IzwnffnZUv5LgEYUPEI7AduDegGKCsPsPsKHwLiVhsVB9wYugdtH/HtHegAthueEPIB3A
g9CcEN+HMRofGy8cP36UcyFPIl/7I29+Z2YRQCUfJi8nP35n/w8yssAzoSkPKh8rL35nD8H5DzJX
RyUPLl8vb35Y1wD/Mc8y3zPvCuUN5hJ/E48Un/8Vrxa/F8//+H52NZ53/3kJ/zQ/hYELbjlGNZ82
rze/RL89RcxFjsARMRGUEYFxdfubIMEgOkY/R09IXxyuTT/vTk9PX0lvC31SEaPL8VccvkRM0FeH
imCSAEtmYpzgffngQQXwEJFXGVRwrBAt31rwWyBdcLHQWNEtr4DHYJVb4DKGcC0F8GItnzK+LRBB
nbBbIADwDYVDS+H8IE24gJRA4dBaP1tAeuFDW5k/gG1lLXkCsS3PoyGywDvQfCBuLXwxEQFzyWBi
MGFtXRYBsA2FTDc+cIrQAqB2ZACh0HRrb96AWn1+oGA7MooAZtF29T2wLZjAcq9wIKBdFgMQ+w2M
DYVOoiERUg8yEZTL8f/NMSERozBR31LvU/9+Z/PQ/6HQdGAPIQ8BDwGSMBDhmOH/gNFrz2zfbe9+
Z+KAcT9yT/dzX1UffoU6dP92D3cfUN+/ed9673v/eD99HFcQQSCg9x6AjlCNcW2Ct14pgrd9//9/
D4AZBJWLMAUpBjfNkYDfp1XNqWJWgGFom+BugrcsSvyXkFmhU8lA9m70d+S6wXKCt1l5griv0P0R
QEKvgJvRjTiFz4bfgB+biu9WFk32UfnRQmqo0PRrbLuQZJIfky+UPzi//5fvmP+aD28HXhDNIA+B
vAH8IEhvsKaAnA+dH54vfP/foO+h/6MPlV+fV0qgUYOS/8QwPnClD6Yfpy+CL2QGTID/ZKSqr6u/
rM+kD6//sQ+yH/uoT59XSxEBMXDOIL+BDYz/Ob86zzvfPO89/z8P//9BL++1L7Y/HRggcWugz8L/
xA/nCs+t1w12TWWNAFwAs68/xr/HzcjPC2YAlroWfQAB0XADAN4/6f0AAAMA8T8HBAAAHgD6PwEA
AAAGAAAAR21haWwAAAADAAlZAwAAAAMALoAIIAYAAAAAAMAAAAAAAABGAAAAABCFAAAAAAAAAwBE
gAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALAHqACCAGAAAAAADAAAAAAAAARgAAAAAGhQAA
AAAAAAsAfIAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAAAwB9gAggBgAAAAAAwAAAAAAAAEYA
AAAAGIUAAAAAAAALAH6ACCAGAAAAAADAAAAAAAAARgAAAACChQAAAAAAAB4Af4AIIAYAAAAAAMAA
AAAAAABGAAAAANiFAAABAAAACQAAAElQTS5Ob3RlAAAAAAMAgIAIIAYAAAAAAMAAAAAAAABGAAAA
AOuFAAAHBAAACwAfDgEAAAACAfgPAQAAABAAAAAjs4acT/h2RboEmno8EeQFAgH6DwEAAAAQAAAA
xp4WthXtX0ya8Jco+GahmgMA/g8FAAAAAwANNP0/rQ4DAA80/T+tDgIBFDQBAAAAEAAAAOkv63WW
UESGg7h95SKqSUgCAeJlAQAAABQAAACEhcWYlzI7TJ1kInrBZjPLAAzqvQIB42UBAAAAFQAAABSE
hcWYlzI7TJ1kInrBZjPLAAzqvQAAAAIBfwABAAAAjQAAADAwMDAwMDAwQzY5RTE2QjYxNUVENUY0
QzlBRjA5NzI4Rjg2NkExOUEwNzAwQzNCNjhFMTBGNzc1MTFDRUI0Q0QwMEFBMDBCQkI2RTYwMDAw
MDAwMDAwMEQwMDAwNUY3RkQ0OTI5QkQxRTI0RDg5MDE5MTVEQzc1N0VEMDUwMDAwMDAwMDg4NjIw
MDAwAAAAAAMABhCjFCLkAwAHECUCAAADABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAAREVBUllB
TkdET0NUT1JTLEZPTExPV0lOR0lTVEhFTElTVE9GWUFOR01PRFVMRVNDVVJSRU5UTFlJTlJFVklF
V1RXT1JFVklFV1NBUkVBQklUT0xEUExFQVNFR0lWRUlUQUNIQQAAAAAr4g==

------=_NextPart_000_010A_01D38FAB.1AA1FE80--


From nobody Wed Jan 17 07:52:05 2018
Return-Path: <mersue@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349DB12FAEF for <yang-doctors@ietfa.amsl.com>; Wed, 17 Jan 2018 07:52:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 GYIO7Tuk7ViK for <yang-doctors@ietfa.amsl.com>; Wed, 17 Jan 2018 07:52:01 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::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 976BC12D7FC for <yang-doctors@ietf.org>; Wed, 17 Jan 2018 07:52:00 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id 141so16607335wme.3 for <yang-doctors@ietf.org>; Wed, 17 Jan 2018 07:52:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=xO8G10xDJo36CJqOiPDK0GRAKkiguryi+i0YBI+Msdc=; b=qIWiMPCKc3zwudgKKeCvv5LnSSeOyaYyVVYZ7oRIu2nKcHy36r82pMzZS9K1vUPp4v lyK0xor9u2H+TRla8+EbSEogL1RwPsE004dSXVhjGbnJ7uEDAmKsfHr1uRbOE8R4kzj0 oAIdmNjQjhm9Qz8T/LjB16ZyPiRM59Ej+UHAQ28adj2kMng1eanolvoMQFxADZbwPOc1 sjEynvheg+wlkjVbSZypRFiGTAdfqTjJ3uKbBQGV5XJc8KZNRctHtPBm2i1TjjH3Yb7G YGdhIjGJvw5mfz+Tdw/hgZ0VRBBkkZ1/y6LHlQRGWL0r2hpkscGCJNSdrpX3F/EUkNRC Y7Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=xO8G10xDJo36CJqOiPDK0GRAKkiguryi+i0YBI+Msdc=; b=Eh/JCXD7SsN7GBrgQGP+nE6HBLSU+aPak8E24jmDA8yL/XVEJyWy7ef+s9SuxiyoH4 fSvy2BzE5xwZ+ICZ8YX5EwXlgsKBtUTVB+GC11z/iaURflRtcnnclsYzldsLohPtyPoa T1+zSaKHkYi9HTB1kW0oXgol/QfudO0ny9HjkBlnlxSkOI1kbO9nmPK3jzZuxgX+ii16 eMfFnaYfUcBfeSfEZ+1U/VQ49ozOStV7fZsuRrcARGJrG3Ej27YK9g6207C9JQXOHSMe WzaINim/aFHXZ+blL8OHhI4WVuW7129y5XBLihIrqnnpqZLsZQgGUUFCe/3uiwhof3k/ rqAg==
X-Gm-Message-State: AKwxytdmORiXA8tHcuAVlMLLHceRUqJoPXeGvW5KZ16qCAqBreBuLzd/ c6/E6/QYLO2Yw2ti7lf/iVo4DQ==
X-Google-Smtp-Source: ACJfBot3aI6dceP18LWfGkkRyzkSFuwZ1hscDWVj1wffTWkyduDWpFg5jSg+NUjl03v8mLquq2qY8g==
X-Received: by 10.28.154.67 with SMTP id c64mr2702612wme.125.1516204318867; Wed, 17 Jan 2018 07:51:58 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([2001:16b8:2dcb:b800:edf8:9118:4795:f16f]) by smtp.gmail.com with ESMTPSA id b25sm845276wrb.52.2018.01.17.07.51.57 for <yang-doctors@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 17 Jan 2018 07:51:57 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'YANG Doctors'" <yang-doctors@ietf.org>
References: 
In-Reply-To: 
Date: Wed, 17 Jan 2018 16:51:58 +0100
Message-ID: <002501d38fab$1baf01b0$530d0510$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0026_01D38FB3.7D73DEE0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdNy1Mpv4ITy2qi/Rc2cRbbQ1AlWpwV306sgAbtp1cAAAkuRMA==
Content-Language: de
X-MS-TNEF-Correlator: 00000000C69E16B615ED5F4C9AF09728F866A19A0700C3B68E10F77511CEB4CD00AA00BBB6E600000000000D00005F7FD4929BD1E24D8901915DC757ED050000000088660000
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/KXR4DG8CM902uoVyevEncHEBH9E>
Subject: [yang-doctors] FW: Summary of Open Review Assignments for YANG Doctors
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jan 2018 15:52:03 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0026_01D38FB3.7D73DEE0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Updated reviewer rotation list:

  Acee Lindem
  Carl Moberg
  Reshad Rahman
  J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
  Ebben Aries
  Andy Bierman
  Martin Bjorklund
  Christian Hopps
  Mahesh Jethanandani
  Radek Krejci
  Jan Lindblad
  Ladislaw Lhotka
  Kent Watsen

Cheers,
Mehmet


_____________________________________________
From: Mehmet Ersue=20
Sent: Wednesday, January 17, 2018 3:52 PM
To: YANG Doctors <yang-doctors@ietf.org>
Subject: Summary of Open Review Assignments for YANG Doctors


Dear YANG Doctors,

following is the list of YANG modules currently in review.
Two reviews are a bit old. Please give it a chance to satisfy the need =
of
the WGs.


Early review requests:

Reviewer               Due        Draft
Ebben Aries            2018-01-04 draft-ietf-i2rs-rib-data-model-09=20
Carl Moberg            2018-01-10
draft-ietf-lime-yang-connection-oriented-oam-model-01=20
Ladislav Lhotka        2018-01-31 draft-ietf-l2sm-l2vpn-service-model-05 =



Next in the reviewer rotation (hope this is correct now):

  Acee Lindem
  Carl Moberg
  Reshad Rahman
  J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
  Ebben Aries
  Andy Bierman
  Martin Bjorklund
  Christian Hopps
  Jan Lindblad
  Ladislaw Lhotka
  Kent Watsen

Thanks,
Mehmet


------=_NextPart_000_0026_01D38FB3.7D73DEE0
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="winmail.dat"

eJ8+IjsPAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQgABQAEAAAAAAAAAAAAAQkABAACAAAAAAAAAAEDkAYAjBgAACkA
AAALAAIAAQAAAAMAJgAAAAAACwApAAAAAAALACsAAAAAAAMALgAAAAAAHgBNAAEAAAABAAAAAAAA
AB4AcAABAAAANAAAAFN1bW1hcnkgb2YgT3BlbiBSZXZpZXcgQXNzaWdubWVudHMgZm9yIFlBTkcg
RG9jdG9ycwACAXEAAQAAACUAAAAB03LUym/ghPLaqL9FzZxFttDUCVanBXfTqyABu2nVwAACS5Ew
AAAACwAXDAAAAAALAAEOAQAAAAMAFA4BAAAAHgAoDgEAAAAgAAAAMDAwMDAwMDMBbWVyc3VlQGdt
YWlsLmNvbQFHbWFpbAAeACkOAQAAACAAAAAwMDAwMDAwMwFtZXJzdWVAZ21haWwuY29tAUdtYWls
AAIBCRABAAAAOhQAADYUAABEQgAATFpGdSVmNOgHAAYBAQtgbmcxMDJmNQBkAHJjcA3QDgAyHQxg
Yw1EATQBMXN0c+JoBXBiY2gQNQkAEMA0MzcQRGgOsBDWYmmTAUMNpDMzEvZmZRNz+HRoZQeAEzUA
UBSnFD48Y3MN4gH3AqQSwGRpjwM2AgAQwArAc2V0AtFQcHJxMgAAKgqhblpvGYAgDfAa0TYTgDA4
NTA0G1EB0BtANH1/B20CgwBQGFYD4xkvGjti/xsRG4Aa4iCUHAAHEwKDDyBXGFYEZB5dMRosNxsx
OX8a0xuiG4AcAAhVB7ICgzP+NBhPHo8aaBuCG0QbIiES3ENhBtAHIQXQYRSgJqT/EaAdjyg/GncB
MBuiIPMqh+xsaSshJqQxG2AYPy0v/xpfG28cfTDCHW8yHy47KpIDL08FECBMaWdodP8wdyH4Nx84
Lzk/Ok8wlROg/zEvPP8zTzRfNW8nD0IvQz//RE9FX0mwDhA770e/Ll8/H/0wdzZMD00fTi9PPzBo
LB9vUf8fjyCfAoM0Ro9W5TIUMzhXZCAHbSBDRT9aFEv4Wx1GclxPXVN5cudaFFXYRywxNjZxX+8D
gvpHCdFrWhRcEWH/YwQh8dtjnwOCVAhwWhQ5Za9i5Y43VdFnbwOCKEhlKyD9B9ApAoNJsGlfamZc
H2v2vwcQAaAOsGzVNnhibThQ4etvHwOCQgdAdA6wbOQh+C9ibkERcx9sI1YIkHRu+ysAB5BlbNVa
eFZ8W/gHE71dhjVL/18ve4VhRTVV3/di33uEZOg1ZZiAHmc2e4T9aLY1aUiAHWrXe4Rsa0lw/4XP
bm6H1XB6Y1KJT3KMe4S/dGlnIoyvdmyH1XheNlp4uyKdW/YxXYAmCF2GNnxo75P+X6WVbWFFNn94
Ip1jRvuVbGToNmWYmu9nNJVsaLb+NmlIno5q1ZVsbGsk0KF/94oto31wejeMeJ6OctWVbP90aQHA
qR+QzaN9eF5cAFp//3p/KvpdhlwAXh99f7L8YUX/XABhz4CPsvtk6FwAZZ+Dv/Oy+2i2MzlxT42P
svt0aZ+/AHUvkM+y+6+vNDF5b/+x7z+2XZYw0McftX/JNmFG/2rAyk+5Dz/FZOlywM2PvL97P8Vo
tzGFv4bPP7ZsazT/DAHUP2591jdweteAjH/AP/8/tnRp14CPv8P/1jevvzDR/7ufyB9gP7PVMNFp
T8tP5L/7t1Yw0DG/L86PY++66OoR/8Lv0e9nv76W6hFBH9Uvd0//bHrqArDf2L/0T3B66gK0X//c
T3NvwinqEVDow4/8P3fv//W40N/jrz+75anUD+dvBR7/6ZjbL+tPBR3ta96f708FHb/xaeQQDm/V
PwU79U4yxw/3928UPfmNMso/+58FLP2s/jJQ7/+vFD0BzwpBAw8EH/8FLwn2Br8HzwjfMHYwwCY/
9wufDK/tpzMOXw9vEH8pV+8SHxMvFD/1ezMWLxc/GE+9+aszGj8bTxxf/dkzHi//Hz8gTyFf5CL+
z+Pf5O8pdf/mbyc/RA/pmMbgRc/rb+x//+2J14BJr+9v8H9I+PIvMp//AL/1XVpvNp9Tj/l+Xg86
r/tXv/2sNP6fPq9Xz0CvSWH/Qe9C/0ff5cdpP0a/ZG/pif9xP0qfaD/ta3UfTp9sH/Fp/ynAbh9S
n1Ov9Wx5WVZPc5+/WG9ppFnfWu9b//27NV3v/17/eD9hH2nRIn9jb8ktacL/Ji9nP8xe4lGMb2sP
z4+JFP8tz28f0v6JMjGPcv/WP4j2/zWfdy/Zz4j2Oa97X91fiRTvPZ9/b+DP4dk2gs+D34Tv/35A
hh+HL4g/4mCo+Yofiy//7YmsqY2fjq+lSJBfkW+Sf/+lZpQPlR+WL6Vml7+Yz5nf/6WEm0+cX51v
4dl3orfvY5zr+YDFUGzlqTeij6OfvcW96Zg4pe+m/73E7Ws4qW/3qn+9xPFpOKzPrd+9xPVO3jiw
f7GPytX5jTi0L7U//73E/ay1stAPf5zK1bpr4hEAY29sb3J0YmyEO1ztcGQwXGftcUZu16DXMHVl
MNdfZf0aIDXYitmh2V/aadh02pK/2P/cz9yN3A/aP9iPZe4w/jjiWuNx4y/kOdh05GLiz9/mn+Zd
5d/kD+fUOW4A6yTf7IHko+yA4lPdBTlmIO1E+jPeBDPaJu9x4ePvcOfU/2YR6GO+weSj8PDiX9sA
pBCh9cIqXGRlwxFw07InDkHW8MMgXGH6MDcgafOGcGH0IXHOoPSQaQ/XoL3Q16DCwGRjdGwt9cBy
9sD5kHDz0WF1e/3A9OBz9cD3IMMw+CJulHVt/jBh9+B0b/Tg4GRqdXN0vdA0QfaBp9gBsrDYAWl0
9dAw9TAwXG5vcbIxeOBvdExlIP4g+eB5bHhgaP0NkHT+IPYf9y/4P/lP+l/P8jD+IPTBwxBzMX7A
9PAf16D08PRisqBq0GcxMP8aIP1BAQACtAJR9FQEAzFxPQPyZuTQBfP0svUBXGinGXD00tegZGIH
lWPoYHN+kAWTbnAF6Qk0fsBz0G5leHQCUXP7oNcAb3jwJVD8ULJAadcA+wB5/ftATgsy10DzgwLx
AlEAsJt+oB1gdvwg/FB1bgdwX/PQAODXgAuJAxBE/tQgGlCnEGHoYPXQaCBG6G9udPN0dAMAagAR
UK1qoHcI0AEAZhFQV36QeHRoQnHgAQD1wA2AbJcEMHewEuRyE1hmbBLG6xIwFMdiFMdyEsHXMPpw
p9eRFsT8cHBlEsFzDdC/1xAdQRFBNLAT4BiGbBiVzmIYlf5gGKRkZxmGGwD3Gob00BikdvX//h//
LwA//wFPAl8DbwR/BY8GnwevCL/PCc/x8AphQSBtaQ5B89D/eRAOCwxUgGA4wPyQMPIi0P96QBz/
Hg8fHyAvIT8iTScR/yNSagAjvyTFJxElLyY2KG/9KX1iL9DXgBDACtIqYyQx2nP6sWtrgA38UDSQ
+nD/gGAKoQy3O1ENeDMfNCM1H3/0QiqyOcUNMjr0OsP0sGv/PBuygMMxDLf1ID2fIrckTLsvkNbA
ZkRiQSsOKUgXsfcZcDsRDLc4RI9FnyS1R0G3ekDDIPywZDSwKEFoR0D39cAKwE2yYk4BSjJBKyr/
6Q5lVW5tMHPW4A3QDrDeTdfwXSAQwAy3OUpfS2+/RqtTAU8PUB8OoRCwbNbw/nfXgEkvpABTHyKu
P6/0RP9HQFoSVj9XRwu4C5EYMFGQi4HAzqBFePBpbFP8cv+kAFmXIuJab1t/XI9dn16v+1+/YM0x
WZdkYWKPY59kr/9lv2bPZ99gvmnZClFqv2vPf2zfbe9u/3APYL7vAFmmNP9y33PvdP92D3cfeC95
P3rg/1mXNQF7L3w/fU9+X39vgH/9YL41aeg9f4Q/hU+GX4dv94h/iY/bADZZl0R/jH+Nj9+On4+v
kL+Rz9sAN1mXSk/3lK+VvqJQMNNBlu+X/5kPx5oU/FCokHBseQph/HD/pyDTgM/A8QCpUApQYQnC
AHfWg/OwqJB21yH8MFFQa437gHdSYfODcGdwpcN/puL68Kbx+uUt5xiwqOFhnjClNaOhpcKpwzQ2
u5DPNNCpw/DwrLAxM8VwqmO+NaQBrBCpw6PVrIQ2E2BveuDCEKOTo9E0yKGjkjn7qqCfADO+0KsT
5ODx8aqgR6sE5PAlwDk2ObOhbbkLUWhQLvCxUxCyM8xAMm3LYGtC+nKylVN1SakRbXMMgWxGzuBj
H7MB05Av4A+RwhBtbE01xqBnsuNytWfz0Upj+7UhLxJJFwBSEbARswFDIDB0TGltswFgwHJ51bhB
MfODeLVAbjGApzMHuXMi4DHQdHA6Ly+uc8MgVxA50C5XIGP70EtRkBVALtbQbS+74GaRzxBlL3fX
AGQvYaB/JcC8w7VA1pCm4PXQGDB37+TgeuDXoL4DaMwSswG1cf8TQK3gylC/ghPwv+a3ob/1tmLx
8LJhZzEA/BBy+pH/MZDWUC6gJQAucRHQLqAZcfEVQG5iavTg1/ANgPSw+xIBtGBr+/AN0EygxIQL
JH/SgDSx88AQwPwBspDXgHN8eXMLILeR8jGjIBDAds+1QCexxncyUWdkC2CpUL3oUWbEUaWgUhHF
IXa0EP/TgAtgQ2C1QLUgTVAR0KMQ9bRgZctAbBKACqL68DhQ+9cAVxF414DW0BDQUhGpIv8N0EMg
ymO5cajhy0G5cRgwb/vQ1IC1IPuAeDSQuqBv6nnX8FxDYHBNUNcQ0DD/+4AvkRlwL+DEcE1w1yG5
oP5iJ9D7cS/hvKALIUcRCyLbTVAxQGUnMNcAesRSGwB/v4JDINQhTUDSckowJ7Fn/nbU+dOxMbBD
IJ7h1XLWdN/WI8syxkHVkdgDatBRNKDBOAB2aWV3axbx3nB/2WK7ALQQJlG+ocGQHBJlvzFA2sUL
IPwAC5GjIHSmYP9DINOQw7HcVzHQC1AxAC/g//txuZAx0DFBFsFHAMKwTCD/OcC5kDRx0aIW8fSQ
3GDaUf8uoC0AEeHcURbBU9AbsbmQ/7Kh0tHTkPuAsqEvEKcSCnH/9dAxEDfSQyC8oFigNHFYsT+8
gMegV3HG8MegLwFwcPcOIC6gL8FpNKDh5q+S+9C3/ACw8L0xMvEQCpB3FsH7o2JHEHP7cfKQEdAw
8ryA/y+wWDHMgbPg/HALITJQMYD7+3EW8W6ykRFQQHDHoOHR58egpaD7cWN4L+D7EC0B//rwFwDR
MVjQ67HQIfuA9PD+Y7mh3sL08OujMQBDIBmAfmjtE9wiurCnAC7hxoFj/8pg3gMWwLKw7dIWgOCi
8CLBymB0eGJ4XOIAOGC/r5AKkC+w2lC7Ec0BbN9RfyUA0OG8kPvgTgElAfzgMOWmsnfJgWZt8VBh
MMIxviCsUalg+3EmQAtgdeuQ3xKQ+9C6oNpx+vBsCyALUPfaUOBguZB1qFIS4vXw/FD/wsEOscKF
MkJDYMlgxCEOMP8YMNOQ+SMvZPgw+ROqaccg/8PCufGm0bmgwsBRsMsBMIH/u6AwsP2RqDBT0P4S
FvFSEX+kEL6hDjA0oadSENAKsGH8IC6mlf2lNmD+Mkwh/p///68Av/3wNvAwgKEg0XACj/sDnwSv
bMHgMICcsAJPBx99CCUpAQwtkAXvCt8IBWL8ICixIQwP/cOfEAmvDn//D48Qn/3hQKAR8v5/E18U
b/0MfTgR7xd/GI8Zn/3S54D/Fo8cLx0/HkW98duwpuA8U//4lS2vLr8vzzDfMe8jMriw/6OpnI+d
kzR/NYY2TzdVQoHfTGA/A6DwL1PWIWIv9TfP/zjbsTBT3CwRP29AcC3QNAH/weCfguyhouCvqk5Q
uLCjmv5VJgDKsULQpZHZcfXh9yGLThBSQSDqMjoNCiMy9iA55TqwQbygnGC4QLdh2m06V0O4sGDg
TeJwvjA6ZzpXUlGA02E9UGFoZbHgbjpXSvzBgFBRU6FOUPZud+TksXI6V+xFYsbQQzBBMRBRgDpY
/9nAozCy0L4wPgq1YcYBQfDSatLAa2xQoGQ7mNCQ9+pB5fFJEG/lYEEYtWC7IL9NUD6w9vEsUNkh
LFBpPNiR03FrIEvrkGpjRzi+SkUBOzLscCgAOldMKAAbtMAsQHc7IMvAdGth5TpXS81RIFdOEOlx
Oez3RJA7AK+QLDnlUgA98PLg/znlsSFT3DQ9NaMsRcHgLob/UeIvRZ7jL9We1DBlntKscPfMgPKg
2/BmNe82/k7PnQb/ne+e8jWvVn9XiSMzI+8k//8mDycfKC8pN6fC/hEp3TLef5agUF6dcFOWlrBa
7zcNX39p32rva5j6A1gf0iBl31y/0iBm/2gPo5q0QPRAOlgvf2X/b39wj6OpTlVAYK+QdX+cYWy/
bc9u33Uvdj+kElO/zVFyj3n/ey98P3bLV/NQpdywc8kgeSxJEnW4sR4gwTCD4Fqw1gAgMzryNZ3Q
UE14b3l/eo+A3/OB76QDVG9+T4cfiE+JX4F2y1lBTkcgROwAo2Ggr5AgPHksUS3EUS2Q0kDZcPFQ
LtLAZz7/hY+Gn4evjd+O7320s6DY4P9fMItPlC+VX5ZvdsuzkLFR84RRu+AgT6JAI9A9YNli3zrQ
oKDMYU6QyhEgxaGQS/9c713/Xw9gH2EvYj8pcmTv/1k9msKbrTpGoOsjjbpg2eC/ok+jX6RvpX9i
jynGOfxw+VNgMzkqvi+hM/MsL1m3/y+wLa8utjD/Mg8zGzRPNV/7nB9cZkTbQKAMTeY55cWg6+RC
xhEgOaAgRqCS0DmSt54ikFPE4GTiIZEAY/bQv+uQ38DHsMFwI9A4dC6g77+sr62/rs+v37Dvsf84
5zD+OPYQNDC6L7s/vE+9X4qnfHdvOGWRAMdQktAIcGL3KWCeIOSwLoVQ67Dl0JLQ/9ag7VDBcPSA
CHA28ePRwaD90VBzOTH84J4QwbLcsDhB454xwbJXR3PEf8WPxp+fx6/Iv8nPyt+qIDQ3VND/52DM
byu1UF/PH9AvV7/ND+/OH+Df4e859EU8MZ4QOHTtOGFxeDDbwHM53Z609eH961xEeDHr1tlg/PDo
JkCIG+tahMIthNDvYDQgZK3tAi2SAvAgMvwwLbhgJmKRcPgQYS3CwWVs/+9gs2BNFjw47m/vcbVQ
78rr3JCfgC2RM2M5YNVQ2OB9OVEtklBCEMOQg2D2cGHebfFWNDA55Up1dkr17q6zVND0ezJz9zAB
0HbawPotTHByntA68PFWLLA57Pk55U5lIsDD0sGyOH8dwP9LEJ5wwaHBgcGB9dDDYdjg+9VAwSAp
Od867zv/AmTjX//kb+V5twVj0C6KuLZj0OYv/zcNPW8+fz+PQJ9BrwT/Bg//5S8KHzccQw9EH0Ut
SS9KP/9LT0xf1q/Xv9jP2d/a79v//7JPs1ERvxLPE98U74qnRrH+a03f4w8mHycrKA8pF7MGCStm
fQAxMAAAAwDeP+n9AAADAPE/BwQAAB4A+j8BAAAABgAAAEdtYWlsAAAAAwAJWQMAAAADAC6ACCAG
AAAAAADAAAAAAAAARgAAAAAQhQAAAAAAAAMARIAIIAYAAAAAAMAAAAAAAABGAAAAAAGFAAAAAAAA
CwB6gAggBgAAAAAAwAAAAAAAAEYAAAAABoUAAAAAAAALAHyACCAGAAAAAADAAAAAAAAARgAAAAAO
hQAAAAAAAAMAfYAIIAYAAAAAAMAAAAAAAABGAAAAABiFAAAAAAAACwB+gAggBgAAAAAAwAAAAAAA
AEYAAAAAgoUAAAAAAAAeAH+ACCAGAAAAAADAAAAAAAAARgAAAADYhQAAAQAAAAkAAABJUE0uTm90
ZQAAAAADAICACCAGAAAAAADAAAAAAAAARgAAAADrhQAABwQAAAsAHw4BAAAAAgH4DwEAAAAQAAAA
I7OGnE/4dkW6BJp6PBHkBQIB+g8BAAAAEAAAAMaeFrYV7V9MmvCXKPhmoZoDAP4PBQAAAAMADTT9
P60OAwAPNP0/rQ4CARQ0AQAAABAAAADpL+t1llBEhoO4feUiqklIAgHiZQEAAAAUAAAAhIXFmJcy
O0ydZCJ6wWYzywAM8JQCAeNlAQAAABUAAAAUhIXFmJcyO0ydZCJ6wWYzywAM8JQAAAACAX8AAQAA
AI0AAAAwMDAwMDAwMEM2OUUxNkI2MTVFRDVGNEM5QUYwOTcyOEY4NjZBMTlBMDcwMEMzQjY4RTEw
Rjc3NTExQ0VCNENEMDBBQTAwQkJCNkU2MDAwMDAwMDAwMDBEMDAwMDVGN0ZENDkyOUJEMUUyNEQ4
OTAxOTE1REM3NTdFRDA1MDAwMDAwMDA4ODY2MDAwMAAAAAADAAYQkgQOhQMABxB+AwAAAwAQEAAA
AAADABEQAAAAAB4ACBABAAAAZQAAAFVQREFURURSRVZJRVdFUlJPVEFUSU9OTElTVDpBQ0VFTElO
REVNQ0FSTE1PQkVSR1JFU0hBRFJBSE1BTkrDvFJHRU5TQ0jDtk5Xw6RMREVSRUJCRU5BUklFU0FO
RFlCSUVSTUEAAAAATLE=

------=_NextPart_000_0026_01D38FB3.7D73DEE0--


From nobody Thu Jan 18 00:33:17 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2246E12EB1C; Thu, 18 Jan 2018 00:33:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ebben Aries <exa@juniper.net>
To: <yang-doctors@ietf.org>
Cc: i2rs@ietf.org, draft-ietf-i2rs-rib-data-model.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151626438402.10775.7250014155413667607@ietfa.amsl.com>
Date: Thu, 18 Jan 2018 00:33:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/VClU_kAndmgWlqQIiTyh56ORy6Y>
Subject: [yang-doctors] Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 08:33:04 -0000

Reviewer: Ebben Aries
Review result: On the Right Track

1 module in this draft:
- ietf-i2rs-rib@2017-12-05.yang

No YANG validation errors or warnings (from pyang 1.7.3 and yanglint 0.14.59)

0 examples are provided in this draft (section 3.12 of
draft-ietf-netmod-rfc6087bis-15)

Module ietf-i2rs-rib@2017-12-05.yang:
- yang-version statement missing - should be 1.1
- prefix 'iir' is recommended for this module, would 'rib' suffice better?
- import "ietf-inet-types" should reference RFC 6991 per (not as a comment)
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.7
- import "ietf-interfaces" should reference RFC 7223 per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.7
- import "ietf-yang-types" should reference RFC 6991 per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.7
- Since this module imports "ietf-interfaces", a normative references must be
  added per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-3.9
- prefix "if" in the import "ietf-interfaces" can remove quotes to remain
  consistent with other imports
- Remove WG Chairs from contact information per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Module description must contain most recent copyright notice per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Module description should contain note to RFC Ed. and placeholder reference
  to RFC when assigned
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Add placeholder reference and note to RFC Ed. for RFC when assigned
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Security Considerations should be updated to reflect new template at
  https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
- Section 1.2 should be replaced with reference to
  draft-ietf-netmod-yang-tree-diagrams-02 rather (as-is in other i2rs YANG
  drafts in progress) per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-2.5.1
- This module contains '12' features.  While it is understood the purpose of
  these features in the module, take precaution as to complexity for clients
  if they need to understand >= quantity of features per module in use on a
  network-element.
- A few comments exist that are either unecessary or redundant.  Encode the
  comment intent rather in description fields if need be.
- Per NMDA, which datastores are targeted for the module?  Will all RPC
  operations be acting upon the dynamic/ephemeral datastore?  It is not clear
  to me if the intention is to be persistent or ephemeral

General comments/Nits:
- references to 'def' could be expanded out to 'definition'
- references to 'decap' could be expanded out to 'decapsulation' for
  readability (across definitions and descriptions)
- Follow consistent capitalization of 'RIB' throughout document text.  Mixed
  use of 'Rib' and 'rib' exists (Outside of YANG node lowercase definitions).
- Is it necessary to prefix all nodes under the nexthop container with
  "nexthop-"?
- Section 2.5 - route-add RPC - text mentions it is required that the nh-add
  RPC be called as a pre-requisite however if the nh already exists and the
  nexthop-id is known, this should not be necessary.  In addition, the text
  reads 'or return' which should rather be a result of querying the
  appropriate node in the data tree.
- In 'IANA Considerations' - s/This document requests to register/This
  document registers/


From nobody Thu Jan 18 01:53:13 2018
Return-Path: <amit.dass@ericsson.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E9F1200C5; Thu, 18 Jan 2018 01:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 egUnLBlhOeyQ; Thu, 18 Jan 2018 01:53:01 -0800 (PST)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 5423312EB20; Thu, 18 Jan 2018 01:52:57 -0800 (PST)
X-AuditID: c1b4fb30-d49ff70000006bc7-91-5a606e77209e
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 7C.25.27591.77E606A5; Thu, 18 Jan 2018 10:52:55 +0100 (CET)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.63) with Microsoft SMTP Server (TLS) id 14.3.352.0; Thu, 18 Jan 2018 10:52:54 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ETkBUhbjfsTH/9SxNsBu9ZBkZFyfYSYbW0omYf1fTac=; b=d6l63P6x8bm4YPYDuu9VjhhPt36XvjkpRACttq1amaw/VlsMAa9IbcROjKXLQis5sC0VCcFD6mrn6HAHxPkLTin1N9Z784HM6vPQ3nNSq3GVFDOWURBh4DGxnr5UdCrEFZUSivM9S5VFpTMecfetZUMrG1fsOkT6kwSJJZZeHt4=
Received: from HE1PR0702MB3580.eurprd07.prod.outlook.com (52.133.6.15) by HE1PR0702MB3834.eurprd07.prod.outlook.com (52.133.7.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.9; Thu, 18 Jan 2018 09:52:53 +0000
Received: from HE1PR0702MB3580.eurprd07.prod.outlook.com ([fe80::40cf:6d37:eed9:864d]) by HE1PR0702MB3580.eurprd07.prod.outlook.com ([fe80::40cf:6d37:eed9:864d%13]) with mapi id 15.20.0428.014; Thu, 18 Jan 2018 09:52:53 +0000
From: Amit Dass <amit.dass@ericsson.com>
To: Ebben Aries <exa@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "i2rs@ietf.org" <i2rs@ietf.org>, "draft-ietf-i2rs-rib-data-model.all@ietf.org" <draft-ietf-i2rs-rib-data-model.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09
Thread-Index: AQHTkDcKZ8fIlvBx70ukLYUj3ljGR6N5YyEA
Date: Thu, 18 Jan 2018 09:52:53 +0000
Message-ID: <HE1PR0702MB35806D6985E0A7754F840EE193E80@HE1PR0702MB3580.eurprd07.prod.outlook.com>
References: <151626438402.10775.7250014155413667607@ietfa.amsl.com>
In-Reply-To: <151626438402.10775.7250014155413667607@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.176.1.92]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0702MB3834; 7:nimEf1DwRc4w5PT1h35r4PuDsWzEIGTgi313uzgWv76UiIoDnzLzRvLBtD3hPp9+lU86amkOCccnaIFYZ1AAf/KcXZgeMBxfLUK+RzesKnb26spSmMQZluUWu31UP4LJ54GlFso12LKOvHO+xaoQoU9YRMPwZtpwi0eeVeI7tqwFlmc6Z9q31R0XH01Z3SH0zRd0hA6f9EosidNtSH0xqU35bqstGVcNGO/aIaKBWC14F4uU9+dgI4Hsz+HbuTpM
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 66b7a1b5-8d0e-47a9-2a53-08d55e593e60
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534125)(4602075)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:HE1PR0702MB3834; 
x-ms-traffictypediagnostic: HE1PR0702MB3834:
x-microsoft-antispam-prvs: <HE1PR0702MB3834DB9B26365E5B42B820F693E80@HE1PR0702MB3834.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(138986009662008);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040492)(2401047)(5005006)(8121501046)(3231046)(2400059)(944501161)(10201501046)(3002001)(93006095)(93001095)(6041279)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:HE1PR0702MB3834; BCL:0; PCL:0; RULEID:(100000803126)(100110400120); SRVR:HE1PR0702MB3834; 
x-forefront-prvs: 05568D1FF7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(396003)(376002)(39380400002)(366004)(199004)(189003)(13464003)(14454004)(478600001)(9686003)(966005)(6436002)(6306002)(97736004)(55016002)(8666007)(81166006)(8936002)(53936002)(229853002)(8676002)(81156014)(68736007)(4326008)(66066001)(2900100001)(33656002)(2501003)(6246003)(25786009)(5250100002)(316002)(26005)(106356001)(3846002)(6116002)(2906002)(7696005)(6346003)(230783001)(1941001)(5660300001)(86362001)(105586002)(3660700001)(2950100002)(54906003)(3280700002)(74316002)(6506007)(102836004)(59450400001)(76176011)(305945005)(110136005)(53546011)(7736002)(99286004); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0702MB3834; H:HE1PR0702MB3580.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=amit.dass@ericsson.com; 
x-microsoft-antispam-message-info: BlblbwrRWWOkFupU88FuZMXTdB3TdDkth/Rn6nycVDnAxqIhw78W8F34g2fqoUm79m33+Bs5y+DJNuzb/yOXjA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 66b7a1b5-8d0e-47a9-2a53-08d55e593e60
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jan 2018 09:52:53.2976 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3834
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRmVeSWpSXmKPExsUyM2K7vW55XkKUwfMmQYtHKzcwWbxcvZXF Yt2MDywWzzbOZ7Ho23WA0YHVY8mSn0we15uusgcwRXHZpKTmZJalFunbJXBlnP50ir3gn1bF /+cnmBoYP2h2MXJySAiYSKzc0s4EYgsJHGaU2L9TuouRC8g+wShx6dQbVhCHRaCXWeJZ9x12 iMw0JomVi+awQTjPGSX+7VzFBtLPJqAhsXb5VpYuRg4OEYEQiZkXikBqmAWWM0p8OLOCBaRG WMBLonHnDDBbRMBb4sHH66wQtpHE0SmbwO5gEVCVmLftNFgNr0CCRMfHZlaI+5wlbj4+wgxi cwq4SLzt/AdmMwqISXw/tQasl1lAXOLWk/lMEL8JSCzZc54ZwhaVePn4HyuErSDx59IjNghb VuLS/G5GkEMlBLYxSTTs74Zq1pPYOvEtI4TtKzHp80EWiKLLjBLHu3uhJulILN0xFaohX+LD 4fuMIN9LCPhI7JlUAFG/g1niwJ02qG0yEo0XJ0IN6meT+Lb7AuMERv1ZSC6fBdTPLKApsX4X VFhRYkr3Q/ZZ4MAQlDg58wnLAkaWVYyixanFSbnpRkZ6qUWZycXF+Xl6eaklmxiBaeXglt8G OxhfPnc8xCjAwajEw/vCLyFKiDWxrLgy9xCjBAezkgjvO2+gEG9KYmVValF+fFFpTmrxIUZp DhYlcd6TnrxRQgLpiSWp2ampBalFMFkmDk6pBkbR7woKv4+5zi/QtJT4dpp/otlCOW6DsMdu rL5i/V8/PZy4Unmux6ESo869p9PqZnBtZNRdZLVIIkZ2cZTa/DDFvUXzlKbpJ4Uf/m7ukRWZ UKrgt93cXC9FQv/LRq/QfYmdYZOSlBgb9AU99p55bC8//9fhzynfV91Z4PvC+O9r2UcBqRYR CUosxRmJhlrMRcWJAD3Md0gnAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/445jHYa3e6sZURQ5zR8366DwJqE>
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 09:53:08 -0000

VGhhbmtzIEViYmVuIGZvciByZXZpZXdpbmcgdGhlIGRyYWZ0LiBJIHdpbGwgdXBkYXRlIHRoZSBz
YW1lIGJhc2VkIG9uIGJlbG93IGNvbW1lbnRzIGFuZCBmZWVkYmFjay4NCg0KDQpCZXN0IHJlZ2Fy
ZHMsDQpBbWl0DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBFYmJlbiBBcmll
cyBbbWFpbHRvOmV4YUBqdW5pcGVyLm5ldF0gDQpTZW50OiBUaHVyc2RheSwgSmFudWFyeSAxOCwg
MjAxOCA5OjMzIEFNDQpUbzogeWFuZy1kb2N0b3JzQGlldGYub3JnDQpDYzogaTJyc0BpZXRmLm9y
ZzsgZHJhZnQtaWV0Zi1pMnJzLXJpYi1kYXRhLW1vZGVsLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRm
Lm9yZw0KU3ViamVjdDogWWFuZ2RvY3RvcnMgZWFybHkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaTJy
cy1yaWItZGF0YS1tb2RlbC0wOQ0KDQpSZXZpZXdlcjogRWJiZW4gQXJpZXMNClJldmlldyByZXN1
bHQ6IE9uIHRoZSBSaWdodCBUcmFjaw0KDQoxIG1vZHVsZSBpbiB0aGlzIGRyYWZ0Og0KLSBpZXRm
LWkycnMtcmliQDIwMTctMTItMDUueWFuZw0KDQpObyBZQU5HIHZhbGlkYXRpb24gZXJyb3JzIG9y
IHdhcm5pbmdzIChmcm9tIHB5YW5nIDEuNy4zIGFuZCB5YW5nbGludCAwLjE0LjU5KQ0KDQowIGV4
YW1wbGVzIGFyZSBwcm92aWRlZCBpbiB0aGlzIGRyYWZ0IChzZWN0aW9uIDMuMTIgb2YNCmRyYWZ0
LWlldGYtbmV0bW9kLXJmYzYwODdiaXMtMTUpDQoNCk1vZHVsZSBpZXRmLWkycnMtcmliQDIwMTct
MTItMDUueWFuZzoNCi0geWFuZy12ZXJzaW9uIHN0YXRlbWVudCBtaXNzaW5nIC0gc2hvdWxkIGJl
IDEuMQ0KLSBwcmVmaXggJ2lpcicgaXMgcmVjb21tZW5kZWQgZm9yIHRoaXMgbW9kdWxlLCB3b3Vs
ZCAncmliJyBzdWZmaWNlIGJldHRlcj8NCi0gaW1wb3J0ICJpZXRmLWluZXQtdHlwZXMiIHNob3Vs
ZCByZWZlcmVuY2UgUkZDIDY5OTEgcGVyIChub3QgYXMgYSBjb21tZW50KQ0KICBodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1uZXRtb2QtcmZjNjA4N2Jpcy0xNSNzZWN0aW9u
LTQuNw0KLSBpbXBvcnQgImlldGYtaW50ZXJmYWNlcyIgc2hvdWxkIHJlZmVyZW5jZSBSRkMgNzIy
MyBwZXINCiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbmV0bW9kLXJm
YzYwODdiaXMtMTUjc2VjdGlvbi00LjcNCi0gaW1wb3J0ICJpZXRmLXlhbmctdHlwZXMiIHNob3Vs
ZCByZWZlcmVuY2UgUkZDIDY5OTEgcGVyDQogIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1pZXRmLW5ldG1vZC1yZmM2MDg3YmlzLTE1I3NlY3Rpb24tNC43DQotIFNpbmNlIHRoaXMg
bW9kdWxlIGltcG9ydHMgImlldGYtaW50ZXJmYWNlcyIsIGEgbm9ybWF0aXZlIHJlZmVyZW5jZXMg
bXVzdCBiZQ0KICBhZGRlZCBwZXINCiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWlldGYtbmV0bW9kLXJmYzYwODdiaXMtMTUjc2VjdGlvbi0zLjkNCi0gcHJlZml4ICJpZiIgaW4g
dGhlIGltcG9ydCAiaWV0Zi1pbnRlcmZhY2VzIiBjYW4gcmVtb3ZlIHF1b3RlcyB0byByZW1haW4N
CiAgY29uc2lzdGVudCB3aXRoIG90aGVyIGltcG9ydHMNCi0gUmVtb3ZlIFdHIENoYWlycyBmcm9t
IGNvbnRhY3QgaW5mb3JtYXRpb24gcGVyDQogIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9k
cmFmdC1pZXRmLW5ldG1vZC1yZmM2MDg3YmlzLTE1I2FwcGVuZGl4LUMNCi0gTW9kdWxlIGRlc2Ny
aXB0aW9uIG11c3QgY29udGFpbiBtb3N0IHJlY2VudCBjb3B5cmlnaHQgbm90aWNlIHBlcg0KICBo
dHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1uZXRtb2QtcmZjNjA4N2Jpcy0x
NSNhcHBlbmRpeC1DDQotIE1vZHVsZSBkZXNjcmlwdGlvbiBzaG91bGQgY29udGFpbiBub3RlIHRv
IFJGQyBFZC4gYW5kIHBsYWNlaG9sZGVyIHJlZmVyZW5jZQ0KICB0byBSRkMgd2hlbiBhc3NpZ25l
ZA0KICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1uZXRtb2QtcmZjNjA4
N2Jpcy0xNSNhcHBlbmRpeC1DDQotIEFkZCBwbGFjZWhvbGRlciByZWZlcmVuY2UgYW5kIG5vdGUg
dG8gUkZDIEVkLiBmb3IgUkZDIHdoZW4gYXNzaWduZWQNCiAgaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWlldGYtbmV0bW9kLXJmYzYwODdiaXMtMTUjYXBwZW5kaXgtQw0KLSBTZWN1
cml0eSBDb25zaWRlcmF0aW9ucyBzaG91bGQgYmUgdXBkYXRlZCB0byByZWZsZWN0IG5ldyB0ZW1w
bGF0ZSBhdA0KICBodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9vcHMvd2lraS95YW5nLXNlY3Vy
aXR5LWd1aWRlbGluZXMNCi0gU2VjdGlvbiAxLjIgc2hvdWxkIGJlIHJlcGxhY2VkIHdpdGggcmVm
ZXJlbmNlIHRvDQogIGRyYWZ0LWlldGYtbmV0bW9kLXlhbmctdHJlZS1kaWFncmFtcy0wMiByYXRo
ZXIgKGFzLWlzIGluIG90aGVyIGkycnMgWUFORw0KICBkcmFmdHMgaW4gcHJvZ3Jlc3MpIHBlcg0K
ICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1uZXRtb2QtcmZjNjA4N2Jp
cy0xNSNzZWN0aW9uLTIuNS4xDQotIFRoaXMgbW9kdWxlIGNvbnRhaW5zICcxMicgZmVhdHVyZXMu
ICBXaGlsZSBpdCBpcyB1bmRlcnN0b29kIHRoZSBwdXJwb3NlIG9mDQogIHRoZXNlIGZlYXR1cmVz
IGluIHRoZSBtb2R1bGUsIHRha2UgcHJlY2F1dGlvbiBhcyB0byBjb21wbGV4aXR5IGZvciBjbGll
bnRzDQogIGlmIHRoZXkgbmVlZCB0byB1bmRlcnN0YW5kID49IHF1YW50aXR5IG9mIGZlYXR1cmVz
IHBlciBtb2R1bGUgaW4gdXNlIG9uIGENCiAgbmV0d29yay1lbGVtZW50Lg0KLSBBIGZldyBjb21t
ZW50cyBleGlzdCB0aGF0IGFyZSBlaXRoZXIgdW5lY2Vzc2FyeSBvciByZWR1bmRhbnQuICBFbmNv
ZGUgdGhlDQogIGNvbW1lbnQgaW50ZW50IHJhdGhlciBpbiBkZXNjcmlwdGlvbiBmaWVsZHMgaWYg
bmVlZCBiZS4NCi0gUGVyIE5NREEsIHdoaWNoIGRhdGFzdG9yZXMgYXJlIHRhcmdldGVkIGZvciB0
aGUgbW9kdWxlPyAgV2lsbCBhbGwgUlBDDQogIG9wZXJhdGlvbnMgYmUgYWN0aW5nIHVwb24gdGhl
IGR5bmFtaWMvZXBoZW1lcmFsIGRhdGFzdG9yZT8gIEl0IGlzIG5vdCBjbGVhcg0KICB0byBtZSBp
ZiB0aGUgaW50ZW50aW9uIGlzIHRvIGJlIHBlcnNpc3RlbnQgb3IgZXBoZW1lcmFsDQoNCkdlbmVy
YWwgY29tbWVudHMvTml0czoNCi0gcmVmZXJlbmNlcyB0byAnZGVmJyBjb3VsZCBiZSBleHBhbmRl
ZCBvdXQgdG8gJ2RlZmluaXRpb24nDQotIHJlZmVyZW5jZXMgdG8gJ2RlY2FwJyBjb3VsZCBiZSBl
eHBhbmRlZCBvdXQgdG8gJ2RlY2Fwc3VsYXRpb24nIGZvcg0KICByZWFkYWJpbGl0eSAoYWNyb3Nz
IGRlZmluaXRpb25zIGFuZCBkZXNjcmlwdGlvbnMpDQotIEZvbGxvdyBjb25zaXN0ZW50IGNhcGl0
YWxpemF0aW9uIG9mICdSSUInIHRocm91Z2hvdXQgZG9jdW1lbnQgdGV4dC4gIE1peGVkDQogIHVz
ZSBvZiAnUmliJyBhbmQgJ3JpYicgZXhpc3RzIChPdXRzaWRlIG9mIFlBTkcgbm9kZSBsb3dlcmNh
c2UgZGVmaW5pdGlvbnMpLg0KLSBJcyBpdCBuZWNlc3NhcnkgdG8gcHJlZml4IGFsbCBub2RlcyB1
bmRlciB0aGUgbmV4dGhvcCBjb250YWluZXIgd2l0aA0KICAibmV4dGhvcC0iPw0KLSBTZWN0aW9u
IDIuNSAtIHJvdXRlLWFkZCBSUEMgLSB0ZXh0IG1lbnRpb25zIGl0IGlzIHJlcXVpcmVkIHRoYXQg
dGhlIG5oLWFkZA0KICBSUEMgYmUgY2FsbGVkIGFzIGEgcHJlLXJlcXVpc2l0ZSBob3dldmVyIGlm
IHRoZSBuaCBhbHJlYWR5IGV4aXN0cyBhbmQgdGhlDQogIG5leHRob3AtaWQgaXMga25vd24sIHRo
aXMgc2hvdWxkIG5vdCBiZSBuZWNlc3NhcnkuICBJbiBhZGRpdGlvbiwgdGhlIHRleHQNCiAgcmVh
ZHMgJ29yIHJldHVybicgd2hpY2ggc2hvdWxkIHJhdGhlciBiZSBhIHJlc3VsdCBvZiBxdWVyeWlu
ZyB0aGUNCiAgYXBwcm9wcmlhdGUgbm9kZSBpbiB0aGUgZGF0YSB0cmVlLg0KLSBJbiAnSUFOQSBD
b25zaWRlcmF0aW9ucycgLSBzL1RoaXMgZG9jdW1lbnQgcmVxdWVzdHMgdG8gcmVnaXN0ZXIvVGhp
cw0KICBkb2N1bWVudCByZWdpc3RlcnMvDQoNCg==


From nobody Thu Jan 18 01:55:16 2018
Return-Path: <shares@ndzh.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C27A512EB2C; Thu, 18 Jan 2018 01:55:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no 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 Ubwk39OlG0mo; Thu, 18 Jan 2018 01:55:07 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 AD41B12EB2A; Thu, 18 Jan 2018 01:55:06 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=166.176.249.181; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Amit Dass'" <amit.dass@ericsson.com>, "'Ebben Aries'" <exa@juniper.net>,  <yang-doctors@ietf.org>
Cc: <i2rs@ietf.org>, <draft-ietf-i2rs-rib-data-model.all@ietf.org>, <ietf@ietf.org>
References: <151626438402.10775.7250014155413667607@ietfa.amsl.com> <HE1PR0702MB35806D6985E0A7754F840EE193E80@HE1PR0702MB3580.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0702MB35806D6985E0A7754F840EE193E80@HE1PR0702MB3580.eurprd07.prod.outlook.com>
Date: Thu, 18 Jan 2018 04:55:03 -0500
Message-ID: <009801d39042$6a4b08e0$3ee11aa0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQC3u74PMe0eeI3XGuaBaMtbP6kcDwEkBmjSpafs26A=
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/U8KLK46XKOgq-7CBc92XjI1iP34>
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 09:55:09 -0000

Amit:

Do you think you and your co-authors can do this within a few days.   I =
would like to forward the publication request.=20

Also, please remember to look at the latest Revised datastore draft and =
yang tree module drafts.=20

Sue Hares=20

-----Original Message-----
From: Amit Dass [mailto:amit.dass@ericsson.com]=20
Sent: Thursday, January 18, 2018 4:53 AM
To: Ebben Aries; yang-doctors@ietf.org
Cc: i2rs@ietf.org; draft-ietf-i2rs-rib-data-model.all@ietf.org; =
ietf@ietf.org
Subject: RE: Yangdoctors early review of =
draft-ietf-i2rs-rib-data-model-09

Thanks Ebben for reviewing the draft. I will update the same based on =
below comments and feedback.


Best regards,
Amit

-----Original Message-----
From: Ebben Aries [mailto:exa@juniper.net]=20
Sent: Thursday, January 18, 2018 9:33 AM
To: yang-doctors@ietf.org
Cc: i2rs@ietf.org; draft-ietf-i2rs-rib-data-model.all@ietf.org; =
ietf@ietf.org
Subject: Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09

Reviewer: Ebben Aries
Review result: On the Right Track

1 module in this draft:
- ietf-i2rs-rib@2017-12-05.yang

No YANG validation errors or warnings (from pyang 1.7.3 and yanglint =
0.14.59)

0 examples are provided in this draft (section 3.12 of
draft-ietf-netmod-rfc6087bis-15)

Module ietf-i2rs-rib@2017-12-05.yang:
- yang-version statement missing - should be 1.1
- prefix 'iir' is recommended for this module, would 'rib' suffice =
better?
- import "ietf-inet-types" should reference RFC 6991 per (not as a =
comment)
  =
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.7
- import "ietf-interfaces" should reference RFC 7223 per
  =
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.7
- import "ietf-yang-types" should reference RFC 6991 per
  =
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.7
- Since this module imports "ietf-interfaces", a normative references =
must be
  added per
  =
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-3.9
- prefix "if" in the import "ietf-interfaces" can remove quotes to =
remain
  consistent with other imports
- Remove WG Chairs from contact information per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Module description must contain most recent copyright notice per
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Module description should contain note to RFC Ed. and placeholder =
reference
  to RFC when assigned
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Add placeholder reference and note to RFC Ed. for RFC when assigned
  https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#appendix-C
- Security Considerations should be updated to reflect new template at
  https://trac.ietf.org/trac/ops/wiki/yang-security-guidelines
- Section 1.2 should be replaced with reference to
  draft-ietf-netmod-yang-tree-diagrams-02 rather (as-is in other i2rs =
YANG
  drafts in progress) per
  =
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-2.5.1=

- This module contains '12' features.  While it is understood the =
purpose of
  these features in the module, take precaution as to complexity for =
clients
  if they need to understand >=3D quantity of features per module in use =
on a
  network-element.
- A few comments exist that are either unecessary or redundant.  Encode =
the
  comment intent rather in description fields if need be.
- Per NMDA, which datastores are targeted for the module?  Will all RPC
  operations be acting upon the dynamic/ephemeral datastore?  It is not =
clear
  to me if the intention is to be persistent or ephemeral

General comments/Nits:
- references to 'def' could be expanded out to 'definition'
- references to 'decap' could be expanded out to 'decapsulation' for
  readability (across definitions and descriptions)
- Follow consistent capitalization of 'RIB' throughout document text.  =
Mixed
  use of 'Rib' and 'rib' exists (Outside of YANG node lowercase =
definitions).
- Is it necessary to prefix all nodes under the nexthop container with
  "nexthop-"?
- Section 2.5 - route-add RPC - text mentions it is required that the =
nh-add
  RPC be called as a pre-requisite however if the nh already exists and =
the
  nexthop-id is known, this should not be necessary.  In addition, the =
text
  reads 'or return' which should rather be a result of querying the
  appropriate node in the data tree.
- In 'IANA Considerations' - s/This document requests to register/This
  document registers/



From nobody Thu Jan 18 01:58:56 2018
Return-Path: <amit.dass@ericsson.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B097C1200C5; Thu, 18 Jan 2018 01:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 w4FPGOVUsKPv; Thu, 18 Jan 2018 01:58:42 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 977BF12EB20; Thu, 18 Jan 2018 01:58:41 -0800 (PST)
X-AuditID: c1b4fb25-473ff7000000341b-c9-5a606fcf2550
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 47.DB.13339.FCF606A5; Thu, 18 Jan 2018 10:58:39 +0100 (CET)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.72) with Microsoft SMTP Server (TLS) id 14.3.352.0; Thu, 18 Jan 2018 10:58:38 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gj9a64SAcIOWwzSaIPb3L8UWhHjs0qlvC+qmAMKM8sQ=; b=KCJRWaTxc2PpqFnZGIdYiGo3XkY2AqG8hNkS73m03Zw2eATWg4bQ3O38ZRzX7xZDh0OOIKc5/MBnwWv0Hgkgmiy7hSe/nHTBeFWUc09kqjIA/R8LTyaFfkhct/iIus5afVv+863gdpKmME1nqBjojD+HdiXqBcJC+jq2MO7DXRM=
Received: from HE1PR0702MB3580.eurprd07.prod.outlook.com (52.133.6.15) by HE1PR0702MB3707.eurprd07.prod.outlook.com (52.133.6.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.9; Thu, 18 Jan 2018 09:58:38 +0000
Received: from HE1PR0702MB3580.eurprd07.prod.outlook.com ([fe80::40cf:6d37:eed9:864d]) by HE1PR0702MB3580.eurprd07.prod.outlook.com ([fe80::40cf:6d37:eed9:864d%13]) with mapi id 15.20.0428.014; Thu, 18 Jan 2018 09:58:38 +0000
From: Amit Dass <amit.dass@ericsson.com>
To: Susan Hares <shares@ndzh.com>, 'Ebben Aries' <exa@juniper.net>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "i2rs@ietf.org" <i2rs@ietf.org>, "draft-ietf-i2rs-rib-data-model.all@ietf.org" <draft-ietf-i2rs-rib-data-model.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09
Thread-Index: AQHTkDcKZ8fIlvBx70ukLYUj3ljGR6N5YyEAgAABQ4CAAABJ4A==
Date: Thu, 18 Jan 2018 09:58:37 +0000
Message-ID: <HE1PR0702MB358050A9745D827C522AB23993E80@HE1PR0702MB3580.eurprd07.prod.outlook.com>
References: <151626438402.10775.7250014155413667607@ietfa.amsl.com> <HE1PR0702MB35806D6985E0A7754F840EE193E80@HE1PR0702MB3580.eurprd07.prod.outlook.com> <009801d39042$6a4b08e0$3ee11aa0$@ndzh.com>
In-Reply-To: <009801d39042$6a4b08e0$3ee11aa0$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.176.1.92]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; HE1PR0702MB3707; 7:RRzNroEAMkZRlCLMILfPlNx82F+L9bcKRHDTwlkg6yxkB/srJfNdG2xgWZ1OmVpMDJVY7EfmPDoBuDGiUhA7CQc/5S9RViG64AC+E1kWvpjkJPWJI8TJGRpelDiir7dIDTZa4uEjv7vK+j8LEOXYgQYaI0FZV6HZ44XddDB/XdpSijj45xT9SzV2Vxmp4b8yO3YDB7o3T37HyxaELVAavrrOLt4PdFre0XSC+JuPBYwmxAHBXWfsF9SkeVkCbxNm
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: b98f47b0-c121-4c1e-6ceb-08d55e5a0bc0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534125)(4602075)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:HE1PR0702MB3707; 
x-ms-traffictypediagnostic: HE1PR0702MB3707:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=amit.dass@ericsson.com; 
x-microsoft-antispam-prvs: <HE1PR0702MB3707BAB0DF54E52E80B8F35E93E80@HE1PR0702MB3707.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(192374486261705)(138986009662008); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040492)(2401047)(8121501046)(5005006)(3231046)(2400059)(944501161)(93006095)(93001095)(10201501046)(3002001)(6041279)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011); SRVR:HE1PR0702MB3707; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:HE1PR0702MB3707; 
x-forefront-prvs: 05568D1FF7
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(396003)(376002)(366004)(39380400002)(13464003)(199004)(189003)(3660700001)(966005)(5250100002)(2501003)(5660300001)(14454004)(2950100002)(33656002)(66066001)(8676002)(68736007)(316002)(81166006)(106356001)(8936002)(97736004)(2906002)(26005)(81156014)(53546011)(55016002)(7736002)(3280700002)(110136005)(53936002)(7696005)(305945005)(86362001)(8666007)(229853002)(1941001)(230783001)(99286004)(6436002)(25786009)(6116002)(3846002)(59450400001)(9686003)(54906003)(6506007)(6246003)(102836004)(105586002)(4326008)(76176011)(74316002)(478600001)(2900100001)(6306002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0702MB3707; H:HE1PR0702MB3580.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 08hpFR9rG9sDJLBxLf9QqcFdrIb2K7LEy/3Q4HPvFTzF3kSL8dJJ2+kAY/+q0UTvDDKA5gqrb5PEuhvD/USfrQ==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b98f47b0-c121-4c1e-6ceb-08d55e5a0bc0
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Jan 2018 09:58:37.9083 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3707
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTYRTHefa+215lgyfzcnAaNhIrmmatGlFR9mUmRkIfUqQ288VJ08k7 HWpCOoXKTBTM6QpNWnmpeWNTm1JqhJq31GoZUabm8hZKkWh22XwN+vY753/Oef7n8FCERwXX l0pMTqWZZKVazHMny8+1yiXDGkXM3sKXEtlkbSNHNvvQSsrqy5ZI2UxTJSlbX5gjZYW2TnSc JzeZVjlyu/41X3573s49Q8S4H4mn1Yk6mgk5pnBXXf8ygVI6D6b/0Y+gbFRwIB+5UYClkPej k8hH7pQHfoag3vKKZINeBFUWM3IFJL5JQM21GR6rGDgwvmLgsoEDQb/+DuEaxsM7wVxtJV3s idOgZSyX7yoicDWCpYGaDWErPgU5j8s2iyJgYtnOZTkMFlfb+S4mcSCU3KjaGCrECnhg/M5n X+tB0DVqcgoU5YYPwXObv6sGYW9YefGI42IC+8C76UoOux0GU8cwwbIXzE795rIcAOujkzyW /WG08sbGnoBbONA4WMRnhWCwFi8iliPhaX8LyRaNIWgdMG5O2gMjxU94rItoaJjs5bvMAdZA xbeTLMZCdlEU29pGwJzp46Y5P8gZKSaLUIjxP99GZwuBd0GDbTO93XmKT3zjxim2QF/5NHkX kXXIS0tr45IS9u0PppnEi1qtJjk4mU5tRs5f02X5GdiGxhZOdCNMIbFAuHZaEePBVeq0GUnd CChC7Cn8GuFMCeOVGZk0o7nApKlpbTcSUaTYR9gXLozxwAnKVPoSTafQzD+VQ7n5ZiPBkCCL bjIXOZjmppKpoPqwy/OiHsxdlr73FUXH1vCH4kbLHKp0v0zDWp6U26/zb3Lc+3D11njdedGb lMpeS9jhgKPloQk2NaFX/JKWdunaC97KmfuGWhQ5pgqUbBvMsJrPfnbQ4VUz4Vm5koYFu19t h72hNOiKIMo7b8eymNSqlKG7CUar/AsPP2gxMQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/7FXd8-kYSCOiSBeuHYtgzCN9VQg>
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-i2rs-rib-data-model-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jan 2018 09:58:45 -0000

SGkgU3VlLA0KDQpJIGV4cGVjdCB0byBoYXZlIHNvbWUgZnJlZSB0aW1lIGR1cmluZyB0aGlzIHdl
ZWsuICBTaG91bGQgYmUgYWJsZSB0byBzZW5kIHRoZSB1cGRhdGUgYnkgTW9uZGF5IG5leHQgd2Vl
ay4NCg0KQmVzdCByZWdhcmRzLA0KQW1pdA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogU3VzYW4gSGFyZXMgW21haWx0bzpzaGFyZXNAbmR6aC5jb21dIA0KU2VudDogVGh1cnNk
YXksIEphbnVhcnkgMTgsIDIwMTggMTA6NTUgQU0NClRvOiBBbWl0IERhc3MgPGFtaXQuZGFzc0Bl
cmljc3Nvbi5jb20+OyAnRWJiZW4gQXJpZXMnIDxleGFAanVuaXBlci5uZXQ+OyB5YW5nLWRvY3Rv
cnNAaWV0Zi5vcmcNCkNjOiBpMnJzQGlldGYub3JnOyBkcmFmdC1pZXRmLWkycnMtcmliLWRhdGEt
bW9kZWwuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSRTogWWFuZ2RvY3Rv
cnMgZWFybHkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaTJycy1yaWItZGF0YS1tb2RlbC0wOQ0KDQpB
bWl0Og0KDQpEbyB5b3UgdGhpbmsgeW91IGFuZCB5b3VyIGNvLWF1dGhvcnMgY2FuIGRvIHRoaXMg
d2l0aGluIGEgZmV3IGRheXMuICAgSSB3b3VsZCBsaWtlIHRvIGZvcndhcmQgdGhlIHB1YmxpY2F0
aW9uIHJlcXVlc3QuIA0KDQpBbHNvLCBwbGVhc2UgcmVtZW1iZXIgdG8gbG9vayBhdCB0aGUgbGF0
ZXN0IFJldmlzZWQgZGF0YXN0b3JlIGRyYWZ0IGFuZCB5YW5nIHRyZWUgbW9kdWxlIGRyYWZ0cy4g
DQoNClN1ZSBIYXJlcyANCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEFtaXQg
RGFzcyBbbWFpbHRvOmFtaXQuZGFzc0Blcmljc3Nvbi5jb21dIA0KU2VudDogVGh1cnNkYXksIEph
bnVhcnkgMTgsIDIwMTggNDo1MyBBTQ0KVG86IEViYmVuIEFyaWVzOyB5YW5nLWRvY3RvcnNAaWV0
Zi5vcmcNCkNjOiBpMnJzQGlldGYub3JnOyBkcmFmdC1pZXRmLWkycnMtcmliLWRhdGEtbW9kZWwu
YWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSRTogWWFuZ2RvY3RvcnMgZWFy
bHkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaTJycy1yaWItZGF0YS1tb2RlbC0wOQ0KDQpUaGFua3Mg
RWJiZW4gZm9yIHJldmlld2luZyB0aGUgZHJhZnQuIEkgd2lsbCB1cGRhdGUgdGhlIHNhbWUgYmFz
ZWQgb24gYmVsb3cgY29tbWVudHMgYW5kIGZlZWRiYWNrLg0KDQoNCkJlc3QgcmVnYXJkcywNCkFt
aXQNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEViYmVuIEFyaWVzIFttYWls
dG86ZXhhQGp1bmlwZXIubmV0XSANClNlbnQ6IFRodXJzZGF5LCBKYW51YXJ5IDE4LCAyMDE4IDk6
MzMgQU0NClRvOiB5YW5nLWRvY3RvcnNAaWV0Zi5vcmcNCkNjOiBpMnJzQGlldGYub3JnOyBkcmFm
dC1pZXRmLWkycnMtcmliLWRhdGEtbW9kZWwuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQpT
dWJqZWN0OiBZYW5nZG9jdG9ycyBlYXJseSByZXZpZXcgb2YgZHJhZnQtaWV0Zi1pMnJzLXJpYi1k
YXRhLW1vZGVsLTA5DQoNClJldmlld2VyOiBFYmJlbiBBcmllcw0KUmV2aWV3IHJlc3VsdDogT24g
dGhlIFJpZ2h0IFRyYWNrDQoNCjEgbW9kdWxlIGluIHRoaXMgZHJhZnQ6DQotIGlldGYtaTJycy1y
aWJAMjAxNy0xMi0wNS55YW5nDQoNCk5vIFlBTkcgdmFsaWRhdGlvbiBlcnJvcnMgb3Igd2Fybmlu
Z3MgKGZyb20gcHlhbmcgMS43LjMgYW5kIHlhbmdsaW50IDAuMTQuNTkpDQoNCjAgZXhhbXBsZXMg
YXJlIHByb3ZpZGVkIGluIHRoaXMgZHJhZnQgKHNlY3Rpb24gMy4xMiBvZg0KZHJhZnQtaWV0Zi1u
ZXRtb2QtcmZjNjA4N2Jpcy0xNSkNCg0KTW9kdWxlIGlldGYtaTJycy1yaWJAMjAxNy0xMi0wNS55
YW5nOg0KLSB5YW5nLXZlcnNpb24gc3RhdGVtZW50IG1pc3NpbmcgLSBzaG91bGQgYmUgMS4xDQot
IHByZWZpeCAnaWlyJyBpcyByZWNvbW1lbmRlZCBmb3IgdGhpcyBtb2R1bGUsIHdvdWxkICdyaWIn
IHN1ZmZpY2UgYmV0dGVyPw0KLSBpbXBvcnQgImlldGYtaW5ldC10eXBlcyIgc2hvdWxkIHJlZmVy
ZW5jZSBSRkMgNjk5MSBwZXIgKG5vdCBhcyBhIGNvbW1lbnQpDQogIGh0dHBzOi8vdG9vbHMuaWV0
Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW5ldG1vZC1yZmM2MDg3YmlzLTE1I3NlY3Rpb24tNC43DQot
IGltcG9ydCAiaWV0Zi1pbnRlcmZhY2VzIiBzaG91bGQgcmVmZXJlbmNlIFJGQyA3MjIzIHBlcg0K
ICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1uZXRtb2QtcmZjNjA4N2Jp
cy0xNSNzZWN0aW9uLTQuNw0KLSBpbXBvcnQgImlldGYteWFuZy10eXBlcyIgc2hvdWxkIHJlZmVy
ZW5jZSBSRkMgNjk5MSBwZXINCiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWll
dGYtbmV0bW9kLXJmYzYwODdiaXMtMTUjc2VjdGlvbi00LjcNCi0gU2luY2UgdGhpcyBtb2R1bGUg
aW1wb3J0cyAiaWV0Zi1pbnRlcmZhY2VzIiwgYSBub3JtYXRpdmUgcmVmZXJlbmNlcyBtdXN0IGJl
DQogIGFkZGVkIHBlcg0KICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1u
ZXRtb2QtcmZjNjA4N2Jpcy0xNSNzZWN0aW9uLTMuOQ0KLSBwcmVmaXggImlmIiBpbiB0aGUgaW1w
b3J0ICJpZXRmLWludGVyZmFjZXMiIGNhbiByZW1vdmUgcXVvdGVzIHRvIHJlbWFpbg0KICBjb25z
aXN0ZW50IHdpdGggb3RoZXIgaW1wb3J0cw0KLSBSZW1vdmUgV0cgQ2hhaXJzIGZyb20gY29udGFj
dCBpbmZvcm1hdGlvbiBwZXINCiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWll
dGYtbmV0bW9kLXJmYzYwODdiaXMtMTUjYXBwZW5kaXgtQw0KLSBNb2R1bGUgZGVzY3JpcHRpb24g
bXVzdCBjb250YWluIG1vc3QgcmVjZW50IGNvcHlyaWdodCBub3RpY2UgcGVyDQogIGh0dHBzOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW5ldG1vZC1yZmM2MDg3YmlzLTE1I2FwcGVu
ZGl4LUMNCi0gTW9kdWxlIGRlc2NyaXB0aW9uIHNob3VsZCBjb250YWluIG5vdGUgdG8gUkZDIEVk
LiBhbmQgcGxhY2Vob2xkZXIgcmVmZXJlbmNlDQogIHRvIFJGQyB3aGVuIGFzc2lnbmVkDQogIGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW5ldG1vZC1yZmM2MDg3YmlzLTE1
I2FwcGVuZGl4LUMNCi0gQWRkIHBsYWNlaG9sZGVyIHJlZmVyZW5jZSBhbmQgbm90ZSB0byBSRkMg
RWQuIGZvciBSRkMgd2hlbiBhc3NpZ25lZA0KICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtaWV0Zi1uZXRtb2QtcmZjNjA4N2Jpcy0xNSNhcHBlbmRpeC1DDQotIFNlY3VyaXR5IENv
bnNpZGVyYXRpb25zIHNob3VsZCBiZSB1cGRhdGVkIHRvIHJlZmxlY3QgbmV3IHRlbXBsYXRlIGF0
DQogIGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL29wcy93aWtpL3lhbmctc2VjdXJpdHktZ3Vp
ZGVsaW5lcw0KLSBTZWN0aW9uIDEuMiBzaG91bGQgYmUgcmVwbGFjZWQgd2l0aCByZWZlcmVuY2Ug
dG8NCiAgZHJhZnQtaWV0Zi1uZXRtb2QteWFuZy10cmVlLWRpYWdyYW1zLTAyIHJhdGhlciAoYXMt
aXMgaW4gb3RoZXIgaTJycyBZQU5HDQogIGRyYWZ0cyBpbiBwcm9ncmVzcykgcGVyDQogIGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW5ldG1vZC1yZmM2MDg3YmlzLTE1I3Nl
Y3Rpb24tMi41LjENCi0gVGhpcyBtb2R1bGUgY29udGFpbnMgJzEyJyBmZWF0dXJlcy4gIFdoaWxl
IGl0IGlzIHVuZGVyc3Rvb2QgdGhlIHB1cnBvc2Ugb2YNCiAgdGhlc2UgZmVhdHVyZXMgaW4gdGhl
IG1vZHVsZSwgdGFrZSBwcmVjYXV0aW9uIGFzIHRvIGNvbXBsZXhpdHkgZm9yIGNsaWVudHMNCiAg
aWYgdGhleSBuZWVkIHRvIHVuZGVyc3RhbmQgPj0gcXVhbnRpdHkgb2YgZmVhdHVyZXMgcGVyIG1v
ZHVsZSBpbiB1c2Ugb24gYQ0KICBuZXR3b3JrLWVsZW1lbnQuDQotIEEgZmV3IGNvbW1lbnRzIGV4
aXN0IHRoYXQgYXJlIGVpdGhlciB1bmVjZXNzYXJ5IG9yIHJlZHVuZGFudC4gIEVuY29kZSB0aGUN
CiAgY29tbWVudCBpbnRlbnQgcmF0aGVyIGluIGRlc2NyaXB0aW9uIGZpZWxkcyBpZiBuZWVkIGJl
Lg0KLSBQZXIgTk1EQSwgd2hpY2ggZGF0YXN0b3JlcyBhcmUgdGFyZ2V0ZWQgZm9yIHRoZSBtb2R1
bGU/ICBXaWxsIGFsbCBSUEMNCiAgb3BlcmF0aW9ucyBiZSBhY3RpbmcgdXBvbiB0aGUgZHluYW1p
Yy9lcGhlbWVyYWwgZGF0YXN0b3JlPyAgSXQgaXMgbm90IGNsZWFyDQogIHRvIG1lIGlmIHRoZSBp
bnRlbnRpb24gaXMgdG8gYmUgcGVyc2lzdGVudCBvciBlcGhlbWVyYWwNCg0KR2VuZXJhbCBjb21t
ZW50cy9OaXRzOg0KLSByZWZlcmVuY2VzIHRvICdkZWYnIGNvdWxkIGJlIGV4cGFuZGVkIG91dCB0
byAnZGVmaW5pdGlvbicNCi0gcmVmZXJlbmNlcyB0byAnZGVjYXAnIGNvdWxkIGJlIGV4cGFuZGVk
IG91dCB0byAnZGVjYXBzdWxhdGlvbicgZm9yDQogIHJlYWRhYmlsaXR5IChhY3Jvc3MgZGVmaW5p
dGlvbnMgYW5kIGRlc2NyaXB0aW9ucykNCi0gRm9sbG93IGNvbnNpc3RlbnQgY2FwaXRhbGl6YXRp
b24gb2YgJ1JJQicgdGhyb3VnaG91dCBkb2N1bWVudCB0ZXh0LiAgTWl4ZWQNCiAgdXNlIG9mICdS
aWInIGFuZCAncmliJyBleGlzdHMgKE91dHNpZGUgb2YgWUFORyBub2RlIGxvd2VyY2FzZSBkZWZp
bml0aW9ucykuDQotIElzIGl0IG5lY2Vzc2FyeSB0byBwcmVmaXggYWxsIG5vZGVzIHVuZGVyIHRo
ZSBuZXh0aG9wIGNvbnRhaW5lciB3aXRoDQogICJuZXh0aG9wLSI/DQotIFNlY3Rpb24gMi41IC0g
cm91dGUtYWRkIFJQQyAtIHRleHQgbWVudGlvbnMgaXQgaXMgcmVxdWlyZWQgdGhhdCB0aGUgbmgt
YWRkDQogIFJQQyBiZSBjYWxsZWQgYXMgYSBwcmUtcmVxdWlzaXRlIGhvd2V2ZXIgaWYgdGhlIG5o
IGFscmVhZHkgZXhpc3RzIGFuZCB0aGUNCiAgbmV4dGhvcC1pZCBpcyBrbm93biwgdGhpcyBzaG91
bGQgbm90IGJlIG5lY2Vzc2FyeS4gIEluIGFkZGl0aW9uLCB0aGUgdGV4dA0KICByZWFkcyAnb3Ig
cmV0dXJuJyB3aGljaCBzaG91bGQgcmF0aGVyIGJlIGEgcmVzdWx0IG9mIHF1ZXJ5aW5nIHRoZQ0K
ICBhcHByb3ByaWF0ZSBub2RlIGluIHRoZSBkYXRhIHRyZWUuDQotIEluICdJQU5BIENvbnNpZGVy
YXRpb25zJyAtIHMvVGhpcyBkb2N1bWVudCByZXF1ZXN0cyB0byByZWdpc3Rlci9UaGlzDQogIGRv
Y3VtZW50IHJlZ2lzdGVycy8NCg0KDQo=


From nobody Mon Jan 22 07:37:02 2018
Return-Path: <lhotka@nic.cz>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 711D812426E for <yang-doctors@ietfa.amsl.com>; Mon, 22 Jan 2018 07:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 8Tn4aZbcQjT5 for <yang-doctors@ietfa.amsl.com>; Mon, 22 Jan 2018 07:36:58 -0800 (PST)
Received: from trail.lhotka.name (trail.lhotka.name [77.48.224.143]) by ietfa.amsl.com (Postfix) with ESMTP id AB222124207 for <yang-doctors@ietf.org>; Mon, 22 Jan 2018 07:36:57 -0800 (PST)
Received: by trail.lhotka.name (Postfix, from userid 109) id 9F9CC1820415; Mon, 22 Jan 2018 16:36:43 +0100 (CET)
Received: from localhost (unknown [195.113.220.121]) by trail.lhotka.name (Postfix) with ESMTPSA id 2C964182040D; Mon, 22 Jan 2018 16:36:38 +0100 (CET)
From: Ladislav Lhotka <lhotka@nic.cz>
To: Michal =?utf-8?Q?Va=C5=A1ko?= <mvasko@cesnet.cz>, Andy Bierman <andy@yumaworks.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, YANG Doctors <yang-doctors@ietf.org>
In-Reply-To: <923-5a4b4280-29-4f262000@198821908>
References: <923-5a4b4280-29-4f262000@198821908>
Date: Mon, 22 Jan 2018 16:36:50 +0100
Message-ID: <871sihnbvx.fsf@nic.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/WFYFMdv74MQ98TF8lkSeKSIIiR8>
Subject: Re: [yang-doctors] Fwd: Re: Issue with ietf-dslite@2017-11-15.yang and yangdump-pro
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2018 15:37:01 -0000

Michal Va=C5=A1ko <mvasko@cesnet.cz> writes:

> Hello everyone,
>
> we would like to clarify a few things from this discussion. We are
> displaying some warnings in case of some almost-certainly invalid
> XPath expressions so we were wondering if it makes sense to add
> another if we detect an equality comparison of an identityref and an
> identity name without the use of derived-from(-or-self)() functions.

Certainly for YANG 1.1 modules.

>
> Another issue, "local module" has no formal definition as was
> mentioned. One can infer it is the module where the statement in
> question is defined but a definition would be appreciated. The same
> problem is with the term "current module" which it seems can be used
> interchangeably. Lastly, "current node" has no definition either and
> so we assumed it to be the node returned by the function current().

As I already proposed, it would be better to declare the result of such
comparisons as undefined.

Lada

>
> Kind regards,
> Michal
>
> On Monday, December 25, 2017 20:14 CET, Andy Bierman <andy@yumaworks.com>=
 wrote:=20
>=20=20
>> On Mon, Dec 25, 2017 at 10:53 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:
>>=20
>> > On Sun, 2017-12-24 at 18:54 -0300, Mahesh Jethanandani wrote:
>> > > > On Dec 23, 2017, at 10:49 AM, Martin Bjorklund <mbj@tail-f.com> wr=
ote:
>> > > >
>> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
>> > > > > > On Sat, 2017-12-23 at 13:01 +0100, Martin Bjorklund wrote:
>> > > > > > Andy Bierman <andy@yumaworks.com> wrote:
>> > > > > > > > On Sat, Dec 23, 2017 at 2:21 AM, Martin Bjorklund <
>> > mbj@tail-f.com>
>> > > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > Hi,
>> > > > > > > >
>> > > > > > > > See section 9.10.3 in RFC 7950:
>> > > > > > > >
>> > > > > > > >   The string value of a node of type "identityref" in a "m=
ust"
>> > or
>> > > > > > > >   "when" XPath expression is the referred identity's quali=
fied
>> > name
>> > > > > > > >   with the prefix present.
>> > > > > > > >
>> > > > > > > > and re. the prefix:
>> > > > > > > >
>> > > > > > > >   If the referred identity is defined in an
>> > > > > > > >   imported module, the prefix in the string value is the p=
refix
>> > > > > > > > defined
>> > > > > > > >   in the corresponding "import" statement.  Otherwise, the
>> > prefix in
>> > > > > > > >   the string value is the prefix for the current module.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > I most cases you should consider using derived-from-or-self
>> > instead
>> > > > > > > > of
>> > > > > > > > equality test for identiyrefs.
>> > > > > > >
>> > > > > > > So what is "the current module"?
>> > > > > > > What is the resolution of 'X'? Is it foo:X or bar:X?
>> > > > > >
>> > > > > > foo:X
>> > > > >
>> > > > > No, the resolution of 'X' is 'X'
>> > > >
>> > > > Yes!  Sorry, I misread the question.  I though the question was wh=
at
>> > > > prefix should be used.
>> > >
>> > > The question started with a 'when' statement (which I understand sho=
uld
>> > be
>> > > changed to 'derived-from') using a identity name that is defined in =
the
>> > other
>> > > (bar) module. Should the 'derived-from' statement reference the iden=
tity
>> > using
>> > > the prefix 'b:X' or just 'X', using Andy's example?
>> >
>> > Both are possible in Andy's example, the former refers to the identity=
 "X"
>> > defined in module "bar", the latter refers to the identity "X" defined=
 in
>> > the
>> > local module ("foo").
>> >
>> >
>> I see the term "local module" used 11 times in RFC 7950, but it is not
>> defined anywhere.
>> IMO the only intuitive solution is that all scoped names are resolved in
>> the same module,
>> which is the module defining the actual statements. Is that the local
>> module?
>>=20
>>=20
>> Lada
>> >
>>=20
>>=20
>> Andy
>>=20
>>=20
>> >
>> > >
>> > > >
>> > > >
>> > > > /martin
>> > > >
>> > > >
>> > > > > because it is an XPath 1.0 string and XPath
>> > > > > knows nothing about YANG identities. Because of the rule of sec.
>> > 9.10.3,
>> > > > > the
>> > > > > equality expression is always false.
>> > > > >
>> > > > > That's why we introduced the new XPath functions derived-from() =
and
>> > > > > derived-
>> > > > > from-or-self() in YANG 1.1.
>> > > > >
>> > > > > Lada
>> > > > >
>> > > > > >
>> > > > > >
>> > > > > > /martin
>> > > > > >
>> > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > > > >
>> > > > > > > > /martin
>> > > > > > >
>> > > > > > > Andy
>> > > > > > >
>> > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > Andy Bierman <andy@yumaworks.com> wrote:
>> > > > > > > > > > On Fri, Dec 15, 2017 at 4:38 AM, Radek Krej=C4=8D=C3=
=AD <
>> > rkrejci@cesnet.cz
>> > > > > > > > > > > wrote:
>> > > > > > > > > >
>> > > > > > > > > > Hi,
>> > > > > > > > > > I'm adding Michal Vasko to cc, he knows better how the=
se
>> > things
>> > > > > > > > > > are
>> > > > > > > > > > checked in libyang.
>> > > > > > > > > >
>> > > > > > > > > > It seems to me that Andy refers the text which does not
>> > apply
>> > > > > > > > > > here.
>> > > > > > > > > > The
>> > > > > > > > > > identity name was used as part of XPath expresion
>> > (when-stmt),
>> > > > > > > > > > so the
>> > > > > > > > > > definition of the context nodes for the when-stmt (RFC
>> > 7950, sec
>> > > > > > > >
>> > > > > > > > 7.21.5)
>> > > > > > > > > > and XPath context rules should apply here. Not the rul=
es
>> > for the
>> > > > > > > > > > identityref's base statement. In this case, the when-s=
tmt
>> > is in
>> > > > > > > >
>> > > > > > > > augment so
>> > > > > > > > > > the context node (which we also understand as the curr=
ent
>> > node
>> > > > > > > > > > in this
>> > > > > > > > > > case) is the augment's target node. And according to X=
Path
>> > > > > > > > > > context
>> > > > > > > >
>> > > > > > > > rules
>> > > > > > > > > > (RFC 7950, sec 6.4.1):
>> > > > > > > > > >
>> > > > > > > > > > o  Names without a namespace prefix belong to the same
>> > namespace
>> > > > > > > > > > as
>> > > > > > > >
>> > > > > > > > the
>> > > > > > > > > > identifier of the current node.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > I cc:ed YANG doctors to get more opinions...
>> > > > > > > > >
>> > > > > > > > > The current node is the augment-stmt.
>> > > > > > > > > Note that it does not say context node, which is the tar=
get
>> > of the
>> > > > > > > >
>> > > > > > > > augment.
>> > > > > > > > > I think prefixes (and default prefix) are resolved in the
>> > module
>> > > > > > > >
>> > > > > > > > containing
>> > > > > > > > > the statement.
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > module foo {
>> > > > > > > > >
>> > > > > > > > >   import bar { prefix b; }
>> > > > > > > > >   identity X;
>> > > > > > > > >
>> > > > > > > > >   augment b:/some-node {
>> > > > > > > > >      leaf test {
>> > > > > > > > >         type string;
>> > > > > > > > >         when "/b:some-node/b:other-node =3D 'X'";
>> > > > > > > > >      }
>> > > > > > > > >   }
>> > > > > > > > > }
>> > > > > > > > >
>> > > > > > > > > module bar {
>> > > > > > > > >
>> > > > > > > > >   identity W;
>> > > > > > > > >   identity X { base W; }
>> > > > > > > > >   container some-node {
>> > > > > > > > >       leaf other-node {
>> > > > > > > > >         type identityref { base W; }
>> > > > > > > > >       }
>> > > > > > > > >   }
>> > > > > > > > > }
>> > > > > > > > >
>> > > > > > > > > Q) Does other-node =3D 'X' resolve to foo:X or bar:X?  I=
MO:
>> > foo:X
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > Andy
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > > In this particular case, the augment node with the
>> > when-stmt
>> > > > > > > > > > augments
>> > > > > > > >
>> > > > > > > > the
>> > > > > > > > > > same module which defines napt44, so they are in the
>> > correct
>> > > > > > > > > > namespace
>> > > > > > > >
>> > > > > > > > and
>> > > > > > > > > > the identity name can be used without the prefix. So it
>> > should
>> > > > > > > > > > be
>> > > > > > > > > > fine,
>> > > > > > > > > > while I believe that using prefix in the cases of
>> > identities is
>> > > > > > > > > > always
>> > > > > > > > > > better approach. From the first sight (it may be
>> > challenging for
>> > > > > > > > > > human
>> > > > > > > >
>> > > > > > > > to
>> > > > > > > > > > correctly resolve the context/current node in some cas=
es),
>> > I
>> > > > > > > > > > would
>> > > > > > > > > > also
>> > > > > > > > > > expect prefix.
>> > > > > > > > > >
>> > > > > > > > > > I propose to keep the change in the draft (added nat
>> > prefix),
>> > > > > > > > > > since it
>> > > > > > > > > > improves readability of the expression. But I don't th=
ink
>> > that
>> > > > > > > > > > it is
>> > > > > > > > > > an
>> > > > > > > > > > error to ommit the prefix.
>> > > > > > > > > >
>> > > > > > > > > > Regards,
>> > > > > > > > > > Radek
>> > > > > > > > > >
>> > > > > > > > > >
>> > > > > > > > > > Dne 19.11.2017 v 20:42 Benoit Claise napsal(a):
>> > > > > > > > > > > Hi Radek,
>> > > > > > > > > > >
>> > > > > > > > > > > Here is a bug report for you.
>> > > > > > > > > > >
>> > > > > > > > > > > Regards, Benoit
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > -------- Forwarded Message --------
>> > > > > > > > > > > Subject:      Re: Issue with ietf-dslite@2017-11-15.=
yang
>> > and
>> > > > > > > > > >
>> > > > > > > > > > yangdump-pro
>> > > > > > > > > > > Date:         Sat, 18 Nov 2017 13:22:58 -0800
>> > > > > > > > > > > From:         Andy Bierman <andy@yumaworks.com>
>> > > > > > > > > > > To:   Benoit Claise <bclaise@cisco.com>
>> > > > > > > > > > > CC:   draft-ietf-softwire-dslite-yang@ietf.org <
>> > > > > > > > > >
>> > > > > > > > > > draft-ietf-softwire-dslite-yang@ietf.org>, Mahesh
>> > Jethanandani <
>> > > > > > > > > > mjethanandani@gmail.com>
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > Hi,
>> > > > > > > > > > >
>> > > > > > > > > > > yangdump-pro is correct. Every other compiler missed
>> > it...
>> > > > > > > > > > >
>> > > > > > > > > > > 9.10.2.  The identityref's "base" Statement
>> > > > > > > > > > >
>> > > > > > > > > > >   The "base" statement, which is a substatement to t=
he
>> > "type"
>> > > > > > > > > > >   statement, MUST be present at least once if the ty=
pe is
>> > > > > > > > > > >   "identityref".  The argument is the name of an
>> > identity, as
>> > > > > > > >
>> > > > > > > > defined
>> > > > > > > > > > >   by an "identity" statement.  If a prefix is presen=
t on
>> > the
>> > > > > > > >
>> > > > > > > > identity
>> > > > > > > > > > >   name, it refers to an identity defined in the modu=
le
>> > that
>> > > > > > > > > > > was
>> > > > > > > > > > >   imported with that prefix.  *Otherwise, an identity
>> > with the
>> > > > > > > >
>> > > > > > > > matching
>> > > > > > > > > > name MUST be defined in the current module or an inclu=
ded
>> > > > > > > > > > submodule.*
>> > > > > > > > > > >
>> > > > > > > > > > > Using ietf-dslite@2017-11-15.yang and
>> > ietf-nat@2017-11-15.yang
>> > > > > > > > > > >
>> > > > > > > > > > > When I change 'natp44' to 'nat:natp44' in both
>> > when-stmts:
>> > > > > > > > > > >
>> > > > > > > > > > > andy@andy-homedev:~/Desktop/FD1289/IETF$ yangdump-pro
>> > > > > > > > > >
>> > > > > > > > > > ietf-dslite@2017-11-15.yang modpath=3D.
>> > > > > > > > > > >
>> > > > > > > > > > > *** /home/andy/Desktop/FD1289/
>> > IETF/ietf-dslite@2017-11-15.yang
>> > > > > > > > > > > *** 0 Errors, 0 Warnings
>> > > > > > > > > > >
>> > > > > > > > > > > andy@andy-homedev:~/Desktop/FD1289/IETF$
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > Andy
>> > > > > > > > > > >
>> > > > > > > > > > >
>> > > > > > > > > > > On Sat, Nov 18, 2017 at 11:07 AM, Benoit Claise
>> > <bclaise@cisco
>> > > > > > > > > > > .com
>> > > > > > > > > >
>> > > > > > > > > > <mailto:bclaise@cisco.com>> wrote:
>> > > > > > > > > > >
>> > > > > > > > > > >    Hi Andy,
>> > > > > > > > > > >
>> > > > > > > > > > >    Can you please have a look at
>> > ietf-dslite@2017-11-15.yang
>> > > > > > > > > > > at
>> > > > > > > > > >
>> > > > > > > > > > http://www.claise.be/IETFYANGPageCompilation.html <
>> > > > > > > >
>> > > > > > > > http://www.claise.be/
>> > > > > > > > > > IETFYANGPageCompilation.html> .
>> > > > > > > > > > >    yangdump-pro reports a new error, while the other
>> > > > > > > > > > > validators are
>> > > > > > > > > >
>> > > > > > > > > > fine.
>> > > > > > > > > > >
>> > > > > > > > > > >    Copying Mahesh, as YANG doctor.
>> > > > > > > > > > >
>> > > > > > > > > > >    Regards, Benoit
>> > > > > >
>> > > > > > _______________________________________________
>> > > > > > yang-doctors mailing list
>> > > > > > yang-doctors@ietf.org
>> > > > > > https://www.ietf.org/mailman/listinfo/yang-doctors
>> > > > >
>> > > > > --
>> > > > > Ladislav Lhotka
>> > > > > Head, CZ.NIC Labs
>> > > > > PGP Key ID: 0xB8F92B08A9F76C67
>> > > >
>> > > > _______________________________________________
>> > > > yang-doctors mailing list
>> > > > yang-doctors@ietf.org
>> > > > https://www.ietf.org/mailman/listinfo/yang-doctors
>> > --
>> > Ladislav Lhotka
>> > Head, CZ.NIC Labs
>> > PGP Key ID: 0xB8F92B08A9F76C67
>> >
>> > _______________________________________________
>> > yang-doctors mailing list
>> > yang-doctors@ietf.org
>> > https://www.ietf.org/mailman/listinfo/yang-doctors
>> >
>=20=20
>=20=20
>

--=20
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67


From nobody Mon Jan 22 08:27:22 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B883126DEE for <yang-doctors@ietfa.amsl.com>; Mon, 22 Jan 2018 08:27:20 -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 I2qoNkHLcLlt for <yang-doctors@ietfa.amsl.com>; Mon, 22 Jan 2018 08:27:15 -0800 (PST)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 18B2F124207 for <yang-doctors@ietf.org>; Mon, 22 Jan 2018 08:27:15 -0800 (PST)
Received: by mail-lf0-x22d.google.com with SMTP id g72so11340466lfg.5 for <yang-doctors@ietf.org>; Mon, 22 Jan 2018 08:27:15 -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=NX8mq1m70AWygQJO9oGpU04QPaBnqJYM+R5YMDmmGyM=; b=R+MRzSsUvxl+OrN/s8lzlWvgSzMy8ygLm458X6Y1OM2Djd6xCq1PH8EMtRfu30hW4F YDNMxcuYyrGAdqfZZ5DkXomNAHdzYkoQFYYQPPhyTJzXXSpOsaoDRfOr45X80/dReHQ0 P603SBr4P/l1BI6wvunrMbCNSp3EncY5vqqNiYJeCS1VAx/AGXnYQ/4LYCQHp7z9q+Vq dJpLg3f/nznRixL3q1tPZiDNfiaxYXYKPM5zSj5GM7Pww3VUQ4GVs8/x2tk6fVqKvJBK oc7CzfhRad1kvOHRj1LO9VbPzjrAZKlSeGE56lpJUBJSPP1QSaZCyj09G7Q5vGFPqSl2 iU8Q==
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=NX8mq1m70AWygQJO9oGpU04QPaBnqJYM+R5YMDmmGyM=; b=L2YvjtWanF+qlPAHx63AUYKizEAagxGQ4/H04Cg/jZsa1RhrArU5ZtSYOwM2FmRE2T EjOMIbv4q6qRiIC1Oa8ngqt+UK3dnx2o/TZtsfxh8XPvj9We5WIruZDdn1ed1ymXO2e+ joYdcItR1gvEYO/of1M8V5HbpBcoNV9gn/LnbZESDahpjzdUjPepHtd1r8IRFjGdQVY7 bCNpI4nV5H5Ve66q54VwesjIqmEU0qg2MNKlAv80e6xgNXPXff6xe/SNM6xaIRJimIYK BzdespNVIeT3hhEQpMAVQNSVwF892FbHm91KFem6UBtQZQcWye25HW9M1UQzZENBUnAk CmMA==
X-Gm-Message-State: AKwxytdx5Zmpla97XAiOUHwuInlHYr3zYfZj4bsZDDadWhOtkYHHFeKK pIJUf67v6tS3Bvd674EOL/nqVajSV5bZXYKdIhOHFA==
X-Google-Smtp-Source: AH8x227MdvAQkc5sgyxlPv8ONiJbqXbgZPrWR2goe3zdNEC9EYR6ao+wqpJrsRmH+jJiMrXPC5S2QoXtZDqCkeJ0RMw=
X-Received: by 10.25.190.203 with SMTP id o194mr2640244lff.120.1516638433271;  Mon, 22 Jan 2018 08:27:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.143.6 with HTTP; Mon, 22 Jan 2018 08:27:12 -0800 (PST)
In-Reply-To: <871sihnbvx.fsf@nic.cz>
References: <923-5a4b4280-29-4f262000@198821908> <871sihnbvx.fsf@nic.cz>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 22 Jan 2018 08:27:12 -0800
Message-ID: <CABCOCHTP1Bf+6sHqjifnPS_iZwjoY0wK9jTXRgp3xnNww-Bahg@mail.gmail.com>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: =?UTF-8?Q?Michal_Va=C5=A1ko?= <mvasko@cesnet.cz>,  Martin Bjorklund <mbj@tail-f.com>, Mahesh Jethanandani <mjethanandani@gmail.com>,  YANG Doctors <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1a185e117a2405635fe7f5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/-XyOQzXj1hJYKgfx2S0fXoTpIfU>
Subject: Re: [yang-doctors] Fwd: Re: Issue with ietf-dslite@2017-11-15.yang and yangdump-pro
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2018 16:27:20 -0000

--94eb2c1a185e117a2405635fe7f5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 22, 2018 at 7:36 AM, Ladislav Lhotka <lhotka@nic.cz> wrote:

> Michal Va=C5=A1ko <mvasko@cesnet.cz> writes:
>
> > Hello everyone,
> >
> > we would like to clarify a few things from this discussion. We are
> > displaying some warnings in case of some almost-certainly invalid
> > XPath expressions so we were wondering if it makes sense to add
> > another if we detect an equality comparison of an identityref and an
> > identity name without the use of derived-from(-or-self)() functions.
>
> Certainly for YANG 1.1 modules.
>
> >
> > Another issue, "local module" has no formal definition as was
> > mentioned. One can infer it is the module where the statement in
> > question is defined but a definition would be appreciated. The same
> > problem is with the term "current module" which it seems can be used
> > interchangeably. Lastly, "current node" has no definition either and
> > so we assumed it to be the node returned by the function current().
>
> As I already proposed, it would be better to declare the result of such
> comparisons as undefined.
>
>
Declaring policy based on undefined terms seems like a bad idea.
We have customers who have used "var =3D 'identity'" hundreds of  times
already
in their YANG modules.   Not a chance that I am going to tell them
to change the YANG or have the YANG compiler start rejecting
this most intuitive and common construct.


Lada
>
>
Andy


> >
> > Kind regards,
> > Michal
> >
> > On Monday, December 25, 2017 20:14 CET, Andy Bierman <andy@yumaworks.co=
m>
> wrote:
> >
> >> On Mon, Dec 25, 2017 at 10:53 AM, Ladislav Lhotka <lhotka@nic.cz>
> wrote:
> >>
> >> > On Sun, 2017-12-24 at 18:54 -0300, Mahesh Jethanandani wrote:
> >> > > > On Dec 23, 2017, at 10:49 AM, Martin Bjorklund <mbj@tail-f.com>
> wrote:
> >> > > >
> >> > > > Ladislav Lhotka <lhotka@nic.cz> wrote:
> >> > > > > > On Sat, 2017-12-23 at 13:01 +0100, Martin Bjorklund wrote:
> >> > > > > > Andy Bierman <andy@yumaworks.com> wrote:
> >> > > > > > > > On Sat, Dec 23, 2017 at 2:21 AM, Martin Bjorklund <
> >> > mbj@tail-f.com>
> >> > > > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > > Hi,
> >> > > > > > > >
> >> > > > > > > > See section 9.10.3 in RFC 7950:
> >> > > > > > > >
> >> > > > > > > >   The string value of a node of type "identityref" in a
> "must"
> >> > or
> >> > > > > > > >   "when" XPath expression is the referred identity's
> qualified
> >> > name
> >> > > > > > > >   with the prefix present.
> >> > > > > > > >
> >> > > > > > > > and re. the prefix:
> >> > > > > > > >
> >> > > > > > > >   If the referred identity is defined in an
> >> > > > > > > >   imported module, the prefix in the string value is the
> prefix
> >> > > > > > > > defined
> >> > > > > > > >   in the corresponding "import" statement.  Otherwise, t=
he
> >> > prefix in
> >> > > > > > > >   the string value is the prefix for the current module.
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > I most cases you should consider using
> derived-from-or-self
> >> > instead
> >> > > > > > > > of
> >> > > > > > > > equality test for identiyrefs.
> >> > > > > > >
> >> > > > > > > So what is "the current module"?
> >> > > > > > > What is the resolution of 'X'? Is it foo:X or bar:X?
> >> > > > > >
> >> > > > > > foo:X
> >> > > > >
> >> > > > > No, the resolution of 'X' is 'X'
> >> > > >
> >> > > > Yes!  Sorry, I misread the question.  I though the question was
> what
> >> > > > prefix should be used.
> >> > >
> >> > > The question started with a 'when' statement (which I understand
> should
> >> > be
> >> > > changed to 'derived-from') using a identity name that is defined i=
n
> the
> >> > other
> >> > > (bar) module. Should the 'derived-from' statement reference the
> identity
> >> > using
> >> > > the prefix 'b:X' or just 'X', using Andy's example?
> >> >
> >> > Both are possible in Andy's example, the former refers to the
> identity "X"
> >> > defined in module "bar", the latter refers to the identity "X"
> defined in
> >> > the
> >> > local module ("foo").
> >> >
> >> >
> >> I see the term "local module" used 11 times in RFC 7950, but it is not
> >> defined anywhere.
> >> IMO the only intuitive solution is that all scoped names are resolved =
in
> >> the same module,
> >> which is the module defining the actual statements. Is that the local
> >> module?
> >>
> >>
> >> Lada
> >> >
> >>
> >>
> >> Andy
> >>
> >>
> >> >
> >> > >
> >> > > >
> >> > > >
> >> > > > /martin
> >> > > >
> >> > > >
> >> > > > > because it is an XPath 1.0 string and XPath
> >> > > > > knows nothing about YANG identities. Because of the rule of se=
c.
> >> > 9.10.3,
> >> > > > > the
> >> > > > > equality expression is always false.
> >> > > > >
> >> > > > > That's why we introduced the new XPath functions derived-from(=
)
> and
> >> > > > > derived-
> >> > > > > from-or-self() in YANG 1.1.
> >> > > > >
> >> > > > > Lada
> >> > > > >
> >> > > > > >
> >> > > > > >
> >> > > > > > /martin
> >> > > > > >
> >> > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > >
> >> > > > > > > > /martin
> >> > > > > > >
> >> > > > > > > Andy
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > Andy Bierman <andy@yumaworks.com> wrote:
> >> > > > > > > > > > On Fri, Dec 15, 2017 at 4:38 AM, Radek Krej=C4=8D=C3=
=AD <
> >> > rkrejci@cesnet.cz
> >> > > > > > > > > > > wrote:
> >> > > > > > > > > >
> >> > > > > > > > > > Hi,
> >> > > > > > > > > > I'm adding Michal Vasko to cc, he knows better how
> these
> >> > things
> >> > > > > > > > > > are
> >> > > > > > > > > > checked in libyang.
> >> > > > > > > > > >
> >> > > > > > > > > > It seems to me that Andy refers the text which does
> not
> >> > apply
> >> > > > > > > > > > here.
> >> > > > > > > > > > The
> >> > > > > > > > > > identity name was used as part of XPath expresion
> >> > (when-stmt),
> >> > > > > > > > > > so the
> >> > > > > > > > > > definition of the context nodes for the when-stmt (R=
FC
> >> > 7950, sec
> >> > > > > > > >
> >> > > > > > > > 7.21.5)
> >> > > > > > > > > > and XPath context rules should apply here. Not the
> rules
> >> > for the
> >> > > > > > > > > > identityref's base statement. In this case, the
> when-stmt
> >> > is in
> >> > > > > > > >
> >> > > > > > > > augment so
> >> > > > > > > > > > the context node (which we also understand as the
> current
> >> > node
> >> > > > > > > > > > in this
> >> > > > > > > > > > case) is the augment's target node. And according to
> XPath
> >> > > > > > > > > > context
> >> > > > > > > >
> >> > > > > > > > rules
> >> > > > > > > > > > (RFC 7950, sec 6.4.1):
> >> > > > > > > > > >
> >> > > > > > > > > > o  Names without a namespace prefix belong to the sa=
me
> >> > namespace
> >> > > > > > > > > > as
> >> > > > > > > >
> >> > > > > > > > the
> >> > > > > > > > > > identifier of the current node.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > I cc:ed YANG doctors to get more opinions...
> >> > > > > > > > >
> >> > > > > > > > > The current node is the augment-stmt.
> >> > > > > > > > > Note that it does not say context node, which is the
> target
> >> > of the
> >> > > > > > > >
> >> > > > > > > > augment.
> >> > > > > > > > > I think prefixes (and default prefix) are resolved in
> the
> >> > module
> >> > > > > > > >
> >> > > > > > > > containing
> >> > > > > > > > > the statement.
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > module foo {
> >> > > > > > > > >
> >> > > > > > > > >   import bar { prefix b; }
> >> > > > > > > > >   identity X;
> >> > > > > > > > >
> >> > > > > > > > >   augment b:/some-node {
> >> > > > > > > > >      leaf test {
> >> > > > > > > > >         type string;
> >> > > > > > > > >         when "/b:some-node/b:other-node =3D 'X'";
> >> > > > > > > > >      }
> >> > > > > > > > >   }
> >> > > > > > > > > }
> >> > > > > > > > >
> >> > > > > > > > > module bar {
> >> > > > > > > > >
> >> > > > > > > > >   identity W;
> >> > > > > > > > >   identity X { base W; }
> >> > > > > > > > >   container some-node {
> >> > > > > > > > >       leaf other-node {
> >> > > > > > > > >         type identityref { base W; }
> >> > > > > > > > >       }
> >> > > > > > > > >   }
> >> > > > > > > > > }
> >> > > > > > > > >
> >> > > > > > > > > Q) Does other-node =3D 'X' resolve to foo:X or bar:X?
> IMO:
> >> > foo:X
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > Andy
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > >
> >> > > > > > > > > > In this particular case, the augment node with the
> >> > when-stmt
> >> > > > > > > > > > augments
> >> > > > > > > >
> >> > > > > > > > the
> >> > > > > > > > > > same module which defines napt44, so they are in the
> >> > correct
> >> > > > > > > > > > namespace
> >> > > > > > > >
> >> > > > > > > > and
> >> > > > > > > > > > the identity name can be used without the prefix. So
> it
> >> > should
> >> > > > > > > > > > be
> >> > > > > > > > > > fine,
> >> > > > > > > > > > while I believe that using prefix in the cases of
> >> > identities is
> >> > > > > > > > > > always
> >> > > > > > > > > > better approach. From the first sight (it may be
> >> > challenging for
> >> > > > > > > > > > human
> >> > > > > > > >
> >> > > > > > > > to
> >> > > > > > > > > > correctly resolve the context/current node in some
> cases),
> >> > I
> >> > > > > > > > > > would
> >> > > > > > > > > > also
> >> > > > > > > > > > expect prefix.
> >> > > > > > > > > >
> >> > > > > > > > > > I propose to keep the change in the draft (added nat
> >> > prefix),
> >> > > > > > > > > > since it
> >> > > > > > > > > > improves readability of the expression. But I don't
> think
> >> > that
> >> > > > > > > > > > it is
> >> > > > > > > > > > an
> >> > > > > > > > > > error to ommit the prefix.
> >> > > > > > > > > >
> >> > > > > > > > > > Regards,
> >> > > > > > > > > > Radek
> >> > > > > > > > > >
> >> > > > > > > > > >
> >> > > > > > > > > > Dne 19.11.2017 v 20:42 Benoit Claise napsal(a):
> >> > > > > > > > > > > Hi Radek,
> >> > > > > > > > > > >
> >> > > > > > > > > > > Here is a bug report for you.
> >> > > > > > > > > > >
> >> > > > > > > > > > > Regards, Benoit
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > > > -------- Forwarded Message --------
> >> > > > > > > > > > > Subject:      Re: Issue with
> ietf-dslite@2017-11-15.yang
> >> > and
> >> > > > > > > > > >
> >> > > > > > > > > > yangdump-pro
> >> > > > > > > > > > > Date:         Sat, 18 Nov 2017 13:22:58 -0800
> >> > > > > > > > > > > From:         Andy Bierman <andy@yumaworks.com>
> >> > > > > > > > > > > To:   Benoit Claise <bclaise@cisco.com>
> >> > > > > > > > > > > CC:   draft-ietf-softwire-dslite-yang@ietf.org <
> >> > > > > > > > > >
> >> > > > > > > > > > draft-ietf-softwire-dslite-yang@ietf.org>, Mahesh
> >> > Jethanandani <
> >> > > > > > > > > > mjethanandani@gmail.com>
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > > > Hi,
> >> > > > > > > > > > >
> >> > > > > > > > > > > yangdump-pro is correct. Every other compiler miss=
ed
> >> > it...
> >> > > > > > > > > > >
> >> > > > > > > > > > > 9.10.2.  The identityref's "base" Statement
> >> > > > > > > > > > >
> >> > > > > > > > > > >   The "base" statement, which is a substatement to
> the
> >> > "type"
> >> > > > > > > > > > >   statement, MUST be present at least once if the
> type is
> >> > > > > > > > > > >   "identityref".  The argument is the name of an
> >> > identity, as
> >> > > > > > > >
> >> > > > > > > > defined
> >> > > > > > > > > > >   by an "identity" statement.  If a prefix is
> present on
> >> > the
> >> > > > > > > >
> >> > > > > > > > identity
> >> > > > > > > > > > >   name, it refers to an identity defined in the
> module
> >> > that
> >> > > > > > > > > > > was
> >> > > > > > > > > > >   imported with that prefix.  *Otherwise, an
> identity
> >> > with the
> >> > > > > > > >
> >> > > > > > > > matching
> >> > > > > > > > > > name MUST be defined in the current module or an
> included
> >> > > > > > > > > > submodule.*
> >> > > > > > > > > > >
> >> > > > > > > > > > > Using ietf-dslite@2017-11-15.yang and
> >> > ietf-nat@2017-11-15.yang
> >> > > > > > > > > > >
> >> > > > > > > > > > > When I change 'natp44' to 'nat:natp44' in both
> >> > when-stmts:
> >> > > > > > > > > > >
> >> > > > > > > > > > > andy@andy-homedev:~/Desktop/FD1289/IETF$
> yangdump-pro
> >> > > > > > > > > >
> >> > > > > > > > > > ietf-dslite@2017-11-15.yang modpath=3D.
> >> > > > > > > > > > >
> >> > > > > > > > > > > *** /home/andy/Desktop/FD1289/
> >> > IETF/ietf-dslite@2017-11-15.yang
> >> > > > > > > > > > > *** 0 Errors, 0 Warnings
> >> > > > > > > > > > >
> >> > > > > > > > > > > andy@andy-homedev:~/Desktop/FD1289/IETF$
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > > > Andy
> >> > > > > > > > > > >
> >> > > > > > > > > > >
> >> > > > > > > > > > > On Sat, Nov 18, 2017 at 11:07 AM, Benoit Claise
> >> > <bclaise@cisco
> >> > > > > > > > > > > .com
> >> > > > > > > > > >
> >> > > > > > > > > > <mailto:bclaise@cisco.com>> wrote:
> >> > > > > > > > > > >
> >> > > > > > > > > > >    Hi Andy,
> >> > > > > > > > > > >
> >> > > > > > > > > > >    Can you please have a look at
> >> > ietf-dslite@2017-11-15.yang
> >> > > > > > > > > > > at
> >> > > > > > > > > >
> >> > > > > > > > > > http://www.claise.be/IETFYANGPageCompilation.html <
> >> > > > > > > >
> >> > > > > > > > http://www.claise.be/
> >> > > > > > > > > > IETFYANGPageCompilation.html> .
> >> > > > > > > > > > >    yangdump-pro reports a new error, while the oth=
er
> >> > > > > > > > > > > validators are
> >> > > > > > > > > >
> >> > > > > > > > > > fine.
> >> > > > > > > > > > >
> >> > > > > > > > > > >    Copying Mahesh, as YANG doctor.
> >> > > > > > > > > > >
> >> > > > > > > > > > >    Regards, Benoit
> >> > > > > >
> >> > > > > > _______________________________________________
> >> > > > > > yang-doctors mailing list
> >> > > > > > yang-doctors@ietf.org
> >> > > > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> >> > > > >
> >> > > > > --
> >> > > > > Ladislav Lhotka
> >> > > > > Head, CZ.NIC Labs
> >> > > > > PGP Key ID: 0xB8F92B08A9F76C67
> >> > > >
> >> > > > _______________________________________________
> >> > > > yang-doctors mailing list
> >> > > > yang-doctors@ietf.org
> >> > > > https://www.ietf.org/mailman/listinfo/yang-doctors
> >> > --
> >> > Ladislav Lhotka
> >> > Head, CZ.NIC Labs
> >> > PGP Key ID: 0xB8F92B08A9F76C67
> >> >
> >> > _______________________________________________
> >> > yang-doctors mailing list
> >> > yang-doctors@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/yang-doctors
> >> >
> >
> >
> >
>
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>

--94eb2c1a185e117a2405635fe7f5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Mon, Jan 22, 2018 at 7:36 AM, Ladislav Lhotka <span dir=3D"ltr">&lt;=
<a href=3D"mailto:lhotka@nic.cz" target=3D"_blank">lhotka@nic.cz</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Michal Va=C5=A1ko &lt;<a href=
=3D"mailto:mvasko@cesnet.cz">mvasko@cesnet.cz</a>&gt; writes:<br>
<br>
&gt; Hello everyone,<br>
&gt;<br>
&gt; we would like to clarify a few things from this discussion. We are<br>
&gt; displaying some warnings in case of some almost-certainly invalid<br>
&gt; XPath expressions so we were wondering if it makes sense to add<br>
&gt; another if we detect an equality comparison of an identityref and an<b=
r>
&gt; identity name without the use of derived-from(-or-self)() functions.<b=
r>
<br>
Certainly for YANG 1.1 modules.<br>
<br>
&gt;<br>
&gt; Another issue, &quot;local module&quot; has no formal definition as wa=
s<br>
&gt; mentioned. One can infer it is the module where the statement in<br>
&gt; question is defined but a definition would be appreciated. The same<br=
>
&gt; problem is with the term &quot;current module&quot; which it seems can=
 be used<br>
&gt; interchangeably. Lastly, &quot;current node&quot; has no definition ei=
ther and<br>
&gt; so we assumed it to be the node returned by the function current().<br=
>
<br>
As I already proposed, it would be better to declare the result of such<br>
comparisons as undefined.<br>
<br></blockquote><div><br></div><div>Declaring policy based on undefined te=
rms seems like a bad idea.</div><div>We have customers who have used &quot;=
var =3D &#39;identity&#39;&quot; hundreds of =C2=A0times already</div><div>=
in their YANG modules. =C2=A0 Not a chance that I am going to tell them</di=
v><div>to change the YANG or have the YANG compiler start rejecting</div><d=
iv>this most intuitive and common construct.</div><div><br></div><div><br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
Lada<br>
<br></blockquote><div><br></div><div>Andy</div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
&gt;<br>
&gt; Kind regards,<br>
&gt; Michal<br>
&gt;<br>
&gt; On Monday, December 25, 2017 20:14 CET, Andy Bierman &lt;<a href=3D"ma=
ilto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; On Mon, Dec 25, 2017 at 10:53 AM, Ladislav Lhotka &lt;<a href=3D"m=
ailto:lhotka@nic.cz">lhotka@nic.cz</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; &gt; On Sun, 2017-12-24 at 18:54 -0300, Mahesh Jethanandani wrote:=
<br>
&gt;&gt; &gt; &gt; &gt; On Dec 23, 2017, at 10:49 AM, Martin Bjorklund &lt;=
<a href=3D"mailto:mbj@tail-f.com">mbj@tail-f.com</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; Ladislav Lhotka &lt;<a href=3D"mailto:lhotka@nic.cz=
">lhotka@nic.cz</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; On Sat, 2017-12-23 at 13:01 +0100, Martin=
 Bjorklund wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; Andy Bierman &lt;<a href=3D"mailto:andy@y=
umaworks.com">andy@yumaworks.com</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; On Sat, Dec 23, 2017 at 2:21 AM=
, Martin Bjorklund &lt;<br>
&gt;&gt; &gt; <a href=3D"mailto:mbj@tail-f.com">mbj@tail-f.com</a>&gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Hi,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; See section 9.10.3 in RFC 7950:=
<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0The string value of=
 a node of type &quot;identityref&quot; in a &quot;must&quot;<br>
&gt;&gt; &gt; or<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0&quot;when&quot; XP=
ath expression is the referred identity&#39;s qualified<br>
&gt;&gt; &gt; name<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0with the prefix pre=
sent.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; and re. the prefix:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0If the referred ide=
ntity is defined in an<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0imported module, th=
e prefix in the string value is the prefix<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; defined<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0in the correspondin=
g &quot;import&quot; statement.=C2=A0 Otherwise, the<br>
&gt;&gt; &gt; prefix in<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0the string value is=
 the prefix for the current module.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; I most cases you should conside=
r using derived-from-or-self<br>
&gt;&gt; &gt; instead<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; of<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; equality test for identiyrefs.<=
br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; So what is &quot;the current module&=
quot;?<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; What is the resolution of &#39;X&#39=
;? Is it foo:X or bar:X?<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; foo:X<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; No, the resolution of &#39;X&#39; is &#39;X&#3=
9;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; Yes!=C2=A0 Sorry, I misread the question.=C2=A0 I t=
hough the question was what<br>
&gt;&gt; &gt; &gt; &gt; prefix should be used.<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; The question started with a &#39;when&#39; statement (wh=
ich I understand should<br>
&gt;&gt; &gt; be<br>
&gt;&gt; &gt; &gt; changed to &#39;derived-from&#39;) using a identity name=
 that is defined in the<br>
&gt;&gt; &gt; other<br>
&gt;&gt; &gt; &gt; (bar) module. Should the &#39;derived-from&#39; statemen=
t reference the identity<br>
&gt;&gt; &gt; using<br>
&gt;&gt; &gt; &gt; the prefix &#39;b:X&#39; or just &#39;X&#39;, using Andy=
&#39;s example?<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Both are possible in Andy&#39;s example, the former refers to=
 the identity &quot;X&quot;<br>
&gt;&gt; &gt; defined in module &quot;bar&quot;, the latter refers to the i=
dentity &quot;X&quot; defined in<br>
&gt;&gt; &gt; the<br>
&gt;&gt; &gt; local module (&quot;foo&quot;).<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; I see the term &quot;local module&quot; used 11 times in RFC 7950,=
 but it is not<br>
&gt;&gt; defined anywhere.<br>
&gt;&gt; IMO the only intuitive solution is that all scoped names are resol=
ved in<br>
&gt;&gt; the same module,<br>
&gt;&gt; which is the module defining the actual statements. Is that the lo=
cal<br>
&gt;&gt; module?<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Lada<br>
&gt;&gt; &gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Andy<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; /martin<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; because it is an XPath 1.0 string and XPath<br=
>
&gt;&gt; &gt; &gt; &gt; &gt; knows nothing about YANG identities. Because o=
f the rule of sec.<br>
&gt;&gt; &gt; 9.10.3,<br>
&gt;&gt; &gt; &gt; &gt; &gt; the<br>
&gt;&gt; &gt; &gt; &gt; &gt; equality expression is always false.<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; That&#39;s why we introduced the new XPath fun=
ctions derived-from() and<br>
&gt;&gt; &gt; &gt; &gt; &gt; derived-<br>
&gt;&gt; &gt; &gt; &gt; &gt; from-or-self() in YANG 1.1.<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; Lada<br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; /martin<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; /martin<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; Andy<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Andy Bierman &lt;<a href=3D"mai=
lto:andy@yumaworks.com">andy@yumaworks.com</a>&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; On Fri, Dec 15, 2017 =
at 4:38 AM, Radek Krej=C4=8D=C3=AD &lt;<br>
&gt;&gt; &gt; <a href=3D"mailto:rkrejci@cesnet.cz">rkrejci@cesnet.cz</a><br=
>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Hi,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; I&#39;m adding Michal=
 Vasko to cc, he knows better how these<br>
&gt;&gt; &gt; things<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; are<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; checked in libyang.<b=
r>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; It seems to me that A=
ndy refers the text which does not<br>
&gt;&gt; &gt; apply<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; here.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; The<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; identity name was use=
d as part of XPath expresion<br>
&gt;&gt; &gt; (when-stmt),<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; so the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; definition of the con=
text nodes for the when-stmt (RFC<br>
&gt;&gt; &gt; 7950, sec<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; 7.21.5)<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; and XPath context rul=
es should apply here. Not the rules<br>
&gt;&gt; &gt; for the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; identityref&#39;s bas=
e statement. In this case, the when-stmt<br>
&gt;&gt; &gt; is in<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; augment so<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; the context node (whi=
ch we also understand as the current<br>
&gt;&gt; &gt; node<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; in this<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; case) is the augment&=
#39;s target node. And according to XPath<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; context<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; rules<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; (RFC 7950, sec 6.4.1)=
:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; o=C2=A0 Names without=
 a namespace prefix belong to the same<br>
&gt;&gt; &gt; namespace<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; as<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; identifier of the cur=
rent node.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; I cc:ed YANG doctors to ge=
t more opinions...<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; The current node is the au=
gment-stmt.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Note that it does not say =
context node, which is the target<br>
&gt;&gt; &gt; of the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; augment.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; I think prefixes (and defa=
ult prefix) are resolved in the<br>
&gt;&gt; &gt; module<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; containing<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; the statement.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; module foo {<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0import bar { p=
refix b; }<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0identity X;<br=
>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0augment b:/som=
e-node {<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 leaf t=
est {<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0type string;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0when &quot;/b:some-node/b:other-node =3D &#39;X&#39;&quot;;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 }<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; }<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; module bar {<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0identity W;<br=
>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0identity X { b=
ase W; }<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0container some=
-node {<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
leaf other-node {<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0type identityref { base W; }<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0=
}<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0}<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; }<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Q) Does other-node =3D &#3=
9;X&#39; resolve to foo:X or bar:X?=C2=A0 IMO:<br>
&gt;&gt; &gt; foo:X<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Andy<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; In this particular ca=
se, the augment node with the<br>
&gt;&gt; &gt; when-stmt<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; augments<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; same module which def=
ines napt44, so they are in the<br>
&gt;&gt; &gt; correct<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; namespace<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; and<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; the identity name can=
 be used without the prefix. So it<br>
&gt;&gt; &gt; should<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; be<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; fine,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; while I believe that =
using prefix in the cases of<br>
&gt;&gt; &gt; identities is<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; always<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; better approach. From=
 the first sight (it may be<br>
&gt;&gt; &gt; challenging for<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; human<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; to<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; correctly resolve the=
 context/current node in some cases),<br>
&gt;&gt; &gt; I<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; would<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; also<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; expect prefix.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; I propose to keep the=
 change in the draft (added nat<br>
&gt;&gt; &gt; prefix),<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; since it<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; improves readability =
of the expression. But I don&#39;t think<br>
&gt;&gt; &gt; that<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; it is<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; an<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; error to ommit the pr=
efix.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Regards,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Radek<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Dne 19.11.2017 v 20:4=
2 Benoit Claise napsal(a):<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Hi Radek,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Here is a bug re=
port for you.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Regards, Benoit<=
br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; -------- Forward=
ed Message --------<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Subject:=C2=A0 =
=C2=A0 =C2=A0 Re: Issue with ietf-dslite@2017-11-15.yang<br>
&gt;&gt; &gt; and<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; yangdump-pro<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Date:=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0Sat, 18 Nov 2017 13:22:58 -0800<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; From:=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0Andy Bierman &lt;<a href=3D"mailto:andy@yumaworks.c=
om">andy@yumaworks.com</a>&gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; To:=C2=A0 =C2=A0=
Benoit Claise &lt;<a href=3D"mailto:bclaise@cisco.com">bclaise@cisco.com</a=
>&gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; CC:=C2=A0 =C2=A0=
<a href=3D"mailto:draft-ietf-softwire-dslite-yang@ietf.org">draft-ietf-soft=
wire-dslite-<wbr>yang@ietf.org</a> &lt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; <a href=3D"mailto:dra=
ft-ietf-softwire-dslite-yang@ietf.org">draft-ietf-softwire-dslite-<wbr>yang=
@ietf.org</a>&gt;, Mahesh<br>
&gt;&gt; &gt; Jethanandani &lt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; <a href=3D"mailto:mje=
thanandani@gmail.com">mjethanandani@gmail.com</a>&gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Hi,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; yangdump-pro is =
correct. Every other compiler missed<br>
&gt;&gt; &gt; it...<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; 9.10.2.=C2=A0 Th=
e identityref&#39;s &quot;base&quot; Statement<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0The =
&quot;base&quot; statement, which is a substatement to the<br>
&gt;&gt; &gt; &quot;type&quot;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0stat=
ement, MUST be present at least once if the type is<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0&quo=
t;identityref&quot;.=C2=A0 The argument is the name of an<br>
&gt;&gt; &gt; identity, as<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; defined<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0by a=
n &quot;identity&quot; statement.=C2=A0 If a prefix is present on<br>
&gt;&gt; &gt; the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; identity<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0name=
, it refers to an identity defined in the module<br>
&gt;&gt; &gt; that<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; was<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0impo=
rted with that prefix.=C2=A0 *Otherwise, an identity<br>
&gt;&gt; &gt; with the<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; matching<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; name MUST be defined =
in the current module or an included<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; submodule.*<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Using ietf-dslit=
e@2017-11-15.yang and<br>
&gt;&gt; &gt; ietf-nat@2017-11-15.yang<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; When I change &#=
39;natp44&#39; to &#39;nat:natp44&#39; in both<br>
&gt;&gt; &gt; when-stmts:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; andy@andy-homede=
v:~/Desktop/<wbr>FD1289/IETF$ yangdump-pro<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; ietf-dslite@2017-11-1=
5.yang modpath=3D.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; *** /home/andy/D=
esktop/FD1289/<br>
&gt;&gt; &gt; IETF/ietf-dslite@2017-11-15.<wbr>yang<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; *** 0 Errors, 0 =
Warnings<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; andy@andy-homede=
v:~/Desktop/<wbr>FD1289/IETF$<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; Andy<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; On Sat, Nov 18, =
2017 at 11:07 AM, Benoit Claise<br>
&gt;&gt; &gt; &lt;bclaise@cisco<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; .com<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &lt;mailto:<a href=3D=
"mailto:bclaise@cisco.com">bclaise@cisco.com</a>&gt;&gt; wrote:<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 Hi =
Andy,<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 Can=
 you please have a look at<br>
&gt;&gt; &gt; ietf-dslite@2017-11-15.yang<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; at<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; <a href=3D"http://www=
.claise.be/IETFYANGPageCompilation.html" rel=3D"noreferrer" target=3D"_blan=
k">http://www.claise.be/<wbr>IETFYANGPageCompilation.html</a> &lt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; <a href=3D"http://www.claise.be=
/" rel=3D"noreferrer" target=3D"_blank">http://www.claise.be/</a><br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; IETFYANGPageCompilati=
on.html&gt; .<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 yan=
gdump-pro reports a new error, while the other<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; validators are<b=
r>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; fine.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 Cop=
ying Mahesh, as YANG doctor.<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt; &gt;=C2=A0 =C2=A0 Reg=
ards, Benoit<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; ______________________________<wbr>______=
___________<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; yang-doctors mailing list<br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; <a href=3D"mailto:yang-doctors@ietf.org">=
yang-doctors@ietf.org</a><br>
&gt;&gt; &gt; &gt; &gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/l=
istinfo/yang-doctors" rel=3D"noreferrer" target=3D"_blank">https://www.ietf=
.org/mailman/<wbr>listinfo/yang-doctors</a><br>
&gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; &gt; --<br>
&gt;&gt; &gt; &gt; &gt; &gt; Ladislav Lhotka<br>
&gt;&gt; &gt; &gt; &gt; &gt; Head, CZ.NIC Labs<br>
&gt;&gt; &gt; &gt; &gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt;&gt; &gt; &gt; &gt;<br>
&gt;&gt; &gt; &gt; &gt; ______________________________<wbr>________________=
_<br>
&gt;&gt; &gt; &gt; &gt; yang-doctors mailing list<br>
&gt;&gt; &gt; &gt; &gt; <a href=3D"mailto:yang-doctors@ietf.org">yang-docto=
rs@ietf.org</a><br>
&gt;&gt; &gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ya=
ng-doctors" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailm=
an/<wbr>listinfo/yang-doctors</a><br>
&gt;&gt; &gt; --<br>
&gt;&gt; &gt; Ladislav Lhotka<br>
&gt;&gt; &gt; Head, CZ.NIC Labs<br>
&gt;&gt; &gt; PGP Key ID: 0xB8F92B08A9F76C67<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; ______________________________<wbr>_________________<br>
&gt;&gt; &gt; yang-doctors mailing list<br>
&gt;&gt; &gt; <a href=3D"mailto:yang-doctors@ietf.org">yang-doctors@ietf.or=
g</a><br>
&gt;&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/yang-doctors=
" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>li=
stinfo/yang-doctors</a><br>
&gt;&gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Ladislav Lhotka<br>
Head, CZ.NIC Labs<br>
PGP Key ID: 0xB8F92B08A9F76C67<br>
</font></span></blockquote></div><br></div></div>

--94eb2c1a185e117a2405635fe7f5--


From nobody Mon Jan 22 10:42:44 2018
Return-Path: <acee@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CABD0127599; Mon, 22 Jan 2018 10:42:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.531
X-Spam-Level: 
X-Spam-Status: No, score=-14.531 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 DpNRo3q-pVLh; Mon, 22 Jan 2018 10:42:21 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19EBC127058; Mon, 22 Jan 2018 10:42:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13412; q=dns/txt; s=iport; t=1516646530; x=1517856130; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Rc8/uiDLDldJhBmi7/THxqIEm5gtJnkGEu1ZPBOoiZM=; b=Yywh2HXiTNi90fvp1mJC9312HO8g75Wf2rkF+UR6bEYs1sHFB4oE2TVB VBJ2jGn7wRv4TmAdIINguPMfbddwoag2sOTqAVpwVL8rTUNGWGPRXOj0b S489rJ2Bwb4pEYwYmMGZGo9xCDTiGltmwzs8wjVVjZ/aWZwxEOD9AoLOY Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AfAQDRL2Za/5BdJa1UCRkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDQoFaJweDVookjmWBWyeXPoIXCoU7AhqEVlQYAQEBAQEBAQE?= =?us-ascii?q?BayiFJAEFIxFFEAIBCA4KAgImAgICMBUQAgQBDQWKM7UlgieKNgEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAR2BD4M6ghWDaAyCeYMvBIFFFBaDFzGCFCAFkjGRSQKMDYl?= =?us-ascii?q?MghuGH4tlh3KPKAIRGQGBOwEfOYFQbxVnAYF/hFd4iCAsgQaBFwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,397,1511827200"; d="scan'208";a="59498102"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jan 2018 18:42:09 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w0MIg8ZN023325 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 22 Jan 2018 18:42:09 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 22 Jan 2018 13:42:08 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Mon, 22 Jan 2018 13:42:07 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>, "lhotka@nic.cz" <lhotka@nic.cz>
CC: "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "draft-ietf-ospf-yang.all@ietf.org" <draft-ietf-ospf-yang.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>
Thread-Topic: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
Thread-Index: AQHTboUcIbs87wVZj0yzoeuFibmmLKNqkMSAgAEjW4CAAARAAIAAdfEAgAAD/ICAAAyegIABJEgAgBMhLoA=
Date: Mon, 22 Jan 2018 18:42:07 +0000
Message-ID: <2AECD072-7E95-4493-82E1-F83EA32F6F2E@cisco.com>
References: <1515510536.26845.18.camel@nic.cz> <20180109.162311.49506989189385960.mbj@tail-f.com> <1515514101.26845.52.camel@nic.cz> <20180110.103428.251892557297447292.mbj@tail-f.com>
In-Reply-To: <20180110.103428.251892557297447292.mbj@tail-f.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E76353956471A14E99348ACA16EB6F8A@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/feYGCQx5-gfKpHyjbpWGISj8x00>
Subject: Re: [yang-doctors] Yangdoctors last call review of draft-ietf-ospf-yang-09
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2018 18:42:24 -0000

SGkgTWFydGluLCBMYWRhLCANCg0KSW4gZXhwZXJpbWVudGluZyB3aXRoIHRoaXMsIEkgZ2V0IFlB
TkdMSU5UIHZhbGlkYXRpb24gZXJyb3JzLiBJ4oCZbSBub3Qgc3VyZSB3aGF0IEnigJltIG1pc3Np
bmcgYnV0IHRoZSBmaXJzdCBhcmd1bWVudCB0byBkZXJpdmVkLWZyb20oKS9kZXJpdmUtZnJvbS1v
ci1zZWxmKCkgaXMgdGhlIHNjaGVtYSBub2RlIGFuZCB0aGUgc2Vjb25kIGlzIHRoZSBpZGVudGl0
eSDigJMgY29ycmVjdD8NCkZvciBleGFtcGxlLCB0aGUgZm9sbG93aW5nIFlBTkcgbGVhZjoNCg0K
aWRlbnRpdHkgb3NwZi1wcm90b2NvbCB7DQogICAgYmFzZSAicnQ6cm91dGluZy1wcm90b2NvbCI7
DQogICAgZGVzY3JpcHRpb24gIkFueSB2ZXJzaW9uIHRoZSBPU1BGIHByb3RvY29sIjsNCiAgfQ0K
DQogIGlkZW50aXR5IG9zcGZ2MiB7DQogICAgYmFzZSAib3NwZi1wcm90b2NvbCI7DQogICAgZGVz
Y3JpcHRpb24gIk9TUEZ2MiI7DQogIH0NCg0KICBpZGVudGl0eSBvc3BmdjMgew0KICAgIGJhc2Ug
Im9zcGYtcHJvdG9jb2wiOw0KICAgIGRlc2NyaXB0aW9uICJPU1BGdjMiOw0KICB9DQoNCmxlYWYg
cm91dGluZy1wcm90b2NvbC1uYW1lIHsNCiAgICAgIHR5cGUgbGVhZnJlZiB7DQogICAgICAgIHBh
dGggIi9ydDpyb3V0aW5nL3J0OmNvbnRyb2wtcGxhbmUtcHJvdG9jb2xzLyINCiAgICAgICAgICAg
KyAicnQ6Y29udHJvbC1wbGFuZS1wcm90b2NvbC9ydDpuYW1lIjsNCiAgICAgIH0NCiAgICAgIG11
c3QgImRlcml2ZWQtZnJvbSggIg0KCSsgIi9ydDpyb3V0aW5nL3J0OmNvbnRyb2wtcGxhbmUtcHJv
dG9jb2xzLyINCiAgICAgICAgKyAicnQ6Y29udHJvbC1wbGFuZS1wcm90b2NvbFtydDpuYW1lPWN1
cnJlbnQoKV0vIg0KICAgICAgICArICJydDp0eXBlLCBvc3BmOm9zcGYtcHJvdG9jb2wpIjsNCiAg
ICAgIGRlc2NyaXB0aW9uDQogICAgICAgIk9TUEYgcm91dGluZyBwcm90b2NvbCBpbnN0YW5jZSBu
YW1lLiI7DQogICAgfQ0KDQpHaXZlcyBtZTogDQoNCndhcm46IFNjaGVtYSBub2RlICJpZXRmLW9z
cGY6b3NwZi1wcm90b2NvbCIgbm90IGZvdW5kIChkZXJpdmVkLWZyb20oIC9pZXRmLXJvdXRpbmc6
cm91dGluZy9pZXRmLXJvdXRpbmc6Y29udHJvbC1wbGFuZS1wcm90b2NvbHMvaWV0Zi1yb3V0aW5n
OmNvbnRyb2wtcGxhbmUtcHJvdG9jb2xbaWV0Zi1yb3V0aW5nOm5hbWU9Y3VycmVudCgpXS9pZXRm
LXJvdXRpbmc6dHlwZSwgaWV0Zi1vc3BmOm9zcGYtcHJvdG9jb2wpIHdpdGggY29udGV4dCBub2Rl
ICIvaWV0Zi1vc3BmOmlmLXN0YXRlLWNoYW5nZS9yb3V0aW5nLXByb3RvY29sLW5hbWUiLg0KDQpU
aGFua3MNCkFjZWUgDQoNCk9uIDEvMTAvMTgsIDQ6MzYgQU0sICJNYXJ0aW4gQmpvcmtsdW5kIiA8
bWJqQHRhaWwtZi5jb20+IHdyb3RlOg0KDQogICAgSGksDQogICAgDQogICAgSSB0aGluayB3ZSBj
YW4gYWdyZWUgdGhhdCB0aGUgbW9kZWwgaW4gdGhpcyBJLUQgc2hvdWxkIHVzZQ0KICAgIGRlcml2
ZWQtZnJvbS1vci1zZWxmKCkgaW5zdGVhZCBvZiBzdHJpbmcgY29tcGFyaXNvbiwgYW5kIGNvbmNs
dWRlIHRoaXMNCiAgICBkaXNjdXNzaW9uIGhlcmUuICBJIHN1Z2dlc3QgdGhhdCBpZiB3ZSBuZWVk
IHRvIGZ1cnRoZXIgZGlzY3VzcyB0aGUNCiAgICByZXByZXNlbnRhdGlvbiBvZiBpZGVudGl0eXJl
ZnMsIHRoZW4gd2Ugc3RhcnQgYSBuZXcgdGhyZWQgb24gdGhlDQogICAgTkVUTU9EIE1MLg0KICAg
IA0KICAgIA0KICAgIC9tYXJ0aW4NCiAgICANCiAgICANCiAgICANCiAgICBMYWRpc2xhdiBMaG90
a2EgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KICAgID4gT24gVHVlLCAyMDE4LTAxLTA5IGF0IDE2
OjIzICswMTAwLCBNYXJ0aW4gQmpvcmtsdW5kIHdyb3RlOg0KICAgID4gPiBMYWRpc2xhdiBMaG90
a2EgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KICAgID4gPiA+IE9uIFR1ZSwgMjAxOC0wMS0wOSBh
dCAwOTowNiArMDEwMCwgTWFydGluIEJqb3JrbHVuZCB3cm90ZToNCiAgICA+ID4gDQogICAgPiA+
ID4gPiBIaSwNCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiBM
YWRpc2xhdiBMaG90a2EgPGxob3RrYUBuaWMuY3o+IHdyb3RlOg0KICAgID4gPiANCiAgICA+ID4g
PiA+ID4gSGkgQWNlZSwNCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+
ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4g
cGxlYXNlIHNlZSBpbmxpbmUuDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAg
ID4gPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4g
PiA+IE9uIE1vbiwgMjAxOC0wMS0wOCBhdCAxOToyOCArMDAwMCwgQWNlZSBMaW5kZW0gKGFjZWUp
IHdyb3RlOg0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4g
PiBIaSBMYWRhLA0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+
ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ID4g
QXBvbG9naWVzIGZvciB0aGUgZGVsYXkuIFdlIHNvbWV3aGF0IGdvdCBodW5nIHVwIG9uIDQgYW5k
IDYuIFNlZQ0KICAgID4gPiBpbmxpbmUuDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+
IA0KICAgID4gPiA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAg
ICA+ID4gPiA+ID4gPiBPbiAxMi82LzE3LCA2OjI2IEFNLCAiTGFkaXNsYXYgTGhvdGthIiA8bGhv
dGthQG5pYy5jej4gd3JvdGU6DQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAg
ID4gPiA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4g
PiA+ID4gPiA+IFJldmlld2VyOiBMYWRpc2xhdiBMaG90a2ENCiAgICA+ID4gDQogICAgPiA+ID4g
PiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ID4gPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRo
IElzc3Vlcw0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4g
DQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gPiAuLi4NCiAg
ICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+IA0KICAgID4gPiAN
CiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gPiA+IA0KICAgID4gPiANCiAg
ICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gPiA+IDMuIE1heWJlIHRoZSBkcmFm
dCBjb3VsZCBtZW50aW9uIHRoYXQgaW1wbGVtZW50YXRpb25zIHNob3VsZCBzdXBwbHkNCiAgICA+
ID4gYQ0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gPiA+
ICAgZGVmYXVsdCByb3V0aW5nIGRvbWFpbiBhcyBhIHN5c3RlbS1jb250cm9sbGVkIHJlc291cmNl
Lg0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gPiANCiAg
ICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ID4gSXNu4oCZdCB0
aGlzIG1vcmUgb2YgYW4gUkZDODAyMkJJUyBzdGF0ZW1lbnQ/IEkgZ3Vlc3Mgd2UgY291bGQgc3Rh
dGUNCiAgICA+ID4gdGhpcyBhcw0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAg
ICA+ID4gPiA+ID4gPiBhbiBhc3N1bXB0aW9uLg0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAg
ID4gPiANCiAgICA+ID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0K
ICAgID4gPiA+ID4gPiBQcm9iYWJseSwgYnV0IGl0IGlzIG5vdCBhIFlBTkcgaXNzdWUsIHNvIEkn
ZCBsZWF2ZSBpdCB0byB5b3Ugcm91dGluZw0KICAgID4gPiBmb2xrcw0KICAgID4gPiANCiAgICA+
ID4gPiA+IHRvDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4g
PiBkZWNpZGUuDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4g
PiANCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ID4gIA0K
ICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gPiANCiAgICA+
ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ID4gPiA0LiBJbiAid2hl
biIgZXhwcmVzc2lvbnMsIHRoZSBtb2R1bGUgdXNlcyBsaXRlcmFsIHN0cmluZ3MgZm9yDQogICAg
PiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gPiA+ID4gICBpZGVudGl0
aWVzLiBUaGlzIGlzIGtub3duIHRvIGJlIHByb2JsZW1hdGljLCB0aGUgWFBhdGggZnVuY3Rpb25z
DQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gPiA+ID4gICBk
ZXJpdmVkLWZyb20oKSBvciBkZXJpdmVkLWZyb20tb3Itc2VsZigpIHNob3VsZCBiZSB1c2VkIGlu
c3RlYWQuDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gPiA+
IA0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gPiBXaHkg
aXMgdGhpcyBwcm9ibGVtYXRpYz8gSXMgaXQgYmVjYXVzZSB0aGUgdHlwZXMgY2FuIGJlIGV4dGVu
ZGVkPw0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gDQog
ICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gPiBUaGF0J3Mgb25l
IHJlYXNvbjogZGVyaXZlZCBpZGVudGl0aWVzIHNob3VsZCBvZnRlbiBhbHNvIHNhdGlzZnkgdGhl
DQogICAgPiA+IA0KICAgID4gPiA+ID4gY29uc3RyYWludC4NCiAgICA+ID4gDQogICAgPiA+ID4g
PiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAg
ID4gPiANCiAgICA+ID4gPiA+ID4gQnV0IHRoZSBtb3JlIHNlcmlvdXMgcHJvYmxlbSBpcyB0aGF0
IHRoaW5ncyBsaWtlDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+
ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ICAg
ICB3aGVuICIuLi8uLi8uLi8uLi8uLi8uLi8uLi9ydDp0eXBlID0gJ29zcGY6b3NwZnYzJyINCiAg
ICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+IA0KICAgID4gPiAN
CiAgICA+ID4gPiA+IA0KICAgID4gPiANCiAgICA+ID4gPiA+ID4gcmVseSBvbiBwbGFpbiBzdHJp
bmcgY29tcGFyaXNvbiB0aGF0IGRlcGVuZHMgb2QgdGhlIGFjdHVhbCBwcmVmaXggdXNlZA0KICAg
ID4gPiBmb3INCiAgICA+ID4gDQogICAgPiA+ID4gPiB0aGUNCiAgICA+ID4gDQogICAgPiA+ID4g
PiANCiAgICA+ID4gDQogICAgPiA+ID4gPiA+ICJydDp0eXBlIiB2YWx1ZS4gRm9yIG9uZSwgYWNj
b3JkaW5nIHRvIFJGQyA3OTUxIHRoZSBKU09OIGVuY29kaW5nIG9mDQogICAgPiA+IHRoaXMNCiAg
ICA+ID4gDQogICAgPiA+ID4gPiB2YWx1ZQ0KICAgID4gPiANCiAgICA+ID4gPiA+IA0KICAgID4g
PiANCiAgICA+ID4gPiA+ID4gd291bGQgYmUgImlldGYtb3NwZjpvc3BmdjMiIHNvIHRoZSBhYm92
ZSBleHByZXNzaW9uIGlzIGFsd2F5cyBmYWxzZS4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQog
ICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gVGhpcyBpcyBub3Qg
Y29ycmVjdDsgdGhlIHdoZW4gZXhwcmVzc2lvbiBpcyBub3QgZXZhbHVhdGVkIG9uIHRoZSBKU09O
DQogICAgPiA+IA0KICAgID4gPiA+ID4gZW5jb2RpbmcuICBTZWUgdGhlIGxhc3QgcGFyYWdyYXBo
IG9mIHNlY3Rpb24gOS4xMC4zIGluIFJGQyA3OTUwOg0KICAgID4gPiANCiAgICA+ID4gPiA+IA0K
ICAgID4gPiANCiAgICA+ID4gPiA+ICAgIFRoZSBzdHJpbmcgdmFsdWUgb2YgYSBub2RlIG9mIHR5
cGUgImlkZW50aXR5cmVmIiBpbiBhICJtdXN0IiBvcg0KICAgID4gPiANCiAgICA+ID4gPiA+ICAg
ICJ3aGVuIiBYUGF0aCBleHByZXNzaW9uIGlzIHRoZSByZWZlcnJlZCBpZGVudGl0eSdzIHF1YWxp
ZmllZCBuYW1lDQogICAgPiA+IA0KICAgID4gPiA+ID4gICAgd2l0aCB0aGUgcHJlZml4IHByZXNl
bnQuICBJZiB0aGUgcmVmZXJyZWQgaWRlbnRpdHkgaXMgZGVmaW5lZCBpbiBhbg0KICAgID4gPiAN
CiAgICA+ID4gPiA+ICAgIGltcG9ydGVkIG1vZHVsZSwgdGhlIHByZWZpeCBpbiB0aGUgc3RyaW5n
IHZhbHVlIGlzIHRoZSBwcmVmaXggZGVmaW5lZA0KICAgID4gPiANCiAgICA+ID4gPiA+ICAgIGlu
IHRoZSBjb3JyZXNwb25kaW5nICJpbXBvcnQiIHN0YXRlbWVudC4gIE90aGVyd2lzZSwgdGhlIHBy
ZWZpeCBpbg0KICAgID4gPiANCiAgICA+ID4gPiA+ICAgIHRoZSBzdHJpbmcgdmFsdWUgaXMgdGhl
IHByZWZpeCBmb3IgdGhlIGN1cnJlbnQgbW9kdWxlLg0KICAgID4gPiANCiAgICA+ID4gPiANCiAg
ICA+ID4gDQogICAgPiA+ID4gVGhpcyBpcyB3ZWlyZCwgdG8gc2F5IHRoZSBsZWFzdC4gVGhlIGxl
YWZyZWYgaW5zdGFuY2UgbWF5IGhhdmUgYW4gaWRlbnRpdHkNCiAgICA+ID4gdmFsdWUNCiAgICA+
ID4gDQogICAgPiA+ID4gdGhhdCBpcyBkZWZpbmVkIGluIGEgbW9kdWxlIHRoYXQgKGhhcyB0byBi
ZSBpbXBsZW1lbnRlZCBieSB0aGUgc2VydmVyIGJ1dCkNCiAgICA+ID4gDQogICAgPiA+ID4gbmVl
ZG4ndCBiZSBpbXBvcnRlZCBpbiB0aGUgbW9kdWxlIHRoYXQgY29udGFpbnMgdGhlIFhQYXRoIGV4
cHJlc3Npb24uIFNvIEkNCiAgICA+ID4gZG9uJ3QNCiAgICA+ID4gDQogICAgPiA+ID4ga25vdyB3
aGF0ICdjb3JyZXNwb25kaW5nICJpbXBvcnQiIHN0YXRlbWVudCcgdGhpcyBwYXJhZ3JhcGggaXMg
dGFsa2luZw0KICAgID4gPiBhYm91dC4NCiAgICA+ID4gDQogICAgPiA+IA0KICAgID4gPiBJdCBo
YXMgdG8gaW1wb3J0IHRoZSBtb2R1bGUgaW4gb3JkZXIgdG8gZ2l2ZSBhIHByZWZpeCwgd2hpY2gg
dGhlbiBjYW4NCiAgICA+ID4gYmUgdXNlZCBpbiB0aGUgWFBhdGggZXhwcmVzc2lvbi4NCiAgICA+
IA0KICAgID4gSW4gdGhlIFhQYXRoIGV4cHJlc3Npb24gYWJvdmUsIGRvIHlvdSBtZWFuIHRoZSAi
cnQiIHByZWZpeCBvZiAicnQ6dHlwZSI/IElmIHNvLA0KICAgID4gaXQgaXMgaXJyZWxldmFudCBm
b3IgdGhlIHN0cmluZyBjb21wYXJpc29uLCB3aGF0J3MgaW1wb3J0YW50IGlzIHRoZSAqdmFsdWUq
IG9mDQogICAgPiB0aGUgInJ0OnR5cGUiIGluc3RhbmNlLCB3aGljaCBjYW4gYmUgYW4gaWRlbnRp
dHkgZGVmaW5lZCBpbiBhIG1vZHVsZSB0aGF0DQogICAgPiBuZWVkbid0IGJlIGltcG9ydGVkIGJ5
IGlldGYtcm91dGluZywgaWV0Zi1vc3BmIG9yIHdoYXRldmVyLiBTZWMuIDkuMTAuMjoNCiAgICA+
IA0KICAgID4gICAgT24gYSBwYXJ0aWN1bGFyIHNlcnZlciwgdGhlIHZhbGlkIHZhbHVlcyBhcmUg
ZnVydGhlciByZXN0cmljdGVkIHRvIHRoZSBzZXQgb2YNCiAgICA+ICAgICAgaWRlbnRpdGllcyBk
ZWZpbmVkIGluIHRoZSBtb2R1bGVzIGltcGxlbWVudGVkIGJ5IHRoZSBzZXJ2ZXIuDQogICAgPiAN
CiAgICA+ID4gDQogICAgPiA+ID4gQWxzbywgcG90ZW50aWFsbHkgdGhlcmUgY2FuIGJlIGEgY29s
bGlzaW9uIGluIHByZWZpeGVzIGFuZCB0aGVuIHRoaXMgYWxzbw0KICAgID4gPiBicmVha3MNCiAg
ICA+ID4gDQogICAgPiA+ID4gZG93bi4NCiAgICA+ID4gDQogICAgPiA+IA0KICAgID4gPiBObywg
dHdvIG1vZHVsZXMgY2Fubm90IGJlIGltcG9ydGVkIHdpdGggdGhlIHNhbWUgcHJlZml4Lg0KICAg
ID4gDQogICAgPiBJIGhhdmUgdG8gZGlzYWdyZWUuIEFuIGlkZW50aXR5IGRlcml2ZWQgZnJvbSB0
aGUgImlldGYtcm91dGluZzpjb250cm9sLXByb3RvY29sLQ0KICAgID4gdHlwZSIgYmFzZSBpZGVu
dGl0eSBjYW4gYmUgZGVmaW5lZCBpbiBhIG1vZHVsZSB0aGF0IGlzIG5vdCBpbXBvcnRlZCBhbnl3
aGVyZS4gSWYNCiAgICA+IGEgc2VydmVyIGRlY2xhcmVzIHN1Y2ggYSBtb2R1bGUgYXMgaW1wbGVt
ZW50ZWQsIHRoZW4gInJ0OnR5cGUiIG1heSBoYXZlIHRoaXMNCiAgICA+IHZhbHVlIHBlciBzZWMu
IDkuMTAuMi4NCiAgICA+IA0KICAgID4gQW5kLCBjb25zZXF1ZW50bHksIHRoZXJlIG1heSBiZSB0
d28gZGlmZmVyZW50IG1vZHVsZXMgd2l0aCBjb25mbGljdGluZyBwcmVmaXhlcw0KICAgID4gZGVm
aW5pbmcgaWRlbnRpdGllcyB0aGF0IGFyZSBkZXJpdmVkIGZyb20gImlldGYtcm91dGluZzpjb250
cm9sLXByb3RvY29sLXR5cGUiLiANCiAgICA+IA0KICAgID4gPiANCiAgICA+ID4gPiBBIG1vcmFs
IG9mIHRoZSBuYW1lc3BhY2UvcHJlZml4IHN0b3J5IGluIFhNTCB3YXMgdGhhdCByZWx5aW5nIG9m
IG5hbWVzcGFjZQ0KICAgID4gPiANCiAgICA+ID4gPiBwcmVmaXhlcyBoYXZpbmcgYSBwYXJ0aWN1
bGFyIHZhbHVlIGlzIGEgcmVhbGx5IGJhZCBpZGVhLiBJIGtub3cgdGhhdCB0aGUNCiAgICA+ID4g
Y2l0ZWQNCiAgICA+ID4gDQogICAgPiA+ID4gcGFyYWdyYXBoIHdhcyBpbnRlbmRlZCB0byBtYWtl
IHN1Y2ggWFBhdGggc3RyaW5nIGNvbXBhcmlzb25zIG1vcmUNCiAgICA+ID4gZGV0ZXJtaW5pc3Rp
YywNCiAgICA+ID4gDQogICAgPiA+ID4gYnV0IGl0IGlzIGFsc28gcHJvYmxlbWF0aWMgYW5kIHNo
b3VsZCBiZSBhdm9pZGVkIGlmIHBvc3NpYmxlLg0KICAgID4gPiANCiAgICA+ID4gDQogICAgPiA+
IE5vdGUgdGhhdCB0aGlzIHByZWZpeCBpcyB1bmRlciB0aGUgY29udHJvbCBvZiB0aGUgbW9kdWxl
IGRlc2lnbmVyDQogICAgPiA+IHdyaXRpbmcgdGhlIFhQYXRoIGV4cHJlc3Npb24uICBUaGUgc2Ft
ZSBpZGVudGl0eXJlZiB2YWx1ZSBtaWdodCB1c2UgYQ0KICAgID4gDQogICAgPiBObywgaXQgaXMg
bm90LiBUaGUgcHJlZml4ZXMgYXBwZWFyIGluIGluc3RhbmNlIGRhdGEuDQogICAgPiANCiAgICA+
IExhZGENCiAgICA+IA0KICAgID4gPiBkaWZmZXJlbnQgcHJlZml4IGluIHNvbWUgb3RoZXIgbW9k
dWxlLg0KICAgID4gPiANCiAgICA+ID4gDQogICAgPiA+IC9tYXJ0aW4NCiAgICA+ID4gDQogICAg
PiA+IA0KICAgID4gPiANCiAgICA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gTGFkYQ0KICAg
ID4gPiANCiAgICA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAg
PiA+ID4gPiBTbyB0aGUgZXF1YWxpdHkgdGVzdCBvZiB0aGUgaWRlbnRpdHlyZWYgaXMgY29ycmVj
dC4NCiAgICA+ID4gDQogICAgPiA+ID4gPiANCiAgICA+ID4gDQogICAgPiA+ID4gPiBIb3dldmVy
LCBJIGFncmVlIHRoYXQgaW4gbW9zdCBjYXNlcyAnZGVyaXZlZC1mcm9tLW9yLXNlbGYnIHNob3Vs
ZCBiZQ0KICAgID4gPiANCiAgICA+ID4gPiA+IHVzZWQsIGluIG9yZGVyIHRvIGhhbmRsZSBkZXJp
dmVkIGlkZW50aXRpZXMuDQogICAgPiA+IA0KICAgID4gPiA+ID4gDQogICAgPiA+IA0KICAgID4g
PiA+ID4gDQogICAgPiA+IA0KICAgID4gPiA+ID4gL21hcnRpbg0KICAgID4gPiANCiAgICA+ID4g
PiAtLSANCiAgICA+ID4gDQogICAgPiA+ID4gTGFkaXNsYXYgTGhvdGthDQogICAgPiA+IA0KICAg
ID4gPiA+IEhlYWQsIENaLk5JQyBMYWJzDQogICAgPiA+IA0KICAgID4gPiA+IFBHUCBLZXkgSUQ6
IDB4QjhGOTJCMDhBOUY3NkM2Nw0KICAgID4gPiANCiAgICA+ID4gPiANCiAgICA+ID4gDQogICAg
PiAtLSANCiAgICA+IExhZGlzbGF2IExob3RrYQ0KICAgID4gSGVhZCwgQ1ouTklDIExhYnMNCiAg
ICA+IFBHUCBLZXkgSUQ6IDB4QjhGOTJCMDhBOUY3NkM2Nw0KICAgID4gDQogICAgDQoNCg==


From nobody Mon Jan 22 14:59:49 2018
Return-Path: <calle@tail-f.com>
X-Original-To: yang-doctors@ietf.org
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D53012D82D; Mon, 22 Jan 2018 14:59:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Carl Moberg <calle@tail-f.com>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org, lime@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.69.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151666198213.29428.5886859342061936318@ietfa.amsl.com>
Date: Mon, 22 Jan 2018 14:59:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/S0QUtyvsj5uos8lEhBHDybfJ3pU>
Subject: [yang-doctors] Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jan 2018 22:59:42 -0000

Reviewer: Carl Moberg
Review result: On the Right Track

This is my review of draft-ietf-lime-yang-connection-oriented-oam-model-03 and
the included YANG module.

Overall, the document is in reasonable shape but needs more attention around
one fundamental aspect, and a short list of minor issues.

My understanding is that this module is intended to be implemented as a network
service model, per the module classification RFC (RFC8199). But e.g. the â€˜mip'
list has a key 'interface' of type 'if:interface-ref'. That type is defined in
ietf-interfaces to be a leafref with path "/if:interfaces/if:interface/if:nameâ€�
assuming that the module context is a single network element. This seems
self-contradicting and needs to be resolved. 

I would suggest running the YANG module through 'pyang -f yang' to provide
consistent formatting of the module. I think it would also be worth considering
putting the content in the canonical order. E.g. the location of the description
statement in the mip-address grouping makes it hard to read.

The 'session' list is 'ordered-by user', but does not provide any description or
explanation to the meaning of the order.

The content of the description strings are in need of language fixes.


From nobody Mon Jan 22 19:17:25 2018
Return-Path: <wangzitao@huawei.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6DD126C0F; Mon, 22 Jan 2018 19:17:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level: 
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 dsSV_jW1_kAp; Mon, 22 Jan 2018 19:17:11 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 8CAFB1205D3; Mon, 22 Jan 2018 19:17:11 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B9A80C406F7F4; Tue, 23 Jan 2018 03:17:07 +0000 (GMT)
Received: from DGGEML405-HUB.china.huawei.com (10.3.17.49) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 23 Jan 2018 03:17:08 +0000
Received: from DGGEML504-MBS.china.huawei.com ([169.254.11.87]) by dggeml405-hub.china.huawei.com ([10.3.17.49]) with mapi id 14.03.0361.001; Tue, 23 Jan 2018 11:17:06 +0800
From: wangzitao <wangzitao@huawei.com>
To: Carl Moberg <calle@tail-f.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org" <draft-ietf-lime-yang-connection-oriented-oam-model.all@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Thread-Topic: Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03
Thread-Index: AdOT9mRYUEM4j8ZmSyWkLn5SZj+pgg==
Date: Tue, 23 Jan 2018 03:17:05 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EA2B8B085D@DGGEML504-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.78.152]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Kh-PVOD-yYgldZMVEsugu-E9o2M>
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-lime-yang-connection-oriented-oam-model-03
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 03:17:13 -0000

SGkgQ2FybCwNClRoYW5rIHlvdSBmb3IgdGhlc2UgZ29vZCBjb21tZW50cyENClBsZWFzZSBmaW5k
IG15IHJlcGx5IGluLWxpbmUuDQoNCkJlc3QgUmVnYXJkcyENCi1NaWNoYWVsDQoNCi0tLS0t6YKu
5Lu25Y6f5Lu2LS0tLS0NCuWPkeS7tuS6ujogQ2FybCBNb2JlcmcgW21haWx0bzpjYWxsZUB0YWls
LWYuY29tXSANCuWPkemAgeaXtumXtDogMjAxOOW5tDHmnIgyM+aXpSA3OjAwDQrmlLbku7bkuro6
IHlhbmctZG9jdG9yc0BpZXRmLm9yZw0K5oqE6YCBOiBkcmFmdC1pZXRmLWxpbWUteWFuZy1jb25u
ZWN0aW9uLW9yaWVudGVkLW9hbS1tb2RlbC5hbGxAaWV0Zi5vcmc7IGxpbWVAaWV0Zi5vcmc7IGll
dGZAaWV0Zi5vcmcNCuS4u+mimDogWWFuZ2RvY3RvcnMgZWFybHkgcmV2aWV3IG9mIGRyYWZ0LWll
dGYtbGltZS15YW5nLWNvbm5lY3Rpb24tb3JpZW50ZWQtb2FtLW1vZGVsLTAzDQoNClJldmlld2Vy
OiBDYXJsIE1vYmVyZw0KUmV2aWV3IHJlc3VsdDogT24gdGhlIFJpZ2h0IFRyYWNrDQoNClRoaXMg
aXMgbXkgcmV2aWV3IG9mIGRyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb24tb3JpZW50ZWQt
b2FtLW1vZGVsLTAzIGFuZCB0aGUgaW5jbHVkZWQgWUFORyBtb2R1bGUuDQoNCk92ZXJhbGwsIHRo
ZSBkb2N1bWVudCBpcyBpbiByZWFzb25hYmxlIHNoYXBlIGJ1dCBuZWVkcyBtb3JlIGF0dGVudGlv
biBhcm91bmQgb25lIGZ1bmRhbWVudGFsIGFzcGVjdCwgYW5kIGEgc2hvcnQgbGlzdCBvZiBtaW5v
ciBpc3N1ZXMuDQoNCk15IHVuZGVyc3RhbmRpbmcgaXMgdGhhdCB0aGlzIG1vZHVsZSBpcyBpbnRl
bmRlZCB0byBiZSBpbXBsZW1lbnRlZCBhcyBhIG5ldHdvcmsgc2VydmljZSBtb2RlbCwgcGVyIHRo
ZSBtb2R1bGUgY2xhc3NpZmljYXRpb24gUkZDIChSRkM4MTk5KS4gQnV0IGUuZy4gdGhlIOKAmG1p
cCcNCmxpc3QgaGFzIGEga2V5ICdpbnRlcmZhY2UnIG9mIHR5cGUgJ2lmOmludGVyZmFjZS1yZWYn
LiBUaGF0IHR5cGUgaXMgZGVmaW5lZCBpbiBpZXRmLWludGVyZmFjZXMgdG8gYmUgYSBsZWFmcmVm
IHdpdGggcGF0aCAiL2lmOmludGVyZmFjZXMvaWY6aW50ZXJmYWNlL2lmOm5hbWXigJ0NCmFzc3Vt
aW5nIHRoYXQgdGhlIG1vZHVsZSBjb250ZXh0IGlzIGEgc2luZ2xlIG5ldHdvcmsgZWxlbWVudC4g
VGhpcyBzZWVtcyBzZWxmLWNvbnRyYWRpY3RpbmcgYW5kIG5lZWRzIHRvIGJlIHJlc29sdmVkLiAN
Cg0KKysrTWljaGFlbDogYWdyZWUuIFRoZSAnaW50ZXJmYWNlJyBtYXkgbm90IGVub3VnaCB0byBk
aXN0aW5ndWlzaCBkaWZmZXJlbnQgTUlQcy4gV2Ugd2lsbCBmaXggaXQgaW4gbmV4dCB2ZXJzaW9u
LCBhbmQgbWF5IGJlIGRlZmluZSBhbiAiaWQiIGFzIHRoZSBrZXkuIA0KDQpJIHdvdWxkIHN1Z2dl
c3QgcnVubmluZyB0aGUgWUFORyBtb2R1bGUgdGhyb3VnaCAncHlhbmcgLWYgeWFuZycgdG8gcHJv
dmlkZSBjb25zaXN0ZW50IGZvcm1hdHRpbmcgb2YgdGhlIG1vZHVsZS4gSSB0aGluayBpdCB3b3Vs
ZCBhbHNvIGJlIHdvcnRoIGNvbnNpZGVyaW5nIHB1dHRpbmcgdGhlIGNvbnRlbnQgaW4gdGhlIGNh
bm9uaWNhbCBvcmRlci4gRS5nLiB0aGUgbG9jYXRpb24gb2YgdGhlIGRlc2NyaXB0aW9uIHN0YXRl
bWVudCBpbiB0aGUgbWlwLWFkZHJlc3MgZ3JvdXBpbmcgbWFrZXMgaXQgaGFyZCB0byByZWFkLg0K
DQorKytNaWNoYWVsOiBPSy4gV2lsbCBpbXByb3ZlIGl0Lg0KDQpUaGUgJ3Nlc3Npb24nIGxpc3Qg
aXMgJ29yZGVyZWQtYnkgdXNlcicsIGJ1dCBkb2VzIG5vdCBwcm92aWRlIGFueSBkZXNjcmlwdGlv
biBvciBleHBsYW5hdGlvbiB0byB0aGUgbWVhbmluZyBvZiB0aGUgb3JkZXIuDQoNCisrK01pY2hh
ZWw6IGFncmVlLiBXaWxsIHJlbW92ZSBpdCBpbiBuZXh0IHZlcnNpb24uIA0KDQpUaGUgY29udGVu
dCBvZiB0aGUgZGVzY3JpcHRpb24gc3RyaW5ncyBhcmUgaW4gbmVlZCBvZiBsYW5ndWFnZSBmaXhl
cy4NCg0KKysrTWljaGFlbDogT0suIFdpbGwgaW1wcm92ZSBpdC4NCg==


From nobody Wed Jan 24 05:50:06 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67441124207 for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 05:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, 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
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 PQeilF9ppFcj for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 05:50:01 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF0581241F8 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 05:50:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1952; q=dns/txt; s=iport; t=1516801801; x=1518011401; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=74LxfK1p0KXYkg5kt0qBjjrbdKjFSXzbTGLW52jP37E=; b=R97l5yjKmlt/FXRyxsjfuG3HvMPUVk46ZgVVBip0wH0TvGUaBuGYEsz5 JPCPEureCnWCcC6D9k1XWhXKNMXh/yB2EQdPvSnWX5DF4gLtcP8ZOrpX/ owCUCVayGmJr3xAZCrUjP8JhAth/oJfo9rtb71MLOhOKOpB5W0IwVJZtB k=;
X-IronPort-AV: E=Sophos;i="5.46,407,1511827200";  d="scan'208";a="1579161"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jan 2018 13:49:59 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0ODnwxl025164; Wed, 24 Jan 2018 13:49:59 GMT
To: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com>
Date: Wed, 24 Jan 2018 14:49:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180116174323.e2b4zr5ffgrycnei@elstar.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/yJ8j8JfNevWjh3-_WresrA4OT_s>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 13:50:04 -0000

Hi JÃ¼rgen,

I like it.
I'm busy with the RFC6087bis AD review and it will be part of the feedback.

Regards, Benoit
> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote:
>> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:
>>> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
>>>> The feature-per-leaf approach should not be approved by YD.
>> Do we want to add a sentence in
>> https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17,
>> expressing that a feature-per-leaf is most likely the wrong approach?
> This is difficult to describe. Perhaps something like this is a
> reasonably small change to the existing text (which only talks about
> too big features but not about too small features).
>
> OLD
>
>     The YANG "feature" statement is used to define a label for a set of
>     optional functionality within a module.  The "if-feature" statement
>     is used in the YANG statements associated with a feature.
>
>     The set of YANG features available in a module should be considered
>     carefully.  The description-stmt within a feature-stmt MUST specify
>     any interactions with other features.
>
>     If there is a large set of objects...
>
> NEW
>
>     The YANG "feature" statement is used to define a label for a set of
>     optional functionality within a module.  The "if-feature" statement
>     is used in the YANG statements associated with a feature.  The
>     description-stmt within a feature-stmt MUST specify any
>     interactions with other features.
>
>     The set of YANG features defined in a module should be considered
>     carefully. Very fine granular features increase interoperability
>     complexity and should be avoided. A likely misuse of the feature
>     mechanism is the tagging of individual leafs (e.g., counters) with
>     separate features.
>
>     If there is a large set of objects...
>
> /js
>


From nobody Wed Jan 24 05:54:18 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDA91242EA for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 05:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 l9Fq4ExNbveI for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 05:54:14 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A45E11241F8 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 05:54:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7479; q=dns/txt; s=iport; t=1516802053; x=1518011653; h=subject:from:to:references:message-id:date:mime-version: in-reply-to; bh=cf+ig4HOnWOOlVS7R1jsQx10aUfHyeoMNjZ1kPMfPTQ=; b=hBWwsREwg4LDNdgtGknowUt6fGlqnIo04b/gky/N5AeJjJqKCzDXviQM 9fMrSb2UoeY8r6+/uDA/YONfZ5EHBLRcxfc33kz5105S3LQql4G5Lyjlz MLRrhqwcLqHSmdwtg7EdURt/uRpNgl6vuER542XnCOhE9XCMQqFFKZfRU g=;
X-IronPort-AV: E=Sophos;i="5.46,407,1511827200"; d="scan'208,217";a="1627052"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jan 2018 13:54:12 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0ODsBnY026865; Wed, 24 Jan 2018 13:54:11 GMT
From: Benoit Claise <bclaise@cisco.com>
To: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local> <1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com>
Message-ID: <283f5774-5995-6ae3-16b7-385b8ea270d1@cisco.com>
Date: Wed, 24 Jan 2018 14:54:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com>
Content-Type: multipart/alternative; boundary="------------B5CAD248AFF2729DC9045329"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/wK_RSKNMfn57aFowhFfTGUjeBxQ>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 13:54:17 -0000

This is a multi-part message in MIME format.
--------------B5CAD248AFF2729DC9045329
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Btw, along the same lines, in section 4.5

OLD:
    If a data definition is optional, depending on server support for a
    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
    statement SHOULD be defined to indicate that the NETCONF or RESTCONF
    capability is supported within the data model.

NEW:
    If a feature or a set of data definitions is optional, depending on server support for a
    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
    statement SHOULD be defined to indicate that the NETCONF or RESTCONF
    capability is supported within the data model.

It will also be in my AD review email.

Regards, B.
> Hi JÃ¼rgen,
>
> I like it.
> I'm busy with the RFC6087bis AD review and it will be part of the 
> feedback.
>
> Regards, Benoit
>> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote:
>>> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:
>>>> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
>>>>> The feature-per-leaf approach should not be approved by YD.
>>> Do we want to add a sentence in
>>> https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17, 
>>>
>>> expressing that a feature-per-leaf is most likely the wrong approach?
>> This is difficult to describe. Perhaps something like this is a
>> reasonably small change to the existing text (which only talks about
>> too big features but not about too small features).
>>
>> OLD
>>
>> Â Â Â  The YANG "feature" statement is used to define a label for a set of
>> Â Â Â  optional functionality within a module.Â  The "if-feature" statement
>> Â Â Â  is used in the YANG statements associated with a feature.
>>
>> Â Â Â  The set of YANG features available in a module should be considered
>> Â Â Â  carefully.Â  The description-stmt within a feature-stmt MUST specify
>> Â Â Â  any interactions with other features.
>>
>> Â Â Â  If there is a large set of objects...
>>
>> NEW
>>
>> Â Â Â  The YANG "feature" statement is used to define a label for a set of
>> Â Â Â  optional functionality within a module.Â  The "if-feature" statement
>> Â Â Â  is used in the YANG statements associated with a feature. The
>> Â Â Â  description-stmt within a feature-stmt MUST specify any
>> Â Â Â  interactions with other features.
>>
>> Â Â Â  The set of YANG features defined in a module should be considered
>> Â Â Â  carefully. Very fine granular features increase interoperability
>> Â Â Â  complexity and should be avoided. A likely misuse of the feature
>> Â Â Â  mechanism is the tagging of individual leafs (e.g., counters) with
>> Â Â Â  separate features.
>>
>> Â Â Â  If there is a large set of objects...
>>
>> /js
>>
>


--------------B5CAD248AFF2729DC9045329
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Btw, along the same lines, in section
      4.5<br>
      <pre class="newpage">OLD:
   If a data definition is optional, depending on server support for a
   NETCONF or RESTCONF protocol capability, then a YANG 'feature'
   statement SHOULD be defined to indicate that the NETCONF or RESTCONF
   capability is supported within the data model.

NEW:
   If a feature or a set of data definitions is optional, depending on server support for a
   NETCONF or RESTCONF protocol capability, then a YANG 'feature'
   statement SHOULD be defined to indicate that the NETCONF or RESTCONF
   capability is supported within the data model.</pre>
    </div>
    It will also be in my AD review email.<br>
    <br>
    Regards, B.<br>
    <blockquote type="cite"
      cite="mid:1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com">Hi
      JÃ¼rgen,
      <br>
      <br>
      I like it.
      <br>
      I'm busy with the RFC6087bis AD review and it will be part of the
      feedback.
      <br>
      <br>
      Regards, Benoit
      <br>
      <blockquote type="cite">On Tue, Jan 16, 2018 at 06:03:05PM +0100,
        Benoit Claise wrote:
        <br>
        <blockquote type="cite">On 1/11/2018 12:28 AM, Juergen
          Schoenwaelder wrote:
          <br>
          <blockquote type="cite">On Wed, Jan 10, 2018 at 02:49:48PM
            -0800, Andy Bierman wrote:
            <br>
            <blockquote type="cite">The feature-per-leaf approach should
              not be approved by YD.
              <br>
            </blockquote>
          </blockquote>
          Do we want to add a sentence in
          <br>
<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17">https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17</a>,
          <br>
          expressing that a feature-per-leaf is most likely the wrong
          approach?
          <br>
        </blockquote>
        This is difficult to describe. Perhaps something like this is a
        <br>
        reasonably small change to the existing text (which only talks
        about
        <br>
        too big features but not about too small features).
        <br>
        <br>
        OLD
        <br>
        <br>
        Â Â Â  The YANG "feature" statement is used to define a label for a
        set of
        <br>
        Â Â Â  optional functionality within a module.Â  The "if-feature"
        statement
        <br>
        Â Â Â  is used in the YANG statements associated with a feature.
        <br>
        <br>
        Â Â Â  The set of YANG features available in a module should be
        considered
        <br>
        Â Â Â  carefully.Â  The description-stmt within a feature-stmt MUST
        specify
        <br>
        Â Â Â  any interactions with other features.
        <br>
        <br>
        Â Â Â  If there is a large set of objects...
        <br>
        <br>
        NEW
        <br>
        <br>
        Â Â Â  The YANG "feature" statement is used to define a label for a
        set of
        <br>
        Â Â Â  optional functionality within a module.Â  The "if-feature"
        statement
        <br>
        Â Â Â  is used in the YANG statements associated with a feature.Â 
        The
        <br>
        Â Â Â  description-stmt within a feature-stmt MUST specify any
        <br>
        Â Â Â  interactions with other features.
        <br>
        <br>
        Â Â Â  The set of YANG features defined in a module should be
        considered
        <br>
        Â Â Â  carefully. Very fine granular features increase
        interoperability
        <br>
        Â Â Â  complexity and should be avoided. A likely misuse of the
        feature
        <br>
        Â Â Â  mechanism is the tagging of individual leafs (e.g.,
        counters) with
        <br>
        Â Â Â  separate features.
        <br>
        <br>
        Â Â Â  If there is a large set of objects...
        <br>
        <br>
        /js
        <br>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------B5CAD248AFF2729DC9045329--


From nobody Wed Jan 24 10:49:42 2018
Return-Path: <mjethanandani@gmail.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88B871275AB for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 10:49:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=gmail.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 fCvO3VMOVoVt for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 10:49:37 -0800 (PST)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 DA1071201FA for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 10:49:36 -0800 (PST)
Received: by mail-it0-x22e.google.com with SMTP id m11so19208195iti.1 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 10:49:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=xJ7m2Mu9Alkjq6CUV+g1m89BIPAtklKRodMnEEkkmF4=; b=hhSI+5Rh2YsxdHDBNOCon4iynWKJcQ6Jztid2UnH6eZ0TXoxYrfs2Uht0Nltw2/Qmi +XJi3g+pGn8xXAMGeN8GU2cY9ORUSZITWWRgM1eFSnDsvewmnxiiLpE6XZ/4JTU2AL95 9sEQ9vwptSykwkO08b5mDV9v4sYV+5TMUkzLqVLNgoq6rlBSBKk9qHMCbWMSfPgQ30zV MJjOE9U8/mvkLmbaNeJYkrkgkthCciy9RNYaxF5B8EFqb8E0qgCVxeR2tVjhB+IrqWxV Q3qiesDcjbWRW2JF+9wzppasq0XRRMrynKAK+4h+CCpj/UYUvbdrvwlkrw71C6QazYA+ NS0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=xJ7m2Mu9Alkjq6CUV+g1m89BIPAtklKRodMnEEkkmF4=; b=kqGNo+mdBRHMHsP20dqy8WsABP5ZnSQbf71md5OhwpK6wVqa288iPKLnILGgE58EOK MnOniavvw3TIdVPFfOtxgZzhephkdsSbIWli49uSUEFivaz+/clO9d2Cky9qwQ1FVMaa JhbJ5r8IHvnKAOsHsy+ES1j24+AmBk5UgU5mshXfx7gkEWO7FH1acmEpKQ1/6HhaS2xp slv9CdWXgd7kROy66ThM6QFT/M60Y/iFvMhnMAwwWmRTFSBGT1Yt24tmYS70CkneuNjy LT8USr9PoQh3KIBKVjHEyoVyY5Ds0zZsAgmW+Tn/dDdmx8+ObyXI5ynDvqD//PPCRbYK 4hog==
X-Gm-Message-State: AKwxytcSgpQ/RM6cYH685XvIZbvx5Vj7++QleneeglGa2aImZikI3OrK bwGPuiWxC8c8xUKtY/jm26o=
X-Google-Smtp-Source: AH8x224tAC3a8RSLkzJ9FV7KUGFkHxIWo2r08py/VV9LfmLZIaQYD7ixSvakyhuX0GYs4mRXxh66Kg==
X-Received: by 10.36.41.72 with SMTP id p69mr9927737itp.47.1516819776275; Wed, 24 Jan 2018 10:49:36 -0800 (PST)
Received: from mahesh-m-m8d1.attlocal.net ([2600:1700:edb0:8fd0:f531:c9be:3b67:558d]) by smtp.gmail.com with ESMTPSA id o8sm508994ioe.56.2018.01.24.10.49.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Jan 2018 10:49:35 -0800 (PST)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <E5618F14-46C8-40BB-9116-9E4A866575BC@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5CA372AC-8267-4DA4-BF71-F13AEC785EE4"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Wed, 24 Jan 2018 10:49:33 -0800
In-Reply-To: <283f5774-5995-6ae3-16b7-385b8ea270d1@cisco.com>
Cc: Andy Bierman <andy@yumaworks.com>, Ebben Aries <exa@juniper.net>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
To: Benoit Claise <bclaise@cisco.com>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local> <1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com> <283f5774-5995-6ae3-16b7-385b8ea270d1@cisco.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/xkS-b6NVE9eBrCobYaqv-60B0Sw>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Jan 2018 18:49:39 -0000

--Apple-Mail=_5CA372AC-8267-4DA4-BF71-F13AEC785EE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

How does one define a feature statement that indicates support for =
NETCONF or RESTCONF protocol capability? I thought feature statements =
were for features within the module.

> On Jan 24, 2018, at 5:54 AM, Benoit Claise <bclaise@cisco.com> wrote:
>=20
> Btw, along the same lines, in section 4.5
> OLD:
>    If a data definition is optional, depending on server support for a
>    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
>    statement SHOULD be defined to indicate that the NETCONF or =
RESTCONF
>    capability is supported within the data model.
>=20
> NEW:
>    If a feature or a set of data definitions is optional, depending on =
server support for a
>    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
>    statement SHOULD be defined to indicate that the NETCONF or =
RESTCONF
>    capability is supported within the data model.
> It will also be in my AD review email.
>=20
> Regards, B.
>> Hi J=C3=BCrgen,=20
>>=20
>> I like it.=20
>> I'm busy with the RFC6087bis AD review and it will be part of the =
feedback.=20
>>=20
>> Regards, Benoit=20
>>> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote:=20
>>>> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:=20
>>>>> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:=20
>>>>>> The feature-per-leaf approach should not be approved by YD.=20
>>>> Do we want to add a sentence in=20
>>>> =
https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17 =
<https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#section-4.17>=
,=20
>>>> expressing that a feature-per-leaf is most likely the wrong =
approach?=20
>>> This is difficult to describe. Perhaps something like this is a=20
>>> reasonably small change to the existing text (which only talks about=20=

>>> too big features but not about too small features).=20
>>>=20
>>> OLD=20
>>>=20
>>>     The YANG "feature" statement is used to define a label for a set =
of=20
>>>     optional functionality within a module.  The "if-feature" =
statement=20
>>>     is used in the YANG statements associated with a feature.=20
>>>=20
>>>     The set of YANG features available in a module should be =
considered=20
>>>     carefully.  The description-stmt within a feature-stmt MUST =
specify=20
>>>     any interactions with other features.=20
>>>=20
>>>     If there is a large set of objects...=20
>>>=20
>>> NEW=20
>>>=20
>>>     The YANG "feature" statement is used to define a label for a set =
of=20
>>>     optional functionality within a module.  The "if-feature" =
statement=20
>>>     is used in the YANG statements associated with a feature.  The=20=

>>>     description-stmt within a feature-stmt MUST specify any=20
>>>     interactions with other features.=20
>>>=20
>>>     The set of YANG features defined in a module should be =
considered=20
>>>     carefully. Very fine granular features increase interoperability=20=

>>>     complexity and should be avoided. A likely misuse of the feature=20=

>>>     mechanism is the tagging of individual leafs (e.g., counters) =
with=20
>>>     separate features.=20
>>>=20
>>>     If there is a large set of objects...=20
>>>=20
>>> /js=20
>>>=20
>>=20
>=20
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

Mahesh Jethanandani
mjethanandani@gmail.com


--Apple-Mail=_5CA372AC-8267-4DA4-BF71-F13AEC785EE4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">How =
does one define a feature statement that indicates support for NETCONF =
or RESTCONF protocol capability? I thought feature statements were for =
features within the module.<br class=3D""><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Jan 24, 2018, at 5:54 AM, =
Benoit Claise &lt;<a href=3D"mailto:bclaise@cisco.com" =
class=3D"">bclaise@cisco.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">
 =20
    <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8" class=3D"">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D"">
    <div class=3D"moz-cite-prefix">Btw, along the same lines, in section
      4.5<br class=3D"">
      <pre class=3D"newpage">OLD:
   If a data definition is optional, depending on server support for a
   NETCONF or RESTCONF protocol capability, then a YANG 'feature'
   statement SHOULD be defined to indicate that the NETCONF or RESTCONF
   capability is supported within the data model.

NEW:
   If a feature or a set of data definitions is optional, depending on =
server support for a
   NETCONF or RESTCONF protocol capability, then a YANG 'feature'
   statement SHOULD be defined to indicate that the NETCONF or RESTCONF
   capability is supported within the data model.</pre>
    </div>
    It will also be in my AD review email.<br class=3D"">
    <br class=3D"">
    Regards, B.<br class=3D"">
    <blockquote type=3D"cite" =
cite=3D"mid:1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com" class=3D"">Hi
      J=C3=BCrgen,
      <br class=3D"">
      <br class=3D"">
      I like it.
      <br class=3D"">
      I'm busy with the RFC6087bis AD review and it will be part of the
      feedback.
      <br class=3D"">
      <br class=3D"">
      Regards, Benoit
      <br class=3D"">
      <blockquote type=3D"cite" class=3D"">On Tue, Jan 16, 2018 at =
06:03:05PM +0100,
        Benoit Claise wrote:
        <br class=3D"">
        <blockquote type=3D"cite" class=3D"">On 1/11/2018 12:28 AM, =
Juergen
          Schoenwaelder wrote:
          <br class=3D"">
          <blockquote type=3D"cite" class=3D"">On Wed, Jan 10, 2018 at =
02:49:48PM
            -0800, Andy Bierman wrote:
            <br class=3D"">
            <blockquote type=3D"cite" class=3D"">The feature-per-leaf =
approach should
              not be approved by YD.
              <br class=3D"">
            </blockquote>
          </blockquote>
          Do we want to add a sentence in
          <br class=3D"">
<a class=3D"moz-txt-link-freetext" =
href=3D"https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#sectio=
n-4.17">https://tools.ietf.org/html/draft-ietf-netmod-rfc6087bis-15#sectio=
n-4.17</a>,
          <br class=3D"">
          expressing that a feature-per-leaf is most likely the wrong
          approach?
          <br class=3D"">
        </blockquote>
        This is difficult to describe. Perhaps something like this is a
        <br class=3D"">
        reasonably small change to the existing text (which only talks
        about
        <br class=3D"">
        too big features but not about too small features).
        <br class=3D"">
        <br class=3D"">
        OLD
        <br class=3D"">
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; The YANG "feature" statement is used to =
define a label for a
        set of
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; optional functionality within a module.&nbsp; =
The "if-feature"
        statement
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; is used in the YANG statements associated =
with a feature.
        <br class=3D"">
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; The set of YANG features available in a =
module should be
        considered
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; carefully.&nbsp; The description-stmt within =
a feature-stmt MUST
        specify
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; any interactions with other features.
        <br class=3D"">
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; If there is a large set of objects...
        <br class=3D"">
        <br class=3D"">
        NEW
        <br class=3D"">
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; The YANG "feature" statement is used to =
define a label for a
        set of
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; optional functionality within a module.&nbsp; =
The "if-feature"
        statement
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; is used in the YANG statements associated =
with a feature.&nbsp;
        The
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; description-stmt within a feature-stmt MUST =
specify any
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; interactions with other features.
        <br class=3D"">
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; The set of YANG features defined in a module =
should be
        considered
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; carefully. Very fine granular features =
increase
        interoperability
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; complexity and should be avoided. A likely =
misuse of the
        feature
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; mechanism is the tagging of individual leafs =
(e.g.,
        counters) with
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; separate features.
        <br class=3D"">
        <br class=3D"">
        &nbsp;&nbsp;&nbsp; If there is a large set of objects...
        <br class=3D"">
        <br class=3D"">
        /js
        <br class=3D"">
        <br class=3D"">
      </blockquote>
      <br class=3D"">
    </blockquote>
    <br class=3D"">
  </div>

_______________________________________________<br class=3D"">yang-doctors=
 mailing list<br class=3D""><a href=3D"mailto:yang-doctors@ietf.org" =
class=3D"">yang-doctors@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/yang-doctors<br =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">
<div class=3D"">Mahesh Jethanandani</div><div class=3D""><a =
href=3D"mailto:mjethanandani@gmail.com" =
class=3D"">mjethanandani@gmail.com</a></div>

</div>
<br class=3D""></body></html>=

--Apple-Mail=_5CA372AC-8267-4DA4-BF71-F13AEC785EE4--


From nobody Wed Jan 24 19:17:35 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F4012D7F7 for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 19:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 59RE7NizBasI for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 19:17:31 -0800 (PST)
Received: from mx0a-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 AE5AB1289B0 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 19:17:31 -0800 (PST)
Received: from pps.filterd (m0108158.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0P3ELc5003416; Wed, 24 Jan 2018 19:17:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : mime-version : content-type; s=PPS1017; bh=JrhPfOaQqWLOkFCa/Vuq+2HBL+5qti43cHqyCxLnQbY=; b=ErFD0YNngcGoozHc3Epsy2r/YClDBGyxw39R+wVvF+fNVYkt5nDWetxUiQRBtyqziQTq Mo0PPBOcyVLszvv/O2jKlvASQ0Ns8fG0VblVBg8zCHVxJqeNq42qx03JIxmEp8lzFtf0 wv51oH0IFQLHYniYSd8xys3dk6pkagv3wP5v6GcuYWa8KYYvUKeUOuoTB03hzpWrxPT8 vWkWGRjVR5m4nMtepnpf5uJv8H/kHluWtZd3hmqfd5cHgSTnQC9ozHPr5uclwkHlDzOG bpDdskTsY/UugU64jNq5vnIP9/y8onaHM0YUvq4Fw/rk0Q3evGgeFEfU6H64jNi+GeBM JA== 
Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp0176.outbound.protection.outlook.com [216.32.181.176]) by mx0a-00273201.pphosted.com with ESMTP id 2fq74ar095-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 24 Jan 2018 19:17:30 -0800
Received: from SN4PR0501CA0079.namprd05.prod.outlook.com (10.171.32.145) by CY4PR05MB3608.namprd05.prod.outlook.com (10.171.244.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.5; Thu, 25 Jan 2018 03:17:29 +0000
Received: from DM3NAM05FT054.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::206) by SN4PR0501CA0079.outlook.office365.com (2603:10b6:803:22::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.464.6 via Frontend Transport; Thu, 25 Jan 2018 03:17:28 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT054.mail.protection.outlook.com (10.152.98.168) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.444.7 via Frontend Transport; Thu, 25 Jan 2018 03:17:28 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 24 Jan 2018 19:16:51 -0800
Date: Wed, 24 Jan 2018 20:16:50 -0700
From: Ebben Aries <exa@juniper.net>
To: <yang-doctors@ietf.org>
Message-ID: <20180125031650.jzdswdgpspontven@smtp.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(376002)(396003)(346002)(39860400002)(39380400002)(2980300002)(189003)(199004)(2351001)(69596002)(106466001)(5660300001)(336011)(105596002)(53416004)(6306002)(26005)(77096007)(55016002)(53936002)(6916009)(478600001)(97736004)(186003)(86362001)(47776003)(59450400001)(305945005)(356003)(7696005)(966005)(2906002)(3716004)(1076002)(104016004)(4326008)(23726003)(316002)(16586007)(68736007)(46406003)(81166006)(81156014)(8936002)(50466002)(8676002)(97756001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR05MB3608; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT054; 1:jz8XcD2Za4ZTBHAFWsuYGwi3UsDHVefSozKGpeJVIAO4I4psijAd3v+KyLukyh5W8zGU+IdGxnUdiDFXeOgGX3bhZVhroTVPFjQUnD1/kvqegSOQ2pWc0HHMbsouDutS
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: c487a927-bee4-48c6-d468-08d563a22a4a
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:CY4PR05MB3608; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 3:LXsF14/NHvMeIDJ6TyfBSWTsW3R2kDU6iQaoxijPj65vsBFm5YzFgA6Dyj7ywF6HG76WUIYdRH+Xw6GdMd2M77sotwJXB8L/k6H8A/aC60aWDyhm8cq2TT+BfCKNrAHUMNMDgJkgwsQExdC2/tlNXizNNVqz4SzwQwAoRKpVb+J/CUfN9i/jXuSiyhHKK0J1d+cl+kjYt8mYhyN7nawhMIUHZqfI5bj1UqrmteoPToMEE8gxVIcC48Xiv+VL/d3Iqf6z1GprtcDJM0HZKVY5rKV6c53T2o3Hh00MWNloawwPkNYDf1+YLlF33BpzVva83eoc127bhhBz8WX7/zo0ajZuiD04NI38zH3ByTwIYKA=; 25:7oPQ8w/Hr0wgEVrbg5yvzrqLmesDUgo2uG7GSFycTnbsWwTnZc+1Oo0iH76WqE3BSj7L30kdiRxit4Sv1HtqcruJwUR6DTwbxgNwKvkP7YXWfIzIyK2rgAr9mFTD/4lC5AzTO3EmHjC/yzBLtJYcq0ZsbcF3GSu2TWPNQz3xdjaMyR7/07wguzoSSpwtsAyzQW7zZkGvcnolnb0ur8xJZjHKn//2Fn+IGzAxlwfD2HYsnghnMZg9Une81us060YOt6brFFjwOk6wauD5pHjhcXiucZ5J1mLkzwfQbjJbNPvphojt5EtXr0J+5RVDym7eYJIrFLeFfxuM68vE47ltHQ==
X-MS-TrafficTypeDiagnostic: CY4PR05MB3608:
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 31:2QoGlFt4BVBsOGBjineu6urCAowybtrXX9ygWPt6B1LNSo4cX7Jj1ihyaUbDFLiv5N09Ck5GDE3humni1iqUr+7vPt320uzZm2Gda3A159PWJEbT3L+lG1qowWng+Yv9493aXelJYbGrJO+2gZbXTUOLoT0dJ43EzdICvuk0TXRFDcI9Gu/+mmrbb0i3lg5/2e4cqk+THHHCmdi4L++LbwejGBRqRAAAWsu/CHFKPMs=; 20:92AktN8IOS63krCSA80N1zyhHAgzxTylZGGuER+q+STg70aNaSznQfk6SrGBvB+U8BEgEs03h70dxzDhxJ4lTqjIn1iXxb7Rc2+OWRlF6XGQC8p99MD6fS310+Cf3zOp8bneCwPHe8ZSNlYpk+OxmcoRWWJFN7HAeD887bpIEIHFFeaf4rEY+iEEhUMSEq+rDdRtLbFKzlc/SSHkmuSaPOJU5CD/G6zmkiQ+UXpCChmGOHQUDsrKfcnwVTHRdARKybe04AT2EabdvpiA7fW5qa4lfWTTVYrqHVF0SJ23BWLBBxh0alUUnNLkrp3YROIF+wNWUYPiibunZvg5hHR+b+l3pQSUkpLTz09Aui/PvR1C5fXgHcC28R9s4lbMTqLqDLlXMEUXDHApMWWTIUnnRtyT1HTZqGzLBvG0ePTp3pyROCAb3KBlHPH+BJz6kz6aeeKVq6He/GDwXCod7S2C9CYml5jUnuzm7Ob/1PiAc7YskWps98OZCp6S6h/VijJl
X-Microsoft-Antispam-PRVS: <CY4PR05MB36080AAFEB8972FE64E616DCA8E10@CY4PR05MB3608.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(131327999870524);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231023)(2400081)(944501161)(6055026)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123560045)(20161123558120)(6072148)(201708071742011); SRVR:CY4PR05MB3608; BCL:0; PCL:0; RULEID:; SRVR:CY4PR05MB3608; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 4:qtPFpT6Yy0q92J+6MjlroRU2HN5wxFQxqUhGFIZ9x9ij6EPg3Htrx/qzzEArKUBtq53yt2mlFmby+yPw9wl/O+OHaVnaQ1zZYeHOAfQV5c3KlockD9PPVEtZkHSrKWfdV3JJvtzxa8QsXfNRiMotSufjDx0w8yxoc7cyUtbjI4/g3FGU5CD7GT/i2AWe7enPxmtEk66VeQ/27kDw4tcShtScjWI8J4iAUo2l/eWND12HK72DsjV+EHio4RlP3amxsiLuZKU+tXCQ5GmZHPMd1SMvUziCNlDRTtonG5BOk2NfIn0w6eK6DupfmFalLxRK
X-Forefront-PRVS: 0563F2E8B7
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; CY4PR05MB3608; 23:HCBniIKGIXchdFTnV+YvW25ZGZbr6zzr7D1rYUahB?= =?us-ascii?Q?bD/BXB0GtBc65T9+UAd2HqZAebGtWnYBAWTH9xlXKPd8+WsrAJsfv/HFf+jt?= =?us-ascii?Q?QmvZXTMNvqNdycoXjIDuwJ2e3t0rJcInuQX33WDxV1SCYthknmHYQ3VR1Je+?= =?us-ascii?Q?exRADCW0HziMu8BGOmVeuXJ2MoN4cTtunLKMk35H2OrHqKX0kQOgfAdSvC2n?= =?us-ascii?Q?pHQXjDrIb/xPa9yLKspRCUmPyiesVQAQORe3QvbE3iAj1AgN5CJ2sV/Fwgi6?= =?us-ascii?Q?pbDHSFv0skgyqYIgee9hEpROu1lafTa/upU0utyeeYFhTq3+iXsVG4+ZYGTT?= =?us-ascii?Q?GP/eFDn7pQSYC3ymHNUWmBZAnj55n5xeWYMq7CwT8dCs9rsDyKCsHjwfUZ4V?= =?us-ascii?Q?J5fhYIpkGSFuPIyyttxtKNFdw4Le7QdXn0mKRveCYWnudRQ+VTLZHad0oA3F?= =?us-ascii?Q?Oa7ybx5kB1bOBu/pcALiXZ3R6YM/0aXpnc4jiJyOVUgP08zlxt7kPVppfjrD?= =?us-ascii?Q?3SMgh/viswkfCli8oQXB3x7sRkkZz4Occ0VlGHSiNR/I2yAXsBbFGeF4BghW?= =?us-ascii?Q?eEsd8zKguupdXLE+FKMpxFKDI+MXpgKSSzuP+jmutIila0XkfHcQxN8TBsK0?= =?us-ascii?Q?+ymtyMm5h/vD+8dKOchHjlApneJsvE6maTxpS1GHTHuparmYTrCg0jHrjFiu?= =?us-ascii?Q?vRpaAb21Xy/dH9wEOMoMNo9y5wKCWqkNW+uvsFKU3yTaVmIIrgI9Uz8ciu7I?= =?us-ascii?Q?CZGYXCDQzJHJAn6Dc/204HzPGJmWi9Zr+Y4W9M0HijaxAUzfgh1lOfCujn5h?= =?us-ascii?Q?TVbznSKyrmseCpXdi9wFeG2UIK3SM7QrO1iXdDVY9kAz19kdrWDvbYq4K6WD?= =?us-ascii?Q?krjqxvM7sS/jeJEiAyAx1aB+1Kz/x0aKIFxxpHSVBHCujXQXhfVyVl97CA79?= =?us-ascii?Q?0S53Jfbr0I8sEGhChM2c38mgTzoNDK1jZFqZ2k/jqTdID9GlOS63j+QiclbP?= =?us-ascii?Q?C/Isuu8yVFiRbpY3klcmX+RD4uG0IYsM35OQfzUMq1miNPkLa9JhJj6wCMl6?= =?us-ascii?Q?f5s6kIbnUoWoVJwEZ/5OR977rAT874SKGJdvDO9AEOt/1f5CQ=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3608; 6:5yQ/5hVS2AZonTF2L9W/uSZ51xtLTVgN/G5WhDbZlkI3osV822AKUvRvZg2X8TTEE0nUX66i95HnqW+rOZpCu8/LWnyqSDGw6cgpIxiCUy8WoRzp79ltzmGBWwQAXVo3iponh4EE427MR8YJhAPrWZ3jsIUNev/Kw+AfRRU8NWWHiSjhE9pAfb/AIkd3d2Chn1YKcIDGnq62thXsssaNYN003uxv/If7ps8deOVINLMouHTOfy5h2fRi80q/Z45fzB7J/5HptCobmCyGSdxQNx+qN1OOja0E+P5Fmlyh7rnS08m8RfBPZ7Im36b5zhV/ruYp1gDUMquRw4hd1stjNhDbaOLIU8GgPelwVQyuY14=; 5:2qeEiYoL5fElDvWNlrUlAy52QIL8bIZxKi8GJrVZubouAHS+JwMjcR0Bw89Xkw/0yA9P2fuel5ApD/0Q6/EPp/lYDV6ubU86j/63cUFHpesr+66daiF/sK034nt3gOEZkstBTg528Oo1hiEgbAvDAHzgxIhLbYGqrWybr5NvcCw=; 24:RgfK7qAaPCJ+nKfjoTGqqGM21KEguPN5U90UVGA76YAHXs+PVDRl0zqcBVtEaxuTnOReuYwuqHDtrg5MFaL7TraPrMm4y7NFsPfCJRjvBrQ=; 7:dR3yqcRdxjH00+ZCRdHh+qCgq8doktVhPexTgOqKGO6JWWwomorJ+vKAjIgj5ZCJxLbMggClGQmlaTh735rTeKlTHK0J/GU1GFuHvMmg9N7W5ZaXER4Ln1RYUu71RRLBqnlgQAa/67HBhCL2Ocfr1BVqwI/30mM7GiefbqMnc6sIGKS2KP2HnoAeUsGARWiDCFLWc7bCP8bYD6L/uKlbZ02QGWyC9VoqCTkra1Cex+Dyh8fGEgf6Cg4O49XVOMMW
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Jan 2018 03:17:28.5067 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: c487a927-bee4-48c6-d468-08d563a22a4a
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR05MB3608
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-25_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=3 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801250042
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/TZ1MXfk1D7ZA0ZA8Y-hWLmJL9W0>
Subject: [yang-doctors] List key model definition order and results w/ pyang/yanglint
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 03:17:34 -0000

Possibly bringing up a subject that may have been discussed before but
could not find anything on it so sending to the group.

RFC 6020 and 7950 both have the same wording on the subject around list
keys per

https://tools.ietf.org/html/rfc6020#section-7.8.2
https://tools.ietf.org/html/rfc7950#section-7.8.2

>From a model definition standpoint, there is nothing mandatory
surrounding that list keys be the first leaf definitions underneath.

>From a content encoding standpoint, the following XML Mapping Rules in
https://tools.ietf.org/html/rfc6020#section-7.8.5 do dictate an order
that the keys be defined before other subelements.  JSON obviously does
not utilize the same encoding technique.

   The list's key nodes are encoded as subelements to the list's
   identifier element, in the same order as they are defined within the
   "key" statement.

   The rest of the list's child nodes are encoded as subelements to the
   list element, after the keys.  If the list defines RPC input or
   output parameters, the subelements are encoded in the same order as
   they are defined within the "list" statement.  Otherwise, the
   subelements are encoded in any order.

Given the following simple example:

module test {
    namespace "http://test";
    prefix test;

    container foo {
        leaf bar {
            type string;
        }
        list car {
            key "far mar";

            leaf par {
                type string;
            }
            leaf far {
                type string;
            }
            leaf mar {
                type string;
            }
            leaf nar {
                type string;
            }
        }
    }
}

leaf 'par' here is defined before the 'far' and 'mar' keys, however if
we render out a sample-xml-skeleton with pyang, we do not take into
account the XML encoding rules defined in Section 7.8.5 and merely keep
the order as defined in the model.

$ pyang test.yang --strict -f sample-xml-skeleton
<?xml version='1.0' encoding='UTF-8'?>
<data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
  <foo xmlns="http://test">
    <bar />
    <car>
      <par />
      <far />
      <mar />
      <nar />
    </car>
  </foo>
</data>

With yanglint, given the following XML document

$ cat test.xml
<foo xmlns="http://test">
    <bar>BAR</bar>
    <car>
        <par>PAR</par>
        <far>FAR</far>
        <mar>MAR</mar>
        <nar>NAR</nar>
    </car>
</foo>

The rendered XML output will actually reorder the list keys to be first

$ yanglint -f xml test.yang test.xml
<foo xmlns="http://test">
  <bar>BAR</bar>
  <car>
    <far>FAR</far>
    <mar>MAR</mar>
    <par>PAR</par>
    <nar>NAR</nar>
  </car>
</foo>

Personally, from a BCP standpoint, defining list keys first eases
readability and want to solicit others thoughts on this (rather than
nested down in the list or via a grouping reference further down).
Generation to yin does not rearrange in either pyang or yanglint which
means any processing of yin would need to undergo some reordering
possibly depending on how it is absorbed.

For the JSON encoding case, there may be no strict ordering but
following a BCP where folks *should* send list keys before other
elements can ease implementation efforts in many cases.  It is also
likely that payloads will generally be constructed in the order in which
they are defined in the model.

So either I see making the definition of such either mandatory or at a
bare minimum pyang sample-xml-skeleton output to take into account
ordering list key leafs prior to other subelements.

Thx

/ebben


From nobody Wed Jan 24 19:50:53 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E72D12E03B for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 19:50:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 J_na5wS9Nzfh for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 19:50:48 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 7955912D950 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 19:50:48 -0800 (PST)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0P3oWQA016851; Wed, 24 Jan 2018 19:50:45 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : subject : message-id : references : mime-version : content-type : in-reply-to; s=PPS1017; bh=aQa7MEL4CvVtenMsYvahyCdM/fEGk1hCTOSkeAHo6XA=; b=ZK1+Vd567hjLfpRnHPZqUNGkSwUIsE24Jc5Nb+wPoPRtEWkW3B9nrr2W9V8leMzTaSfI DyS01ZawMg4BfXD5B4tSH6UWLPmH5MkKksV83YVgto7QEiXwkZO9QkTL/lwYjlotZbHp YkxvDBmLyJvyeB6Ja5900+L6ZRyEESKFcjf39gh0is043Tdj2z4KczBJEAuD9IKiqbWW 5/a7lAooOTTzzwb5dOCXKiaqoBQwLzvKsGOCjLWIsHZUjkDvTVw+B89ZjF3davfOsCgG Y1xUUCZ+Vk3FWHrxSGeT4/DyBbusmYeyVeu0qoXb+bJewRN8WeXT/EyGfnw9S6i3bdGB 2Q== 
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0085.outbound.protection.outlook.com [207.46.163.85]) by mx0b-00273201.pphosted.com with ESMTP id 2fq7eng0kb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 24 Jan 2018 19:50:45 -0800
Received: from BLUPR05CA0046.namprd05.prod.outlook.com (10.141.20.16) by DM5PR05MB3017.namprd05.prod.outlook.com (10.168.177.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.5; Thu, 25 Jan 2018 03:50:43 +0000
Received: from DM3NAM05FT029.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::204) by BLUPR05CA0046.outlook.office365.com (2a01:111:e400:855::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.464.6 via Frontend Transport; Thu, 25 Jan 2018 03:50:43 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT029.mail.protection.outlook.com (10.152.98.140) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.444.7 via Frontend Transport; Thu, 25 Jan 2018 03:50:42 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 24 Jan 2018 19:50:40 -0800
Date: Wed, 24 Jan 2018 20:50:38 -0700
From: Ebben Aries <exa@juniper.net>
To: Benoit Claise <bclaise@cisco.com>, Andy Bierman <andy@yumaworks.com>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180125035038.mxf7sm4f773czuof@smtp.juniper.net>
References: <9E242E7E-E87D-41C7-BFED-EB8185195F26@cisco.com> <20180110.223316.2175524120457720164.mbj@tail-f.com> <20180110220131.xmsorl4gwixqv77s@smtp.juniper.net> <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180116174323.e2b4zr5ffgrycnei@elstar.local>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(346002)(396003)(39860400002)(376002)(39380400002)(2980300002)(189003)(199004)(105596002)(1076002)(2950100002)(23726003)(966005)(46406003)(47776003)(26005)(478600001)(104016004)(50466002)(68736007)(55016002)(76176011)(2501003)(77096007)(106466001)(7696005)(336011)(6306002)(53546011)(186003)(229853002)(5660300001)(53416004)(305945005)(81156014)(81166006)(8676002)(86362001)(575784001)(356003)(97756001)(69596002)(110136005)(316002)(6246003)(16586007)(2906002)(93886005)(53936002)(8936002)(97736004)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3017; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT029; 1:jHzOWJnByuMtWTK2mCwr1Us/4IQDaICPeLinSzeMyqqDn4qc947izC0r7x9XO7Ir3qvKgdfhHfV8NnvA+gFxM8aVgtpODQod+fqmWPqhkVwkb3tzewUf3M/JEmXyp9O0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 785d796e-dbe4-4891-6351-08d563a6ceef
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:DM5PR05MB3017; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3017; 3:PZIVu9iqxAuSkBYtolaVeOvm5d7cQiUj8MuWF42rJJlW2p8BCbYiI+n7ynA1uXyti8TVl+30/JG2ZXp9QsAtcAlOsXsVtA4JsiU9RsIP7Y5+NclZzDC6W2zlfBDySLDL77w4vpkP86P7+VVXhsSax/MHm3eB9L3pSEZfMxtINpYM38z0BE0PiP4ejU13llMoaq+MB1BvUMCoaHDC9DRZwl1UnnIAix8uSNcvUDRqz8EZL8K9X0I/yD4MMmwjOZgnEJzA+wEM66GMOsX8oqH4hXZzNufWn5rG5K4SPsaOxDi1I0Ka4Nd3SSKFJUL4KN4D961vYs8QF4QIxT0/JqdhNU+Pz1516H/6pglazbjBDLM=; 25:LRuVySGVtEosh9BBXGvsCaou4lCqI+YEavkEUX7HTRucJZJlnNocl0OWZ1S7zFKCdbeHiPPSc81Zdn37JoAeOfKCS/sbtQqHxklmpNLz2Vc1CeAm36AdxUXXw6GberrTKjstgM9D0pfVWNFCtY64Hp6cDsibM/j+e5vM7mt8ULIVgKN49gaLHCYB4suw+2Cr+TrVUMxQLQxNjRjopTy6EUPTx2niw+zGppqRMKfuaYrKPb5jea6cJpuqsc4QHjvcSft3MJoaeyubdFIYDstj7IKjZPk+HNhilmdXVVzaAv9N/PmqtEhpx9sSbGws464xXZ+kR4nJ3XDWp6HrfO2nFQ==
X-MS-TrafficTypeDiagnostic: DM5PR05MB3017:
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3017; 31:MJnU6s+s7qAKBILkPKpcbfSeXMwhK6sW7VIkDnAyQZHK6PVipYAReRg3vTIhLlTFlv0W+DPVcOHjIwQ1dyEnPz7ki3KAKZzpA5DYj5XnWtYPS8yjkcB0MqZw2R3liRbOT0pQjAjXamSfdIaO+vfXotHXLSNzHFWjmVNS/y71ZjCMoZz8wu6qQqrK7W22ohK3QioZofe6xU7LaqdaaWKFGkhc9q+sVeAnYrdLQW7DjvI=; 20:gICUgjr4iyD9viPwGWhHDo5G/iFPvkoW//ITosNp0dtgIu9hr8LgJof/pcscWeocwAjpBQOcEpV6kzF5tHW0BO9lIgd9q6vllkjdgPgolYktXTN/nJcx9tBpChdKWq5GhQ9fB4QoyjjnowOaaPqJZRj2WGorQGFbJNfR5PRT4FEkhTC9ausBY70cfZvUw1PQiQZb02V5nk5LuUinZj3luXGJUbu8xiz8E33Um1wo8fLwlfD7DwV4R9ayq+HBkpc3lvcfufHUXLqnMT4o6EkS5VNlN6OzXiRotH205SlJxBg0DPxC7z/h3TB5b4axWxzXtW29KXxrnXEOzHBUeNkFhpD2mL49UCtfjHPw2QF7DoAZd76JtzOW63n/1Cxl/xgJmdCYUheAP2ifzR7b+6nOKU3o9f65H1mtVbJAMQWPngPZuNdHhAqdYQyAif4Aq+o8SVFKub5nb7D1K/p0E3tRBmVQMgW7b+1HciTSwJz79DO1f3V9EKMfb4XJh/+9RNjg
X-Microsoft-Antispam-PRVS: <DM5PR05MB30176FA64624690D356EE7EEA8E10@DM5PR05MB3017.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(10436049006162);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231023)(2400081)(944501161)(10201501046)(3002001)(6055026)(6041288)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(6072148)(201708071742011); SRVR:DM5PR05MB3017; BCL:0; PCL:0; RULEID:; SRVR:DM5PR05MB3017; 
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3017; 4:k600XHHf3uIuuiwiqHq6Uc0ylYvHuymwdnx0Z6zoAN7uSj+O0Up+EU97AZRldyNWA3OyIZwr/ulndLa8vwqXluxUiSh3+XxJepsun9stu2UhBBbPQ9yHLpCBZwe5kEaABqgqWWne+BnUFbwN3PsNNLox+cePWtEm+QFXcJWGjJTLScdHr5kFJ1QjdzmCVy2CahxaaXYUWz2uDuYIxYVuwEGKGmnLkUu2rBTj37MMZFNZvE5LN/eOzsHj8lIce0gr6D/oDPnddBBPo72PKlDPgfEAYVHPnKAzB1DpXVtfjhN4ag4JoL9vAcXdSvcRQ0XS
X-Forefront-PRVS: 0563F2E8B7
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; DM5PR05MB3017; 23:AJQ3UCZ72RlfatBC8Ad+vvuTAjPhiQd8LfINQK8tR?= =?us-ascii?Q?VyaWhh5y3v5IoCRYECY059ZSGChW/WIreHu/fxr0Sc3c+Djx9to5hT1yugnJ?= =?us-ascii?Q?0U2+U87hsx7MeL0Hs1QeWaW9D8RFh1U8NFYlExGP2UhRMWImW7haXlUyK77/?= =?us-ascii?Q?VDaTfRJ0xBH+BU1li5xxsVPSXw4WyV//711kXf12yB4IvRQjaxrDcgJXvezf?= =?us-ascii?Q?698hijol8volqtbyTdEBtRIMZR6xMEILGD+NT6WZtrNGQSAWSPNmn2jd7AIQ?= =?us-ascii?Q?vuI5Qk2tl5NHM3xqgbcF+XYeV1Sf6NKVm+t+IRHW2dEcCjakIxRn+Sh74KMB?= =?us-ascii?Q?HlUObrAi0G6wkyUFr9o2FqfSGSkmwBVizIQ7vgGqjNzMKtB56wGnvNZteQja?= =?us-ascii?Q?4FJxpiuWGgYS5m11uJLbxaE2HViUjrXsiLZJTxI7h+IyU7kz/8FGOEuTRHjR?= =?us-ascii?Q?BYo6s0Mz2jNqvMMmg9t1lj3wNbWxaMJMhhb4hybeUmyV2+wu6ctZaFhxf5Cn?= =?us-ascii?Q?KcooIbb8ZDZxN3w6kYa3VDAflp5/PoiXKFzx9TtTsLOs83PB069BntKInNQ/?= =?us-ascii?Q?VAnL3mWNojf0IqpyfDMlLnZ9TMWjZ7wLPYcirX0rueukDVRhzNfKU68FehWT?= =?us-ascii?Q?nZM+dHY55xzgpaGfSj1ZfZLC1xCQG+HAfXYFLeb+3aHmWQCusVJtZRJEn0Og?= =?us-ascii?Q?8VGzjxTfO0B+mn4XFPqRMwW0wwv5drl7uStda+c7U06aTEFjmMMVmTGZwCi2?= =?us-ascii?Q?Z9zb521Ok6cjPF14oLW+RmKTAPAKAQ/Nx7ikH4efFa8DvNgpijGH+W3o6zj0?= =?us-ascii?Q?FydMqsfV7SJjczIuIxV7GsSj29pJhe5A542Fy6dq56c8SU3DxgAS8/mfZ/5V?= =?us-ascii?Q?KLfqw9A+kzYzb3uuAOovrLRri7WtwWetS5DEF7PxCm/Wn3hmOWd+5FYPI6DO?= =?us-ascii?Q?wfFvaNzTaHw/Bslt/Y5Hsq1+E8AK+enLfDg5CUqDaC9zC96OtXI7JUKCYo+c?= =?us-ascii?Q?4m80tXg6Y5C2wcBj9YAU+FDcOKZu9K+oQ5w/19G+d4W+4Kj1V2LWCMSJk8RT?= =?us-ascii?Q?d0W/MrcR7c/E4oEjIctJQdwDWtQgRhz/tIGlb5KT/3Zg9+Xc64U+TJuJZ+RH?= =?us-ascii?Q?tOGXu4Fd25pCg5sN7A26hAjJHeJyW0uoGqUNP9bOx5Ajr/C7xTxo3SZiEpA9?= =?us-ascii?Q?lhf6nAUETqBwzrcdvNldjRs3auoBj7IqmMU?=
X-Microsoft-Exchange-Diagnostics: 1; DM5PR05MB3017; 6:v0j5F4sUJXhPzhDLSJR10nUbjEr8QAtmnQgPQDpHY2I2ZM3TQx4jEr7cfJqGA+DhjqY127Jyni4zrxK2fg+YlfBJQlEFgML6JaioiUQsyIM13gZgUsDkzlR8tEpM+GF1ENsMuUUTLuq+mqn681ZYxdvHvxI6CJwQlyEjwuxAs3zQdzqjDkag+XpNQCctUzWph5ijtGyOtvsIAqa4wmQ9g4acHKhEfZsZUiv4c/b7KLTa4S/WPgN+8L6DAARWTnlR9cO67ZlsSU3eBY+3RK5k2kVpmSK81b5l6Yn1SAWDvPod6bdcTYQhHBHFouHQDWkIoqzCO1ohrZqNDgQKv1tA/gz3zVbenlsF0vSqSThCz+E=; 5:HWrQPI9wkpFRtkcF1hGpgORyvh6RBV1JJlnmnB7N6eMr8cmkZTd66SMUGH0el0GPkzRFa79jwANkSgDDYK/v7hcHKiS1QpUSUkSXeGARP//5EqjBDgQKPeO8sZGKNp7qC9tpGXSpvIT9yEx/qnHE5+1CseMlv5Z7xwcUtT5fn/E=; 24:uwl+hB+PdB9HfQvceMO2PUNR8IzCRi7WvuoLUYBY4MQ+7AC44+bP2E6EfSwMipW9w64RF5K6XJOBlnjzMTVpMtzQuI1ICNWMV22wf6mLq8U=; 7:7Bzb+o19vtV3OJhvS4rMz6CvCBpSr+nvlQf5moEQTCC3dm0oHT7/Gy3cO25oWtYlJKrRc6Rl/M8SydBzZlAnKetOEJqyJC0+c4vnCkkxnpoBjbog9sqOwsGcIIpgjGDo0BKIQSxORKvxsIOHmGKdTpofMDPMuYK2/xD4qu8GRpXhk14St3mbCt/bEtb3FoZH6Cf1LnKEaCrQSb2vC9j2mHePaOcEm9FfSXZYPcOaPzUUoUEOUUBoOTEZpwm+WiJJ
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Jan 2018 03:50:42.7027 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 785d796e-dbe4-4891-6351-08d563a6ceef
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3017
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-25_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801250051
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Y0xnSYzQebIwQdZ6AwOQIoidn0Q>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 03:50:51 -0000

I think this change looks good

On Jan 16 18:43 PM, Juergen Schoenwaelder wrote:
> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote:
> > On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote:
> > > On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:
> > > > The feature-per-leaf approach should not be approved by YD.
> > Do we want to add a sentence in
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=DwIBAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=coUU0hud2Ev6mARcSeDrSXnjLioAu_TOiWqw0BDn_c4&s=yaqHtXjjzMi643nHVelr4Zq0_YelOsvOMfEMImH4NHE&e=,
> > expressing that a feature-per-leaf is most likely the wrong approach?
> 
> This is difficult to describe. Perhaps something like this is a
> reasonably small change to the existing text (which only talks about
> too big features but not about too small features).
> 
> OLD
> 
>    The YANG "feature" statement is used to define a label for a set of
>    optional functionality within a module.  The "if-feature" statement
>    is used in the YANG statements associated with a feature.
> 
>    The set of YANG features available in a module should be considered
>    carefully.  The description-stmt within a feature-stmt MUST specify
>    any interactions with other features.
> 
>    If there is a large set of objects...
> 
> NEW
> 
>    The YANG "feature" statement is used to define a label for a set of
>    optional functionality within a module.  The "if-feature" statement
>    is used in the YANG statements associated with a feature.  The
>    description-stmt within a feature-stmt MUST specify any
>    interactions with other features.
> 
>    The set of YANG features defined in a module should be considered
>    carefully. Very fine granular features increase interoperability
>    complexity and should be avoided. A likely misuse of the feature
>    mechanism is the tagging of individual leafs (e.g., counters) with
>    separate features.
> 
>    If there is a large set of objects...
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.jacobs-2Duniversity.de_&d=DwIBAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=coUU0hud2Ev6mARcSeDrSXnjLioAu_TOiWqw0BDn_c4&s=TlDlQ41jN97aNeLJGGDlYf6DPYwdLss2UmogmWbTPTU&e=>


From nobody Wed Jan 24 20:25:25 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C5412E85E for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 20:25:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 lBJJEI24FW7a for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 20:25:20 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0a-00273201.pphosted.com [208.84.65.16]) (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 72C1512E6A3 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 20:25:20 -0800 (PST)
Received: from pps.filterd (m0108157.ppops.net [127.0.0.1]) by mx0a-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0P4NhAt014891; Wed, 24 Jan 2018 20:25:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to; s=PPS1017; bh=i3xIzjQJS10x30taZghp7XJ2lAlKDxJ/YWVo+f9XZm8=; b=tIXdlACYvq3GEflSjvrRj9Ob4cUNuFQnqiwsJ41Ehqxny5zzizwOVAsfpeiNzMhVMRRD Wk3QsMeazWrkcv4OMFDh2EuTT/n+Yr8dNKiR3HtqG4ldwULKKqPh8oebWN2dJKGJxySz JQ11PSTYTDQ0rM85ymB78EGHnJifhiVJDmJUvp9LmDyVMM9jhrqG2R39hOArwJL67TK+ dOYgCuzREdH8/hi6JjZO2F5zyk3DKEYCzc2p0I3GdzVaJECKkQ/zQe3kJIh2Nv0BSU6/ DBVC1datkzgGVUfgtD/S8KUPxCdXpYhlDpnFU3bOwxmHGXMRmRP73b2IzZtrZuFsl4yF nw== 
Received: from nam02-sn1-obe.outbound.protection.outlook.com (mail-sn1nam02lp0021.outbound.protection.outlook.com [216.32.180.21]) by mx0a-00273201.pphosted.com with ESMTP id 2fq831r0cr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 24 Jan 2018 20:25:17 -0800
Received: from SN4PR0501CA0103.namprd05.prod.outlook.com (10.167.128.20) by MWHPR05MB3615.namprd05.prod.outlook.com (10.174.251.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.5; Thu, 25 Jan 2018 04:25:15 +0000
Received: from CO1NAM05FT045.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::208) by SN4PR0501CA0103.outlook.office365.com (2603:10b6:803:42::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.464.6 via Frontend Transport; Thu, 25 Jan 2018 04:25:14 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by CO1NAM05FT045.mail.protection.outlook.com (10.152.96.159) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256) id 15.20.444.7 via Frontend Transport; Thu, 25 Jan 2018 04:25:12 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 24 Jan 2018 20:24:46 -0800
Date: Wed, 24 Jan 2018 21:24:45 -0700
From: Ebben Aries <exa@juniper.net>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
CC: Benoit Claise <bclaise@cisco.com>, Andy Bierman <andy@yumaworks.com>, "Reshad Rahman (rrahman)" <rrahman@cisco.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180125042444.vtdozlf7mm7wpcz5@smtp.juniper.net>
References: <16188AE1-697A-47E4-817B-CB6D7CE6D0B9@cisco.com> <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local> <1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com> <283f5774-5995-6ae3-16b7-385b8ea270d1@cisco.com> <E5618F14-46C8-40BB-9116-9E4A866575BC@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E5618F14-46C8-40BB-9116-9E4A866575BC@gmail.com>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(39380400002)(396003)(346002)(39860400002)(376002)(2980300002)(189003)(199004)(39060400002)(1076002)(47776003)(2950100002)(6916009)(6246003)(7696005)(53546011)(76176011)(86362001)(575784001)(2906002)(69596002)(4326008)(2870700001)(53416004)(229853002)(50466002)(6306002)(55016002)(53936002)(305945005)(5660300001)(105596002)(1411001)(8676002)(356003)(81166006)(316002)(81156014)(8936002)(93886005)(54906003)(97736004)(966005)(23756003)(106466001)(478600001)(68736007)(336011)(77096007)(26005)(186003)(104016004)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR05MB3615; H:P-EMFE01C-SAC.jnpr.net; FPR:;  SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; CO1NAM05FT045; 1:VX0NY8cUeW6Cr+xbB0tqrOuYXJ3IMgD5VtU7liAa9wrE7EPIsjzmP1JsUcdX5UamMKDRuc/jkDz87M7x0/aRuvdPofUmU6tZtj+1gEiId5sTMaf/Shib4x3/KqLZbjnA
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 301bcd19-ef3c-48de-d091-08d563aba179
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:MWHPR05MB3615; 
X-Microsoft-Exchange-Diagnostics: 1; MWHPR05MB3615; 3:Hw3aAGXfgkSzJYaQ7ChlpcoXLt6QpwewZlaAkzrbIsrhB8UUlbtclmSXZz+almLrrr/HmLWfFe/o9sdPpSji5sgsn0RzwzQmpq/8KksOObUWxVQSntUv0uPcXrDb7aHbQ3GuaJ/QgrZ4013CEUidN1A9p1ZsEdjeVVu7pH53FTOGasoPQJ4PTuff2vljpoGEszjvdyWpmBsTCD2sdr+xgqzEJbsxMOC84+uvcWWS1FidfAYhTuHM33ImKKPz7JHb/0DNkPRt5DjoOtzZH+58TZHw5fgWA8GYjTdkHJOn7nMYKcy+1MeEBXPcM07FFHa2Uf9WFpCqLjrDa9nZHL8Nz89IcSySzBa8lOoGyZWcHYU=; 25:LqQXj6/eAvUEW90+jtzhfHI8+HmMpdJyahpTVI+ouO0gFbQhmQ4lbUq/1muhaCDAUQ9qbMrFdNrZQvhTmeLckmRBCz7T9GD+6Ikl3Kpa0bXlM5z9aGeGUJ3rE/F8Q0Sdk7EVRvfScLYcpsYl+z7FaqffQVf8iWz5SJXVIgfiJN8/GZlkxsyKgDQZEIulbCOl7R13XCyOqVD+IkWa3SMHiji5X+LfRcrFqubVfms4BBovRM4MnUz7EYiJxZgfs/BD0YSugN4bfRp+8hn66p9BjmaZrJxXRBGSWVen0FrfXd7+/81F3Ye7ckLklit8NVlWsx2dMl7aPIyIbtg1CuwOSw==
X-MS-TrafficTypeDiagnostic: MWHPR05MB3615:
X-Microsoft-Exchange-Diagnostics: 1; MWHPR05MB3615; 31:2hESUIKXuv/YKm0TFNE0up/27hPe0lqUbRcz5ObzkH8U5DqTN7mOcLJeoKvrwLS2SC80qoWjCGXsuU5APoY/NAW5IeDbnn/2155BdMhP8Nt4k3VHgVN6UcNsta3zvy7RNEbtN0nfn84WZoyEoH0ZSfsEowROiPZf8X1BXgsTCgvtK6j//m44Q/sZ1J5H1Dhbvg05HsyLFVrTViuTjNKxchzfB6dSYSywAtIhCrZ72Ow=; 20:6kHf8yp2kVuR8U0qML07uNuTszff08G+ojdMM+3pe8E6WICxGSdByzfOmlOE+t/Ct9rPfEbPlAyYKrH7Xf4dIQejYcmp55hA0tQNQ1qAZov7yeaAxYXy3wylN8rJCxSwSdTYnyGc04/cxsVDEiuzz3p9RO0MbcYHAI6+pEcQloGvcp4iBjHpbHR1TX0cGRMigvmVPkQ+XmvC7nQVor6rFWZ65h9EHipmbWkJ3I4zMKjK4ayC/5+Y5dtnCroO//Cv8iCCsB5ATgigdBqnewoVlgawnvLiZ0edM68ygZ1L9T7vpXZ2yka/3klSQvrtxcheouM9tYqswsGHAd/WxzrpQ3GWEAeClR05xnnybVi77JlCrrk/Xvwzu/cuh8WK1V2s+Hdxw9HUEiySwYB4KwK32cuStBMMm0R9rutL+SvjASdGAQfzyKvlsT3myBMfafKV5KgJnSwhYc71PvnL1Il8LeBpoy8Ef3H58D+2SONDuzRyJ4vwu9PdRQ6JBq90qWqe
X-Microsoft-Antispam-PRVS: <MWHPR05MB3615B232931CA1EA5818DF13A8E10@MWHPR05MB3615.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(10436049006162)(85827821059158)(95692535739014); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(10201501046)(3002001)(93006095)(93001095)(6055026)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123560045)(20161123562045)(20161123558120)(6072148)(201708071742011); SRVR:MWHPR05MB3615; BCL:0; PCL:0; RULEID:; SRVR:MWHPR05MB3615; 
X-Microsoft-Exchange-Diagnostics: 1; MWHPR05MB3615; 4:IWGATqDXAWKlVUGPhbwjx7pRgF5yLsoU4riI7rjEsA2mRFsMoKWFoRF7AyViFoCUb08T45zH8XqiXsA9aYmQuyhIz3dKxsgKcVwIk3mZ7gc4oQ+Fb+NOZP6TO8UAcuBnP5lsvu3kZhEDZWFmd7Ccq6Y9si+bBaG0L6Xh8dckuEm0wpyQsJ400xjKrd7jd6+kDruhHMC5nOasY9l3hpkcJSiUdZXnf0gha7K9nAhLpnI2SXMABzQ0cOzIT7kIrhFSLJFvUYjepcBMWfniAGBYs2saK4I+8pzEZivYVa9R/ogpbsUPdyqxlypHvlA0NCtg4hdq+yw+YnoXEWP7sczC9XkxzEmqGuMe5zRGhnhPTARRLrqcPrEXnCi2ZeBy7JDrXTxGZ+DiKuWw4oY8YXZhgMBm7AiKDFWPP33qdV1h0Bo=
X-Forefront-PRVS: 0563F2E8B7
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; MWHPR05MB3615; 23:54BUxzSKw/KCtHUOlvB4MqzC3ndHbc81/vQscSa?= =?iso-8859-1?Q?wY5LeWIObWxQVON2G5wLHSupK6GNaujtJPCbndxP0nsLEKgOheNVe4WrXF?= =?iso-8859-1?Q?0rn4d5o/mFdGDTwEwFfYfI49DhZQ7a22ebz8BFm1b+w4q+pDyHncd/nlZ6?= =?iso-8859-1?Q?EBIHODV1tmdLDLWWOcKDGuVUa3ubp5Hxtiuu7vLDgwcDDhFg/2xKO+fdJF?= =?iso-8859-1?Q?U/NPDCX21pY16PPWwApbZ3jvm3uDkihG8pCXW5C2SLjyIl+UDu4DcUfSXN?= =?iso-8859-1?Q?3pxSQ5WaBbvxXMcP//GSIN6DcuOhBx8zQ0bJssa8dO8GOpK0uBELjhJv8f?= =?iso-8859-1?Q?b8BelMKhKmuwVBWulKKw+Z1iR89mTrsS8az0FX9wK63fQFG2oZTfWEo2TI?= =?iso-8859-1?Q?9pd5wB1dLyY4z9IHGYA2pF61RoD0TQAPV23ESUH20FCdT8NWxKLj2eNNVU?= =?iso-8859-1?Q?QOu5mjM+OaWRvzJ8e7uLnmQfGEIRmeLi/KEVql4nLxVN+t0JFUWWcY7GF8?= =?iso-8859-1?Q?6kDEDqHnabsuyNcznYdPi3N4ac2yPMIQjQj8pGFy/HaY4foRRlCuTQlzk2?= =?iso-8859-1?Q?joPiiSA4shBkN4WjYG34nGEOE1nkwwT6A8E3cVctzIUbBMOsMvs7gy94gW?= =?iso-8859-1?Q?bdD1kNhCOYTb2/V7er3+eWj1qxWpKKxlKFCJHnIZHaZ5KG87GiabJlbgoE?= =?iso-8859-1?Q?1r9qp0UNkK/YGM6s53b8TQaIG/3KxIEnWCfDV6kwLK5LwkKTMVvm7lNfVl?= =?iso-8859-1?Q?kY+kYzzeByVykzY4nEq6VxFpqtHLQ1ZobEwKIWKOhapke0W6QNpUtTtX3T?= =?iso-8859-1?Q?8Ybdj+uzhBYiqIzKwl4TJS2Iw4JIItdFgdoelyCYjXClGEPLxXuCnMIZqD?= =?iso-8859-1?Q?K6HVrARTnKh1Dy3kwOQd1TNmGHzDmCaUz9qdxKDq924f1/t4NpOilp2yUI?= =?iso-8859-1?Q?+pedlWcD6llG4bmlBgVnGMs5GpCbH0TZMxW3CKIAMcyjFpusFbrCKBoXon?= =?iso-8859-1?Q?R3Ck/cwz2YaihzcQoypWX5CJZJ+cN7EnhEcIaqJ+UyQvZ3mg18DlwlOAby?= =?iso-8859-1?Q?j1fNQHWW1lxyI15/lkoptgtZAmNlt9DYxB/OsCIfCC9b5eEiASJmiR5AKA?= =?iso-8859-1?Q?cxBL0BgeYxz+E6gkI2RB2AyBwM0c4hdH9hsvrNOTl8B8OJUokia+tFyE5z?= =?iso-8859-1?Q?bIq6PtJZu5RSOGCOnfRuTPXfea0aRD0S1qRtQMaRm0J5vMrnhoZ/djq5lM?= =?iso-8859-1?Q?p1fwhXmgR2hKsEOMztH+ViFWzsJAsw2EselN5Og=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; MWHPR05MB3615; 6:b9eZcJqIkMOl71Bh9rzYCAu6IwIYUJVwkxYlNhsGTyexWas+dBVgQMkL1yrsfGA2Dhxn9OY/Vdzh7X+6ybX13YFsB2LEP5FbL+iOl1xx2M1HxtZGcGzems+jQ754d1uYxS0JfZ6HG8Q9a5pU34cOpnXLFwO9lz3+OLbYG9MBjQ+zuefKAobd517waPzoAgIN+dhYZFUxh+I/Srp9jXwzcJXSsDuR+ApVUvOjRKYpHnUWmx0ZzORsdZS3iIVXy+HAJpI11WJtuvgYfNUxT+MbxwObKp9Y1xaJ9qmTkuxvRiOUvSlDHwV8etlN/kxaI0bwNAbGQdlJN5zMKOjpTIkARoJ6MkjvTxrLoc+sF9LOqfw=; 5:sfYhIUhQT20NpnjMtPx9y2iRgfkduc+rWFyav2pz/ZW1MUqyEpZLWHcfXpFyj9OlYIuGIV3CIILGgvcp26fRuwaTzZrAypyQX83BeDsSZU5R+dfPP26X8k6ZjawY2+CJkaoncHHX/ZkE8zx9WoorQmodomFh9O9gb+7B2DFW8do=; 24:Up2YSqPTMmDxaiuW6aUGeakh6ZFLrTedF7MeuBKmt6wXL+uwCS5tKILBfgXUzuKVTzMVlrNr9cKG4E7ph/inRs4LQtq1eb2FBKU+1bYrkkU=; 7:MkWk2DRy3r8TgGz7ScuNSCFRtBz+HpkMfrqVVdiiUwPG36oGri+/KBLsu/iCkZCUyfRgxpB3L1c93n8qrvkEjzjnANxCBW1pe9cQJB7hU72uTe+KDL04KdqhW9zojMe4tY2ufBzrzLXQQ8TRFdLLxjhaOWBYOJjf9QtXsScqtpG78ZMM/c10WNhBe3AEUZ63Q9ufVrjWIxyKOCl0gSp6EBNz2eEDFuVj2U+CVXwBWptWYd3d2vb7LWd3CK8dPH0C
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Jan 2018 04:25:12.4183 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 301bcd19-ef3c-48de-d091-08d563aba179
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR05MB3615
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-25_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801250059
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/x-AcC6RM1J8zUACVXQ3Nec-dK3w>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 04:25:23 -0000

I'm not sure I understand the intent of the newly proposed text

I'm reading this as now stating that if a 'feature' is optional, then a
'feature' should be defined.  I think the old text was mostly correct in
what is trying to be conveyed.

How about something like:

   If a data definition is optional which depends on server support then
   a YANG 'feature' statement SHOULD be defined and conveyed through a
   NETCONF or RESTCONF protocol capability.  The defined 'feature'
   SHOULD then be used in the conditional 'if-feature' statement
   referencing the optional data definition.

On Jan 24 10:49 AM, Mahesh Jethanandani wrote:
> How does one define a feature statement that indicates support for NETCONF or RESTCONF protocol capability? I thought feature statements were for features within the module.
> 
> > On Jan 24, 2018, at 5:54 AM, Benoit Claise <bclaise@cisco.com> wrote:
> > 
> > Btw, along the same lines, in section 4.5
> > OLD:
> >    If a data definition is optional, depending on server support for a
> >    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
> >    statement SHOULD be defined to indicate that the NETCONF or RESTCONF
> >    capability is supported within the data model.
> > 
> > NEW:
> >    If a feature or a set of data definitions is optional, depending on server support for a
> >    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
> >    statement SHOULD be defined to indicate that the NETCONF or RESTCONF
> >    capability is supported within the data model.
> > It will also be in my AD review email.
> > 
> > Regards, B.
> >> Hi Jürgen, 
> >> 
> >> I like it. 
> >> I'm busy with the RFC6087bis AD review and it will be part of the feedback. 
> >> 
> >> Regards, Benoit 
> >>> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote: 
> >>>> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote: 
> >>>>> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote: 
> >>>>>> The feature-per-leaf approach should not be approved by YD. 
> >>>> Do we want to add a sentence in 
> >>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=uU5M6cHYuTrKiyxOMMI8MKvBIpYS_yg1VSIYI4MfxKo&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=uU5M6cHYuTrKiyxOMMI8MKvBIpYS_yg1VSIYI4MfxKo&e=>, 
> >>>> expressing that a feature-per-leaf is most likely the wrong approach? 
> >>> This is difficult to describe. Perhaps something like this is a 
> >>> reasonably small change to the existing text (which only talks about 
> >>> too big features but not about too small features). 
> >>> 
> >>> OLD 
> >>> 
> >>>     The YANG "feature" statement is used to define a label for a set of 
> >>>     optional functionality within a module.  The "if-feature" statement 
> >>>     is used in the YANG statements associated with a feature. 
> >>> 
> >>>     The set of YANG features available in a module should be considered 
> >>>     carefully.  The description-stmt within a feature-stmt MUST specify 
> >>>     any interactions with other features. 
> >>> 
> >>>     If there is a large set of objects... 
> >>> 
> >>> NEW 
> >>> 
> >>>     The YANG "feature" statement is used to define a label for a set of 
> >>>     optional functionality within a module.  The "if-feature" statement 
> >>>     is used in the YANG statements associated with a feature.  The 
> >>>     description-stmt within a feature-stmt MUST specify any 
> >>>     interactions with other features. 
> >>> 
> >>>     The set of YANG features defined in a module should be considered 
> >>>     carefully. Very fine granular features increase interoperability 
> >>>     complexity and should be avoided. A likely misuse of the feature 
> >>>     mechanism is the tagging of individual leafs (e.g., counters) with 
> >>>     separate features. 
> >>> 
> >>>     If there is a large set of objects... 
> >>> 
> >>> /js 
> >>> 
> >> 
> > 
> > _______________________________________________
> > yang-doctors mailing list
> > yang-doctors@ietf.org
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=Uah4DbYVrvtZTrkciA0m1OfOgmwMXrRg_tjGmG0iX8I&e=
> 
> Mahesh Jethanandani
> mjethanandani@gmail.com
> 


From nobody Wed Jan 24 23:28:13 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 782FE12E042 for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 23:28:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 4UU58sAZKm7V for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 23:28:09 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8F7312D95F for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 23:28:08 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 0CCB5EEF; Thu, 25 Jan 2018 08:28:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id XX7c41ySAFDJ; Thu, 25 Jan 2018 08:28:06 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 25 Jan 2018 08:28:07 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id E86C520149; Thu, 25 Jan 2018 08:28:06 +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 IlLlS2rPZUvE; Thu, 25 Jan 2018 08:28:06 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id EF92B20147; Thu, 25 Jan 2018 08:28:05 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 003594228D2E; Thu, 25 Jan 2018 08:28:04 +0100 (CET)
Date: Thu, 25 Jan 2018 08:28:04 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Ebben Aries <exa@juniper.net>
Cc: Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Message-ID: <20180125072804.qpmhvax6hojrprrf@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Ebben Aries <exa@juniper.net>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <20180110222610.qgdknjrkxdw65jbk@smtp.juniper.net> <20180110223801.hx23svra4xpuww2i@elstar.local> <CABCOCHQEsHGETaKnfa7bBM955h1L28WqqcT72MSRm4xcoNW1pw@mail.gmail.com> <20180110232830.6rqbhpw5s55kx6zo@elstar.local> <29599bf2-f920-355c-8b3f-a7d696380e73@cisco.com> <20180116174323.e2b4zr5ffgrycnei@elstar.local> <1101aeba-67ad-f8df-b8d0-30109b915129@cisco.com> <283f5774-5995-6ae3-16b7-385b8ea270d1@cisco.com> <E5618F14-46C8-40BB-9116-9E4A866575BC@gmail.com> <20180125042444.vtdozlf7mm7wpcz5@smtp.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: 8bit
In-Reply-To: <20180125042444.vtdozlf7mm7wpcz5@smtp.juniper.net>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/qD9ZLn9QQwAK8wEfwkXl4Hy1QrQ>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 07:28:12 -0000

It is not clear what the intention of this paragraph is (was). It is
unchanged from RFC 6087. The paragraph could mean multiple
things. First interpretation:

   If a collection of data definitions is optional, then a YANG
   'feature' statement SHOULD be defined. The YANG library then
   indicates whether the optional definitions are supported by a
   server.

This is just restating how features work but perhaps this was the
intention in order to put the following text into some context. The
text could also mean this:

   If a data definition is optional and it depends on a NETCONF
   protocol capability, then a YANG 'feature' statement SHOULD be
   defined to indicate that the definition depends on a NETCONF
   capability.

This would be a discussion of a very specific case and not really
helpful in a BCP, except if it would be intended as an example (but
there is no indication for this).

Whatever we do with this paragraph, we should avoid talking about
protocol specifics and we should point to YANG library instead of
talking about protocol capabilities.

My proposal would be to either replace the paragraph with the first
interpretation given above or to delete it entirely.

/js

On Wed, Jan 24, 2018 at 09:24:45PM -0700, Ebben Aries wrote:
> I'm not sure I understand the intent of the newly proposed text
> 
> I'm reading this as now stating that if a 'feature' is optional, then a
> 'feature' should be defined.  I think the old text was mostly correct in
> what is trying to be conveyed.
> 
> How about something like:
> 
>    If a data definition is optional which depends on server support then
>    a YANG 'feature' statement SHOULD be defined and conveyed through a
>    NETCONF or RESTCONF protocol capability.  The defined 'feature'
>    SHOULD then be used in the conditional 'if-feature' statement
>    referencing the optional data definition.
> 
> On Jan 24 10:49 AM, Mahesh Jethanandani wrote:
> > How does one define a feature statement that indicates support for NETCONF or RESTCONF protocol capability? I thought feature statements were for features within the module.
> > 
> > > On Jan 24, 2018, at 5:54 AM, Benoit Claise <bclaise@cisco.com> wrote:
> > > 
> > > Btw, along the same lines, in section 4.5
> > > OLD:
> > >    If a data definition is optional, depending on server support for a
> > >    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
> > >    statement SHOULD be defined to indicate that the NETCONF or RESTCONF
> > >    capability is supported within the data model.
> > > 
> > > NEW:
> > >    If a feature or a set of data definitions is optional, depending on server support for a
> > >    NETCONF or RESTCONF protocol capability, then a YANG 'feature'
> > >    statement SHOULD be defined to indicate that the NETCONF or RESTCONF
> > >    capability is supported within the data model.
> > > It will also be in my AD review email.
> > > 
> > > Regards, B.
> > >> Hi Jürgen, 
> > >> 
> > >> I like it. 
> > >> I'm busy with the RFC6087bis AD review and it will be part of the feedback. 
> > >> 
> > >> Regards, Benoit 
> > >>> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote: 
> > >>>> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote: 
> > >>>>> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote: 
> > >>>>>> The feature-per-leaf approach should not be approved by YD. 
> > >>>> Do we want to add a sentence in 
> > >>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=uU5M6cHYuTrKiyxOMMI8MKvBIpYS_yg1VSIYI4MfxKo&e= <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=uU5M6cHYuTrKiyxOMMI8MKvBIpYS_yg1VSIYI4MfxKo&e=>, 
> > >>>> expressing that a feature-per-leaf is most likely the wrong approach? 
> > >>> This is difficult to describe. Perhaps something like this is a 
> > >>> reasonably small change to the existing text (which only talks about 
> > >>> too big features but not about too small features). 
> > >>> 
> > >>> OLD 
> > >>> 
> > >>>     The YANG "feature" statement is used to define a label for a set of 
> > >>>     optional functionality within a module.  The "if-feature" statement 
> > >>>     is used in the YANG statements associated with a feature. 
> > >>> 
> > >>>     The set of YANG features available in a module should be considered 
> > >>>     carefully.  The description-stmt within a feature-stmt MUST specify 
> > >>>     any interactions with other features. 
> > >>> 
> > >>>     If there is a large set of objects... 
> > >>> 
> > >>> NEW 
> > >>> 
> > >>>     The YANG "feature" statement is used to define a label for a set of 
> > >>>     optional functionality within a module.  The "if-feature" statement 
> > >>>     is used in the YANG statements associated with a feature.  The 
> > >>>     description-stmt within a feature-stmt MUST specify any 
> > >>>     interactions with other features. 
> > >>> 
> > >>>     The set of YANG features defined in a module should be considered 
> > >>>     carefully. Very fine granular features increase interoperability 
> > >>>     complexity and should be avoided. A likely misuse of the feature 
> > >>>     mechanism is the tagging of individual leafs (e.g., counters) with 
> > >>>     separate features. 
> > >>> 
> > >>>     If there is a large set of objects... 
> > >>> 
> > >>> /js 
> > >>> 
> > >> 
> > > 
> > > _______________________________________________
> > > yang-doctors mailing list
> > > yang-doctors@ietf.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_yang-2Ddoctors&d=DwIFaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=Uah4DbYVrvtZTrkciA0m1OfOgmwMXrRg_tjGmG0iX8I&e=
> > 
> > Mahesh Jethanandani
> > mjethanandani@gmail.com
> > 
> 
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors

-- 
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/>


From nobody Wed Jan 24 23:31:04 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A52EE12D95F for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 23:31:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 EjV40D_7JN_m for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 23:31:00 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 191321275C5 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 23:31:00 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 0F52A1AE0290; Thu, 25 Jan 2018 08:30:59 +0100 (CET)
Date: Thu, 25 Jan 2018 08:30:58 +0100 (CET)
Message-Id: <20180125.083058.1067336366755903306.mbj@tail-f.com>
To: exa@juniper.net
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180125031650.jzdswdgpspontven@smtp.juniper.net>
References: <20180125031650.jzdswdgpspontven@smtp.juniper.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/KKzucObBGRo3luthzJuAfoNpcP0>
Subject: Re: [yang-doctors] List key model definition order and results w/ pyang/yanglint
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 07:31:03 -0000

Hi,

Ebben Aries <exa@juniper.net> wrote:
> Possibly bringing up a subject that may have been discussed before but
> could not find anything on it so sending to the group.
> 
> RFC 6020 and 7950 both have the same wording on the subject around list
> keys per
> 
> https://tools.ietf.org/html/rfc6020#section-7.8.2
> https://tools.ietf.org/html/rfc7950#section-7.8.2
> 
> From a model definition standpoint, there is nothing mandatory
> surrounding that list keys be the first leaf definitions underneath.
> 
> From a content encoding standpoint, the following XML Mapping Rules in
> https://tools.ietf.org/html/rfc6020#section-7.8.5 do dictate an order
> that the keys be defined before other subelements.  JSON obviously does
> not utilize the same encoding technique.
> 
>    The list's key nodes are encoded as subelements to the list's
>    identifier element, in the same order as they are defined within the
>    "key" statement.
> 
>    The rest of the list's child nodes are encoded as subelements to the
>    list element, after the keys.  If the list defines RPC input or
>    output parameters, the subelements are encoded in the same order as
>    they are defined within the "list" statement.  Otherwise, the
>    subelements are encoded in any order.
> 
> Given the following simple example:
> 
> module test {
>     namespace "http://test";
>     prefix test;
> 
>     container foo {
>         leaf bar {
>             type string;
>         }
>         list car {
>             key "far mar";
> 
>             leaf par {
>                 type string;
>             }
>             leaf far {
>                 type string;
>             }
>             leaf mar {
>                 type string;
>             }
>             leaf nar {
>                 type string;
>             }
>         }
>     }
> }
> 
> leaf 'par' here is defined before the 'far' and 'mar' keys, however if
> we render out a sample-xml-skeleton with pyang, we do not take into
> account the XML encoding rules defined in Section 7.8.5 and merely keep
> the order as defined in the model.
> 
> $ pyang test.yang --strict -f sample-xml-skeleton
> <?xml version='1.0' encoding='UTF-8'?>
> <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
>   <foo xmlns="http://test">
>     <bar />
>     <car>
>       <par />
>       <far />
>       <mar />
>       <nar />
>     </car>
>   </foo>
> </data>
> 
> With yanglint, given the following XML document
> 
> $ cat test.xml
> <foo xmlns="http://test">
>     <bar>BAR</bar>
>     <car>
>         <par>PAR</par>
>         <far>FAR</far>
>         <mar>MAR</mar>
>         <nar>NAR</nar>
>     </car>
> </foo>
> 
> The rendered XML output will actually reorder the list keys to be first
> 
> $ yanglint -f xml test.yang test.xml
> <foo xmlns="http://test">
>   <bar>BAR</bar>
>   <car>
>     <far>FAR</far>
>     <mar>MAR</mar>
>     <par>PAR</par>
>     <nar>NAR</nar>
>   </car>
> </foo>
> 
> Personally, from a BCP standpoint, defining list keys first eases
> readability and want to solicit others thoughts on this (rather than
> nested down in the list or via a grouping reference further down).

I agree.

> Generation to yin does not rearrange in either pyang or yanglint which
> means any processing of yin would need to undergo some reordering
> possibly depending on how it is absorbed.

I don't understand what you mean.  Yin follows the same rules as basic
YANG syntax; it is the "key" statement that defines the XML element
order.

> For the JSON encoding case, there may be no strict ordering but
> following a BCP where folks *should* send list keys before other
> elements can ease implementation efforts in many cases.

I disagree.  Implementations MUST handle object members in any order
(std JSON), so they can never use a simpler implementation that is
built on the presumption that keys always are sent first.

(However, a clever implemention could check if the keys are sent
first, then it can parse more efficiently; it wouldn't have to buffer
data.  But this is the opposite of a simple implemention.)

> It is also
> likely that payloads will generally be constructed in the order in which
> they are defined in the model.

Yes.

> So either I see making the definition of such either mandatory or at a
> bare minimum pyang sample-xml-skeleton output to take into account
> ordering list key leafs prior to other subelements.

I think the bug in pyang should be fixed!


/martin


From nobody Wed Jan 24 23:33:04 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42A6912E042 for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 23:33:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 Uh2PJIcePLee for <yang-doctors@ietfa.amsl.com>; Wed, 24 Jan 2018 23:33:00 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id A7B0F1275C5 for <yang-doctors@ietf.org>; Wed, 24 Jan 2018 23:33:00 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id C7E251AE0290; Thu, 25 Jan 2018 08:32:59 +0100 (CET)
Date: Thu, 25 Jan 2018 08:32:59 +0100 (CET)
Message-Id: <20180125.083259.831686468389092592.mbj@tail-f.com>
To: exa@juniper.net
Cc: mjethanandani@gmail.com, yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180125042444.vtdozlf7mm7wpcz5@smtp.juniper.net>
References: <283f5774-5995-6ae3-16b7-385b8ea270d1@cisco.com> <E5618F14-46C8-40BB-9116-9E4A866575BC@gmail.com> <20180125042444.vtdozlf7mm7wpcz5@smtp.juniper.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/e6AYM00BFA8u_Gl0kV8aWPnpn28>
Subject: Re: [yang-doctors] Features and must-condition
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 07:33:03 -0000

Hi,

Ebben Aries <exa@juniper.net> wrote:
> I'm not sure I understand the intent of the newly proposed text
> =

> I'm reading this as now stating that if a 'feature' is optional, then=
 a
> 'feature' should be defined.  I think the old text was mostly correct=
 in
> what is trying to be conveyed.

This was also my reaction to the new text.

> How about something like:
> =

>    If a data definition is optional which depends on server support t=
hen
>    a YANG 'feature' statement SHOULD be defined and conveyed through =
a
>    NETCONF or RESTCONF protocol capability.  The defined 'feature'
>    SHOULD then be used in the conditional 'if-feature' statement
>    referencing the optional data definition.

Or keep the protocol thing out of this text; this is a guideline to
the *model writer*.

    If a data definition is optional which depends on server support th=
en
    a YANG 'feature' statement SHOULD be defined.  The defined 'feature=
'
    SHOULD then be used in the conditional 'if-feature' statement
    referencing the optional data definition.


/martin


> =

> On Jan 24 10:49 AM, Mahesh Jethanandani wrote:
> > How does one define a feature statement that indicates support for =
NETCONF or RESTCONF protocol capability? I thought feature statements w=
ere for features within the module.
> > =

> > > On Jan 24, 2018, at 5:54 AM, Benoit Claise <bclaise@cisco.com> wr=
ote:
> > > =

> > > Btw, along the same lines, in section 4.5
> > > OLD:
> > >    If a data definition is optional, depending on server support =
for a
> > >    NETCONF or RESTCONF protocol capability, then a YANG 'feature'=

> > >    statement SHOULD be defined to indicate that the NETCONF or RE=
STCONF
> > >    capability is supported within the data model.
> > > =

> > > NEW:
> > >    If a feature or a set of data definitions is optional, dependi=
ng on server support for a
> > >    NETCONF or RESTCONF protocol capability, then a YANG 'feature'=

> > >    statement SHOULD be defined to indicate that the NETCONF or RE=
STCONF
> > >    capability is supported within the data model.
> > > It will also be in my AD review email.
> > > =

> > > Regards, B.
> > >> Hi J=FCrgen, =

> > >> =

> > >> I like it. =

> > >> I'm busy with the RFC6087bis AD review and it will be part of th=
e feedback. =

> > >> =

> > >> Regards, Benoit =

> > >>> On Tue, Jan 16, 2018 at 06:03:05PM +0100, Benoit Claise wrote: =

> > >>>> On 1/11/2018 12:28 AM, Juergen Schoenwaelder wrote: =

> > >>>>> On Wed, Jan 10, 2018 at 02:49:48PM -0800, Andy Bierman wrote:=
 =

> > >>>>>> The feature-per-leaf approach should not be approved by YD. =

> > >>>> Do we want to add a sentence in =

> > >>>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.i=
etf.org_html_draft-2Dietf-2Dnetmod-2Drfc6087bis-2D15-23section-2D4.17&d=
=3DDwIFaQ&c=3DHAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=3DGIehbDpQl=
o31lSi6WbnEkA&m=3D7ZRQ7cSbMoQOwcUvfJf7Q1kdto8zoglQ4ZHXDURQl3s&s=3DuU5M6=
cHYuTrKiyxOMMI8MKvBIpYS_yg1VSIYI4MfxKo&e=3D <https://urldefense.proofpo=
int.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dietf-2Dnetmod-=
2Drfc6087bis-2D15-23section-2D4.17&d=3DDwIFaQ&c=3DHAkYuh63rsuhr6Scbfh0U=
jBXeMK-ndb3voDTXcWzoCI&r=3DGIehbDpQlo31lSi6WbnEkA&m=3D7ZRQ7cSbMoQOwcUvf=
Jf7Q1kdto8zoglQ4ZHXDURQl3s&s=3DuU5M6cHYuTrKiyxOMMI8MKvBIpYS_yg1VSIYI4Mf=
xKo&e=3D>, =

> > >>>> expressing that a feature-per-leaf is most likely the wrong ap=
proach? =

> > >>> This is difficult to describe. Perhaps something like this is a=
 =

> > >>> reasonably small change to the existing text (which only talks =
about =

> > >>> too big features but not about too small features). =

> > >>> =

> > >>> OLD =

> > >>> =

> > >>>     The YANG "feature" statement is used to define a label for =
a set of =

> > >>>     optional functionality within a module.  The "if-feature" s=
tatement =

> > >>>     is used in the YANG statements associated with a feature. =

> > >>> =

> > >>>     The set of YANG features available in a module should be co=
nsidered =

> > >>>     carefully.  The description-stmt within a feature-stmt MUST=
 specify =

> > >>>     any interactions with other features. =

> > >>> =

> > >>>     If there is a large set of objects... =

> > >>> =

> > >>> NEW =

> > >>> =

> > >>>     The YANG "feature" statement is used to define a label for =
a set of =

> > >>>     optional functionality within a module.  The "if-feature" s=
tatement =

> > >>>     is used in the YANG statements associated with a feature.  =
The =

> > >>>     description-stmt within a feature-stmt MUST specify any =

> > >>>     interactions with other features. =

> > >>> =

> > >>>     The set of YANG features defined in a module should be cons=
idered =

> > >>>     carefully. Very fine granular features increase interoperab=
ility =

> > >>>     complexity and should be avoided. A likely misuse of the fe=
ature =

> > >>>     mechanism is the tagging of individual leafs (e.g., counter=
s) with =

> > >>>     separate features. =

> > >>> =

> > >>>     If there is a large set of objects... =

> > >>> =

> > >>> /js =

> > >>> =

> > >> =

> > > =

> > > _______________________________________________
> > > yang-doctors mailing list
> > > yang-doctors@ietf.org
> > > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.o=
rg_mailman_listinfo_yang-2Ddoctors&d=3DDwIFaQ&c=3DHAkYuh63rsuhr6Scbfh0U=
jBXeMK-ndb3voDTXcWzoCI&r=3DGIehbDpQlo31lSi6WbnEkA&m=3D7ZRQ7cSbMoQOwcUvf=
Jf7Q1kdto8zoglQ4ZHXDURQl3s&s=3DUah4DbYVrvtZTrkciA0m1OfOgmwMXrRg_tjGmG0i=
X8I&e=3D
> > =

> > Mahesh Jethanandani
> > mjethanandani@gmail.com
> > =

> =

> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
> =


From nobody Thu Jan 25 00:18:50 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAC6F12D868 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 00:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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, T_RP_MATCHES_RCVD=-0.01, 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
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 Xh9-e0QKcKZN for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 00:18:48 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBA7412E877 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 00:18:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=256; q=dns/txt; s=iport; t=1516868328; x=1518077928; h=from:subject:to:message-id:date:mime-version: content-transfer-encoding; bh=oIPzOekB5Jrc5zaqyeskXtbtLsZhnd4nDqBW5tYBWJY=; b=DhmdYZhQ86JQ4zQbOI/o9BR1g9MyI70eEtdtwL05YnUKG6zf1kjCWReJ 9uhbZJvcoA0Tl+uKINDhGI3kfJwuy90DbLm4dtk8mm8b48I5s2RUj8StI vT7OtBplcgkQsFsPy205M2qbUYoDEuL5JoUhQPacFa7GHPTV/W3tsj2iJ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BwAQChkmla/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYUchASLGKdOggIKixgUAQEBAQEBAQECayiFTRV2AiYCXw0IAQG?= =?us-ascii?q?KMaUdkBmCJ4pgAQEIAiaBD4NCg2yCEYdvg0+CZQWkCZViggIBiiiHeo9FiBOBP?= =?us-ascii?q?DYigVAzGggbFYJohFdAjwIBAQE?=
X-IronPort-AV: E=Sophos;i="5.46,411,1511827200";  d="scan'208";a="1588691"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2018 08:18:28 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w0P8IRKB004499 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 08:18:28 GMT
From: Benoit Claise <bclaise@cisco.com>
To: YANG Doctors <yang-doctors@ietf.org>
Message-ID: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com>
Date: Thu, 25 Jan 2018 09:18:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/6LOEPw5co5kccAMdr0YWnEm4xJM>
Subject: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 08:18:50 -0000

Dear all,

Still busy with the RFC6087bis AD review, reviewing the enum sections now.

Do I recall correctly a guideline about not using "value" in enum?
Something to be inserted in RFC6087bis? At least a pros and cons discussion?

Regards, Benoit


From nobody Thu Jan 25 00:37:58 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323CF12D943 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 00:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 1dEqVedEX2WO for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 00:37:55 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BA0812D868 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 00:37:55 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 4DCF5EC0; Thu, 25 Jan 2018 09:37:54 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id YG9VqEu5bSZb; Thu, 25 Jan 2018 09:37:53 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 25 Jan 2018 09:37:54 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3792020149; Thu, 25 Jan 2018 09:37:54 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id kpgbs_hVL2kC; Thu, 25 Jan 2018 09:37:53 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id CCEC020147; Thu, 25 Jan 2018 09:37:53 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 9FCCC422901F; Thu, 25 Jan 2018 09:37:53 +0100 (CET)
Date: Thu, 25 Jan 2018 09:37:53 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Cc: YANG Doctors <yang-doctors@ietf.org>
Message-ID: <20180125083753.kngg2f3zysxq4qbm@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, YANG Doctors <yang-doctors@ietf.org>
References: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/X3rXCK0T4SZBOPWoJqqpuffz0BM>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 08:37:57 -0000

On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
> Dear all,
> 
> Still busy with the RFC6087bis AD review, reviewing the enum sections now.
> 
> Do I recall correctly a guideline about not using "value" in enum?
> Something to be inserted in RFC6087bis? At least a pros and cons discussion?
>

I would rather say the opposite:

  YANG automatically assigns numeric values to enums if no values are
  specified. This automatic assignment requires that (a) the order of
  enums never changes and (b) additional enums are only appended but
  never prepended or inserted. This is subtle and using explicit value
  assignments, though more verbose, tends to be more robust when
  modules are revised.

Background:

Note that NETCONF and RESTCONF do not send the numeric values due to
the way the XML and JSON encodings are defined. But this may be
different for other encodings, the proposed CBOR encoding uses the
numeric value. Some implementations do support mappings to protocols
such as SNMP where numeric values are used.

We had a longer discussion about this when we talked about how we deal
with timezones, which change regularly and have no natural numeric
value. Algorithms to produce YANG enumerations from the timezone
databases are difficult if you want to have stable numeric values.

/js

-- 
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/>


From nobody Thu Jan 25 00:59:27 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA6312E870 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 00:59:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 j5Y5K2KOHKlD for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 00:59:24 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE0812D868 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 00:59:24 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id C96461AE0442; Thu, 25 Jan 2018 09:59:22 +0100 (CET)
Date: Thu, 25 Jan 2018 09:59:21 +0100 (CET)
Message-Id: <20180125.095921.224499312159563778.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: bclaise@cisco.com, yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180125083753.kngg2f3zysxq4qbm@elstar.local>
References: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com> <20180125083753.kngg2f3zysxq4qbm@elstar.local>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/gkSiPXok7rQ5T5w7BogKBpyFqig>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 08:59:26 -0000

Hi,

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
> > Dear all,
> > 
> > Still busy with the RFC6087bis AD review, reviewing the enum sections now.
> > 
> > Do I recall correctly a guideline about not using "value" in enum?

I think this was a discussion on YANG 1.1, not 6087bis (but I might be
wrong).

> > Something to be inserted in RFC6087bis? At least a pros and cons discussion?
> >
> 
> I would rather say the opposite:
> 
>   YANG automatically assigns numeric values to enums if no values are
>   specified. This automatic assignment requires that (a) the order of
>   enums never changes and (b) additional enums are only appended but
>   never prepended or inserted. This is subtle and using explicit value
>   assignments, though more verbose, tends to be more robust when
>   modules are revised.

Is this a recommendation to always use the "value" statement?  I don't
think now is the right time to add such an recommendation, and I don't
think it should be recommended.  Maybe we could say something about
taking care when adding an enum, but RFC 7950, section 11, bullet 1
already says that value must not change, so we would essentially just
say that you must follow the rules of 7950.


/martin


> 
> Background:
> 
> Note that NETCONF and RESTCONF do not send the numeric values due to
> the way the XML and JSON encodings are defined. But this may be
> different for other encodings, the proposed CBOR encoding uses the
> numeric value. Some implementations do support mappings to protocols
> such as SNMP where numeric values are used.
> 
> We had a longer discussion about this when we talked about how we deal
> with timezones, which change regularly and have no natural numeric
> value. Algorithms to produce YANG enumerations from the timezone
> databases are difficult if you want to have stable numeric values.
> 
> /js
> 
> -- 
> 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/>
> 
> _______________________________________________
> yang-doctors mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors
> 


From nobody Thu Jan 25 01:11:33 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4584112DA01 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 01:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 KaLURX9zcruF for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 01:11:20 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 959C112D868 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 01:11:20 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 5EC356BA; Thu, 25 Jan 2018 10:11:19 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id vfb9t6O0s7Ca; Thu, 25 Jan 2018 10:11:18 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 25 Jan 2018 10:11:19 +0100 (CET)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3C50720147; Thu, 25 Jan 2018 10:11:19 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id S5-XKIATe10Q; Thu, 25 Jan 2018 10:11:18 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id BECFE2014D; Thu, 25 Jan 2018 10:11:18 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 80A9F4229138; Thu, 25 Jan 2018 10:11:18 +0100 (CET)
Date: Thu, 25 Jan 2018 10:11:18 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: bclaise@cisco.com, yang-doctors@ietf.org
Message-ID: <20180125091118.tjn5eiv2hzmc7k23@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Martin Bjorklund <mbj@tail-f.com>, bclaise@cisco.com, yang-doctors@ietf.org
References: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com> <20180125083753.kngg2f3zysxq4qbm@elstar.local> <20180125.095921.224499312159563778.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180125.095921.224499312159563778.mbj@tail-f.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/t-81hS4BhsRZXU8uDtRmRCQfVag>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 09:11:27 -0000

On Thu, Jan 25, 2018 at 09:59:21AM +0100, Martin Bjorklund wrote:
> Hi,
> 
> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
> > > Dear all,
> > > 
> > > Still busy with the RFC6087bis AD review, reviewing the enum sections now.
> > > 
> > > Do I recall correctly a guideline about not using "value" in enum?
> 
> I think this was a discussion on YANG 1.1, not 6087bis (but I might be
> wrong).
> 
> > > Something to be inserted in RFC6087bis? At least a pros and cons discussion?
> > >
> > 
> > I would rather say the opposite:
> > 
> >   YANG automatically assigns numeric values to enums if no values are
> >   specified. This automatic assignment requires that (a) the order of
> >   enums never changes and (b) additional enums are only appended but
> >   never prepended or inserted. This is subtle and using explicit value
> >   assignments, though more verbose, tends to be more robust when
> >   modules are revised.
> 
> Is this a recommendation to always use the "value" statement?  I don't
> think now is the right time to add such an recommendation, and I don't
> think it should be recommended.  Maybe we could say something about
> taking care when adding an enum, but RFC 7950, section 11, bullet 1
> already says that value must not change, so we would essentially just
> say that you must follow the rules of 7950.
>

The text I wrote explains the issue. It does not say you have to use
explicit value assignments (but if you want to be robust, then its
probably a good idea to use explicit assignments).

The fact that Benoit did not recall this correctly is likely an
indication that people not deeply involved in YANG do not necessarily
memorize this subtlety. Not everybody knows RFC 7950 by heart. (But
yes, not everybody will read RFC6087bis either and there are likely
quite a few things in RFC6087bis that are not strictly needed.)
Anyway, I do not plan to spend more time on guessing whether this is
helpful or not.

/js

-- 
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/>


From nobody Thu Jan 25 02:26:12 2018
Return-Path: <bclaise@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12036126CBF for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 02:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level: 
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 6C8CmU7TZbFa for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 02:26:07 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5550B12D84A for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 02:26:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9137; q=dns/txt; s=iport; t=1516875967; x=1518085567; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=r6RJ77s/YlEQ9pBqpkH8QF/nMrvoFDb6vO6krhOPOQw=; b=DORnJTCU0vyYNm9WLUeeGFV3Huv3G1R969S0nscvC7V1D6ZoqMQ6Hdva CBIMJbWSPBxC06Mge6kwWw2bclRzOXs3Oz9HMA8v/ZdbOriNd+4JuSIGR JRynFvq0QSI48dkCo/gQfbwQJTxOcb4V2Mn4p0OgFQar29RD7Nwe5t1p4 Q=;
X-IronPort-AV: E=Sophos;i="5.46,411,1511827200"; d="scan'208,217";a="1597092"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2018 10:26:05 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id w0PAQ5wF010870; Thu, 25 Jan 2018 10:26:05 GMT
To: Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org, "Einar Nilsen-Nygaard (einarnn)" <einarnn@cisco.com>
References: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com> <20180125083753.kngg2f3zysxq4qbm@elstar.local> <20180125.095921.224499312159563778.mbj@tail-f.com> <20180125091118.tjn5eiv2hzmc7k23@elstar.local>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <dfb94426-c408-e215-e23b-539e127050a2@cisco.com>
Date: Thu, 25 Jan 2018 11:26:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <20180125091118.tjn5eiv2hzmc7k23@elstar.local>
Content-Type: multipart/alternative; boundary="------------8819E126663DD7BF581332FE"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/Y3Xr4X82Z89YY8e4F-5fAdASgx0>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 10:26:10 -0000

This is a multi-part message in MIME format.
--------------8819E126663DD7BF581332FE
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit


> On Thu, Jan 25, 2018 at 09:59:21AM +0100, Martin Bjorklund wrote:
>> Hi,
>>
>> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>>> On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
>>>> Dear all,
>>>>
>>>> Still busy with the RFC6087bis AD review, reviewing the enum sections now.
>>>>
>>>> Do I recall correctly a guideline about not using "value" in enum?
>> I think this was a discussion on YANG 1.1, not 6087bis (but I might be
>> wrong).
>>
>>>> Something to be inserted in RFC6087bis? At least a pros and cons discussion?
>>>>
>>> I would rather say the opposite:
>>>
>>>    YANG automatically assigns numeric values to enums if no values are
>>>    specified. This automatic assignment requires that (a) the order of
>>>    enums never changes and (b) additional enums are only appended but
>>>    never prepended or inserted. This is subtle and using explicit value
>>>    assignments, though more verbose, tends to be more robust when
>>>    modules are revised.
>> Is this a recommendation to always use the "value" statement?  I don't
>> think now is the right time to add such an recommendation, and I don't
>> think it should be recommended.  Maybe we could say something about
>> taking care when adding an enum, but RFC 7950, section 11, bullet 1
>> already says that value must not change, so we would essentially just
>> say that you must follow the rules of 7950.
>>
> The text I wrote explains the issue. It does not say you have to use
> explicit value assignments (but if you want to be robust, then its
> probably a good idea to use explicit assignments).
>
> The fact that Benoit did not recall this correctly is likely an
> indication that people not deeply involved in YANG do not necessarily
> memorize this subtlety. Not everybody knows RFC 7950 by heart. (But
> yes, not everybody will read RFC6087bis either and there are likely
> quite a few things in RFC6087bis that are not strictly needed.)
Investigating further, Einar mentioned:

    I don't advice "value" because the value doesn't appear on the wire
    & is primarily something for the backend implementation. Thus it may
    change, and having it in the model gives an opportunity for a change
    that breaks RFC 7950 backwards compatibility rules. For something
    that is irrelevant to the model consumer.

Granted, I read RFC 7950, section 11, bullet 1 multiple times by now, 
but I forgot. And finding that paragraph back is ... well challenging
The point is to provide guidelines to YANG module designers. Yes, we 
wish everybody would read (and remember) all the RFCs beforehand. I 
believe we can help those YANG module designers reading RFC6087bis, 
looking up "enum" in the TOC, found "Enumeration and Bits" and boom, 
they would find a text expressing something such as:

   YANG automatically assigns numeric values to enums if no values are
   specified. This automatic assignment requires that (a) the order of
   enums never changes and (b) additional enums are only appended but
   never prepended or inserted. Therefore, think carefully whether you
   want to assign values to enumerations in YANG modules. On one side, though
   more verbose, assigning values might be considered more robust when modules
   are revised. On the other side, NETCONF and RESTCONF do not send the numeric
   values on the wire due to the way the XML and JSON encodings are defined
   (other protocols might), so assigning values is irrelevant to the model
   consumer.

Do you believe it's useful guidance? I believe it is.
Btw, I trust the YANG doctor on the right text.

Regards, Benoit
> Anyway, I do not plan to spend more time on guessing whether this is
> helpful or not.
>
> /js
>


--------------8819E126663DD7BF581332FE
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix"><br>
    </div>
    <blockquote type="cite"
      cite="mid:20180125091118.tjn5eiv2hzmc7k23@elstar.local">
      <pre wrap="">On Thu, Jan 25, 2018 at 09:59:21AM +0100, Martin Bjorklund wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">Hi,

Juergen Schoenwaelder <a class="moz-txt-link-rfc2396E" href="mailto:j.schoenwaelder@jacobs-university.de">&lt;j.schoenwaelder@jacobs-university.de&gt;</a> wrote:
</pre>
        <blockquote type="cite">
          <pre wrap="">On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">Dear all,

Still busy with the RFC6087bis AD review, reviewing the enum sections now.

Do I recall correctly a guideline about not using "value" in enum?
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">
I think this was a discussion on YANG 1.1, not 6087bis (but I might be
wrong).

</pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <pre wrap="">Something to be inserted in RFC6087bis? At least a pros and cons discussion?

</pre>
          </blockquote>
          <pre wrap="">
I would rather say the opposite:

  YANG automatically assigns numeric values to enums if no values are
  specified. This automatic assignment requires that (a) the order of
  enums never changes and (b) additional enums are only appended but
  never prepended or inserted. This is subtle and using explicit value
  assignments, though more verbose, tends to be more robust when
  modules are revised.
</pre>
        </blockquote>
        <pre wrap="">
Is this a recommendation to always use the "value" statement?  I don't
think now is the right time to add such an recommendation, and I don't
think it should be recommended.  Maybe we could say something about
taking care when adding an enum, but RFC 7950, section 11, bullet 1
already says that value must not change, so we would essentially just
say that you must follow the rules of 7950.

</pre>
      </blockquote>
      <pre wrap="">
The text I wrote explains the issue. It does not say you have to use
explicit value assignments (but if you want to be robust, then its
probably a good idea to use explicit assignments).

The fact that Benoit did not recall this correctly is likely an
indication that people not deeply involved in YANG do not necessarily
memorize this subtlety. Not everybody knows RFC 7950 by heart. (But
yes, not everybody will read RFC6087bis either and there are likely
quite a few things in RFC6087bis that are not strictly needed.)</pre>
    </blockquote>
    Investigating further, Einar mentioned:<br>
    <blockquote>I don't advice "value" because the value doesn't appear
      on the wire &amp; is primarily something for the backend
      implementation. Thus it may change, and having it in the model
      gives an opportunity for a change that breaks RFC <span
        style="color: blue; text-decoration: underline; cursor:
        pointer;">7950</span> backwards compatibility rules. For
      something that is irrelevant to the model consumer.</blockquote>
    Granted, I read RFC 7950, section 11, bullet 1 multiple times by
    now, but I forgot. And finding that paragraph back is ... well
    challenging<br>
    The point is to provide guidelines to YANG module designers. Yes, we
    wish everybody would read (and remember) all the RFCs beforehand. I
    believe we can help those YANG module designers reading RFC6087bis,
    looking up "enum" in the TOC, found "Enumeration and Bits" and boom,
    they would find a text expressing something such as:<br>
    <pre wrap="">  YANG automatically assigns numeric values to enums if no values are
  specified. This automatic assignment requires that (a) the order of
  enums never changes and (b) additional enums are only appended but
  never prepended or inserted. Therefore, think carefully whether you 
  want to assign values to enumerations in YANG modules. On one side, though 
  more verbose, assigning values might be considered more robust when modules 
  are revised. On the other side, NETCONF and RESTCONF do not send the numeric 
  values on the wire due to the way the XML and JSON encodings are defined 
  (other protocols might), so assigning values is irrelevant to the model
  consumer.
</pre>
    Do you believe it's useful guidance? I believe it is.<br>
    Btw, I trust the YANG doctor on the right text.<br>
    <br>
    Regards, Benoit<br>
    <blockquote type="cite"
      cite="mid:20180125091118.tjn5eiv2hzmc7k23@elstar.local">
      <pre wrap="">
Anyway, I do not plan to spend more time on guessing whether this is
helpful or not.

/js

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------8819E126663DD7BF581332FE--


From nobody Thu Jan 25 02:51:31 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E01A12DA05 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 02:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 ZQ_qM0PzYSDa for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 02:51:27 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B49F5126CBF for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 02:51:26 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 82B156BA; Thu, 25 Jan 2018 11:51:25 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id wwWED-RZRk_p; Thu, 25 Jan 2018 11:51:24 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 25 Jan 2018 11:51:25 +0100 (CET)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id 689202014B; Thu, 25 Jan 2018 11:51:25 +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 Lr7U_tvPR_yE; Thu, 25 Jan 2018 11:51:24 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 6DF9920149; Thu, 25 Jan 2018 11:51:24 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 5A33F422941C; Thu, 25 Jan 2018 11:51:24 +0100 (CET)
Date: Thu, 25 Jan 2018 11:51:24 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org, "Einar Nilsen-Nygaard (einarnn)" <einarnn@cisco.com>
Message-ID: <20180125105124.a3c7qupkheejjf55@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, Martin Bjorklund <mbj@tail-f.com>, yang-doctors@ietf.org, "Einar Nilsen-Nygaard (einarnn)" <einarnn@cisco.com>
References: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com> <20180125083753.kngg2f3zysxq4qbm@elstar.local> <20180125.095921.224499312159563778.mbj@tail-f.com> <20180125091118.tjn5eiv2hzmc7k23@elstar.local> <dfb94426-c408-e215-e23b-539e127050a2@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <dfb94426-c408-e215-e23b-539e127050a2@cisco.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/N6uWBnMEJWDBa43s2jNo8WNS--I>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 10:51:30 -0000

On Thu, Jan 25, 2018 at 11:26:05AM +0100, Benoit Claise wrote:
> 
> > On Thu, Jan 25, 2018 at 09:59:21AM +0100, Martin Bjorklund wrote:
> > > Hi,
> > > 
> > > Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > > > On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
> > > > > Dear all,
> > > > > 
> > > > > Still busy with the RFC6087bis AD review, reviewing the enum sections now.
> > > > > 
> > > > > Do I recall correctly a guideline about not using "value" in enum?
> > > I think this was a discussion on YANG 1.1, not 6087bis (but I might be
> > > wrong).
> > > 
> > > > > Something to be inserted in RFC6087bis? At least a pros and cons discussion?
> > > > > 
> > > > I would rather say the opposite:
> > > > 
> > > >    YANG automatically assigns numeric values to enums if no values are
> > > >    specified. This automatic assignment requires that (a) the order of
> > > >    enums never changes and (b) additional enums are only appended but
> > > >    never prepended or inserted. This is subtle and using explicit value
> > > >    assignments, though more verbose, tends to be more robust when
> > > >    modules are revised.
> > > Is this a recommendation to always use the "value" statement?  I don't
> > > think now is the right time to add such an recommendation, and I don't
> > > think it should be recommended.  Maybe we could say something about
> > > taking care when adding an enum, but RFC 7950, section 11, bullet 1
> > > already says that value must not change, so we would essentially just
> > > say that you must follow the rules of 7950.
> > > 
> > The text I wrote explains the issue. It does not say you have to use
> > explicit value assignments (but if you want to be robust, then its
> > probably a good idea to use explicit assignments).
> > 
> > The fact that Benoit did not recall this correctly is likely an
> > indication that people not deeply involved in YANG do not necessarily
> > memorize this subtlety. Not everybody knows RFC 7950 by heart. (But
> > yes, not everybody will read RFC6087bis either and there are likely
> > quite a few things in RFC6087bis that are not strictly needed.)
> Investigating further, Einar mentioned:
> 
>    I don't advice "value" because the value doesn't appear on the wire
>    & is primarily something for the backend implementation. Thus it may
>    change, and having it in the model gives an opportunity for a change
>    that breaks RFC 7950 backwards compatibility rules. For something
>    that is irrelevant to the model consumer.

Yes, the XML and JSON encodings do not use the value. However, the
CBOR encoding does use the value [draft-ietf-core-yang-cbor-05]. So we
either make sure the values are stable or we tell the CBOR people that
they can't use the value for their encoding. [There may also be bad
side effects on backend implementations if values change but the IETF
could declare that this is not the module writer's problem but the
backend writers problem.]

> Granted, I read RFC 7950, section 11, bullet 1 multiple times by now, but I
> forgot. And finding that paragraph back is ... well challenging
> The point is to provide guidelines to YANG module designers. Yes, we wish
> everybody would read (and remember) all the RFCs beforehand. I believe we
> can help those YANG module designers reading RFC6087bis, looking up "enum"
> in the TOC, found "Enumeration and Bits" and boom, they would find a text
> expressing something such as:
> 
>   YANG automatically assigns numeric values to enums if no values are
>   specified. This automatic assignment requires that (a) the order of
>   enums never changes and (b) additional enums are only appended but
>   never prepended or inserted. Therefore, think carefully whether you
>   want to assign values to enumerations in YANG modules. On one side, though
>   more verbose, assigning values might be considered more robust when modules
>   are revised. On the other side, NETCONF and RESTCONF do not send the numeric
>   values on the wire due to the way the XML and JSON encodings are defined
>   (other protocols might), so assigning values is irrelevant to the model
>   consumer.

If the CBOR encoding goes forward as it is designed today, then there
is nothing that prevents to use CBOR with RESTCONF (this combination
actually makes sense in situations where you care about payload size
and encoding/decoding efficiency). What I am trying to say is that if
we allow the enum value to be used by encodings, then any protocol is
affected that can use that encoding. So listing specific protocols is
likely misleading since RESTCONF for sure can be affected (as it
supports multiple encodings).

Note, this is what RFC 7950 says on page 177:

   o  An "enumeration" type may have new enums added, provided the old
      enums's values do not change.  Note that inserting a new enum
      before an existing enum or reordering existing enums will result
      in new values for the existing enums, unless they have explicit
      values assigned to them.

My reading of the first sentence is that RFC 7950 does _not_ allow
enum value changes.

/js

-- 
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/>


From nobody Thu Jan 25 02:57:21 2018
Return-Path: <acee@cisco.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67FD612DA05 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 02:57:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.53
X-Spam-Level: 
X-Spam-Status: No, score=-14.53 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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
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 YdHm-DD3rC91 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 02:57:17 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16DCD126CBF for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 02:57:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3100; q=dns/txt; s=iport; t=1516877837; x=1518087437; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=U043Tjmy3zHrpVBYwwKlxGuBWplBMLFmHskNlfKP8DA=; b=Lk+8w+IhGc85jInYNil7YZtwwhZWKLjXrGvJYXRMsoDPpfAIDMUjmGjI 1okUCC/8PBDZK38DSdPYzexv1ejdw0vw7Q8q11LJcPRt9VTGxG8am/pSs FncaYN8qIX89FlTwlFXNUz5SzE0vGWFeCLjjH0V7Zkzq0Dt5xrIukNmNJ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AsAQAst2la/5tdJa1aAxkBAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDQmZ0JweDVookjmiBWyeXQxWCAgoYC4UYAhqEIlQYAQEBAQE?= =?us-ascii?q?BAQECayiFJAEBBAEBIRE6Cw4CAgEIDgIIAgImAgICGQwLFRACBAENBYo1ELR9g?= =?us-ascii?q?ieKXgEBAQEBAQEBAQEBAQEBAQEBAQEBARgFBYEKg0KCFYM/KQyCeYMvAQECgTc?= =?us-ascii?q?4FwomglAxghQgBaQKAowPiVGUJZctAhEZAYE7AR85gVBwFT0qAYF/hFd4jTuBF?= =?us-ascii?q?wEBAQ?=
X-IronPort-AV: E=Sophos;i="5.46,411,1511827200"; d="scan'208";a="60895498"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jan 2018 10:57:16 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id w0PAvGAQ013938 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 25 Jan 2018 10:57:16 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 25 Jan 2018 05:57:15 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Thu, 25 Jan 2018 05:57:15 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
CC: YANG Doctors <yang-doctors@ietf.org>
Thread-Topic: [yang-doctors] guideline for enum and value?
Thread-Index: AQHTlbUkzfVXBtKozU2IeKLGGrnAZ6OEl/yA///THIA=
Date: Thu, 25 Jan 2018 10:57:15 +0000
Message-ID: <03309732-5A6C-4527-A442-99F4DB9AD423@cisco.com>
References: <c3d21c6e-8cc0-e109-4b81-278242d70071@cisco.com> <20180125083753.kngg2f3zysxq4qbm@elstar.local>
In-Reply-To: <20180125083753.kngg2f3zysxq4qbm@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: text/plain; charset="utf-8"
Content-ID: <EDFD0F7CB451234C954545B5152D8EAE@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/m5Rlz-Zu3zLMJJ_17uWGZdcLAyY>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 10:57:19 -0000

SSBhZ3JlZSB3aXRoIEp1ZXJnZW4uIEkgYWxzbyBiZWxpZXZlIHdoZW4gdGhlIGVudW0gY29ycmVz
cG9uZHMgdG8gc29tZSBzdGFuZGFyZCB2YWx1ZSAoZS5nLiwgSUVURiBhZGRyZXNzIGZhbWlsaWVz
KSwgdGhlcmUgaXMgc2lnbmlmaWNhbnQgYWR2YW50YWdlIGluIHByZXNlcnZpbmcgdGhhdCB2YWx1
ZSBpbiB0aGUgWUFORyBlbnVtLiANClRoYW5rcywNCkFjZWUgDQoNCu+7v09uIDEvMjUvMTgsIDM6
MzggQU0sICJ5YW5nLWRvY3RvcnMgb24gYmVoYWxmIG9mIEp1ZXJnZW4gU2Nob2Vud2FlbGRlciIg
PHlhbmctZG9jdG9ycy1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiBqLnNjaG9lbndhZWxk
ZXJAamFjb2JzLXVuaXZlcnNpdHkuZGU+IHdyb3RlOg0KDQogICAgT24gVGh1LCBKYW4gMjUsIDIw
MTggYXQgMDk6MTg6MjdBTSArMDEwMCwgQmVub2l0IENsYWlzZSB3cm90ZToNCiAgICA+IERlYXIg
YWxsLA0KICAgID4gDQogICAgPiBTdGlsbCBidXN5IHdpdGggdGhlIFJGQzYwODdiaXMgQUQgcmV2
aWV3LCByZXZpZXdpbmcgdGhlIGVudW0gc2VjdGlvbnMgbm93Lg0KICAgID4gDQogICAgPiBEbyBJ
IHJlY2FsbCBjb3JyZWN0bHkgYSBndWlkZWxpbmUgYWJvdXQgbm90IHVzaW5nICJ2YWx1ZSIgaW4g
ZW51bT8NCiAgICA+IFNvbWV0aGluZyB0byBiZSBpbnNlcnRlZCBpbiBSRkM2MDg3YmlzPyBBdCBs
ZWFzdCBhIHByb3MgYW5kIGNvbnMgZGlzY3Vzc2lvbj8NCiAgICA+DQogICAgDQogICAgSSB3b3Vs
ZCByYXRoZXIgc2F5IHRoZSBvcHBvc2l0ZToNCiAgICANCiAgICAgIFlBTkcgYXV0b21hdGljYWxs
eSBhc3NpZ25zIG51bWVyaWMgdmFsdWVzIHRvIGVudW1zIGlmIG5vIHZhbHVlcyBhcmUNCiAgICAg
IHNwZWNpZmllZC4gVGhpcyBhdXRvbWF0aWMgYXNzaWdubWVudCByZXF1aXJlcyB0aGF0IChhKSB0
aGUgb3JkZXIgb2YNCiAgICAgIGVudW1zIG5ldmVyIGNoYW5nZXMgYW5kIChiKSBhZGRpdGlvbmFs
IGVudW1zIGFyZSBvbmx5IGFwcGVuZGVkIGJ1dA0KICAgICAgbmV2ZXIgcHJlcGVuZGVkIG9yIGlu
c2VydGVkLiBUaGlzIGlzIHN1YnRsZSBhbmQgdXNpbmcgZXhwbGljaXQgdmFsdWUNCiAgICAgIGFz
c2lnbm1lbnRzLCB0aG91Z2ggbW9yZSB2ZXJib3NlLCB0ZW5kcyB0byBiZSBtb3JlIHJvYnVzdCB3
aGVuDQogICAgICBtb2R1bGVzIGFyZSByZXZpc2VkLg0KICAgIA0KICAgIEJhY2tncm91bmQ6DQog
ICAgDQogICAgTm90ZSB0aGF0IE5FVENPTkYgYW5kIFJFU1RDT05GIGRvIG5vdCBzZW5kIHRoZSBu
dW1lcmljIHZhbHVlcyBkdWUgdG8NCiAgICB0aGUgd2F5IHRoZSBYTUwgYW5kIEpTT04gZW5jb2Rp
bmdzIGFyZSBkZWZpbmVkLiBCdXQgdGhpcyBtYXkgYmUNCiAgICBkaWZmZXJlbnQgZm9yIG90aGVy
IGVuY29kaW5ncywgdGhlIHByb3Bvc2VkIENCT1IgZW5jb2RpbmcgdXNlcyB0aGUNCiAgICBudW1l
cmljIHZhbHVlLiBTb21lIGltcGxlbWVudGF0aW9ucyBkbyBzdXBwb3J0IG1hcHBpbmdzIHRvIHBy
b3RvY29scw0KICAgIHN1Y2ggYXMgU05NUCB3aGVyZSBudW1lcmljIHZhbHVlcyBhcmUgdXNlZC4N
CiAgICANCiAgICBXZSBoYWQgYSBsb25nZXIgZGlzY3Vzc2lvbiBhYm91dCB0aGlzIHdoZW4gd2Ug
dGFsa2VkIGFib3V0IGhvdyB3ZSBkZWFsDQogICAgd2l0aCB0aW1lem9uZXMsIHdoaWNoIGNoYW5n
ZSByZWd1bGFybHkgYW5kIGhhdmUgbm8gbmF0dXJhbCBudW1lcmljDQogICAgdmFsdWUuIEFsZ29y
aXRobXMgdG8gcHJvZHVjZSBZQU5HIGVudW1lcmF0aW9ucyBmcm9tIHRoZSB0aW1lem9uZQ0KICAg
IGRhdGFiYXNlcyBhcmUgZGlmZmljdWx0IGlmIHlvdSB3YW50IHRvIGhhdmUgc3RhYmxlIG51bWVy
aWMgdmFsdWVzLg0KICAgIA0KICAgIC9qcw0KICAgIA0KICAgIC0tIA0KICAgIEp1ZXJnZW4gU2No
b2Vud2FlbGRlciAgICAgICAgICAgSmFjb2JzIFVuaXZlcnNpdHkgQnJlbWVuIGdHbWJIDQogICAg
UGhvbmU6ICs0OSA0MjEgMjAwIDM1ODcgICAgICAgICBDYW1wdXMgUmluZyAxIHwgMjg3NTkgQnJl
bWVuIHwgR2VybWFueQ0KICAgIEZheDogICArNDkgNDIxIDIwMCAzMTAzICAgICAgICAgPGh0dHBz
Oi8vd3d3LmphY29icy11bml2ZXJzaXR5LmRlLz4NCiAgICANCiAgICBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgIHlhbmctZG9jdG9ycyBtYWlsaW5n
IGxpc3QNCiAgICB5YW5nLWRvY3RvcnNAaWV0Zi5vcmcNCiAgICBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3lhbmctZG9jdG9ycw0KICAgIA0KDQo=


From nobody Thu Jan 25 03:08:10 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB8FB12E894 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 03:08:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 WKv9GwIHqyS1 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 03:08:06 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 873C812E890 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 03:08:06 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 34A781AE0442; Thu, 25 Jan 2018 12:08:05 +0100 (CET)
Date: Thu, 25 Jan 2018 12:08:04 +0100 (CET)
Message-Id: <20180125.120804.68412726225731762.mbj@tail-f.com>
To: bclaise@cisco.com
Cc: yang-doctors@ietf.org, einarnn@cisco.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <dfb94426-c408-e215-e23b-539e127050a2@cisco.com>
References: <20180125.095921.224499312159563778.mbj@tail-f.com> <20180125091118.tjn5eiv2hzmc7k23@elstar.local> <dfb94426-c408-e215-e23b-539e127050a2@cisco.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/dDTHGwVpmGvHh5CIKT4kQ2ApAz8>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 11:08:09 -0000

Benoit Claise <bclaise@cisco.com> wrote:
> 
> > On Thu, Jan 25, 2018 at 09:59:21AM +0100, Martin Bjorklund wrote:
> >> Hi,
> >>
> >> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> >>> On Thu, Jan 25, 2018 at 09:18:27AM +0100, Benoit Claise wrote:
> >>>> Dear all,
> >>>>
> >>>> Still busy with the RFC6087bis AD review, reviewing the enum sections
> >>>> now.
> >>>>
> >>>> Do I recall correctly a guideline about not using "value" in enum?
> >> I think this was a discussion on YANG 1.1, not 6087bis (but I might be
> >> wrong).
> >>
> >>>> Something to be inserted in RFC6087bis? At least a pros and cons
> >>>> discussion?
> >>>>
> >>> I would rather say the opposite:
> >>>
> >>>    YANG automatically assigns numeric values to enums if no values are
> >>>    specified. This automatic assignment requires that (a) the order of
> >>>    enums never changes and (b) additional enums are only appended but
> >>>    never prepended or inserted. This is subtle and using explicit value
> >>>    assignments, though more verbose, tends to be more robust when
> >>>    modules are revised.
> >> Is this a recommendation to always use the "value" statement?  I don't
> >> think now is the right time to add such an recommendation, and I don't
> >> think it should be recommended.  Maybe we could say something about
> >> taking care when adding an enum, but RFC 7950, section 11, bullet 1
> >> already says that value must not change, so we would essentially just
> >> say that you must follow the rules of 7950.
> >>
> > The text I wrote explains the issue. It does not say you have to use
> > explicit value assignments (but if you want to be robust, then its
> > probably a good idea to use explicit assignments).
> >
> > The fact that Benoit did not recall this correctly is likely an
> > indication that people not deeply involved in YANG do not necessarily
> > memorize this subtlety. Not everybody knows RFC 7950 by heart. (But
> > yes, not everybody will read RFC6087bis either and there are likely
> > quite a few things in RFC6087bis that are not strictly needed.)
> Investigating further, Einar mentioned:
> 
>    I don't advice "value" because the value doesn't appear on the wire
>    & is primarily something for the backend implementation. Thus it may
>    change, and having it in the model gives an opportunity for a change
>    that breaks RFC 7950 backwards compatibility rules. For something
>    that is irrelevant to the model consumer.
> 
> Granted, I read RFC 7950, section 11, bullet 1 multiple times by now,
> but I forgot. And finding that paragraph back is ... well
> challenging

Note that when the initial module is designed, this doesn't matter.

When you upgrade a module, I think we can assume that people read
section 11 of RFC 7950.

> The point is to provide guidelines to YANG module designers.

Right.  And I don't think we should have a guideline that encourage
people to use explicit value statements in most cases.  I would be ok
with a recommendation along the lines:

  Do not use explicit 'value' statements, except if:

    o  the enum corresponds to some standard integer value, or

    o  you update the set of enums by inserting new enums in the
    middle of the list


/martin

> Yes, we
> wish everybody would read (and remember) all the RFCs beforehand. I
> believe we can help those YANG module designers reading RFC6087bis,
> looking up "enum" in the TOC, found "Enumeration and Bits" and boom,
> they would find a text expressing something such as:
> 
>   YANG automatically assigns numeric values to enums if no values are
>   specified. This automatic assignment requires that (a) the order of
>   enums never changes and (b) additional enums are only appended but
>   never prepended or inserted. Therefore, think carefully whether you
>   want to assign values to enumerations in YANG modules. On one side,
>   though
>   more verbose, assigning values might be considered more robust when
>   modules
>   are revised. On the other side, NETCONF and RESTCONF do not send the
>   numeric
>   values on the wire due to the way the XML and JSON encodings are
>   defined
>   (other protocols might), so assigning values is irrelevant to the
>   model
>   consumer.
> 
> Do you believe it's useful guidance? I believe it is.
> Btw, I trust the YANG doctor on the right text.
> 
> Regards, Benoit
> > Anyway, I do not plan to spend more time on guessing whether this is
> > helpful or not.
> >
> > /js
> >
> 


From nobody Thu Jan 25 03:53:32 2018
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A60D12DA12 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 03:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 XNUWX-tLqsha for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 03:53:29 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E925B1201F8 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 03:53:28 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id B70B2EEF; Thu, 25 Jan 2018 12:53:27 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id Rj1lQZUPWMBT; Thu, 25 Jan 2018 12:53:26 +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 atlas5.jacobs-university.de (Postfix) with ESMTPS; Thu, 25 Jan 2018 12:53:27 +0100 (CET)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9C1362014B; Thu, 25 Jan 2018 12:53:27 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id SCmoAgV0ZwOF; Thu, 25 Jan 2018 12:53:27 +0100 (CET)
Received: from elstar.local (unknown [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4026220149; Thu, 25 Jan 2018 12:53:27 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 68D3E422956B; Thu, 25 Jan 2018 12:53:26 +0100 (CET)
Date: Thu, 25 Jan 2018 12:53:26 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: bclaise@cisco.com, einarnn@cisco.com, yang-doctors@ietf.org
Message-ID: <20180125115326.okxwqlmpu3bpty6w@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Martin Bjorklund <mbj@tail-f.com>, bclaise@cisco.com, einarnn@cisco.com, yang-doctors@ietf.org
References: <20180125.095921.224499312159563778.mbj@tail-f.com> <20180125091118.tjn5eiv2hzmc7k23@elstar.local> <dfb94426-c408-e215-e23b-539e127050a2@cisco.com> <20180125.120804.68412726225731762.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180125.120804.68412726225731762.mbj@tail-f.com>
User-Agent: NeoMutt/20171215
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/jMqO_nS4fhaYKqSl3kLGxN7fthM>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 11:53:31 -0000

On Thu, Jan 25, 2018 at 12:08:04PM +0100, Martin Bjorklund wrote:
> 
> When you upgrade a module, I think we can assume that people read
> section 11 of RFC 7950.
>

Good luck with that.

/js

-- 
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/>


From nobody Thu Jan 25 04:00:12 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 767C412DA23 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 04:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 56MPqnUXw3WJ for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 04:00:06 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id E16B912DA28 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 04:00:05 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id E0EDA1AE0442; Thu, 25 Jan 2018 13:00:04 +0100 (CET)
Date: Thu, 25 Jan 2018 13:00:04 +0100 (CET)
Message-Id: <20180125.130004.259422860351840392.mbj@tail-f.com>
To: j.schoenwaelder@jacobs-university.de
Cc: bclaise@cisco.com, einarnn@cisco.com, yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180125115326.okxwqlmpu3bpty6w@elstar.local>
References: <dfb94426-c408-e215-e23b-539e127050a2@cisco.com> <20180125.120804.68412726225731762.mbj@tail-f.com> <20180125115326.okxwqlmpu3bpty6w@elstar.local>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/DwLRryEwe3cevYrEAqomuq6ix10>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 12:00:10 -0000

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> On Thu, Jan 25, 2018 at 12:08:04PM +0100, Martin Bjorklund wrote:
> > 
> > When you upgrade a module, I think we can assume that people read
> > section 11 of RFC 7950.
> >
> 
> Good luck with that.

I can rephrase:  It is as likely that people read section 11 of RFC
7950 as they read section XXX of RFC6087bis.


/martin


From nobody Thu Jan 25 04:17:02 2018
Return-Path: <chopps@chopps.org>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC0B1242F7 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 04:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.46
X-Spam-Level: 
X-Spam-Status: No, score=-0.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BRBL_LASTEXT=1.449, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no 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 6oYS2BSUCpO9 for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 04:16:59 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id D1DBC12025C for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 04:16:59 -0800 (PST)
Received: from tops.chopps.org (47-50-69-38.static.klmz.mi.charter.com [47.50.69.38]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id E63ED629FA; Thu, 25 Jan 2018 12:16:58 +0000 (UTC)
References: <20180125.095921.224499312159563778.mbj@tail-f.com> <20180125091118.tjn5eiv2hzmc7k23@elstar.local> <dfb94426-c408-e215-e23b-539e127050a2@cisco.com> <20180125.120804.68412726225731762.mbj@tail-f.com>
User-agent: mu4e 0.9.18; emacs 25.3.1
From: Christian Hopps <chopps@chopps.org>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: bclaise@cisco.com, einarnn@cisco.com, yang-doctors@ietf.org
In-reply-to: <20180125.120804.68412726225731762.mbj@tail-f.com>
Date: Thu, 25 Jan 2018 07:16:57 -0500
Message-ID: <87inbqxhdy.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/rtO0Q4I1ZKugiPqio9GjWdaaZWs>
Subject: Re: [yang-doctors] guideline for enum and value?
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 12:17:01 -0000

Martin Bjorklund <mbj@tail-f.com> writes:

> Benoit Claise <bclaise@cisco.com> wrote:
>> Granted, I read RFC 7950, section 11, bullet 1 multiple times by now,
>> but I forgot. And finding that paragraph back is ... well
>> challenging
>
> Note that when the initial module is designed, this doesn't matter.
>
> When you upgrade a module, I think we can assume that people read
> section 11 of RFC 7950.

This made me wonder, shouldn't incompatible changes be caught somewhere
in the model validation process? Do we have tooling to support that? I
realize this would only apply to our own process (and anyone who borrows
it).

Thanks,
Chris.


From nobody Thu Jan 25 14:21:25 2018
Return-Path: <andy@yumaworks.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF4FE12EACD for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 14:21:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 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, URIBL_BLOCKED=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 Yu1LoR_02eLv for <yang-doctors@ietfa.amsl.com>; Thu, 25 Jan 2018 14:21:20 -0800 (PST)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::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 4DC34129C6F for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 14:21:20 -0800 (PST)
Received: by mail-lf0-x230.google.com with SMTP id w27so10568286lfd.6 for <yang-doctors@ietf.org>; Thu, 25 Jan 2018 14:21:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=MVERVrwqiV03aHfOYI4DR9USElr3c5OmwhD6JOHklpA=; b=GqRjlohTf9QPHHXqx4NTCzPsSnTItqwxfWmeASk0+/vbgC+ACI4WNcXp3y1ftZla1L ShMTuLrscQhi/iCXinDMYRzddwCrQY1BlVwj5moMM1LrAXxBt36bPPY0NCZuGVKaH1Zv g0klqob5h7vwlhDfGq258GiEoBQDzdCFql+QwI3PSC1SdDrWJqLS6MxuJALLDO8tWDDf Z7myx6cYeeP4x8Ce58VmZjX2Nt/aRpeIMjngddF5W2DzavefA3ot/GBVf+tLrFYzAWVP S467tQqOC8mmMdbi8CVXbQhVFCEHHlYrk7Ui9gRL5IiLegslD7nDsvEzL6fcX9miGCDy 7tUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=MVERVrwqiV03aHfOYI4DR9USElr3c5OmwhD6JOHklpA=; b=bloMzdmXBGTNxtmMorEifQl4rVdzzGb1Sa9j8m5cCekp8bM0KVc33KcZ9Xyasqg377 If8/x3LpgG0mfXFKRA0toteWAiEr2pwqaai6dTn4XP9gb0IBhukQQYXWLWZHRg+hU91H XD6jSReeE3unVxZ/7e+TVojqZVGoqt7fpWjQlWA87Rm+USXY5VjHjiSZgOCW3lK5UJ8R YdMX988n0cEtyfdm2DFU44GPLUpV5OdaCUG+BaTscOwZjC8TZ4TVI+vR2n3D61ggkXyh 75081QBEglpOZvpoI75DV0ANoriLjzKNkSXRi2I8Fd3AsSFTxcZt5NCcBmzh7nSISA+q p4kA==
X-Gm-Message-State: AKwxytctvl3zFaFW+yg0GODRMmcBSqVSbcML/XAP7D96tlMw6RBMr6Uu Eey8NrP1yhgJianWmaM76bf6U1N48grvff4k50cS1Ia/
X-Google-Smtp-Source: AH8x225ICx3bCczqvHM1vULqR1PZFvVop5gsIpxyq4mrCHx9ITO+kXaM3uDpAk6971UhahNnqi0XLQ1CPkXOhzNr2OE=
X-Received: by 10.25.149.143 with SMTP id x137mr7155561lfd.119.1516918878169;  Thu, 25 Jan 2018 14:21:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.143.6 with HTTP; Thu, 25 Jan 2018 14:21:17 -0800 (PST)
From: Andy Bierman <andy@yumaworks.com>
Date: Thu, 25 Jan 2018 14:21:17 -0800
Message-ID: <CABCOCHRSrZQZBQqrRk7a4KfJT+_mp_n4reA7CEUaPfcCy6ypPQ@mail.gmail.com>
To: YANG Doctors <yang-doctors@ietf.org>
Content-Type: multipart/alternative; boundary="001a1147dcfee303760563a132c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/he1bCtBvxx7IQJTRCM2zySuRvRI>
Subject: [yang-doctors] usage of mandatory node in an optional choice
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jan 2018 22:21:23 -0000

--001a1147dcfee303760563a132c6
Content-Type: text/plain; charset="UTF-8"

Hi,

I am working on a bug in our server, and I noticed the NACM rule choice
is a bit odd -- why is leaf path within implied case "path" a mandatory
node?
Why does this node have mandatory=true and none of the other leafs have
that?

Is this 'path' leaf really mandatory, given that the choice is optional?
Perhaps this is future-proofing -- making sure if the case is augmented
that the path node is still provided?  (If so, then why not do all
short-case
definitions this way?)

IMO this usage of mandatory true should be avoided, or clarified, or both...

Andy


        choice rule-type {
            description
              "This choice matches if all leafs present in the rule
             match the request.  If no leafs are present, the
             choice matches all requests.";
            leaf rpc-name {
              type union {
                type matchall-string-type
<http://www.netconfcentral.org/modulereport/ietf-netconf-acm#matchall-string-type.109>;
                type string;
              }
              description
                "This leaf matches if it has the value '*' or if
                 its value equals the requested protocol operation
                 name.";
            }
            leaf notification-name {
              type union {
                type matchall-string-type
<http://www.netconfcentral.org/modulereport/ietf-netconf-acm#matchall-string-type.109>;
                type string;
              }
              description
                "This leaf matches if it has the value '*' or if its
                 value equals the requested notification name.";
            }
            leaf path {
              type node-instance-identifier
<http://www.netconfcentral.org/modulereport/ietf-netconf-acm#node-instance-identifier.175>;
              mandatory true;
              description
                "Data Node Instance Identifier associated with the
                 data node, action, or notification controlled by
                 this rule.

                 Configuration data or state data instance
                 identifiers start with a top-level data node.  A
                 complete instance identifier is required for this
                 type of path value.

                 The special value '/' refers to all possible
                 datastore contents.";
            }
          }  // choice rule-type

--001a1147dcfee303760563a132c6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>I am working on a bug in our server=
, and I noticed the NACM rule choice</div><div>is a bit odd -- why is leaf =
path within implied case &quot;path&quot; a mandatory node?</div><div>Why d=
oes this node have mandatory=3Dtrue and none of the other leafs have that?<=
/div><div><br></div><div>Is this &#39;path&#39; leaf really mandatory, give=
n that the choice is optional?</div><div>Perhaps this is future-proofing --=
 making sure if the case is augmented</div><div>that the path node is still=
 provided? =C2=A0(If so, then why not do all short-case</div><div>definitio=
ns this way?)</div><div><br></div><div>IMO this usage of mandatory true sho=
uld be avoided, or clarified, or both...</div><div><br></div><div>Andy</div=
><div><br></div><div><br></div><div><pre style=3D"margin-top:0px;margin-bot=
tom:0px;color:rgb(0,0,0);font-size:10.8px">        <a name=3D"rule-type.381=
"></a><span class=3D"gmail-yang_kw" style=3D"color:blue">choice</span> <spa=
n class=3D"gmail-yang_id" style=3D"color:red">rule-type</span> {
            <span class=3D"gmail-yang_kw" style=3D"color:blue">description<=
/span>
              <span class=3D"gmail-yang_str" style=3D"color:green">&quot;Th=
is choice matches if all leafs present in the rule
             match the request.  If no leafs are present, the
             choice matches all requests.&quot;</span>;
            <a name=3D"rpc-name.387"></a><span class=3D"gmail-yang_kw" styl=
e=3D"color:blue">leaf</span> <span class=3D"gmail-yang_id" style=3D"color:r=
ed">rpc-name</span> {
              <span class=3D"gmail-yang_kw" style=3D"color:blue">type</span=
> <span class=3D"gmail-yang_id" style=3D"color:red">union</span> {
                <span class=3D"gmail-yang_kw" style=3D"color:blue">type</sp=
an> <span class=3D"gmail-yang_id" style=3D"color:red"><a href=3D"http://www=
.netconfcentral.org/modulereport/ietf-netconf-acm#matchall-string-type.109"=
 style=3D"color:red">matchall-string-type</a></span>;
                <span class=3D"gmail-yang_kw" style=3D"color:blue">type</sp=
an> <span class=3D"gmail-yang_id" style=3D"color:red">string</span>;
              }
              <span class=3D"gmail-yang_kw" style=3D"color:blue">descriptio=
n</span>
                <span class=3D"gmail-yang_str" style=3D"color:green">&quot;=
This leaf matches if it has the value &#39;*&#39; or if
                 its value equals the requested protocol operation
                 name.&quot;</span>;
            }
            <a name=3D"notification-name.399"></a><span class=3D"gmail-yang=
_kw" style=3D"color:blue">leaf</span> <span class=3D"gmail-yang_id" style=
=3D"color:red">notification-name</span> {
              <span class=3D"gmail-yang_kw" style=3D"color:blue">type</span=
> <span class=3D"gmail-yang_id" style=3D"color:red">union</span> {
                <span class=3D"gmail-yang_kw" style=3D"color:blue">type</sp=
an> <span class=3D"gmail-yang_id" style=3D"color:red"><a href=3D"http://www=
.netconfcentral.org/modulereport/ietf-netconf-acm#matchall-string-type.109"=
 style=3D"color:red">matchall-string-type</a></span>;
                <span class=3D"gmail-yang_kw" style=3D"color:blue">type</sp=
an> <span class=3D"gmail-yang_id" style=3D"color:red">string</span>;
              }
              <span class=3D"gmail-yang_kw" style=3D"color:blue">descriptio=
n</span>
                <span class=3D"gmail-yang_str" style=3D"color:green">&quot;=
This leaf matches if it has the value &#39;*&#39; or if its
                 value equals the requested notification name.&quot;</span>=
;
            }
            <a name=3D"path.410"></a><span class=3D"gmail-yang_kw" style=3D=
"color:blue">leaf</span> <span class=3D"gmail-yang_id" style=3D"color:red">=
path</span> {
              <span class=3D"gmail-yang_kw" style=3D"color:blue">type</span=
> <span class=3D"gmail-yang_id" style=3D"color:red"><a href=3D"http://www.n=
etconfcentral.org/modulereport/ietf-netconf-acm#node-instance-identifier.17=
5" style=3D"color:red">node-instance-identifier</a></span>;
              <span class=3D"gmail-yang_kw" style=3D"color:blue">mandatory<=
/span> <span class=3D"gmail-yang_str" style=3D"color:green">true</span>;
              <span class=3D"gmail-yang_kw" style=3D"color:blue">descriptio=
n</span>
                <span class=3D"gmail-yang_str" style=3D"color:green">&quot;=
Data Node Instance Identifier associated with the
                 data node, action, or notification controlled by
                 this rule.

                 Configuration data or state data instance
                 identifiers start with a top-level data node.  A
                 complete instance identifier is required for this
                 type of path value.

                 The special value &#39;/&#39; refers to all possible
                 datastore contents.&quot;</span>;
            }
          }  <span class=3D"gmail-yang_cmt" style=3D"color:brown">// choice=
 rule-type</span></pre></div></div>

--001a1147dcfee303760563a132c6--


From nobody Fri Jan 26 00:22:36 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A5B12D959 for <yang-doctors@ietfa.amsl.com>; Fri, 26 Jan 2018 00:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 bA1ylq8HTE6L for <yang-doctors@ietfa.amsl.com>; Fri, 26 Jan 2018 00:22:31 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 36F4C12D80F for <yang-doctors@ietf.org>; Fri, 26 Jan 2018 00:22:31 -0800 (PST)
Received: from localhost (h-80-27.A165.priv.bahnhof.se [212.85.80.27]) by mail.tail-f.com (Postfix) with ESMTPSA id B13DB1AE0118; Fri, 26 Jan 2018 09:22:28 +0100 (CET)
Date: Fri, 26 Jan 2018 09:22:28 +0100 (CET)
Message-Id: <20180126.092228.468237320419748997.mbj@tail-f.com>
To: andy@yumaworks.com
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <CABCOCHRSrZQZBQqrRk7a4KfJT+_mp_n4reA7CEUaPfcCy6ypPQ@mail.gmail.com>
References: <CABCOCHRSrZQZBQqrRk7a4KfJT+_mp_n4reA7CEUaPfcCy6ypPQ@mail.gmail.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/X-QDKi5ii02mRSiH_HmZluLMv48>
Subject: Re: [yang-doctors] usage of mandatory node in an optional choice
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 08:22:34 -0000

Hi,

Andy Bierman <andy@yumaworks.com> wrote:
> Hi,
> 
> I am working on a bug in our server, and I noticed the NACM rule choice
> is a bit odd -- why is leaf path within implied case "path" a mandatory
> node?
> Why does this node have mandatory=true and none of the other leafs have
> that?

Browsing through the history of this module I found this design from
2010:


    list data-rule {
        key "rule-name";
        ordered-by user;

        ...

        leaf path {
          type schema-instance-identifier;
          mandatory true;
    ...

So I think this is merely a left over from this design that we forgot
to change.

> Is this 'path' leaf really mandatory, given that the choice is optional?
> Perhaps this is future-proofing -- making sure if the case is augmented
> that the path node is still provided?  (If so, then why not do all
> short-case
> definitions this way?)

Future-proofing is an interesting angle.  Maybe we should use *more*
mandatory true in cases (!) like this...?


/martin

> IMO this usage of mandatory true should be avoided, or clarified, or both...
> 
> Andy
> 
> 
>         choice rule-type {
>             description
>               "This choice matches if all leafs present in the rule
>              match the request.  If no leafs are present, the
>              choice matches all requests.";
>             leaf rpc-name {
>               type union {
>                 type matchall-string-type
> <http://www.netconfcentral.org/modulereport/ietf-netconf-acm#matchall-string-type.109>;
>                 type string;
>               }
>               description
>                 "This leaf matches if it has the value '*' or if
>                  its value equals the requested protocol operation
>                  name.";
>             }
>             leaf notification-name {
>               type union {
>                 type matchall-string-type
> <http://www.netconfcentral.org/modulereport/ietf-netconf-acm#matchall-string-type.109>;
>                 type string;
>               }
>               description
>                 "This leaf matches if it has the value '*' or if its
>                  value equals the requested notification name.";
>             }
>             leaf path {
>               type node-instance-identifier
> <http://www.netconfcentral.org/modulereport/ietf-netconf-acm#node-instance-identifier.175>;
>               mandatory true;
>               description
>                 "Data Node Instance Identifier associated with the
>                  data node, action, or notification controlled by
>                  this rule.
> 
>                  Configuration data or state data instance
>                  identifiers start with a top-level data node.  A
>                  complete instance identifier is required for this
>                  type of path value.
> 
>                  The special value '/' refers to all possible
>                  datastore contents.";
>             }
>           }  // choice rule-type


From nobody Fri Jan 26 03:36:42 2018
Return-Path: <chopps@chopps.org>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF2E12D779 for <yang-doctors@ietfa.amsl.com>; Fri, 26 Jan 2018 03:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.461
X-Spam-Level: 
X-Spam-Status: No, score=-0.461 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BRBL_LASTEXT=1.449, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 MnkEl8D2ZgM0 for <yang-doctors@ietfa.amsl.com>; Fri, 26 Jan 2018 03:36:40 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id E754D126CBF for <yang-doctors@ietf.org>; Fri, 26 Jan 2018 03:36:39 -0800 (PST)
Received: from tops.chopps.org (47-50-69-38.static.klmz.mi.charter.com [47.50.69.38]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 523F462A7A; Fri, 26 Jan 2018 11:36:39 +0000 (UTC)
References: <CABCOCHRSrZQZBQqrRk7a4KfJT+_mp_n4reA7CEUaPfcCy6ypPQ@mail.gmail.com> <20180126.092228.468237320419748997.mbj@tail-f.com>
User-agent: mu4e 0.9.18; emacs 25.3.1
From: Christian Hopps <chopps@chopps.org>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: andy@yumaworks.com, yang-doctors@ietf.org
Message-ID: <87tvv8g8hs.fsf@chopps.org>
In-reply-to: <20180126.092228.468237320419748997.mbj@tail-f.com>
Date: Fri, 26 Jan 2018 06:36:38 -0500
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/rmJRXx35morO-57a49v0Ai9FZa0>
Subject: Re: [yang-doctors] usage of mandatory node in an optional choice
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jan 2018 11:36:41 -0000

Martin Bjorklund <mbj@tail-f.com> writes:
> Andy Bierman <andy@yumaworks.com> wrote:
>> Hi,
>>
>> I am working on a bug in our server, and I noticed the NACM rule choice
>> is a bit odd -- why is leaf path within implied case "path" a mandatory
>> node?
>> Why does this node have mandatory=true and none of the other leafs have
>> that?
...
>> Is this 'path' leaf really mandatory, given that the choice is optional?
>> Perhaps this is future-proofing -- making sure if the case is augmented
>> that the path node is still provided?  (If so, then why not do all
>> short-case
>> definitions this way?)
>
> Future-proofing is an interesting angle.  Maybe we should use *more*
> mandatory true in cases (!) like this...?

So I recently used a choice, and wondered why the "case" name values were not
included explicitly in the tree and instead the case choice was simply implied
by one of it's leaf nodes being present from underneath the case. It struck me
as an overly clever optimization. This seems to bear that feeling out.

If one has a choice with case nodes that are non-mandatory, it would
seem that yang would allow augments to these cases to exclusively select those
cases and it might seem that these augments are backward compatible
when in fact they are not:

  module foo;
  choice X {
    case A {
      leaf a {
        type boolean;
      }
    }
    case B {
      leaf b {
        type boolean;
      }
    }
  }

  module bar;
  augment /foo:X/foo:B/ {
    leaf bb {
      type string;
    }
  }

Now a client that only implements module foo might receive:

    <bar:bb>extra-info</bar:bb>

and have no idea that case B of choice X had been chosen.

So for choices to allow for augmenting with backward compatibility each case must
have at least one mandatory leaf in it. To my earlier point, this wouldn't have
been required if the case name itself had been included in the returned tree.

Thanks,
Chris.


From nobody Mon Jan 29 17:12:48 2018
Return-Path: <exa@juniper.net>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97583131985 for <yang-doctors@ietfa.amsl.com>; Mon, 29 Jan 2018 17:12:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
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 XOSO5gV1bxFT for <yang-doctors@ietfa.amsl.com>; Mon, 29 Jan 2018 17:12:44 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 E012B131994 for <yang-doctors@ietf.org>; Mon, 29 Jan 2018 17:12:33 -0800 (PST)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w0U18p7n031818; Mon, 29 Jan 2018 17:12:32 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : in-reply-to; s=PPS1017; bh=jAc0iFV9GvagGCaazjXHU6erpYUwVlK0SmLECkj3/YY=; b=OnrIZbRLrwgiFgivf4Z7NcVFqynfkW38yM+yPRJFBjS7dTgBgc51emJE5wEmEDt3BkcP GEDPs/Qcl85EYkvNrXbog5K61tYypPvllVkGgzv2X5ZHOKnT253DTPyko0sFYg08gzGQ hhQ678BSoIXZyUg4wmVyZEVsbt2knid0Ovdb5T+whrKcOQ0+P0S2BmVo5HJNTlqqQrOg L02K7c2czKoa1MudzDBpY1QInWaqGhZWmAt0fKSPjPmiT+XvZAg4wLyeeds6WtbvQa1N rpvdy1fo4O4OyU979YkCIVGYxfHda7itkprUHcbCJv8d32oe1VEhBonEcStmZq9CfR5C JA== 
Received: from nam01-by2-obe.outbound.protection.outlook.com (mail-by2nam01lp0178.outbound.protection.outlook.com [216.32.181.178]) by mx0b-00273201.pphosted.com with ESMTP id 2ftdgdg5df-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 29 Jan 2018 17:12:31 -0800
Received: from CO2PR05CA0082.namprd05.prod.outlook.com (10.166.88.178) by BY2PR0501MB2069.namprd05.prod.outlook.com (10.163.197.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.464.6; Tue, 30 Jan 2018 01:12:30 +0000
Received: from DM3NAM05FT013.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::202) by CO2PR05CA0082.outlook.office365.com (2603:10b6:102:2::50) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.464.6 via Frontend Transport; Tue, 30 Jan 2018 01:12:29 +0000
Received-SPF: SoftFail (protection.outlook.com: domain of transitioning juniper.net discourages use of 66.129.239.15 as permitted sender)
Received: from P-EMFE01C-SAC.jnpr.net (66.129.239.15) by DM3NAM05FT013.mail.protection.outlook.com (10.152.98.122) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384) id 15.20.464.8 via Frontend Transport; Tue, 30 Jan 2018 01:12:28 +0000
Received: from smtp.juniper.net (10.163.2.159) by P-EMFE01C-SAC.jnpr.net (172.24.192.21) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 29 Jan 2018 17:12:08 -0800
Date: Mon, 29 Jan 2018 18:12:05 -0700
From: Ebben Aries <exa@juniper.net>
To: Martin Bjorklund <mbj@tail-f.com>
CC: <yang-doctors@ietf.org>
Message-ID: <20180130011205.rr4aacdpo4tnovx2@smtp.juniper.net>
References: <20180125031650.jzdswdgpspontven@smtp.juniper.net> <20180125.083058.1067336366755903306.mbj@tail-f.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180125.083058.1067336366755903306.mbj@tail-f.com>
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:66.129.239.15; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(396003)(346002)(39380400002)(376002)(39860400002)(2980300002)(189003)(199004)(59450400001)(8936002)(50466002)(316002)(53936002)(68736007)(53416004)(8676002)(81156014)(97756001)(104016004)(16586007)(966005)(77096007)(6306002)(105596002)(336011)(356003)(26005)(6346003)(6246003)(55016002)(81166006)(229853002)(5660300001)(478600001)(6916009)(97736004)(76176011)(106466001)(69596002)(2950100002)(6666003)(1076002)(186003)(7696005)(575784001)(86362001)(23726003)(2906002)(46406003)(47776003)(305945005)(4326008)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0501MB2069; H:P-EMFE01C-SAC.jnpr.net; FPR:; SPF:SoftFail; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; DM3NAM05FT013; 1:/25+1v7npn56MY3LU7Ex0P7QTpZyJpbELd1f5leIE9FUF5wGRLWeQC1h9Z9Uq0cNt7VGngrNj+TOFJoc/v8AE3u14P96S7dBLPtYQp9LwiAY89pB9qjCL9Jpb0cpgsP5
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: e67c6f23-d73b-4039-d756-08d5677e881f
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603307)(7153060); SRVR:BY2PR0501MB2069; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2069; 3:S2VJqABoYNH1kuGFtBsWIQyp1NQnSmkMuV5/uPTi+JvIWmqUIvBtYG3AnZFRHUla22ca1UENE6IzE9HT7Fsywi8VXBc5bWaHCX95hqTVUzbtUu/YVVCC1QJb19W5Wt7lS69OhqHxu/ZgJtatgE6kTf4NuINfnmVqlZx3agr+oRLsniOKTJUecYa7Bl0eYcnQjKQh/1vjIEkwaV9RCXXDApG4t5ngSCnaO9bfkohyBmtGeKhA1E/XtmhwnSAPGE9goFlvQO1rXnpkhqTC0riLwi4GHUYyTxT7i2LbDh9JiyyB++dtvn3zzmoLgfuYBPSa1F/ZSQlCp6xL6J6HJU5HXs3U/exbV4WwifpRv2Ajne4=; 25:WizFP7sYAqLU+kdEJxzZWO2WoOvc5wUyqxTWXKk+Yicjxx2e4oiOV6CVPmgdEtQ1hVUQpgVnzBENwEkKzitjvumlkP378sJfCN/ASU9eMroSi+PiEaBDCtxw5NijlaAery4A1CODPQThBf7tgLH8sL0pz6YdN9ONwO+6g1MMHt1Bu2ynZ71HmLdtZEONLPzHKBnoaLI899sVKOIGT5FwdvqpQ0HbSOWjRMBTlja0VoJJA91sA5WT9k8Cpwed3leoAloHpLT9oHqOuYRRMEy8F9gne3egZOzv2UdRo7dwcYkCJnLyYzY2Ab9ZU73+Hh/qQn1rr/j2DorzZUiN8o9ZZQ==
X-MS-TrafficTypeDiagnostic: BY2PR0501MB2069:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2069; 31:oxbM9lL//Wr9yVM2Ux47xKvYUbkDwiYGdis0SgHRNL61x/8+TNlAgnJ9JsSkS2nH2RT4igMSySs7AHs4Dehe0nNazKa6PflwKw7+DHSFXx5pBB8LThfRhh4U+X8jicQVJqrvSUN4j9N7MdumvvrPgvKt+9h5yb1WcMIw0YGJMCLNtbU8NsyyWFKd/OycXdAWfwStaaqvShrBNNnpbUOlUCA5nMiWTJ3abJJV9vmxXIg=; 20:vBbf7vm3dm2LTn/ohzy3/syqn9p6uMu97FvHjCk/jXc9O6OdHksbphm4JlWM9RKjMB1I4x+kGhIC22cUZA4EKYnGyueOQB3e8JJzhedoUpUN5GiGB+TjcmLD7Ti+K7TkU64rXG2SIHL8E2TBWF8vvEuTlTZfrP3XQ1ilYm2Y0f4ut+JQTvL+uTYk0JoII7o3PMpnOhV6sc3jbd9N5Q7xJsh/wszBiAdcHAdK/wwFF4Ouo1y+WE66K+gXRYUR0Yj6cZ8jBPUsS1bB30J3QimoqWMN+Y0kpyu5Fysc7PjDHEXcXDQcIonpxZPFoRp//BpEZBAKcSq6ozPytITT+JA0ZyiNWCKs1/P7EbUIEl/P5/1QtC+i2Oo92oi+kC8r1VoWt9zid2ILCrDKgp0IQYFdM0H3JQcTk6TFOZ9PAN9j60ZnaLQd/X1aIT0bbBFAZsdQdj3OFR9CCBZdK25q0v7oHjQaicA4azPsA8ug2lTQjwJMHKY54EuWY7fldP7t5gMc
X-Microsoft-Antispam-PRVS: <BY2PR0501MB2069DED84AF5D286501D5A09A8E40@BY2PR0501MB2069.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(10436049006162)(166708455590820)(131327999870524)(138986009662008); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231101)(944501161)(6055026)(6041288)(20161123558120)(20161123562045)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BY2PR0501MB2069; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0501MB2069; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2069; 4:DkQ9AKRIv2BofQ7rgZHSIf/kpFH45tqvUQnimRqAlrI0lamGWvuGM7bLBQjKbyCDlOXc6gf2mN68eyvg89r+s9eiK40JFHmzunLaRRMEXENjcJpUgQ3jFm0kKLMKUCQOdUXBrqq3HIZT0x3nTv0UP0fYmMSCPjhtBa9utfSVhFyfvcQlaNMRw2SS68/tGtl9EMyBz6qR+n1FoJ4x3wRwEpz6rJhbVdksONq0OiFyi9j7SCi8lPSIHfMJtRin1MHM/2VIU7Js7mLhL8fQIrZiFdTPYXZfB2SzLRI/A5sExAAIxZMTgr45Z6SWMdbbsZzeIkVHIEtPskDvT2Go9Ej3zrjXTqGAy5uR+9araR+NAM40VK1pndpCfcvjvi6QFQ9MGVqPki3gJN5YzCPFUagJSx3NQ57hT84fnslyHuY2KNk=
X-Forefront-PRVS: 0568F32D91
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; BY2PR0501MB2069; 23:J+TGuOr1KReDVbIVvAyI3q1oYSEm3yQynbHwvfl?= =?us-ascii?Q?jEoXogfN7eg304znB5473tUGGw44wjGqfGXGfqpb3XNJwIlCe37EeBsQ5YCu?= =?us-ascii?Q?QIP+IsQiU7tkIQXnLO79LC2cKPFwwfTQQUxUZpHrRrYp2O7Y1k/zK6QQGnuf?= =?us-ascii?Q?PtUPeqz5Wf3qff5JbdQ1E0ldSrZA/Bb3GDYmQkxvDzMpEawvJHZ6RJAxVjn1?= =?us-ascii?Q?hys3vq2rRt7va+mLPIRbwlv/CM7SugYrXHnyDZ7FcaJUVEfYARItVpBUy1DY?= =?us-ascii?Q?sbnJjeyQNheyBPYudULwTDu1okiuwmGTqkHCsdDq20iUeJ6TInhHfLrPWLgp?= =?us-ascii?Q?ky4hP5083FynSF7AUjXcRG527EgPfcf5orJ82oDJSq1tmpOskbl1QZ2RqMmz?= =?us-ascii?Q?OY6FpoT/AoTqzXnKlaPksp2H/PL5TMozooREpWyiWAhHX4ldGLfvLqcfq83n?= =?us-ascii?Q?3nYwBfOY0yh0kc8WpKYXxE6H+R+5+GNSjO6GZx/l3tIUFKiAlLq0LtMYlOkG?= =?us-ascii?Q?1O/eSbMtTNODuWLkAexAxPNgtb/Ib+SxgLwP2eDdJYawG6dBLNE0muuGJmRL?= =?us-ascii?Q?RI3Ds9kpChYCjMurW30MFTCeN+kt71CSTu2Tb6lrSUhK450Dmwe7aO6+Dus9?= =?us-ascii?Q?vRi9ez9A2HfLfbJVWS4BSPDUP74kbB9Khf2/sTZqBh3GdwBersWFzWcEduMa?= =?us-ascii?Q?3sYJ0jWGhzHHbMDw1Hp193f8zdW4JTi/qwLXSpXpFNIc9PysPTnF9cHRMAEH?= =?us-ascii?Q?JS1oIB1vmpyyp6zVA3o0bb9yHmNzhEzhTNEMLvwGMBACRtZTpXoD1+Wyrgsg?= =?us-ascii?Q?Z05IJSmG06W7R12yXP1p3He/vgpRk3jfnRu/92bw7xhxtWvjX+N2U0oeHx9w?= =?us-ascii?Q?E3qlVWtqaKtTL3fQLhnsu3MDQqM5qQn4dVoFn8GnTr6dk3hnoNWbADgcNlFY?= =?us-ascii?Q?eyF/+817BQEH9yON5W9G+agKet/+t0kas9IjcLhD57oIsn6lqpZKMupHx3uI?= =?us-ascii?Q?vr3ozTXWpmtSO7A/jiLLml2MHrIE074odUj6gtYo9Nprek1wCqPloo0jSKyf?= =?us-ascii?Q?rrnCTyq7K0caSqXvQ0E37huZtQwVGw05plEygRo5LaSBRgdUhKS9Ea3mJ/ym?= =?us-ascii?Q?q/aKqvQGPiX1heTnRl5+pJi0HL6NysalkL33LUDRSGGMHDz42ziyEOYYXuzG?= =?us-ascii?Q?Ehq4ZzzrfZqPLog5nt7UIxQqI+wHpBxrBxwBOJhYVuszkpTRiJeGWJbrufw?= =?us-ascii?Q?=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR0501MB2069; 6:23Kq+uLHGZDkeQDsYVG9NGcczAF6qs7RRZPJbQfZon4iKURTZ2XSk3WZJIDYng1fXDVRcP9rv4e3DfQCQHXhLCRmKw2UbeUDmVJiXfyUEh9//+zaAEP1oYFhRbt/KhocVL2QuSo1IBnxhq8Ry1yAwksp5BviwOW5/XLtp9KvBO7QRu4/OGFu3/qys8569J0hu8Mj6P6quteFaulpeqtDTNQQWdj8qn2CHngoe8OKbDUTmqIzrDUdMztcA4IF/7HZx2aA7t8BbI8xIREKfCB3/riVIlEAqbiA96oUpb9mbqAOuPub1HMj4htJA3iFP8f5eMpk6aAG9xBBmGKOsIq37bS75eHEiyqEugJsANXxhuk=; 5:svVjpt8sNDx8RGFdAHmz1tBVW95mflHyj7fYUaXlKO8sLjKX+rr3TLlEqiG0HdHmZbGSShR71tNAxx2meCHn0URaywd2wOPCWEA8RogkyoWfBpiSK0PsTLDQBbFpLZbfTSkzOJ/kcxUMC5LnsH8Z2PvPKEZU0jDEKMz95U3WwNo=; 24:Yd/WW3MiWY6doOF+xXZIxIEaAOwwmLZqUnVtsiB7LLlb4VacG19czofWHQQrIEtah0XwKx+kunC1bT+Exmt+zaRerJ1+HdIYPX9nGrJD7Ro=; 7:Hg5h519CCScywdgsXeuKG3/7/keG9zIzMhbwl6lAYdqv9Of9epwF2jdBl0fAKRinnSUFXY7M9EoFXh7IdHm6VnaoEHamodpaQdk95Mt+OLn97BzGBIQAqN8w0Z+KSTpFv4hqrqa8a4d5m99aqE9LtXP2I82O1CYcry2AVHadqTB5Og+C+y/gQsyfl98SCq2fbJC7r0AHDfcyx9LdWq6nBR/EDuThwQ1id44HFOEz4qiDCytLl/1+B1c29ACBRnwX
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Jan 2018 01:12:28.6527 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: e67c6f23-d73b-4039-d756-08d5677e881f
X-MS-Exchange-CrossTenant-Id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=bea78b3c-4cdb-4130-854a-1d193232e5f4; Ip=[66.129.239.15];  Helo=[P-EMFE01C-SAC.jnpr.net]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0501MB2069
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2018-01-30_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1801300012
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/xwKmiN_O6KITqYCGj9BLoKcuw98>
Subject: Re: [yang-doctors] List key model definition order and results w/ pyang/yanglint
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jan 2018 01:12:47 -0000

inline...

On Jan 25 08:30 AM, Martin Bjorklund wrote:
> Hi,
> 
> Ebben Aries <exa@juniper.net> wrote:
> > Possibly bringing up a subject that may have been discussed before but
> > could not find anything on it so sending to the group.
> > 
> > RFC 6020 and 7950 both have the same wording on the subject around list
> > keys per
> > 
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc6020-23section-2D7.8.2&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=s0ueqUyec_0t88MK81g6lUGSHXLivei_aFPMFmdUATQ&e=
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7950-23section-2D7.8.2&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=tnRmYIIjLA3KSnysiPYAaVjjLJ7GLK-No5AFu9bJ1hg&e=
> > 
> > From a model definition standpoint, there is nothing mandatory
> > surrounding that list keys be the first leaf definitions underneath.
> > 
> > From a content encoding standpoint, the following XML Mapping Rules in
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc6020-23section-2D7.8.5&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=El_GT294heczTOGSYxV-s0MdzjwhB-vEBEVCQNYEdzs&e= do dictate an order
> > that the keys be defined before other subelements.  JSON obviously does
> > not utilize the same encoding technique.
> > 
> >    The list's key nodes are encoded as subelements to the list's
> >    identifier element, in the same order as they are defined within the
> >    "key" statement.
> > 
> >    The rest of the list's child nodes are encoded as subelements to the
> >    list element, after the keys.  If the list defines RPC input or
> >    output parameters, the subelements are encoded in the same order as
> >    they are defined within the "list" statement.  Otherwise, the
> >    subelements are encoded in any order.
> > 
> > Given the following simple example:
> > 
> > module test {
> >     namespace "https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=";
> >     prefix test;
> > 
> >     container foo {
> >         leaf bar {
> >             type string;
> >         }
> >         list car {
> >             key "far mar";
> > 
> >             leaf par {
> >                 type string;
> >             }
> >             leaf far {
> >                 type string;
> >             }
> >             leaf mar {
> >                 type string;
> >             }
> >             leaf nar {
> >                 type string;
> >             }
> >         }
> >     }
> > }
> > 
> > leaf 'par' here is defined before the 'far' and 'mar' keys, however if
> > we render out a sample-xml-skeleton with pyang, we do not take into
> > account the XML encoding rules defined in Section 7.8.5 and merely keep
> > the order as defined in the model.
> > 
> > $ pyang test.yang --strict -f sample-xml-skeleton
> > <?xml version='1.0' encoding='UTF-8'?>
> > <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
> >   <foo xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=">
> >     <bar />
> >     <car>
> >       <par />
> >       <far />
> >       <mar />
> >       <nar />
> >     </car>
> >   </foo>
> > </data>
> > 
> > With yanglint, given the following XML document
> > 
> > $ cat test.xml
> > <foo xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=">
> >     <bar>BAR</bar>
> >     <car>
> >         <par>PAR</par>
> >         <far>FAR</far>
> >         <mar>MAR</mar>
> >         <nar>NAR</nar>
> >     </car>
> > </foo>
> > 
> > The rendered XML output will actually reorder the list keys to be first
> > 
> > $ yanglint -f xml test.yang test.xml
> > <foo xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=">
> >   <bar>BAR</bar>
> >   <car>
> >     <far>FAR</far>
> >     <mar>MAR</mar>
> >     <par>PAR</par>
> >     <nar>NAR</nar>
> >   </car>
> > </foo>
> > 
> > Personally, from a BCP standpoint, defining list keys first eases
> > readability and want to solicit others thoughts on this (rather than
> > nested down in the list or via a grouping reference further down).
> 
> I agree.
> 

Should we add text to rfc6087bis to suggest such?  Any reason not to?

> > Generation to yin does not rearrange in either pyang or yanglint which
> > means any processing of yin would need to undergo some reordering
> > possibly depending on how it is absorbed.
> 
> I don't understand what you mean.  Yin follows the same rules as basic
> YANG syntax; it is the "key" statement that defines the XML element
> order.
> 

Just merely pointing out that the same handling that would be done for
XML encoding rules would need to be done for potential processing of YIN
if the consumer of said data needs to process ordered elements
in whatever application.

Understood this is lossless and a direct mapping

> > For the JSON encoding case, there may be no strict ordering but
> > following a BCP where folks *should* send list keys before other
> > elements can ease implementation efforts in many cases.
> 
> I disagree.  Implementations MUST handle object members in any order
> (std JSON), so they can never use a simpler implementation that is
> built on the presumption that keys always are sent first.
> 

Agreed

> (However, a clever implemention could check if the keys are sent
> first, then it can parse more efficiently; it wouldn't have to buffer
> data.  But this is the opposite of a simple implemention.)
> 

This was precisely my point but agree, the assumption can never be made
due to this

A BCP could very well be put into code for --ietf, -f yang (and other
flags) that *could* enforce this ordering within the model itself.  If
we do add text to rfc6087bis, this should come along w/ imo.

> > It is also
> > likely that payloads will generally be constructed in the order in which
> > they are defined in the model.
> 
> Yes.
> 
> > So either I see making the definition of such either mandatory or at a
> > bare minimum pyang sample-xml-skeleton output to take into account
> > ordering list key leafs prior to other subelements.
> 
> I think the bug in pyang should be fixed!
> 

Have the fix in a local branch - pull request now at:

https://github.com/mbj4668/pyang/pull/359

/ebben


From nobody Tue Jan 30 07:09:10 2018
Return-Path: <mbj@tail-f.com>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8B4B12D96B for <yang-doctors@ietfa.amsl.com>; Tue, 30 Jan 2018 07:09:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 NoBrfPqNmd3V for <yang-doctors@ietfa.amsl.com>; Tue, 30 Jan 2018 07:09:01 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 56B5212D833 for <yang-doctors@ietf.org>; Tue, 30 Jan 2018 07:09:01 -0800 (PST)
Received: from localhost (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 8713E1AE018A; Tue, 30 Jan 2018 16:09:00 +0100 (CET)
Date: Tue, 30 Jan 2018 16:09:00 +0100 (CET)
Message-Id: <20180130.160900.1240244423754350192.mbj@tail-f.com>
To: exa@juniper.net
Cc: yang-doctors@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <20180130011205.rr4aacdpo4tnovx2@smtp.juniper.net>
References: <20180125031650.jzdswdgpspontven@smtp.juniper.net> <20180125.083058.1067336366755903306.mbj@tail-f.com> <20180130011205.rr4aacdpo4tnovx2@smtp.juniper.net>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/eIXYiPWJ_yPAOgEEKa0wp4UYlVM>
Subject: Re: [yang-doctors] List key model definition order and results w/ pyang/yanglint
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email list of the yang-doctors directorate  <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>, <mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jan 2018 15:09:09 -0000

Hi,

Thank you for contributing with a pull request, I will have a look at
it!


/martin



Ebben Aries <exa@juniper.net> wrote:
> inline...
> 
> On Jan 25 08:30 AM, Martin Bjorklund wrote:
> > Hi,
> > 
> > Ebben Aries <exa@juniper.net> wrote:
> > > Possibly bringing up a subject that may have been discussed before but
> > > could not find anything on it so sending to the group.
> > > 
> > > RFC 6020 and 7950 both have the same wording on the subject around list
> > > keys per
> > > 
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc6020-23section-2D7.8.2&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=s0ueqUyec_0t88MK81g6lUGSHXLivei_aFPMFmdUATQ&e=
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc7950-23section-2D7.8.2&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=tnRmYIIjLA3KSnysiPYAaVjjLJ7GLK-No5AFu9bJ1hg&e=
> > > 
> > > From a model definition standpoint, there is nothing mandatory
> > > surrounding that list keys be the first leaf definitions underneath.
> > > 
> > > From a content encoding standpoint, the following XML Mapping Rules in
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_rfc6020-23section-2D7.8.5&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=El_GT294heczTOGSYxV-s0MdzjwhB-vEBEVCQNYEdzs&e= do dictate an order
> > > that the keys be defined before other subelements.  JSON obviously does
> > > not utilize the same encoding technique.
> > > 
> > >    The list's key nodes are encoded as subelements to the list's
> > >    identifier element, in the same order as they are defined within the
> > >    "key" statement.
> > > 
> > >    The rest of the list's child nodes are encoded as subelements to the
> > >    list element, after the keys.  If the list defines RPC input or
> > >    output parameters, the subelements are encoded in the same order as
> > >    they are defined within the "list" statement.  Otherwise, the
> > >    subelements are encoded in any order.
> > > 
> > > Given the following simple example:
> > > 
> > > module test {
> > >     namespace "https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=";
> > >     prefix test;
> > > 
> > >     container foo {
> > >         leaf bar {
> > >             type string;
> > >         }
> > >         list car {
> > >             key "far mar";
> > > 
> > >             leaf par {
> > >                 type string;
> > >             }
> > >             leaf far {
> > >                 type string;
> > >             }
> > >             leaf mar {
> > >                 type string;
> > >             }
> > >             leaf nar {
> > >                 type string;
> > >             }
> > >         }
> > >     }
> > > }
> > > 
> > > leaf 'par' here is defined before the 'far' and 'mar' keys, however if
> > > we render out a sample-xml-skeleton with pyang, we do not take into
> > > account the XML encoding rules defined in Section 7.8.5 and merely keep
> > > the order as defined in the model.
> > > 
> > > $ pyang test.yang --strict -f sample-xml-skeleton
> > > <?xml version='1.0' encoding='UTF-8'?>
> > > <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
> > >   <foo xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=">
> > >     <bar />
> > >     <car>
> > >       <par />
> > >       <far />
> > >       <mar />
> > >       <nar />
> > >     </car>
> > >   </foo>
> > > </data>
> > > 
> > > With yanglint, given the following XML document
> > > 
> > > $ cat test.xml
> > > <foo xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=">
> > >     <bar>BAR</bar>
> > >     <car>
> > >         <par>PAR</par>
> > >         <far>FAR</far>
> > >         <mar>MAR</mar>
> > >         <nar>NAR</nar>
> > >     </car>
> > > </foo>
> > > 
> > > The rendered XML output will actually reorder the list keys to be first
> > > 
> > > $ yanglint -f xml test.yang test.xml
> > > <foo xmlns="https://urldefense.proofpoint.com/v2/url?u=http-3A__test&d=DwICAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=GIehbDpQlo31lSi6WbnEkA&m=aIc-CQ8w2Asg5EZaRCunbRr33N3KJwrY_LQRZg_ED0A&s=DtGK_MVelzL9TNkronbZ5Jb77kpX3cG2aR0Sthda_Z4&e=">
> > >   <bar>BAR</bar>
> > >   <car>
> > >     <far>FAR</far>
> > >     <mar>MAR</mar>
> > >     <par>PAR</par>
> > >     <nar>NAR</nar>
> > >   </car>
> > > </foo>
> > > 
> > > Personally, from a BCP standpoint, defining list keys first eases
> > > readability and want to solicit others thoughts on this (rather than
> > > nested down in the list or via a grouping reference further down).
> > 
> > I agree.
> > 
> 
> Should we add text to rfc6087bis to suggest such?  Any reason not to?
> 
> > > Generation to yin does not rearrange in either pyang or yanglint which
> > > means any processing of yin would need to undergo some reordering
> > > possibly depending on how it is absorbed.
> > 
> > I don't understand what you mean.  Yin follows the same rules as basic
> > YANG syntax; it is the "key" statement that defines the XML element
> > order.
> > 
> 
> Just merely pointing out that the same handling that would be done for
> XML encoding rules would need to be done for potential processing of YIN
> if the consumer of said data needs to process ordered elements
> in whatever application.
> 
> Understood this is lossless and a direct mapping
> 
> > > For the JSON encoding case, there may be no strict ordering but
> > > following a BCP where folks *should* send list keys before other
> > > elements can ease implementation efforts in many cases.
> > 
> > I disagree.  Implementations MUST handle object members in any order
> > (std JSON), so they can never use a simpler implementation that is
> > built on the presumption that keys always are sent first.
> > 
> 
> Agreed
> 
> > (However, a clever implemention could check if the keys are sent
> > first, then it can parse more efficiently; it wouldn't have to buffer
> > data.  But this is the opposite of a simple implemention.)
> > 
> 
> This was precisely my point but agree, the assumption can never be made
> due to this
> 
> A BCP could very well be put into code for --ietf, -f yang (and other
> flags) that *could* enforce this ordering within the model itself.  If
> we do add text to rfc6087bis, this should come along w/ imo.
> 
> > > It is also
> > > likely that payloads will generally be constructed in the order in which
> > > they are defined in the model.
> > 
> > Yes.
> > 
> > > So either I see making the definition of such either mandatory or at a
> > > bare minimum pyang sample-xml-skeleton output to take into account
> > > ordering list key leafs prior to other subelements.
> > 
> > I think the bug in pyang should be fixed!
> > 
> 
> Have the fix in a local branch - pull request now at:
> 
> https://github.com/mbj4668/pyang/pull/359
> 
> /ebben
> 

