- From: Shigeru Aoki <shig@tfm.co.jp>
- Date: Sat, 7 Feb 2004 01:00:29 +0900
- To: <Black_David@emc.com>, <uri@w3.org>
> 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. It looks controversial to me on "[ ";" [engine ":"] context ]" in the snmp_URI syntax. Can someone tell about this? Regards, Shigeru Aoki Engineering & Technology Div., TFM Co., LTD. Tokyo, JAPAN. ----- Original Message ----- From: <Black_David@emc.com> To: <uri@w3.org> Sent: Friday, February 06, 2004 4:20 PM Subject: FW: I-D ACTION:draft-black-snmp-uri-02.txt > FYI, comments appreciated. > > Thanks, > --David > ---------------------------------------------------- > David L. Black, Senior Technologist > EMC Corporation, 176 South St., Hopkinton, MA 01748 > +1 (508) 293-7953 FAX: +1 (508) 293-7786 > black_david@emc.com Mobile: +1 (978) 394-7754 > ---------------------------------------------------- > > -----Original Message----- > From: owner-ietf-announce@ietf.org [mailto:owner-ietf-announce@ietf.org] On > Behalf Of Internet-Drafts@ietf.org > Sent: Thursday, February 05, 2004 3:44 PM > Subject: I-D ACTION:draft-black-snmp-uri-02.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > Title : URI Scheme for SNMP > Author(s) : D. Black, K. McCloghrie > Filename : draft-black-snmp-uri-02.txt > Pages : 11 > Date : 2004-2-5 > > SNMP and the Internet-Standard Management Framework are widely > used for management of communication devices, creating needs to > specify SNMP access (including access to SNMP MIB object > instances) from non-SNMP management environments. For example, > when out-of-band IP management is used via a separate management > interface (e.g., for a device that does not support in-band IP > access), there is a need for a uniform way to indicate how to > contact the device for management. URLs fit this need well, as > they allow a single text string to indicate a management access > communication endpoint for a wide variety of IP-based protocols. > This document defines a simple URI scheme so that SNMP can be > designated as the protocol used for management. This scheme also > allows URI specification of individual MIB object instances. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-black-snmp-uri-02.txt > > To remove yourself from the IETF Announcement list, send a message to > ietf-announce-request with the word unsubscribe in the body of the message. > > Internet-Drafts are also available by anonymous FTP. Login with the username > "anonymous" and a password of your e-mail address. After logging in, > type "cd internet-drafts" and then > "get draft-black-snmp-uri-02.txt". > > A list of Internet-Drafts directories can be found in > http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > > Internet-Drafts can also be obtained by e-mail. > > Send a message to: > mailserv@ietf.org. > In the body type: > "FILE /internet-drafts/draft-black-snmp-uri-02.txt". > > NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > >
Received on Friday, 6 February 2004 10:34:15 UTC