RE: [Entmib] entstate-651 Notification Description Changes (Part II)
"Sharon Chisholm" <schishol@nortelnetworks.com> Mon, 20 December 2004 14:28 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 JAA01346 for <entmib-archive@lists.ietf.org>; Mon, 20 Dec 2004 09:28:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgOQB-0002WU-9k; Mon, 20 Dec 2004 09:21:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgOJu-0001ZJ-Fp for entmib@megatron.ietf.org; Mon, 20 Dec 2004 09:15:31 -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 JAA00431 for <entmib@ietf.org>; Mon, 20 Dec 2004 09:15:28 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgOT9-0001JK-Vt for entmib@ietf.org; Mon, 20 Dec 2004 09:25:05 -0500
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id iBKEEsO06829 for <entmib@ietf.org>; Mon, 20 Dec 2004 09:14:54 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <YZAC8S29>; Mon, 20 Dec 2004 09:14:54 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4022BF713@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: Mon, 20 Dec 2004 09:14:44 -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: d0bdc596f8dd1c226c458f0b4df27a88
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
hi There is a strong need for this MIB. Turn around times are slow since this working group hasn't responded well historically to trying to close issues quickly. We have a number of low-risk changes proposed. I suggest we make those, keep the notifications as they are and then proceed to forward things up to the IESG (without calling YAWLC (yet another working group last call)). Sharon -----Original Message----- From: Margaret Wasserman [mailto:margaret@thingmagic.com] Sent: Monday, December 20, 2004 8:35 AM To: Juergen Schoenwaelder; Chisholm, Sharon [CAR:5K50:EXCH] Cc: entmib@ietf.org Subject: Re: [Entmib] entstate-651 Notification Description Changes (Part II) Juergen and Sharon, I don't personally care whether the Entity State notifications are optional or mandatory, but I do have a concern about this discussion... This document has been through two or three WG LCs already, and now we seem to be discussing changes to features of the MIB that have been constant since the beginning. It seems like there are always 6 or more outstanding issues with this document. We fix the current issues, and then new issues are raised during the LC that is intended to check the resolutions of the previous issues. Where does this stop? At what point can we pull the plug on this discussion and declare the document "good enough"? Juergen, do you have any blocking objections to the publication of this document at this point? Or just suggestions for improvement? Personally, I think that this constant editing is a symptom of the fact that there is no driving force for the publication of this document. Do we actually care about getting this document published? If so, let's reach closure on the existing issues and publish it. If not, let's stop thrashing... Margaret >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 _______________________________________________ Entmib mailing list Entmib@ietf.org https://www1.ietf.org/mailman/listinfo/entmib
- RE: [Entmib] entstate-651 Notification Descriptio… Sharon Chisholm
- [Entmib] entstate-651 Notification Description Ch… Sharon Chisholm
- Re: [Entmib] entstate-651 Notification Descriptio… Juergen Schoenwaelder
- Re: [Entmib] entstate-651 Notification Descriptio… Juergen Schoenwaelder
- RE: [Entmib] entstate-651 Notification Descriptio… Sharon Chisholm
- Re: [Entmib] entstate-651 Notification Descriptio… Margaret Wasserman
- Re: [Entmib] entstate-651 Notification Descriptio… Juergen Schoenwaelder
- RE: [Entmib] entstate-651 Notification Descriptio… Sharon Chisholm
- RE: [Entmib] entstate-651 Notification Descriptio… Romascanu, Dan (Dan)
- Re: [Entmib] entstate-651 Notification Descriptio… Margaret Wasserman
- Re: [Entmib] entstate-651 Notification Descriptio… Juergen Schoenwaelder
- Re: [Entmib] entstate-651 Notification Descriptio… Margaret Wasserman