From owner-disman@dorothy.bmc.com  Thu Aug  1 19:06:48 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20142
	for <disman-archive@lists.ietf.org>; Thu, 1 Aug 2002 19:06:48 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g71NB4n20051;
	Thu, 1 Aug 2002 18:11:05 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA06403
	for disman-list; Thu, 1 Aug 2002 16:01:33 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA06396;
	Thu, 1 Aug 2002 16:01:27 -0700 (PDT)
Date: Thu, 1 Aug 2002 16:01:27 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208012301.QAA06396@dorothy.bmc.com>
To: minutes@ietf.org
Subject: consolidated disman WG minutes from Yokohama
Cc: disman@dorothy.bmc.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Hi -

These are the consolidated minutes from the two sessions of
the distributed management (disman) working group at the 54th
IETF meeting in Yokohama, Japan.  The meeting was chaired
by Randy Presuhn <rpresuhn@bmc.com>  The minutes on Tuesday,
July 16th were taken by Niraj Gopal <niraj@cisco.com> and on
Thursday, July 18th by Chris Elliott <chelliot@cisco.com>

DISMAN WG Meeting minutes
Date : 07/16/2002
Time : 1545-1645
Room Number : 304
Reported by : Niraj Gopal (niraj@cisco.com)

Chair Presentation:

