On 15/10/2018 21:09, Martin Bjorklund wrote: > Hi, > > Robert Varga <n...@hq.sk> wrote: >> It is wide-spread practice to use tailf:action and target statements >> within it with augment/deviate statements -- which I think is a failure >> to follow RFC7950 section 6.3.1: >> >> Care must be taken when defining extensions so that modules that use >> the extensions are meaningful also for applications that do not >> support the extensions. > > Yes, but note that 7950 means a 1.1 module, and tailf:action should be > replaced with 'action' in a 1.1 module.
I think the argument applies (and proposed extension would be
applicable) to RFC6020 as well.
I am not complaining about tailf:action specifically, I will just map it
YANG 1.1 action even in YANG 1.0 mode and I'm done :)
> One reason we added the quoted paragraph to 7950 was because of the
> problem you describe with tailf:action.
I suspected as much, thank you for that :)
>> I think the proper way of fixing this would be to define a YANG
>> extension, which, when used within another extension, would indicate
>> that the extension being defined is part of the schema tree, for example:
>>
>> extension schematree-statement;
>>
>> extension foo {
>> argument bar;
>>
>> sts:schematree-statement;
>> }
>
> Unfortunately, this doesn't solve the problem, since a parser that
> doesn't understand sts:schematree-statement still wouldn't know that
> foo defined a schema node, and thus it will still complain if it sees
> an augment of a node introduced with "ex:foo".
>
> In order for this to work, "schematree-statement" would have to be a
> builtin statement.
>
> (... and if we had this statement, we could have used it in yang-ext
> as well, and avoid augement-yang-data)
Understood and agreed, parsers not supporting schematree-statement would
be left unfixed, but also no worse off.
My skin in the game is to future-proof my parser (based on supporting
widely-available specifications) until this is fixed for everyone with
YANG 1.2. Adding support for a language extension is much simpler than
to bump YANG language support by 0.1, at least in my experience.
This could even help augment-yang-data in that the semantics of what it
does would be kept with the extension (yang-data) as opposed to a
different, related (as understandable by humans), language extension. An
an implementor,
Such extension would also address a piece of RFC7950 section 7.19's:
An extension can allow refinement (see Section 7.13.2) and deviations
(Section 7.20.3.2), but the mechanism for how this is defined is
outside the scope of this specification.
by defining how an extension can declare that it _does_allow_ refinement
and deviations without getting into the business of how that
refinement/deviations are done. This could even be separate extensions:
extension augmentable-statement;
extension deviable-statement;
Such a language extension can be picked up by parsers across all YANG
versions, making adoption much easier and faster.
>> Using that knowledge, the parser can correctly interpret
>> augment/deviation arguments as validly pointing to a particular use of
>> foo (or its descendants) and correctly ignore their effects.
>>
>> Is this something the WG feels is a real problem and would be interested
>> in solving?
>
> The current advice is of course to NEVER add nodes to the schema tree
> with an extension. I think it is probably best to stick to this
> advice...
That advice I missed. Is there a link I can quote? :)
Thanks,
Robert
signature.asc
Description: OpenPGP digital signature
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
