Re: [Netconf] draft-ietf-netconf-monitoring-09 last call comments from js

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

On Tue, Nov 03, 2009 at 02:51:09PM +0100, Phil Shafer wrote:
> Juergen Schoenwaelder writes:
> >Not sure I understand your comment - why does radius/tacplus lead to a
> >difference between a "user name" and a "login name"? Which AVPs are
> >you referring to?
> 
> AVP?  My comment has that with radius I can login as one user and
> have the radius server return a different user name to use locally,
> so I can remotely administer a hundred operators as a single
> "operator" local user.  So the permissions may track with the real
> user name ("operator") but the login name ("phil") is also vital
> information.

Tell me how this works (AVPs are the things RADIUS sends around in the
payload) - or better tell me not, since this would impact ISMS badly.

> >This is pretty much what we have been doing in SMIv2 land.
> 
> Cool.  I've seen examples that aren't this way, where the
> MIB text documents the leafs, but not their meaning.  An
> example would be rfc3412, where in a ~40 page rfc, the mib
> is ~3 pages.

You won't expect TCP objects to document how TCP works, right. The
same logic applies to RFC 3412 and all the other SNMP RFCs.

/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/>