RE: [Entmib] WG LAST CALL: draft-ietf-entmib-state-05.txt

"Sharon Chisholm" <schishol@nortelnetworks.com> Thu, 30 September 2004 21:27 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 RAA04222 for <entmib-archive@lists.ietf.org>; Thu, 30 Sep 2004 17:27:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD88k-0002ic-39; Thu, 30 Sep 2004 17:07:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CD7cU-0003Hu-4u for entmib@megatron.ietf.org; Thu, 30 Sep 2004 16:33: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 QAA29046 for <entmib@ietf.org>; Thu, 30 Sep 2004 16:33:39 -0400 (EDT)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CD7kn-0002Yh-GL for entmib@ietf.org; Thu, 30 Sep 2004 16:42:17 -0400
Received: from zrtps0m6.us.nortel.com (zrtps0m6.us.nortel.com [47.140.192.58]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i8UKX8p02572 for <entmib@ietf.org>; Thu, 30 Sep 2004 16:33:08 -0400 (EDT)
Received: from zcard305.ca.nortel.com (zcard305.ca.nortel.com [47.129.242.61]) by zrtps0m6.us.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i8UKX6Z16426 for <entmib@ietf.org>; Thu, 30 Sep 2004 16:33:07 -0400 (EDT)
Received: by zcard305.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <T8ZG9G4S>; Thu, 30 Sep 2004 15:27:22 -0400
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4017C0892@zcarhxm2.corp.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] WG LAST CALL: draft-ietf-entmib-state-05.txt
Date: Thu, 30 Sep 2004 15:27:16 -0400
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: b19722fc8d3865b147c75ae2495625f2
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

I've opened tickets to track all of the issues except 'e', which is a
previously discussed and closed issue. I likely crammed too many points into
the first one. Time will tell.

648  Wordsmith - Various  
651  Notification Description Changes  
649  Clarification on 'this information'   
652  Security Considerations Text Changes    
650  Rename to ENTITY-STATE-TC-MIB 
653  Don't need to import the textual conventions?  

Sharon 

-----Original Message-----
From: entmib-bounces@ietf.org [mailto:entmib-bounces@ietf.org] On Behalf Of
Juergen Schoenwaelder
Sent: Wednesday, September 29, 2004 5:25 AM
To: entmib@ietf.org
Cc: Margaret Wasserman
Subject: Re: [Entmib] WG LAST CALL: draft-ietf-entmib-state-05.txt
<clip>

e) I know we have beaten this horse, but still I do not really
   understand why there are actually two MIB modules. Having two MIB
   modules only has an advantage if (a) the TCs progress faster on the
   standards track than the state MIB module or (b) some other module
   uses the TCs while the state MIB itself goes to historic. I find
   both scenarios rather unrealistic and hence you argue to simply put
   the TCs into the state MIB module.

<clip>

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