Re: [Isms] current naming agreement
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Isms] current naming agreement
On Thu, Jul 31, 2008 at 02:41:12AM -0700, Wes Hardaker wrote:
> >>>>> On Thu, 31 Jul 2008 10:39:05 +0200, Juergen Schoenwaelder <j.schoenwaelder at jacobs-university.de> said:
>
> JS> If the prefix is dropped by TSM, then I think all the "higher" layers
> JS> in the SNMP engine should never see/worry about the prefix. So it is
> JS> TSM's job to put the prefix back in place again for outgoing
> JS> notifications.
>
> Well, except it's not the lower layers that actually care. Really, the
> thing that cares the most is the VACM which is where we need it. The
> "agent" is the one that needs the prefixed name since it can check the
> VACM for ssh:juergen vs dtls:juergen when the scalar is set to false
> regardless of whether it's checking the authorization of a SET or a INFORM.
But if I turn the 'drop magic prefixes' button on in TSM, I likely do
this because I do not want to distinguish between dtls:schoenw and
tls:schoenw, that is, I do not want to deal with this distinction in
VACM. So in this case, I would expect that TSM has to fill in the
right prefix, no?
/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/>
_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.