Re: VACM reports/responses
"Randy Presuhn" <[email protected]> Thu, 8 May 2003 16:33:38 -0700
| Newsgroups | gmane.ietf.snmpv3 |
|---|---|
| Message-ID | <000c01c315ba$40ea40a0$7f1afea9@oemcomputer> |
Hi - (I dropped Sean from the CC list because his mail service has blacklisted my ISP, Earthlink/Mindspring) > From: "Steve Moulton" <[email protected]> > To: <[email protected]> > Cc: <[email protected]> > Sent: Thursday, May 08, 2003 2:37 PM > Subject: Re: VACM reports/responses ... > Note that SNMPv3 command responders will not generate noSuchName > errors in response to SNMPv3 requests. See RFC2576 for more on this. ... But do keep RFC 3416 section 4.2.4 in mind. There are cases where command responders are doing things that are proxy in the classic sense, but not in the RFC 2576 sense, and will not necessarily be able to make the fine-grained distinctions. One case that's probably more wide-spread than anyone would like is access via underlying RFC 1227 machinery. These will generate noSuchName errors when the modern codes would be better. Randy