RFC 3986 contains a (brief) description of security considerations for agents that produce or receive and interpret URIs. I would expect this document to at the very least reference those security considerations more explicitly, and at best to analyze how they apply in particular to URIs used within SNMP. It's not clear whether it makes sense for SNMP URIs to contain, for example, 'data:' URIs or 'urn:' or any of a number of schemes, and I would expect some discussion about the applicability of URIs within a SNMP context. URIs are defined as a sequence of characters, not a sequence of octets. The mapping should be explicit (e.g., 'use US-ASCII') and not implicit. In practice, many systems allow and produce IRIs (RFC 3987) and not URIs, to allow for accents and non-roman scripts. I wonder if it would be more appropriate to define the MIB value as an IRI encoded in UTF-8, for example. Larry > -----Original Message----- > From: The IESG [mailto:iesg-secretary@xxxxxxxx] > Sent: Thursday, February 08, 2007 3:02 PM > To: IETF-Announce > Cc: uri-review@xxxxxxxx; uri@xxxxxx > Subject: Last Call: draft-mcwalter-uri-mib (Uniform Resource > Identifier (URI) MIB) to Proposed Standard > > The IESG has received a request from an individual submitter > to consider > the following document: > > - 'Uniform Resource Identifier (URI) MIB ' > <draft-mcwalter-uri-mib-02.txt> as a Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive > comments to the > ietf@xxxxxxxx mailing lists by 2007-03-08. Exceptionally, > comments may be sent to iesg@xxxxxxxx instead. In either case, please > retain the beginning of the Subject line to allow automated sorting. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-mcwalter-uri-mib-02.txt > > > IESG discussion can be tracked via > https://datatracker.ietf.org/public/pidtracker.cgi?command=vie w_id&dTag=15468&rfc_flag=0 > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@xxxxxxxx > https://www1.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf