From disman-bounces@ietf.org Fri Jun 03 17:01:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DeJHv-0001MK-Cs; Fri, 03 Jun 2005 17:01:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DeJHq-0001M9-MR
	for disman@megatron.ietf.org; Fri, 03 Jun 2005 17:01:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14480
	for <disman@ietf.org>; Fri, 3 Jun 2005 17:01:00 -0400 (EDT)
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeJc8-0001Sf-8i
	for disman@ietf.org; Fri, 03 Jun 2005 17:22:01 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j53L0pa22168
	for <disman@ietf.org>; Fri, 3 Jun 2005 23:00:51 +0200 (CEST)
Received: from [10.61.64.27] (ams-clip-vpn-dhcp27.cisco.com [10.61.64.27])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j53L0nF06381
	for <disman@ietf.org>; Fri, 3 Jun 2005 23:00:49 +0200 (CEST)
Message-ID: <42A0C501.1040003@cisco.com>
Date: Fri, 03 Jun 2005 23:00:49 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Disman (E-mail)" <disman@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [Disman] Some editorial proposals for
	draft-ietf-disman-event-mib-v2-04.txt
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Dear all,

The draft is expired, so ... 
http://www.watersprings.org/pub/id/draft-ietf-disman-event-mib-v2-04.txt

Here are three (minor) editorial proposals I would like to insert

1. Section 3. Relationship to Other MIBs

   "Event MIB triggers maintain the RMON handling of thresholds and add the concept
   of booleans."

I would propose:
   "Event MIB triggers maintain the RMON handling of thresholds and add the concept
   of booleans and existence."
AFAIK, RMON doesn't have the concept of "existence"



2. Section 4.  MIB Sections

   "The MIB has four sections: triggers, objects, events, and
   notifications.  Triggers define the conditions that lead to events.
   Events may cause notifications."

I would propose:
   "The MIB has four sections: triggers, objects, events, and
   notifications.  Triggers define the conditions that lead to events.
   Events may cause notifications and/or may set a MIB object."



3. The MIB is full of mte*. I think the meaning of it is somehow hidden in the MIB:
-- Management Triggered Event (MTE) objects

I would propose to modify the MIB description from :
    DESCRIPTION
     "The MIB module for defining event triggers and actions
     for network management purposes.
To:
    DESCRIPTION
     "The MIB module for defining Managed Triggered Event (MTE) and actions
     for network management purposes.


Any objections?

Regards, Benoit.




From disman-bounces@ietf.org Fri Jun 03 17:53:23 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DeK6V-0004w7-1O; Fri, 03 Jun 2005 17:53:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DeK6T-0004vx-Ea
	for disman@megatron.ietf.org; Fri, 03 Jun 2005 17:53:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17564
	for <disman@ietf.org>; Fri, 3 Jun 2005 17:53:18 -0400 (EDT)
Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeKQk-0002Xw-Fr
	for disman@ietf.org; Fri, 03 Jun 2005 18:14:20 -0400
Received: from h-68-166-37-204.snvacaid.dynamic.covad.net ([68.166.37.204]
	helo=oemcomputer)
	by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DeK6P-0005tY-00
	for disman@ietf.org; Fri, 03 Jun 2005 17:53:17 -0400
Message-ID: <002101c56887$12c4fae0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
References: <200503092221.55706.david.partain@ericsson.com>	<4240974F.50906@cisco.com>
	<001601c56645$33fe2f40$7f1afea9@oemcomputer>
	<42A0C4DC.6080305@cisco.com>
Subject: Re: [Disman] Status of the Event MIB?
Date: Fri, 3 Jun 2005 14:56:17 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Benoit Claise" <bclaise@cisco.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "Ramanathan Kavasseri" <ramk@cisco.com>
> Sent: Friday, June 03, 2005 2:00 PM
> Subject: Re: [Disman] Status of the Event MIB?
...
> >Any word on when this will be posted?
> >
> >
> Working on it now.
>
> Regards, Benoit.
...

Thanks for the update.
Does anyone have any response to Dave Shields' comments of 2005-03-30?

Randy







From disman-bounces@ietf.org Fri Jun 03 18:00:38 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DeKDW-0006IS-GK; Fri, 03 Jun 2005 18:00:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DeKDU-0006IN-Ma
	for disman@megatron.ietf.org; Fri, 03 Jun 2005 18:00:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17935
	for <disman@ietf.org>; Fri, 3 Jun 2005 18:00:33 -0400 (EDT)
Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeKXn-0002fp-QN
	for disman@ietf.org; Fri, 03 Jun 2005 18:21:36 -0400
Received: from h-68-166-37-204.snvacaid.dynamic.covad.net ([68.166.37.204]
	helo=oemcomputer)
	by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DeKDS-0007at-00
	for disman@ietf.org; Fri, 03 Jun 2005 18:00:34 -0400
Message-ID: <002801c56888$18d6d2e0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
References: <42A0C501.1040003@cisco.com>
Subject: Re: [Disman] Some editorial proposals
	fordraft-ietf-disman-event-mib-v2-04.txt
Date: Fri, 3 Jun 2005 15:03:38 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

(as a technical contributor)

> From: "Benoit Claise" <bclaise@cisco.com>
> To: "Disman (E-mail)" <disman@ietf.org>
> Sent: Friday, June 03, 2005 2:00 PM
> Subject: [Disman] Some editorial proposals fordraft-ietf-disman-event-mib-v2-04.txt
...
> 1. Section 3. Relationship to Other MIBs
>
>    "Event MIB triggers maintain the RMON handling of thresholds and add the concept
>    of booleans."
>
> I would propose:
>    "Event MIB triggers maintain the RMON handling of thresholds and add the concept
>    of booleans and existence."
> AFAIK, RMON doesn't have the concept of "existence"

I don't think we need this.
See the first paragraph of RFC 2021's definition of TimeFilter.

> 2. Section 4.  MIB Sections
>
>    "The MIB has four sections: triggers, objects, events, and
>    notifications.  Triggers define the conditions that lead to events.
>    Events may cause notifications."
>
> I would propose:
>    "The MIB has four sections: triggers, objects, events, and
>    notifications.  Triggers define the conditions that lead to events.
>    Events may cause notifications and/or may set a MIB object."

Ok, but "and/or" is an abomination.  Also, why is "object" in the singular while
"notifications" is plural?

> 3. The MIB is full of mte*. I think the meaning of it is somehow hidden in the MIB:
> -- Management Triggered Event (MTE) objects
>
> I would propose to modify the MIB description from :
>     DESCRIPTION
>      "The MIB module for defining event triggers and actions
>      for network management purposes.
> To:
>     DESCRIPTION
>      "The MIB module for defining Managed Triggered Event (MTE) and actions
>      for network management purposes.

This seems helpful.

>
> Any objections?
>
> Regards, Benoit.

Randy







From disman-bounces@ietf.org Fri Jun 03 19:16:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DeLOv-00068W-BT; Fri, 03 Jun 2005 19:16:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DeLOu-00068R-Ch
	for disman@megatron.ietf.org; Fri, 03 Jun 2005 19:16:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23816
	for <disman@ietf.org>; Fri, 3 Jun 2005 19:16:25 -0400 (EDT)
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeLjE-0004Jh-Bz
	for disman@ietf.org; Fri, 03 Jun 2005 19:37:28 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j53NGIH29863; Sat, 4 Jun 2005 01:16:18 +0200 (CEST)
Received: from [10.61.64.27] (ams-clip-vpn-dhcp27.cisco.com [10.61.64.27])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j53NGHF21366; Sat, 4 Jun 2005 01:16:17 +0200 (CEST)
Message-ID: <42A0E4BF.6070203@cisco.com>
Date: Sat, 04 Jun 2005 01:16:15 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: [Disman] Some editorial
	proposals	fordraft-ietf-disman-event-mib-v2-04.txt
References: <42A0C501.1040003@cisco.com>
	<002801c56888$18d6d2e0$7f1afea9@oemcomputer>
In-Reply-To: <002801c56888$18d6d2e0$7f1afea9@oemcomputer>
Content-Type: multipart/alternative;
	boundary="------------050300030102020409050801"
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 36fb765c89ed47dab364ab702a78e8fd
Cc: "Disman \(E-mail\)" <disman@ietf.org>
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

This is a multi-part message in MIME format.
--------------050300030102020409050801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Randy,

>Hi -
>
>(as a technical contributor)
>
>  
>
>>From: "Benoit Claise" <bclaise@cisco.com>
>>To: "Disman (E-mail)" <disman@ietf.org>
>>Sent: Friday, June 03, 2005 2:00 PM
>>Subject: [Disman] Some editorial proposals fordraft-ietf-disman-event-mib-v2-04.txt
>>    
>>
>...
>  
>
>>1. Section 3. Relationship to Other MIBs
>>
>>   "Event MIB triggers maintain the RMON handling of thresholds and add the concept
>>   of booleans."
>>
>>I would propose:
>>   "Event MIB triggers maintain the RMON handling of thresholds and add the concept
>>   of booleans and existence."
>>AFAIK, RMON doesn't have the concept of "existence"
>>    
>>
>
>I don't think we need this.
>See the first paragraph of RFC 2021's definition of TimeFilter.
>  
>
Right, but whenever we referred to "RMON handling of thresholds", I 
thought we were referring to the RMON event/alarm (RFC2819), which 
doesn't have the notion of existence?

