RE: [Entmib] Entity comments

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Thu, 25 March 2004 15:44 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01411 for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 10:44:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6X1n-00022B-E5; Thu, 25 Mar 2004 10:44:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B6Wtm-0000f1-JV for entmib@optimus.ietf.org; Thu, 25 Mar 2004 10:36:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01068 for <entmib@ietf.org>; Thu, 25 Mar 2004 10:35:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B6Wtk-0000sh-00 for entmib@ietf.org; Thu, 25 Mar 2004 10:36:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B6Wss-0000pg-00 for entmib@ietf.org; Thu, 25 Mar 2004 10:35:07 -0500
Received: from ihemail2.lucent.com ([192.11.222.163] helo=ihemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 1B6WsI-0000j2-00 for entmib@ietf.org; Thu, 25 Mar 2004 10:34:30 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2PFXtZ12323 for <entmib@ietf.org>; Thu, 25 Mar 2004 09:33:56 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <16996Z01>; Thu, 25 Mar 2004 16:33:54 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503ED0541@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Sharon Chisholm <schishol@nortelnetworks.com>, entmib@ietf.org
Subject: RE: [Entmib] Entity comments
Date: Thu, 25 Mar 2004 16:33:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
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>

In hindsight (after having seen discussion over the last 2 days)
and based on:
> So, in the beginning we evaluated our options for creating 
> states and agreed
> there was value in leverage the OSI (X.731) state work rather than
> re-inventing the wheel, but as Dave indicated we said we would make
> modifications as we deemed appropriate. We have done this, 
> mainly through
> only picking the states we thought were useful, the addition 
> of enumerations
> to the states and additional descriptions of their application to our
> problem domain. 
> 
> Where we have ended up is we are somewhere in between the 
> using the OSI
> states and doing our own thing, perhaps leaning more towards 
> the OSI side.
> The positioning in this spectrum has affected the proposed 
> resolutions to a
> number of issues around naming. Even though these don't 
> affect functionality
> at all, people seem to feel strongly about them. (Yes, there are other
> issues which do affect functionality, but that's not what I'm 
> talking about
> here). Here are the high level issues
> 
> 1. Prefixing the TCs with ITU prefix. The answer to this 
> depends on where we are in that spectrum.
> 
It seems that a ITU is NOT the proper prefix.
But some prefix does make sense.

Bert

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