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

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Mon, 20 December 2004 14:42 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 JAA02325 for <entmib-archive@lists.ietf.org>; Mon, 20 Dec 2004 09:42:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgOhV-0004Ld-9X; Mon, 20 Dec 2004 09:39:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CgOaI-0003cO-7s for entmib@megatron.ietf.org; Mon, 20 Dec 2004 09:32:26 -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 JAA01526 for <entmib@ietf.org>; Mon, 20 Dec 2004 09:32:24 -0500 (EST)
Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgOjW-0001hu-6L for entmib@ietf.org; Mon, 20 Dec 2004 09:42:01 -0500
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 iBKENNja009143 for <entmib@ietf.org>; Mon, 20 Dec 2004 09:23:24 -0500 (EST)
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 iBKENLja009075 for <entmib@ietf.org>; Mon, 20 Dec 2004 09:23:22 -0500 (EST)
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Entmib] entstate-651 Notification Description Changes (Part II)
Date: Mon, 20 Dec 2004 16:32:15 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F06E3072B@is0004avexu1.global.avaya.com>
Thread-Topic: [Entmib] entstate-651 Notification Description Changes (Part II)
Thread-Index: AcTmoCLJgQyo9dW6T7WCopzqfbizjAAAG5bg
From: "Romascanu, Dan \(Dan\)" <dromasca@avaya.com>
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, <entmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Content-Transfer-Encoding: quoted-printable
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
Content-Transfer-Encoding: quoted-printable

I strongly support Sharon's statement about the need seeing this document put on the standards track. 

I also am in favor of the fast track process that Sharon is suggesting. 

Regards,

Dan



> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf Of Sharon Chisholm
> Sent: 20 December, 2004 4:15 PM
> To: entmib@ietf.org
> Subject: RE: [Entmib] entstate-651 Notification Description 
> Changes (Part II)
> 
> 
> 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
> 

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