[YANG] config-stmt missing for choice construct

Hi,

It seems the 'config true/false' clause is missing from
the choice-stmt data definition statement.

Without it, there is no way to declare a top-level non-config
choice.  It should be legal to declare a non-config choice nested
within a config node.

Also, 7.17.1, para 2 (config statement) needs to add text that
the 'config' property for the following nodes is hardwired into
the NETCONF architecture:

    rpc/input   --  config true;
                    non-config nodes MUST NOT appear under rpc/input

    rpc/output  --  config false;
                    config nodes MUST NOT appear under rpc/output

    notification -- config false;
                    config nodes MUST NOT appear within a notification

All other nodes follow the rules already defined in this section.

<side-issue>
A top-level RPC method node cannot have config true/false
set, but what about an optional classification field like
(config, exec, monitor, debug, other)?  IMO, this is useful
for operators and access control.
</side-issue>

Andy

_______________________________________________
YANG mailing list
YANG@ietf.org
http://www.ietf.org/mailman/listinfo/yang