[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: snmpconf Comments on BCP-09

Hi -

> Date: Tue, 13 Aug 2002 11:13:48 +0200
> Message-Id: <200208130913.g7D9Dm200849@haerke.ibr.cs.tu-bs.de>
> From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
> To: snmpconf@snmp.com
> In-reply-to: <>
> 	(dperkins@dsperkins.com)
> Subject: Re: snmpconf Comments on BCP-09
> References: <>
>  <>
>  <>
>  <> <>
> Reply-To: snmpconf@snmp.com
> >>>>> David T Perkins writes:
> David> 6) David> Fine grained access control assignment - a desirable
> David> property is to allow management apps to create resource
> David> instances via an SNMP set, and to gain "exclusive" or "owner"
> David> access as found in file creation operations found in many
> David> operating systems, such as the Unix variants. However, the
> David> VACM-based access control is VERY different than Unix-like file
> David> access control. A design pattern was introduced in the MIB
> David> modules from the DISMAN WG which attempted to mimic the
> David> Unix-like access control behavior on creation. This design
> David> pattern is flawed (and many have not yet realized it). Please
> David> describe the objective, show the MIB design pattern and
> David> describe how it is flawed.
> Can you please send a message to the DISMAN WG list which explains why
> the design pattern is flawed so that we can all understand the issue
> and either fix it or at least document it somewhere?

As disman WG chair, I'd welcome such a discussion on the
disman WG mailing list.

 Randy Presuhn          BMC Software, Inc.  SJC-1.3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San Josť, California 95131  USA
 My opinions and BMC's are independent variables.