The chair mentioned that INTAP/OSMIC (http://www.intap.or.jp)
is working on CIM/XML over SOAP for Alarms and that might be
relevant for us. But no specific action is needed.
XMLCONF might have some impact on us e.g. Juniper scheme does
not send events thru XML.

Condition MIB Prsentation:

Action Item - Bert to resolve Boiler plate references for
rfc1155, 1215, 1157, 2571 to informative/normative. Especially
becasue SNMPv1 status is now historic and should be
informative.

Action Item - For security section, Kam to list the objects
that are read-create or read-write and if they contain any
privacy information.

There was a discussion regarding referential integrity problem
in one of the tables in this MIB. That MIB table uses a fully
qualified Object Identifier of a resource (MIB Varable in
another table) as one of its indices. But the value of that
resource ID can change across reboots thereby causing this
MIB table index to point to some other value, if the table is
persisted. In addition, VACM configuration for such resource
IDs can be problematic.

It was asked if it would be adequate to say in the Security
Considerations section that resources with unstable indices
(non-persistent) can have problems. Bert pointed out that we
need a separate doc as this a generic problem. Randy pointed
out that ADSL profiles handle it thru description and that
it is a known limitation of VACM.

Action Item - A BCP might be needed for this general referential
integrity problem.

Shall we add a storage type to this table or save all entries?
David Perkins pointed out that for CLI you cannot say if
a particular instance be saved while others are not but it
could be SNMP specific.  Bert mentioned that either storage
type or all entries saved is fine but it should be the same
as we have been doing.

Action Item - Kam to raise this question on mailing list if
all entries should be persistent or only some.

Action Item - Kam to define a IANAItuProbableCauseOrZero TC
in this MIB with Unsigned32 syntax that can take any value
of IANAItuProbableCause or 0. IANA should also be informed
not to assign 0, in future, for IANAItuProbableCause.

Bert pointed out that it could have a 0 value and 0 in Index
is not good. Randy suggested that it is ok for this case.

Rest of the presentation to be finished on Thursday.



Disman Thursday 3:30 18 July 2002

Reported by Chris Elliott chelliot@cisco.com

Alarm MIB

Alarm 38: This issue needs to be clarified on the mailing list.

Alarm 42: Sharon gets to do what she wants with this and will
post her decision for comments on the mailing list.

Alarm n+2: Reserve 0 in TC and point IANA to this TC so they
know to not allocate 0.


Clustering and Replication

No consensus on if this would be useful.

Needs further discussion on mailing list.


MIB table modification tracking MIB

Meeting seemed to have a fair amount of interest in developing
this MIB.

Should it include all objects in table, exclude all counters,
or exclude all objects by default?

Needs further discussion on mailing list


Distributed Management Apps.

No consensus whether the IETF is the appropriate org for this
or whether SNMP has a role here.

No action required. Continued discussion should be on ops-nm
mailing list.


Charter Updates

Have two target dates overdue…

Alarm MIB will be updated and go WG last call August.
ARC MIB update next week and will go WG last call then.

Can disman go dormant?

Consensus of meeting (not list) was that there is still
interesting things to work on.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------


From owner-disman@dorothy.bmc.com  Fri Aug  2 05:52:01 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12519
	for <disman-archive@lists.ietf.org>; Fri, 2 Aug 2002 05:52:00 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g729u2i04371;
	Fri, 2 Aug 2002 04:56:03 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id CAA08203
	for disman-list; Fri, 2 Aug 2002 02:48:49 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA08197;
	Fri, 2 Aug 2002 02:48:43 -0700 (PDT)
Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g729jV400628;
	Fri, 2 Aug 2002 04:45:31 -0500 (CDT)
Received: from auemail1.firewall.lucent.com (unknown [192.11.223.161])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP
	id A829820F074; Fri,  2 Aug 2002 04:50:19 -0500 (CDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g729oGk07582;
	Fri, 2 Aug 2002 05:50:16 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <QDVP151H>; Fri, 2 Aug 2002 11:50:15 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E9389BB@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Cc: disman@dorothy.bmc.com
Subject: RE: consolidated disman WG minutes from Yokohama
Date: Fri, 2 Aug 2002 11:50:11 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

Mmmm.,.. maybe I missed this in the draft minutes.
Anyway your consolidated minutes state:
> Condition MIB Prsentation:
> 
> Action Item - Bert to resolve Boiler plate references for
> rfc1155, 1215, 1157, 2571 to informative/normative. Especially
> becasue SNMPv1 status is now historic and should be informative.
> 
Maybe someone did say this, but the fact is that at this very moment,
and certainly during the Yokohama meeting, SNMPv1 was not yet
historic. Such may be the case in the near future, but it has 
not been reclassified by the IESG yet. It is on our agenda for
next week.

I do have the actiuon item to resilve the normative/informatibe
references. Discussion has started on the mibs@ops.ietf.org
mailing list.

Bert


From owner-disman@dorothy.bmc.com  Fri Aug  2 13:46:46 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28317
	for <disman-archive@lists.ietf.org>; Fri, 2 Aug 2002 13:46:46 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g72Hp4K12064;
	Fri, 2 Aug 2002 12:51:05 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09496
	for disman-list; Fri, 2 Aug 2002 10:43:09 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09489;
	Fri, 2 Aug 2002 10:43:04 -0700 (PDT)
Date: Fri, 2 Aug 2002 10:43:04 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208021743.KAA09489@dorothy.bmc.com>
To: minutes@ietf.org
Subject: Re:  consolidated disman WG minutes from Yokohama
Cc: disman@dorothy.bmc.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Hi -

The following includes a correction to the minutes previously
sent out.
 - - - - - - 

These are the consolidated minutes from the two sessions of
the distributed management (disman) working group at the 54th
IETF meeting in Yokohama, Japan.  The meeting was chaired
by Randy Presuhn <rpresuhn@bmc.com>  The minutes on Tuesday,
July 16th were taken by Niraj Gopal <niraj@cisco.com> and on
Thursday, July 18th by Chris Elliott <chelliot@cisco.com>

DISMAN WG Meeting minutes
Date : 07/16/2002
Time : 1545-1645
Room Number : 304
Reported by : Niraj Gopal (niraj@cisco.com)

Chair Presentation:

The chair mentioned that INTAP/OSMIC (http://www.intap.or.jp)
is working on CIM/XML over SOAP for Alarms and that might be
relevant for us. But no specific action is needed.
XMLCONF might have some impact on us e.g. Juniper scheme does
not send events thru XML.

Condition MIB Prsentation:

Action Item - Bert to resolve Boiler plate references for
rfc1155, 1215, 1157, 2571 to informative/normative. Especially
becasue SNMPv1 status may be going historic and should be
informative.

Action Item - For security section, Kam to list the objects
that are read-create or read-write and if they contain any
privacy information.

There was a discussion regarding referential integrity problem
in one of the tables in this MIB. That MIB table uses a fully
qualified Object Identifier of a resource (MIB Varable in
another table) as one of its indices. But the value of that
resource ID can change across reboots thereby causing this
MIB table index to point to some other value, if the table is
persisted. In addition, VACM configuration for such resource
IDs can be problematic.

It was asked if it would be adequate to say in the Security
Considerations section that resources with unstable indices
(non-persistent) can have problems. Bert pointed out that we
need a separate doc as this a generic problem. Randy pointed
out that ADSL profiles handle it thru description and that
it is a known limitation of VACM.

Action Item - A BCP might be needed for this general referential
integrity problem.

Shall we add a storage type to this table or save all entries?
David Perkins pointed out that for CLI you cannot say if
a particular instance be saved while others are not but it
could be SNMP specific.  Bert mentioned that either storage
type or all entries saved is fine but it should be the same
as we have been doing.

Action Item - Kam to raise this question on mailing list if
all entries should be persistent or only some.

Action Item - Kam to define a IANAItuProbableCauseOrZero TC
in this MIB with Unsigned32 syntax that can take any value
of IANAItuProbableCause or 0. IANA should also be informed
not to assign 0, in future, for IANAItuProbableCause.

Bert pointed out that it could have a 0 value and 0 in Index
is not good. Randy suggested that it is ok for this case.

Rest of the presentation to be finished on Thursday.



Disman Thursday 3:30 18 July 2002

Reported by Chris Elliott chelliot@cisco.com

Alarm MIB

Alarm 38: This issue needs to be clarified on the mailing list.

Alarm 42: Sharon gets to do what she wants with this and will
post her decision for comments on the mailing list.

Alarm n+2: Reserve 0 in TC and point IANA to this TC so they
know to not allocate 0.


Clustering and Replication

No consensus on if this would be useful.

Needs further discussion on mailing list.


MIB table modification tracking MIB

Meeting seemed to have a fair amount of interest in developing
this MIB.

Should it include all objects in table, exclude all counters,
or exclude all objects by default?

Needs further discussion on mailing list


Distributed Management Apps.

No consensus whether the IETF is the appropriate org for this
or whether SNMP has a role here.

No action required. Continued discussion should be on ops-nm
mailing list.


Charter Updates

Have two target dates overdue…

Alarm MIB will be updated and go WG last call August.
ARC MIB update next week and will go WG last call then.

Can disman go dormant?

Consensus of meeting (not list) was that there is still
interesting things to work on.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------



From owner-disman@dorothy.bmc.com  Fri Aug  2 13:46:54 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28330
	for <disman-archive@lists.ietf.org>; Fri, 2 Aug 2002 13:46:53 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g72HpG212129;
	Fri, 2 Aug 2002 12:51:16 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09506
	for disman-list; Fri, 2 Aug 2002 10:43:56 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA09500
	for disman@dorothy.bmc.com; Fri, 2 Aug 2002 10:43:51 -0700 (PDT)
Date: Fri, 2 Aug 2002 10:43:51 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208021743.KAA09500@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: RE: consolidated disman WG minutes from Yokohama
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Hi -

I've sent in the correction.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------

> From owner-disman@dorothy.bmc.com Fri Aug  2 02:49:47 PDT 2002
> Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E9389BB@nl0006exch003u.nl.lucent.com>
> From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
> Cc: disman@dorothy.bmc.com
> Subject: RE: consolidated disman WG minutes from Yokohama
> Date: Fri, 2 Aug 2002 11:50:11 +0200 
> List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
> 
> Mmmm.,.. maybe I missed this in the draft minutes.
> Anyway your consolidated minutes state:
> > Condition MIB Prsentation:
> > 
> > Action Item - Bert to resolve Boiler plate references for
> > rfc1155, 1215, 1157, 2571 to informative/normative. Especially
> > becasue SNMPv1 status is now historic and should be informative.
> > 
> Maybe someone did say this, but the fact is that at this very moment,
> and certainly during the Yokohama meeting, SNMPv1 was not yet
> historic. Such may be the case in the near future, but it has 
> not been reclassified by the IESG yet. It is on our agenda for
> next week.
> 
> I do have the actiuon item to resilve the normative/informatibe
> references. Discussion has started on the mibs@ops.ietf.org
> mailing list.
> 
> Bert
> 


From owner-disman@dorothy.bmc.com  Fri Aug  2 14:43:26 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00622
	for <disman-archive@lists.ietf.org>; Fri, 2 Aug 2002 14:43:25 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g72Iltt06631;
	Fri, 2 Aug 2002 13:47:55 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA10932
	for disman-list; Fri, 2 Aug 2002 11:40:22 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA10926
	for disman@dorothy.bmc.com; Fri, 2 Aug 2002 11:40:19 -0700 (PDT)
Date: Fri, 2 Aug 2002 11:40:19 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208021840.LAA10926@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: more synthetic objects
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Hi -

There's a new i-d, draft-bush-inline-predictive-mgt-00.txt,
that extends the temporal dimensions of of synthetic objects.
Interesting stuff!

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------


From owner-disman@dorothy.bmc.com  Mon Aug  5 01:09:03 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22255
	for <disman-archive@lists.ietf.org>; Mon, 5 Aug 2002 01:09:03 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g755Crn29546;
	Mon, 5 Aug 2002 00:12:53 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id WAA21369
	for disman-list; Sun, 4 Aug 2002 22:03:53 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id WAA21364
	for <disman@dorothy.bmc.com>; Sun, 4 Aug 2002 22:03:49 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7550a708238
	for <disman@dorothy.bmc.com>; Mon, 5 Aug 2002 00:00:36 -0500 (CDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 92FD01FF029
	for <disman@dorothy.bmc.com>; Mon,  5 Aug 2002 00:05:25 -0500 (CDT)
Received: from mira-linc3-1.cisco.com (IDENT:mirapoint@mira-linc3-1.cisco.com [171.69.20.160])
	by sj-msg-core-2.cisco.com (8.12.2/8.12.2) with ESMTP id g7555EhI004592;
	Sun, 4 Aug 2002 22:05:14 -0700 (PDT)
Received: from niraj-w2k3.cisco.com (sjc-vpn3-920.cisco.com [10.21.67.152])
	by mira-linc3-1.cisco.com (Mirapoint)
	with ESMTP id ABD39074;
	Sun, 4 Aug 2002 22:00:44 -0700 (PDT)
Message-Id: <4.3.2.7.2.20020804204059.03ee9cd8@mira-linc3-1.cisco.com>
X-Sender: niraj@mira-linc3-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 04 Aug 2002 22:05:12 -0700
To: disman@dorothy.bmc.com
From: Niraj Gopal <niraj@cisco.com>
Subject: MIB table modifications tracking MIB discussion...
Cc: Niraj Gopal <niraj@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

Hi,

I presented this MIB at DISMAN WG meeting in Yokohama.
The WG members attending this presentation showed fair
amount of interest in pursuing this work. It was decided to
have more discussion about this MIB on the mailing list. I'm
sending this email hoping to kick-off some discussion.

The following items/issues in this MIB were pointed out by
WG members:

- Chris Elliott mentioned that it would be good to combine
the functionality provided by this MIB with the Event MIB.

- Randy mentioned that this MIB could be used for audit
log i.e. a history of who changed what on the device.

- David Perkins pointed out that "web", "xml" enums
  were missing from tmtHistRowModifSource object.

- The user name should be recorded in SNMPv3 case
  also.

- In CLI case, the IP address of the VTY should be
  recorded.

- When a new table is registered, should all the objects
  in that table be moved to tmtRegExcludeObjTable by
  default or not?

- Dave Perkins also pointed out that the way this MIB
  handles notifications target is not legal and it should
  rely on SNMP-TARGET-MIB for notifications handling.

  Response: This MIB allows the NMS to configure a target for
  mib data change notifications for only the tables that the
  users has registered. I was under the impression that it
  was not possible to achieve this using SNMP-TARGET-MIB.
  I'll look into the target MIB again and if it could be done
  using this MIB, I'll remove the notifications handling
  mechanism from TMT MIB.

Thanks,
Niraj



From owner-disman@dorothy.bmc.com  Mon Aug  5 20:08:43 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08286
	for <disman-archive@lists.ietf.org>; Mon, 5 Aug 2002 20:08:42 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g760D9C11749;
	Mon, 5 Aug 2002 19:13:10 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA25977
	for disman-list; Mon, 5 Aug 2002 17:05:40 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA25971
	for disman@dorothy.bmc.com; Mon, 5 Aug 2002 17:05:35 -0700 (PDT)
Date: Mon, 5 Aug 2002 17:05:35 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208060005.RAA25971@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re:  MIB table modifications tracking MIB discussion...
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Hi -

> Message-Id: <4.3.2.7.2.20020804204059.03ee9cd8@mira-linc3-1.cisco.com>
> Date: Sun, 04 Aug 2002 22:05:12 -0700
> To: disman@dorothy.bmc.com
> From: Niraj Gopal <niraj@cisco.com>
> Subject: MIB table modifications tracking MIB discussion...
> Cc: Niraj Gopal <niraj@cisco.com>
...
> - Dave Perkins also pointed out that the way this MIB
>   handles notifications target is not legal and it should
>   rely on SNMP-TARGET-MIB for notifications handling.
> 
>   Response: This MIB allows the NMS to configure a target for
>   mib data change notifications for only the tables that the
>   users has registered. I was under the impression that it
>   was not possible to achieve this using SNMP-TARGET-MIB.
>   I'll look into the target MIB again and if it could be done
>   using this MIB, I'll remove the notifications handling
>   mechanism from TMT MIB.
...

Since tmtRegistrationTable and tmtHistRowModifTable
both have an owner string index, one could use the
snmpNotifyFilterSubtree from RFC 2573 to forward
tmtTableRowModified notifications corresponding to a
particular user's entries. There's really no need for the
special-purpose tmtControlNotificationsTable mechanism in
this MIB, as far as I can see.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------


From owner-disman@dorothy.bmc.com  Tue Aug  6 12:00:58 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16186
	for <disman-archive@lists.ietf.org>; Tue, 6 Aug 2002 12:00:57 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g76G5C821312;
	Tue, 6 Aug 2002 11:05:12 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA04600
	for disman-list; Tue, 6 Aug 2002 08:56:16 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA04595
	for <disman@dorothy.bmc.com>; Tue, 6 Aug 2002 08:56:12 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g76Fqve00215
	for <disman@dorothy.bmc.com>; Tue, 6 Aug 2002 10:52:57 -0500 (CDT)
Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id A1B601FF024
	for <disman@dorothy.bmc.com>; Tue,  6 Aug 2002 10:57:46 -0500 (CDT)
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g76FvYW16871
	for <disman@dorothy.bmc.com>; Tue, 6 Aug 2002 11:57:34 -0400 (EDT)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <MT10YBMQ>; Tue, 6 Aug 2002 11:57:34 -0400
Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE00BE85C@nj7460exch004u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: "'disman@dorothy.bmc.com'" <disman@dorothy.bmc.com>
Subject: Actiuon items from ARC discussion 
Date: Tue, 6 Aug 2002 11:57:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

Hi,

During the ARC discussion, I was assigned several action items.
(See the Consolidated disman WG minutes from Yokohama from Randy on August 1.)
Here are the status of those action items.

(1) Security 
> Action Item - For security section, Kam to list the objects
> that are read-create or read-write and if they contain any
> privacy information.

In version -03 of the ARC mib, the following text was added 
as the 2nd paragraph of section 6.

   In particular, the ARC setting feature defined in the MIB affects 
   alarm notification generation. Unauthorized access to the write-able 
   objects could cause omission of alarm notifications or flooding 
   of unwanted alarm notifications from the netowrk. These write-able
   objects (defined with a MAX-ACCESS clause of read-create) are:
   arcMIBTITimeInterval, arcMIBCDTimeInterval, arcState,
   arcNalmTimeRemaining, and arcRowStatus.

(2) Persistency 
> Shall we add a storage type to this table or save all entries?
> David Perkins pointed out that for CLI you cannot say if
> a particular instance be saved while others are not but it
> could be SNMP specific.  Bert mentioned that either storage
> type or all entries saved is fine but it should be the same
> as we have been doing.
> 
> Action Item - Kam to raise this question on mailing list if
> all entries should be persistent or only some.

Discussion on "persistency" has already occurred in this mailing 
list since July 20 right after the Yokohama meeting and also occurred
recently in the mibs mailing list. 

In version -03 of the ARC mib, the following sentence was added to
the arcEntry to describe persistence across agent restarts.

     Instances of this conceptual row SHOULD persist across agent 
     restarts.

Any comments?

(3) IANAItuProbableCauseOrZero
> Action Item - Kam to define a IANAItuProbableCauseOrZero TC
> in this MIB with Unsigned32 syntax that can take any value
> of IANAItuProbableCause or 0. IANA should also be informed
> not to assign 0, in future, for IANAItuProbableCause.

In version -03 of the ARC mib, a IANAItuProbableCauseOrZero TC
is defined. The syntax of arcAlarmType is thus changed from 
IANAItuProbableCause to IANAItuProbableCauseOrZero.

I think it is more appropriate for the Alarm MIB document to 
note that IANA should reserve 0 for the IANAItuProbableCause
TC. In fact the meeting minute has the following note for the
Alarm MIB discussion.
> 
> Alarm n+2: Reserve 0 in TC and point IANA to this TC so they
> know to not allocate 0.
> 

(4) Version -03 of the ARC MIB
> ARC MIB update next week and will go WG last call then.
> 
Version -03 has been submitted and available at
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-03.txt

Regards,
Kam


From owner-disman@dorothy.bmc.com  Tue Aug  6 12:58:19 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18488
	for <disman-archive@lists.ietf.org>; Tue, 6 Aug 2002 12:58:18 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g76H2dt11925;
	Tue, 6 Aug 2002 12:02:44 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA04720
	for disman-list; Tue, 6 Aug 2002 09:55:37 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA04715
	for <disman@dorothy.bmc.com>; Tue, 6 Aug 2002 09:55:33 -0700 (PDT)
Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g76GqDE09875
	for <disman@dorothy.bmc.com>; Tue, 6 Aug 2002 11:52:13 -0500 (CDT)
Received: from sj-msg-core-4.cisco.com (unknown [171.71.163.54])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 0005620EF8C
	for <disman@dorothy.bmc.com>; Tue,  6 Aug 2002 11:57:03 -0500 (CDT)
Received: from mira-linc3-1.cisco.com (IDENT:mirapoint@mira-linc3-1.cisco.com [171.69.20.160])
	by sj-msg-core-4.cisco.com (8.12.2/8.12.2) with ESMTP id g76Gv26I002533
	for <disman@dorothy.bmc.com>; Tue, 6 Aug 2002 09:57:02 -0700 (PDT)
Received: from niraj-w2k3.cisco.com (dhcp-171-71-137-59.cisco.com [171.71.137.59])
	by mira-linc3-1.cisco.com (Mirapoint)
	with ESMTP id ABD51159;
	Tue, 6 Aug 2002 09:52:32 -0700 (PDT)
Message-Id: <4.3.2.7.2.20020806095542.02a83868@mira-linc3-1.cisco.com>
X-Sender: niraj@mira-linc3-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 06 Aug 2002 09:57:00 -0700
To: disman@dorothy.bmc.com
From: Niraj Gopal <niraj@cisco.com>
Subject: Re:  MIB table modifications tracking MIB discussion...
In-Reply-To: <200208060005.RAA25971@dorothy.bmc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id JAA04716
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

At 05:05 PM 8/5/2002 -0700, Randy Presuhn wrote:
>Hi -
>
> > Message-Id: <4.3.2.7.2.20020804204059.03ee9cd8@mira-linc3-1.cisco.com>
> > Date: Sun, 04 Aug 2002 22:05:12 -0700
> > To: disman@dorothy.bmc.com
> > From: Niraj Gopal <niraj@cisco.com>
> > Subject: MIB table modifications tracking MIB discussion...
> > Cc: Niraj Gopal <niraj@cisco.com>
>...
> > - Dave Perkins also pointed out that the way this MIB
> >   handles notifications target is not legal and it should
> >   rely on SNMP-TARGET-MIB for notifications handling.
> >
> >   Response: This MIB allows the NMS to configure a target for
> >   mib data change notifications for only the tables that the
> >   users has registered. I was under the impression that it
> >   was not possible to achieve this using SNMP-TARGET-MIB.
> >   I'll look into the target MIB again and if it could be done
> >   using this MIB, I'll remove the notifications handling
> >   mechanism from TMT MIB.
>...
>
>Since tmtRegistrationTable and tmtHistRowModifTable
>both have an owner string index, one could use the
>snmpNotifyFilterSubtree from RFC 2573 to forward
>tmtTableRowModified notifications corresponding to a
>particular user's entries. There's really no need for the
>special-purpose tmtControlNotificationsTable mechanism in
>this MIB, as far as I can see.

Ok, I'll take the notifications handling mechanism out
of this MIB.

Thanks,
-Niraj


>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  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.
>  ------------------------------------------------------




From owner-disman@dorothy.bmc.com  Tue Aug  6 14:34:56 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22869
	for <disman-archive@lists.ietf.org>; Tue, 6 Aug 2002 14:34:56 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g76IcP518674;
	Tue, 6 Aug 2002 13:38:26 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA05771
	for disman-list; Tue, 6 Aug 2002 11:31:21 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA05765
	for disman@dorothy.bmc.com; Tue, 6 Aug 2002 11:31:18 -0700 (PDT)
Date: Tue, 6 Aug 2002 11:31:18 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208061831.LAA05765@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re: referential integrity across reboots
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Hi -

There is a discussion taking place on the mibs and the entmib
WG mailing lists about referential integrity across reboots.
This is relevant to all disman mibs that have (potentially)
persistent object references, including, for example,
alarmActiveResourceId in the current alarm work.  We don't
need to replay the discussion here, but if you're not already
on those mailing lists, I strongly recommend joining those
discussions.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------


From owner-disman@dorothy.bmc.com  Tue Aug  6 14:43:30 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23300
	for <disman-archive@lists.ietf.org>; Tue, 6 Aug 2002 14:43:29 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g76Ilmn22377;
	Tue, 6 Aug 2002 13:47:48 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA05889
	for disman-list; Tue, 6 Aug 2002 11:41:03 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA05881
	for disman@dorothy.bmc.com; Tue, 6 Aug 2002 11:40:59 -0700 (PDT)
Date: Tue, 6 Aug 2002 11:40:59 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208061840.LAA05881@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re:  MIB table modifications tracking MIB discussion...
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Hi -

> Message-Id: <4.3.2.7.2.20020806095542.02a83868@mira-linc3-1.cisco.com>
> Date: Tue, 06 Aug 2002 09:57:00 -0700
> To: disman@dorothy.bmc.com
> From: Niraj Gopal <niraj@cisco.com>
> Subject: Re:  MIB table modifications tracking MIB discussion...
> In-Reply-To: <200208060005.RAA25971@dorothy.bmc.com>
...
> >Since tmtRegistrationTable and tmtHistRowModifTable
> >both have an owner string index, one could use the
> >snmpNotifyFilterSubtree from RFC 2573 to forward
> >tmtTableRowModified notifications corresponding to a
> >particular user's entries. There's really no need for the
> >special-purpose tmtControlNotificationsTable mechanism in
> >this MIB, as far as I can see.
> 
> Ok, I'll take the notifications handling mechanism out
> of this MIB.
...

Since it seems clear that how one would use RFC 2573 to
support this function is not sufficiently obvious to everyone,
it might be a good idea to include as an informational "use
case" how one would use RFC 2573 in conjuction with this MIB
to accomplish this particular function.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  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.
 ------------------------------------------------------


From owner-disman@dorothy.bmc.com  Tue Aug 13 12:55:15 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03946
	for <disman-archive@lists.ietf.org>; Tue, 13 Aug 2002 12:55:14 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7DGwqc06518;
	Tue, 13 Aug 2002 11:58:52 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA10151
	for disman-list; Tue, 13 Aug 2002 09:49:42 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA10146
	for <disman@dorothy.bmc.com>; Tue, 13 Aug 2002 09:49:38 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7DGkHo24565
	for <disman@dorothy.bmc.com>; Tue, 13 Aug 2002 11:46:17 -0500 (CDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id B16611FF03A
	for <disman@dorothy.bmc.com>; Tue, 13 Aug 2002 11:51:09 -0500 (CDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g7DGor41010881;
	Tue, 13 Aug 2002 18:50:53 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g7DGoqE07222;
	Tue, 13 Aug 2002 18:50:52 +0200
Date: Tue, 13 Aug 2002 18:50:52 +0200
Message-Id: <200208131650.g7DGoqE07222@haerke.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: hklam@lucent.com
Cc: disman@dorothy.bmc.com
In-reply-to: 
	<E4BB443436F22D4AB9E84B06AB7C4CE00BE85C@nj7460exch004u.ho.lucent.com>
	(hklam@lucent.com)
Subject: Re: Actiuon items from ARC discussion
References:  <E4BB443436F22D4AB9E84B06AB7C4CE00BE85C@nj7460exch004u.ho.lucent.com>
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>


>>>>> Lam, Hing-Kam (Kam) writes:

Lam> In version -03 of the ARC mib, the following sentence was added
Lam> to the arcEntry to describe persistence across agent restarts.

Lam>      Instances of this conceptual row SHOULD persist across agent
Lam>      restarts.

Lam> Any comments?

What does that tell me as a management application writer? Can I
assume that all rows have an implicit storage type of nonVolatile or
stronger? Moreover, can I rely on the rows being persistent?  (In
other words, when does the SHOULD apply?)

Note that without a storage type, there is no way to distinguish
between permanent,readOnly and nonVolatile rows which makes it harder
to grab and replay configurations...

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>




From owner-disman@dorothy.bmc.com  Fri Aug 23 21:07:40 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21828
	for <disman-archive@lists.ietf.org>; Fri, 23 Aug 2002 21:07:39 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7O1CAh02783;
	Fri, 23 Aug 2002 20:12:10 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA00660
	for disman-list; Fri, 23 Aug 2002 18:02:47 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA00650
	for disman@dorothy.bmc.com; Fri, 23 Aug 2002 18:02:44 -0700 (PDT)
Date: Fri, 23 Aug 2002 18:02:44 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208240102.SAA00650@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Document updates?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Hi -

In Yokohama, there were action items to generated updated documents.
When will these appear?

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


From owner-disman@dorothy.bmc.com  Tue Aug 27 15:19:09 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08490
	for <disman-archive@lists.ietf.org>; Tue, 27 Aug 2002 15:19:09 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7RJNZu06823;
	Tue, 27 Aug 2002 14:23:40 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA11346
	for disman-list; Tue, 27 Aug 2002 12:14:58 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA11203
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 11:51:19 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7RIlnZ11942
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 13:47:49 -0500 (CDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 5BD5A1FF034
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 13:50:31 -0500 (CDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06546
	for <1timer>; Tue, 27 Aug 2002 14:44:44 -0400 (EDT)
Message-Id: <200208271844.OAA06546@ietf.org>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: IETF WG Participants: ;
Subject: Nomcom call for volunteers
Date: Tue, 27 Aug 2002 14:44:44 -0400
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>


The members of the IESG and IAB and the IETF chair are selected
by a nominations committee made up of volunteers from the
IETF community.  The nominations committee is now in the process
of being formed and volunteers are being accepted until Sep 6.
Please see (http://www.ietf.org/nomcom/msg19765.html)
for information if you are interested in volunteering 
to be on the nominations committee.




From owner-disman@dorothy.bmc.com  Tue Aug 27 15:19:10 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08489
	for <disman-archive@lists.ietf.org>; Tue, 27 Aug 2002 15:19:09 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7RJNwi07004;
	Tue, 27 Aug 2002 14:23:58 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA11375
	for disman-list; Tue, 27 Aug 2002 12:16:56 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA11213
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 11:51:34 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7RIjhv10460
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 13:45:43 -0500 (CDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 5BD5A1FF034
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 13:50:31 -0500 (CDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06546
	for <1timer>; Tue, 27 Aug 2002 14:44:44 -0400 (EDT)
Message-Id: <200208271844.OAA06546@ietf.org>
From: Phil Roberts <PRoberts@MEGISTO.com>
To: IETF WG Participants: ;
Subject: Nomcom call for volunteers
Date: Tue, 27 Aug 2002 14:44:44 -0400
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>


The members of the IESG and IAB and the IETF chair are selected
by a nominations committee made up of volunteers from the
IETF community.  The nominations committee is now in the process
of being formed and volunteers are being accepted until Sep 6.
Please see (http://www.ietf.org/nomcom/msg19765.html)
for information if you are interested in volunteering 
to be on the nominations committee.




From owner-disman@dorothy.bmc.com  Tue Aug 27 17:42:08 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13665
	for <disman-archive@lists.ietf.org>; Tue, 27 Aug 2002 17:42:08 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7RLl3A25201;
	Tue, 27 Aug 2002 16:47:03 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA11942
	for disman-list; Tue, 27 Aug 2002 14:39:46 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA11937
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 14:39:41 -0700 (PDT)
Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7RLaDX04537
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 16:36:13 -0500 (CDT)
Received: from auemail2.firewall.lucent.com (unknown [192.11.223.163])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 35B7220EF8A
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 16:41:16 -0500 (CDT)
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g7RLfEh04075
	for <disman@dorothy.bmc.com>; Tue, 27 Aug 2002 17:41:15 -0400 (EDT)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <RJ47DASF>; Tue, 27 Aug 2002 17:41:14 -0400
Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE00BE8C9@nj7460exch004u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: "'Juergen Schoenwaelder'" <schoenw@ibr.cs.tu-bs.de>,
        disman@dorothy.bmc.com
Subject: RE: Actiuon items from ARC discussion
Date: Tue, 27 Aug 2002 17:41:14 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

There are at least three possible levels of granulatity for persistence.

(1) With a storage type object. This will allow differentiation of
different level of persistence (e.g., nonVolatile vs permanent vs 
readOnly) and different row to have different level of persistence.

(2) With a MUST sentence: "Instances of this conceptual row MUST persist 
across agent restarts." This implies ALL rows are persistent. But there
is no differentiation of different level of persistence.

(3) With a SHOULD sentence: "Instances of this conceptual row SHOULD 
persist across agent restarts." There is no differentiation of different 
level of persistence. Moreover, cannot tell which row is persistent.

I agree with Juergen's concern. To address that, I would like to propose 
adding a storage type object to the ARC table. 
Note that according to the M.3100 ARC requirements, arcState must allow
changes by management request. Therefore, no row can be readOnly.

Given that, here is the proposed text for the storage type object that 
will be added to the arcTable.

arcStorageType OBJECT-TYPE
    SYNTAX       StorageType
    MAX-ACCESS   read-create
    STATUS       current
    DESCRIPTION "The storage type for this conceptual row.
                 Conceptual rows having the value 'permanent' must 
                 allow write-access at a minimum to arcState.
                 Note that arcState must allow change by management request.      
                 Therefore, no row can be created with 'readOnly'.
                 If a set operation tries to set the value to 'readOnly',
                 then an 'inconsistentValue' error must be returned.
                "
    DEFVAL      { nonVolatile }
    ::= { arcEntry 7}


Any comments?

Regards,
Kam Lam


   

> -----Original Message-----
> From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
> Sent: Tuesday, August 13, 2002 12:51 PM
> To: hklam@lucent.com
> Cc: disman@dorothy.bmc.com
> Subject: Re: Actiuon items from ARC discussion
> 
> 
> 
> >>>>> Lam, Hing-Kam (Kam) writes:
> 
> Lam> In version -03 of the ARC mib, the following sentence was added
> Lam> to the arcEntry to describe persistence across agent restarts.
> 
> Lam>      Instances of this conceptual row SHOULD persist across agent
> Lam>      restarts.
> 
> Lam> Any comments?
> 
> What does that tell me as a management application writer? Can I
> assume that all rows have an implicit storage type of nonVolatile or
> stronger? Moreover, can I rely on the rows being persistent?  (In
> other words, when does the SHOULD apply?)
> 
> Note that without a storage type, there is no way to distinguish
> between permanent,readOnly and nonVolatile rows which makes it harder
> to grab and replay configurations...
> 
> /js
> 
> -- 
> Juergen Schoenwaelder    
> <http://www.informatik.uni-osnabrueck.de/schoenw/>
> 
> 


From owner-disman@dorothy.bmc.com  Wed Aug 28 06:05:30 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22269
	for <disman-archive@lists.ietf.org>; Wed, 28 Aug 2002 06:05:30 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7SAAMV24938;
	Wed, 28 Aug 2002 05:10:23 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id DAA13710
	for disman-list; Wed, 28 Aug 2002 03:02:39 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id DAA13705
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 03:02:34 -0700 (PDT)
Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7S9x7608643
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 04:59:07 -0500 (CDT)
Received: from auemail2.firewall.lucent.com (unknown [192.11.223.163])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id BDC8520EF92
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 05:04:10 -0500 (CDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g7SA45701988
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 06:04:09 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <RV6DTT0H>; Wed, 28 Aug 2002 12:04:04 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0EC61A69@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>, disman@dorothy.bmc.com
Subject: RE: Actiuon items from ARC discussion
Date: Wed, 28 Aug 2002 12:04:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

Once you define this object as described, you can then
in the MODULE-COMPLIANCE specify that it cannot be
set to read-only as follows:

   OBJECT arcStorageType
   WRITE-SYNTAX StorageType {
                     other(1),      -- atually I am not sure you would like to allow this?
                     volatile(2), 
                     nonVolatile(3),
                     permanent(4) 
                }
   DESCRITPION "The arcState object must allow change by management request.      
                Therefore, no row can be created with 'readOnly'."

Bert 

> -----Original Message-----
> From: Lam, Hing-Kam (Kam) [mailto:hklam@lucent.com]
> Sent: dinsdag 27 augustus 2002 23:41
> To: 'Juergen Schoenwaelder'; disman@dorothy.bmc.com
> Subject: RE: Actiuon items from ARC discussion
> 
> 
> There are at least three possible levels of granulatity for 
> persistence.
> 
> (1) With a storage type object. This will allow differentiation of
> different level of persistence (e.g., nonVolatile vs permanent vs 
> readOnly) and different row to have different level of persistence.
> 
> (2) With a MUST sentence: "Instances of this conceptual row 
> MUST persist 
> across agent restarts." This implies ALL rows are persistent. 
> But there
> is no differentiation of different level of persistence.
> 
> (3) With a SHOULD sentence: "Instances of this conceptual row SHOULD 
> persist across agent restarts." There is no differentiation 
> of different 
> level of persistence. Moreover, cannot tell which row is persistent.
> 
> I agree with Juergen's concern. To address that, I would like 
> to propose 
> adding a storage type object to the ARC table. 
> Note that according to the M.3100 ARC requirements, arcState 
> must allow
> changes by management request. Therefore, no row can be readOnly.
> 
> Given that, here is the proposed text for the storage type 
> object that 
> will be added to the arcTable.
> 
> arcStorageType OBJECT-TYPE
>     SYNTAX       StorageType
>     MAX-ACCESS   read-create
>     STATUS       current
>     DESCRIPTION "The storage type for this conceptual row.
>                  Conceptual rows having the value 'permanent' must 
>                  allow write-access at a minimum to arcState.
>                  Note that arcState must allow change by 
> management request.      
>                  Therefore, no row can be created with 'readOnly'.
>                  If a set operation tries to set the value to 
> 'readOnly',
>                  then an 'inconsistentValue' error must be returned.
>                 "
>     DEFVAL      { nonVolatile }
>     ::= { arcEntry 7}
> 
> 
> Any comments?
> 
> Regards,
> Kam Lam
> 
> 
>    
> 
> > -----Original Message-----
> > From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de]
> > Sent: Tuesday, August 13, 2002 12:51 PM
> > To: hklam@lucent.com
> > Cc: disman@dorothy.bmc.com
> > Subject: Re: Actiuon items from ARC discussion
> > 
> > 
> > 
> > >>>>> Lam, Hing-Kam (Kam) writes:
> > 
> > Lam> In version -03 of the ARC mib, the following sentence was added
> > Lam> to the arcEntry to describe persistence across agent restarts.
> > 
> > Lam>      Instances of this conceptual row SHOULD persist 
> across agent
> > Lam>      restarts.
> > 
> > Lam> Any comments?
> > 
> > What does that tell me as a management application writer? Can I
> > assume that all rows have an implicit storage type of nonVolatile or
> > stronger? Moreover, can I rely on the rows being persistent?  (In
> > other words, when does the SHOULD apply?)
> > 
> > Note that without a storage type, there is no way to distinguish
> > between permanent,readOnly and nonVolatile rows which makes 
> it harder
> > to grab and replay configurations...
> > 
> > /js
> > 
> > -- 
> > Juergen Schoenwaelder    
> > <http://www.informatik.uni-osnabrueck.de/schoenw/>
> > 
> > 
> 


From owner-disman@dorothy.bmc.com  Wed Aug 28 07:56:51 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24842
	for <disman-archive@lists.ietf.org>; Wed, 28 Aug 2002 07:56:50 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7SBuVB02630;
	Wed, 28 Aug 2002 06:56:36 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA13914
	for disman-list; Wed, 28 Aug 2002 04:49:13 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id EAA13909
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 04:49:09 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7SBjgc02734
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 06:45:42 -0500 (CDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 5C0C91FF036
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 06:50:44 -0500 (CDT)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g7SBoTA14417
	for <disman@dorothy.bmc.com>; Wed, 28 Aug 2002 07:50:32 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <RL839V74>; Wed, 28 Aug 2002 07:50:32 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD34049D1B7F@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: RE: Document updates?
Date: Wed, 28 Aug 2002 07:50:31 -0400
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

hi

The Alarm MIB is in final review and will be sent in by the
end of the week.

Sharon

-----Original Message-----
From: Randy Presuhn [mailto:rpresuhn@dorothy.bmc.com]
Sent: Friday, August 23, 2002 9:03 PM
To: disman@dorothy.bmc.com
Subject: Document updates?


Hi -

In Yokohama, there were action items to generated updated documents.
When will these appear?

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


From owner-disman@dorothy.bmc.com  Wed Aug 28 15:27:27 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15206
	for <disman-archive@lists.ietf.org>; Wed, 28 Aug 2002 15:27:27 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7SJVml03594;
	Wed, 28 Aug 2002 14:31:48 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA15223
	for disman-list; Wed, 28 Aug 2002 12:23:14 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA15217;
	Wed, 28 Aug 2002 12:23:10 -0700 (PDT)
Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7SJJeu01916;
	Wed, 28 Aug 2002 14:19:40 -0500 (CDT)
Received: from auemail2.firewall.lucent.com (unknown [192.11.223.163])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP
	id 71CFD20EFBA; Wed, 28 Aug 2002 14:24:43 -0500 (CDT)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g7SJOgE26685;
	Wed, 28 Aug 2002 15:24:42 -0400 (EDT)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <RJT6TXRC>; Wed, 28 Aug 2002 15:24:41 -0400
Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE00BE8D1@nj7460exch004u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: "'Randy Presuhn'" <rpresuhn@dorothy.bmc.com>, disman@dorothy.bmc.com
Subject: RE: Document updates?
Date: Wed, 28 Aug 2002 15:24:41 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

Randy,

Per the action item, Version -03 of the ARC MIB has been submitted on 
July 29 and available at
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-03.txt

Based on the recent comments on persistence, I have proposed to add a 
storage type object to the arc table. If there is no objection, I would 
like to submit soon a version -04 to incorporate the proposal.

Regards,
Kam

> -----Original Message-----
> From: Randy Presuhn [mailto:rpresuhn@dorothy.bmc.com]
> Sent: Friday, August 23, 2002 9:03 PM
> To: disman@dorothy.bmc.com
> Subject: Document updates?
> 
> 
> Hi -
> 
> In Yokohama, there were action items to generated updated documents.
> When will these appear?
> 
>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  SJC-1.3141
>  randy_presuhn@bmc.com  2141 North First Street
>  Tel: +1 408 546-1006   San Jose, California 95131  USA
>  ------------------------------------------------------
>  My opinions and BMC's are independent variables.
>  ------------------------------------------------------
> 


From owner-disman@dorothy.bmc.com  Wed Aug 28 16:54:47 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18700
	for <disman-archive@lists.ietf.org>; Wed, 28 Aug 2002 16:54:46 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7SKxZl20246;
	Wed, 28 Aug 2002 15:59:35 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA15461
	for disman-list; Wed, 28 Aug 2002 13:51:54 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA15455
	for disman@dorothy.bmc.com; Wed, 28 Aug 2002 13:51:50 -0700 (PDT)
Date: Wed, 28 Aug 2002 13:51:50 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208282051.NAA15455@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: RE: Document updates?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Hi -

> Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE00BE8D1@nj7460exch004u.ho.lucent.com>
> From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
> To: "'Randy Presuhn'" <rpresuhn@dorothy.bmc.com>, disman@dorothy.bmc.com
> Subject: RE: Document updates?
> Date: Wed, 28 Aug 2002 15:24:41 -0400
...
> Per the action item, Version -03 of the ARC MIB has been submitted on 
> July 29 and available at
> http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-03.txt
> 
> Based on the recent comments on persistence, I have proposed to add a 
> storage type object to the arc table. If there is no objection, I would 
> like to submit soon a version -04 to incorporate the proposal.
...

Go for it.

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


From owner-disman@dorothy.bmc.com  Thu Aug 29 14:38:25 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06031
	for <disman-archive@lists.ietf.org>; Thu, 29 Aug 2002 14:38:24 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7TIhJQ12044;
	Thu, 29 Aug 2002 13:43:19 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA18958
	for disman-list; Thu, 29 Aug 2002 11:35:48 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA18209
	for <disman@dorothy.bmc.com>; Thu, 29 Aug 2002 07:43:03 -0700 (PDT)
Received: from mx-us-hou-1-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7TEdYi09716
	for <disman@dorothy.bmc.com>; Thu, 29 Aug 2002 09:39:34 -0500 (CDT)
Received: from mailwest.unispherenetworks.com (unknown [65.194.140.130])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 6E9E320EF93
	for <disman@dorothy.bmc.com>; Thu, 29 Aug 2002 09:44:38 -0500 (CDT)
Received: by UNIWEST1 with Internet Mail Service (5.5.2653.19)
	id <RDGT6ZSJ>; Thu, 29 Aug 2002 10:44:38 -0400
Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C0274F6AE@UNIWEST1>
From: "Sajedi, Mohammad" <msajedi@juniper.net>
To: "'disman@dorothy.bmc.com'" <disman@dorothy.bmc.com>
Subject: Event MIB mteTriggerEnabled
Date: Thu, 29 Aug 2002 10:44:33 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

What is the difference between (mteTriggerEnabled = false) and
(mteTriggerEntryStatus = notInService)?
I think they are the same and the mteTriggerEnabled object is redundant.

Mohammad Sajedi
Juniper Networks Inc.
10 Technology Park Drive, MS 3135
Westford, MA 01886
978-589-0524





From owner-disman@dorothy.bmc.com  Thu Aug 29 18:17:38 2002
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13348
	for <disman-archive@lists.ietf.org>; Thu, 29 Aug 2002 18:17:37 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7TMKst04935;
	Thu, 29 Aug 2002 17:20:55 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA19590
	for disman-list; Thu, 29 Aug 2002 15:12:46 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA19584
	for disman@dorothy.bmc.com; Thu, 29 Aug 2002 15:12:42 -0700 (PDT)
Date: Thu, 29 Aug 2002 15:12:42 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208292212.PAA19584@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re:  Event MIB mteTriggerEnabled
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Hi -

> Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C0274F6AE@UNIWEST1>
> From: "Sajedi, Mohammad" <msajedi@juniper.net>
> To: "'disman@dorothy.bmc.com'" <disman@dorothy.bmc.com>
> Subject: Event MIB mteTriggerEnabled
> Date: Thu, 29 Aug 2002 10:44:33 -0400
> List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
> 
> What is the difference between (mteTriggerEnabled = false) and
> (mteTriggerEntryStatus = notInService)?
> I think they are the same and the mteTriggerEnabled object is redundant.
...

See the thread "RFC 2981 (disman event MIB) Implementation
Experience" in the disman WG archives for November 8th, 2001.
ftp://amethyst.bmc.com/pub/disman/archives/2001-11

Or, read the RowStatus textual convention's definition
to see the side-effects of setting something to "notInService".

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


From owner-disman@dorothy.bmc.com  Fri Aug 30 07:52:12 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12462
	for <disman-archive@lists.ietf.org>; Fri, 30 Aug 2002 07:52:12 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7UBuuU06329;
	Fri, 30 Aug 2002 06:57:01 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA22623
	for disman-list; Fri, 30 Aug 2002 04:49:11 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id EAA22618
	for <disman@dorothy.bmc.com>; Fri, 30 Aug 2002 04:48:46 -0700 (PDT)
Received: from mx-us-hou-2-int.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.10.2) with ESMTP id g7UBjHP20503
	for <disman@dorothy.bmc.com>; Fri, 30 Aug 2002 06:45:18 -0500 (CDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id D9EB61FF104
	for <disman@dorothy.bmc.com>; Fri, 30 Aug 2002 06:50:10 -0500 (CDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11989;
	Fri, 30 Aug 2002 07:48:29 -0400 (EDT)
Message-Id: <200208301148.HAA11989@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@dorothy.bmc.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-disman-alarm-mib-08.txt
Date: Fri, 30 Aug 2002 07:48:28 -0400
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>



--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Management Working Group of the IETF.

	Title		: Alarm MIB
	Author(s)	: S. Chisholm, D. Romascanu
	Filename	: draft-ietf-disman-alarm-mib-08.txt
	Pages		: 65
	Date		: 2002-8-29
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes management objects used for defining
and storing alarms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-08.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-disman-alarm-mib-08.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-disman-alarm-mib-08.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"



--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2002-8-29142059.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-alarm-mib-08.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-alarm-mib-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2002-8-29142059.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-disman@dorothy.bmc.com  Fri Aug 30 14:17:25 2002
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28957
	for <disman-archive@lists.ietf.org>; Fri, 30 Aug 2002 14:17:25 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g7UIMQE04074;
	Fri, 30 Aug 2002 13:22:27 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA23733
	for disman-list; Fri, 30 Aug 2002 11:15:02 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA23727
	for disman@dorothy.bmc.com; Fri, 30 Aug 2002 11:14:58 -0700 (PDT)
Date: Fri, 30 Aug 2002 11:14:58 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200208301814.LAA23727@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re:  Event MIB mteTriggerEnabled
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Hi -

> Message-ID: <20020830131100.47014.qmail@web12102.mail.yahoo.com>
> Date: Fri, 30 Aug 2002 06:11:00 -0700 (PDT)
> From: Mohammad Sajedi <msajedi@yahoo.com>
> Subject: Re:  Event MIB mteTriggerEnabled
> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
> In-Reply-To: <200208292212.PAA19584@dorothy.bmc.com>
> 
> you are correct. But the way the definition of row
> status reads "Once made active an entry may not be
> modified except to delete it".

Not the definition of RowStatus.
See Column "D" in the table on page 9 of RFC 2579,
which specifies what can be done with an RowStatus
value of "active".

> How the value of mteTriggerEnabled can be changed
> after row status is set to active? I thought we want
> to toggle the mteTriggerEnabled value to true and
> false.
...

The description of mteTriggerEntryStatus was fixed in
<draft-ietf-disman-event-mib-v2-00.txt>

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


