From disman-bounces@ietf.org  Mon Feb 28 12:30:38 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13192
	for <disman-archive@lists.ietf.org>; Mon, 28 Feb 2005 12:30:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1D5ogL-0003mD-La; Mon, 28 Feb 2005 12:27:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1D5ogK-0003m8-W2
	for disman@megatron.ietf.org; Mon, 28 Feb 2005 12:27:45 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12944
	for <disman@ietf.org>; Mon, 28 Feb 2005 12:27:42 -0500 (EST)
Received: from mx2.liv.ac.uk ([138.253.100.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5oh7-0003uY-IW
	for disman@ietf.org; Mon, 28 Feb 2005 12:28:34 -0500
Received: from mailhub3.liv.ac.uk ([138.253.100.83])
	by mx2.liv.ac.uk with esmtp (Exim 4.34) id 1D5og9-0001zs-4y
	for disman@ietf.org; Mon, 28 Feb 2005 17:27:33 +0000
Received: from localhost ([127.0.0.1] helo=mailhub3.liv.ac.uk)
	by mailhub3.liv.ac.uk with esmtp (Exim 4.34) id 1D5og9-0000qA-30
	for disman@ietf.org; Mon, 28 Feb 2005 17:27:33 +0000
Received: from tethys.server.csc.liv.ac.uk ([138.253.184.237])
	by mailhub3.liv.ac.uk with esmtp (Exim 4.34) id 1D5og9-0000q7-1S
	for disman@ietf.org; Mon, 28 Feb 2005 17:27:33 +0000
Received: from daves.staff.csc.liv.ac.uk (IDENT:daves@daves [10.1.67.1])
	by tethys.server.csc.liv.ac.uk (8.11.1 - (Revision
	1.5)/LUCS-DTS-3.0M10) with ESMTP id j1SHRWX26310
	for <disman@ietf.org>; Mon, 28 Feb 2005 17:27:32 GMT
From: Dave Shield <D.T.Shield@csc.liv.ac.uk>
To: disman@ietf.org
Content-Type: text/plain
Organization: University of Liverpool, Computer Science
Message-Id: <1109611611.8339.179.camel@daves.staff.csc.liv.ac.uk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Mon, 28 Feb 2005 17:26:52 +0000
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Content-Transfer-Encoding: 7bit
Subject: [Disman] Event-MIB - request for clarifications
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

I've recently been looking at the Event MIB, and whilst I've
mostly got a handle on how this works, there are a few things
that I'm not fully clear on.   I've had a look through the
mail archives without much luck, but if these issues have been
covered before, just point me to where they've been discussed.

  The points on which I'd appreciate some clarification are
the following:


a) Wildcard handling

  If mteTriggerValueID uses a "partial" wildcard, then
should the wildcard handling of corresponding mteObjectsID
and mteEventSetObject entry append the *full* instance of
the mteTriggerValueID value that matched, or just the OID
suffix added as part of the expansion?

For example, suppose I'm monitoring an interface-related
table that's indexed by ifName strings, and specify a
mteTriggerValueID of 'someObject."eth"'
(with mteTriggerValueIDWildcard set true).

Then a trigger fires, matching "eth1" (i.e. adding '1')

Should the corresponding mteObjectsID entries be specified
as 'someObject2."eth"' (and add the matching '1' suffix) or
just 'someObject2' (and add the full matching instance "eth1")



b) Updating configuration settings

  The objects in the mteTriggerTable are defined as
read-create, but the description of mteTriggerEntryStatus
states:
     "Once made active an entry may not be modified
      except to delete it."

Does that apply to the whole of that mteTriggerEntry
row, or just the mteTriggerEntryStatus?
For example, is it legitimate to adjust the frequency of
a given trigger, or does the whole row have to be deleted
and recreated?  Similarly for (e.g.) mteTriggerComment?



c)  Access control

The description of mteTriggerTargetTag states that the
mteTriggerValueID value should be retrieved using 
    "the security credentials of the requester that
     set mteTriggerEntryStatus to 'active'"

What credentials should be used if the entry wasn't
configured via SNMP (e.g. from static configuration) ?


The implication of this is that the mteOwner index string
is only used for grouping related entries together (so
that they can all be covered by a single VACM entry).

But the third paragraph of section 7 talks about mapping
this "owner index" to a securityName or groupName.  How
does this relate to the use of the requestor's security
credentials?

This is probably the area that I found least clear?
I await enlightenment.....


Dave




