Re: [Isms] comments on draft-nelson-isms-extended-vacm-00

[Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de>]

On Mon, Jul 27, 2009 at 04:47:32PM +0200, d.b.nelson at comcast.net wrote:

> Well, if we follow that precedent, and we want to avoid modifying
> the ASI of the access control model, we'll need to find another
> place to put the "magic".  Since the tmStateReference pointer is
> only used in a "management" channel rather than a "message flow"
> channel, maybe it doesn't need to affect VACM's ASI, anyway.
> 
> Any way you parse it, however, adding new functionality without
> modifying APIs (yes, I meant API, as in concrete implementation
> interface) is difficult.

I think Randy Presuhn's model was that the RADIUS client acts pretty
much like an "embedded" SNMP manager doing a local set to modify the
VACM table. At least this one model to look at this. Another is the
black box magic (like someone /something modifying the SNMP agent's
configuration file is just magic). The WG needs to figure out to which
level of detail we want to / have to specify this.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>