2009/6/5 PoWah Wong <wong_po...@yahoo.ca>: > > RFC1904, section 6.5.2.3. "Mapping of the ACCESS clause" state that: > The value "write-only" is provided solely for backward compatibility, > and shall not be used for newly-defined object types. > Why?
Because SMIv2 (RFC 2578) defines MIB objects with a *maximum* level of access (rather than an exact access), and has increased the number of possible access values. Allowing arbitrary combinations would have introduce an unnecessary level of complexity. "read-write" effectively covers "write-only" anyway. "write-only" is not a valid MAX-ACCESS level in SMIv2, so has been deprecated in the conformance definitions as well. If you need a more official answer, you should ask on the relevant IETF lists. This list is really intended for support of the Net-SNMP software. Dave ------------------------------------------------------------------------------ OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
