RE: [Isms] securityName

[Randy Presuhn <randy_presuhn at mindspring.com>]

Hi -

> From: "Fleischman, Eric" <eric.fleischman at boeing.com>
> Sent: Aug 2, 2005 11:07 AM
> To: Tom Petch <nwnetworks at dial.pipex.com>
> Cc: isms at ietf.org
> Subject: RE: [Isms] securityName
...
> However, I am not clear how we are planning on adding additional privacy
> and authentication mechanisms and still leave SNMPv3 USM and VACM
> untouched. Where are the interfaces between the two systems (the old and
> new) being drawn?
...
That is a key point of the SNMPv3 architecture: new interfaces between the
old and new mechanisms should not be needed.  They should plug in using
the *conceptual* interface provided by the ASIs, which are really just a
way of modularizing the specification, not necessarily an implementation.

The addition of a new authentication mechanism should not require any
changes whatsoever to VACM.  The introduction of a new privacy mechanism
should not require any changes whatsoever to VACM.  If it does, something
is very broken.

Randy

Randy

_______________________________________________
Isms mailing list
Isms at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/isms