From owner-disman@dorothy.bmc.com  Mon Jun  3 07:35: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 HAA08191
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 07:35:26 -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 g53BXX927953;
	Mon, 3 Jun 2002 06:33:33 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA15526
	for disman-list; Mon, 3 Jun 2002 04:24:55 -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 EAA15521
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 04:24:52 -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 g53BMG110966
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 06:22:16 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (unknown [47.129.242.56])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id D210720EFCD
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 06:26:28 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g53BQHF18953
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 07:26:17 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYB3KDM>; Mon, 3 Jun 2002 07:26:18 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403878935@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #26, 27
Date: Mon, 3 Jun 2002 07:26:11 -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

Randy said individual, but to conserve email, I figured I'd double
up some of the more benign open issues.

Alarm #26 Extensibility of alarmActiveEntry
  "In the overview, it would be nice to add a description regarding the
  extensibility of
  the AlarmActiveEntry.  I think this is an important feature."
  Solution:
  Add text to section 4.1.1 explaining that more information can be
  stored for an active alarm by defining a table extension of
alarmActiveEntry.

Alarm #27 Resource Type
  "Section 4.1.4, it is not clear to me how it can be know what type of
  resource the alarm
  is for.  It would be nice to have a description of this."
  Solution: 
  Add text explaining that the consumer of the resourceID does
  not necessarily need to know the type of the resource in the resource ID,
  but if they want to know this, it can be derived by examining the content
  of the resource ID - 1.3.6.1.2.1.2.2.1.1.something is an interface for
  example.

Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Mon Jun  3 07:37:13 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 HAA08229
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 07:37: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 g53BeQw00084;
	Mon, 3 Jun 2002 06:40:26 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA15546
	for disman-list; Mon, 3 Jun 2002 04:34:22 -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 EAA15541
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 04:34:19 -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 g53BVgm14642
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 06:31:42 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (unknown [47.129.242.56])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 7B6BD20EF95
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 06:35:55 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g53BZiF19146
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 07:35:44 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYB3KFN>; Mon, 3 Jun 2002 07:35:45 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD340387893A@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #31, #33, #44 - Probable Causes
Date: Mon, 3 Jun 2002 07:35:39 -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 following are all related to Probable Causes:

Alarm #31 Duplicate Probable causes
  Solution:
    remove: fireDetected (266)
            floodDetected (267)
            configurationOrCustomizationError(260)
            underlyingResourceUnavailable(287)
  and possibly 
  toxicGas (133) & toxicLeakDetected (286)

Alarm #44 Probable Cause corrections from ITU Study group 4

  Solution: Currently the reserved space for ITU values is < 255.
            Increase this to 1024, to allow more ITU defined values.

            Change text to clarify that "ITU probable cause values 
            for alarms are currently assigned as per M.3100-1995 (1-254), 
            X.733-1992 (256-287), and X.736-1992 (288-303)." 

            Add missing value 158 (reinitialized) 


Alarm #33 Disman Immortality
  Text in the IANA considerations section suggests we'll still be
  around for IETF 34523421, held in the Mars colonies.
  Solution:
  Change text to the following:
  "Over time, there will be a need to add new IANAItuProbableCause
   enumerated values for new probable causes. The Internet
   Assigned Number Authority (IANA) is responsible for the assignment of
   all Internet numbers, including various SNMP-related numbers, and
   specifically, new IANAItuProbableCause values. Values of 
   IANAItuProbableCause less than 255 are reserved for causes
   that correspond to ITU probable cause.

   The following shall be used as the initial values, but the latest
   values for these textual conventions should be obtained from IANA:"


Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Mon Jun  3 07:41: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 HAA08644
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 07:41: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 g53BiRY01302;
	Mon, 3 Jun 2002 06:44:28 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA15563
	for disman-list; Mon, 3 Jun 2002 04:38:26 -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 EAA15558
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 04:38:06 -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 g53BZU816282
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 06:35:30 -0500 (CDT)
Received: from ietf.org (unknown [132.151.1.176])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id BFD0D20EF82
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 06:39:42 -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 HAA08571;
	Mon, 3 Jun 2002 07:39:08 -0400 (EDT)
Message-Id: <200206031139.HAA08571@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@dorothy.bmc.com, eos@ops.ietf.org, snmpv3@lists.tislabs.com
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-presuhn-nmwebdav-00.txt
Date: Mon, 03 Jun 2002 07:39:07 -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.


	Title		: Applying WebDAV (Web Distributed Authoring and 
                          Versioning)to Network Configuration Management 
                          Problems
	Author(s)	: R. Presuhn
	Filename	: draft-presuhn-nmwebdav-00.txt
	Pages		: 12
	Date		: 31-May-02
	
This memo examines the potential of using WWW Distributed Authoring
and Versioning (WebDAV) technologies to address the problems of
network configuration management.  It reviews requirements and issues
that have been identified in IETF network configuration management
and operator requirements discussions, matching these requirements
and issues with various WebDAV facilities.  It concludes by
identifying areas for further exploration.
Comments are welcomed, both from the Operations and Management Area
in general, and from participants in the webdav and deltav working
groups in particular.  Please send comments to the author at
randy_presuhn@bmc.com.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-presuhn-nmwebdav-00.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-presuhn-nmwebdav-00.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-presuhn-nmwebdav-00.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:	<20020531143844.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-presuhn-nmwebdav-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-presuhn-nmwebdav-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--




From owner-disman@dorothy.bmc.com  Mon Jun  3 08: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 IAA09766
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 08:19: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 g53CMLe13524;
	Mon, 3 Jun 2002 07:22:22 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA15654
	for disman-list; Mon, 3 Jun 2002 05:16:19 -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 FAA15649
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 05:16:16 -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 g53CDdK01680
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 07:13:40 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (unknown [47.129.242.56])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id CA65920EFB1
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 07:17:52 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g53CHkF22187
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 08:17:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYB3K96>; Mon, 3 Jun 2002 08:17:47 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403878998@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #35, #36 - Varbinds to alarmActive Notification
Date: Mon, 3 Jun 2002 08:17:41 -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 following two are related to the varbinds of 
alarmActiveState.

Alarm #35 AlarmState Notification varbinds
  "While we're on the topic of these two notifications, I
   think that alarmActiveResourceId is not particularly useful
   without alarmActiveContextName, alarmActiveEngineAddressType,
   alarmActiveEngineAddress, and alarmActiveEngineID."  

  Solution: Solutions interested in being able
  to differentiate the source of the alarm by means other 
  than the source IP address and alarmActiveResourceId, 
  should create alarmListName such that each context/IP 
  pair is its own list

Alarm #36 Varbinds to alarmActiveState notifications
  Using explicit varbinds if model, state and name or using
  alarmActiveModelPointer
  Option 1) varbind alarmListName, alarmModelIndex, alarmModelState
  Option 2) varbind alarmActiveModelPointer  

Solution: Replace alarmModelIndex and alarmModelState 
  in alarmActiveState notification with alarmModelPointer.          


Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Mon Jun  3 08:58:20 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 IAA10716
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 08:58:19 -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 g53D0xL28576;
	Mon, 3 Jun 2002 08:00:59 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA15720
	for disman-list; Mon, 3 Jun 2002 05:54:21 -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 FAA15715
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 05:54:17 -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 g53CpdT20191
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 07:51:39 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (unknown [47.129.242.56])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 82E3D20EFCD
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 07:55:52 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g53CtjF24442
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 08:55:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYB3L5B>; Mon, 3 Jun 2002 08:55:46 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403878A50@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #41, #47 - listName, security & Ascii Art
Date: Mon, 3 Jun 2002 08:55:40 -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

Alarm #41 Example of listName use is required
  Solution:
    Incorporate Randy's suggested text for alarm #47
    Add some additional clarifying text as required.

Alarm #47 Security Issues, ASCII Art Changes
   Solution:
     Use Randy's updated ASCII art and suggested text changes. 


Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Mon Jun  3 09:14:29 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 JAA11377
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 09:14:28 -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 g53DHL505000;
	Mon, 3 Jun 2002 08:17:21 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id GAA15907
	for disman-list; Mon, 3 Jun 2002 06:11:19 -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 GAA15902
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 06:11:16 -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 g53D8d328147
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 08:08:39 -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 3BF831FF034
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 08:12:52 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g53DCPl15882
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 09:12:25 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYB3MMX>; Mon, 3 Jun 2002 09:12:26 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403878AB2@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #39, #48 - Minor Edits
Date: Mon, 3 Jun 2002 09:12:15 -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

Alarm #39 Description of alarmActiveVariableTable
  Should this table be renamed to alarmActiveVarbindTable?

  Solution: No, probably not.

Alarm #48 Mechanical/Editorial Update
  48.1 The copyright notice between the "Status of this Memo" and
  the "Abstract" sections is missing.
  48.2 Since this is the product of the working group, it would be
  good to include the working group mailing list in the
  CONTACT-INFO.
  48.3 the "Intellectual Property" section (per RFC 2026 clause 10.4,
  especially (D)) is missing.
  48.4 In the security considerations, the "sensitive" objects should
  be listed.
  48.5 The title of section 8 should probably be "Authors' Addresses",
  unless Sharon and Dan are moving in together.  :-)  A phone
  number for Sharon would also be nice.
  48.6 the "References" section should be split into normative
  and non-normative references, per
  draft-rfc-editor-rfc2223bis-02.txt
  48.7 The Copyright date (section 11) needs to be adjusted.

  Solution: Make these changes.

Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Mon Jun  3 10:21:04 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 KAA14892
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 10:21: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 g53ENq501933;
	Mon, 3 Jun 2002 09:23:52 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id HAA16031
	for disman-list; Mon, 3 Jun 2002 07:17:29 -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 HAA16026
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 07:17:15 -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 g53EEd001990
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 09:14:39 -0500 (CDT)
Received: from ihemail1.firewall.lucent.com (unknown [192.11.222.161])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 8721520EF94
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 09:18:47 -0500 (CDT)
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g53EIeM18837
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 10:18:41 -0400 (EDT)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <K9DF50MB>; Mon, 3 Jun 2002 10:18:40 -0400
Message-ID: <2E12619580C0D1118C6400805F9F4C950D7CF0E7@nj7460exch001u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: disman@dorothy.bmc.com,
        "'atommib@research.telcordia.com'" <atommib@research.telcordia.com>
Subject: RE: Closing out alarm/arc issues
Date: Mon, 3 Jun 2002 10:18:36 -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,

For the ARC MIB (draft-ietf-disman-conditionmib-02.txt), no open issues have been identified. If you see differently, please raise the issue.

Note that draft-ietf-disman-conditionmib-02.txt now contains only the ARC MIB. The Condition MIB is no longer in -02.

For the Condition MIB module, which was contained in the previous version -01 (i.e., draft-ietf-disman-conditionmib-01.txt), the open issue is its relationship with the Alarm MIB. However, unless someone wants to continue the Condition MIB module, otherwise the issue will be dropped along with the Condition MIB module.

Regards,
Kam

> -----Original Message-----
> From: Randy Presuhn [mailto:rpresuhn@dorothy.bmc.com]
> Sent: Friday, May 31, 2002 5:17 PM
> To: disman@dorothy.bmc.com
> Subject: Closing out alarm/arc issues
> 
> 
> Hi -
> 
> I've asked the editors of our alarm-related documents
> to re-post their open issues one-by-one, with proposed
> resolutions.  In each case, if no objections are raised within
> one week of the posting, I will declare consensus so we can
> finish this work and move on.
> 
>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  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  Mon Jun  3 14:54: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 OAA27483
	for <disman-archive@odin.ietf.org>; Mon, 3 Jun 2002 14:54:26 -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 g53Ivcx23825;
	Mon, 3 Jun 2002 13:57:38 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA16469
	for disman-list; Mon, 3 Jun 2002 11:51:08 -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 LAA16464
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 11:51:05 -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 g53ImSA00275
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 13:48:28 -0500 (CDT)
Received: from riverstonenet.com (unknown [63.113.148.10])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 585AC20EFDC
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 13:52:19 -0500 (CDT)
Received: from dperkins-nb2.dsperkins.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id LAA06010; Mon, 3 Jun 2002 11:52:18 -0700 (PDT)
Message-Id: <5.1.0.14.2.20020603115043.02d42c50@mail4.bayarea.net>
X-Sender: dperkins@mail4.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 03 Jun 2002 11:51:29 -0700
To: disman@dorothy.bmc.com
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: Disman in Yokohama?
In-Reply-To: <200205301946.MAA03561@dorothy.bmc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>

HI,

I believe so....

At 12:46 PM 5/30/2002 -0700, Randy Presuhn wrote:
>Hi -
>
>This list has been really quiet.  Is it going to take a
>face-to-face meeting in Yokohama to finish the items on
>our collective plate?
>
> ------------------------------------------------------
> Randy Presuhn          BMC Software, Inc.  1-3141

Regards,
/david t. perkins



From owner-disman@dorothy.bmc.com  Wed Jun  5 23:24:23 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 XAA11415
	for <disman-archive@lists.ietf.org>; Wed, 5 Jun 2002 23:24:22 -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 g563RRd29607;
	Wed, 5 Jun 2002 22:27:27 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id UAA22855
	for disman-list; Wed, 5 Jun 2002 20:18:21 -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 FAA15699
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 05:52:17 -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 g53CneL19121
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 07:49:40 -0500 (CDT)
Received: from zcars04f.ca.nortel.com (unknown [47.129.242.57])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 51EF920EFC1
	for <disman@dorothy.bmc.com>; Mon,  3 Jun 2002 07:53:53 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g53Crkl14237
	for <disman@dorothy.bmc.com>; Mon, 3 Jun 2002 08:53:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYB3LYG>; Mon, 3 Jun 2002 08:53:47 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403878A3E@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #38, #43 - trap/notification varbind and timestamps
Date: Mon, 3 Jun 2002 08:53:41 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C20AFD.AFFC8BC4"
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C20AFD.AFFC8BC4
Content-Type: text/plain;
	charset="iso-8859-1"

hi

Since potentially always treating notification varbinds like
they are NOTIFICATION-TYPE in #38 is related to the always
storing varbinds as if they are from notifications, as appose
to v1 traps, in #43, I've grouped these two:

Alarm #38 Description of object alarmModelVarbindIndex 
  Option 1) Change "For SNMPv1 traps, a 1 indicates the first varbind. For
  NOTIFICATION-TYPE," to "For v1Traps,For v2Traps and Informs, a 1 indicates
  the first varbind. ". 
  Option 2) Alternatively, always treat it like v2 traps

  Solution: For consistency with #43 and to comply with the
  philosophy of 2576, notifications, regardless of the protocol
  will be treated *as though* they were NOTIFICATION-TYPE. We still
  need to provide guidance of how to use this with v1 traps, as
  well as indicate whether an index of 3 is the third varbind in the
  notification on the wire, or as defined in the SMI. Therefore, the
  the text from option 1) still applies:

   "For SNMPv1 traps, a 1 indicates the first varbind. For
         v2Traps and Informs, a 1 indicates the first real varbind
         after the required varbinds of sysUptime and SNMPTrapOID.".

Alarm #43 Timestamp Description & Do we need two timestamps
  Change text to:
  'The time that the error information was added to the alarm table. 
  The time when the error occurred may be retrieved from a different 
  source, e.g. from the variable bindings of the notification if a 
  distributed system using notifications for alarm generation is 
  being implemented'.
  Does this then require sysUptime and trapOID to be stored in 
    alarmActiveVariableTable, even for v1 traps?
 
  Solution: Change text as described above. Always store notifications
    as if they are NOTIFICATION-TYPE/v2 traps/informs.

Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario

------_=_NextPart_001_01C20AFD.AFFC8BC4
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>Alarm #38, #43 - trap/notification varbind and timestamps</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>hi</FONT>
</P>

<P><FONT SIZE=2>Since potentially always treating notification varbinds like</FONT>
<BR><FONT SIZE=2>they are NOTIFICATION-TYPE in #38 is related to the always</FONT>
<BR><FONT SIZE=2>storing varbinds as if they are from notifications, as appose</FONT>
<BR><FONT SIZE=2>to v1 traps, in #43, I've grouped these two:</FONT>
</P>