>  
>
>>2. Section 4.  MIB Sections
>>
>>   "The MIB has four sections: triggers, objects, events, and
>>   notifications.  Triggers define the conditions that lead to events.
>>   Events may cause notifications."
>>
>>I would propose:
>>   "The MIB has four sections: triggers, objects, events, and
>>   notifications.  Triggers define the conditions that lead to events.
>>   Events may cause notifications and/or may set a MIB object."
>>    
>>
>
>Ok, but "and/or" is an abomination.  
>
ok.

>Also, why is "object" in the singular while
>"notifications" is plural?
>  
>
Corrected.

New proposal: Triggers define the conditions that lead to events.  
Events may cause notifications, may set MIB objects, or both.
Is this better?

Thanks for your comment.

Regards, Benoit.

>  
>
>>3. The MIB is full of mte*. I think the meaning of it is somehow hidden in the MIB:
>>-- Management Triggered Event (MTE) objects
>>
>>I would propose to modify the MIB description from :
>>    DESCRIPTION
>>     "The MIB module for defining event triggers and actions
>>     for network management purposes.
>>To:
>>    DESCRIPTION
>>     "The MIB module for defining Managed Triggered Event (MTE) and actions
>>     for network management purposes.
>>    
>>
>
>This seems helpful.
>
>  
>
>>Any objections?
>>
>>Regards, Benoit.
>>    
>>
>
>Randy
>
>  
>


--------------050300030102020409050801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Randy,<br>
<blockquote cite="mid002801c56888$18d6d2e0$7f1afea9@oemcomputer"
 type="cite">
  <pre wrap="">Hi -

(as a technical contributor)

  </pre>
  <blockquote type="cite">
    <pre wrap="">From: "Benoit Claise" <a class="moz-txt-link-rfc2396E" href="mailto:bclaise@cisco.com">&lt;bclaise@cisco.com&gt;</a>
To: "Disman (E-mail)" <a class="moz-txt-link-rfc2396E" href="mailto:disman@ietf.org">&lt;disman@ietf.org&gt;</a>
Sent: Friday, June 03, 2005 2:00 PM
Subject: [Disman] Some editorial proposals fordraft-ietf-disman-event-mib-v2-04.txt
    </pre>
  </blockquote>
  <pre wrap=""><!---->...
  </pre>
  <blockquote type="cite">
    <pre wrap="">1. Section 3. Relationship to Other MIBs

   "Event MIB triggers maintain the RMON handling of thresholds and add the concept
   of booleans."

I would propose:
   "Event MIB triggers maintain the RMON handling of thresholds and add the concept
   of booleans and existence."
AFAIK, RMON doesn't have the concept of "existence"
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I don't think we need this.
See the first paragraph of RFC 2021's definition of TimeFilter.
  </pre>
</blockquote>
Right, but whenever we referred to "RMON handling of thresholds", I
thought we were referring to the RMON event/alarm (RFC2819), which
doesn't have the notion of existence?<br>
<blockquote cite="mid002801c56888$18d6d2e0$7f1afea9@oemcomputer"
 type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">2. Section 4.  MIB Sections

   "The MIB has four sections: triggers, objects, events, and
   notifications.  Triggers define the conditions that lead to events.
   Events may cause notifications."

I would propose:
   "The MIB has four sections: triggers, objects, events, and
   notifications.  Triggers define the conditions that lead to events.
   Events may cause notifications and/or may set a MIB object."
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Ok, but "and/or" is an abomination.  </pre>
</blockquote>
<p class="RFCText">ok.<br>
</p>
<blockquote cite="mid002801c56888$18d6d2e0$7f1afea9@oemcomputer"
 type="cite">
  <pre wrap="">Also, why is "object" in the singular while
"notifications" is plural?
  </pre>
</blockquote>
Corrected.<br>
<br>
New proposal: Triggers define the conditions that lead to events.<span
 style="">&nbsp; </span>Events may cause notifications, may set
MIB objects, or both.<br>
Is this better?<br>
<br>
Thanks for your comment.<br>
<br>
Regards, Benoit.<br>
<blockquote cite="mid002801c56888$18d6d2e0$7f1afea9@oemcomputer"
 type="cite">
  <pre wrap="">
  </pre>
  <blockquote type="cite">
    <pre wrap="">3. The MIB is full of mte*. I think the meaning of it is somehow hidden in the MIB:
-- Management Triggered Event (MTE) objects

I would propose to modify the MIB description from :
    DESCRIPTION
     "The MIB module for defining event triggers and actions
     for network management purposes.
To:
    DESCRIPTION
     "The MIB module for defining Managed Triggered Event (MTE) and actions
     for network management purposes.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
This seems helpful.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Any objections?

Regards, Benoit.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Randy

  </pre>
</blockquote>
<br>
</body>
</html>

--------------050300030102020409050801--




From disman-bounces@ietf.org Fri Jun 03 20:15:53 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DeMKP-00032Y-7v; Fri, 03 Jun 2005 20:15:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DeMKO-00032T-5a
	for disman@megatron.ietf.org; Fri, 03 Jun 2005 20:15:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27475
	for <disman@ietf.org>; Fri, 3 Jun 2005 20:15:50 -0400 (EDT)
