On 2019-11-04 11:32, Schönwälder, Jürgen wrote:
Hi,
this may be resolved by adding
The special value '/' refers to the entire accessible tree.
to the description statement. Does this work for you?
Hm, it seems to me that this would conflict with this part of the
description:
A node-instance-identifier value is an
unrestricted YANG instance-identifier expression.
All the same rules as an instance-identifier apply,
except that predicates for keys are optional. If a key
predicate is missing, then the node-instance-identifier
represents all possible server instances for that key.
- since '/' is not a valid value for a YANG instance-identifier.
I.e. if '/' should be included in the typedef (seems reasonable to
me), the text for it probably needs to be "incorporated" in the text
above.
--Per
/js
On Mon, Sep 30, 2019 at 03:17:25PM +0100, Robert Wilton wrote:
Hi Juergen,
Should the "node-instance-identify" type specify how the path "/" is
treated?
I noted that in rfc8341, the behavior for "/" is described in the leaf
"path" description rather than in the type definition, but I was thinking
that it might be better if this behaviour was specified as part of the
typedef.
Snippet from RFC8341:
case data-node {
leaf path {
type node-instance-identifier;
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.";
}
}
Thanks,
Rob
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
