- From: Stefan Eissing <stefan.eissing@greenbytes.de>
- Date: Fri, 6 Feb 2004 17:23:06 +0100
- To: <uri@w3.org> <uri@w3.org> <uri@w3.org>
Am 06.02.2004 um 17:00 schrieb Shigeru Aoki: > >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-black-snmp-uri-02.txt > > > Although the syntax of snmp_URI allows text string context in the > authority > part of the URI, RFC2396bis doesn't allow text string context in there. Correct. RFC 2396 did allow it, but 2396bis does no longer. The proposed snmp URI scheme looks almost like a hierarchical uri, but as you noted it differs significantly. I'm in no way fluent on SNMP, but it would seem prudent to either go the "opaque way" and use another character than '/' for separating components, or go the "hierarchical" way and shift the engine/context parts into the path part of the uri. One simple way could be the usage of query parameter or always treat the first two path segments as engine/context identifier with a defined constant for default values. //Stefan
Received on Friday, 6 February 2004 11:25:33 UTC