Received: from pop-borzoi.atl.sa.earthlink.net ([207.69.195.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeMei-0005We-Gb
	for disman@ietf.org; Fri, 03 Jun 2005 20:36:52 -0400
Received: from h-68-166-37-204.snvacaid.dynamic.covad.net ([68.166.37.204]
	helo=oemcomputer)
	by pop-borzoi.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DeMKI-0006OZ-00
	for disman@ietf.org; Fri, 03 Jun 2005 20:15:46 -0400
Message-ID: <000b01c5689a$fbbc4880$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
References: <42A0C501.1040003@cisco.com><002801c56888$18d6d2e0$7f1afea9@oemcomputer>
	<42A0E4BF.6070203@cisco.com>
Subject: Re: [Disman] Some editorial proposals for
	draft-ietf-disman-event-mib-v2-04.txt
Date: Fri, 3 Jun 2005 17:18:49 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Benoit Claise" <bclaise@cisco.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "Disman (E-mail)" <disman@ietf.org>
> Sent: Friday, June 03, 2005 4:16 PM
> Subject: Re: [Disman] Some editorialproposals fordraft-ietf-disman-event-mib-v2-04.txt
...
> >I don't think we need this.
> >See the first paragraph of RFC 2021's definition of TimeFilter.
> >
> >
> Right, but whenever we referred to "RMON handling of thresholds", I
> thought we were referring to the RMON event/alarm (RFC2819), which
> doesn't have the notion of existence?

I don't know.  I don't feel strongly about this text.

> >>2. Section 4.  MIB Sections
...
> New proposal: Triggers define the conditions that lead to events.
> Events may cause notifications, may set MIB objects, or both.
> Is this better?
...

Much.

Randy







From disman-bounces@ietf.org Fri Jun 03 20:50:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DeMrS-0002RM-Pe; Fri, 03 Jun 2005 20:50:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DeMrR-0002Qg-6H
	for disman@megatron.ietf.org; Fri, 03 Jun 2005 20:50:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29637
	for <disman@ietf.org>; Fri, 3 Jun 2005 20:49:59 -0400 (EDT)
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DeNBm-0006B6-0k
	for disman@ietf.org; Fri, 03 Jun 2005 21:11:02 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j540npH05934
	for <disman@ietf.org>; Sat, 4 Jun 2005 02:49:51 +0200 (CEST)
Received: from [10.61.64.27] (ams-clip-vpn-dhcp27.cisco.com [10.61.64.27])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j540nnF26612
	for <disman@ietf.org>; Sat, 4 Jun 2005 02:49:49 +0200 (CEST)
Message-ID: <42A0FAAA.7080905@cisco.com>
Date: Sat, 04 Jun 2005 02:49:46 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Disman (E-mail)" <disman@ietf.org>
Content-Type: multipart/alternative;
	boundary="------------010103030504010606060203"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Subject: [Disman] draft-ietf-disman-event-mib-v2-05.txt has been posted
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

This is a multi-part message in MIME format.
--------------010103030504010606060203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

A new version of event-mib draft, draft-ietf-disman-event-mib-v2-05.txt, has been posted.

Here is the list of changes:

- "StorageType" imported FROM SNMPv2-TC.
- In the "MteObjectsEntry" definition, the second "t" in "Storagetype"
 changed to "T" ("StorageType").
- The OID assignment for "mteObjectsEntryStorageType" was missing a "j":
   "::= { mteObectsEntry 6 }" changed to "::= { mteObjectsEntry 6 }"
- "mteTriggerEntryStorageType" added to the "dismanEventTriggerGroup" OBJECT-GROUP.
- "mteObjectsEntryStorageType" should be added to the "dismanEventObjectsGroup" OBJECT-GROUP.
- "mteEventEntryStorageType" should be added to the "dismanEventEventGroup" OBJECT-GROUP.
- new "status of this memo"
- new SNMP boilerplate
    As a consequence, the list of references is reduced
- normative versus informative references
- updated references. 

    Ex: RFC2573 -> RFC3413
    Ex: RFC2575 -> RFC3415
    Ex: [SNMP-TARGET-MIB] or [rfcNotificationLogMIB] not defined. Note: 
it was already the case in RFC2981
- reordered the last sections: security, references, author's address
        Also, author's address and acknowledgment sections not part 
anymore of the table of content
-"This document obsoletes RFC 2981. " in the abstract, and "This 
document obsoletes RFC 2981 [RFC2981]." in the overview
- DESCRIPTION

      "The MIB module for defining Managed Triggered Event (MTE) and actions
      for network management purposes.
- "Triggers define the conditions that lead to events. Events may cause notifications, may set MIB objects, or both."
instead of 
  "Triggers define the conditions that lead to events. Events may cause notifications."


Feel free to provide any feedback.


I run "idnits" against the draft. It complains that: 
  * The document seems to lack an Introduction section.
  * The document seems to lack an IANA Considerations section.

Is the introduction compulsory?
Is this "IANA Considerations" section compulsory? For example, if I look at RFC 3970 (TE MIB), there is none!

Regards, Benoit.





--------------010103030504010606060203
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<pre wrap="">Dear all,

A new version of event-mib draft, draft-ietf-disman-event-mib-v2-05.txt, has been posted.

Here is the list of changes:

- "StorageType" imported FROM SNMPv2-TC.
- In the "MteObjectsEntry" definition, the second "t" in "Storagetype"
 changed to "T" ("StorageType").
- The OID assignment for "mteObjectsEntryStorageType" was missing a "j":
   "::= { mteObectsEntry 6 }" changed to "::= { mteObjectsEntry 6 }"
- "mteTriggerEntryStorageType" added to the "dismanEventTriggerGroup" OBJECT-GROUP.
- "mteObjectsEntryStorageType" should be added to the "dismanEventObjectsGroup" OBJECT-GROUP.
- "mteEventEntryStorageType" should be added to the "dismanEventEventGroup" OBJECT-GROUP.
- new "status of this memo"
- new SNMP boilerplate
&nbsp;&nbsp;&nbsp; As a consequence, the list of references is reduced
- normative versus informative references
- updated references. 
</pre>
&nbsp;&nbsp;&nbsp; Ex: RFC2573 -&gt; RFC3413<br>
&nbsp;&nbsp;&nbsp; Ex: RFC2575 -&gt; RFC3415<br>
&nbsp;&nbsp;&nbsp; Ex: [SNMP-TARGET-MIB] or [rfcNotificationLogMIB] not defined. Note:
it was already the case in RFC2981<br>
- reordered the last sections: security, references, author's address<br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Also, author's address and acknowledgment sections not part
anymore of the table of content<br>
-<span style="">"This document
obsoletes RFC 2981.</span>
" in the abstract, and<span style="" lang="FR"> "This document
obsoletes RFC 2981 [RFC2981].</span><span style="" lang="FR"><o:p></o:p></span>"
in the overview<br>
- DESCRIPTION<br>
<pre wrap=""><span class="moz-txt-citetags"> </span>     "The MIB module for defining Managed Triggered Event (MTE) and actions
<span class="moz-txt-citetags"> </span>     for network management purposes.
- "Triggers define the conditions that lead to events.<span
 class="moz-txt-citetags"> </span>Events may cause notifications, may set MIB objects, or both."
instead of 
&nbsp; "Triggers define the conditions that lead to events. Events may cause notifications."


Feel free to provide any feedback.


I run "idnits" against the draft. It complains that: 
  * The document seems to lack an Introduction section.
  * The document seems to lack an IANA Considerations section.

Is the introduction compulsory?
Is this "IANA Considerations" section compulsory? For example, if I look at RFC 3970 (TE MIB), there is none!

Regards, Benoit.


</pre>
<br>
<span style="font-size: 10pt; font-family: &quot;Times New Roman&quot;;"> </span>
</body>
</html>

--------------010103030504010606060203--




From disman-bounces@ietf.org Sat Jun 04 19:02:24 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Deheq-0008MI-Ik; Sat, 04 Jun 2005 19:02:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dehep-0008M8-E1
	for disman@megatron.ietf.org; Sat, 04 Jun 2005 19:02:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06048
	for <disman@ietf.org>; Sat, 4 Jun 2005 19:02:20 -0400 (EDT)
Received: from pop-tawny.atl.sa.earthlink.net ([207.69.195.67])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DehzI-0005hp-LN
	for disman@ietf.org; Sat, 04 Jun 2005 19:23:35 -0400
Received: from h-68-164-241-3.snvacaid.dynamic.covad.net ([68.164.241.3]
	helo=oemcomputer)
	by pop-tawny.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1Dehej-0000rY-00
	for disman@ietf.org; Sat, 04 Jun 2005 19:02:18 -0400
Message-ID: <001701c56959$e3146e60$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
References: <42A0FAAA.7080905@cisco.com>
Subject: Re: [Disman] draft-ietf-disman-event-mib-v2-05.txt has been posted
Date: Sat, 4 Jun 2005 16:05:22 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Benoit Claise" <bclaise@cisco.com>
> To: "Disman (E-mail)" <disman@ietf.org>
> Sent: Friday, June 03, 2005 5:49 PM
> Subject: [Disman] draft-ietf-disman-event-mib-v2-05.txt has been posted
...
> Is the introduction compulsory?

Yes.  I'd suggest moving the current "Overview" section up and
re-labeling it "Introduction" to meet this requirement.  Any objections?

> Is this "IANA Considerations" section compulsory?
...

Yes.    See http://www.ietf.org/ID-Checklist.html section 2.2 item 7 D
for the course of action in this case.

Randy







From disman-bounces@ietf.org Mon Jun 06 16:34:17 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfOIb-0007UV-NA; Mon, 06 Jun 2005 16:34:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfNUs-00071x-RK; Mon, 06 Jun 2005 15:42:54 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02719;
	Mon, 6 Jun 2005 15:42:53 -0400 (EDT)
Message-Id: <200506061942.PAA02719@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 06 Jun 2005 15:42:52 -0400
X-Mailman-Approved-At: Mon, 06 Jun 2005 16:34:16 -0400
Cc: disman@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-event-mib-v2-05.txt
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

--NextPart

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

	Title		: Event MIB
	Author(s)	: R. Kavasseri, B. Claise
	Filename	: draft-ietf-disman-event-mib-v2-05.txt
	Pages		: 54
	Date		: 2005-6-6
	
This memo defines a portion of the Management Information 
   Base (MIB) for use with network management protocols in the Internet 
   community.  In particular, it describes managed objects that can be 
   used to manage and monitor MIB objects and take action through 
   events.  This document obsoletes RFC 2981.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


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-event-mib-v2-05.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-event-mib-v2-05.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: <2005-6-6161752.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-event-mib-v2-05.txt

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

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


--OtherAccess--

--NextPart--






From disman-bounces@ietf.org Mon Jun 06 21:59:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfTNY-0000Xa-O1; Mon, 06 Jun 2005 21:59:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DfTNW-0000XV-Mx
	for disman@megatron.ietf.org; Mon, 06 Jun 2005 21:59:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14569
	for <disman@ietf.org>; Mon, 6 Jun 2005 21:59:40 -0400 (EDT)
Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfTiT-0005vT-Fw
	for disman@ietf.org; Mon, 06 Jun 2005 22:21:22 -0400
Received: from h-68-164-241-191.snvacaid.dynamic.covad.net ([68.164.241.191]
	helo=oemcomputer)
	by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DfTNP-00012H-00
	for disman@ietf.org; Mon, 06 Jun 2005 21:59:36 -0400
Message-ID: <024c01c56b04$ffc578e0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B155071BE83C@nl0006exch001u.nl.lucent.com>
	<EE359991BA9D6B1490413AB4@[192.168.0.112]>
Date: Mon, 6 Jun 2005 19:02:20 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [Disman] Re: MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-0 6.tx t
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Juergen Quittek" <quittek@ccrle.nec.de>
> To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>; <j.schoenwaelder@iu-bremen.de>
> Cc: "Juergen Quittek" <quittek@ccrle.nec.de>; "Randy Presuhn" <randy_presuhn@mindspring.com>
> Sent: Monday, May 16, 2005 5:38 PM
> Subject: RE: MIB Doctor review: publish draft-ietf-disman-remops-mib-v2-0 6.tx t
...
> I will send a detailed message to the mailing list addressing each
> of Juergen's comments individually as soon as we have discussed his
> open issues.
...

What's the status of this?

Randy







From disman-bounces@ietf.org Mon Jun 06 22:38:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfTz0-0005l2-HE; Mon, 06 Jun 2005 22:38:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DfTyz-0005kx-GQ
	for disman@megatron.ietf.org; Mon, 06 Jun 2005 22:38:25 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16646
	for <disman@ietf.org>; Mon, 6 Jun 2005 22:38:22 -0400 (EDT)
Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfUJx-0006dz-3S
	for disman@ietf.org; Mon, 06 Jun 2005 23:00:05 -0400
Received: from h-68-164-241-191.snvacaid.dynamic.covad.net ([68.164.241.191]
	helo=oemcomputer)
	by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DfTyx-0003E5-00
	for disman@ietf.org; Mon, 06 Jun 2005 22:38:23 -0400
Message-ID: <026501c56b0a$6be5e280$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <disman@ietf.org>
References: <1109611611.8339.179.camel@daves.staff.csc.liv.ac.uk>
Subject: Re: [Disman] Event-MIB - request for clarifications
Date: Mon, 6 Jun 2005 19:41:34 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

I still haven't seen a response to Dave's request.  These all
strike me as legitimate issues that should be addressed in the
update.  Would someone like to take a stab at providing text
to update the i-d to answer these questions?

Randy

> From: "Dave Shield" <D.T.Shield@csc.liv.ac.uk>
> To: <disman@ietf.org>
> Sent: Monday, February 28, 2005 10:26 AM
> Subject: [Disman] Event-MIB - request for clarifications
>
> I've recently been looking at the Event MIB, and whilst I've
> mostly got a handle on how this works, there are a few things
> that I'm not fully clear on.   I've had a look through the
> mail archives without much luck, but if these issues have been
> covered before, just point me to where they've been discussed.
>
>   The points on which I'd appreciate some clarification are
> the following:
>
>
> a) Wildcard handling
>
>   If mteTriggerValueID uses a "partial" wildcard, then
> should the wildcard handling of corresponding mteObjectsID
> and mteEventSetObject entry append the *full* instance of
> the mteTriggerValueID value that matched, or just the OID
> suffix added as part of the expansion?
>
> For example, suppose I'm monitoring an interface-related
> table that's indexed by ifName strings, and specify a
> mteTriggerValueID of 'someObject."eth"'
> (with mteTriggerValueIDWildcard set true).
>
> Then a trigger fires, matching "eth1" (i.e. adding '1')
>
> Should the corresponding mteObjectsID entries be specified
> as 'someObject2."eth"' (and add the matching '1' suffix) or
> just 'someObject2' (and add the full matching instance "eth1")
>
>
>
> b) Updating configuration settings
>
>   The objects in the mteTriggerTable are defined as
> read-create, but the description of mteTriggerEntryStatus
> states:
>      "Once made active an entry may not be modified
>       except to delete it."
>
> Does that apply to the whole of that mteTriggerEntry
> row, or just the mteTriggerEntryStatus?
> For example, is it legitimate to adjust the frequency of
> a given trigger, or does the whole row have to be deleted
> and recreated?  Similarly for (e.g.) mteTriggerComment?
>
>
>
> c)  Access control
>
> The description of mteTriggerTargetTag states that the
> mteTriggerValueID value should be retrieved using
>     "the security credentials of the requester that
>      set mteTriggerEntryStatus to 'active'"
>
> What credentials should be used if the entry wasn't
> configured via SNMP (e.g. from static configuration) ?
>
>
> The implication of this is that the mteOwner index string
> is only used for grouping related entries together (so
> that they can all be covered by a single VACM entry).
>
> But the third paragraph of section 7 talks about mapping
> this "owner index" to a securityName or groupName.  How
> does this relate to the use of the requestor's security
> credentials?
>
> This is probably the area that I found least clear?
> I await enlightenment.....
>
>
> Dave
>
>