<P><FONT SIZE=2>Alarm #38 Description of object alarmModelVarbindIndex </FONT>
<BR><FONT SIZE=2>&nbsp; Option 1) Change &quot;For SNMPv1 traps, a 1 indicates the first varbind. For</FONT>
<BR><FONT SIZE=2>&nbsp; NOTIFICATION-TYPE,&quot; to &quot;For v1Traps,For v2Traps and Informs, a 1 indicates</FONT>
<BR><FONT SIZE=2>&nbsp; the first varbind. &quot;. </FONT>
<BR><FONT SIZE=2>&nbsp; Option 2) Alternatively, always treat it like v2 traps</FONT>
</P>

<P><FONT SIZE=2>&nbsp; Solution: For consistency with #43 and to comply with the</FONT>
<BR><FONT SIZE=2>&nbsp; philosophy of 2576, notifications, regardless of the protocol</FONT>
<BR><FONT SIZE=2>&nbsp; will be treated *as though* they were NOTIFICATION-TYPE. We still</FONT>
<BR><FONT SIZE=2>&nbsp; need to provide guidance of how to use this with v1 traps, as</FONT>
<BR><FONT SIZE=2>&nbsp; well as indicate whether an index of 3 is the third varbind in the</FONT>
<BR><FONT SIZE=2>&nbsp; notification on the wire, or as defined in the SMI. Therefore, the</FONT>
<BR><FONT SIZE=2>&nbsp; the text from option 1) still applies:</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp; &quot;For SNMPv1 traps, a 1 indicates the first varbind. For</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; v2Traps and Informs, a 1 indicates the first real varbind</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; after the required varbinds of sysUptime and SNMPTrapOID.&quot;.</FONT>
</P>

<P><FONT SIZE=2>Alarm #43 Timestamp Description &amp; Do we need two timestamps</FONT>
<BR><FONT SIZE=2>&nbsp; Change text to:</FONT>
<BR><FONT SIZE=2>&nbsp; 'The time that the error information was added to the alarm table. </FONT>
<BR><FONT SIZE=2>&nbsp; The time when the error occurred may be retrieved from a different </FONT>
<BR><FONT SIZE=2>&nbsp; source, e.g. from the variable bindings of the notification if a </FONT>
<BR><FONT SIZE=2>&nbsp; distributed system using notifications for alarm generation is </FONT>
<BR><FONT SIZE=2>&nbsp; being implemented'.</FONT>
<BR><FONT SIZE=2>&nbsp; Does this then require sysUptime and trapOID to be stored in </FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; alarmActiveVariableTable, even for v1 traps?</FONT>
<BR><FONT SIZE=2>&nbsp;</FONT>
<BR><FONT SIZE=2>&nbsp; Solution: Change text as described above. Always store notifications</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; as if they are NOTIFICATION-TYPE/v2 traps/informs.</FONT>
</P>

<P><FONT SIZE=2>Sharon Chisholm</FONT>
<BR><FONT SIZE=2>Preside Management</FONT>
<BR><FONT SIZE=2>Nortel Networks</FONT>
<BR><FONT SIZE=2>Ottawa, Ontario</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C20AFD.AFFC8BC4--




From owner-disman@dorothy.bmc.com  Tue Jun 11 18:18:14 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 SAA14893
	for <disman-archive@lists.ietf.org>; Tue, 11 Jun 2002 18:18: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 g5BMLNX27411;
	Tue, 11 Jun 2002 17:21:23 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA23878
	for disman-list; Tue, 11 Jun 2002 15:12:18 -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 PAA23873
	for <disman@dorothy.bmc.com>; Tue, 11 Jun 2002 15:12:14 -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 g5BM9XT05015
	for <disman@dorothy.bmc.com>; Tue, 11 Jun 2002 17:09:33 -0500 (CDT)
Received: from inf.ufpr.br (unknown [200.17.212.164])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id A98A520EFD0
	for <disman@dorothy.bmc.com>; Tue, 11 Jun 2002 17:13:50 -0500 (CDT)
Received: (qmail 12036 invoked from network); 11 Jun 2002 22:13:49 -0000
Received: from giselda.inf.ufpr.br (elias@200.17.212.179)
  by caco.inf.ufpr.br with SMTP; 11 Jun 2002 22:13:49 -0000
Received: by giselda.inf.ufpr.br (sSMTP sendmail emulation); Tue, 11 Jun 2002 19:17:37 -0300
From: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>
Subject: only 2 remaining goals, is disman dying?
To: disman@dorothy.bmc.com
Date: Tue, 11 Jun 2002 19:17:37 -0300 (BRT)
Cc: "Elias Procopio Duarte Jr." <elias@mx-us-hou-1-int.bmc.com>
X-Mailer: ELM [version 2.4ME+ PL66 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20020611221350.A98A520EFD0@mx-us-hou-1-int.bmc.com>
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,

Distributed management is a truly broad field, and disman has currently
only two remaining goals... Actually so much has been done in the past, 
and now the list is so quiet, and there are nearly no new developments...

As quoted from the WG page: "It is recognized that the scope of this
working group is narrow relative to the potential in the area of distributed
network management. This is intentional in order to increase the likelihood of
producing useful, quality specifications in a timely manner."

We think this has been accomplished in the past.
But perhaps this is time start new developments in order to keep the WG
alive?
We offer you the Replication MIB as a possible new goal for new developments
in the same Working Group.

We have a new revised version of the Clustering/Replication MIB, 
and are looking forward to a disman WG meeting in Yokohama.

The document is available at:
http://www.inf.ufpr.br/~aldri/draft/replicationmib/index.html

The proposed approach, as presented in Salt Lake City, is a 3-tier
architecture for dependable monitoring by replicating managed objects
in middle-layer managers called clusters.

Replication is a key component of distributed systems, it can enhance
both the availability and performance impact of monitoring. Using the
proposed approach, a managed object is accessible, through the regular
MIB interface, even when the agent/network element is down.  By using
the Replication MIB together with the Expression MIB and Event MIB we
have a powerful approach for managing objects from agents distributed
throughout the network.

We are looking forward to hearing from you,

Sincerely,

Elias 


From owner-disman@dorothy.bmc.com  Wed Jun 12 02:10:50 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 CAA04452
	for <disman-archive@odin.ietf.org>; Wed, 12 Jun 2002 02:10: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 g5C6EU526834;
	Wed, 12 Jun 2002 01:14:30 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id XAA24963
	for disman-list; Tue, 11 Jun 2002 23:08:05 -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 XAA24956
	for <disman@dorothy.bmc.com>; Tue, 11 Jun 2002 23:07:58 -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 g5C65Iu00445
	for <disman@dorothy.bmc.com>; Wed, 12 Jun 2002 01:05:18 -0500 (CDT)
Received: from ierw.net.avaya.com (unknown [198.152.13.101])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id CCE6120EFD1
	for <disman@dorothy.bmc.com>; Wed, 12 Jun 2002 01:09:35 -0500 (CDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id CAA07761
	for <disman@dorothy.bmc.com>; Wed, 12 Jun 2002 02:07:44 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id CAA07755
	for <disman@dorothy.bmc.com>; Wed, 12 Jun 2002 02:07:43 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: only 2 remaining goals, is disman dying?
Date: Wed, 12 Jun 2002 09:06:54 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F017B7255@IS0004AVEXU1.global.avaya.com>
Thread-Topic: only 2 remaining goals, is disman dying?
Thread-Index: AcIRlbxFK2rRBAdLQhez1ip2CNOdaAAPCUdA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>, <disman@dorothy.bmc.com>
Cc: "Elias Procopio Duarte Jr." <elias@mx-us-hou-1-int.bmc.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id XAA24957
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Elias,

I am not sure that 'keeping alive' a working group is really the goal that we should follow. If there is relevant new work to do, we can certainly ask for re-Charter, otherwise there is nothing bad in declaring victory, entering in maintenance mode and leaving the scene open for other IETF activities.

Concerning the Replication MIB, I think that there is merit in what you propose, but we need to define clearly the problem that we want to solve. A more generic problem of synchronization and replication of distributed data bases seems to be hidden between what you suggest. we need to understand if this is something we want to tackle, and if yes review the range of solutions that might be available for this problem.

Also, did you submit this draft? I could not find it in the Internet-Drafts repository.

Regards,

Dan

> -----Original Message-----
> From: Elias Procopio Duarte Jr. [mailto:elias@inf.ufpr.br]
> Sent: Wednesday, June 12, 2002 1:18 AM
> To: disman@dorothy.bmc.com
> Cc: Elias Procopio Duarte Jr.
> Subject: only 2 remaining goals, is disman dying?
> 
> 
> Hi,
> 
> Distributed management is a truly broad field, and disman has 
> currently
> only two remaining goals... Actually so much has been done in 
> the past, 
> and now the list is so quiet, and there are nearly no new 
> developments...
> 
> As quoted from the WG page: "It is recognized that the scope of this
> working group is narrow relative to the potential in the area 
> of distributed
> network management. This is intentional in order to increase 
> the likelihood of
> producing useful, quality specifications in a timely manner."
> 
> We think this has been accomplished in the past.
> But perhaps this is time start new developments in order to 
> keep the WG
> alive?
> We offer you the Replication MIB as a possible new goal for 
> new developments
> in the same Working Group.
> 
> We have a new revised version of the Clustering/Replication MIB, 
> and are looking forward to a disman WG meeting in Yokohama.
> 
> The document is available at:
> http://www.inf.ufpr.br/~aldri/draft/replicationmib/index.html
> 
> The proposed approach, as presented in Salt Lake City, is a 3-tier
> architecture for dependable monitoring by replicating managed objects
> in middle-layer managers called clusters.
> 
> Replication is a key component of distributed systems, it can enhance
> both the availability and performance impact of monitoring. Using the
> proposed approach, a managed object is accessible, through the regular
> MIB interface, even when the agent/network element is down.  By using
> the Replication MIB together with the Expression MIB and Event MIB we
> have a powerful approach for managing objects from agents distributed
> throughout the network.
> 
> We are looking forward to hearing from you,
> 
> Sincerely,
> 
> Elias 
> 


From owner-disman@dorothy.bmc.com  Fri Jun 14 12:46:55 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 MAA05918
	for <disman-archive@lists.ietf.org>; Fri, 14 Jun 2002 12:46:54 -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 g5EGnPS24178;
	Fri, 14 Jun 2002 11:49:25 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id JAA04065
	for disman-list; Fri, 14 Jun 2002 09:37:52 -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 KAA01183
	for <disman@dorothy.bmc.com>; Thu, 13 Jun 2002 10:17:26 -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 g5DHEfF07393
	for <disman@dorothy.bmc.com>; Thu, 13 Jun 2002 12:14:42 -0500 (CDT)
Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 922611FF019
	for <disman@dorothy.bmc.com>; Thu, 13 Jun 2002 12:18:59 -0500 (CDT)
Received: (qmail 1027 invoked from network); 13 Jun 2002 17:18:46 -0000
Received: from usermg35.uk.uudial.com (HELO tom3) (62.188.122.21)
  by smtp-2.dial.pipex.com with SMTP; 13 Jun 2002 17:18:46 -0000
Message-ID: <00ee01c212fe$04af84c0$0301a8c0@tom3>
Reply-To: "Tom Petch" <nwnetworks@dial.pipex.com>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, <disman@dorothy.bmc.com>
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
Date: Thu, 13 Jun 2002 18:14:52 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00E4_01C21306.36865520"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>



This is a multi-part message in MIME format.

------=_NextPart_000_00E4_01C21306.36865520
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I believe the same index should retrieve the same value, regardless of =
v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It is simple., it =
is logical.  But I am not clear from the text if that is an option you =
are offering me  !
Tom Petch, Network Consultant
nwnetworks@dial.pipex.com
    -----Original Message-----
    From: Sharon Chisholm <schishol@nortelnetworks.com>
    To: disman@dorothy.bmc.com <disman@dorothy.bmc.com>
    Date: 06 June 2002 04:22
    Subject: Alarm #38, #43 - trap/notification varbind and timestamps
   =20
   =20
    hi=20

    Since potentially always treating notification varbinds like=20
    they are NOTIFICATION-TYPE in #38 is related to the always=20
    storing varbinds as if they are from notifications, as appose=20
    to v1 traps, in #43, I've grouped these two:=20

    Alarm #38 Description of object alarmModelVarbindIndex=20
      Option 1) Change "For SNMPv1 traps, a 1 indicates the first =
varbind. For=20
      NOTIFICATION-TYPE," to "For v1Traps,For v2Traps and Informs, a 1 =
indicates=20
      the first varbind. ".=20
      Option 2) Alternatively, always treat it like v2 traps=20

      Solution: For consistency with #43 and to comply with the=20
      philosophy of 2576, notifications, regardless of the protocol=20
      will be treated *as though* they were NOTIFICATION-TYPE. We still=20
      need to provide guidance of how to use this with v1 traps, as=20
      well as indicate whether an index of 3 is the third varbind in the =

      notification on the wire, or as defined in the SMI. Therefore, the =

      the text from option 1) still applies:=20

       "For SNMPv1 traps, a 1 indicates the first varbind. For=20
             v2Traps and Informs, a 1 indicates the first real varbind=20
             after the required varbinds of sysUptime and SNMPTrapOID.". =


    Alarm #43 Timestamp Description & Do we need two timestamps=20
      Change text to:=20
      'The time that the error information was added to the alarm table. =

      The time when the error occurred may be retrieved from a different =

      source, e.g. from the variable bindings of the notification if a=20
      distributed system using notifications for alarm generation is=20
      being implemented'.=20
      Does this then require sysUptime and trapOID to be stored in=20
        alarmActiveVariableTable, even for v1 traps?=20
     =20
      Solution: Change text as described above. Always store =
notifications=20
        as if they are NOTIFICATION-TYPE/v2 traps/informs.=20

    Sharon Chisholm=20
    Preside Management=20
    Nortel Networks=20
    Ottawa, Ontario=20


------=_NextPart_000_00E4_01C21306.36865520
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type><TITLE>Alarm #38, #43 - trap/notification =
varbind and timestamps</TITLE><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
3.2//EN">
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>I believe the same index should =
retrieve the=20
same value, regardless of v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID =

etc.&nbsp; It is simple., it is logical.&nbsp; But I am not clear from =
the text=20
if that is an option you are offering me&nbsp; !</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2>Tom Petch, Network Consultant<BR><A=20
href=3D"mailto:nwnetworks@dial.pipex.com">nwnetworks@dial.pipex.com</A></=
FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: =
5px">
    <DIV><FONT face=3DArial size=3D2><B>-----Original =
Message-----</B><BR><B>From:=20
    </B>Sharon Chisholm &lt;<A=20
    =
href=3D"mailto:schishol@nortelnetworks.com">schishol@nortelnetworks.com</=
A>&gt;<BR><B>To:=20
    </B><A =
href=3D"mailto:disman@dorothy.bmc.com">disman@dorothy.bmc.com</A>=20
    &lt;<A=20
    =
href=3D"mailto:disman@dorothy.bmc.com">disman@dorothy.bmc.com</A>&gt;<BR>=
<B>Date:=20
    </B>06 June 2002 04:22<BR><B>Subject: </B>Alarm #38, #43 - =
trap/notification=20
    varbind and timestamps<BR><BR></DIV></FONT>
    <P><FONT size=3D2>hi</FONT> </P>
    <P><FONT size=3D2>Since potentially always treating notification =
varbinds=20
    like</FONT> <BR><FONT size=3D2>they are NOTIFICATION-TYPE in #38 is =
related to=20
    the always</FONT> <BR><FONT size=3D2>storing varbinds as if they are =
from=20
    notifications, as appose</FONT> <BR><FONT size=3D2>to v1 traps, in =
#43, I've=20
    grouped these two:</FONT> </P>
    <P><FONT size=3D2>Alarm #38 Description of object =
alarmModelVarbindIndex=20
    </FONT><BR><FONT size=3D2>&nbsp; Option 1) Change &quot;For SNMPv1 =
