parsing and comparing URIs

[Andy Bierman <ietf@andybierman.com>]

Hi,

I re-read RFC 3986, and it doesn't really say not to parse URIs.
Section 6.2.1 says it is safe to compare 2 URIs as strings.
However, the rules for Normalization and Comparison (sec. 6)
are quite complicated.  I seriously doubt any NETCONF implementation
is following these rules.  RFC 4741 is silent wrt/ normalization.
I need to read more about the URN scheme, which may impose
some constraints on various encodings that would require normalization.

We did not really resolve the 1, 2, or 3 namespace issue wrt/ 
notification draft,
but it seems clear to me that we were ready to agree on 2 namespaces
(1 for <create-subscription> and <notification>, and the other for the 
data model content).

IMO, it is fine to use this convention of a separate namespace for content,
but we should not try to parse NETCONF URIs for some field that
differentiates between protocol operation and protocol content.
If we defined our own scheme with these specific semantics built-in
then this would be okay, but we have to use the 'urn' scheme, so that
is not an option.

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