RE: [Entmib] entstate-651 Notification Description Changes (Part II)

"Sharon Chisholm" <schishol@nortelnetworks.com> Fri, 17 December 2004 13:46 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18412 for <entmib-archive@lists.ietf.org>; Fri, 17 Dec 2004 08:46:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfIOy-0002MT-CL; Fri, 17 Dec 2004 08:44:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfILT-0001rJ-KZ for entmib@megatron.ietf.org; Fri, 17 Dec 2004 08:40:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18200 for <entmib@ietf.org>; Fri, 17 Dec 2004 08:40:34 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfIU6-0004xn-Ke for entmib@ietf.org; Fri, 17 Dec 2004 08:49:32 -0500
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id iBHDe1802427 for <entmib@ietf.org>; Fri, 17 Dec 2004 08:40:01 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <YZAC7Z4F>; Fri, 17 Dec 2004 08:40:02 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4022408C3@zcarhxm2.corp.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] entstate-651 Notification Description Changes (Part II)
Date: Fri, 17 Dec 2004 08:39:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
Sender: entmib-bounces@ietf.org
Errors-To: entmib-bounces@ietf.org

In the RT tool, I only found one issue related to this: 75. There might have
been others, but I filtered on issue title. It doesn't seem to have captured
the previous discussion around consensus. It also doesn't seem to be on the
mailing list. It must have been during a face to face meeting, although I
didn't see it reflected in any meeting minutes either.

So, that might put us in a better position to change it?

Sharon
-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@iu-bremen.de] On Behalf Of
Juergen Schoenwaelder
Sent: Friday, December 17, 2004 8:12 AM
To: Chisholm, Sharon [CAR:5K50:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] entstate-651 Notification Description Changes (Part
II)


On Fri, Dec 17, 2004 at 07:31:28AM -0500, Sharon Chisholm wrote:
 
> Well, as I said, I can't think of a design pattern to make then 
> conditionally mandatory. Personally, I'd love to see them mandatory, 
> but I think we would need strong consensus to make that change at this 
> point.

What were the arguments against making these mandatory? Generally too hard
to detect such state changes? Something else?

/js

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


_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib