Re: [Isms] comments on draft-nelson-isms-extended-vacm-00
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



On Mon, Jul 27, 2009 at 02:54:27PM +0200, Dave Nelson wrote:
 
> The transport populates tmStateReference.  It's up to the extended VACM code
> to do something with that information, i.e., populate MIB tables.

Except that the ASIs do not pass the tmStateReference to VACM.
 
> My concern is related to attempting to use extended VACM, and thus the
> tmStateRefrence, in the absence of a RADIUS-aware secure transport.  The
> only input to the VACM's ASI that would indicate whether there is or is not
> a RADIUS-aware transport at work would be the Security Model selector.  Do
> you see another way to accomplish 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/>

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.