traps, a 1=20
    indicates the first varbind. For</FONT> <BR><FONT size=3D2>&nbsp;=20
    NOTIFICATION-TYPE,&quot; to &quot;For v1Traps,For v2Traps and =
Informs, a 1=20
    indicates</FONT> <BR><FONT size=3D2>&nbsp; the first varbind. =
&quot;.=20
    </FONT><BR><FONT size=3D2>&nbsp; Option 2) Alternatively, always =
treat it like=20
    v2 traps</FONT> </P>
    <P><FONT size=3D2>&nbsp; Solution: For consistency with #43 and to =
comply with=20
    the</FONT> <BR><FONT size=3D2>&nbsp; philosophy of 2576, =
notifications,=20
    regardless of the protocol</FONT> <BR><FONT size=3D2>&nbsp; will be =
treated=20
    *as though* they were NOTIFICATION-TYPE. We still</FONT> <BR><FONT=20
    size=3D2>&nbsp; need to provide guidance of how to use this with v1 =
traps,=20
    as</FONT> <BR><FONT size=3D2>&nbsp; well as indicate whether an =
index of 3 is=20
    the third varbind in the</FONT> <BR><FONT size=3D2>&nbsp; =
notification on the=20
    wire, or as defined in the SMI. Therefore, the</FONT> <BR><FONT=20
    size=3D2>&nbsp; the text from option 1) still applies:</FONT> </P>
    <P><FONT size=3D2>&nbsp;&nbsp; &quot;For SNMPv1 traps, a 1 indicates =
the first=20
    varbind. For</FONT> <BR><FONT=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; v2Traps =
and Informs,=20
    a 1 indicates the first real varbind</FONT> <BR><FONT=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; after the =
required=20
    varbinds of sysUptime and SNMPTrapOID.&quot;.</FONT> </P>
    <P><FONT size=3D2>Alarm #43 Timestamp Description &amp; Do we need =
two=20
    timestamps</FONT> <BR><FONT size=3D2>&nbsp; Change text to:</FONT> =
<BR><FONT=20
    size=3D2>&nbsp; 'The time that the error information was added to =
the alarm=20
    table. </FONT><BR><FONT size=3D2>&nbsp; The time when the error =
occurred may=20
    be retrieved from a different </FONT><BR><FONT size=3D2>&nbsp; =
source, e.g.=20
    from the variable bindings of the notification if a </FONT><BR><FONT =

    size=3D2>&nbsp; distributed system using notifications for alarm =
generation is=20
    </FONT><BR><FONT size=3D2>&nbsp; being implemented'.</FONT> =
<BR><FONT=20
    size=3D2>&nbsp; Does this then require sysUptime and trapOID to be =
stored in=20
    </FONT><BR><FONT size=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableTable, even=20
    for v1 traps?</FONT> <BR><FONT size=3D2>&nbsp;</FONT> <BR><FONT =
size=3D2>&nbsp;=20
    Solution: Change text as described above. Always store =
notifications</FONT>=20
    <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp; as if they are =
NOTIFICATION-TYPE/v2=20
    traps/informs.</FONT> </P>
    <P><FONT size=3D2>Sharon Chisholm</FONT> <BR><FONT size=3D2>Preside=20
    Management</FONT> <BR><FONT size=3D2>Nortel Networks</FONT> =
<BR><FONT=20
    size=3D2>Ottawa, Ontario</FONT> </P></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_00E4_01C21306.36865520--





From owner-disman@dorothy.bmc.com  Fri Jun 14 16:39:45 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 QAA14616
	for <disman-archive@lists.ietf.org>; Fri, 14 Jun 2002 16:39:45 -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 g5EKhBA26598;
	Fri, 14 Jun 2002 15:43:11 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA06879
	for disman-list; Fri, 14 Jun 2002 13:36:30 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA06873
	for disman@dorothy.bmc.com; Fri, 14 Jun 2002 13:36:27 -0700 (PDT)
Date: Fri, 14 Jun 2002 13:36:27 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206142036.NAA06873@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: yet another notification mechanism
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 -

Yet another notification protocol has surfaced.  See
draft-sibley-dist-vect-monit-protocol-00.txt

This is just an FYI; I am NOT suggesting that this be
included in our work.

 ------------------------------------------------------
 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 Jun 14 19:29:33 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 TAA19264
	for <disman-archive@odin.ietf.org>; Fri, 14 Jun 2002 19:29:33 -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 g5ENX8x23917;
	Fri, 14 Jun 2002 18:33:08 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA12402
	for disman-list; Fri, 14 Jun 2002 16:26:30 -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 QAA12397
	for <disman@dorothy.bmc.com>; Fri, 14 Jun 2002 16:26:25 -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 g5ENNiZ06313
	for <disman@dorothy.bmc.com>; Fri, 14 Jun 2002 18:23:44 -0500 (CDT)
Received: from inf.ufpr.br (unknown [200.17.212.164])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 57F9C20EF8A
	for <disman@dorothy.bmc.com>; Fri, 14 Jun 2002 18:28:02 -0500 (CDT)
Received: (qmail 16673 invoked from network); 14 Jun 2002 23:28:01 -0000
Received: from giselda.inf.ufpr.br (elias@200.17.212.179)
  by caco.inf.ufpr.br with SMTP; 14 Jun 2002 23:28:01 -0000
Received: by giselda.inf.ufpr.br (sSMTP sendmail emulation); Fri, 14 Jun 2002 20:32:38 -0300
From: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>
Subject: Re: only 2 remaining goals, is disman dying?
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F017B7255@IS0004AVEXU1.global.avaya.com>
 from "Romascanu, Dan (Dan)" at "Jun 12, 2002 09:06:54 am"
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Date: Fri, 14 Jun 2002 20:32:38 -0300 (BRT)
Cc: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>, disman@dorothy.bmc.com,
        "Elias Procopio Duarte Jr." <elias@mx-us-hou-1-int.bmc.com>
X-Mailer: ELM [version 2.4ME+ PL66 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20020614232802.57F9C20EF8A@mx-us-hou-1-int.bmc.com>
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Dan,

I agree with you, a WG is meaningless if there is no
significant/interesting work to be done. However IMHO distributed management
certainly presents many challenges and has a huge potential in terms of
practical/efficient/reliable solutions. I think it would be a pity to let
disman die at this point!

You can see the Replication MIB as a systematic approach for dependable
monitoring. Objects are kept at replicated cluster managers, where they can
be accessed via the regular MIB interface.

Synchronization is not really a problem in the proposed solution because
of the usage of semi-active replication, in which the order in which
replicated objects are updated is guaranteed by a _leader_, which is a
cluster manager selected for that purpose. This leader replicates objects in
so called peer clusters.

This presents a fault-tolerant approach for fault-monitoring, in the sense
that objects are available even when part of the agent at the network
element is down, or part of the cluster managers are down, or unreachable.

The current version of the draft is available at
http://www.inf.ufpr.br/~aldri/draft/replicationmib/index.html

We didn't submit it because of the uncertainty regarding disman meeting or
not in Yohohama...

Cheers,

Elias 


> Elias,
> 
> I am not sure that 'keeping alive' a working group is really the goal that we should follow. If there is relevant new work to do, we can certainly ask for re-Charter, otherwise there is nothing bad in declaring victory, entering in maintenance mode and leaving the scene open for other IETF activities.
> 
> Concerning the Replication MIB, I think that there is merit in what you propose, but we need to define clearly the problem that we want to solve. A more generic problem of synchronization and replication of distributed data bases seems to be hidden between what you suggest. we need to understand if this is something we want to tackle, and if yes review the range of solutions that might be available for this problem.
> 
> Also, did you submit this draft? I could not find it in the Internet-Drafts repository.
> 
> Regards,
> 
> Dan
> 
> > -----Original Message-----
> > From: Elias Procopio Duarte Jr. [mailto:elias@inf.ufpr.br]
> > Sent: Wednesday, June 12, 2002 1:18 AM
> > To: disman@dorothy.bmc.com
> > Cc: Elias Procopio Duarte Jr.
> > Subject: only 2 remaining goals, is disman dying?
> > 
> > 
> > Hi,
> > 
> > Distributed management is a truly broad field, and disman has 
> > currently
> > only two remaining goals... Actually so much has been done in 
> > the past, 
> > and now the list is so quiet, and there are nearly no new 
> > developments...
> > 
> > As quoted from the WG page: "It is recognized that the scope of this
> > working group is narrow relative to the potential in the area 
> > of distributed
> > network management. This is intentional in order to increase 
> > the likelihood of
> > producing useful, quality specifications in a timely manner."
> > 
> > We think this has been accomplished in the past.
> > But perhaps this is time start new developments in order to 
> > keep the WG
> > alive?
> > We offer you the Replication MIB as a possible new goal for 
> > new developments
> > in the same Working Group.
> > 
> > We have a new revised version of the Clustering/Replication MIB, 
> > and are looking forward to a disman WG meeting in Yokohama.
> > 
> > The document is available at:
> > http://www.inf.ufpr.br/~aldri/draft/replicationmib/index.html
> > 
> > The proposed approach, as presented in Salt Lake City, is a 3-tier
> > architecture for dependable monitoring by replicating managed objects
> > in middle-layer managers called clusters.
> > 
> > Replication is a key component of distributed systems, it can enhance
> > both the availability and performance impact of monitoring. Using the
> > proposed approach, a managed object is accessible, through the regular
> > MIB interface, even when the agent/network element is down.  By using
> > the Replication MIB together with the Expression MIB and Event MIB we
> > have a powerful approach for managing objects from agents distributed
> > throughout the network.
> > 
> > We are looking forward to hearing from you,
> > 
> > Sincerely,
> > 
> > Elias 
> > 
> 



From owner-disman@dorothy.bmc.com  Fri Jun 14 21:43:22 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 VAA21023
	for <disman-archive@odin.ietf.org>; Fri, 14 Jun 2002 21:43:22 -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 g5F1iUp01759;
	Fri, 14 Jun 2002 20:44:31 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA12822
	for disman-list; Fri, 14 Jun 2002 18:37:55 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA12816
	for disman@dorothy.bmc.com; Fri, 14 Jun 2002 18:37:52 -0700 (PDT)
Date: Fri, 14 Jun 2002 18:37:52 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206150137.SAA12816@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re: only 2 remaining goals, is disman dying?
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 -

> From: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>
> Subject: Re: only 2 remaining goals, is disman dying?
> In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F017B7255@IS0004AVEXU1.global.avaya.com>
>  from "Romascanu, Dan (Dan)" at "Jun 12, 2002 09:06:54 am"
> To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> Date: Fri, 14 Jun 2002 20:32:38 -0300 (BRT)
> Cc: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>, disman@dorothy.bmc.com,
>         "Elias Procopio Duarte Jr." <elias@mx-us-hou-1-int.bmc.com>
> Message-Id: <20020614232802.57F9C20EF8A@mx-us-hou-1-int.bmc.com>
...
> The current version of the draft is available at
> http://www.inf.ufpr.br/~aldri/draft/replicationmib/index.html
> 
> We didn't submit it because of the uncertainty regarding disman meeting or
> not in Yohohama...
...

The working group chair has some difficulty understanding
this reasoning.  Without an i-d, there probably won't be much
discussion on the mailing list.  Without significant interest
expressed on the mailing list, the WG chair is unlikely to
allocate time in a WG face-to-face meeting, particularly when
work on our existing deliverables remains.

 ------------------------------------------------------
 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 Jun 17 13:30:53 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 NAA12644
	for <disman-archive@lists.ietf.org>; Mon, 17 Jun 2002 13:30: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 g5HHXsC25049;
	Mon, 17 Jun 2002 12:33:54 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA19534
	for disman-list; Mon, 17 Jun 2002 10:25:23 -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 TAA12917;
	Fri, 14 Jun 2002 19:16:07 -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 g5F2DPI12724;
	Fri, 14 Jun 2002 21:13:25 -0500 (CDT)
Received: from geto.cysol.co.jp (geto.cysol.co.jp [210.169.247.73])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP
	id E28CA1FF04D; Fri, 14 Jun 2002 21:17:42 -0500 (CDT)
Received: from cysols.com (niseko.cysol.co.jp [210.169.247.75])
	by geto.cysol.co.jp (8.11.3/3.7W) with ESMTP id g5F2H6I10278;
	Sat, 15 Jun 2002 11:17:06 +0900 (JST)
Message-ID: <3D0AA395.2010106@cysols.com>
Date: Sat, 15 Jun 2002 11:16:53 +0900
From: Glenn Mansfield Keeni <glenn@cysols.com>
Organization: Cyber Solutions Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-gb, en, ja
MIME-Version: 1.0
To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Cc: disman@dorothy.bmc.com
Subject: Re: only 2 remaining goals, is disman dying?
References: <200206150137.SAA12816@dorothy.bmc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-MIME-Autoconverted: from 8bit to quoted-printable by geto.cysol.co.jp id g5F2H6I10278
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id TAA12918
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit

Elias,
       I think that the I-D should be submitted anyway.
Can you please do that. The deadline is 24th - we can
still make it.

Glenn

Randy Presuhn wrote:

> Hi -
> 
> 
>>From: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>
>>Subject: Re: only 2 remaining goals, is disman dying?
>>In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F017B7255@IS0004AVEXU1.global.avaya.com>
>> from "Romascanu, Dan (Dan)" at "Jun 12, 2002 09:06:54 am"
>>To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
>>Date: Fri, 14 Jun 2002 20:32:38 -0300 (BRT)
>>Cc: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>, disman@dorothy.bmc.com,
>>        "Elias Procopio Duarte Jr." <elias@mx-us-hou-1-int.bmc.com>
>>Message-Id: <20020614232802.57F9C20EF8A@mx-us-hou-1-int.bmc.com>
>>
> ...
> 
>>The current version of the draft is available at
>>http://www.inf.ufpr.br/~aldri/draft/replicationmib/index.html
>>
>>We didn't submit it because of the uncertainty regarding disman meeting or
>>not in Yohohama...
>>
> ...
> 
> The working group chair has some difficulty understanding
> this reasoning.  Without an i-d, there probably won't be much
> discussion on the mailing list.  Without significant interest
> expressed on the mailing list, the WG chair is unlikely to
> allocate time in a WG face-to-face meeting, particularly when
> work on our existing deliverables remains.
> 
>  ------------------------------------------------------
>  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 Jun 17 14:01:43 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 OAA14331
	for <disman-archive@lists.ietf.org>; Mon, 17 Jun 2002 14:01: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 g5HI5NC07261;
	Mon, 17 Jun 2002 13:05:23 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA20642
	for disman-list; Mon, 17 Jun 2002 10:58:19 -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 IAA19254
	for <disman@dorothy.bmc.com>; Mon, 17 Jun 2002 08: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 g5HFqm916765
	for <disman@dorothy.bmc.com>; Mon, 17 Jun 2002 10:52:48 -0500 (CDT)
Received: from ihemail1.firewall.lucent.com (unknown [192.11.222.161])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id BB2DB20EF86
	for <disman@dorothy.bmc.com>; Mon, 17 Jun 2002 10:57:10 -0500 (CDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5HFv2p29934
	for <disman@dorothy.bmc.com>; Mon, 17 Jun 2002 11:57:02 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id RAA06560; Mon, 17 Jun 2002 17:56:56 +0200 (MET DST)
To: <disman@dorothy.bmc.com>, <aaa-wg@merit.edu>, <rmonmib@ietf.org>,
        <policy@ietf.org>, <snmpv3@lists.tislabs.com>, <sming@ops.ietf.org>,
        <mpls@uu.net>, <mobile-ip@sunroof.eng.sun.com>, <gsmp@ietf.org>,
        <diffserv@ietf.org>, <sip@ietf.org>, <mmusic@ietf.org>
Received: from ouranos by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id RAA06555; Mon, 17 Jun 2002 17:56:49 +0200 (MET DST)
Message-ID: <01de01c21617$a602b790$9981cdd4@ouranos>
Reply-To: "Nikos A. Nikolaou" <nikolaou@lucent.com>
From: "Nikos A. Nikolaou" <nikolaou@lucent.com>
Original-To: <disman@dorothy.bmc.com>, <aaa-wg@merit.edu>, <rmonmib@ietf.org>,
        <policy@ietf.org>, <snmpv3@lists.tislabs.com>, <sming@ops.ietf.org>,
        <mpls@uu.net>, <mobile-ip@sunroof.eng.sun.com>, <gsmp@ietf.org>,
        <diffserv@ietf.org>, <sip@ietf.org>, <mmusic@ietf.org>
Subject: CFP: Special Issue in IEEE Network on Network Management
Date: Mon, 17 Jun 2002 18:57:04 +0300
Organization: Lucent Technologies
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-7"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

My apologies if you receive multiple copies of this.

A pdf version of this CFP will be available soon at
http://www.comsoc.org/pubs/net/ntwrk/special.html

Kind regards,
Nikos A. Nikolaou


-------------------------------------------------------------------------------
                        Call For Papers
                IEEE Network Magazine Special Issue on
    Network Management of Multi-service, Multimedia, IP-based Networks

Guest Editors

Dr. Nikolaos Nikolaou                   Dr. Theodore Zahariadis
Lucent Technologies                     Networking & Multimedia Systems
Bell Labs - AT, EMEA                    Ellemedia Technologies
Botterstraat 45                         Syggrou 223,
1270 AA, Huizen,                        171 21, Athens
The Netherlands                         Greece
Tel: +31 - 35 - 687 5302                Tel: +30 - 10 - 937 3097
Email: nikolaou@lucent.com              Email: zahariad@ellemedia.com

Prof. Joan Serrat                       Dr. Bharat Doshi
Telecommunication Engineering           Lucent Technologies
Universitat Politecnica de Catalunya    Bell Labs
Sor Eulalia d'Anzizu, s/n,              101 Crawfords Corner Rd,
08034, Barcelona,                       Holmdel, NJ  07733
Spain                                   USA
Tel: +34 - 93 - 401 6786                Tel: +1732 949 0823
Email: serrat@tsc.upc.es                Email: bdoshi@lucent.com


Objectives

During the last decade, innovations concerning optical networking technology, as
well as advances in digital compression and transmission over copper and cable
have dramatically increased the capabilities and the efficiency of existing and
imminent access-, metropolitan- and core-networks. A major breakthrough in
communications was the fast deployment of cellular systems. Currently, 3G
wireless systems, targeting the transmission of voice, video and high-speed
data, are already under preliminary deployment. Furthermore, researchers and
vendors are expressing a growing interest in 4G wireless systems that will
support even higher rates and cater for global roaming across multiple wireless
networks.

Meanwhile, based on the TCP/IP protocol suite, the Internet has evolved from a
research network, targeting a limited audience of academic and military users,
to a huge and commercially operated network. Next-generation IP technology has
the potential to prevail, both in the access and in the core, as we are moving
toward a worldwide, multi-service, multimedia and high-speed networking
environment. The explosion of IP-based multimedia applications led to an
exponential growth of IP traffic and initiated a number of research activities
that would allow efficient Quality of Service (QoS) support. Additionally, the
issue of security became more important and acquired considerable attention
owing to the proliferation of IP-based Virtual Private Networks (VPNs).

However, apart from efficient compression, sophisticated transmission schemes
and support for QoS, mobility and security, contemporary networking applications
require significant functionality for management operations, ensuring that the
underlining network is both available and capable of supporting the service
uninterruptedly. Configuration, performance and fault management over
heterogeneous underlying technologies and multi-layered networks, along with
end-to-end QoS, traffic management, service control platforms, billing and
mobility management are also crucial components of multi-service and high-speed
IP-based networks.

The goal of this special issue in IEEE Network Magazine is to present to the
magazine's audience (1) a comprehensive study of the design, performance and
deployment issues and solutions of end-to-end network management over
multi-domain, multi-technology, IP-based networks, and (2) a consolidated
insight into ongoing research, development and trials' evaluation of network
management technologies and platforms, broadening future research directions. To
achieve this goal, this special issue seeks for original papers with strong
tutorial and/or survey perspective that will consolidate and present the
leading-edge research prototype development, trials and early deployment and
performance studies in Network Management of multi-service, multimedia, IP-based
networks.


Topics

In particular, focused tutorial and survey contributions are solicited on (but
not restricted to) the following areas:
* End-to-end IP multimedia network and service management
* VoIP, IP Video, streaming, interactive video service management
* Provisioning of multimedia networks and services
* Wireless LAN and 3G/4G mobile multimedia network management
* Management of terminal and network mobility
* Inter-domain IP over WDM multimedia network management
* Network management models and architectures
* Management issues for billing and security for IP multimedia services
* Multi-domain, multi-point, multicast services management
* Policy-based management for multimedia services
* Performance and Fault Management of Multi-layered Networks
* QoS management
* Multimedia traffic management
* Active multimedia network management
* Middleware support for management


Manuscript Submission

Interested authors should submit an electronic version of the manuscript, in
either Postscript or PDF format, as an email attachment to one of the guest
editors.

Additional information including "Guidelines for authors" is available at the
IEEE Network Website: http://www.comsoc.org/pubs/net/ntwrk/authors.html


Important Dates

Submission Deadline:            October 1, 2002
Notification of Acceptance:     December 21, 2002
Final Manuscript Due:           March 1, 2003
Publication Date:               May/June 2003
-------------------------------------------------------------------------------





From owner-disman@dorothy.bmc.com  Mon Jun 17 18:50:32 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 SAA22360
	for <disman-archive@lists.ietf.org>; Mon, 17 Jun 2002 18:50:31 -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 g5HHhot28798;
	Mon, 17 Jun 2002 12:43:50 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA20375
	for disman-list; Mon, 17 Jun 2002 10:37:35 -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 CAA16055
	for <disman@dorothy.bmc.com>; Sun, 16 Jun 2002 02:49:19 -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 g5G9kYp03550
	for <disman@dorothy.bmc.com>; Sun, 16 Jun 2002 04:46:34 -0500 (CDT)
Received: from ierw.net.avaya.com (unknown [198.152.13.101])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 8C17B20F011
	for <disman@dorothy.bmc.com>; Sun, 16 Jun 2002 04:50:56 -0500 (CDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id FAA18098
	for <disman@dorothy.bmc.com>; Sun, 16 Jun 2002 05:49:03 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id FAA18084
	for <disman@dorothy.bmc.com>; Sun, 16 Jun 2002 05:49:02 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Subject: RE: Alarm #38, #43 - trap/notification varbind and timestamps
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2151A.EA53B064"
Date: Sun, 16 Jun 2002 12:48:06 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F01BD12E1@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Alarm #38, #43 - trap/notification varbind and timestamps
Thread-Index: AcITwuP6Je/0iSiZS1KPEuuNutl97QBNxixg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Tom Petch" <nwnetworks@dial.pipex.com>,
        "Sharon Chisholm" <schishol@nortelnetworks.com>,
        <disman@dorothy.bmc.com>
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>



This is a multi-part message in MIME format.

------_=_NextPart_001_01C2151A.EA53B064
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Tom,=20
=20
Would the following edit for #43 reflect your intention?
=20
'The time when the error occurred MAY be retrieved from a different =
source. If a   distributed system using notifications for alarm =
generation is being implemented, then he time when the error occurred =
SHOULD be retrieved from the variable bindings of the notification. '
=20
Regards,
=20
Dan
=20

-----Original Message-----
From: Tom Petch [mailto:nwnetworks@dial.pipex.com]
Sent: Thursday, June 13, 2002 8:15 PM
To: Sharon Chisholm; disman@dorothy.bmc.com
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps


I believe the same index should retrieve the same value, regardless of =
v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It is simple., it =
is logical.  But I am not clear from the text if that is an option you =
are offering me  !
Tom Petch, Network Consultant
nwnetworks@dial.pipex.com

-----Original Message-----
From: Sharon Chisholm < schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com < disman@dorothy.bmc.com>
Date: 06 June 2002 04:22
Subject: Alarm #38, #43 - trap/notification varbind and timestamps



hi=20

Since potentially always treating notification varbinds like=20
they are NOTIFICATION-TYPE in #38 is related to the always=20
storing varbinds as if they are from notifications, as appose=20
to v1 traps, in #43, I've grouped these two:=20

Alarm #38 Description of object alarmModelVarbindIndex=20
  Option 1) Change "For SNMPv1 traps, a 1 indicates the first varbind. =
For=20
  NOTIFICATION-TYPE," to "For v1Traps,For v2Traps and Informs, a 1 =
indicates=20
  the first varbind. ".=20
  Option 2) Alternatively, always treat it like v2 traps=20

  Solution: For consistency with #43 and to comply with the=20
  philosophy of 2576, notifications, regardless of the protocol=20
  will be treated *as though* they were NOTIFICATION-TYPE. We still=20
  need to provide guidance of how to use this with v1 traps, as=20
  well as indicate whether an index of 3 is the third varbind in the=20
  notification on the wire, or as defined in the SMI. Therefore, the=20
  the text from option 1) still applies:=20

   "For SNMPv1 traps, a 1 indicates the first varbind. For=20
         v2Traps and Informs, a 1 indicates the first real varbind=20
         after the required varbinds of sysUptime and SNMPTrapOID.".=20

Alarm #43 Timestamp Description & Do we need two timestamps=20
  Change text to:=20
  'The time that the error information was added to the alarm table.=20
  The time when the error occurred may be retrieved from a different=20
  source, e.g. from the variable bindings of the notification if a=20
  distributed system using notifications for alarm generation is=20
  being implemented'.=20
  Does this then require sysUptime and trapOID to be stored in=20
    alarmActiveVariableTable, even for v1 traps?=20
 =20
  Solution: Change text as described above. Always store notifications=20
    as if they are NOTIFICATION-TYPE/v2 traps/informs.=20

Sharon Chisholm=20
Preside Management=20
Nortel Networks=20
Ottawa, Ontario=20


------_=_NextPart_001_01C2151A.EA53B064
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Alarm #38, #43 - trap/notification varbind and timestamps</TITLE>

<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY bgColor=3D#ffffff>
<DIV><SPAN class=3D842235205-16062002><FONT face=3DArial color=3D#0000ff =
size=3D2>Tom,=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D842235205-16062002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D842235205-16062002><FONT face=3DArial color=3D#0000ff =
size=3D2>Would=20
the following edit for #43 reflect your intention?</FONT></SPAN></DIV>
<DIV><SPAN class=3D842235205-16062002><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D842235205-16062002><FONT size=3D2>'<SPAN=20
class=3D842235205-16062002><FONT size=3D2>The time when the error =
occurred&nbsp;MAY=20
be retrieved from a different&nbsp;source. </FONT></SPAN>If =
a&nbsp;</FONT><FONT=20
size=3D2>&nbsp; distributed system using notifications for alarm =
generation=20
is&nbsp;</FONT><FONT size=3D2>being implemented, then <SPAN=20
class=3D842235205-16062002><FONT size=3D2>he time when the error =
occurred SHOULD be=20
retrieved from the variable bindings of the notification.=20
</FONT></SPAN>'</FONT></SPAN></DIV>
<DIV><SPAN class=3D842235205-16062002><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D842235205-16062002><FONT =
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=3D842235205-16062002><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D842235205-16062002><FONT =
size=3D2>Dan</FONT></SPAN></DIV>
<DIV><SPAN class=3D842235205-16062002><FONT =
size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Tom Petch=20
  [mailto:nwnetworks@dial.pipex.com]<BR><B>Sent:</B> Thursday, June 13, =
2002=20
  8:15 PM<BR><B>To:</B> Sharon Chisholm;=20
  disman@dorothy.bmc.com<BR><B>Subject:</B> Re: Alarm #38, #43 -=20
  trap/notification varbind and timestamps<BR><BR></FONT></DIV>
  <DIV><FONT color=3D#000000 size=3D2>I believe the same index should =
retrieve the=20
  same value, regardless of v1 or v2 ie 1 for sysUpTime, 2 for =
SNMPTrapOID=20
  etc.&nbsp; It is simple., it is logical.&nbsp; But I am not clear from =
the=20
  text if that is an option you are offering me&nbsp; !</FONT></DIV>
  <DIV><FONT color=3D#000000 size=3D2>Tom Petch, Network =
Consultant<BR><A=20
  =
href=3D"mailto:nwnetworks@dial.pipex.com">nwnetworks@dial.pipex.com</A></=
FONT></DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid">
    <DIV><FONT face=3DArial size=3D2><B>-----Original =
Message-----</B><BR><B>From:=20
    </B>Sharon Chisholm &lt;<A=20
    =
href=3D"mailto:schishol@nortelnetworks.com">schishol@nortelnetworks.com</=
A>&gt;<BR><B>To:=20
    </B><A =
href=3D"mailto:disman@dorothy.bmc.com">disman@dorothy.bmc.com</A>=20
    &lt;<A=20
    =
href=3D"mailto:disman@dorothy.bmc.com">disman@dorothy.bmc.com</A>&gt;<BR>=
<B>Date:=20
    </B>06 June 2002 04:22<BR><B>Subject: </B>Alarm #38, #43 - =
trap/notification=20
    varbind and timestamps<BR><BR></DIV></FONT>
    <P><FONT size=3D2>hi</FONT> </P>
    <P><FONT size=3D2>Since potentially always treating notification =
varbinds=20
    like</FONT> <BR><FONT size=3D2>they are NOTIFICATION-TYPE in #38 is =
related to=20
    the always</FONT> <BR><FONT size=3D2>storing varbinds as if they are =
from=20
    notifications, as appose</FONT> <BR><FONT size=3D2>to v1 traps, in =
#43, I've=20
    grouped these two:</FONT> </P>
    <P><FONT size=3D2>Alarm #38 Description of object =
alarmModelVarbindIndex=20
    </FONT><BR><FONT size=3D2>&nbsp; Option 1) Change "For SNMPv1 traps, =
a 1=20
    indicates the first varbind. For</FONT> <BR><FONT size=3D2>&nbsp;=20
    NOTIFICATION-TYPE," to "For v1Traps,For v2Traps and Informs, a 1=20
    indicates</FONT> <BR><FONT size=3D2>&nbsp; the first varbind. ".=20
    </FONT><BR><FONT size=3D2>&nbsp; Option 2) Alternatively, always =
treat it like=20
    v2 traps</FONT> </P>
    <P><FONT size=3D2>&nbsp; Solution: For consistency with #43 and to =
comply with=20
    the</FONT> <BR><FONT size=3D2>&nbsp; philosophy of 2576, =
notifications,=20
    regardless of the protocol</FONT> <BR><FONT size=3D2>&nbsp; will be =
treated=20
    *as though* they were NOTIFICATION-TYPE. We still</FONT> <BR><FONT=20
    size=3D2>&nbsp; need to provide guidance of how to use this with v1 =
traps,=20
    as</FONT> <BR><FONT size=3D2>&nbsp; well as indicate whether an =
index of 3 is=20
    the third varbind in the</FONT> <BR><FONT size=3D2>&nbsp; =
notification on the=20
    wire, or as defined in the SMI. Therefore, the</FONT> <BR><FONT=20
    size=3D2>&nbsp; the text from option 1) still applies:</FONT> </P>
    <P><FONT size=3D2>&nbsp;&nbsp; "For SNMPv1 traps, a 1 indicates the =
first=20
    varbind. For</FONT> <BR><FONT=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; v2Traps =
and Informs,=20
    a 1 indicates the first real varbind</FONT> <BR><FONT=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; after the =
required=20
    varbinds of sysUptime and SNMPTrapOID.".</FONT> </P>
    <P><FONT size=3D2>Alarm #43 Timestamp Description &amp; Do we need =
two=20
    timestamps</FONT> <BR><FONT size=3D2>&nbsp; Change text to:</FONT> =
<BR><FONT=20
    size=3D2>&nbsp; 'The time that the error information was added to =
the alarm=20
    table. </FONT><BR><FONT size=3D2>&nbsp; The time when the error =
occurred may=20
    be retrieved from a different </FONT><BR><FONT size=3D2>&nbsp; =
source, e.g.=20
    from the variable bindings of the notification if a </FONT><BR><FONT =

    size=3D2>&nbsp; distributed system using notifications for alarm =