From disman-bounces@ietf.org Mon Jun 06 22:40:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfU0Y-0005n9-QL; Mon, 06 Jun 2005 22:40:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DfU0W-0005mQ-Vw
	for disman@megatron.ietf.org; Mon, 06 Jun 2005 22:40:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA16757
	for <disman@ietf.org>; Mon, 6 Jun 2005 22:39:58 -0400 (EDT)
Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfULU-0006fk-U7
	for disman@ietf.org; Mon, 06 Jun 2005 23:01:41 -0400
Received: from h-68-164-241-191.snvacaid.dynamic.covad.net ([68.164.241.191]
	helo=oemcomputer)
	by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DfU0V-0003cC-00
	for disman@ietf.org; Mon, 06 Jun 2005 22:39:59 -0400
Message-ID: <026a01c56b0a$a5b6e900$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <disman@ietf.org>
References: <1109866130.12812.36.camel@daves.staff.csc.liv.ac.uk>
Subject: Re: [Disman] Event MIB object handling
Date: Mon, 6 Jun 2005 19:43:11 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Here's another event MIB question that still needs to be addressed.
Comments?

Randy

> From: "Dave Shield" <D.T.Shield@csc.liv.ac.uk>
> To: <disman@ietf.org>
> Sent: Thursday, March 03, 2005 9:08 AM
> Subject: [Disman] Event MIB object handling
>
> I've got another question relating to the Event-MIB, in particular
> the handling of the objects to be added to a notification payload.
>
> Should the objects listed in the mteObjectsTable cover *all*
> the varbinds for a particular notification, or just the "extra"
> ones not included in the NOTIFICATION-TYPE definition (with those
> being inserted automatically) ?
>
> I've been assuming that this table should list everything
> (since the agent might not have access to the MIB definition).
> In which case I'm a little puzzled about the order in which
> the three mte{Trigger,TriggerXxx,EventNotification}Objects
> tags are applied.
>
> Naively, I'd expect that the mandatory notification objects
> would be closely linked with the notification itself, and hence
> be specified via the mteEventNotificationObjects tag, with the
> two trigger tags being used to add extra non-standard varbinds.
> Which would imply that the mteENObjects tag would have to be
> applied first.  And there's a note in the archives from Mike
> Daniele (<3665A029.C3B03BD@zk3.dec.com> dated 02 Dec 1998)
> commenting on draft #05 which seems to suggest the same thing.
>
>   But draft #06 introduces text in the mteObjectsIndex
> description which says:
>
>    Groups are placed in the notification in the order of the
>    selections for overall trigger, trigger test, and event.
>
> and this seems to have remained the same through into RFC
> 2981 and the latest IDraft.  But I wasn't able to find an
> explanation of why this particular order was used, or any
> further discussion of this.
>
> Am I missing something obvious?
>
> Dave
>
>







From disman-bounces@ietf.org Tue Jun 07 08:09:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dfctw-0006pH-1J; Tue, 07 Jun 2005 08:09:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dfctt-0006oV-Ue
	for disman@megatron.ietf.org; Tue, 07 Jun 2005 08:09:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16950
	for <disman@ietf.org>; Tue, 7 Jun 2005 08:09:44 -0400 (EDT)
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfdEv-0001ID-Su
	for disman@ietf.org; Tue, 07 Jun 2005 08:31:31 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j57C9Ti25654
	for <disman@ietf.org>; Tue, 7 Jun 2005 14:09:30 +0200 (CEST)
Received: from [10.61.65.182] (ams-clip-vpn-dhcp438.cisco.com [10.61.65.182])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j57C9IF24585
	for <disman@ietf.org>; Tue, 7 Jun 2005 14:09:29 +0200 (CEST)
Message-ID: <42A58E6D.30609@cisco.com>
Date: Tue, 07 Jun 2005 14:09:17 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Disman (E-mail)" <disman@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
Subject: [Disman] Small editorial correction to
	draft-ietf-disman-event-mib-v2-05.txt
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Dear all,

   +-----------------------------+ 
   | mteTriggerEntry             |      subclassed by: 
   |  { mteOwner,                |---+ 
   |    IMPLIED mteTriggerName } |   +-- mteTriggerDeltaEntry 
   |                             |   | 
   |                             |   +-- mteTriggerExistenceEntry 
   |                             |   | 
   |                             |   +-- mteTriggerBooleanEntry 
   |                             |   | 
   |                             |   +-- mteTriggerThresholdEntry 
   |                             | 
   |       mteTrigger*Event -------------------------------->+ 
   |                             |                           | 
   |       mteTriggerObjects ------------------>+            | 
   +-----------------------------+              |            | 
                                                |            | 
   +-----------------------------+              V            | 
   | mteObjectsEntry             |              |            | 
   |  { mteOwner,                |<-------------+            | 
   |    mteObjectsName,          |                           | 
   |    mteObjectsIndex }        |                           | 
   +-----------------------------+                           | 
                                                             V 
   +---------------------------+                             | 
   | mteEventEntry             |<----------------------------+ 
   |  { mteOwner,              | 
   |    IMPLIED mteEventName } | 
   |                           | 
   |            mteEventAction---> + (condition) 
   +---------------------------+   | 
                                   V 
   +---------------------------+   |   +--------------------------+ 
   | mteEventNotificationEntry |   |   | mteEventSetEntry          | 
   |  { mteOwner,              |<--+-->|  { mteOwner,              | 
   |    IMPLIED mteEventName } |       |    IMPLIED mteEventName } | 
   +---------------------------+       +---------------------------+ 


mteTriggerObjects should read mteTrigger*Objects, as it relates to mteTriggerExistenceObjects, mteTriggerBooleanObjects, and mteTriggerThresholdObjects.

Feedback?

Regards, Benoit






From disman-bounces@ietf.org Tue Jun 07 10:27:10 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dff2s-0006J8-6q; Tue, 07 Jun 2005 10:27:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dff2r-0006Iz-3z
	for disman@megatron.ietf.org; Tue, 07 Jun 2005 10:27:09 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27940
	for <disman@ietf.org>; Tue, 7 Jun 2005 10:27:07 -0400 (EDT)
Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DffNt-0004Ej-1P
	for disman@ietf.org; Tue, 07 Jun 2005 10:48:55 -0400
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost [127.0.0.1])
	by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j57EQuK04644
	for <disman@ietf.org>; Tue, 7 Jun 2005 16:26:56 +0200 (CEST)
Received: from [10.61.65.182] (ams-clip-vpn-dhcp438.cisco.com [10.61.65.182])
	by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id
	j57EQuF00096
	for <disman@ietf.org>; Tue, 7 Jun 2005 16:26:56 +0200 (CEST)
Message-ID: <42A5AEAF.7060004@cisco.com>
Date: Tue, 07 Jun 2005 16:26:55 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Disman (E-mail)" <disman@ietf.org>
Subject: Re: [Disman] Small editorial correction
	to	draft-ietf-disman-event-mib-v2-05.txt
References: <42A58E6D.30609@cisco.com>
In-Reply-To: <42A58E6D.30609@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Benoit Claise wrote:

