Re: VACM reports/responses

Hi -

I think you'd find RFC 3413, especially section 3.2 (page 11 or so)
helpful.  The endOfMibView would be correct only if there is nothing
else lexicographically later in the context to which access could be
permitted.  RFC 2741 might also be helpful in explaining the things
that need to happen during get-next and get-bulk proccessing when
access control enters the picture.

Randy

----- Original Message ----- 
From: "Sean Lawless" <[email protected]>
To: <[email protected]>
Sent: Thursday, May 08, 2003 9:29 AM
Subject: VACM reports/responses


> Greetings,
>
> We are having difficulty locating a specification document for View based
> Access Control Model (VACM) error responses/reports.  Specifically, from a
> Command Responder perspective, what should be sent in response to a
> request that results in the VACM function isAccessAllowed returning
> notInView, noSuchView, etc.
>
> From rfc3414 and rfc3415, the best guess we can ascertain is to return a
> standard endOfMibView for GetNext requests that encounter any VACM problem
> and noSuchName for Get and Set requests.
>
> Is this correct and does anyone know a document (rfc) that specifies this?
>
> Thank you much and good day.
>
> Sean Lawless
> Mibtonix, Inc.
>
>