generation is=20
    </FONT><BR><FONT size=3D2>&nbsp; being implemented'.</FONT> =
<BR><FONT=20
    size=3D2>&nbsp; Does this then require sysUptime and trapOID to be =
stored in=20
    </FONT><BR><FONT size=3D2>&nbsp;&nbsp;&nbsp; =
alarmActiveVariableTable, even=20
    for v1 traps?</FONT> <BR><FONT size=3D2>&nbsp;</FONT> <BR><FONT =
size=3D2>&nbsp;=20
    Solution: Change text as described above. Always store =
notifications</FONT>=20
    <BR><FONT size=3D2>&nbsp;&nbsp;&nbsp; as if they are =
NOTIFICATION-TYPE/v2=20
    traps/informs.</FONT> </P>
    <P><FONT size=3D2>Sharon Chisholm</FONT> <BR><FONT size=3D2>Preside=20
    Management</FONT> <BR><FONT size=3D2>Nortel Networks</FONT> =
<BR><FONT=20
    size=3D2>Ottawa, Ontario</FONT> =
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C2151A.EA53B064--




From owner-disman@dorothy.bmc.com  Tue Jun 18 08:34: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 IAA14767
	for <disman-archive@odin.ietf.org>; Tue, 18 Jun 2002 08:34: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 g5ICbtd19125;
	Tue, 18 Jun 2002 07:37:55 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA23915
	for disman-list; Tue, 18 Jun 2002 05:31:01 -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 FAA23908
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 05:30:57 -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 g5ICSBU28318
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 07:28:11 -0500 (CDT)
Received: from penguin.wise.edt.ericsson.se (unknown [193.180.251.47])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 2B76120EF8F
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 07:32:34 -0500 (CDT)
Received: from mbb5.ericsson.se (mbb5.ericsson.se [136.225.151.210])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5ICWSRb019825
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 14:32:28 +0200 (MEST)
Received: from lm6068 (lm6068.lmera.ericsson.se [150.132.106.68])
 by mbb1.ericsson.se (PMDF V5.2-29 #39352)
 with ESMTP id <0GXW003CAIU4XE@mbb1.ericsson.se> for disman@dorothy.bmc.com;
 Tue, 18 Jun 2002 14:32:28 +0200 (MET DST)
Date: Tue, 18 Jun 2002 14:32:26 +0200
From: David Partain <David.Partain@ericsson.com>
Subject: Re: Alarm #35, #36 - Varbinds to alarmActive Notification
In-reply-to: <3549C09B853DD5119B540002A52CDD3403878998@zcard0ka.ca.nortel.com>
To: Sharon Chisholm <schishol@nortelnetworks.com>, disman@dorothy.bmc.com
Reply-To: David.Partain@ericsson.com
Message-id: <200206181432.26435.David.Partain@ericsson.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8bit
User-Agent: KMail/1.4.1
References: <3549C09B853DD5119B540002A52CDD3403878998@zcard0ka.ca.nortel.com>
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,

Thanks for the work on getting these issues closed out.

> Alarm #36 Varbinds to alarmActiveState notifications
>   Using explicit varbinds if model, state and name or using
>   alarmActiveModelPointer
>   Option 1) varbind alarmListName, alarmModelIndex, alarmModelState
>   Option 2) varbind alarmActiveModelPointer
>
> Solution: Replace alarmModelIndex and alarmModelState
>   in alarmActiveState notification with alarmModelPointer.

Actually, I _think_ you mean alarmActiveModelPointer, right?

NOTE:  Your suggestion doesn't provide a change to
alarmClearState, which has exactly the same problem as
alarmActiveState.

-------------------------------------------------------------------
Change 1:

So, just to make sure I have it right, you're proposing that:

   alarmActiveState NOTIFICATION-TYPE
    OBJECTS     { alarmModelIndexVarbind,
                  alarmModelStateVarbind,
                  alarmActiveResourceId }
    STATUS      current
    DESCRIPTION
       "An instance of the alarm indicated by
       alarmModelIndexVarbind has been raised
       against the entity indicated by
       alarmActiveResourceType and alarmACtiveResourceId."
    ::= { alarmNotifications 2 }

becomes

   alarmActiveState NOTIFICATION-TYPE
    OBJECTS     { alarmActiveModelPointer,
                  alarmActiveResourceId }
    STATUS      current
    DESCRIPTION
       "An instance of the alarm modeled in the model table
       pointed to by alarmActiveModelPointer has been raised
       against the entity indicated by alarmActiveResourceId."
    ::= { alarmNotifications 2 }


-------------------------------------------------------------------
Change 2:

Since alarmClearState also has to be fixed, I suggest that:

   alarmClearState NOTIFICATION-TYPE
      OBJECTS     { alarmModelIndexVarbind,
                    alarmActiveResourceId }
      STATUS      current
      DESCRIPTION
        "An instance of the alarm indicated by
        alarmModelIndexVarbind has been cleared against
        the entity indicated by alarmActiveResourceType
        and alarmACtiveResourceId."
      ::= { alarmNotifications 3 }

be changed to:

   alarmClearState NOTIFICATION-TYPE
      OBJECTS     { alarmActiveModelPointer,
                    alarmActiveResourceId }
      STATUS      current
      DESCRIPTION
        "An instance of the alarm modeled in the model table row
        pointed to by alarmActiveModelPointer has been cleared
        against the entity indicated by alarmActiveResourceId."
      ::= { alarmNotifications 3 }

Cheers,

dlp



From owner-disman@dorothy.bmc.com  Tue Jun 18 08:43:45 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 IAA15055
	for <disman-archive@odin.ietf.org>; Tue, 18 Jun 2002 08:43:45 -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 g5IClNt22534;
	Tue, 18 Jun 2002 07:47:23 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA23985
	for disman-list; Tue, 18 Jun 2002 05:41:08 -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 FAA23980
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 05:41:04 -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 g5ICcJT03188
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 07:38:19 -0500 (CDT)
Received: from penguin.wise.edt.ericsson.se (unknown [193.180.251.47])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id A8AD620EFB7
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 07:42:41 -0500 (CDT)
Received: from mbb5.ericsson.se (mbb5.ericsson.se [136.225.151.210])
	by penguin.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5ICgZRb023295
	for <disman@dorothy.bmc.com>; Tue, 18 Jun 2002 14:42:35 +0200 (MEST)
Received: from lm6068 (lm6068.lmera.ericsson.se [150.132.106.68])
 by mbb1.ericsson.se (PMDF V5.2-29 #39352)
 with ESMTP id <0GXW0060QJAZZJ@mbb1.ericsson.se> for disman@dorothy.bmc.com;
 Tue, 18 Jun 2002 14:42:35 +0200 (MET DST)
Date: Tue, 18 Jun 2002 14:42:34 +0200
From: David Partain <David.Partain@ericsson.com>
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
In-reply-to: <00ee01c212fe$04af84c0$0301a8c0@tom3>
To: disman@dorothy.bmc.com
Reply-To: David.Partain@ericsson.com
Message-id: <200206181442.34057.David.Partain@ericsson.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8bit
User-Agent: KMail/1.4.1
References: <00ee01c212fe$04af84c0$0301a8c0@tom3>
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,

On Thursday 13 June 2002 19.14, Tom Petch wrote:
> I believe the same index should retrieve the same value, regardless of
> v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It is simple., it
> is logical.  But I am not clear from the text if that is an option you
> are offering me  !

There is no varbind holding sysUpTime.0 or SNMPTrapOID in
an SNMPv1 trap.  They are embedded in the message wrapper.
As such, what you are asking for is not possible.

Since the first two VarBinds in a v2c/v3 trap/inform somewhat
approximate information that's in the message wrapper for
SNMPv1 traps, I thought Sharon's proposed text was just fine
(I removed the "real" from "real varbinds" since I don't know
how to send a "fake" varbind).

That is:

 "For SNMPv1 traps, a 1 indicates the first varbind. For
 v2Traps and Informs, a 1 indicates the first varbind after
 the required varbinds of sysUptime and SNMPTrapOID."

Cheers,

dlp



From owner-disman@dorothy.bmc.com  Tue Jun 18 20:58:48 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 UAA10079
	for <disman-archive@odin.ietf.org>; Tue, 18 Jun 2002 20:58:47 -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 g5J11nA25381;
	Tue, 18 Jun 2002 20:01:49 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA26242
	for disman-list; Tue, 18 Jun 2002 17:53:49 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id RAA26236
	for disman@dorothy.bmc.com; Tue, 18 Jun 2002 17:53:44 -0700 (PDT)
Date: Tue, 18 Jun 2002 17:53:44 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206190053.RAA26236@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
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 -

> Date: Tue, 18 Jun 2002 14:42:34 +0200
> From: David Partain <David.Partain@ericsson.com>
> Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
> In-reply-to: <00ee01c212fe$04af84c0$0301a8c0@tom3>
> To: disman@dorothy.bmc.com
> Reply-To: David.Partain@ericsson.com
> Message-id: <200206181442.34057.David.Partain@ericsson.com>
> User-Agent: KMail/1.4.1
> References: <00ee01c212fe$04af84c0$0301a8c0@tom3>
> List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
> 
> Hi,
> 
> On Thursday 13 June 2002 19.14, Tom Petch wrote:
> > I believe the same index should retrieve the same value, regardless of
> > v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It is simple., it
> > is logical.  But I am not clear from the text if that is an option you
> > are offering me  !
> 
> There is no varbind holding sysUpTime.0 or SNMPTrapOID in
> an SNMPv1 trap.  They are embedded in the message wrapper.
> As such, what you are asking for is not possible.
> 
> Since the first two VarBinds in a v2c/v3 trap/inform somewhat
> approximate information that's in the message wrapper for
> SNMPv1 traps, I thought Sharon's proposed text was just fine
> (I removed the "real" from "real varbinds" since I don't know
> how to send a "fake" varbind).
> 
> That is:
> 
>  "For SNMPv1 traps, a 1 indicates the first varbind. For
>  v2Traps and Informs, a 1 indicates the first varbind after
>  the required varbinds of sysUptime and SNMPTrapOID."
...

The same logic leads me, as a technical contributor, down a
very different path.

In order to avoid losing information and to maintain the
valuable distinction between the notification and the active
alarm's time stamps, I would suggest that we follow the RFC 2576
rules (section 3.1) so that everything is represented as though
it had arrived in RFC 1905 format.  I think this is ultimately
simpler than introducing a new set of rules peculiar to this
MIB to treat everything as though it were SNMPv1.

 ------------------------------------------------------
 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  Wed Jun 19 02:45:53 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 CAA09225
	for <disman-archive@odin.ietf.org>; Wed, 19 Jun 2002 02:45:52 -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 g5J6nY123432;
	Wed, 19 Jun 2002 01:49:34 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id XAA26864
	for disman-list; Tue, 18 Jun 2002 23:43:02 -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 XAA26856;
	Tue, 18 Jun 2002 23:42:58 -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 g5J6eCw02579;
	Wed, 19 Jun 2002 01:40:12 -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 12CD11FF017; Wed, 19 Jun 2002 01:44:35 -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 g5J6iJiB003281;
	Wed, 19 Jun 2002 08:44:19 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g5J6iIH22804;
	Wed, 19 Jun 2002 08:44:18 +0200
Date: Wed, 19 Jun 2002 08:44:18 +0200
Message-Id: <200206190644.g5J6iIH22804@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: rpresuhn@dorothy.bmc.com
Cc: disman@dorothy.bmc.com
In-reply-to: <200206190053.RAA26236@dorothy.bmc.com> (message from Randy
	Presuhn on Tue, 18 Jun 2002 17:53:44 -0700 (PDT))
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
References:  <200206190053.RAA26236@dorothy.bmc.com>
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>


>>>>> Randy Presuhn writes:

Randy> In order to avoid losing information and to maintain the
Randy> valuable distinction between the notification and the active
Randy> alarm's time stamps, I would suggest that we follow the RFC
Randy> 2576 rules (section 3.1) so that everything is represented as
Randy> though it had arrived in RFC 1905 format.  I think this is
Randy> ultimately simpler than introducing a new set of rules peculiar
Randy> to this MIB to treat everything as though it were SNMPv1.

I agree.

/js

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




From owner-disman@dorothy.bmc.com  Wed Jun 19 03:14:20 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 DAA09682
	for <disman-archive@odin.ietf.org>; Wed, 19 Jun 2002 03:14:19 -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 g5J7I2602336;
	Wed, 19 Jun 2002 02:18:02 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id AAA26913
	for disman-list; Wed, 19 Jun 2002 00:11: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 AAA26907;
	Wed, 19 Jun 2002 00:11:44 -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 g5J78wm13997;
	Wed, 19 Jun 2002 02:08:58 -0500 (CDT)
Received: from albatross.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [193.180.251.49])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP
	id 6F1A91FF007; Wed, 19 Jun 2002 02:13:21 -0500 (CDT)
Received: from mbb5.ericsson.se (mbb5.ericsson.se [136.225.151.210])
	by albatross.wise.edt.ericsson.se (8.12.1/8.12.1/WIREfire-1.4) with ESMTP id g5J7CtrU007786;
	Wed, 19 Jun 2002 09:12:55 +0200 (MEST)
Received: from lm6068 (lm6068.lmera.ericsson.se [150.132.106.68])
 by mbb1.ericsson.se (PMDF V5.2-29 #39352)
 with ESMTP id <0GXX006K3YPJOM@mbb1.ericsson.se>; Wed,
 19 Jun 2002 09:12:55 +0200 (MET DST)
Date: Wed, 19 Jun 2002 09:12:53 +0200
From: David Partain <David.Partain@ericsson.com>
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
In-reply-to: <200206190053.RAA26236@dorothy.bmc.com>
To: Randy Presuhn <rpresuhn@dorothy.bmc.com>, disman@dorothy.bmc.com
Reply-To: David.Partain@ericsson.com
Message-id: <200206190912.53511.David.Partain@ericsson.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8bit
User-Agent: KMail/1.4.1
References: <200206190053.RAA26236@dorothy.bmc.com>
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 all,

> > > On Thursday 13 June 2002 19.14, Tom Petch wrote:
> > > I believe the same index should retrieve the same value, regardless of
> > > v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It is simple., it
> > > is logical.  But I am not clear from the text if that is an option you
> > > are offering me  !

I responded:
> > There is no varbind holding sysUpTime.0 or SNMPTrapOID in
> > an SNMPv1 trap.  They are embedded in the message wrapper.
> > As such, what you are asking for is not possible.
> >
> > Since the first two VarBinds in a v2c/v3 trap/inform somewhat
> > approximate information that's in the message wrapper for
> > SNMPv1 traps, I thought Sharon's proposed text was just fine
> > (I removed the "real" from "real varbinds" since I don't know
> > how to send a "fake" varbind).
> >
> > That is:
> >
> >  "For SNMPv1 traps, a 1 indicates the first varbind. For
> >  v2Traps and Informs, a 1 indicates the first varbind after
> >  the required varbinds of sysUptime and SNMPTrapOID."

Then, Randy P. wrote:

> The same logic leads me, as a technical contributor, down a
> very different path.
>
> In order to avoid losing information and to maintain the
> valuable distinction between the notification and the active
> alarm's time stamps, I would suggest that we follow the RFC 2576
> rules (section 3.1) so that everything is represented as though
> it had arrived in RFC 1905 format.  I think this is ultimately
> simpler than introducing a new set of rules peculiar to this
> MIB to treat everything as though it were SNMPv1.

That's absolutely fine with me.  In that case, the DESCRIPTION
for alarmModelVarbindIndex needs to explain this.  The issue
remains that if that holds a value of 2, and that's going to
refer to the trap OID even if the incoming notification is a v1
trap, then there must be some information in this description
that states that.  Otherwise, I think there's a strong risk for
confusion.

How about this as a replacement for the second paragraph of
the DESCRIPTION:

  "Note that the value of alarmModelVarbindIndex assumes
  the existence of the first two obligatory varbinds in
  the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0
  and snmpTrapOID.0).  That is, a value of 1 refers to
  sysUpTime.0, and a value of 3 refers to the first varbind
  after snmpTrapOID.0.

  If the incoming notification is instead an SNMPv1 Trap-PDU and
  the value of alarmModelVarbindIndex is 1 or 2, an appropriate
  value for sysUpTime.0 or snmpTrapOID.0 shall be determined
  by using the rules in section 3.1 of [appropriate reference
  for RFC2576]."

That way, a 1 always means sysUpTime and a 3 always means the
first "real" varbind.

Did I understand what you want?  Does this work?

Cheers,

dlp



From owner-disman@dorothy.bmc.com  Wed Jun 19 04:01:32 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 EAA10434
	for <disman-archive@odin.ietf.org>; Wed, 19 Jun 2002 04:01:32 -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 g5J85B818356;
	Wed, 19 Jun 2002 03:05:11 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id AAA27035
	for disman-list; Wed, 19 Jun 2002 00:58:35 -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 AAA27029;
	Wed, 19 Jun 2002 00:58:31 -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 g5J7tjd08408;
	Wed, 19 Jun 2002 02:55:45 -0500 (CDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP
	id 59C7E1FF01B; Wed, 19 Jun 2002 03:00:08 -0500 (CDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id DAA23098;
	Wed, 19 Jun 2002 03:58:06 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51])
	by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id DAA23082;
	Wed, 19 Jun 2002 03:58:05 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Alarm #38, #43 - trap/notification varbind and timestamps
Date: Wed, 19 Jun 2002 10:57:08 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0199A4D2@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Alarm #38, #43 - trap/notification varbind and timestamps
Thread-Index: AcIXYMUydppoO8ShS/2/fJY1z+yQSQABlw8Q
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <David.Partain@ericsson.com>, "Randy Presuhn" <rpresuhn@dorothy.bmc.com>,
        <disman@dorothy.bmc.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id AAA27030
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 8bit



> -----Original Message-----
> From: David Partain [mailto:David.Partain@ericsson.com]
> Sent: Wednesday, June 19, 2002 10:13 AM
> To: Randy Presuhn; disman@dorothy.bmc.com
> Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
> 
> 
> Hi all,
> 
> > > > On Thursday 13 June 2002 19.14, Tom Petch wrote:
> > > > I believe the same index should retrieve the same 
> value, regardless of
> > > > v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It 
> is simple., it
> > > > is logical.  But I am not clear from the text if that 
> is an option you
> > > > are offering me  !
> 
> I responded:
> > > There is no varbind holding sysUpTime.0 or SNMPTrapOID in
> > > an SNMPv1 trap.  They are embedded in the message wrapper.
> > > As such, what you are asking for is not possible.
> > >
> > > Since the first two VarBinds in a v2c/v3 trap/inform somewhat
> > > approximate information that's in the message wrapper for
> > > SNMPv1 traps, I thought Sharon's proposed text was just fine
> > > (I removed the "real" from "real varbinds" since I don't know
> > > how to send a "fake" varbind).
> > >
> > > That is:
> > >
> > >  "For SNMPv1 traps, a 1 indicates the first varbind. For
> > >  v2Traps and Informs, a 1 indicates the first varbind after
> > >  the required varbinds of sysUptime and SNMPTrapOID."
> 
> Then, Randy P. wrote:
> 
> > The same logic leads me, as a technical contributor, down a
> > very different path.
> >
> > In order to avoid losing information and to maintain the
> > valuable distinction between the notification and the active
> > alarm's time stamps, I would suggest that we follow the RFC 2576
> > rules (section 3.1) so that everything is represented as though
> > it had arrived in RFC 1905 format.  I think this is ultimately
> > simpler than introducing a new set of rules peculiar to this
> > MIB to treat everything as though it were SNMPv1.
> 
> That's absolutely fine with me.  In that case, the DESCRIPTION
> for alarmModelVarbindIndex needs to explain this.  The issue
> remains that if that holds a value of 2, and that's going to
> refer to the trap OID even if the incoming notification is a v1
> trap, then there must be some information in this description
> that states that.  Otherwise, I think there's a strong risk for
> confusion.
> 
> How about this as a replacement for the second paragraph of
> the DESCRIPTION:
> 
>   "Note that the value of alarmModelVarbindIndex assumes
>   the existence of the first two obligatory varbinds in
>   the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0
>   and snmpTrapOID.0).  That is, a value of 1 refers to
>   sysUpTime.0, and a value of 3 refers to the first varbind
>   after snmpTrapOID.0.
> 
>   If the incoming notification is instead an SNMPv1 Trap-PDU and
>   the value of alarmModelVarbindIndex is 1 or 2, an appropriate
>   value for sysUpTime.0 or snmpTrapOID.0 shall be determined
>   by using the rules in section 3.1 of [appropriate reference
>   for RFC2576]."
> 
> That way, a 1 always means sysUpTime and a 3 always means the
> first "real" varbind.
> 
> Did I understand what you want?  Does this work?

I think it does. Regards, Dan



From owner-disman@dorothy.bmc.com  Thu Jun 20 17:12:43 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 RAA12672
	for <disman-archive@lists.ietf.org>; Thu, 20 Jun 2002 17:12:43 -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 g5KLGGh13567;
	Thu, 20 Jun 2002 16:16:16 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA03634
	for disman-list; Thu, 20 Jun 2002 14:08:07 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA03628
	for disman@dorothy.bmc.com; Thu, 20 Jun 2002 14:08:03 -0700 (PDT)
Date: Thu, 20 Jun 2002 14:08:03 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206202108.OAA03628@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Disman in 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 have requested a meeting slot in Yokohama.  I was hoping
that we'd be able to avoid holding a meeting, but it's clear
from the slow pace on the mailing list that we'll need to
use our face-to-face time to finish off our work items.

Preliminary agenda:

    1. administratsiya
    2. finishing the active alarm document
    3. finishing the alarm report control document
    4. wrap-up

Expected output: editors will know exactly what needs to
be done so we can issue updated i-ds and do a final WG last
call.

Editors: there is little time remaining for i-d submission.
I'd appreciate it if you could ensure that current consensus
i-ds will be available well before the meeting.

 ------------------------------------------------------
 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 Jun 21 07:27:00 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 HAA07610
	for <disman-archive@odin.ietf.org>; Fri, 21 Jun 2002 07:26:44 -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 g5LBUPn19843;
	Fri, 21 Jun 2002 06:30:25 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id EAA06631
	for disman-list; Fri, 21 Jun 2002 04:23: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 EAA06625;
	Fri, 21 Jun 2002 04:23:27 -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 g5LBKes28521;
	Fri, 21 Jun 2002 06:20:40 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP
	id 400F61FF02F; Fri, 21 Jun 2002 06:25:03 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g5LBOl204715;
	Fri, 21 Jun 2002 07:24:47 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYBW84D>; Fri, 21 Jun 2002 07:24:46 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403D7F751@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Cc: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Subject: RE: Disman in Yokohama
Date: Fri, 21 Jun 2002 07:24:45 -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

Sure, we were planning on issuing a new version of the alarm MIB
before the cut-off date. The only open issue that hasn't 
been reposted to try and close it off is #alarm 40, which
is the one that relates to trying to get the resource ID
from the varbinds. I can post that today and we should then
be able to get a rough consensus. 

Sharon

-----Original Message-----
From: Randy Presuhn [mailto:rpresuhn@dorothy.bmc.com]
Sent: Thursday, June 20, 2002 5:08 PM
To: disman@dorothy.bmc.com
Subject: Disman in Yokohama


Hi -

I have requested a meeting slot in Yokohama.  I was hoping
that we'd be able to avoid holding a meeting, but it's clear
from the slow pace on the mailing list that we'll need to
use our face-to-face time to finish off our work items.

Preliminary agenda:

    1. administratsiya
    2. finishing the active alarm document
    3. finishing the alarm report control document
    4. wrap-up

Expected output: editors will know exactly what needs to
be done so we can issue updated i-ds and do a final WG last
call.

Editors: there is little time remaining for i-d submission.
I'd appreciate it if you could ensure that current consensus
i-ds will be available well before the meeting.

 ------------------------------------------------------
 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 Jun 21 10:12: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 KAA13780
	for <disman-archive@odin.ietf.org>; Fri, 21 Jun 2002 10:12: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 g5LEFsc19570;
	Fri, 21 Jun 2002 09:15:54 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id HAA07049
	for disman-list; Fri, 21 Jun 2002 07:09:10 -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 HAA07043;
	Fri, 21 Jun 2002 07:09:07 -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 g5LE6JB18983;
	Fri, 21 Jun 2002 09:06:19 -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 C789020EFDB; Fri, 21 Jun 2002 09:10:43 -0500 (CDT)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5LEAcL25860;
	Fri, 21 Jun 2002 10:10:38 -0400 (EDT)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <MP3CS0R1>; Fri, 21 Jun 2002 10:10:37 -0400
Message-ID: <2E12619580C0D1118C6400805F9F4C950D7CF16C@nj7460exch001u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: "'Randy Presuhn'" <rpresuhn@dorothy.bmc.com>, disman@dorothy.bmc.com
Subject: RE: Disman in Yokohama
Date: Fri, 21 Jun 2002 10:10:37 -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,

The alarm report control document "draft-ietf-disman-conditionmib-02.txt" has been posted on April 25 and available at
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-02.txt

If there is any issue, please raise.

Regards,
Kam

> -----Original Message-----
> From: Randy Presuhn [mailto:rpresuhn@dorothy.bmc.com]
> Sent: Thursday, June 20, 2002 5:08 PM
> To: disman@dorothy.bmc.com
> Subject: Disman in Yokohama
> 
> 
> Hi -
> 
> I have requested a meeting slot in Yokohama.  I was hoping
> that we'd be able to avoid holding a meeting, but it's clear
> from the slow pace on the mailing list that we'll need to
> use our face-to-face time to finish off our work items.
> 
> Preliminary agenda:
> 
>     1. administratsiya
>     2. finishing the active alarm document
>     3. finishing the alarm report control document
>     4. wrap-up
> 
> Expected output: editors will know exactly what needs to
> be done so we can issue updated i-ds and do a final WG last
> call.
> 
> Editors: there is little time remaining for i-d submission.
> I'd appreciate it if you could ensure that current consensus
> i-ds will be available well before the meeting.
> 
>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  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  Fri Jun 21 14:16:52 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 OAA25549
	for <disman-archive@odin.ietf.org>; Fri, 21 Jun 2002 14:16: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 g5LIKQM20244;
	Fri, 21 Jun 2002 13:20:26 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA07718
	for disman-list; Fri, 21 Jun 2002 11:13:51 -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 UAA05701
	for <disman@dorothy.bmc.com>; Thu, 20 Jun 2002 20:46:10 -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 g5L3hNA14430
	for <disman@dorothy.bmc.com>; Thu, 20 Jun 2002 22:43:23 -0500 (CDT)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id C644D1FF04F
	for <disman@dorothy.bmc.com>; Thu, 20 Jun 2002 22:47:47 -0500 (CDT)
Received: from nj7460exch001h.wins.lucent.com (h135-17-42-36.lucent.com [135.17.42.36])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g5L3lWB19343
	for <disman@dorothy.bmc.com>; Thu, 20 Jun 2002 23:47:32 -0400 (EDT)
Received: by nj7460exch001h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <MP3CSNDA>; Thu, 20 Jun 2002 23:47:31 -0400
Message-ID: <2E12619580C0D1118C6400805F9F4C950D7CF16A@nj7460exch001u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: "'disman@dorothy.bmc.com'" <disman@dorothy.bmc.com>
Subject: draft-ietf-disman-conditionmib-02.txt
Date: Thu, 20 Jun 2002 23:47:30 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C218D6.5DC41FFC"
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>



This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C218D6.5DC41FFC
Content-Type: text/plain;
	charset="iso-8859-1"

On Thu, 20 Jun 2002, Randy Presuhn wrote:
>
> Editors: there is little time remaining for i-d submission.
> I'd appreciate it if you could ensure that current consensus
> i-ds will be available well before the meeting.
>

Dear all,

Please note that draft-ietf-disman-conditionmib-02.txt has been posted on April 20 and available at
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-02.txt

Any comments will be appreciated.

Regards,
Kam
 <<I-D ACTION:draft-ietf-disman-conditionmib-02.txt>> 


------_=_NextPart_000_01C218D6.5DC41FFC
Content-Type: message/rfc822
Content-Description: I-D ACTION:draft-ietf-disman-conditionmib-02.txt

Message-ID: <200204251219.IAA02661@ietf.org>
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
To: 
Cc: disman@dorothy.bmc.com
Subject: I-D ACTION:draft-ietf-disman-conditionmib-02.txt
Date: Thu, 25 Apr 2002 08:19:15 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01C218D6.5DC41FFC"




------_=_NextPart_002_01C218D6.5DC41FFC
Content-Type: text/plain

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 Report Control MIB
	Author(s)	: K. Lam, A. Huynh, D. Perkins
	Filename	: draft-ietf-disman-conditionmib-02.txt
	Pages		: 
	Date		: 24-Apr-02
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for controlling the reporting of 
alarm conditions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-02.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-conditionmib-02.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-conditionmib-02.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_002_01C218D6.5DC41FFC
Content-Type: message/rfc822

To: 
Subject: 
Date: Thu, 25 Apr 2002 08:39:49 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_004_01C218D6.5DC41FFC"




------_=_NextPart_004_01C218D6.5DC41FFC
Content-Type: text/plain



------_=_NextPart_004_01C218D6.5DC41FFC
Content-Type: application/octet-stream;
	name="ATT19540"
Content-Disposition: attachment;
	filename="ATT19540"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-conditionmib-02.txt

------_=_NextPart_004_01C218D6.5DC41FFC
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-ietf-disman-conditionmib-02.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_004_01C218D6.5DC41FFC--

------_=_NextPart_002_01C218D6.5DC41FFC--

------_=_NextPart_000_01C218D6.5DC41FFC--




From owner-disman@dorothy.bmc.com  Fri Jun 21 14:49:40 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 OAA26846
	for <disman-archive@odin.ietf.org>; Fri, 21 Jun 2002 14:49: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 g5LIq9I01147;
	Fri, 21 Jun 2002 13:52:09 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA08742
	for disman-list; Fri, 21 Jun 2002 11:45:48 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA08736
	for disman@dorothy.bmc.com; Fri, 21 Jun 2002 11:45:45 -0700 (PDT)
Date: Fri, 21 Jun 2002 11:45:45 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206211845.LAA08736@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: disman list reminder
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 -