> Dear all,
>
>   +-----------------------------+   | mteTriggerEntry             
> |      subclassed by:   |  { mteOwner,                |---+   |    
> IMPLIED mteTriggerName } |   +-- mteTriggerDeltaEntry   
> |                             |   |   |                             
> |   +-- mteTriggerExistenceEntry   |                             |   | 
>   |                             |   +-- mteTriggerBooleanEntry   
> |                             |   |   |                             
> |   +-- mteTriggerThresholdEntry   |                             |   
> |       mteTrigger*Event -------------------------------->+   
> |                             |                           |   |       
> mteTriggerObjects ------------------>+            |   
> +-----------------------------+              |            | 
>                                                |            |   
> +-----------------------------+              V            |   | 
> mteObjectsEntry             |              |            |   |  { 
> mteOwner,                |<-------------+            |   |    
> mteObjectsName,          |                           |   |    
> mteObjectsIndex }        |                           |   
> +-----------------------------+                           | 
>                                                             V   
> +---------------------------+                             |   | 
> mteEventEntry             |<----------------------------+   |  { 
> mteOwner,              |   |    IMPLIED mteEventName } |   
> |                           |   |            mteEventAction---> + 
> (condition)   +---------------------------+   | 
>                                   V   +---------------------------+   
> |   +--------------------------+   | mteEventNotificationEntry |   |   
> | mteEventSetEntry          |   |  { mteOwner,              |<--+-->|  
> { mteOwner,              |   |    IMPLIED mteEventName } |       |    
> IMPLIED mteEventName } |   +---------------------------+       
> +---------------------------+
>
> mteTriggerObjects should read mteTrigger*Objects, as it relates to 
> mteTriggerExistenceObjects, mteTriggerBooleanObjects, and 
> mteTriggerThresholdObjects.

Oops. Forgot mteTriggerObjects itself.
Anyway, IMHO it doesn't change the proposal that, in the diagram of 
section 4, mteTriggerObjects should read mteTrigger*Objects.

Regards, Benoit.

>
>
> Feedback?
>
> Regards, Benoit






From disman-bounces@ietf.org Tue Jun 07 14:37:56 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DfixY-0002hz-9a; Tue, 07 Jun 2005 14:37:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DfixX-0002hs-Kz
	for disman@megatron.ietf.org; Tue, 07 Jun 2005 14:37:55 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19490
	for <disman@ietf.org>; Tue, 7 Jun 2005 14:37:54 -0400 (EDT)
