headers
Randy Presuhn | 2 Aug 2002 01:01
Picon

consolidated disman WG minutes from Yokohama

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 <at> bmc.com>  The minutes on Tuesday,
July 16th were taken by Niraj Gopal <niraj <at> cisco.com> and on
Thursday, July 18th by Chris Elliott <chelliot <at> cisco.com>

DISMAN WG Meeting minutes
Date : 07/16/2002
Time : 1545-1645
Room Number : 304
Reported by : Niraj Gopal (niraj <at> 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.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Wijnen, Bert (Bert | 2 Aug 2002 11:50
Picon
Favicon

RE: consolidated disman WG minutes from Yokohama

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 <at> ops.ietf.org
mailing list.

Bert
Permalink | Reply | 0 comments |
headers
Randy Presuhn | 2 Aug 2002 19:43
Picon

RE: consolidated disman WG minutes from Yokohama

Hi -

I've sent in the correction.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn <at> 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 <at> dorothy.bmc.com Fri Aug  2 02:49:47 PDT 2002
> Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E9389BB <at> nl0006exch003u.nl.lucent.com>
> From: "Wijnen, Bert (Bert)" <bwijnen <at> lucent.com>
> To: Randy Presuhn <rpresuhn <at> dorothy.bmc.com>
> Cc: disman <at> 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,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Presuhn | 2 Aug 2002 19:43
Picon

Re: consolidated disman WG minutes from Yokohama

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 <at> bmc.com>  The minutes on Tuesday,
July 16th were taken by Niraj Gopal <niraj <at> cisco.com> and on
Thursday, July 18th by Chris Elliott <chelliot <at> cisco.com>

DISMAN WG Meeting minutes
Date : 07/16/2002
Time : 1545-1645
Room Number : 304
Reported by : Niraj Gopal (niraj <at> 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
(Continue reading)

Permalink | Reply | 2 comments |
headers
Randy Presuhn | 2 Aug 2002 20:40
Picon

more synthetic objects

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 <at> bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------
Permalink | Reply | 0 comments |
headers
Niraj Gopal | 5 Aug 2002 07:05
Picon
Favicon

MIB table modifications tracking MIB discussion...

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?
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Presuhn | 6 Aug 2002 02:05
Picon

Re: MIB table modifications tracking MIB discussion...

Hi -

> Message-Id: <4.3.2.7.2.20020804204059.03ee9cd8 <at> mira-linc3-1.cisco.com>
> Date: Sun, 04 Aug 2002 22:05:12 -0700
> To: disman <at> dorothy.bmc.com
> From: Niraj Gopal <niraj <at> cisco.com>
> Subject: MIB table modifications tracking MIB discussion...
> Cc: Niraj Gopal <niraj <at> 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.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Lam, Hing-Kam (Kam | 6 Aug 2002 17:57
Picon
Favicon

Actiuon items from ARC discussion

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.
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Niraj Gopal | 6 Aug 2002 18:57
Picon
Favicon

Re: MIB table modifications tracking MIB discussion...

At 05:05 PM 8/5/2002 -0700, Randy Presuhn wrote:
>Hi -
>
> > Message-Id: <4.3.2.7.2.20020804204059.03ee9cd8 <at> mira-linc3-1.cisco.com>
> > Date: Sun, 04 Aug 2002 22:05:12 -0700
> > To: disman <at> dorothy.bmc.com
> > From: Niraj Gopal <niraj <at> cisco.com>
> > Subject: MIB table modifications tracking MIB discussion...
> > Cc: Niraj Gopal <niraj <at> 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.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Presuhn | 6 Aug 2002 20:31
Picon

Re: referential integrity across reboots

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 <at> bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------
Permalink | Reply | 2 comments |

Gmane