Please keep in mind that if you post HTML or multipart MIME
messages to the disman list, those messages will be quarantined
by the spam filters and have to be manually approved.  If you
don't like they delay, please don't use HTML or multipart MIME on
this mailing list.  (With the huge quantities of forged viral
spam out there, these are our most effective filters for stopping
the really bad 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  Fri Jun 21 17:49:02 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 RAA02333
	for <disman-archive@odin.ietf.org>; Fri, 21 Jun 2002 17:48:59 -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 g5LLqTN15022;
	Fri, 21 Jun 2002 16:52:29 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA09234
	for disman-list; Fri, 21 Jun 2002 14:44:55 -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 OAA09229
	for <disman@dorothy.bmc.com>; Fri, 21 Jun 2002 14:44:47 -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 g5LLg0S16700
	for <disman@dorothy.bmc.com>; Fri, 21 Jun 2002 16:42:00 -0500 (CDT)
Received: from inf.ufpr.br (unknown [200.17.212.164])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id A0CCE20EFDA
	for <disman@dorothy.bmc.com>; Fri, 21 Jun 2002 16:46:19 -0500 (CDT)
Received: (qmail 30165 invoked from network); 21 Jun 2002 21:46:18 -0000
Received: from giselda.inf.ufpr.br (elias@200.17.212.179)
  by caco.inf.ufpr.br with SMTP; 21 Jun 2002 21:46:18 -0000
Received: by giselda.inf.ufpr.br (sSMTP sendmail emulation); Fri, 21 Jun 2002 18:47:23 -0300
From: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>
Subject: Re: Disman in Yokohama
In-Reply-To: <2E12619580C0D1118C6400805F9F4C950D7CF16C@nj7460exch001u.ho.lucent.com>
 from "Lam, Hing-Kam (Kam)" at "Jun 21, 2002 10:10:37 am"
To: disman@dorothy.bmc.com
Date: Fri, 21 Jun 2002 18:47:23 -0300 (BRT)
Cc: "'Randy Presuhn'" <rpresuhn@dorothy.bmc.com>, elias@inf.ufpr.br
X-Mailer: ELM [version 2.4ME+ PL66 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20020621214619.A0CCE20EFDA@mx-us-hou-1-int.bmc.com>
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,

The clustering/replication document "draft-aldri-disman-replication-mib-01.txt"
has been submitted on June 19 and is available at

http://www.ietf.org/internet-drafts/draft-aldri-disman-replication-mib-01.txt

(Sorry we hadn't submitted it before!)

I would like to repeat the advantage of using replication for monitoring: you
have a systematic fault-tolerant fault-monitoring approach. 

If one of the key functions of network management is fault management, 
monitoring must be fault-tolerant! 

Please, take a look at the document! We are sure there is a contribution
there, but we need your interest and feedback. If there is interest, we
would like to ask Randy if there could possibly be a little slot for
discussion in Yokohama...

Cheers,

Elias


From owner-disman@dorothy.bmc.com  Fri Jun 21 18:40:56 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 SAA03232
	for <disman-archive@odin.ietf.org>; Fri, 21 Jun 2002 18:40:54 -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 g5LMidh03192;
	Fri, 21 Jun 2002 17:44:39 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA09473
	for disman-list; Fri, 21 Jun 2002 15:38:23 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA09465
	for disman@dorothy.bmc.com; Fri, 21 Jun 2002 15:38:18 -0700 (PDT)
Date: Fri, 21 Jun 2002 15:38:18 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206212238.PAA09465@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Re: Disman in 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 -

> From: "Elias Procopio Duarte Jr." <elias@inf.ufpr.br>
> Subject: Re: Disman in Yokohama
> To: disman@dorothy.bmc.com
> Date: Fri, 21 Jun 2002 18:47:23 -0300 (BRT)
> Cc: "'Randy Presuhn'" <rpresuhn@dorothy.bmc.com>, elias@inf.ufpr.br
> Message-Id: <20020621214640.5891B1FF035@mx-us-hou-2-int.bmc.com>
...
> Please, take a look at the document! We are sure there is a contribution
> there, but we need your interest and feedback. If there is interest, we
> would like to ask Randy if there could possibly be a little slot for
> discussion in Yokohama...
...

Thanks for the contribution.  Discussion on this mailing list
is appropriate and encouraged.  Our priority for Yokohama
must be finishing off our current work items.  Loa Andersson
put it well:

   It is not the purpose of a WG session to have presentation
   of the content of a document.  It is assumed that all
   attendees will have read the drafts in advance of the
   meeting.

   For documents that are work-in-progress, the presentation
   should cover issues resolved since the last draft followed
   by open issues and controversial topics with the intent
   to reach a resolution of said issues and topics.

   For new work items, the presentation should focus on what
   the problems is and why it is necessary for the work group
   to address it.  Further it should be either shown how it
   falls within the existing charter or why and how the charter
   should be extended to encompass it....

In short, meeting time is for the resolution of issues that
we haven't brought to closure on the mailing list.

 ------------------------------------------------------
 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  Sun Jun 23 11:08:42 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 LAA28140
	for <disman-archive@odin.ietf.org>; Sun, 23 Jun 2002 11:08:41 -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 g5NFBbx00864;
	Sun, 23 Jun 2002 10:11:37 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id IAA13901
	for disman-list; Sun, 23 Jun 2002 08:03: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 IAA13896
	for <disman@dorothy.bmc.com>; Sun, 23 Jun 2002 08:03:09 -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 g5NF0Hr25124
	for <disman@dorothy.bmc.com>; Sun, 23 Jun 2002 10:00:21 -0500 (CDT)
Received: from monsoon.mail.pipex.net (unknown [158.43.128.69])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 6FF7C20EFC9
	for <disman@dorothy.bmc.com>; Sun, 23 Jun 2002 10:04:42 -0500 (CDT)
Received: (qmail 7061 invoked from network); 23 Jun 2002 15:04:41 -0000
Received: from useraq34.uk.uudial.com (HELO tom3) (62.188.136.94)
  by smtp-1.dial.pipex.com with SMTP; 23 Jun 2002 15:04:41 -0000
Message-ID: <026401c21ac6$f11aafe0$0301a8c0@tom3>
Reply-To: "Tom Petch" <nwnetworks@dial.pipex.com>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, <David.Partain@ericsson.com>,
        "Randy Presuhn" <rpresuhn@dorothy.bmc.com>,
        "disman" <disman@dorothy.bmc.com>
Subject: Re: Alarm #38, #43 - trap/notification varbind and timestamps
Date: Sun, 23 Jun 2002 15:46:17 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit

Yes, Randy's suggestion is an improvement; also simple, logical and as
you
rightly say, in line with RFC2576.

(and yes, David,  I do know the details of trap PDUs in RFC1157,
RFC1448, RFC1905 etc :-)

Tom Petch, Network Consultant
nwnetworks@dial.pipex.com

-----Original Message-----
From: Romascanu, Dan (Dan) <dromasca@avaya.com>
To: David.Partain@ericsson.com <David.Partain@ericsson.com>; Randy
Presuhn <rpresuhn@dorothy.bmc.com>; disman@dorothy.bmc.com
<disman@dorothy.bmc.com>
Date: 19 June 2002 08:59
Subject: RE: Alarm #38, #43 - trap/notification varbind and timestamps


>
>
>> -----Original Message-----
>> From: David Partain [mailto:David.Partain@ericsson.com]
>> Sent: Wednesday, June 19, 2002 10:13 AM
>> To: Randy Presuhn; disman@dorothy.bmc.com
>> Subject: Re: Alarm #38, #43 - trap/notification varbind and
timestamps
>>
>>
>> Hi all,
>>
>> > > > On Thursday 13 June 2002 19.14, Tom Petch wrote:
>> > > > I believe the same index should retrieve the same
>> value, regardless of
>> > > > v1 or v2 ie 1 for sysUpTime, 2 for SNMPTrapOID etc.  It
>> is simple., it
>> > > > is logical.  But I am not clear from the text if that
>> is an option you
>> > > > are offering me  !
>>
>> I responded:
>> > > There is no varbind holding sysUpTime.0 or SNMPTrapOID in
>> > > an SNMPv1 trap.  They are embedded in the message wrapper.
>> > > As such, what you are asking for is not possible.
>> > >
>> > > Since the first two VarBinds in a v2c/v3 trap/inform somewhat
>> > > approximate information that's in the message wrapper for
>> > > SNMPv1 traps, I thought Sharon's proposed text was just fine
>> > > (I removed the "real" from "real varbinds" since I don't know
>> > > how to send a "fake" varbind).
>> > >
>> > > That is:
>> > >
>> > >  "For SNMPv1 traps, a 1 indicates the first varbind. For
>> > >  v2Traps and Informs, a 1 indicates the first varbind after
>> > >  the required varbinds of sysUptime and SNMPTrapOID."
>>
>> Then, Randy P. wrote:
>>
>> > The same logic leads me, as a technical contributor, down a
>> > very different path.
>> >
>> > In order to avoid losing information and to maintain the
>> > valuable distinction between the notification and the active
>> > alarm's time stamps, I would suggest that we follow the RFC 2576
>> > rules (section 3.1) so that everything is represented as though
>> > it had arrived in RFC 1905 format.  I think this is ultimately
>> > simpler than introducing a new set of rules peculiar to this
>> > MIB to treat everything as though it were SNMPv1.
>>
>> That's absolutely fine with me.  In that case, the DESCRIPTION
>> for alarmModelVarbindIndex needs to explain this.  The issue
>> remains that if that holds a value of 2, and that's going to
>> refer to the trap OID even if the incoming notification is a v1
>> trap, then there must be some information in this description
>> that states that.  Otherwise, I think there's a strong risk for
>> confusion.
>>
>> How about this as a replacement for the second paragraph of
>> the DESCRIPTION:
>>
>>   "Note that the value of alarmModelVarbindIndex assumes
>>   the existence of the first two obligatory varbinds in
>>   the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0
>>   and snmpTrapOID.0).  That is, a value of 1 refers to
>>   sysUpTime.0, and a value of 3 refers to the first varbind
>>   after snmpTrapOID.0.
>>
>>   If the incoming notification is instead an SNMPv1 Trap-PDU and
>>   the value of alarmModelVarbindIndex is 1 or 2, an appropriate
>>   value for sysUpTime.0 or snmpTrapOID.0 shall be determined
>>   by using the rules in section 3.1 of [appropriate reference
>>   for RFC2576]."
>>
>> That way, a 1 always means sysUpTime and a 3 always means the
>> first "real" varbind.
>>
>> Did I understand what you want?  Does this work?
>
>I think it does. Regards, Dan
>




From owner-disman@dorothy.bmc.com  Mon Jun 24 18:42:14 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 SAA05808
	for <disman-archive@odin.ietf.org>; Mon, 24 Jun 2002 18: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 g5OMiaB03008;
	Mon, 24 Jun 2002 17:44:36 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA19420
	for disman-list; Mon, 24 Jun 2002 15:35: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 OAA19307
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 14:56: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 g5OLrtD18668
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 16:53:55 -0500 (CDT)
Received: from sj-msg-core-1.cisco.com (unknown [171.71.163.11])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 1128C20EFAD
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 16:58:21 -0500 (CDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g5OLwFdg011887;
	Mon, 24 Jun 2002 14:58:16 -0700 (PDT)
Received: from niraj-w2k3.cisco.com (dhcp-171-71-137-37.cisco.com [171.71.137.37]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA20091; Mon, 24 Jun 2002 14:58:14 -0700 (PDT)
Message-Id: <4.3.2.7.2.20020624133218.06849d48@mira-linc3-1.cisco.com>
X-Sender: niraj@mira-linc3-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 24 Jun 2002 14:58:14 -0700
To: disman@dorothy.bmc.com
From: Niraj Gopal <niraj@cisco.com>
Subject: Internet Draft for table modifications tracking MIB...
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've authored a MIB to track modifications in other MIB
tables. As you know, NMSes (Network Management
Stations) usually poll these MIB tables at regular intervals
to gather  data, and compare it with the data from earlier
polls to determine if anything significant has changed.

Some of these tables can be huge (e.g., a core router's
routing table might have tens of thousands of entries),
and often little or none of the data varies between
polls. Bandwidth and CPU are wasted in uselessly
transferring data.

To minimize this waste, this MIB allows an NMS to
register for "change monitoring" in the tables it's
interested in. This MIB then tracks changes in the
registered tables, allowing the NMS to poll one table
to determine if others need to be polled. The MIB is
flexible enough to allow the NMS to track changes in
only a few objects in the table coz sometimes stats
info (counters etc.) is also included along with the
config  info in single MIB table.

This MIB keeps track of all changes, including adding
a new row, deletion of a row, and modification of an
object in a row. It can also be configured to send
change notifications to an NMS.

Thus, by polling this table and/or listening to this MIB's
notifications, the NMS can find out which tables have
changed since the last poll and choose to poll only those
tables instead of polling all tables at fixed intervals.

This MIB has been in limited use in Cisco for more than
a year and has proved useful in reducing the time required
to synchronize the config data between the NMS and the
NE especially when the config data is huge and the number
of managed NEs is very large. There is also a Cisco patent
pending against this MIB.

I unknowingly missed the deadline for submitting this ID
by a few hours and will make it a real ID after Yokohama
meeting. Randy has been kind enough to put it on the
DISMAN WG's ftp site at:

ftp://amethyst.bmc.com/pub/disman/ietf54/draft-niraj-tmt-mib-00.txt

Please send me your comments.

Thanks&Regards,
-Niraj





From owner-disman@dorothy.bmc.com  Mon Jun 24 21:47:14 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 VAA09633
	for <disman-archive@odin.ietf.org>; Mon, 24 Jun 2002 21:47: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 g5P1nnX03276;
	Mon, 24 Jun 2002 20:49:49 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id SAA19949
	for disman-list; Mon, 24 Jun 2002 18:43:05 -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 SAA19944
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 18:43:01 -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 g5P1eCL28501
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 20:40:12 -0500 (CDT)
Received: from zcars04f.ca.nortel.com (unknown [47.129.242.57])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id 7B9D820EFAD
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 20:44:38 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g5P1iTf12544
	for <disman@dorothy.bmc.com>; Mon, 24 Jun 2002 21:44:33 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYBYDPN>; Mon, 24 Jun 2002 21:44:29 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403DF06E7@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: Alarm #40 - Resource Identification
Date: Mon, 24 Jun 2002 21:44:23 -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

I did a rather serious "oops" to my computer, so I wasn't able
to send this out sooner.

Alarm #40 Identify where to find resource identifier in notification
  Option 1) Document how knowledge of the given notifications is assumed
  Option 2) Add Sharon's suggestion which allows raise/clear correlation 
            in most cases
  Option 3) Add Randy's suggestion which allows algorithmic determination
            of resourceId from notification varbinds in most cases.

Solution: Option 3)

Add two new objects which can be used both by the agent to calculate the
resource ID and by the manager to determine when alarms are against
the same resource.

   alarmModelVarbindSubtree  OBJECT-TYPE
      SYNTAX  OBJECT IDENTIFIER
      MAX-ACCESS   read-create
      STATUS       current
      DESCRIPTION
        "The name portion of each VarBind in the notification,
         in order, is compared to the value of this object.
         If the name is equal to or a subtree of the value
         of this object, for purposes of computing the value
         of AlarmActiveResourceID the 'prefix' will be the
         matching portion, and the 'indexes' will be any
         remainder.  The examination of varbinds ends with
         the first match.
        "
      DEFVAL { {0 0} }
      ::= { whatever }

   alarmModelResourcePrefix  OBJECT-TYPE
      SYNTAX  OBJECT IDENTIFIER
      MAX-ACCESS   read-create
      STATUS       current
      DESCRIPTION
        "The value of AlarmActiveResourceID is computed
         by appending any indexes extracted in accordance
         with the description of alarmModelVarbindSubtree
         onto the value of this object.  If this object's
         value is 0.0, then the 'prefix' extracted is used
         instead.
        "
      DEFVAL { {0 0} }
      ::= { whatever }

Three concrete examples:

1) if I receive an authenticationFailure, I'd like the
   resource to be 1.3.6.1.6.3.15.1.1, so I configure:
        alarmModelVarbindSubtree = 0.0
        alarmModelResourcePrefix = 1.3.6.1.6.3.15.1.1

2) if I receive a linkDown that contains SDLC physicalFailures
   statistics, I'd like to have my alarm refer to the right ifEntry:
        alarmModelVarbindSubtree = 1.3.6.1.2.1.41.1.1.3.1.1
        alarmModelResourcePrefix = 1.3.6.1.2.1.2.2.1.1

3) if the first varbind is always going to point to the
   right thing, then I just:
        alarmModelVarbindSubtree = 0.0
        alarmModelResourcePrefix = 0.0

Sharon's attempt at pseudo code:

  if ( alarmModelResourcePrefix == 0.0 )
     resourceId = fullExtractedFirstMatch(varbinds,alarmModeVarbindSubtree)
  else {
     resourceId = alarmModelResoucePrefix + 
 
extractInstanceFromFirstMatch(varbinds,alarmModelVarbindSubree)
  }
Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Tue Jun 25 16:09:22 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 QAA26469
	for <disman-archive@lists.ietf.org>; Tue, 25 Jun 2002 16:09:22 -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 g5PKD7803627;
	Tue, 25 Jun 2002 15:13:07 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA22684
	for disman-list; Tue, 25 Jun 2002 13:05:47 -0700 (PDT)
Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA22679
	for <Disman@dorothy.bmc.com>; Tue, 25 Jun 2002 13:05:42 -0700 (PDT)