Received: from pop-borzoi.atl.sa.earthlink.net ([207.69.195.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfjId-0001jp-8l
	for disman@ietf.org; Tue, 07 Jun 2005 14:59:44 -0400
Received: from h-68-166-189-237.snvacaid.dynamic.covad.net ([68.166.189.237]
	helo=oemcomputer)
	by pop-borzoi.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DfixT-0001FL-00
	for disman@ietf.org; Tue, 07 Jun 2005 14:37:51 -0400
Message-ID: <001d01c56b90$75815500$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
References: <42A58E6D.30609@cisco.com> <42A5AEAF.7060004@cisco.com>
Subject: Re: [Disman] Small editorial correction
	to	draft-ietf-disman-event-mib-v2-05.txt
Date: Tue, 7 Jun 2005 11:41:03 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Benoit Claise" <bclaise@cisco.com>
> To: "Disman (E-mail)" <disman@ietf.org>
> Sent: Tuesday, June 07, 2005 7:26 AM
> Subject: Re: [Disman] Small editorial correctionto draft-ietf-disman-event-mib-v2-05.txt
...
> > mteTriggerObjects should read mteTrigger*Objects, as it relates to
> > mteTriggerExistenceObjects, mteTriggerBooleanObjects, and
> > mteTriggerThresholdObjects.
>
> Oops. Forgot mteTriggerObjects itself.
> Anyway, IMHO it doesn't change the proposal that, in the diagram of
> section 4, mteTriggerObjects should read mteTrigger*Objects.
...

Seems reasonable to me.

Randy







From disman-bounces@ietf.org Wed Jun 08 14:16:31 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg56M-0004Zi-W9; Wed, 08 Jun 2005 14:16:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dg56K-0004ZV-Pt; Wed, 08 Jun 2005 14:16:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22840;
	Wed, 8 Jun 2005 14:16:26 -0400 (EDT)
Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Dg5Rb-0002hX-7p; Wed, 08 Jun 2005 14:38:29 -0400
Received: from h-64-105-137-152.snvacaid.dynamic.covad.net ([64.105.137.152]
	helo=oemcomputer)
	by pop-canoe.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1Dg568-00070F-00; Wed, 08 Jun 2005 14:16:16 -0400
Message-ID: <001a01c56c56$9a6ab980$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "LTRU Working Group" <ltru@ietf.org>, "Disman" <disman@ietf.org>
Date: Wed, 8 Jun 2005 11:18:32 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Cc: 
Subject: [Disman] Fw: An interesting sub-note for all of you using the xml
	tool for drafts
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Forwarded for your information if you plan on submitting i-ds and are
using the xml2rfc tools.

Randy

----- Original Message ----- 
> From: "Carl Malamud" <carl@media.org>
> To: "Randall Stewart" <randall@stewart.chicago.il.us>
> Cc: <ietf@ietf.org>
> Sent: Wednesday, June 08, 2005 8:09 AM
> Subject: Re: An interesting sub-note for all of you using the xml tool fordrafts
>

> Randall's method works, or you can do what the readme suggests:
>
> <rfc ipr='full3978' docName='draft-mrose-writing-rfcs-01'>
>
> see:
>
> http://xml.resource.org/authoring/draft-mrose-writing-rfcs.html#ipr
>
> Regards,
>
> Carl
>
>
> > Dear all:
> >
> > I recently submitted a draft to the ietf repository and got
> > this response... Note that the front of my document had
> > "
> >
> >     This document is an Internet-Draft and is subject to all provisions
> >     of Section 3 of RFC 3667.  By submitting this Internet-Draft, each
> >     author represents that any applicable patent or other IPR claims of
> >     which he or she is aware have been or will be disclosed, and any of
> >     which he or she become aware will be disclosed, in accordance with
> >     RFC 3668.
> >
> > "
> >
> > as the very first paragraph.. .this was generated via the XML tool..
> >
> > So, I guess the automated tool will no longer accept this statement
> > with a reference to RFC 36668.... it has to be BCP 79... and the
> > section number.
> >
> > So if you are planning to do the "rush to submit" at the last
> > hour... and if you are using the xml tool.. be sure to save the
> > wording below and manually edit it into place... that is what
> > I have been doing this week to all the drafts I have been submitting..
> >
> > If you don't .. you will have a rather funny surprise aka rejected
> > draft... and that would not be fun if your a procrastanator :-0
> >
> > R
> >
> > >
> > > The Secretariat CANNOT process your Internet-Draft submission due to
> > > following reason(s):
> > >
> > >  * All Internet-Drafts must have on the first page an intellectual property
> > > rights (IPR) statement that says:
> > >
> > >
> > > By submitting this Internet-Draft, each author represents
> > > that any applicable patent or other IPR claims of which he
> > > or she is aware have been or will be disclosed, and any of
> > > which he or she becomes aware will be disclosed, in
> > > accordance with Section 6 of BCP 79.
> > >
> >
> >
> > -- 
> > Randall Stewart
> > 803-345-0369 <or> 815-342-5222(cell)
> >
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> >
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf







From disman-bounces@ietf.org Thu Jun 09 14:15:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgRW1-00040C-LK; Thu, 09 Jun 2005 14:12:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DgRW0-0003zG-9A; Thu, 09 Jun 2005 14:12:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00260;
	Thu, 9 Jun 2005 14:12:26 -0400 (EDT)
Received: from pop-altamira.atl.sa.earthlink.net ([207.69.195.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DgRrU-0000pX-UE; Thu, 09 Jun 2005 14:34:42 -0400
Received: from h-68-166-188-156.snvacaid.dynamic.covad.net ([68.166.188.156]
	helo=oemcomputer)
	by pop-altamira.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DgRVp-0001TE-00; Thu, 09 Jun 2005 14:12:17 -0400
Message-ID: <000c01c56d1f$37a98f00$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "LTRU Working Group" <ltru@ietf.org>, "Disman" <disman@ietf.org>
Date: Thu, 9 Jun 2005 11:15:27 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: 
Subject: [Disman] Useful tool for i-d authors & editors
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

If you don't already use this tool, you should give it a try.

http://ietf.levkowetz.com/tools/idnits/idnits.pyht

Randy







From disman-bounces@ietf.org Sat Jun 11 17:43:40 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DhDlU-0006aI-KC; Sat, 11 Jun 2005 17:43:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DhDlS-0006Zj-KS; Sat, 11 Jun 2005 17:43:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17936;
	Sat, 11 Jun 2005 17:43:36 -0400 (EDT)
Received: from pop-altamira.atl.sa.earthlink.net ([207.69.195.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DhE7P-0003yM-NW; Sat, 11 Jun 2005 18:06:19 -0400
Received: from h-68-165-4-189.snvacaid.dynamic.covad.net ([68.165.4.189]
	helo=oemcomputer)
	by pop-altamira.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DhDlR-0000y6-00; Sat, 11 Jun 2005 17:43:37 -0400
Message-ID: <001301c56ecf$17002be0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "LTRU Working Group" <ltru@ietf.org>, "Disman" <disman@ietf.org>
Date: Sat, 11 Jun 2005 14:46:46 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: 
Subject: [Disman] Fw: Internet-Drafts Submission Cutoff Dates for the 63rd
	IETF Meeting in Paris, France 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Note well.  The deadline fast approacheth.

Randy

> From: <ietf-secretariat@ietf.org>
> To: <ietf-announce@ietf.org>
> Sent: Thursday, June 09, 2005 9:00 PM
> Subject: Internet-Drafts Submission Cutoff Dates for the 63rd IETF Meeting in Paris, France
>
> There are two (2) Internet-Draft cutoff dates for the 63rd
> IETF Meeting in Paris, France:
>
> July 11th: Cutoff Date for Initial (i.e., version -00)
> Internet-Draft Submissions
>
> All initial Internet-Drafts (version -00) must be submitted by Monday,
> July 11th at 9:00 AM ET. As always, all initial submissions with a
> filename beginning with "draft-ietf" must be approved by the
> appropriate WG Chair before they can be processed or announced.  The
> Secretariat would appreciate receiving WG Chair approval by Tuesday,
> July 5th at 9:00 AM ET.
>
> July 18th: Cutoff Date for Revised (i.e., version -01 and higher)
> Internet-Draft Submissions
>
> All revised Internet-Drafts (version -01 and higher) must be submitted
> by Monday, July 18th at 9:00 AM ET.
>
> Initial and revised Internet-Drafts received after their respective
> cutoff dates will not be made available in the Internet-Drafts
> directory or announced until on or after Monday, August 1st at 9:00
> AM ET, when Internet-Draft posting resumes.  Please do not wait until
> the last minute to submit.
>
> PLEASE NOTE THE CHANGE OF PROCEDURE:  If you submit an initial or
> revised Internet-Draft after their respective cutoff deadlines, then
> your document will be retained and posted when Internet-Draft
> processing resumes.  You will no longer be required to resubmit the
> document.
>
> Thank you for your understanding and cooperation. If you have any
> questions or concerns, then please send a message to
> internet-drafts@ietf.org.
>
> The IETF Secretariat
>
> FYI: The Internet-Draft cutoff dates as well as other significant dates
> for the 63rd IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_63.html.
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce







From disman-bounces@ietf.org Sat Jun 18 14:43:02 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DjiHW-0007GW-Kx; Sat, 18 Jun 2005 14:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DjiHV-0007GR-FR
	for disman@megatron.ietf.org; Sat, 18 Jun 2005 14:43:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02824
	for <disman@ietf.org>; Sat, 18 Jun 2005 14:42:59 -0400 (EDT)
Received: from pop-knobcone.atl.sa.earthlink.net ([207.69.195.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Djieq-0004Mr-Tt
	for disman@ietf.org; Sat, 18 Jun 2005 15:07:10 -0400
Received: from h-64-105-136-136.snvacaid.dynamic.covad.net ([64.105.136.136]
	helo=oemcomputer)
	by pop-knobcone.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DjiHT-00070D-00
	for disman@ietf.org; Sat, 18 Jun 2005 14:42:59 -0400
Message-ID: <004601c57436$0c479140$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
Date: Sat, 18 Jun 2005 11:46:32 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [Disman] Fw: Posting of IPR Disclosure
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Forwarded for your information.

Randy

> From: "IETF Secretariat" <ietf-ipr@ietf.org>
> To: <dromasca@avaya.com>; <schishol@nortelnetworks.com>
> Cc: <bwijnen@lucent.com>; <randy_presuhn@mindspring.com>
> Sent: Friday, June 17, 2005 4:05 PM
> Subject: Posting of IPR Disclosure
>
> Dear Dan Romascanu, Sharon Chisholm:
>
> An IPR disclosure that pertains to your RFC entitled "Alarm MIB" (RFC3877) was
> submitted to the IETF Secretariat on 2005-06-10 and has been posted on the "IETF
> Page of Intellectual Property Rights Disclosures"
> (https://datatracker.ietf.org/public/ipr_list.cgi). The title of the IPR
> disclosure is "Nortel Networks Updated Patent Statement pertaining to
> draft-chisholm-disman-active-alarm about IPR claimed in RFC 3877."
>
> The IETF Secretariat
>
>







From disman-bounces@ietf.org Mon Jun 20 18:43:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DkUza-0002EG-Ab; Mon, 20 Jun 2005 18:43:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DkUzZ-0002EB-1D
	for disman@megatron.ietf.org; Mon, 20 Jun 2005 18:43:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18317
	for <disman@ietf.org>; Mon, 20 Jun 2005 18:43:41 -0400 (EDT)
Received: from pop-satin.atl.sa.earthlink.net ([207.69.195.63])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkVNM-00087c-Hp
	for disman@ietf.org; Mon, 20 Jun 2005 19:08:20 -0400
Received: from h-64-105-137-238.snvacaid.dynamic.covad.net ([64.105.137.238]
	helo=oemcomputer)
	by pop-satin.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DkUzX-0000bc-00
	for disman@ietf.org; Mon, 20 Jun 2005 18:43:43 -0400
Message-ID: <022501c575ea$04b699c0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B155071BE83C@nl0006exch001u.nl.lucent.com><EE359991BA9D6B1490413AB4@[192.168.0.112]>
	<024c01c56b04$ffc578e0$7f1afea9@oemcomputer>
Subject: Re: [Disman] Re: MIB Doctor review:
	publishdraft-ietf-disman-remops-mib-v2-0 6.tx t
Date: Mon, 20 Jun 2005 15:47:03 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Randy Presuhn" <randy_presuhn@mindspring.com>
> To: "Disman" <disman@ietf.org>
> Sent: Monday, June 06, 2005 7:02 PM
> Subject: [Disman] Re: MIB Doctor review: publishdraft-ietf-disman-remops-mib-v2-0 6.tx t
>

> Hi -
>
> > From: "Juergen Quittek" <quittek@ccrle.nec.de>
> > To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>; <j.schoenwaelder@iu-bremen.de>
> > Cc: "Juergen Quittek" <quittek@ccrle.nec.de>; "Randy Presuhn" <randy_presuhn@mindspring.com>
> > Sent: Monday, May 16, 2005 5:38 PM
> > Subject: RE: MIB Doctor review: publish draft-ietf-disman-remops-mib-v2-0 6.tx t
> ...
> > I will send a detailed message to the mailing list addressing each
> > of Juergen's comments individually as soon as we have discussed his
> > open issues.
> ...
>
> What's the status of this?
>
> Randy

Could we just discuss those comments on this mailing list and be done with them?
It's been over a month and a half now since the review...

Randy, disman chair







From disman-bounces@ietf.org Wed Jun 22 00:29:52 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dkws4-0007q4-R3; Wed, 22 Jun 2005 00:29:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dkws2-0007pz-RS
	for disman@megatron.ietf.org; Wed, 22 Jun 2005 00:29:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18699
	for <disman@ietf.org>; Wed, 22 Jun 2005 00:29:47 -0400 (EDT)
Received: from pop-altamira.atl.sa.earthlink.net ([207.69.195.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DkxG3-0001Y2-2L
	for disman@ietf.org; Wed, 22 Jun 2005 00:54:42 -0400
Received: from h-64-105-34-60.snvacaid.dynamic.covad.net ([64.105.34.60]
	helo=oemcomputer)
	by pop-altamira.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1Dkwrx-0007n9-00
	for disman@ietf.org; Wed, 22 Jun 2005 00:29:45 -0400
Message-ID: <000501c576e3$858ea8e0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
Date: Tue, 21 Jun 2005 21:33:20 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [Disman] Should we close the disman WG?
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

The extreme lack of activity here, including the lack of response
to those few questions that have been posted, leads me to
believe that it's time to ask our AD to close this WG.  Does
anyone have a reason to keep the WG alive?  Surely at
least one of our 240 list subscribers must have some opinion.

RAndy







From disman-bounces@ietf.org Wed Jun 22 09:05:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl4ub-0003ck-0r; Wed, 22 Jun 2005 09:05:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl4uZ-0003cb-G8
	for disman@megatron.ietf.org; Wed, 22 Jun 2005 09:04:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06370
	for <disman@ietf.org>; Wed, 22 Jun 2005 09:04:57 -0400 (EDT)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl5Ig-00076I-FI
	for disman@ietf.org; Wed, 22 Jun 2005 09:29:55 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j5MCqxAK014248
	for <disman@ietf.org>; Wed, 22 Jun 2005 08:52:59 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j5MCqvAK014211
	for <disman@ietf.org>; Wed, 22 Jun 2005 08:52:58 -0400 (EDT)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Disman] Should we close the disman WG?
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 16:04:53 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F08B54EEB@is0004avexu1.global.avaya.com>
Thread-Topic: [Disman] Should we close the disman WG?
Thread-Index: AcV24x/IDEjQH2a8QCel/lu0dZyY8AARyGkg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, "Disman" <disman@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

I do not believe that there is new work that would require keeping the
WG update. I assume the list will stay active to answer (hopefully)
clarification questions in the future. What is the process to advance
documents beyond Proposed, if need would arise in the future?=20

Thanks and Regards,

Dan



=20

> -----Original Message-----
> From: disman-bounces@ietf.org=20
> [mailto:disman-bounces@ietf.org] On Behalf Of Randy Presuhn
> Sent: Wednesday, June 22, 2005 7:33 AM
> To: Disman
> Subject: [Disman] Should we close the disman WG?
>=20
> Hi -
>=20
> The extreme lack of activity here, including the lack of=20
> response to those few questions that have been posted, leads=20
> me to believe that it's time to ask our AD to close this WG. =20
> Does anyone have a reason to keep the WG alive?  Surely at=20
> least one of our 240 list subscribers must have some opinion.
>=20
> RAndy
>=20
>=20
>=20
>=20
>=20




From disman-bounces@ietf.org Wed Jun 22 09:43:27 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl5Vn-0006Ch-Pj; Wed, 22 Jun 2005 09:43:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl5Vm-0006CW-AI
	for disman@megatron.ietf.org; Wed, 22 Jun 2005 09:43:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10456
	for <disman@ietf.org>; Wed, 22 Jun 2005 09:43:24 -0400 (EDT)
Received: from mx3.liv.ac.uk ([138.253.100.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl5tr-0008Vw-LK
	for disman@ietf.org; Wed, 22 Jun 2005 10:08:22 -0400
Received: from mailhub1.liv.ac.uk ([138.253.100.94])
	by mx3.liv.ac.uk with esmtp (Exim 4.34)
	id 1Dl5VH-0007Dj-8z; Wed, 22 Jun 2005 14:42:55 +0100
Received: from localhost ([127.0.0.1] helo=mailhub1.liv.ac.uk)
	by mailhub1.liv.ac.uk with esmtp (Exim 4.51)
	id 1Dl5VH-0002Vx-77; Wed, 22 Jun 2005 14:42:55 +0100
Received: from tethys.server.csc.liv.ac.uk ([138.253.184.237])
	by mailhub1.liv.ac.uk with esmtp (Exim 4.34)
	id 1Dl5VH-0002Vu-3g; Wed, 22 Jun 2005 14:42:55 +0100
Received: from daves.staff.csc.liv.ac.uk (IDENT:daves@daves [10.1.67.1])
	by tethys.server.csc.liv.ac.uk (8.11.1 - (Revision
	1.5)/LUCS-DTS-3.0M10) with ESMTP id j5MDgsv12904; 
	Wed, 22 Jun 2005 14:42:54 +0100 (BST)
Subject: RE: [Disman] Should we close the disman WG?
From: Dave Shield <D.T.Shield@csc.liv.ac.uk>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F08B54EEB@is0004avexu1.global.avaya.com>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F08B54EEB@is0004avexu1.global.avaya.com>
Content-Type: text/plain
Organization: University of Liverpool, Computer Science
Message-Id: <1119447590.10072.67.camel@daves.staff.csc.liv.ac.uk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Wed, 22 Jun 2005 14:39:50 +0100
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, Disman <disman@ietf.org>
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

On Wed, 2005-06-22 at 14:04, Romascanu, Dan (Dan) wrote:
> I do not believe that there is new work that would require
> keeping the WG update.

Well, I recently put forward a suggestion that the current
handling of the three mte*Objects tags is fundamentally
flawed, and makes it effectively impossible to combine
trigger-based and event-based object tags when building up
a notification payload.


I've spoken briefly with Benoit about this issue, but have
otherwise had basically no response to this, or various other
questions posed here.

So I'd suggest that there *is* outstanding work to be done,
but possibly not much interest in doing it  :-(



>  I assume the list will stay active to answer (hopefully)
> clarification questions in the future.

I admire your optimism.....


Dave





From disman-bounces@ietf.org Wed Jun 22 10:01:30 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dl5nG-0004ej-4A; Wed, 22 Jun 2005 10:01:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dl5nD-0004eb-Vx
	for disman@megatron.ietf.org; Wed, 22 Jun 2005 10:01:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12370
	for <disman@ietf.org>; Wed, 22 Jun 2005 10:01:25 -0400 (EDT)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dl6BJ-0000mQ-37
	for disman@ietf.org; Wed, 22 Jun 2005 10:26:24 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j5MDnOAK021695
	for <disman@ietf.org>; Wed, 22 Jun 2005 09:49:25 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j5MDn9AK021253
	for <disman@ietf.org>; Wed, 22 Jun 2005 09:49:11 -0400 (EDT)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Disman] Should we close the disman WG?
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Wed, 22 Jun 2005 17:01:01 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F08B54F34@is0004avexu1.global.avaya.com>
Thread-Topic: [Disman] Should we close the disman WG?
Thread-Index: AcV3MHzMKWprEuBnQMCQQ7gQj4K9BwAAeENw
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Dave Shield" <D.T.Shield@csc.liv.ac.uk>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: quoted-printable
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, Disman <disman@ietf.org>
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

=20

> -----Original Message-----
> From: Dave Shield [mailto:D.T.Shield@csc.liv.ac.uk]=20
> Sent: Wednesday, June 22, 2005 4:40 PM
> To: Romascanu, Dan (Dan)
> Cc: Randy Presuhn; Disman
> Subject: RE: [Disman] Should we close the disman WG?
>=20
> On Wed, 2005-06-22 at 14:04, Romascanu, Dan (Dan) wrote:
> > I do not believe that there is new work that would require=20
> keeping the=20
> > WG update.
>=20
> Well, I recently put forward a suggestion that the current=20
> handling of the three mte*Objects tags is fundamentally=20
> flawed, and makes it effectively impossible to combine=20
> trigger-based and event-based object tags when building up a=20
> notification payload.
>=20
>=20
> I've spoken briefly with Benoit about this issue, but have=20
> otherwise had basically no response to this, or various other=20
> questions posed here.
>=20
> So I'd suggest that there *is* outstanding work to be done,=20
> but possibly not much interest in doing it  :-(

I agree and stand corrected - there were issue that were raised related
to existing documents, and even proposals for new work, but none seemed
to gather the minimal critical mass of interest.=20

>=20
>=20
>=20
> >  I assume the list will stay active to answer (hopefully)=20
> > clarification questions in the future.
>=20
> I admire your optimism.....

One must always believe :-)

>=20
>=20
> Dave
>=20

Dan





From disman-bounces@ietf.org Tue Jun 28 17:45:47 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DnNtr-0006NX-A5; Tue, 28 Jun 2005 17:45:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DnNtq-0006Mo-EG
	for disman@megatron.ietf.org; Tue, 28 Jun 2005 17:45:46 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00006
	for <disman@ietf.org>; Tue, 28 Jun 2005 17:45:43 -0400 (EDT)
Received: from pop-borzoi.atl.sa.earthlink.net ([207.69.195.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnOJH-0003g0-92
	for disman@ietf.org; Tue, 28 Jun 2005 18:12:03 -0400
Received: from h-64-105-35-218.snvacaid.dynamic.covad.net ([64.105.35.218]
	helo=oemcomputer)
	by pop-borzoi.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DnNto-0005cT-00
	for disman@ietf.org; Tue, 28 Jun 2005 17:45:45 -0400
Message-ID: <00f501c57c2b$47d7f360$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B155071BE83C@nl0006exch001u.nl.lucent.com><EE359991BA9D6B1490413AB4@[192.168.0.112]><024c01c56b04$ffc578e0$7f1afea9@oemcomputer>
	<022501c575ea$04b699c0$7f1afea9@oemcomputer>
Subject: Re: [Disman] Re: MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-06.txt
Date: Tue, 28 Jun 2005 14:49:36 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

Hello, anyone out there?  Should we just drop this item?

Randy

> From: "Randy Presuhn" <randy_presuhn@mindspring.com>
> To: "Disman" <disman@ietf.org>
> Sent: Monday, June 20, 2005 3:47 PM
> Subject: Re: [Disman] Re: MIB Doctor review:publishdraft-ietf-disman-remops-mib-v2-0 6.tx t
>
> Hi -
>
> > From: "Randy Presuhn" <randy_presuhn@mindspring.com>
> > To: "Disman" <disman@ietf.org>
> > Sent: Monday, June 06, 2005 7:02 PM
> > Subject: [Disman] Re: MIB Doctor review: publishdraft-ietf-disman-remops-mib-v2-0 6.tx t
> >
>
> > Hi -
> >
> > > From: "Juergen Quittek" <quittek@ccrle.nec.de>
> > > To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>; <j.schoenwaelder@iu-bremen.de>
> > > Cc: "Juergen Quittek" <quittek@ccrle.nec.de>; "Randy Presuhn" <randy_presuhn@mindspring.com>
> > > Sent: Monday, May 16, 2005 5:38 PM
> > > Subject: RE: MIB Doctor review: publish draft-ietf-disman-remops-mib-v2-0 6.tx t
> > ...
> > > I will send a detailed message to the mailing list addressing each
> > > of Juergen's comments individually as soon as we have discussed his
> > > open issues.
> > ...
> >
> > What's the status of this?
> >
> > Randy
>
> Could we just discuss those comments on this mailing list and be done with them?
> It's been over a month and a half now since the review...
>
> Randy, disman chair
>
>
>
>







From disman-bounces@ietf.org Wed Jun 29 02:29:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DnW4J-0001jv-E4; Wed, 29 Jun 2005 02:29:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DnW4H-0001jq-6L
	for disman@megatron.ietf.org; Wed, 29 Jun 2005 02:29:05 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09408
	for <disman@ietf.org>; Wed, 29 Jun 2005 02:29:04 -0400 (EDT)
Received: from i8c12.i.pppool.de ([85.73.140.18] helo=boskop.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnWTj-0004Gy-9v
	for disman@ietf.org; Wed, 29 Jun 2005 02:55:26 -0400
Received: by boskop.local (Postfix, from userid 501)
	id 5F35E352727; Wed, 29 Jun 2005 08:28:44 +0200 (CEST)
Date: Wed, 29 Jun 2005 08:28:44 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: [Disman] Re: MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-06.txt
Message-ID: <20050629062844.GA1128@boskop.local>
Mail-Followup-To: Randy Presuhn <randy_presuhn@mindspring.com>,
	Disman <disman@ietf.org>
References: <022501c575ea$04b699c0$7f1afea9@oemcomputer>
	<00f501c57c2b$47d7f360$7f1afea9@oemcomputer>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <00f501c57c2b$47d7f360$7f1afea9@oemcomputer>
User-Agent: Mutt/1.5.8i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: Disman <disman@ietf.org>
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

On Tue, Jun 28, 2005 at 02:49:36PM -0700, Randy Presuhn wrote:

> Hello, anyone out there?  Should we just drop this item?

Well, having spend some time on the review and having seen this
MIB implemented on some boxes, I would hope that we do not give
up the plan to get this finalized.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany




From disman-bounces@ietf.org Wed Jun 29 03:59:59 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DnXUE-0002OR-UI; Wed, 29 Jun 2005 03:59:58 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DnXUD-0002OM-GI
	for disman@megatron.ietf.org; Wed, 29 Jun 2005 03:59:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20419
	for <disman@ietf.org>; Wed, 29 Jun 2005 03:59:56 -0400 (EDT)
Received: from tierw.net.avaya.com ([198.152.13.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnXtj-0007Xf-Jl
	for disman@ietf.org; Wed, 29 Jun 2005 04:26:19 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j5T7lmAK009452
	for <disman@ietf.org>; Wed, 29 Jun 2005 03:47:48 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com
	[135.64.105.51])
	by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id
	j5T7lkAK009433
	for <disman@ietf.org>; Wed, 29 Jun 2005 03:47:47 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Disman] Re: MIB Doctor review:
	publishdraft-ietf-disman-remops-mib-v2-06.txt
Date: Wed, 29 Jun 2005 10:59:48 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F08BFA196@is0004avexu1.global.avaya.com>
Thread-Topic: [Disman] Re: MIB Doctor review:
	publishdraft-ietf-disman-remops-mib-v2-06.txt
Thread-Index: AcV8KssKSyyzMBipS3qVZ4/7SzkjCQAVFQ2A
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, "Disman" <disman@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Content-Transfer-Encoding: quoted-printable
Cc: 
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Randy,

Same as JuergenS, I am in favor of finishing this work before wrapping
up the WG.=20

I am not sure whether you expect input from anybody else but JuergenQ.
Here is what I see in the archives:

May 4 - you forwarded the MIB Doctor review to the list=20
May 5 - you asked 'Does anyone on this mailing list *disagree*' with
JuergenS's recommendations from the review. The way you asked the
question silence means consent
Same day - JuergenQ answers that he agrees with JuergenS's
recommendations with some exceptions that he would try to discuss 'on
the phone in the next days'.=20

Did the conversation between the two Juergens happen?

Are we waiting for an I-D update from JuergenQ, or for something else?=20

Dan
=20

> -----Original Message-----
> From: disman-bounces@ietf.org=20
> [mailto:disman-bounces@ietf.org] On Behalf Of Randy Presuhn
> Sent: Wednesday, June 29, 2005 12:50 AM
> To: Disman
> Subject: Re: [Disman] Re: MIB Doctor review:=20
> publishdraft-ietf-disman-remops-mib-v2-06.txt
>=20
> Hi -
>=20
> Hello, anyone out there?  Should we just drop this item?
>=20
> Randy
>=20
> > From: "Randy Presuhn" <randy_presuhn@mindspring.com>
> > To: "Disman" <disman@ietf.org>
> > Sent: Monday, June 20, 2005 3:47 PM
> > Subject: Re: [Disman] Re: MIB Doctor=20
> > review:publishdraft-ietf-disman-remops-mib-v2-0 6.tx t
> >
> > Hi -
> >
> > > From: "Randy Presuhn" <randy_presuhn@mindspring.com>
> > > To: "Disman" <disman@ietf.org>
> > > Sent: Monday, June 06, 2005 7:02 PM
> > > Subject: [Disman] Re: MIB Doctor review:=20
> > > publishdraft-ietf-disman-remops-mib-v2-0 6.tx t
> > >
> >
> > > Hi -
> > >
> > > > From: "Juergen Quittek" <quittek@ccrle.nec.de>
> > > > To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>;=20
> > > > <j.schoenwaelder@iu-bremen.de>
> > > > Cc: "Juergen Quittek" <quittek@ccrle.nec.de>; "Randy Presuhn"=20
> > > > <randy_presuhn@mindspring.com>
> > > > Sent: Monday, May 16, 2005 5:38 PM
> > > > Subject: RE: MIB Doctor review: publish=20
> > > > draft-ietf-disman-remops-mib-v2-0 6.tx t
> > > ...
> > > > I will send a detailed message to the mailing list=20
> addressing each=20
> > > > of Juergen's comments individually as soon as we have discussed=20
> > > > his open issues.
> > > ...
> > >
> > > What's the status of this?
> > >
> > > Randy
> >
> > Could we just discuss those comments on this mailing list=20
> and be done with them?
> > It's been over a month and a half now since the review...
> >
> > Randy, disman chair
> >
> >
> >
> >
>=20
>=20
>=20
>=20
>=20




From disman-bounces@ietf.org Wed Jun 29 14:44:32 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DnhY0-0005rT-5d; Wed, 29 Jun 2005 14:44:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DnhXy-0005rN-JP
	for disman@megatron.ietf.org; Wed, 29 Jun 2005 14:44:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23085
	for <disman@ietf.org>; Wed, 29 Jun 2005 14:44:29 -0400 (EDT)
Received: from pop-sarus.atl.sa.earthlink.net ([207.69.195.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DnhxY-0002Ao-U5
	for disman@ietf.org; Wed, 29 Jun 2005 15:10:58 -0400
Received: from h-68-165-4-178.snvacaid.dynamic.covad.net ([68.165.4.178]
	helo=oemcomputer)
	by pop-sarus.atl.sa.earthlink.net with smtp (Exim 3.36 #10)
	id 1DnhXn-0002Lc-00
	for disman@ietf.org; Wed, 29 Jun 2005 14:44:19 -0400
Message-ID: <000401c57cdb$1a79d040$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman" <disman@ietf.org>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F08BFA196@is0004avexu1.global.avaya.com>
Subject: Re: [Disman] MIB Doctor review: publish
	draft-ietf-disman-remops-mib-v2-06.txt
Date: Wed, 29 Jun 2005 11:48:11 -0700
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

Hi -

> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; "Disman" <disman@ietf.org>
> Sent: Wednesday, June 29, 2005 12:59 AM
> Subject: RE: [Disman] Re: MIB Doctor review:publishdraft-ietf-disman-remops-mib-v2-06.txt
...
> Same day - JuergenQ answers that he agrees with JuergenS's
> recommendations with some exceptions that he would try to discuss 'on
> the phone in the next days'.
>
> Did the conversation between the two Juergens happen?
...

A report on the conversation was promised, and has not shown up,
and I haven't heard anything from the Juergens to indicate that they've
had their discussion.  Since some of the comments were agreed, in
any case a new i-d is expected.

Randy







From disman-bounces@ietf.org Wed Jun 29 14:58:35 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Dnhlb-0000R8-IL; Wed, 29 Jun 2005 14:58:35 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Dnhla-0000Qy-Gb
	for disman@megatron.ietf.org; Wed, 29 Jun 2005 14:58:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24613
	for <disman@ietf.org>; Wed, 29 Jun 2005 14:58:33 -0400 (EDT)
Received: from ia1d5.i.pppool.de ([85.73.161.213] helo=boskop.local)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DniBB-0002dm-CL
	for disman@ietf.org; Wed, 29 Jun 2005 15:25:02 -0400
Received: by boskop.local (Postfix, from userid 501)
	id C1C553528E9; Wed, 29 Jun 2005 10:56:50 +0200 (CEST)
Date: Wed, 29 Jun 2005 10:56:50 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [Disman] Re: MIB Doctor review:
	publishdraft-ietf-disman-remops-mib-v2-06.txt
Message-ID: <20050629085650.GA1812@boskop.local>
Mail-Followup-To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>,
	Randy Presuhn <randy_presuhn@mindspring.com>,
	Disman <disman@ietf.org>
References: <AAB4B3D3CF0F454F98272CBE187FDE2F08BFA196@is0004avexu1.global.avaya.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AAB4B3D3CF0F454F98272CBE187FDE2F08BFA196@is0004avexu1.global.avaya.com>
User-Agent: Mutt/1.5.8i
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Randy Presuhn <randy_presuhn@mindspring.com>, Disman <disman@ietf.org>
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
List-Id: Distributed Management <disman.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/disman>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
Sender: disman-bounces@ietf.org
Errors-To: disman-bounces@ietf.org

On Wed, Jun 29, 2005 at 10:59:48AM +0300, Romascanu, Dan (Dan) wrote:

> May 4 - you forwarded the MIB Doctor review to the list 
> May 5 - you asked 'Does anyone on this mailing list *disagree*' with
> JuergenS's recommendations from the review. The way you asked the
> question silence means consent
> Same day - JuergenQ answers that he agrees with JuergenS's
> recommendations with some exceptions that he would try to discuss 'on
> the phone in the next days'. 
> 
> Did the conversation between the two Juergens happen?

Not yet.
 
> Are we waiting for an I-D update from JuergenQ, or for something else? 

At the end, this is what we are waiting for.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany




