Hi,

I removed the warnings from our code.
Now doing what YANG says to do.
Ignoring child node different status than parent.
This does not seem to count as a reference.


Andy



On Fri, Dec 29, 2017 at 3:40 AM, Mahesh Jethanandani <
[email protected]> wrote:

> Hi Benoit,
>
> Please ignore my last E-mail. You are referencing ietf-software-ce model
> and I was confused about the e-mail subject line referencing ietf-dslite
> model.
>
> I would agree with Andy about publishing a warning when the reference is
> in the other model.
>
> Med, in the meantime, for the dslite model, can you replace the =
> expression in the 'when' statement with 'derived-from'. Thanks.
>
> Mahesh Jethanandani
> [email protected]
>
> On Dec 27, 2017, at 11:29 AM, Benoit Claise <[email protected]> wrote:
>
> Hi Med,
>
> Thanks.
> With the latest yangdump-pro, there is a new error for
> [email protected]
> See http://www.claise.be/IETFYANGPageCompilation.html
>
> Regards, B.
>
> Hi Andy, Benoit,
>
>
>
> Thank you for investigating this.
>
>
>
> A new version which fixes this issue is available online. A diff is
> available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-
> dslite-yang-11
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Andy Bierman [mailto:[email protected] <[email protected]>]
> *Envoyé :* samedi 18 novembre 2017 22:23
> *À :* Benoit Claise
> *Cc :* [email protected]; Mahesh Jethanandani
> *Objet :* Re: Issue with [email protected] and yangdump-pro
>
>
>
> 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 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 [email protected] and [email protected]
>
>
>
> When I change 'natp44' to 'nat:natp44' in both when-stmts:
>
>
>
> andy@andy-homedev:~/Desktop/FD1289/IETF$ yangdump-pro
> [email protected] modpath=.
>
>
>
> *** /home/andy/Desktop/FD1289/IETF/[email protected]
>
> *** 0 Errors, 0 Warnings
>
>
>
> andy@andy-homedev:~/Desktop/FD1289/IETF$
>
>
>
>
>
> Andy
>
>
>
>
>
> On Sat, Nov 18, 2017 at 11:07 AM, Benoit Claise <[email protected]> wrote:
>
> Hi Andy,
>
> Can you please have a look at [email protected] at
> 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
>
>
>
>
>
>
_______________________________________________
Softwires mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/softwires

Reply via email to