Re: [yang-doctors] Features and must-condition

[Benoit Claise <[e-mail]>]

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