subtree filtering: content match nodes

[Andy Bierman <ietf@andybierman.com>]

Hi,

I just read sec. 6.2.5 again in RFC 4741, and found yet another 'concern'
with subtree filtering.

The text in the 2nd sentence explicitly states  wrt/ to
a content match node:  "it represents an exact-match filter".

I cannot find any text anywhere that mentions canonical data formats,
or schema data type conversion.  It is extremely likely that an
agent implementation will need to convert between a numeric data type
and a string representation of that data type to support this feature.

For interoperability, we should have a precise meaning of 'exact match'.

Does 'exact match' mean that the agent MUST NOT convert the
filter value to any schema-defined data type (i.e., convert number
to canonical and/or internal format, or adjust string whitespace or
convert character entities)?

Instead, the agent must compare a string representation of the internal
value to the exact filter string value.

Or is the agent allowed to convert the raw filter string to an internal
(schema defined) data type before comparing it to the value from the
target config?

IMO, the post-conversion compare is more user-friendly.

thanks,
Andy











--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>