Received: from ec03-hou.bmc.com (localhost [127.0.0.1])
	by creeper.bmc.com (8.10.2/8.10.2) with ESMTP id g5PK79W12817
	for <Disman@dorothy.bmc.com>; Tue, 25 Jun 2002 15:07:09 -0500 (CDT)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2653.19)
	id <M9K7D1CM>; Tue, 25 Jun 2002 15:07:25 -0500
Message-ID: <D77353F1D8FCD411AC3400105A640BB50380ECBA@es01-sjc.bmc.com>
From: "Presuhn, Randy" <Randy_Presuhn@bmc.com>
To: "'Disman@dorothy.bmc.com'" <Disman@dorothy.bmc.com>
Subject: Disman time slot in Yokohama
Date: Tue, 25 Jun 2002 15:07:24 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by dorothy.bmc.com id NAA22680
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 -

We have our time slot!

> From: agenda@ietf.org [mailto:agenda@ietf.org]
> Sent: Tuesday, June 25, 2002 12:56
> To: iesg@ietf.org; wgchairs@ietf.org; bofchairs@ietf.org
> Cc: dinaras@ietf.org
> Subject: 54th IETF WG/BOF Scheduling - *** FINAL Agenda ***
...
> WEDNESDAY, July 17, 2002
...
> 0900-1130 Morning Sessions
> APP     simple    SIP for Instant Messaging and Presence 
> Leveraging Extensions WG
> OPS     disman    Distributed Management WG
> OPS     ngtrans   Next Generation Transition WG
> RTG     manet     Mobile Ad-hoc Networks WG
> SUB     ccamp     Common Control and Measurement Plane WG
> TSV     cats      Control of ASR and TTS Servers BOF
> TSV     rohc      Robust Header Compression WG
...

 ------------------------------------------------------
 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  Wed Jun 26 13:40:37 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 NAA01862
	for <disman-archive@lists.ietf.org>; Wed, 26 Jun 2002 13:40:36 -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 g5QHi0o13160;
	Wed, 26 Jun 2002 12:44:00 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA27731
	for disman-list; Wed, 26 Jun 2002 10:35:59 -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 KAA27726
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 10:35:54 -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 g5QHX4O14605
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 12:33:04 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 5EBA81FF017
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 12:37:31 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g5QHbFn21087;
	Wed, 26 Jun 2002 13:37:15 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYBZB57>; Wed, 26 Jun 2002 13:37:15 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403E53649@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Cc: David.Partain@ericsson.com
Subject: RE: Alarm #35, #36 - Varbinds to alarmActive Notification
Date: Wed, 26 Jun 2002 13:37:12 -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

I guess I never responded to this. Yes, that should
be alarmActiveModelPointer. 

You're right. Both notifications need to be changed.

thanks,

Sharon

-----Original Message-----
From: David Partain [mailto:David.Partain@ericsson.com]
Sent: Tuesday, June 18, 2002 8:32 AM
To: Chisholm, Sharon [CAR:NM50:EXCH]; disman@dorothy.bmc.com
Subject: Re: Alarm #35, #36 - Varbinds to alarmActive Notification


Hi,

Thanks for the work on getting these issues closed out.

> Alarm #36 Varbinds to alarmActiveState notifications
>   Using explicit varbinds if model, state and name or using
>   alarmActiveModelPointer
>   Option 1) varbind alarmListName, alarmModelIndex, alarmModelState
>   Option 2) varbind alarmActiveModelPointer
>
> Solution: Replace alarmModelIndex and alarmModelState
>   in alarmActiveState notification with alarmModelPointer.

Actually, I _think_ you mean alarmActiveModelPointer, right?

NOTE:  Your suggestion doesn't provide a change to
alarmClearState, which has exactly the same problem as
alarmActiveState.

-------------------------------------------------------------------
Change 1:

So, just to make sure I have it right, you're proposing that:

   alarmActiveState NOTIFICATION-TYPE
    OBJECTS     { alarmModelIndexVarbind,
                  alarmModelStateVarbind,
                  alarmActiveResourceId }
    STATUS      current
    DESCRIPTION
       "An instance of the alarm indicated by
       alarmModelIndexVarbind has been raised
       against the entity indicated by
       alarmActiveResourceType and alarmACtiveResourceId."
    ::= { alarmNotifications 2 }

becomes

   alarmActiveState NOTIFICATION-TYPE
    OBJECTS     { alarmActiveModelPointer,
                  alarmActiveResourceId }
    STATUS      current
    DESCRIPTION
       "An instance of the alarm modeled in the model table
       pointed to by alarmActiveModelPointer has been raised
       against the entity indicated by alarmActiveResourceId."
    ::= { alarmNotifications 2 }


-------------------------------------------------------------------
Change 2:

Since alarmClearState also has to be fixed, I suggest that:

   alarmClearState NOTIFICATION-TYPE
      OBJECTS     { alarmModelIndexVarbind,
                    alarmActiveResourceId }
      STATUS      current
      DESCRIPTION
        "An instance of the alarm indicated by
        alarmModelIndexVarbind has been cleared against
        the entity indicated by alarmActiveResourceType
        and alarmACtiveResourceId."
      ::= { alarmNotifications 3 }

be changed to:

   alarmClearState NOTIFICATION-TYPE
      OBJECTS     { alarmActiveModelPointer,
                    alarmActiveResourceId }
      STATUS      current
      DESCRIPTION
        "An instance of the alarm modeled in the model table row
        pointed to by alarmActiveModelPointer has been cleared
        against the entity indicated by alarmActiveResourceId."
      ::= { alarmNotifications 3 }

Cheers,

dlp



From owner-disman@dorothy.bmc.com  Wed Jun 26 17:19:46 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 RAA11516
	for <disman-archive@lists.ietf.org>; Wed, 26 Jun 2002 17:19:45 -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 g5QLNIS24691;
	Wed, 26 Jun 2002 16:23:18 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA28948
	for disman-list; Wed, 26 Jun 2002 14:16:36 -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 OAA28943
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 14:16:32 -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 g5QLDfC22080
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 16:13:41 -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 1A7CE1FF007
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 16:18:08 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g5QLHqI19503
	for <disman@dorothy.bmc.com>; Wed, 26 Jun 2002 17:17:52 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYBZG67>; Wed, 26 Jun 2002 17:17:52 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403E53975@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: RE: Alarm #31, #33, #44 - Probable Causes
Date: Wed, 26 Jun 2002 17:17:51 -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

An alternative solution for #31 which would both make ITU study group 4
happy and make it easier for those to already support a particular 
flavour of probably cause in their network - M.3100, X.733 or X.736 -
would be to include all the values of each flavour. There's a bit of
duplication, which could cause confusion, but removing the duplicates
also has the potential to cause confusion as well.

Here's a quote from somewhere:
"ITU probable cause values for alarms are currently assigned as per 
M.3100-1995 (1-254), X.733-1992 (256-287), and X.736-1992 (288-303)."

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:NM50:EXCH] 
Sent: Monday, June 03, 2002 7:36 AM
To: disman@dorothy.bmc.com
Subject: Alarm #31, #33, #44 - Probable Causes


hi

The following are all related to Probable Causes:

Alarm #31 Duplicate Probable causes
  Solution:
    remove: fireDetected (266)
            floodDetected (267)
            configurationOrCustomizationError(260)
            underlyingResourceUnavailable(287)
  and possibly 
  toxicGas (133) & toxicLeakDetected (286)

Alarm #44 Probable Cause corrections from ITU Study group 4

  Solution: Currently the reserved space for ITU values is < 255.
            Increase this to 1024, to allow more ITU defined values.

            Change text to clarify that "ITU probable cause values 
            for alarms are currently assigned as per M.3100-1995 (1-254), 
            X.733-1992 (256-287), and X.736-1992 (288-303)." 

            Add missing value 158 (reinitialized) 


Alarm #33 Disman Immortality
  Text in the IANA considerations section suggests we'll still be
  around for IETF 34523421, held in the Mars colonies.
  Solution:
  Change text to the following:
  "Over time, there will be a need to add new IANAItuProbableCause
   enumerated values for new probable causes. The Internet
   Assigned Number Authority (IANA) is responsible for the assignment of
   all Internet numbers, including various SNMP-related numbers, and
   specifically, new IANAItuProbableCause values. Values of 
   IANAItuProbableCause less than 255 are reserved for causes
   that correspond to ITU probable cause.

   The following shall be used as the initial values, but the latest
   values for these textual conventions should be obtained from IANA:"


Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario


From owner-disman@dorothy.bmc.com  Wed Jun 26 18:47:13 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 SAA14322
	for <disman-archive@lists.ietf.org>; Wed, 26 Jun 2002 18:47: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 g5QMoJS01887;
	Wed, 26 Jun 2002 17:50:19 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA00256
	for disman-list; Wed, 26 Jun 2002 15:43:43 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id PAA00250
	for disman@dorothy.bmc.com; Wed, 26 Jun 2002 15:43:40 -0700 (PDT)
Date: Wed, 26 Jun 2002 15:43:40 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206262243.PAA00250@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Other Event / Alarm MIBs
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 -

Take a look at draft-deketelaere-pktc-ipcdn-eventmess-00.txt

 ------------------------------------------------------
 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  Wed Jun 26 19:46:42 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 TAA15988
	for <disman-archive@lists.ietf.org>; Wed, 26 Jun 2002 19:46: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 g5QNo5p21509;
	Wed, 26 Jun 2002 18:50:05 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA05393
	for disman-list; Wed, 26 Jun 2002 16:43:34 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA05387
	for disman@dorothy.bmc.com; Wed, 26 Jun 2002 16:43:29 -0700 (PDT)
Date: Wed, 26 Jun 2002 16:43:29 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206262343.QAA05387@dorothy.bmc.com>
To: disman@dorothy.bmc.com
Subject: Yokohama Deadline
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: <200206211138.HAA08404@ietf.org>
> To: IETF-Announce: ;
> From: Internet-Drafts Administrator <internet-drafts@ietf.org>
> Subject: Internet-Draft Cutoff Dates for Yokohama, Japan 
> Date: Fri, 21 Jun 2002 07:38:41 -0400
...
> All revised Internet-Draft submissions must be submitted by Monday,
> July 1st, 2002 at 09:00 US-EDT (eastern daylight time). 
...

Yes, that's SIX O'CLOCK Monday morning, Pacific daylight time.
Don't play "chicken" with the secretariat!

 ------------------------------------------------------
 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  Thu Jun 27 09:03: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 JAA15859
	for <disman-archive@odin.ietf.org>; Thu, 27 Jun 2002 09:03: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 g5RD6dt04850;
	Thu, 27 Jun 2002 08:06:39 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id FAA07027
	for disman-list; Thu, 27 Jun 2002 05:58:40 -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 FAA07022
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 05:58:36 -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 g5RCtj700656
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 07:55:45 -0500 (CDT)
Received: from mogwai.dataductus.se (unknown [213.199.99.186])
	by mx-us-hou-1-int.bmc.com (Postfix) with SMTP id A228A20EFC1
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 08:00:11 -0500 (CDT)
Received: (from nobody@localhost)
	by mogwai.dataductus.se (8.11.6/8.11.6) id g5RCs7626339
	for disman@dorothy.bmc.com; Thu, 27 Jun 2002 14:54:07 +0200
X-Authentication-Warning: mogwai.dataductus.se: nobody set sender to stefan.wallin@dataductus.se using -f
Received: from 156.153.255.134 ( [156.153.255.134])
	as user ddskswa@imap.dataductus.se by webmail.dataductus.se with HTTP;
	Thu, 27 Jun 2002 14:54:07 +0200
Message-ID: <1025182447.3d1b0aef0a760@webmail.dataductus.se>
Date: Thu, 27 Jun 2002 14:54:07 +0200
From: Stefan Wallin <stefan.wallin@dataductus.se>
To: disman@dorothy.bmc.com
Subject: traces of "alarmActiveResourceType"
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1
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!
Solutions on the items especially resource var-bind #40 looks OK.

Just a detail, there are traces of alarmActiveResourceType in description 
clauses of the notifications.

".... alarmModelIndexVarbind has been cleared against
        the entity indicated by alarmActiveResourceType
        and alarmACtiveResourceId...."



Sorry if this has been noted already, have not been able to follow the mailing 
list 100%

Good luck in Yokohama!
/stefan

   
-- 
Data Ductus Nord AB
stefan.wallin@dataductus.se
tel: +46 (0)70 5233262


From owner-disman@dorothy.bmc.com  Thu Jun 27 14:53:41 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 OAA08900
	for <disman-archive@odin.ietf.org>; Thu, 27 Jun 2002 14:53:41 -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 g5RIugF15324;
	Thu, 27 Jun 2002 13:56:42 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA08527
	for disman-list; Thu, 27 Jun 2002 11:49:28 -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 LAA08522
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 11:49:24 -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 g5RIkYk24885
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 13:46:34 -0500 (CDT)
Received: from zcars04e.ca.nortel.com (zcars04e.nortelnetworks.com [47.129.242.56])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id A9F0E1FF027
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 13:51:01 -0500 (CDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g5RIok902671
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 14:50:46 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <KTYBZWDD>; Thu, 27 Jun 2002 14:50:45 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403EAFD16@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: disman@dorothy.bmc.com
Subject: RFC3014: Cross-reference typo
Date: Thu, 27 Jun 2002 14:50:35 -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

I just did a quick look back and I have not seen this discussed. Apologies
if it has been.

Section 6 of RFC3014 refers to section 3.1.2, but it should
be section 2.1.2.

...
  2.1.2. Security 
...
  6. Security Considerations 
  Security issues are discussed in Section 3.1.2

Sharon Chisholm
Preside Management
Nortel Networks
Ottawa, Ontario



From owner-disman@dorothy.bmc.com  Thu Jun 27 15:40:23 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 PAA11724
	for <disman-archive@odin.ietf.org>; Thu, 27 Jun 2002 15:40:23 -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 g5RJi4I04111;
	Thu, 27 Jun 2002 14:44:04 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA08660
	for disman-list; Thu, 27 Jun 2002 12:37: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 MAA08655
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 12:37:35 -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 g5RJYjh21848
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 14:34:45 -0500 (CDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by mx-us-hou-2-int.bmc.com (Postfix) with SMTP id 3D1EA1FF027
	for <disman@dorothy.bmc.com>; Thu, 27 Jun 2002 14:39:12 -0500 (CDT)
Received: from mira-sjcm-2.cisco.com (IDENT:mirapoint@mira-sjcm-2.cisco.com [171.69.24.14])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g5RJcvdg010630;
	Thu, 27 Jun 2002 12:38:57 -0700 (PDT)
Received: from ramkw2k (dhcp-128-107-165-172.cisco.com [128.107.165.172])
	by mira-sjcm-2.cisco.com (Mirapoint)
	with SMTP id ADF37019;
	Thu, 27 Jun 2002 12:38:48 -0700 (PDT)
From: "Ram Kavasseri" <ramk@cisco.com>
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, <disman@dorothy.bmc.com>
Subject: RE: RFC3014: Cross-reference typo
Date: Thu, 27 Jun 2002 12:38:46 -0700
Message-ID: <GLEHIDGKIFNBEONBMOLCAEFNCAAA.ramk@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3549C09B853DD5119B540002A52CDD3403EAFD16@zcard0ka.ca.nortel.com>
Importance: Normal
Sender: owner-disman@dorothy.bmc.com
Precedence: bulk
List-Id: IETF disman Working Group mailing list <disman.dorothy.bmc.com>
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: owner-disman@dorothy.bmc.com
> [mailto:owner-disman@dorothy.bmc.com]On Behalf Of Sharon Chisholm
> Sent: Thursday, June 27, 2002 11:51 AM
> To: disman@dorothy.bmc.com
> Subject: RFC3014: Cross-reference typo
>
>
> hi
>
> I just did a quick look back and I have not seen this discussed. Apologies
> if it has been.
>
> Section 6 of RFC3014 refers to section 3.1.2, but it should
> be section 2.1.2.
>

Will fix this.

Ram

> ...
>   2.1.2. Security
> ...
>   6. Security Considerations
>   Security issues are discussed in Section 3.1.2
>
> Sharon Chisholm
> Preside Management
> Nortel Networks
> Ottawa, Ontario
>
>



