From mailman-admin@ietf.org  Mon Mar  1 09:18:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21212
	for <entmib-archive@lists.ietf.org>; Mon, 1 Mar 2004 09:18:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxoEz-0000oE-L6
	for entmib-archive@lists.ietf.org; Mon, 01 Mar 2004 09:17:53 -0500
Date: Mon, 01 Mar 2004 09:17:53 -0500
Message-ID: <20040301141753.27462.20173.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: entmib-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, entmib-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

***************************************************************************


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

        * the IETF plenary session,
        * any IETF working group or portion thereof,
        * the IESG, or any member thereof on behalf of the IESG,
        * the IAB or any member thereof on behalf of the IAB,
        * any IETF mailing list, including the IETF list itself, any
working
            group or design team list, or any other list functioning
under IETF
            auspices,
        * the RFC Editor or the Internet-Drafts function

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

   
***************************************************************************


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.ietf.org.  Thanks!

Passwords for entmib-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
entmib@ietf.org                          CNIo      
https://www1.ietf.org/mailman/options/entmib/entmib-archive%40lists.ietf.org


From entmib-admin@ietf.org  Wed Mar  3 20:38:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13170
	for <entmib-archive@lists.ietf.org>; Wed, 3 Mar 2004 20:38:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyhoH-0007ln-Cz; Wed, 03 Mar 2004 20:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyhnP-0007XJ-50
	for entmib@optimus.ietf.org; Wed, 03 Mar 2004 20:37:07 -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 UAA13131
	for <entmib@ietf.org>; Wed, 3 Mar 2004 20:37:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyhnM-0007ZR-00
	for entmib@ietf.org; Wed, 03 Mar 2004 20:37:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayhmf-0007Pl-00
	for entmib@ietf.org; Wed, 03 Mar 2004 20:36:22 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayhlx-0007GT-00
	for entmib@ietf.org; Wed, 03 Mar 2004 20:35:37 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i241Z1517110
	for <entmib@ietf.org>; Wed, 3 Mar 2004 20:35:01 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD7FHB6>; Wed, 3 Mar 2004 20:35:01 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A60B11D@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
	 ate
Date: Wed, 3 Mar 2004 20:35:01 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Ok, here is probably a better summary of the issues from Dave's email.

1. Language nit: Is it appropriate to describe the interpretation of these
objects in the context of physical entities considering the entire MIB, with
the exception of the Textual Conventions, is just talking about physical
entities?

2. Given the definition of Usage and Admin, it is not clear how to apply
'shuttingDown'. [Note there is also discussion about redesigning the TC, but
it is not clear to me what problem that is trying to solve]

3. Not sure how to map the concept of interface status of 'testing' into
this model.

4. There is discussion again about containment hierarchy and state and what
the relationships.

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Sunday, February 15, 2004 6:41 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


Hi

I'm distilling two things from this email

1. It would be good to better understand the relationship between the admin
state and the usage state to ensure there are no issues

2. There is discussion again about containment, which should be explained by
the text in section 2.1

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Thursday, February 12, 2004 4:50 PM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: Re: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin
State


HI,

I also find several problems with the current definition of the value
"shuttingDown" for AdminState.

First, the definition of usageState was radically changed in the current
draft of the document. From the DESCRIPTION clause of object entStateUsage
(with comments in "<...>"): " <text cut>

  Note that in the context of a physical entity, this
  <this is sort of silly to say "in the context of
   a physical entity", since this MIB module is
   describing physical entities>     
  object refers to an entity's ability to service more    
  physical entities in a containment hierarchy. A value   
  of 'idle' means this entity is able to contain other    
  entities but that no other entity is currently          
  contained within this entity, as would have been        
  demonstrated by a value  of entPhysicalContainedIn      
  that referenced this entity.                            
                                                        
  A value of 'active' means that at least one entity is   
  contained within this entity and therefore has a value  
  of entPhysicalContainedIn that references this entity,  
  but that it could handle more. A value of 'busy' means  
  that the entity is unable to handle any additional      
  entities being contained in it, as demonstrated by      
  having a value of entPhysicalContainedIn that refers to 
  this entity.                                            
                                                        
  Some entities will exhibit only a subset of the         
  usage state values. Entities that are unable to ever    
  service any entities within a containment hierarchy will
  always have a usage state of 'busy'. Some entities will 
  only ever be able to support one entity within its      
  containment hierarchy and will therefore only exhibit
  values of 'idle' and 'busy'."                        

Given the above, I don't know how to apply the value of "shuttingDown". But
first, let's look at the values.

Secondly, the X.731 document models the admin characteristic as with a 3
state diagram. The states are "unlocked", "shutting down", and "locked". The
"shutting down" state is meant to represent a graceful shutdown of an
"object". The event "shutdown" is a state transition from "unlocked" to
"shutting down". Another transition occurs from state "shutting down" to
"lock" when event "the last user quits" occurs. Now, if I were to model this
in SNMP's SMI, I would have an "action/state" object with values:
  locked - a state and action
  unlocked - a state and action
  shutDown - an action (a write only value) (on a SET with no
               error, a read would return either value "locked"
               or "shuttingDown")
  shuttingDown - a state (a read only value)

However, given the change of definition of the meaning of usage state, I'm a
little confused as to how to "update" the TC (and object type) definitions.
In general, I'm not sure that there is a need for a "graceful" and "force"
administrative shutdown action values. 
If "graceful" shutdown is added, then I suggest that the value of
"shuttingDown" be return until the value of "operState" is no longer
"enabled". This removes the confusing "user" terminology. (See section
3.1.13 of RFC 2863)

Thirdly, object IF-MIB::ifAdminStatus has a value of "testing". I don't know
it maps to values for AdminState. This was not covered in the document.
 
Finally, neither the IF MIB document nor X.731 describe the relationship
between the admin values and admin (and oper) values of "contained" objects.
And thus, this document does not cover this topic. It can be one of:
  1) there is no relationship
  2) the relationship is implementation defined
  3) there is no relationship between admin values, but there
      is a weak relationship between oper values (more on this
      in message about #309 (oper state values))

At 01:59 PM 2/11/2004 -0500, Sharon Chisholm wrote:
>The following is the proposed resolution to entstate-308. The issue
>will be considered closed with no changes made to the document.
>
>The following explanations were provided and no questions were raised.
>
>"
>1. Is shutting down really more an operational state?
>
>The state refers more to whether your administrative model allows 
>systems to be shut down gracefully or not. The idea being that if it 
>does, you would still have the options to bring it down less 
>gracefully. We have allowed in the description of the object for 
>systems that don't support this value for the state.
>
>2. Would 'noNewUsage' be a better term.
>
>Well, except that the idea is that once all the existing 'users' are 
>gone, the system will shut down. The term 'noNewUsage' does not really 
>reflect that."
>
>Sharon
>
>
>-----Original Message-----
>From: entity-state [mailto:rt+entity-state@rt.psg.com]
>Sent: Tuesday, January 13, 2004 2:55 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Subject: [psg.com #308] AutoReply: Shutting Down Admin State <clip>
>
>-----------------------------------------------------------------------
>--
>Keith McCloghrie [kzm@cisco.com]
>
>"
>
>the term 'shuttingDown' suggests that the action of shutting down is
>>   in progress, which of course is an operational condition, not an
>admin
>>   state.  A term more reflective of what the AdminState DESCRIPTION
>appears
>>   to define would be 'noNewUsage'.  In any case, this concept
>of 'usage'
>>   is almost always a higher-level usage (e.g., a new ATM connection
>on an
>>   ATM interface, a new Unix login on a cpu module, etc.) and thus
>don't
>>   belong at the physical layer (i.e., don't apply to
>> entPhysicalIndex).
>"
Regards,
/david t. perkins 


_______________________________________________
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


From exim@www1.ietf.org  Wed Mar  3 20:38:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13179
	for <entmib-archive@odin.ietf.org>; Wed, 3 Mar 2004 20:38:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyhoI-0007mQ-1g
	for entmib-archive@odin.ietf.org; Wed, 03 Mar 2004 20:38:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i241c1EI029886
	for entmib-archive@odin.ietf.org; Wed, 3 Mar 2004 20:38:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyhoH-0007ln-Cz; Wed, 03 Mar 2004 20:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyhnP-0007XJ-50
	for entmib@optimus.ietf.org; Wed, 03 Mar 2004 20:37:07 -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 UAA13131
	for <entmib@ietf.org>; Wed, 3 Mar 2004 20:37:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyhnM-0007ZR-00
	for entmib@ietf.org; Wed, 03 Mar 2004 20:37:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayhmf-0007Pl-00
	for entmib@ietf.org; Wed, 03 Mar 2004 20:36:22 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayhlx-0007GT-00
	for entmib@ietf.org; Wed, 03 Mar 2004 20:35:37 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i241Z1517110
	for <entmib@ietf.org>; Wed, 3 Mar 2004 20:35:01 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD7FHB6>; Wed, 3 Mar 2004 20:35:01 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A60B11D@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
	 ate
Date: Wed, 3 Mar 2004 20:35:01 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Ok, here is probably a better summary of the issues from Dave's email.

1. Language nit: Is it appropriate to describe the interpretation of these
objects in the context of physical entities considering the entire MIB, with
the exception of the Textual Conventions, is just talking about physical
entities?

2. Given the definition of Usage and Admin, it is not clear how to apply
'shuttingDown'. [Note there is also discussion about redesigning the TC, but
it is not clear to me what problem that is trying to solve]

3. Not sure how to map the concept of interface status of 'testing' into
this model.

4. There is discussion again about containment hierarchy and state and what
the relationships.

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Sunday, February 15, 2004 6:41 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


Hi

I'm distilling two things from this email

1. It would be good to better understand the relationship between the admin
state and the usage state to ensure there are no issues

2. There is discussion again about containment, which should be explained by
the text in section 2.1

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Thursday, February 12, 2004 4:50 PM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: Re: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin
State


HI,

I also find several problems with the current definition of the value
"shuttingDown" for AdminState.

First, the definition of usageState was radically changed in the current
draft of the document. From the DESCRIPTION clause of object entStateUsage
(with comments in "<...>"): " <text cut>

  Note that in the context of a physical entity, this
  <this is sort of silly to say "in the context of
   a physical entity", since this MIB module is
   describing physical entities>     
  object refers to an entity's ability to service more    
  physical entities in a containment hierarchy. A value   
  of 'idle' means this entity is able to contain other    
  entities but that no other entity is currently          
  contained within this entity, as would have been        
  demonstrated by a value  of entPhysicalContainedIn      
  that referenced this entity.                            
                                                        
  A value of 'active' means that at least one entity is   
  contained within this entity and therefore has a value  
  of entPhysicalContainedIn that references this entity,  
  but that it could handle more. A value of 'busy' means  
  that the entity is unable to handle any additional      
  entities being contained in it, as demonstrated by      
  having a value of entPhysicalContainedIn that refers to 
  this entity.                                            
                                                        
  Some entities will exhibit only a subset of the         
  usage state values. Entities that are unable to ever    
  service any entities within a containment hierarchy will
  always have a usage state of 'busy'. Some entities will 
  only ever be able to support one entity within its      
  containment hierarchy and will therefore only exhibit
  values of 'idle' and 'busy'."                        

Given the above, I don't know how to apply the value of "shuttingDown". But
first, let's look at the values.

Secondly, the X.731 document models the admin characteristic as with a 3
state diagram. The states are "unlocked", "shutting down", and "locked". The
"shutting down" state is meant to represent a graceful shutdown of an
"object". The event "shutdown" is a state transition from "unlocked" to
"shutting down". Another transition occurs from state "shutting down" to
"lock" when event "the last user quits" occurs. Now, if I were to model this
in SNMP's SMI, I would have an "action/state" object with values:
  locked - a state and action
  unlocked - a state and action
  shutDown - an action (a write only value) (on a SET with no
               error, a read would return either value "locked"
               or "shuttingDown")
  shuttingDown - a state (a read only value)

However, given the change of definition of the meaning of usage state, I'm a
little confused as to how to "update" the TC (and object type) definitions.
In general, I'm not sure that there is a need for a "graceful" and "force"
administrative shutdown action values. 
If "graceful" shutdown is added, then I suggest that the value of
"shuttingDown" be return until the value of "operState" is no longer
"enabled". This removes the confusing "user" terminology. (See section
3.1.13 of RFC 2863)

Thirdly, object IF-MIB::ifAdminStatus has a value of "testing". I don't know
it maps to values for AdminState. This was not covered in the document.
 
Finally, neither the IF MIB document nor X.731 describe the relationship
between the admin values and admin (and oper) values of "contained" objects.
And thus, this document does not cover this topic. It can be one of:
  1) there is no relationship
  2) the relationship is implementation defined
  3) there is no relationship between admin values, but there
      is a weak relationship between oper values (more on this
      in message about #309 (oper state values))

At 01:59 PM 2/11/2004 -0500, Sharon Chisholm wrote:
>The following is the proposed resolution to entstate-308. The issue
>will be considered closed with no changes made to the document.
>
>The following explanations were provided and no questions were raised.
>
>"
>1. Is shutting down really more an operational state?
>
>The state refers more to whether your administrative model allows 
>systems to be shut down gracefully or not. The idea being that if it 
>does, you would still have the options to bring it down less 
>gracefully. We have allowed in the description of the object for 
>systems that don't support this value for the state.
>
>2. Would 'noNewUsage' be a better term.
>
>Well, except that the idea is that once all the existing 'users' are 
>gone, the system will shut down. The term 'noNewUsage' does not really 
>reflect that."
>
>Sharon
>
>
>-----Original Message-----
>From: entity-state [mailto:rt+entity-state@rt.psg.com]
>Sent: Tuesday, January 13, 2004 2:55 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Subject: [psg.com #308] AutoReply: Shutting Down Admin State <clip>
>
>-----------------------------------------------------------------------
>--
>Keith McCloghrie [kzm@cisco.com]
>
>"
>
>the term 'shuttingDown' suggests that the action of shutting down is
>>   in progress, which of course is an operational condition, not an
>admin
>>   state.  A term more reflective of what the AdminState DESCRIPTION
>appears
>>   to define would be 'noNewUsage'.  In any case, this concept
>of 'usage'
>>   is almost always a higher-level usage (e.g., a new ATM connection
>on an
>>   ATM interface, a new Unix login on a cpu module, etc.) and thus
>don't
>>   belong at the physical layer (i.e., don't apply to
>> entPhysicalIndex).
>"
Regards,
/david t. perkins 


_______________________________________________
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



From entmib-admin@ietf.org  Wed Mar  3 21:11:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15893
	for <entmib-archive@lists.ietf.org>; Wed, 3 Mar 2004 21:11:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiKE-0003bw-4Z; Wed, 03 Mar 2004 21:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiJK-0003Wh-Ps
	for entmib@optimus.ietf.org; Wed, 03 Mar 2004 21:10:06 -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 VAA15708
	for <entmib@ietf.org>; Wed, 3 Mar 2004 21:10:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiJI-0006eb-00
	for entmib@ietf.org; Wed, 03 Mar 2004 21:10:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyiIL-0006Sm-00
	for entmib@ietf.org; Wed, 03 Mar 2004 21:09:05 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiHb-00069J-00
	for entmib@ietf.org; Wed, 03 Mar 2004 21:08:19 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2427mO21530
	for <entmib@ietf.org>; Wed, 3 Mar 2004 21:07:48 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD7FHH1>; Wed, 3 Mar 2004 21:07:48 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A60B136@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope
Date: Wed, 3 Mar 2004 21:07:47 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Here's my summary of the issues in this #329 thread:

1. It seems that some state/status objects apply to the entity itself, while
others relate more to its ability to do containment. This should be made
more clear.

2. It seems that there is a difference between entities which can contain
other entities and those which never will with respect to some states. This
should be made more clear.

3. Dave doesn't see a use for the usage state.

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Friday, February 13, 2004 3:06 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope


Hi

I think it is important to distinguish between standardizing on the
behaviour and characteristics of physical entities and how this information
is reported. I think when you look at different real-world products you
can't really generalize by physical class type, only by the features that
are supported. Some of the fans and power supplies I've heard about are very
sophisticated. I'm not saying that all fans and power supplies should be,
but I don't want to put anything in the MIB that would prevent these
entities from taking advantage of the reporting capabilities within the MIB.

Sharon.

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Friday, February 13, 2004 8:48 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope <clip>

In short: I think the interpretation of the states for the various entity
classes needs to be clarified. (I think Dave also wrote something in that
direction.) Without guidance from the spec, implementations will just not
use the same model and fail to interoperate.

/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


From exim@www1.ietf.org  Wed Mar  3 21:11:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15906
	for <entmib-archive@odin.ietf.org>; Wed, 3 Mar 2004 21:11:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiKE-0003cT-Ri
	for entmib-archive@odin.ietf.org; Wed, 03 Mar 2004 21:11:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i242B2dn013900
	for entmib-archive@odin.ietf.org; Wed, 3 Mar 2004 21:11:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiKE-0003bw-4Z; Wed, 03 Mar 2004 21:11:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiJK-0003Wh-Ps
	for entmib@optimus.ietf.org; Wed, 03 Mar 2004 21:10:06 -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 VAA15708
	for <entmib@ietf.org>; Wed, 3 Mar 2004 21:10:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiJI-0006eb-00
	for entmib@ietf.org; Wed, 03 Mar 2004 21:10:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyiIL-0006Sm-00
	for entmib@ietf.org; Wed, 03 Mar 2004 21:09:05 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiHb-00069J-00
	for entmib@ietf.org; Wed, 03 Mar 2004 21:08:19 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2427mO21530
	for <entmib@ietf.org>; Wed, 3 Mar 2004 21:07:48 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD7FHH1>; Wed, 3 Mar 2004 21:07:48 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A60B136@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope
Date: Wed, 3 Mar 2004 21:07:47 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Here's my summary of the issues in this #329 thread:

1. It seems that some state/status objects apply to the entity itself, while
others relate more to its ability to do containment. This should be made
more clear.

2. It seems that there is a difference between entities which can contain
other entities and those which never will with respect to some states. This
should be made more clear.

3. Dave doesn't see a use for the usage state.

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Friday, February 13, 2004 3:06 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope


Hi

I think it is important to distinguish between standardizing on the
behaviour and characteristics of physical entities and how this information
is reported. I think when you look at different real-world products you
can't really generalize by physical class type, only by the features that
are supported. Some of the fans and power supplies I've heard about are very
sophisticated. I'm not saying that all fans and power supplies should be,
but I don't want to put anything in the MIB that would prevent these
entities from taking advantage of the reporting capabilities within the MIB.

Sharon.

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Friday, February 13, 2004 8:48 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope <clip>

In short: I think the interpretation of the states for the various entity
classes needs to be clarified. (I think Dave also wrote something in that
direction.) Without guidance from the spec, implementations will just not
use the same model and fail to interoperate.

/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



From exim@www1.ietf.org  Wed Mar 10 13:04:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23693
	for <entmib-archive@odin.ietf.org>; Wed, 10 Mar 2004 13:04:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B183m-0005eO-Tc
	for entmib-archive@odin.ietf.org; Wed, 10 Mar 2004 13:04:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AI42TY021688
	for entmib-archive@odin.ietf.org; Wed, 10 Mar 2004 13:04:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B183k-0005ct-E9; Wed, 10 Mar 2004 13:04:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B183T-0005bu-Bw
	for entmib@optimus.ietf.org; Wed, 10 Mar 2004 13:03:43 -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 NAA23682
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:03:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B183R-0001a3-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:03:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B182T-0001PF-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:02:41 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B181S-00013l-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:01:38 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2AI16m19220
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:01:06 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD72HVJ>; Wed, 10 Mar 2004 13:01:06 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A74340F@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
	 ate
Date: Wed, 10 Mar 2004 13:01:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

The following is the proposed resolution to entstate-308. The issue 
will be considered closed pending the proposed edit being done.

1. In the DESCRIPTION of entStateUsage, replace

"Note that in the context of a physical entity, this
object refers to an entity's ability to service more"

with

"This object refers to an entity's ability to service more"
                              
2. In the DESCRIPTION of entStateAdmin add the following text

"This object refers to an entities administrative permission 
to service both other entities within its containment hierarchy
as well other users of its services defined by means outside the
scope of this MIB."

[Editor's Note: There used to be text along these lines here at
one point, but it was apparently removed at some point.] 

3. 'testing' has already been added to the operational status in -03.
No further edit is proposed.

4. This should be covered by the text in section 2.1. No further edit 
is proposed.

Sharon


-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 03, 2004 8:35 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


hi

Ok, here is probably a better summary of the issues from Dave's email.

1. Language nit: Is it appropriate to describe the interpretation of these
objects in the context of physical entities considering the entire MIB, with
the exception of the Textual Conventions, is just talking about physical
entities?

2. Given the definition of Usage and Admin, it is not clear how to apply
'shuttingDown'. [Note there is also discussion about redesigning the TC, but
it is not clear to me what problem that is trying to solve]

3. Not sure how to map the concept of interface status of 'testing' into
this model.

4. There is discussion again about containment hierarchy and state and what
the relationships.

Sharon

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



From entmib-admin@ietf.org  Wed Mar 10 13:04:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23695
	for <entmib-archive@lists.ietf.org>; Wed, 10 Mar 2004 13:04:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B183k-0005ct-E9; Wed, 10 Mar 2004 13:04:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B183T-0005bu-Bw
	for entmib@optimus.ietf.org; Wed, 10 Mar 2004 13:03:43 -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 NAA23682
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:03:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B183R-0001a3-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:03:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B182T-0001PF-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:02:41 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B181S-00013l-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:01:38 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2AI16m19220
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:01:06 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD72HVJ>; Wed, 10 Mar 2004 13:01:06 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A74340F@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
	 ate
Date: Wed, 10 Mar 2004 13:01:02 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

The following is the proposed resolution to entstate-308. The issue 
will be considered closed pending the proposed edit being done.

1. In the DESCRIPTION of entStateUsage, replace

"Note that in the context of a physical entity, this
object refers to an entity's ability to service more"

with

"This object refers to an entity's ability to service more"
                              
2. In the DESCRIPTION of entStateAdmin add the following text

"This object refers to an entities administrative permission 
to service both other entities within its containment hierarchy
as well other users of its services defined by means outside the
scope of this MIB."

[Editor's Note: There used to be text along these lines here at
one point, but it was apparently removed at some point.] 

3. 'testing' has already been added to the operational status in -03.
No further edit is proposed.

4. This should be covered by the text in section 2.1. No further edit 
is proposed.

Sharon


-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 03, 2004 8:35 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


hi

Ok, here is probably a better summary of the issues from Dave's email.

1. Language nit: Is it appropriate to describe the interpretation of these
objects in the context of physical entities considering the entire MIB, with
the exception of the Textual Conventions, is just talking about physical
entities?

2. Given the definition of Usage and Admin, it is not clear how to apply
'shuttingDown'. [Note there is also discussion about redesigning the TC, but
it is not clear to me what problem that is trying to solve]

3. Not sure how to map the concept of interface status of 'testing' into
this model.

4. There is discussion again about containment hierarchy and state and what
the relationships.

Sharon

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


From entmib-admin@ietf.org  Wed Mar 10 13:42:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25547
	for <entmib-archive@lists.ietf.org>; Wed, 10 Mar 2004 13:42:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B18eX-0001A5-9n; Wed, 10 Mar 2004 13:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B18dl-00018p-2o
	for entmib@optimus.ietf.org; Wed, 10 Mar 2004 13:41:13 -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 NAA25428
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:41:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B18di-0007iL-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:41:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B18d9-0007X3-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:40:36 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B18cC-0007MU-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:39:36 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2AId5m21895
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:39:05 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD722KG>; Wed, 10 Mar 2004 13:39:05 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A74349C@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope
Date: Wed, 10 Mar 2004 13:39:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

The following is the proposed resolution to entstate-329. The issue 
will be considered closed pending the proposed edit being done.

Add a new section 2.3 called "Physical Entity Users"

"There are three ways to define the 'user' of a physical entity"

1. Direct Containment in physical hierarchy

2. Anywhere in physical hierarchy

3. As defined by a means outside the scope of this MIB. This could include
logical interfaces that could run on a port, software that could run on a
module, etc.

Administrative, operational, alarm and standby state use all three
definitions of 'user'. Usage state only supports the concept of direct
containment to simplify implementations of this object."

Add a new section 2.4 called "Physical Class Behaviour"

"This MIB makes no effort to standardize on the behaviours and
characteristics of the various physical classes [RFC2737], but rather how
this information is reported. In looking at real-world products, items
within the same physical class vary substantially. The MIB has therefore
provided guidance on how to support objects where a particular instance of a
physical class can not support part or all of a particular state."

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 03, 2004 9:08 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope


hi

Here's my summary of the issues in this #329 thread:

1. It seems that some state/status objects apply to the entity itself, while
others relate more to its ability to do containment. This should be made
more clear.

2. It seems that there is a difference between entities which can contain
other entities and those which never will with respect to some states. This
should be made more clear.

3. Dave doesn't see a use for the usage state.

Sharon

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


From exim@www1.ietf.org  Wed Mar 10 13:42:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25552
	for <entmib-archive@odin.ietf.org>; Wed, 10 Mar 2004 13:42:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B18eX-0001AX-Lb
	for entmib-archive@odin.ietf.org; Wed, 10 Mar 2004 13:42:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AIg1Wk004479
	for entmib-archive@odin.ietf.org; Wed, 10 Mar 2004 13:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B18eX-0001A5-9n; Wed, 10 Mar 2004 13:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B18dl-00018p-2o
	for entmib@optimus.ietf.org; Wed, 10 Mar 2004 13:41:13 -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 NAA25428
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:41:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B18di-0007iL-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:41:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B18d9-0007X3-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:40:36 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B18cC-0007MU-00
	for entmib@ietf.org; Wed, 10 Mar 2004 13:39:36 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2AId5m21895
	for <entmib@ietf.org>; Wed, 10 Mar 2004 13:39:05 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GHD722KG>; Wed, 10 Mar 2004 13:39:05 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A74349C@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope
Date: Wed, 10 Mar 2004 13:39:04 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

The following is the proposed resolution to entstate-329. The issue 
will be considered closed pending the proposed edit being done.

Add a new section 2.3 called "Physical Entity Users"

"There are three ways to define the 'user' of a physical entity"

1. Direct Containment in physical hierarchy

2. Anywhere in physical hierarchy

3. As defined by a means outside the scope of this MIB. This could include
logical interfaces that could run on a port, software that could run on a
module, etc.

Administrative, operational, alarm and standby state use all three
definitions of 'user'. Usage state only supports the concept of direct
containment to simplify implementations of this object."

Add a new section 2.4 called "Physical Class Behaviour"

"This MIB makes no effort to standardize on the behaviours and
characteristics of the various physical classes [RFC2737], but rather how
this information is reported. In looking at real-world products, items
within the same physical class vary substantially. The MIB has therefore
provided guidance on how to support objects where a particular instance of a
physical class can not support part or all of a particular state."

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 03, 2004 9:08 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #329] AutoReply: Usage State Scope


hi

Here's my summary of the issues in this #329 thread:

1. It seems that some state/status objects apply to the entity itself, while
others relate more to its ability to do containment. This should be made
more clear.

2. It seems that there is a difference between entities which can contain
other entities and those which never will with respect to some states. This
should be made more clear.

3. Dave doesn't see a use for the usage state.

Sharon

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



From entmib-admin@ietf.org  Wed Mar 17 08:12:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04907
	for <entmib-archive@lists.ietf.org>; Wed, 17 Mar 2004 08:12:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3aq2-0008OM-Fa; Wed, 17 Mar 2004 08:12:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3apa-0008N1-5k
	for entmib@optimus.ietf.org; Wed, 17 Mar 2004 08:11:34 -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 IAA04870
	for <entmib@ietf.org>; Wed, 17 Mar 2004 08:11:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3apZ-0002Ci-00
	for entmib@ietf.org; Wed, 17 Mar 2004 08:11:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3apD-00026d-00
	for entmib@ietf.org; Wed, 17 Mar 2004 08:11:12 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3aoN-0001zz-00
	for entmib@ietf.org; Wed, 17 Mar 2004 08:10:20 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2HD9kf07245
	for <entmib@ietf.org>; Wed, 17 Mar 2004 08:09:46 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6GR8K>; Wed, 17 Mar 2004 08:09:46 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A8248FA@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
	 ate
Date: Wed, 17 Mar 2004 08:09:45 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

In reviewing the draft, I have found that there is text in section 3.1 and
3.4 that needs to be updated to reflect the addition of the 'testing'
operational status. This change will also be made.

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 10, 2004 1:01 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


The following is the proposed resolution to entstate-308. The issue 
will be considered closed pending the proposed edit being done.

1. In the DESCRIPTION of entStateUsage, replace

"Note that in the context of a physical entity, this
object refers to an entity's ability to service more"

with

"This object refers to an entity's ability to service more"
                              
2. In the DESCRIPTION of entStateAdmin add the following text

"This object refers to an entities administrative permission 
to service both other entities within its containment hierarchy as well
other users of its services defined by means outside the scope of this MIB."

[Editor's Note: There used to be text along these lines here at one point,
but it was apparently removed at some point.] 

3. 'testing' has already been added to the operational status in -03. No
further edit is proposed.

4. This should be covered by the text in section 2.1. No further edit 
is proposed.

Sharon


-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 03, 2004 8:35 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


hi

Ok, here is probably a better summary of the issues from Dave's email.

1. Language nit: Is it appropriate to describe the interpretation of these
objects in the context of physical entities considering the entire MIB, with
the exception of the Textual Conventions, is just talking about physical
entities?

2. Given the definition of Usage and Admin, it is not clear how to apply
'shuttingDown'. [Note there is also discussion about redesigning the TC, but
it is not clear to me what problem that is trying to solve]

3. Not sure how to map the concept of interface status of 'testing' into
this model.

4. There is discussion again about containment hierarchy and state and what
the relationships.

Sharon

_______________________________________________
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


From exim@www1.ietf.org  Wed Mar 17 09:05:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04909
	for <entmib-archive@odin.ietf.org>; Wed, 17 Mar 2004 08:12:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3aq4-0008Oz-NH
	for entmib-archive@odin.ietf.org; Wed, 17 Mar 2004 08:12:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HDC47R032269
	for entmib-archive@odin.ietf.org; Wed, 17 Mar 2004 08:12:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3aq2-0008OM-Fa; Wed, 17 Mar 2004 08:12:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3apa-0008N1-5k
	for entmib@optimus.ietf.org; Wed, 17 Mar 2004 08:11:34 -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 IAA04870
	for <entmib@ietf.org>; Wed, 17 Mar 2004 08:11:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3apZ-0002Ci-00
	for entmib@ietf.org; Wed, 17 Mar 2004 08:11:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3apD-00026d-00
	for entmib@ietf.org; Wed, 17 Mar 2004 08:11:12 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3aoN-0001zz-00
	for entmib@ietf.org; Wed, 17 Mar 2004 08:10:20 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2HD9kf07245
	for <entmib@ietf.org>; Wed, 17 Mar 2004 08:09:46 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6GR8K>; Wed, 17 Mar 2004 08:09:46 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A8248FA@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
	 ate
Date: Wed, 17 Mar 2004 08:09:45 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

In reviewing the draft, I have found that there is text in section 3.1 and
3.4 that needs to be updated to reflect the addition of the 'testing'
operational status. This change will also be made.

Sharon

-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 10, 2004 1:01 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


The following is the proposed resolution to entstate-308. The issue 
will be considered closed pending the proposed edit being done.

1. In the DESCRIPTION of entStateUsage, replace

"Note that in the context of a physical entity, this
object refers to an entity's ability to service more"

with

"This object refers to an entity's ability to service more"
                              
2. In the DESCRIPTION of entStateAdmin add the following text

"This object refers to an entities administrative permission 
to service both other entities within its containment hierarchy as well
other users of its services defined by means outside the scope of this MIB."

[Editor's Note: There used to be text along these lines here at one point,
but it was apparently removed at some point.] 

3. 'testing' has already been added to the operational status in -03. No
further edit is proposed.

4. This should be covered by the text in section 2.1. No further edit 
is proposed.

Sharon


-----Original Message-----
From: Chisholm, Sharon [CAR:0S00:EXCH] 
Sent: Wednesday, March 03, 2004 8:35 PM
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #308] AutoReply: Shutting Down Admin St
ate


hi

Ok, here is probably a better summary of the issues from Dave's email.

1. Language nit: Is it appropriate to describe the interpretation of these
objects in the context of physical entities considering the entire MIB, with
the exception of the Textual Conventions, is just talking about physical
entities?

2. Given the definition of Usage and Admin, it is not clear how to apply
'shuttingDown'. [Note there is also discussion about redesigning the TC, but
it is not clear to me what problem that is trying to solve]

3. Not sure how to map the concept of interface status of 'testing' into
this model.

4. There is discussion again about containment hierarchy and state and what
the relationships.

Sharon

_______________________________________________
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



From entmib-admin@ietf.org  Mon Mar 22 08:16:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22440
	for <entmib-archive@lists.ietf.org>; Mon, 22 Mar 2004 08:16:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5PHd-0006MZ-E0; Mon, 22 Mar 2004 08:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5PH4-0006Iw-28
	for entmib@optimus.ietf.org; Mon, 22 Mar 2004 08:15:26 -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 IAA22309
	for <entmib@ietf.org>; Mon, 22 Mar 2004 08:15:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5PH3-0006vA-00
	for entmib@ietf.org; Mon, 22 Mar 2004 08:15:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5PG7-0006ol-00
	for entmib@ietf.org; Mon, 22 Mar 2004 08:14:28 -0500
Received: from smtp.exodus.net ([66.35.230.237] helo=smtp02-w.exodus.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5PFD-0006cQ-00
	for entmib@ietf.org; Mon, 22 Mar 2004 08:13:31 -0500
Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174])
	by smtp02-w.exodus.net (8.12.8/8.12.8) with ESMTP id i2MAKqEv019090
	for <entmib@ietf.org>; Mon, 22 Mar 2004 04:20:52 -0600
Received: from [192.168.2.2] (unverified [24.61.30.237]) by accounting.espmail.com
 (Rockliffe SMTPRA 5.2.5) with ESMTP id <B0018844189@ms101.mail1.com> for <entmib@ietf.org>;
 Mon, 22 Mar 2004 05:12:55 -0800
Mime-Version: 1.0
X-Sender: margaret@thingmagic.com@ms101.mail1.com
Message-Id: <p0602043ebc849527e216@[192.168.2.2]>
Date: Mon, 22 Mar 2004 08:12:52 -0500
To: entmib@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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
Subject: [Entmib] Final Closure on Entity State MIB Issues
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>


Hi All,

Sharon has proposed changes to all of the issues that have been 
raised regarding the Entity State MIB.  The proposed resolutions can 
be found at:   http://rt.psg.com (userid: ietf, password: ietf). 
Please review Sharon's proposed changes and send mail to the list by 
this Friday (26-Mar-2004) if you have any objections to the 
resolutions that Sharon has proposed.  If there are any contentious 
issues, let's discuss them so that we can determine WG consensus 
regarding their resolution.

We are quite close to finishing this document, so if there are any 
remaining issue, please get them on the table as soon as possible.

Thanks,
Margaret



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


From exim@www1.ietf.org  Mon Mar 22 08:16:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22442
	for <entmib-archive@odin.ietf.org>; Mon, 22 Mar 2004 08:16:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5PHe-0006NB-29
	for entmib-archive@odin.ietf.org; Mon, 22 Mar 2004 08:16:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MDG1TQ024481
	for entmib-archive@odin.ietf.org; Mon, 22 Mar 2004 08:16:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5PHd-0006MZ-E0; Mon, 22 Mar 2004 08:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5PH4-0006Iw-28
	for entmib@optimus.ietf.org; Mon, 22 Mar 2004 08:15:26 -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 IAA22309
	for <entmib@ietf.org>; Mon, 22 Mar 2004 08:15:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5PH3-0006vA-00
	for entmib@ietf.org; Mon, 22 Mar 2004 08:15:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5PG7-0006ol-00
	for entmib@ietf.org; Mon, 22 Mar 2004 08:14:28 -0500
Received: from smtp.exodus.net ([66.35.230.237] helo=smtp02-w.exodus.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5PFD-0006cQ-00
	for entmib@ietf.org; Mon, 22 Mar 2004 08:13:31 -0500
Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174])
	by smtp02-w.exodus.net (8.12.8/8.12.8) with ESMTP id i2MAKqEv019090
	for <entmib@ietf.org>; Mon, 22 Mar 2004 04:20:52 -0600
Received: from [192.168.2.2] (unverified [24.61.30.237]) by accounting.espmail.com
 (Rockliffe SMTPRA 5.2.5) with ESMTP id <B0018844189@ms101.mail1.com> for <entmib@ietf.org>;
 Mon, 22 Mar 2004 05:12:55 -0800
Mime-Version: 1.0
X-Sender: margaret@thingmagic.com@ms101.mail1.com
Message-Id: <p0602043ebc849527e216@[192.168.2.2]>
Date: Mon, 22 Mar 2004 08:12:52 -0500
To: entmib@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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
Subject: [Entmib] Final Closure on Entity State MIB Issues
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>


Hi All,

Sharon has proposed changes to all of the issues that have been 
raised regarding the Entity State MIB.  The proposed resolutions can 
be found at:   http://rt.psg.com (userid: ietf, password: ietf). 
Please review Sharon's proposed changes and send mail to the list by 
this Friday (26-Mar-2004) if you have any objections to the 
resolutions that Sharon has proposed.  If there are any contentious 
issues, let's discuss them so that we can determine WG consensus 
regarding their resolution.

We are quite close to finishing this document, so if there are any 
remaining issue, please get them on the table as soon as possible.

Thanks,
Margaret



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



From entmib-admin@ietf.org  Mon Mar 22 16:34:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25733
	for <entmib-archive@lists.ietf.org>; Mon, 22 Mar 2004 16:34:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X3a-0003SK-5z; Mon, 22 Mar 2004 16:34:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X2S-0003Qp-M3
	for entmib@optimus.ietf.org; Mon, 22 Mar 2004 16:32:56 -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 QAA25669
	for <entmib@ietf.org>; Mon, 22 Mar 2004 16:32:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X2Q-0001LG-00
	for entmib@ietf.org; Mon, 22 Mar 2004 16:32:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5X1f-0001F8-00
	for entmib@ietf.org; Mon, 22 Mar 2004 16:32:04 -0500
Received: from g4182.g.pppool.de ([80.185.65.130] helo=james.eecs.iu-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X1A-00018a-00
	for entmib@ietf.org; Mon, 22 Mar 2004 16:31:33 -0500
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id B90C58515; Mon, 22 Mar 2004 22:31:31 +0100 (CET)
Date: Mon, 22 Mar 2004 22:31:31 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Margaret Wasserman <margaret@thingmagic.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] Final Closure on Entity State MIB Issues
Message-ID: <20040322213131.GB2294@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Margaret Wasserman <margaret@thingmagic.com>,
	entmib@ietf.org
References: <p0602043ebc849527e216@[192.168.2.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p0602043ebc849527e216@[192.168.2.2]>
User-Agent: Mutt/1.5.5.1+cvs20040105i
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=none 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>

On Mon, Mar 22, 2004 at 08:12:52AM -0500, Margaret Wasserman wrote:
 
> Sharon has proposed changes to all of the issues that have been 
> raised regarding the Entity State MIB.  The proposed resolutions can 
> be found at:   http://rt.psg.com (userid: ietf, password: ietf). 
> Please review Sharon's proposed changes and send mail to the list by 
> this Friday (26-Mar-2004) if you have any objections to the 
> resolutions that Sharon has proposed.  If there are any contentious 
> issues, let's discuss them so that we can determine WG consensus 
> regarding their resolution.

I went through all the issues and here is what I think where we are
with respect to the various issues. Note that the server does seem
to have some problems at the moment.

#306: entStateTrap rename/oid to entStateNotifs

	OK

#307: 'notSupported' is semantically wrong

	I think "unknown" as suggested by Keith is what we typically
	use and prefer this over "unavailable" or any other terms.

#308: Shutting Down Admin State

	I tend to agree with Keith' comment and I do not think that
	the response addresses Keith issue with the name/state itself.

#309: Operational State Names and Concepts

	I am not sure I understand the issue so I keep silent.

#310: Alarm State Issues

	OK

#311: DateAndTimeOrZero ?

	The new text refers to the initialization of "the local
	system" - whatever that may be. In a subagent environment, the
	actual instrumentation might not have easy access to what an
	operator would consider "the local system". So I think it
	would be better to adopt the approach where a the special
	value '0000000000000000'H is returned. Sure, this value falls
	not strictly under the DateAndTime TC set of values, but we
	have several MIBs using this special value on the standards
	track so this should work here as well.

#312: Locked Admin State

	I am not sure I understand the issue so I keep silent.

#322: Textual Convention Names (Prefix)

	I think the TC names should be prefixed.

#325:

	The figures in the discussion of this issue are wrong as
	xxxCompliances(1) and xxxGroups(2) are typically registered
	below xxxConformance(2).

#326: Too many state objects

	Andy wants a "green light" MIB which this is not supposed
	to be. There is no way to resolve this issue.

#327: More Editorial Issues

	OK

#328: Containment Hierach and entPhysicalContainedin

	I think this issue is not really solved. It must be clear in
	all cases where a description clause talks about containment
	what this really means.

#329: Usage State Scope

	OK, although I would prefer to have the semantics spelled out
        in the relevant description clauses as well.

#330: Notification Varbinds

	OK

#332: More Standby State/Status Issues

	I am not sure I understand the issue so I keep silent.

#333: Relationship with Alarm MIB

	OK

#334: Table, Index Descriptions

	I am having problems with the suggested new text. In
	particular the following sentence:

	Entries appear in this table for values of entPhysicalClass
        [RFC2737] that in this implementation are able to report any
        of the state or status stored in this table.

	I think that the class is not necessarily the property which
	defines whether a component will be able to report useful
	information in a subagent environment. I think this sentence
	hurts more than it helps. BTW, the most obvious reason for
	sparse augmentations is that new hardware and software will in
	practice be mixed with old hardware and software in subagent
	environments. (Not sure we need to document this. I think it
	is sufficient to say it is a sparse augmentation.)

#335: Notification Comments

	To me, entStateStandby related notifications might make sense
	and this should not be ruled out by being late. However, there
	needs to be a concrete proposal to look at. Without a concrete
	proposal, no change seems OK.

/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


From exim@www1.ietf.org  Mon Mar 22 16:34:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25739
	for <entmib-archive@odin.ietf.org>; Mon, 22 Mar 2004 16:34:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X3a-0003Sf-Vy
	for entmib-archive@odin.ietf.org; Mon, 22 Mar 2004 16:34:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MLY2wm013302
	for entmib-archive@odin.ietf.org; Mon, 22 Mar 2004 16:34:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X3a-0003SK-5z; Mon, 22 Mar 2004 16:34:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X2S-0003Qp-M3
	for entmib@optimus.ietf.org; Mon, 22 Mar 2004 16:32:56 -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 QAA25669
	for <entmib@ietf.org>; Mon, 22 Mar 2004 16:32:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X2Q-0001LG-00
	for entmib@ietf.org; Mon, 22 Mar 2004 16:32:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5X1f-0001F8-00
	for entmib@ietf.org; Mon, 22 Mar 2004 16:32:04 -0500
Received: from g4182.g.pppool.de ([80.185.65.130] helo=james.eecs.iu-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X1A-00018a-00
	for entmib@ietf.org; Mon, 22 Mar 2004 16:31:33 -0500
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id B90C58515; Mon, 22 Mar 2004 22:31:31 +0100 (CET)
Date: Mon, 22 Mar 2004 22:31:31 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Margaret Wasserman <margaret@thingmagic.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] Final Closure on Entity State MIB Issues
Message-ID: <20040322213131.GB2294@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Margaret Wasserman <margaret@thingmagic.com>,
	entmib@ietf.org
References: <p0602043ebc849527e216@[192.168.2.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p0602043ebc849527e216@[192.168.2.2]>
User-Agent: Mutt/1.5.5.1+cvs20040105i
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=none 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>

On Mon, Mar 22, 2004 at 08:12:52AM -0500, Margaret Wasserman wrote:
 
> Sharon has proposed changes to all of the issues that have been 
> raised regarding the Entity State MIB.  The proposed resolutions can 
> be found at:   http://rt.psg.com (userid: ietf, password: ietf). 
> Please review Sharon's proposed changes and send mail to the list by 
> this Friday (26-Mar-2004) if you have any objections to the 
> resolutions that Sharon has proposed.  If there are any contentious 
> issues, let's discuss them so that we can determine WG consensus 
> regarding their resolution.

I went through all the issues and here is what I think where we are
with respect to the various issues. Note that the server does seem
to have some problems at the moment.

#306: entStateTrap rename/oid to entStateNotifs

	OK

#307: 'notSupported' is semantically wrong

	I think "unknown" as suggested by Keith is what we typically
	use and prefer this over "unavailable" or any other terms.

#308: Shutting Down Admin State

	I tend to agree with Keith' comment and I do not think that
	the response addresses Keith issue with the name/state itself.

#309: Operational State Names and Concepts

	I am not sure I understand the issue so I keep silent.

#310: Alarm State Issues

	OK

#311: DateAndTimeOrZero ?

	The new text refers to the initialization of "the local
	system" - whatever that may be. In a subagent environment, the
	actual instrumentation might not have easy access to what an
	operator would consider "the local system". So I think it
	would be better to adopt the approach where a the special
	value '0000000000000000'H is returned. Sure, this value falls
	not strictly under the DateAndTime TC set of values, but we
	have several MIBs using this special value on the standards
	track so this should work here as well.

#312: Locked Admin State

	I am not sure I understand the issue so I keep silent.

#322: Textual Convention Names (Prefix)

	I think the TC names should be prefixed.

#325:

	The figures in the discussion of this issue are wrong as
	xxxCompliances(1) and xxxGroups(2) are typically registered
	below xxxConformance(2).

#326: Too many state objects

	Andy wants a "green light" MIB which this is not supposed
	to be. There is no way to resolve this issue.

#327: More Editorial Issues

	OK

#328: Containment Hierach and entPhysicalContainedin

	I think this issue is not really solved. It must be clear in
	all cases where a description clause talks about containment
	what this really means.

#329: Usage State Scope

	OK, although I would prefer to have the semantics spelled out
        in the relevant description clauses as well.

#330: Notification Varbinds

	OK

#332: More Standby State/Status Issues

	I am not sure I understand the issue so I keep silent.

#333: Relationship with Alarm MIB

	OK

#334: Table, Index Descriptions

	I am having problems with the suggested new text. In
	particular the following sentence:

	Entries appear in this table for values of entPhysicalClass
        [RFC2737] that in this implementation are able to report any
        of the state or status stored in this table.

	I think that the class is not necessarily the property which
	defines whether a component will be able to report useful
	information in a subagent environment. I think this sentence
	hurts more than it helps. BTW, the most obvious reason for
	sparse augmentations is that new hardware and software will in
	practice be mixed with old hardware and software in subagent
	environments. (Not sure we need to document this. I think it
	is sufficient to say it is a sparse augmentation.)

#335: Notification Comments

	To me, entStateStandby related notifications might make sense
	and this should not be ruled out by being late. However, there
	needs to be a concrete proposal to look at. Without a concrete
	proposal, no change seems OK.

/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



From entmib-admin@ietf.org  Tue Mar 23 09:30:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28987
	for <entmib-archive@lists.ietf.org>; Tue, 23 Mar 2004 09:30:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5mun-0002ZT-1t; Tue, 23 Mar 2004 09:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5muc-0002YY-DU
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 09:29:50 -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 JAA28920
	for <entmib@ietf.org>; Tue, 23 Mar 2004 09:29:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5mua-0001aQ-00
	for entmib@ietf.org; Tue, 23 Mar 2004 09:29:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5mtS-0001QS-00
	for entmib@ietf.org; Tue, 23 Mar 2004 09:28:39 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5msv-0001GB-00
	for entmib@ietf.org; Tue, 23 Mar 2004 09:28:05 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2NERV522569
	for <entmib@ietf.org>; Tue, 23 Mar 2004 09:27:31 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT62538>; Tue, 23 Mar 2004 09:27:31 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A967516@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 09:27:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

I've updated the issues in http://rt.psg.com. The tool often has a lot of
issues with timeouts and things. I've learned a few tricks to work around
them.

Comments inline...

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Monday, March 22, 2004 4:32 PM
To: Margaret Wasserman
Cc: entmib@ietf.org
Subject: Re: [Entmib] Final Closure on Entity State MIB Issues
<clip>


#307: 'notSupported' is semantically wrong

	I think "unknown" as suggested by Keith is what we typically
	use and prefer this over "unavailable" or any other terms.

Sharon> I don't have a strong opinion on this. Others did though.

#308: Shutting Down Admin State

	I tend to agree with Keith' comment and I do not think that
	the response addresses Keith issue with the name/state itself.

Sharon> Well, shutting down has to be an administrative state since you have
a choice of graceful shutdown and just shutting it down. As far as the name
goes, in order to fully describe state, it would have to be
'noNewUsageThenShuttingDown'. It's sort of a fun name, but some may think it
too long.

<clip>

#311: DateAndTimeOrZero ?

	The new text refers to the initialization of "the local
	system" - whatever that may be. In a subagent environment, the
	actual instrumentation might not have easy access to what an
	operator would consider "the local system". So I think it
	would be better to adopt the approach where a the special
	value '0000000000000000'H is returned. Sure, this value falls
	not strictly under the DateAndTime TC set of values, but we
	have several MIBs using this special value on the standards
	track so this should work here as well.

Sharon> I like this simpler approach. I had been half way down the path of
defining new TCs to behave like this when I looked up how we did it in the
Alarm MIB. Would answering the question of what the 'local system' is or
using a better term help?

<clip>

#322: Textual Convention Names (Prefix)

	I think the TC names should be prefixed.

Sharon> Ok. I think we need to step back a level on this one. We seemed to
have had agreement on the list that if the TCs were intended to be not
specific to Entities, then they should not have the prefix but if they were
they should. So, I suspect we are disagreeing on whether these TCs are
specific to Entities. I certainly never intended them to be and went out of
my way to ensure they weren't. Is there something in their definition that
leads you to believe they are limited in their application to Entities?

#325:

	The figures in the discussion of this issue are wrong as
	xxxCompliances(1) and xxxGroups(2) are typically registered
	below xxxConformance(2).

Sharon> This is from the MIB Review Guidelines. 

<clip>

#328: Containment Hierach and entPhysicalContainedin

	I think this issue is not really solved. It must be clear in
	all cases where a description clause talks about containment
	what this really means.

Sharon> Embedded? Perhaps.

<clip>


#334: Table, Index Descriptions

	I am having problems with the suggested new text. In
	particular the following sentence:

	Entries appear in this table for values of entPhysicalClass
        [RFC2737] that in this implementation are able to report any
        of the state or status stored in this table.

	I think that the class is not necessarily the property which
	defines whether a component will be able to report useful
	information in a subagent environment. I think this sentence
	hurts more than it helps. BTW, the most obvious reason for
	sparse augmentations is that new hardware and software will in
	practice be mixed with old hardware and software in subagent
	environments. (Not sure we need to document this. I think it
	is sufficient to say it is a sparse augmentation.)

Sharon>I have had a lot of trouble with this text since I actually don't
think this table should be sparse augment. I was just going with a working
group consensus we agreed to a long time ago. Your reasons makes more sense.
I'll try to rework the text.

#335: Notification Comments

	To me, entStateStandby related notifications might make sense
	and this should not be ruled out by being late. However, there
	needs to be a concrete proposal to look at. Without a concrete
	proposal, no change seems OK.

Sharon> Ok, so in the absence of that ...


Sharon

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


From exim@www1.ietf.org  Tue Mar 23 09:30:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28998
	for <entmib-archive@odin.ietf.org>; Tue, 23 Mar 2004 09:30:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5mup-0002a8-Fu
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 09:30:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NEU3YF009916
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 09:30:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5mun-0002ZT-1t; Tue, 23 Mar 2004 09:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5muc-0002YY-DU
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 09:29:50 -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 JAA28920
	for <entmib@ietf.org>; Tue, 23 Mar 2004 09:29:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5mua-0001aQ-00
	for entmib@ietf.org; Tue, 23 Mar 2004 09:29:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5mtS-0001QS-00
	for entmib@ietf.org; Tue, 23 Mar 2004 09:28:39 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5msv-0001GB-00
	for entmib@ietf.org; Tue, 23 Mar 2004 09:28:05 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2NERV522569
	for <entmib@ietf.org>; Tue, 23 Mar 2004 09:27:31 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT62538>; Tue, 23 Mar 2004 09:27:31 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A967516@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 09:27:26 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

I've updated the issues in http://rt.psg.com. The tool often has a lot of
issues with timeouts and things. I've learned a few tricks to work around
them.

Comments inline...

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Monday, March 22, 2004 4:32 PM
To: Margaret Wasserman
Cc: entmib@ietf.org
Subject: Re: [Entmib] Final Closure on Entity State MIB Issues
<clip>


#307: 'notSupported' is semantically wrong

	I think "unknown" as suggested by Keith is what we typically
	use and prefer this over "unavailable" or any other terms.

Sharon> I don't have a strong opinion on this. Others did though.

#308: Shutting Down Admin State

	I tend to agree with Keith' comment and I do not think that
	the response addresses Keith issue with the name/state itself.

Sharon> Well, shutting down has to be an administrative state since you have
a choice of graceful shutdown and just shutting it down. As far as the name
goes, in order to fully describe state, it would have to be
'noNewUsageThenShuttingDown'. It's sort of a fun name, but some may think it
too long.

<clip>

#311: DateAndTimeOrZero ?

	The new text refers to the initialization of "the local
	system" - whatever that may be. In a subagent environment, the
	actual instrumentation might not have easy access to what an
	operator would consider "the local system". So I think it
	would be better to adopt the approach where a the special
	value '0000000000000000'H is returned. Sure, this value falls
	not strictly under the DateAndTime TC set of values, but we
	have several MIBs using this special value on the standards
	track so this should work here as well.

Sharon> I like this simpler approach. I had been half way down the path of
defining new TCs to behave like this when I looked up how we did it in the
Alarm MIB. Would answering the question of what the 'local system' is or
using a better term help?

<clip>

#322: Textual Convention Names (Prefix)

	I think the TC names should be prefixed.

Sharon> Ok. I think we need to step back a level on this one. We seemed to
have had agreement on the list that if the TCs were intended to be not
specific to Entities, then they should not have the prefix but if they were
they should. So, I suspect we are disagreeing on whether these TCs are
specific to Entities. I certainly never intended them to be and went out of
my way to ensure they weren't. Is there something in their definition that
leads you to believe they are limited in their application to Entities?

#325:

	The figures in the discussion of this issue are wrong as
	xxxCompliances(1) and xxxGroups(2) are typically registered
	below xxxConformance(2).

Sharon> This is from the MIB Review Guidelines. 

<clip>

#328: Containment Hierach and entPhysicalContainedin

	I think this issue is not really solved. It must be clear in
	all cases where a description clause talks about containment
	what this really means.

Sharon> Embedded? Perhaps.

<clip>


#334: Table, Index Descriptions

	I am having problems with the suggested new text. In
	particular the following sentence:

	Entries appear in this table for values of entPhysicalClass
        [RFC2737] that in this implementation are able to report any
        of the state or status stored in this table.

	I think that the class is not necessarily the property which
	defines whether a component will be able to report useful
	information in a subagent environment. I think this sentence
	hurts more than it helps. BTW, the most obvious reason for
	sparse augmentations is that new hardware and software will in
	practice be mixed with old hardware and software in subagent
	environments. (Not sure we need to document this. I think it
	is sufficient to say it is a sparse augmentation.)

Sharon>I have had a lot of trouble with this text since I actually don't
think this table should be sparse augment. I was just going with a working
group consensus we agreed to a long time ago. Your reasons makes more sense.
I'll try to rework the text.

#335: Notification Comments

	To me, entStateStandby related notifications might make sense
	and this should not be ruled out by being late. However, there
	needs to be a concrete proposal to look at. Without a concrete
	proposal, no change seems OK.

Sharon> Ok, so in the absence of that ...


Sharon

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



From entmib-admin@ietf.org  Tue Mar 23 10:17:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02428
	for <entmib-archive@lists.ietf.org>; Tue, 23 Mar 2004 10:17:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5neH-0003Kq-2H; Tue, 23 Mar 2004 10:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5ndc-0003CB-0g
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 10:16:20 -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 KAA02300
	for <entmib@ietf.org>; Tue, 23 Mar 2004 10:16:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ndY-0000Ih-00
	for entmib@ietf.org; Tue, 23 Mar 2004 10:16:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ncb-0000Bb-00
	for entmib@ietf.org; Tue, 23 Mar 2004 10:15:18 -0500
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5nbm-0007lw-00
	for entmib@ietf.org; Tue, 23 Mar 2004 10:14:26 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2NFDH215618
	for <entmib@ietf.org>; Tue, 23 Mar 2004 09:13:26 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72)
	id <1699ZYFP>; Tue, 23 Mar 2004 16:13:15 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503DB1146@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Sharon Chisholm <schishol@nortelnetworks.com>, entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 16:13:13 +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>

> #322: Textual Convention Names (Prefix)
> 
> 	I think the TC names should be prefixed.
> 
> Sharon> Ok. I think we need to step back a level on this one. 
> We seemed to
> have had agreement on the list that if the TCs were intended to be not
> specific to Entities, then they should not have the prefix 
> but if they were
> they should. So, I suspect we are disagreeing on whether these TCs are
> specific to Entities. I certainly never intended them to be 
> and went out of
> my way to ensure they weren't. Is there something in their 
> definition that
> leads you to believe they are limited in their application to 
> Entities?
> 

It seems to me that your TCs shoudl be prefixed with something aka

   ItuXxxx
   
or
   UtuX731Xxxx

That is what they claim to represent.
And having said that... should it be a separate ITU module (i.e. have ITU
in the name and TC-MIB as a suffix) ??
Maybe to heavy ?

> #325:
> 
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> 
> Sharon> This is from the MIB Review Guidelines. 
> 
I think Juergen meant to say that you are using xxxConformance(3)
while you should be using xxxConformance(2).

Your OIDs look like:
OID tree
1.3.6.1.2.1.xx  entityStateMIB  [ENTITY-STATE-MIB]: module-identity
1.3.6.1.2.1.xx.0  entStateNotifications  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.0.1  entStateOperEnabled  [ENTITY-STATE-MIB]: notification-type
1.3.6.1.2.1.xx.0.2  entStateOperDisabled  [ENTITY-STATE-MIB]: notification-type
1.3.6.1.2.1.xx.1  entStateObjects  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.1.1  entStateTable  [ENTITY-STATE-MIB]: table-object-type
1.3.6.1.2.1.xx.1.1.1  entStateEntry  [ENTITY-STATE-MIB]: row-object-type
1.3.6.1.2.1.xx.1.1.1.1  entStateLastChanged  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.2  entStateAdmin  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.3  entStateOper  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.4  entStateUsage  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.5  entStateAlarm  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.6  entStateStandby  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.3  entStateConformance  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.1  entStateCompliances  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.1.1  entStateCompliance  [ENTITY-STATE-MIB]: module-compliance
1.3.6.1.2.1.xx.3.2  entStateGroups  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.2.1  entStateGroup  [ENTITY-STATE-MIB]: object-group
1.3.6.1.2.1.xx.3.2.2  entStateNotificationsGroup  [ENTITY-STATE-MIB]: notification-group
**end of oid tree**

And so 1.3.6.1.2.1.xx.2 was skipped (for as far as we can tell no good reason).



Bert

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


From exim@www1.ietf.org  Tue Mar 23 10:17:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02443
	for <entmib-archive@odin.ietf.org>; Tue, 23 Mar 2004 10:17:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5neH-0003LS-OM
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 10:17:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NFH1IK012837
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 10:17:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5neH-0003Kq-2H; Tue, 23 Mar 2004 10:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5ndc-0003CB-0g
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 10:16:20 -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 KAA02300
	for <entmib@ietf.org>; Tue, 23 Mar 2004 10:16:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ndY-0000Ih-00
	for entmib@ietf.org; Tue, 23 Mar 2004 10:16:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ncb-0000Bb-00
	for entmib@ietf.org; Tue, 23 Mar 2004 10:15:18 -0500
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5nbm-0007lw-00
	for entmib@ietf.org; Tue, 23 Mar 2004 10:14:26 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2NFDH215618
	for <entmib@ietf.org>; Tue, 23 Mar 2004 09:13:26 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72)
	id <1699ZYFP>; Tue, 23 Mar 2004 16:13:15 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503DB1146@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Sharon Chisholm <schishol@nortelnetworks.com>, entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 16:13:13 +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>

> #322: Textual Convention Names (Prefix)
> 
> 	I think the TC names should be prefixed.
> 
> Sharon> Ok. I think we need to step back a level on this one. 
> We seemed to
> have had agreement on the list that if the TCs were intended to be not
> specific to Entities, then they should not have the prefix 
> but if they were
> they should. So, I suspect we are disagreeing on whether these TCs are
> specific to Entities. I certainly never intended them to be 
> and went out of
> my way to ensure they weren't. Is there something in their 
> definition that
> leads you to believe they are limited in their application to 
> Entities?
> 

It seems to me that your TCs shoudl be prefixed with something aka

   ItuXxxx
   
or
   UtuX731Xxxx

That is what they claim to represent.
And having said that... should it be a separate ITU module (i.e. have ITU
in the name and TC-MIB as a suffix) ??
Maybe to heavy ?

> #325:
> 
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> 
> Sharon> This is from the MIB Review Guidelines. 
> 
I think Juergen meant to say that you are using xxxConformance(3)
while you should be using xxxConformance(2).

Your OIDs look like:
OID tree
1.3.6.1.2.1.xx  entityStateMIB  [ENTITY-STATE-MIB]: module-identity
1.3.6.1.2.1.xx.0  entStateNotifications  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.0.1  entStateOperEnabled  [ENTITY-STATE-MIB]: notification-type
1.3.6.1.2.1.xx.0.2  entStateOperDisabled  [ENTITY-STATE-MIB]: notification-type
1.3.6.1.2.1.xx.1  entStateObjects  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.1.1  entStateTable  [ENTITY-STATE-MIB]: table-object-type
1.3.6.1.2.1.xx.1.1.1  entStateEntry  [ENTITY-STATE-MIB]: row-object-type
1.3.6.1.2.1.xx.1.1.1.1  entStateLastChanged  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.2  entStateAdmin  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.3  entStateOper  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.4  entStateUsage  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.5  entStateAlarm  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.1.1.1.6  entStateStandby  [ENTITY-STATE-MIB]: columnar-object-type
1.3.6.1.2.1.xx.3  entStateConformance  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.1  entStateCompliances  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.1.1  entStateCompliance  [ENTITY-STATE-MIB]: module-compliance
1.3.6.1.2.1.xx.3.2  entStateGroups  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.2.1  entStateGroup  [ENTITY-STATE-MIB]: object-group
1.3.6.1.2.1.xx.3.2.2  entStateNotificationsGroup  [ENTITY-STATE-MIB]: notification-group
**end of oid tree**

And so 1.3.6.1.2.1.xx.2 was skipped (for as far as we can tell no good reason).



Bert

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



From entmib-admin@ietf.org  Tue Mar 23 12:26:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13450
	for <entmib-archive@lists.ietf.org>; Tue, 23 Mar 2004 12:26:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5pfE-0004mx-B9; Tue, 23 Mar 2004 12:26:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5peW-0004Y5-FH
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 12:25:24 -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 MAA13421
	for <entmib@ietf.org>; Tue, 23 Mar 2004 12:25:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5peU-000317-00
	for entmib@ietf.org; Tue, 23 Mar 2004 12:25:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5pdS-0002zS-00
	for entmib@ietf.org; Tue, 23 Mar 2004 12:24:18 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5pcT-0002vd-00
	for entmib@ietf.org; Tue, 23 Mar 2004 12:23:17 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2NHMdF21176
	for <entmib@ietf.org>; Tue, 23 Mar 2004 12:22:39 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6JALN>; Tue, 23 Mar 2004 12:22:39 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9677EB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 12:22:28 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Comments inline

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Tuesday, March 23, 2004 10:13 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues

<clip>

It seems to me that your TCs shoudl be prefixed with something aka

   ItuXxxx
   
or
   UtuX731Xxxx

That is what they claim to represent.
And having said that... should it be a separate ITU module (i.e. have ITU
in the name and TC-MIB as a suffix) ??
Maybe to heavy ?

Sharon> Except we have made a couple of modifications to the states. I think
we would have to undo these to call them OSI or ITU states.

> #325:
> 
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> 
> Sharon> This is from the MIB Review Guidelines. 
> 
I think Juergen meant to say that you are using xxxConformance(3)
while you should be using xxxConformance(2).

Your OIDs look like:
OID tree
1.3.6.1.2.1.xx  entityStateMIB  [ENTITY-STATE-MIB]: module-identity
1.3.6.1.2.1.xx.0  entStateNotifications  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.0.1  entStateOperEnabled  [ENTITY-STATE-MIB]:
notification-type
1.3.6.1.2.1.xx.0.2  entStateOperDisabled  [ENTITY-STATE-MIB]:
notification-type
1.3.6.1.2.1.xx.1  entStateObjects  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.1.1  entStateTable  [ENTITY-STATE-MIB]: table-object-type
1.3.6.1.2.1.xx.1.1.1  entStateEntry  [ENTITY-STATE-MIB]: row-object-type
1.3.6.1.2.1.xx.1.1.1.1  entStateLastChanged  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.2  entStateAdmin  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.3  entStateOper  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.4  entStateUsage  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.5  entStateAlarm  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.6  entStateStandby  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.3  entStateConformance  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.3.1  entStateCompliances  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.3.1.1  entStateCompliance  [ENTITY-STATE-MIB]:
module-compliance
1.3.6.1.2.1.xx.3.2  entStateGroups  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.2.1  entStateGroup  [ENTITY-STATE-MIB]: object-group
1.3.6.1.2.1.xx.3.2.2  entStateNotificationsGroup  [ENTITY-STATE-MIB]:
notification-group
**end of oid tree**

And so 1.3.6.1.2.1.xx.2 was skipped (for as far as we can tell no good
reason).

Sharon> This sounds like a different problem then what he is saying.

Sharon

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


From exim@www1.ietf.org  Tue Mar 23 12:26:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13452
	for <entmib-archive@odin.ietf.org>; Tue, 23 Mar 2004 12:26:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5pfI-0004na-Sr
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 12:26:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NHQCGG018433
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 12:26:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5pfE-0004mx-B9; Tue, 23 Mar 2004 12:26:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5peW-0004Y5-FH
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 12:25:24 -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 MAA13421
	for <entmib@ietf.org>; Tue, 23 Mar 2004 12:25:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5peU-000317-00
	for entmib@ietf.org; Tue, 23 Mar 2004 12:25:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5pdS-0002zS-00
	for entmib@ietf.org; Tue, 23 Mar 2004 12:24:18 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5pcT-0002vd-00
	for entmib@ietf.org; Tue, 23 Mar 2004 12:23:17 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2NHMdF21176
	for <entmib@ietf.org>; Tue, 23 Mar 2004 12:22:39 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6JALN>; Tue, 23 Mar 2004 12:22:39 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9677EB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues
Date: Tue, 23 Mar 2004 12:22:28 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Comments inline

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Tuesday, March 23, 2004 10:13 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Final Closure on Entity State MIB Issues

<clip>

It seems to me that your TCs shoudl be prefixed with something aka

   ItuXxxx
   
or
   UtuX731Xxxx

That is what they claim to represent.
And having said that... should it be a separate ITU module (i.e. have ITU
in the name and TC-MIB as a suffix) ??
Maybe to heavy ?

Sharon> Except we have made a couple of modifications to the states. I think
we would have to undo these to call them OSI or ITU states.

> #325:
> 
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> 
> Sharon> This is from the MIB Review Guidelines. 
> 
I think Juergen meant to say that you are using xxxConformance(3)
while you should be using xxxConformance(2).

Your OIDs look like:
OID tree
1.3.6.1.2.1.xx  entityStateMIB  [ENTITY-STATE-MIB]: module-identity
1.3.6.1.2.1.xx.0  entStateNotifications  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.0.1  entStateOperEnabled  [ENTITY-STATE-MIB]:
notification-type
1.3.6.1.2.1.xx.0.2  entStateOperDisabled  [ENTITY-STATE-MIB]:
notification-type
1.3.6.1.2.1.xx.1  entStateObjects  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.1.1  entStateTable  [ENTITY-STATE-MIB]: table-object-type
1.3.6.1.2.1.xx.1.1.1  entStateEntry  [ENTITY-STATE-MIB]: row-object-type
1.3.6.1.2.1.xx.1.1.1.1  entStateLastChanged  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.2  entStateAdmin  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.3  entStateOper  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.4  entStateUsage  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.5  entStateAlarm  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.1.1.1.6  entStateStandby  [ENTITY-STATE-MIB]:
columnar-object-type
1.3.6.1.2.1.xx.3  entStateConformance  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.3.1  entStateCompliances  [ENTITY-STATE-MIB]:
oid-value-assignment
1.3.6.1.2.1.xx.3.1.1  entStateCompliance  [ENTITY-STATE-MIB]:
module-compliance
1.3.6.1.2.1.xx.3.2  entStateGroups  [ENTITY-STATE-MIB]: oid-value-assignment
1.3.6.1.2.1.xx.3.2.1  entStateGroup  [ENTITY-STATE-MIB]: object-group
1.3.6.1.2.1.xx.3.2.2  entStateNotificationsGroup  [ENTITY-STATE-MIB]:
notification-group
**end of oid tree**

And so 1.3.6.1.2.1.xx.2 was skipped (for as far as we can tell no good
reason).

Sharon> This sounds like a different problem then what he is saying.

Sharon

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



From entmib-admin@ietf.org  Tue Mar 23 16:56:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05081
	for <entmib-archive@lists.ietf.org>; Tue, 23 Mar 2004 16:56:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tsP-00038F-BF; Tue, 23 Mar 2004 16:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5trg-00031J-OW
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 16:55:16 -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 QAA04943
	for <entmib@ietf.org>; Tue, 23 Mar 2004 16:55:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tre-0007kW-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:55:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5tqY-0007Zc-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:54:06 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tpS-0007HX-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:52:58 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2NLqL504633
	for <entmib@ietf.org>; Tue, 23 Mar 2004 16:52:22 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6JG8J>; Tue, 23 Mar 2004 16:52:22 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A967B52@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Tue, 23 Mar 2004 16:52:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] I thought we were keeping entAliasMappingTable?
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>

hi

I was just looking at the lasted version of the Entity MIB version 3 and I
notice that the entAliasMappingTable is still deprecated. I thought we
agreed to keep this table?  

It's a critical table that ties together the logical interfaces and the
ports. If we deprecate this table we will a leave huge gaping hole in our
information model. I think it is worth holding back advancement until we get
implementation reports if that is what it takes.

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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


From exim@www1.ietf.org  Tue Mar 23 16:56:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05095
	for <entmib-archive@odin.ietf.org>; Tue, 23 Mar 2004 16:56:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tsP-00038m-O8
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 16:56:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NLu1qQ012057
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 16:56:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tsP-00038F-BF; Tue, 23 Mar 2004 16:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5trg-00031J-OW
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 16:55:16 -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 QAA04943
	for <entmib@ietf.org>; Tue, 23 Mar 2004 16:55:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tre-0007kW-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:55:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5tqY-0007Zc-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:54:06 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tpS-0007HX-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:52:58 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2NLqL504633
	for <entmib@ietf.org>; Tue, 23 Mar 2004 16:52:22 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6JG8J>; Tue, 23 Mar 2004 16:52:22 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A967B52@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Tue, 23 Mar 2004 16:52:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] I thought we were keeping entAliasMappingTable?
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>

hi

I was just looking at the lasted version of the Entity MIB version 3 and I
notice that the entAliasMappingTable is still deprecated. I thought we
agreed to keep this table?  

It's a critical table that ties together the logical interfaces and the
ports. If we deprecate this table we will a leave huge gaping hole in our
information model. I think it is worth holding back advancement until we get
implementation reports if that is what it takes.

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



From entmib-admin@ietf.org  Tue Mar 23 16:59:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05486
	for <entmib-archive@lists.ietf.org>; Tue, 23 Mar 2004 16:59:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tvJ-0003Rb-GT; Tue, 23 Mar 2004 16:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tuZ-0003ML-3X
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 16:58:15 -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 QAA05321
	for <entmib@ietf.org>; Tue, 23 Mar 2004 16:58:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tuW-0000Sp-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:58:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ttM-0000Gy-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:57:01 -0500
Received: from g43dd.g.pppool.de ([80.185.67.221] helo=james.eecs.iu-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tsT-00006e-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:56:05 -0500
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id D411F8531; Tue, 23 Mar 2004 15:53:37 +0100 (CET)
Date: Tue, 23 Mar 2004 15:53:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] Final Closure on Entity State MIB Issues
Message-ID: <20040323145337.GC1131@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A967516@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A967516@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	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>

On Tue, Mar 23, 2004 at 09:27:26AM -0500, Sharon Chisholm wrote:
> Comments inline...
> 
> #311: DateAndTimeOrZero ?
> 
> 	The new text refers to the initialization of "the local
> 	system" - whatever that may be. In a subagent environment, the
> 	actual instrumentation might not have easy access to what an
> 	operator would consider "the local system". So I think it
> 	would be better to adopt the approach where a the special
> 	value '0000000000000000'H is returned. Sure, this value falls
> 	not strictly under the DateAndTime TC set of values, but we
> 	have several MIBs using this special value on the standards
> 	track so this should work here as well.
> 
> Sharon> I like this simpler approach. I had been half way down the path of
> defining new TCs to behave like this when I looked up how we did it in the
> Alarm MIB. Would answering the question of what the 'local system' is or
> using a better term help?

I think it is not a terminology issue. Consider a hot-swappable line
card which has its own subagent. It can easily report
'0000000000000000'H but making it report the date and time of the
initialization of the "local system" is either very hard (if local
system means the system runnning the master agent) or you just report
the time when the card was inserted, which is kind of meaningless for
the manager. So I think the only workable solution is really to report
the special value '0000000000000000'H since it avoids any ambiguities
and is very easy to implement.
 
> <clip>
> 
> #322: Textual Convention Names (Prefix)
> 
> 	I think the TC names should be prefixed.
> 
> Sharon> Ok. I think we need to step back a level on this one. We seemed to
> have had agreement on the list that if the TCs were intended to be not
> specific to Entities, then they should not have the prefix but if they were
> they should. So, I suspect we are disagreeing on whether these TCs are
> specific to Entities. I certainly never intended them to be and went out of
> my way to ensure they weren't. Is there something in their definition that
> leads you to believe they are limited in their application to Entities?

As others have noted before: If these TCs are really generic, put them 
into a separate MIB module and perhaps even document so that these 
definitions also get wider review (and actual users). If I were writing
a MIB on a standards track, I would think more than twice whether I
import these TCs for a module which itself depends on other modules
which I really do not want to depend on. Generic TCs really should go
into self contained modules.

To complete this piece of work on the charter, I do not think that we
have to produce generic TCs for operational and usage state.
 
> #325:
> 
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> 
> Sharon> This is from the MIB Review Guidelines. 

My copy of <draft-ietf-ops-mib-review-guidelines-02.txt> clearly
has the following.
 
         xxxMIB
         |
         +-- xxxNotifications(0)
         +-- xxxObjects(1)
         +-- xxxConformance(2)
             |
             +-- xxxCompliances(1)
             +-- xxxGroups(2)

And since I contributed this figure to the ID, I am almost sure my 
copy of <draft-ietf-ops-mib-review-guidelines-02.txt> is correct...

> #328: Containment Hierach and entPhysicalContainedin
> 
> 	I think this issue is not really solved. It must be clear in
> 	all cases where a description clause talks about containment
> 	what this really means.
> 
> Sharon> Embedded? Perhaps.

??? Not sure I understand this.
 
> #334: Table, Index Descriptions
> 
> 	I am having problems with the suggested new text. In
> 	particular the following sentence:
> 
> 	Entries appear in this table for values of entPhysicalClass
>         [RFC2737] that in this implementation are able to report any
>         of the state or status stored in this table.
> 
> 	I think that the class is not necessarily the property which
> 	defines whether a component will be able to report useful
> 	information in a subagent environment. I think this sentence
> 	hurts more than it helps. BTW, the most obvious reason for
> 	sparse augmentations is that new hardware and software will in
> 	practice be mixed with old hardware and software in subagent
> 	environments. (Not sure we need to document this. I think it
> 	is sufficient to say it is a sparse augmentation.)
> 
> Sharon>I have had a lot of trouble with this text since I actually don't
> think this table should be sparse augment. I was just going with a working
> group consensus we agreed to a long time ago. Your reasons makes more sense.
> I'll try to rework the text.

I think the relationship has to be sparse and I do not think we need to 
write lengthy explanations about this.

/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


From exim@www1.ietf.org  Tue Mar 23 16:59:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05496
	for <entmib-archive@odin.ietf.org>; Tue, 23 Mar 2004 16:59:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tvJ-0003Rs-JS
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 16:59:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NLx1Vo013249
	for entmib-archive@odin.ietf.org; Tue, 23 Mar 2004 16:59:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tvJ-0003Rb-GT; Tue, 23 Mar 2004 16:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5tuZ-0003ML-3X
	for entmib@optimus.ietf.org; Tue, 23 Mar 2004 16:58:15 -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 QAA05321
	for <entmib@ietf.org>; Tue, 23 Mar 2004 16:58:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tuW-0000Sp-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:58:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ttM-0000Gy-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:57:01 -0500
Received: from g43dd.g.pppool.de ([80.185.67.221] helo=james.eecs.iu-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5tsT-00006e-00
	for entmib@ietf.org; Tue, 23 Mar 2004 16:56:05 -0500
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id D411F8531; Tue, 23 Mar 2004 15:53:37 +0100 (CET)
Date: Tue, 23 Mar 2004 15:53:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] Final Closure on Entity State MIB Issues
Message-ID: <20040323145337.GC1131@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A967516@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A967516@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,DATE_IN_PAST_06_12 
	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>

On Tue, Mar 23, 2004 at 09:27:26AM -0500, Sharon Chisholm wrote:
> Comments inline...
> 
> #311: DateAndTimeOrZero ?
> 
> 	The new text refers to the initialization of "the local
> 	system" - whatever that may be. In a subagent environment, the
> 	actual instrumentation might not have easy access to what an
> 	operator would consider "the local system". So I think it
> 	would be better to adopt the approach where a the special
> 	value '0000000000000000'H is returned. Sure, this value falls
> 	not strictly under the DateAndTime TC set of values, but we
> 	have several MIBs using this special value on the standards
> 	track so this should work here as well.
> 
> Sharon> I like this simpler approach. I had been half way down the path of
> defining new TCs to behave like this when I looked up how we did it in the
> Alarm MIB. Would answering the question of what the 'local system' is or
> using a better term help?

I think it is not a terminology issue. Consider a hot-swappable line
card which has its own subagent. It can easily report
'0000000000000000'H but making it report the date and time of the
initialization of the "local system" is either very hard (if local
system means the system runnning the master agent) or you just report
the time when the card was inserted, which is kind of meaningless for
the manager. So I think the only workable solution is really to report
the special value '0000000000000000'H since it avoids any ambiguities
and is very easy to implement.
 
> <clip>
> 
> #322: Textual Convention Names (Prefix)
> 
> 	I think the TC names should be prefixed.
> 
> Sharon> Ok. I think we need to step back a level on this one. We seemed to
> have had agreement on the list that if the TCs were intended to be not
> specific to Entities, then they should not have the prefix but if they were
> they should. So, I suspect we are disagreeing on whether these TCs are
> specific to Entities. I certainly never intended them to be and went out of
> my way to ensure they weren't. Is there something in their definition that
> leads you to believe they are limited in their application to Entities?

As others have noted before: If these TCs are really generic, put them 
into a separate MIB module and perhaps even document so that these 
definitions also get wider review (and actual users). If I were writing
a MIB on a standards track, I would think more than twice whether I
import these TCs for a module which itself depends on other modules
which I really do not want to depend on. Generic TCs really should go
into self contained modules.

To complete this piece of work on the charter, I do not think that we
have to produce generic TCs for operational and usage state.
 
> #325:
> 
> 	The figures in the discussion of this issue are wrong as
> 	xxxCompliances(1) and xxxGroups(2) are typically registered
> 	below xxxConformance(2).
> 
> Sharon> This is from the MIB Review Guidelines. 

My copy of <draft-ietf-ops-mib-review-guidelines-02.txt> clearly
has the following.
 
         xxxMIB
         |
         +-- xxxNotifications(0)
         +-- xxxObjects(1)
         +-- xxxConformance(2)
             |
             +-- xxxCompliances(1)
             +-- xxxGroups(2)

And since I contributed this figure to the ID, I am almost sure my 
copy of <draft-ietf-ops-mib-review-guidelines-02.txt> is correct...

> #328: Containment Hierach and entPhysicalContainedin
> 
> 	I think this issue is not really solved. It must be clear in
> 	all cases where a description clause talks about containment
> 	what this really means.
> 
> Sharon> Embedded? Perhaps.

??? Not sure I understand this.
 
> #334: Table, Index Descriptions
> 
> 	I am having problems with the suggested new text. In
> 	particular the following sentence:
> 
> 	Entries appear in this table for values of entPhysicalClass
>         [RFC2737] that in this implementation are able to report any
>         of the state or status stored in this table.
> 
> 	I think that the class is not necessarily the property which
> 	defines whether a component will be able to report useful
> 	information in a subagent environment. I think this sentence
> 	hurts more than it helps. BTW, the most obvious reason for
> 	sparse augmentations is that new hardware and software will in
> 	practice be mixed with old hardware and software in subagent
> 	environments. (Not sure we need to document this. I think it
> 	is sufficient to say it is a sparse augmentation.)
> 
> Sharon>I have had a lot of trouble with this text since I actually don't
> think this table should be sparse augment. I was just going with a working
> group consensus we agreed to a long time ago. Your reasons makes more sense.
> I'll try to rework the text.

I think the relationship has to be sparse and I do not think we need to 
write lengthy explanations about this.

/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



From entmib-admin@ietf.org  Wed Mar 24 09:09:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22822
	for <entmib-archive@lists.ietf.org>; Wed, 24 Mar 2004 09:09:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6940-0006gK-GB; Wed, 24 Mar 2004 09:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B693l-0006fq-0p
	for entmib@optimus.ietf.org; Wed, 24 Mar 2004 09:08:45 -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 JAA22793
	for <entmib@ietf.org>; Wed, 24 Mar 2004 09:08:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B693j-0001oj-00
	for entmib@ietf.org; Wed, 24 Mar 2004 09:08:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B692X-0001Z8-00
	for entmib@ietf.org; Wed, 24 Mar 2004 09:07:30 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B691y-0001H6-00
	for entmib@ietf.org; Wed, 24 Mar 2004 09:06:54 -0500
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i2OE6KBB014530;
	Wed, 24 Mar 2004 06:06:21 -0800 (PST)
Received: from ABIERMAN-W2K.cisco.com (sjc-vpn2-669.cisco.com [10.21.114.157])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ASG06125;
	Wed, 24 Mar 2004 06:06:20 -0800 (PST)
Message-Id: <6.0.3.0.2.20040324055842.0360e260@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Wed, 24 Mar 2004 06:02:38 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] I thought we were keeping entAliasMappingTable?
Cc: entmib@ietf.org
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A967B52@zcard0ka.ca.norte
 l.com>
References: <3549C09B853DD5119B540002A52CDD340A967B52@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

At 01:52 PM 3/23/2004, Sharon Chisholm wrote:
>hi
>
>I was just looking at the lasted version of the Entity MIB version 3 and I
>notice that the entAliasMappingTable is still deprecated. I thought we
>agreed to keep this table?  
>
>It's a critical table that ties together the logical interfaces and the
>ports. If we deprecate this table we will a leave huge gaping hole in our
>information model. I think it is worth holding back advancement until we get
>implementation reports if that is what it takes.

Then where are the implementations if this is so critical?
I think Cisco was the only vendor to submit an implementation
report for this table, and it's only in a few of our products.


>Sharon Chisholm
>Portfolio Integration
>Nortel Networks
>Ottawa, Canada

Andy


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


From exim@www1.ietf.org  Wed Mar 24 09:09:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22824
	for <entmib-archive@odin.ietf.org>; Wed, 24 Mar 2004 09:09:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6940-0006gl-St
	for entmib-archive@odin.ietf.org; Wed, 24 Mar 2004 09:09:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OE90Js025698
	for entmib-archive@odin.ietf.org; Wed, 24 Mar 2004 09:09:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6940-0006gK-GB; Wed, 24 Mar 2004 09:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B693l-0006fq-0p
	for entmib@optimus.ietf.org; Wed, 24 Mar 2004 09:08:45 -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 JAA22793
	for <entmib@ietf.org>; Wed, 24 Mar 2004 09:08:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B693j-0001oj-00
	for entmib@ietf.org; Wed, 24 Mar 2004 09:08:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B692X-0001Z8-00
	for entmib@ietf.org; Wed, 24 Mar 2004 09:07:30 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B691y-0001H6-00
	for entmib@ietf.org; Wed, 24 Mar 2004 09:06:54 -0500
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com [171.71.163.17])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i2OE6KBB014530;
	Wed, 24 Mar 2004 06:06:21 -0800 (PST)
Received: from ABIERMAN-W2K.cisco.com (sjc-vpn2-669.cisco.com [10.21.114.157])
	by mira-sjc5-c.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id ASG06125;
	Wed, 24 Mar 2004 06:06:20 -0800 (PST)
Message-Id: <6.0.3.0.2.20040324055842.0360e260@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Wed, 24 Mar 2004 06:02:38 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] I thought we were keeping entAliasMappingTable?
Cc: entmib@ietf.org
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A967B52@zcard0ka.ca.norte
 l.com>
References: <3549C09B853DD5119B540002A52CDD340A967B52@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

At 01:52 PM 3/23/2004, Sharon Chisholm wrote:
>hi
>
>I was just looking at the lasted version of the Entity MIB version 3 and I
>notice that the entAliasMappingTable is still deprecated. I thought we
>agreed to keep this table?  
>
>It's a critical table that ties together the logical interfaces and the
>ports. If we deprecate this table we will a leave huge gaping hole in our
>information model. I think it is worth holding back advancement until we get
>implementation reports if that is what it takes.

Then where are the implementations if this is so critical?
I think Cisco was the only vendor to submit an implementation
report for this table, and it's only in a few of our products.


>Sharon Chisholm
>Portfolio Integration
>Nortel Networks
>Ottawa, Canada

Andy


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



From entmib-admin@ietf.org  Wed Mar 24 16:23:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22136
	for <entmib-archive@lists.ietf.org>; Wed, 24 Mar 2004 16:23:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fq1-0000Hi-5U; Wed, 24 Mar 2004 16:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FpW-0000GE-CP
	for entmib@optimus.ietf.org; Wed, 24 Mar 2004 16:22:30 -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 QAA22056
	for <entmib@ietf.org>; Wed, 24 Mar 2004 16:22:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FpU-0002BM-00
	for entmib@ietf.org; Wed, 24 Mar 2004 16:22:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Foe-00026S-00
	for entmib@ietf.org; Wed, 24 Mar 2004 16:21:36 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Fnk-0001vy-00
	for entmib@ietf.org; Wed, 24 Mar 2004 16:20:40 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2OLK4613797
	for <entmib@ietf.org>; Wed, 24 Mar 2004 16:20:04 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6JYCY>; Wed, 24 Mar 2004 16:20:04 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2B46@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] I thought we were keeping entAliasMappingTable?
Date: Wed, 24 Mar 2004 16:19:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Well, I suspect there are many implementations in the pipe. I'm aware of a
couple. We had previously discussed one that people thought might be soon
available. It would be good to ping that person to see if it is now
available.  

I'll look around to see if I can find something completed.

I know we've been waiting for a while for implementation, so if you've lost
patience, I'd certainly understand. Alternatively, we could look at
publishing the ID without progressing it.

Sharon

-----Original Message-----
From: Andy Bierman [mailto:abierman@cisco.com] 
Sent: Wednesday, March 24, 2004 9:03 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] I thought we were keeping entAliasMappingTable?


At 01:52 PM 3/23/2004, Sharon Chisholm wrote:
>hi
>
>I was just looking at the lasted version of the Entity MIB version 3 
>and I notice that the entAliasMappingTable is still deprecated. I 
>thought we agreed to keep this table?
>
>It's a critical table that ties together the logical interfaces and the 
>ports. If we deprecate this table we will a leave huge gaping hole in 
>our information model. I think it is worth holding back advancement 
>until we get implementation reports if that is what it takes.

Then where are the implementations if this is so critical?
I think Cisco was the only vendor to submit an implementation report for
this table, and it's only in a few of our products.


>Sharon Chisholm
>Portfolio Integration
>Nortel Networks
>Ottawa, Canada

Andy


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


From exim@www1.ietf.org  Wed Mar 24 17:08:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22139
	for <entmib-archive@odin.ietf.org>; Wed, 24 Mar 2004 16:23:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fq1-0000I7-AZ
	for entmib-archive@odin.ietf.org; Wed, 24 Mar 2004 16:23:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OLN1Za001107
	for entmib-archive@odin.ietf.org; Wed, 24 Mar 2004 16:23:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fq1-0000Hi-5U; Wed, 24 Mar 2004 16:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FpW-0000GE-CP
	for entmib@optimus.ietf.org; Wed, 24 Mar 2004 16:22:30 -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 QAA22056
	for <entmib@ietf.org>; Wed, 24 Mar 2004 16:22:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FpU-0002BM-00
	for entmib@ietf.org; Wed, 24 Mar 2004 16:22:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Foe-00026S-00
	for entmib@ietf.org; Wed, 24 Mar 2004 16:21:36 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Fnk-0001vy-00
	for entmib@ietf.org; Wed, 24 Mar 2004 16:20:40 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2OLK4613797
	for <entmib@ietf.org>; Wed, 24 Mar 2004 16:20:04 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6JYCY>; Wed, 24 Mar 2004 16:20:04 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2B46@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] I thought we were keeping entAliasMappingTable?
Date: Wed, 24 Mar 2004 16:19:57 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Well, I suspect there are many implementations in the pipe. I'm aware of a
couple. We had previously discussed one that people thought might be soon
available. It would be good to ping that person to see if it is now
available.  

I'll look around to see if I can find something completed.

I know we've been waiting for a while for implementation, so if you've lost
patience, I'd certainly understand. Alternatively, we could look at
publishing the ID without progressing it.

Sharon

-----Original Message-----
From: Andy Bierman [mailto:abierman@cisco.com] 
Sent: Wednesday, March 24, 2004 9:03 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] I thought we were keeping entAliasMappingTable?


At 01:52 PM 3/23/2004, Sharon Chisholm wrote:
>hi
>
>I was just looking at the lasted version of the Entity MIB version 3 
>and I notice that the entAliasMappingTable is still deprecated. I 
>thought we agreed to keep this table?
>
>It's a critical table that ties together the logical interfaces and the 
>ports. If we deprecate this table we will a leave huge gaping hole in 
>our information model. I think it is worth holding back advancement 
>until we get implementation reports if that is what it takes.

Then where are the implementations if this is so critical?
I think Cisco was the only vendor to submit an implementation report for
this table, and it's only in a few of our products.


>Sharon Chisholm
>Portfolio Integration
>Nortel Networks
>Ottawa, Canada

Andy


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



From entmib-admin@ietf.org  Thu Mar 25 02:01:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21658
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 02:01:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6OrM-0001jD-Gh; Thu, 25 Mar 2004 02:01:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6OrF-0001g8-Hs
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 02:00:53 -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 CAA20966
	for <entmib@ietf.org>; Thu, 25 Mar 2004 02:00:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6OrB-0001lq-00
	for entmib@ietf.org; Thu, 25 Mar 2004 02:00:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6OqK-0001gQ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 01:59:57 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6OpY-0001bJ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 01:59:09 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2P6x3b00674
	for <entmib@ietf.org>; Wed, 24 Mar 2004 22:59:03 -0800
Message-Id: <5.2.0.9.2.20040324145446.02343138@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 24 Mar 2004 22:58:57 -0800
To: entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_3 autolearn=no 
	version=2.60
Subject: [Entmib] Entity comments
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>

HI,

In general, it has seemed to me that in the beginning and at the last few
ENITITY MIB WG meetings that the consensus desire was to have a simple
extension to the entity physical table with the following:
  adminState - to indicate the administrative state of a physical
               component, and allow change
  operState - to indicate the operational state of a physical component
  backupState - to indicate if a physical component was backing up
                  another physical component
  alarmStatus - to indicate current fault conditions (if any) were
                  present on a physical component
A small minority wanted to base the definitions on X.731 definitions.
However, the majority felt that was OK only if the above needs were not
impacted, and the cost to support the objects on an agent was not
significantly impacted.

To me, the resulting definitions have not met the rough consensus
needs. In addition, the document (and its yet to be sent out
update) is not internally consistent.

The entity state document is quite small, and I can provide a complete replacement, if the WG wants one. However, to follow the process, here
are responses to the outstanding issues. I believe that these might
be difficult to evaluate due to the missing context. But here it goes...

#306 & #325: descriptor naming and OID tree
  Please, lets follow current standard layout as determined by Bert

#307: not-supported is wrong
  I agree with Keith and Juergen. Either "unknown" or "unavailable"
  is fine with me.
  However, what is a BIG problem is the text in the DESCRIPTION
  clauses using the term "unreportable". This is wrong. That is,
  the term "unreportable" MUST be removed from the DESCRIPTION
  clauses and a semantically correct term must be used.

#308 & 312: admin state enum values
  I agree with Keith and Juergen.  Also, a radical approach is
  to remove the object altogether. However, if the object is kept,
  then I suggest the following enum values:
    up - action(to set to up) and state(is administratively up)
    down - action(to force set to down) and state(is administratively down)
    gracedown - action(to gracefully set to down)
    shuttingdown - state(in process of gracefully shutting down)
    testing - state(in test mode. requires other specific means to
                  put in a test mode)
  (and if it's not obvious, then I can provide a state diagram, like
   that found for RowStatus TC)

#309 & #332: Oper State enum names
  I agree with Keith. I also have problems with the values being
  semantically different from ifOperStatus. And, to really simplify,
  I suggest that the standby status object be removed, and it's
  values be combined. The resulting enum values would be:
    unknown - state unknown
    up - working OK
    down - not working (a failure)
    downDueToAdmin - not working since turned off and cannot tell if
                          could work if administratively turned on
    downDueToContained - not working due to contained component
    testing - in a test mode
    coldStandby - backing up a component, and may be able to provide
                      service after some initialization activity
    hotStandby - backing up a component, and will be able to immediately
                      provide service without need for initialization 
  NOTE: in X.731, the value of operState is independent of the value
    of adminState. However, for many real-world physical devices,
    one cannot determine the operState without "turning on" the
    component. So the above is a compromise. That is, if a component
    operState follows adminState (like as done by ifOperStatus),
    then value 'downDueToAdmin' would be used (when appropriate).
    And if independent, then 'down' would be used (when appropriate).  

#310: Alarm Status values
  The resolution must include a value when the operState value is
  'testing'. The resulting BITs should be something like:
      unknown - status unknown (if set, then no other bits may be set)
      underRepair - item under repair
      underTest - item being tested
      critial - one or more critical fault conditions present
      major - one or more major fault conditions present
      minor - one or more minor fault conditions present
      warning - one or more warning fault conditions present
      indeterminate - one or more indeterminate fault conditions present   
  Note: when 'underRepair' or 'underTest' BITs are set, then
      the manager should probably "discount" the importance
      of any outstanding fault conditions

#311 - Initial DateTime value
   I agree with Keith and Juergen.

#312: (see #308 above)

#322: TC Names
   I agree with Andy and Juergen. And believe that the prefix
   should be EntPhys (that is not just Entity)!

#325: (see #306 above)

#326: Too many objects
  I agree with andy.
  The Usage object provides no additional info (that is, its value
  can be determined by looking at other objects in the EntPhysical table),
  and should be removed. The standby object can be deleted, and its
  values folded into oper State.

#327: Editorial edits
  I agree with Juergen that the document needs language fixes.
  In addition to what he points out, I believe the following
  modifications are needed:
    a) The term "report" must be replaced with an appropriate
       one through out the document
    b) X.731 needs to be removed from the REFERENCE clauses,
       and X.731 needs to be changed from a normative reference
       to an informative reference
    c) X.721 and X.732 need to be added as informative references
    d) the alarm MIB needs to be changed from an normative reference
       to an informative reference

#328: Definition of "contained in"
  I agree with Juergen that this needs to be well defined.
  And I previously specified a definition that I believe
  is sufficient.

#329: Problems with usage state
  Remove the object. See #326 above.

#330: Notification varbinds
  This needs review and update after update of enum values for
  operState. 

#332: Standby State issues
  See #326 and #309 above.

#333: Relationship with alarm MIB
  The reported problem was not address. Said another way,
  the Entity State MIB SHOULD NOT depend on the support of
  the Alarm MIB. And the Alarm MIB RFC should be an informative
  and NOT a normative reference.

#334: Table index Description
  The SMI (RFC 2578, last para of section 7.7) requires a description
  of the index. Also, I would add text explaining that typically
  instances with physical class of chassis, backplane, container
  and stack do not have status instances, where typically instances
  powerSupply, fan, sensor, module, and port do have status instances.
  However, they may not support modification of admin state.

#335a: Clarification of notification generation
  The resolution didn't add clarity. That is, can multiple
  notifications be generated for a single event. (I think so,
  but I'm not sure that other reviewers noticed this.)

#335b: Need for notification on change of Standby state
  From my previous experience, each protection switch was an
  important event and thus a notification is appropriate.

Regards,
/david t. perkins
 


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


From exim@www1.ietf.org  Thu Mar 25 02:01:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21663
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 02:01:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6OrM-0001jl-TY
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 02:01:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2P710l8006663
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 02:01:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6OrM-0001jD-Gh; Thu, 25 Mar 2004 02:01:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6OrF-0001g8-Hs
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 02:00:53 -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 CAA20966
	for <entmib@ietf.org>; Thu, 25 Mar 2004 02:00:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6OrB-0001lq-00
	for entmib@ietf.org; Thu, 25 Mar 2004 02:00:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6OqK-0001gQ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 01:59:57 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6OpY-0001bJ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 01:59:09 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2P6x3b00674
	for <entmib@ietf.org>; Wed, 24 Mar 2004 22:59:03 -0800
Message-Id: <5.2.0.9.2.20040324145446.02343138@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 24 Mar 2004 22:58:57 -0800
To: entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,EXCUSE_3 autolearn=no 
	version=2.60
Subject: [Entmib] Entity comments
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>

HI,

In general, it has seemed to me that in the beginning and at the last few
ENITITY MIB WG meetings that the consensus desire was to have a simple
extension to the entity physical table with the following:
  adminState - to indicate the administrative state of a physical
               component, and allow change
  operState - to indicate the operational state of a physical component
  backupState - to indicate if a physical component was backing up
                  another physical component
  alarmStatus - to indicate current fault conditions (if any) were
                  present on a physical component
A small minority wanted to base the definitions on X.731 definitions.
However, the majority felt that was OK only if the above needs were not
impacted, and the cost to support the objects on an agent was not
significantly impacted.

To me, the resulting definitions have not met the rough consensus
needs. In addition, the document (and its yet to be sent out
update) is not internally consistent.

The entity state document is quite small, and I can provide a complete replacement, if the WG wants one. However, to follow the process, here
are responses to the outstanding issues. I believe that these might
be difficult to evaluate due to the missing context. But here it goes...

#306 & #325: descriptor naming and OID tree
  Please, lets follow current standard layout as determined by Bert

#307: not-supported is wrong
  I agree with Keith and Juergen. Either "unknown" or "unavailable"
  is fine with me.
  However, what is a BIG problem is the text in the DESCRIPTION
  clauses using the term "unreportable". This is wrong. That is,
  the term "unreportable" MUST be removed from the DESCRIPTION
  clauses and a semantically correct term must be used.

#308 & 312: admin state enum values
  I agree with Keith and Juergen.  Also, a radical approach is
  to remove the object altogether. However, if the object is kept,
  then I suggest the following enum values:
    up - action(to set to up) and state(is administratively up)
    down - action(to force set to down) and state(is administratively down)
    gracedown - action(to gracefully set to down)
    shuttingdown - state(in process of gracefully shutting down)
    testing - state(in test mode. requires other specific means to
                  put in a test mode)
  (and if it's not obvious, then I can provide a state diagram, like
   that found for RowStatus TC)

#309 & #332: Oper State enum names
  I agree with Keith. I also have problems with the values being
  semantically different from ifOperStatus. And, to really simplify,
  I suggest that the standby status object be removed, and it's
  values be combined. The resulting enum values would be:
    unknown - state unknown
    up - working OK
    down - not working (a failure)
    downDueToAdmin - not working since turned off and cannot tell if
                          could work if administratively turned on
    downDueToContained - not working due to contained component
    testing - in a test mode
    coldStandby - backing up a component, and may be able to provide
                      service after some initialization activity
    hotStandby - backing up a component, and will be able to immediately
                      provide service without need for initialization 
  NOTE: in X.731, the value of operState is independent of the value
    of adminState. However, for many real-world physical devices,
    one cannot determine the operState without "turning on" the
    component. So the above is a compromise. That is, if a component
    operState follows adminState (like as done by ifOperStatus),
    then value 'downDueToAdmin' would be used (when appropriate).
    And if independent, then 'down' would be used (when appropriate).  

#310: Alarm Status values
  The resolution must include a value when the operState value is
  'testing'. The resulting BITs should be something like:
      unknown - status unknown (if set, then no other bits may be set)
      underRepair - item under repair
      underTest - item being tested
      critial - one or more critical fault conditions present
      major - one or more major fault conditions present
      minor - one or more minor fault conditions present
      warning - one or more warning fault conditions present
      indeterminate - one or more indeterminate fault conditions present   
  Note: when 'underRepair' or 'underTest' BITs are set, then
      the manager should probably "discount" the importance
      of any outstanding fault conditions

#311 - Initial DateTime value
   I agree with Keith and Juergen.

#312: (see #308 above)

#322: TC Names
   I agree with Andy and Juergen. And believe that the prefix
   should be EntPhys (that is not just Entity)!

#325: (see #306 above)

#326: Too many objects
  I agree with andy.
  The Usage object provides no additional info (that is, its value
  can be determined by looking at other objects in the EntPhysical table),
  and should be removed. The standby object can be deleted, and its
  values folded into oper State.

#327: Editorial edits
  I agree with Juergen that the document needs language fixes.
  In addition to what he points out, I believe the following
  modifications are needed:
    a) The term "report" must be replaced with an appropriate
       one through out the document
    b) X.731 needs to be removed from the REFERENCE clauses,
       and X.731 needs to be changed from a normative reference
       to an informative reference
    c) X.721 and X.732 need to be added as informative references
    d) the alarm MIB needs to be changed from an normative reference
       to an informative reference

#328: Definition of "contained in"
  I agree with Juergen that this needs to be well defined.
  And I previously specified a definition that I believe
  is sufficient.

#329: Problems with usage state
  Remove the object. See #326 above.

#330: Notification varbinds
  This needs review and update after update of enum values for
  operState. 

#332: Standby State issues
  See #326 and #309 above.

#333: Relationship with alarm MIB
  The reported problem was not address. Said another way,
  the Entity State MIB SHOULD NOT depend on the support of
  the Alarm MIB. And the Alarm MIB RFC should be an informative
  and NOT a normative reference.

#334: Table index Description
  The SMI (RFC 2578, last para of section 7.7) requires a description
  of the index. Also, I would add text explaining that typically
  instances with physical class of chassis, backplane, container
  and stack do not have status instances, where typically instances
  powerSupply, fan, sensor, module, and port do have status instances.
  However, they may not support modification of admin state.

#335a: Clarification of notification generation
  The resolution didn't add clarity. That is, can multiple
  notifications be generated for a single event. (I think so,
  but I'm not sure that other reviewers noticed this.)

#335b: Need for notification on change of Standby state
  From my previous experience, each protection switch was an
  important event and thus a notification is appropriate.

Regards,
/david t. perkins
 


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



From entmib-admin@ietf.org  Thu Mar 25 09:40:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25142
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 09:40:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6W1r-0005rc-2H; Thu, 25 Mar 2004 09:40:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6W1L-0005m5-Ne
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 09:39:47 -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 JAA25014
	for <entmib@ietf.org>; Thu, 25 Mar 2004 09:39:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6W1F-0002RQ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 09:39:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6W0E-0002Fy-00
	for entmib@ietf.org; Thu, 25 Mar 2004 09:38:39 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Vy4-0001h7-00
	for entmib@ietf.org; Thu, 25 Mar 2004 09:36:24 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PEZqR09088
	for <entmib@ietf.org>; Thu, 25 Mar 2004 09:35:52 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6J0B7>; Thu, 25 Mar 2004 09:35:53 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2E92@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Entity comments
Date: Thu, 25 Mar 2004 09:35:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Ok, I this isn't really response to Dave's email so much as leveraging his
summary of events to step back and have a high-level discussion which
affects a number of issues.  

I think I'll open a new issue to track this. I think if we get consensus on
this, a number of other issues fall out of that.

<Dave>

In general, it has seemed to me that in the beginning and at the last few
ENITITY MIB WG meetings that the consensus desire was to have a simple
extension to the entity physical table with the following:
  adminState - to indicate the administrative state of a physical
               component, and allow change
  operState - to indicate the operational state of a physical component
  backupState - to indicate if a physical component was backing up
                  another physical component
  alarmStatus - to indicate current fault conditions (if any) were
                  present on a physical component
A small minority wanted to base the definitions on X.731 definitions.
However, the majority felt that was OK only if the above needs were not
impacted, and the cost to support the objects on an agent was not
significantly impacted.
</Dave>

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.

2. Renaming state values. While I don't really see the value in changing the
name of the state values, if that is consensus, then that it what we should
do. If we do go down this path, we will have to add a section that describes
the mapping from OSI states.

Where do people think we should be?

Sharon

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


From exim@www1.ietf.org  Thu Mar 25 09:40:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25155
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 09:40:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6W1s-0005sc-6Y
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 09:40:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PEeJEC022564
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 09:40:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6W1r-0005rc-2H; Thu, 25 Mar 2004 09:40:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6W1L-0005m5-Ne
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 09:39:47 -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 JAA25014
	for <entmib@ietf.org>; Thu, 25 Mar 2004 09:39:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6W1F-0002RQ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 09:39:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6W0E-0002Fy-00
	for entmib@ietf.org; Thu, 25 Mar 2004 09:38:39 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Vy4-0001h7-00
	for entmib@ietf.org; Thu, 25 Mar 2004 09:36:24 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PEZqR09088
	for <entmib@ietf.org>; Thu, 25 Mar 2004 09:35:52 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6J0B7>; Thu, 25 Mar 2004 09:35:53 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2E92@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Entity comments
Date: Thu, 25 Mar 2004 09:35:52 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Ok, I this isn't really response to Dave's email so much as leveraging his
summary of events to step back and have a high-level discussion which
affects a number of issues.  

I think I'll open a new issue to track this. I think if we get consensus on
this, a number of other issues fall out of that.

<Dave>

In general, it has seemed to me that in the beginning and at the last few
ENITITY MIB WG meetings that the consensus desire was to have a simple
extension to the entity physical table with the following:
  adminState - to indicate the administrative state of a physical
               component, and allow change
  operState - to indicate the operational state of a physical component
  backupState - to indicate if a physical component was backing up
                  another physical component
  alarmStatus - to indicate current fault conditions (if any) were
                  present on a physical component
A small minority wanted to base the definitions on X.731 definitions.
However, the majority felt that was OK only if the above needs were not
impacted, and the cost to support the objects on an agent was not
significantly impacted.
</Dave>

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.

2. Renaming state values. While I don't really see the value in changing the
name of the state values, if that is consensus, then that it what we should
do. If we do go down this path, we will have to add a section that describes
the mapping from OSI states.

Where do people think we should be?

Sharon

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



From entmib-admin@ietf.org  Thu Mar 25 10:44:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01377
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 10:44:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X1f-0001u4-6v; Thu, 25 Mar 2004 10:44:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6WpX-0000RE-Ts
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 10:31:39 -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 KAA00752
	for <entmib@ietf.org>; Thu, 25 Mar 2004 10:31:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6WpV-0000RG-00
	for entmib@ietf.org; Thu, 25 Mar 2004 10:31:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6WoM-0000K2-00
	for entmib@ietf.org; Thu, 25 Mar 2004 10:30:27 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Wnl-0000DJ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 10:29:49 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PFTHV28431
	for <entmib@ietf.org>; Thu, 25 Mar 2004 10:29:17 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KA87>; Thu, 25 Mar 2004 10:29:17 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2F5B@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: "'entmib@ietf.org'" <entmib@ietf.org>
Date: Thu, 25 Mar 2004 10:29:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] Entity State: Two new Issues Created
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>

hi

I've created two new issues in http://rt.psg.com (ietf, ietf)

354 More Editorial Changes (2)
	New Editorial issues raised by Dave

355 OSI State to Something New Spectrum 
	The high-level issue from my last email which I think gates the
resolution of a number of other issues.

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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


From exim@www1.ietf.org  Thu Mar 25 10:44:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01394
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 10:44:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X1h-0001x2-3Q
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 10:44:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PFiC1s007333
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 10:44:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X1f-0001u4-6v; Thu, 25 Mar 2004 10:44:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6WpX-0000RE-Ts
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 10:31:39 -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 KAA00752
	for <entmib@ietf.org>; Thu, 25 Mar 2004 10:31:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6WpV-0000RG-00
	for entmib@ietf.org; Thu, 25 Mar 2004 10:31:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6WoM-0000K2-00
	for entmib@ietf.org; Thu, 25 Mar 2004 10:30:27 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Wnl-0000DJ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 10:29:49 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PFTHV28431
	for <entmib@ietf.org>; Thu, 25 Mar 2004 10:29:17 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KA87>; Thu, 25 Mar 2004 10:29:17 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2F5B@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: "'entmib@ietf.org'" <entmib@ietf.org>
Date: Thu, 25 Mar 2004 10:29:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] Entity State: Two new Issues Created
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>

hi

I've created two new issues in http://rt.psg.com (ietf, ietf)

354 More Editorial Changes (2)
	New Editorial issues raised by Dave

355 OSI State to Something New Spectrum 
	The high-level issue from my last email which I think gates the
resolution of a number of other issues.

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



From entmib-admin@ietf.org  Thu Mar 25 10:44:45 2004
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


From exim@www1.ietf.org  Thu Mar 25 10:44:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01417
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 10:44:46 -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-00022g-Ps
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 10:44:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PFiJ3L007830
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 10:44:19 -0500
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



From exim@www1.ietf.org  Thu Mar 25 11:07:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03820
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:07:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XNl-0006Hm-Ii
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:07:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PG71mq024142
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:07:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XNl-0006HC-8i; Thu, 25 Mar 2004 11:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XN4-0006BX-Uo
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:06:18 -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 LAA03755
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:06:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XN2-0003VS-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:06:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XM6-0003PX-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:05:19 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XKj-0002zJ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:03:53 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PG3Lg14022
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:03:21 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KCBJ>; Thu, 25 Mar 2004 11:03:21 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Thu, 25 Mar 2004 11:03:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #322 -  Textual Convention Names (Prefix)
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>

hi

Ok, so what would be the proper prefix? I think we have ruled out 'Entity'
and 'ITU'. 

There have been some suggestions about creating a new MIB module to house
the TCs. I've personally seen a lot of interest in using the TCs, so I think
it would be worth the effort. Of course if we deviate too far away from the
well-deployed OSI model, there may be less demand, but it is probably still
worth doing.

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Thursday, March 25, 2004 10:34 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Entity comments


In hindsight (after having seen discussion over the last 2 days) and based
on:
<clip>
> 
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

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



From entmib-admin@ietf.org  Thu Mar 25 11:20:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04703
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:20:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XaL-00086U-Jc; Thu, 25 Mar 2004 11:20:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xa6-00085Q-1W
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:19:46 -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 LAA04609
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:19:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xa2-0004Uw-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:19:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XYv-0004Rn-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:18:33 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XYS-0004OY-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:18:04 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2PGHwb18879;
	Thu, 25 Mar 2004 08:17:58 -0800
Message-Id: <5.2.0.9.2.20040325081635.02334c78@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 25 Mar 2004 08:17:47 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

Tell me again why a prefix of "EntityPhys" doesn't work?

At 11:03 AM 3/25/2004 -0500, Sharon Chisholm wrote:
>hi
>
>Ok, so what would be the proper prefix? I think we have ruled out 'Entity'
>and 'ITU'. 
>
>There have been some suggestions about creating a new MIB module to house
>the TCs. I've personally seen a lot of interest in using the TCs, so I think
>it would be worth the effort. Of course if we deviate too far away from the
>well-deployed OSI model, there may be less demand, but it is probably still
>worth doing.
>
>Sharon
>
>-----Original Message-----
>From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
>Sent: Thursday, March 25, 2004 10:34 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
>Subject: RE: [Entmib] Entity comments
>
>
>In hindsight (after having seen discussion over the last 2 days) and based
>on:
><clip>
>> 
>It seems that a ITU is NOT the proper prefix.
>But some prefix does make sense.
>
>Bert
Regards,
/david t. perkins 


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


From entmib-admin@ietf.org  Thu Mar 25 11:36:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05423
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:36:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xpr-0000w1-32; Thu, 25 Mar 2004 11:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XpP-0000tR-SH
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:35:35 -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 LAA05385
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:35:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XpO-0005W8-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:35:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XoT-0005Tv-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:34:37 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xo2-0005Qb-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:34:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PGXcc06000
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:33:38 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KC09>; Thu, 25 Mar 2004 11:33:38 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Thu, 25 Mar 2004 11:33:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #355: OSI State to Something New Spectrum
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>

hi

Ok, that means we are not tied to one end of the spectrum. Here are my two
views on where we setting in the spectrum.

Personal: I'm worried about change for the sake of changes or
over-simplification of this MIB which in this continuum could be considered
moving too far over the other way.   The first would end in mapping tables,
which while not ideal are not too bad, the latter would result in me and
others having to continue to use proprietary MIBs to get meaningful state
management. We've put a lot of effort into getting to current set of objects
to try to meet WG needs and I think we are pretty close. If we focus our
efforts on resolving the known issues without falling down the slippery
slope of re-designing everything, we can be done soon. If we don't we could
be here for another two years. I haven't yet seen consensus for deleting any
of the states, but if we get there I think I'd prefer to see them made
optional instead.

Co-Editor: As indicated, if we deviate too much we need to provide a mapping
back to the OSI model much like we have done with other state objects. 

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Thursday, March 25, 2004 10:34 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Entity comments


In hindsight (after having seen discussion over the last 2 days) and based
on:
<clip>
> 
> 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

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


From exim@www1.ietf.org  Thu Mar 25 11:36:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05424
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:36:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xpr-0000wf-M7
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:36:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGa3gx003609
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:36:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xpr-0000w1-32; Thu, 25 Mar 2004 11:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XpP-0000tR-SH
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:35:35 -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 LAA05385
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:35:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XpO-0005W8-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:35:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XoT-0005Tv-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:34:37 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xo2-0005Qb-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:34:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PGXcc06000
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:33:38 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KC09>; Thu, 25 Mar 2004 11:33:38 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Thu, 25 Mar 2004 11:33:38 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #355: OSI State to Something New Spectrum
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>

hi

Ok, that means we are not tied to one end of the spectrum. Here are my two
views on where we setting in the spectrum.

Personal: I'm worried about change for the sake of changes or
over-simplification of this MIB which in this continuum could be considered
moving too far over the other way.   The first would end in mapping tables,
which while not ideal are not too bad, the latter would result in me and
others having to continue to use proprietary MIBs to get meaningful state
management. We've put a lot of effort into getting to current set of objects
to try to meet WG needs and I think we are pretty close. If we focus our
efforts on resolving the known issues without falling down the slippery
slope of re-designing everything, we can be done soon. If we don't we could
be here for another two years. I haven't yet seen consensus for deleting any
of the states, but if we get there I think I'd prefer to see them made
optional instead.

Co-Editor: As indicated, if we deviate too much we need to provide a mapping
back to the OSI model much like we have done with other state objects. 

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Thursday, March 25, 2004 10:34 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Entity comments


In hindsight (after having seen discussion over the last 2 days) and based
on:
<clip>
> 
> 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

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



From entmib-admin@ietf.org  Thu Mar 25 11:40:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05661
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:40:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xth-0001kE-I0; Thu, 25 Mar 2004 11:40:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xt9-0001es-Sn
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:39:27 -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 LAA05590
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:39:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xt4-0005ko-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:39:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xs9-0005gq-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:38:25 -0500
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XrG-0005ao-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:37:30 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2PGauc19204
	for <entmib@ietf.org>; Thu, 25 Mar 2004 10:36:57 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72)
	id <169967G7>; Thu, 25 Mar 2004 17:36:54 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503ED059B@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "David T. Perkins" <dperkins@dsperkins.com>,
        Sharon Chisholm
	 <schishol@nortelnetworks.com>, entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 17:36: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>

> HI,
> 
> Tell me again why a prefix of "EntityPhys" doesn't work?
> 
That would work for me!

Bert

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


From exim@www1.ietf.org  Thu Mar 25 11:40:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05679
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:40:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xti-0001kn-U9
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:40:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGe2u9006722
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:40:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xth-0001kE-I0; Thu, 25 Mar 2004 11:40:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xt9-0001es-Sn
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:39:27 -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 LAA05590
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:39:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xt4-0005ko-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:39:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xs9-0005gq-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:38:25 -0500
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XrG-0005ao-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:37:30 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id i2PGauc19204
	for <entmib@ietf.org>; Thu, 25 Mar 2004 10:36:57 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72)
	id <169967G7>; Thu, 25 Mar 2004 17:36:54 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503ED059B@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "David T. Perkins" <dperkins@dsperkins.com>,
        Sharon Chisholm
	 <schishol@nortelnetworks.com>, entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 17:36: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>

> HI,
> 
> Tell me again why a prefix of "EntityPhys" doesn't work?
> 
That would work for me!

Bert

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



From entmib-admin@ietf.org  Thu Mar 25 11:42:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05838
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:42:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xvd-0001w7-EI; Thu, 25 Mar 2004 11:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xv7-0001v4-66
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:41:29 -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 LAA05784
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:41:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xv5-0005vC-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:41:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XuM-0005t1-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:40:42 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xtr-0005nG-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:40:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PGdec06735
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:39:40 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KDF6>; Thu, 25 Mar 2004 11:39:40 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D3086@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 11:39:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

We had previously agreed that if these state objects were not specific to
physical entities then they should not have this prefix. We seem to be back
to not agreeing that they are specific to physical entities. 

I don't think they are and I don't think they should be. What specifically
about them do people view as being specific to physical entities?

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Thursday, March 25, 2004 11:37 AM
To: David T. Perkins; Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] #322 - Textual Convention Names (Prefix)


> HI,
> 
> Tell me again why a prefix of "EntityPhys" doesn't work?
> 
That would work for me!

Bert

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


From exim@www1.ietf.org  Thu Mar 25 11:42:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05840
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:42:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xvd-0001wk-K9
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:42:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGg1T3007470
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xvd-0001w7-EI; Thu, 25 Mar 2004 11:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xv7-0001v4-66
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:41:29 -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 LAA05784
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:41:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xv5-0005vC-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:41:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XuM-0005t1-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:40:42 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xtr-0005nG-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:40:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PGdec06735
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:39:40 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KDF6>; Thu, 25 Mar 2004 11:39:40 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D3086@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 11:39:39 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

We had previously agreed that if these state objects were not specific to
physical entities then they should not have this prefix. We seem to be back
to not agreeing that they are specific to physical entities. 

I don't think they are and I don't think they should be. What specifically
about them do people view as being specific to physical entities?

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Thursday, March 25, 2004 11:37 AM
To: David T. Perkins; Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] #322 - Textual Convention Names (Prefix)


> HI,
> 
> Tell me again why a prefix of "EntityPhys" doesn't work?
> 
That would work for me!

Bert

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



From entmib-admin@ietf.org  Thu Mar 25 11:43:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05915
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:43:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XwZ-00021F-Uq; Thu, 25 Mar 2004 11:42:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xvz-0001xw-RL
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:42:23 -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 LAA05819
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:42:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xvy-0005yP-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:42:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xv5-0005vG-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:41:28 -0500
Received: from merkur.iu-bremen.de ([212.201.44.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XuR-0005p7-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:40:47 -0500
Received: from localhost (localhost [127.0.0.1])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id 38146894D3; Thu, 25 Mar 2004 17:40:16 +0100 (CET)
Received: from james.eecs.iu-bremen.de (unknown [212.201.46.228])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id 83ECD893C1; Thu, 25 Mar 2004 17:40:15 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 95A6E851E; Thu, 25 Mar 2004 17:40:15 +0100 (CET)
Date: Thu, 25 Mar 2004 17:40:15 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Message-ID: <20040325164015.GC1194@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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>

On Thu, Mar 25, 2004 at 11:03:21AM -0500, Sharon Chisholm wrote:
 
> There have been some suggestions about creating a new MIB module to house
> the TCs. I've personally seen a lot of interest in using the TCs, so I think
> it would be worth the effort. Of course if we deviate too far away from the
> well-deployed OSI model, there may be less demand, but it is probably still
> worth doing.

Where did you see this interest? Inhouse, other companies, WG in the
IETF? ITU? And can these people speak up or is this "confidential"
interest in these TCs?

/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


From exim@www1.ietf.org  Thu Mar 25 11:43:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05923
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:43:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xwa-00021f-2m
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:43:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGh0d3007771
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:43:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XwZ-00021F-Uq; Thu, 25 Mar 2004 11:42:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xvz-0001xw-RL
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:42:23 -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 LAA05819
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:42:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xvy-0005yP-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:42:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xv5-0005vG-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:41:28 -0500
Received: from merkur.iu-bremen.de ([212.201.44.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XuR-0005p7-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:40:47 -0500
Received: from localhost (localhost [127.0.0.1])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id 38146894D3; Thu, 25 Mar 2004 17:40:16 +0100 (CET)
Received: from james.eecs.iu-bremen.de (unknown [212.201.46.228])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id 83ECD893C1; Thu, 25 Mar 2004 17:40:15 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 95A6E851E; Thu, 25 Mar 2004 17:40:15 +0100 (CET)
Date: Thu, 25 Mar 2004 17:40:15 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Message-ID: <20040325164015.GC1194@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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>

On Thu, Mar 25, 2004 at 11:03:21AM -0500, Sharon Chisholm wrote:
 
> There have been some suggestions about creating a new MIB module to house
> the TCs. I've personally seen a lot of interest in using the TCs, so I think
> it would be worth the effort. Of course if we deviate too far away from the
> well-deployed OSI model, there may be less demand, but it is probably still
> worth doing.

Where did you see this interest? Inhouse, other companies, WG in the
IETF? ITU? And can these people speak up or is this "confidential"
interest in these TCs?

/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



From entmib-admin@ietf.org  Thu Mar 25 11:52:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06398
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:52:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Y5Q-0002hr-G9; Thu, 25 Mar 2004 11:52:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Y4y-0002eD-35
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:51:40 -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 LAA06375
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:51:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Y4w-0006XF-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:51:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Y4A-0006Tw-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:50:51 -0500
Received: from merkur.iu-bremen.de ([212.201.44.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Y3Z-0006PI-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:50:13 -0500
Received: from localhost (localhost [127.0.0.1])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id D2F6B894E2; Thu, 25 Mar 2004 17:49:42 +0100 (CET)
Received: from james.eecs.iu-bremen.de (unknown [212.201.46.228])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id 58DA9894D3; Thu, 25 Mar 2004 17:49:37 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 3B1C3851E; Thu, 25 Mar 2004 17:49:37 +0100 (CET)
Date: Thu, 25 Mar 2004 17:49:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Message-ID: <20040325164937.GD1194@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A9D3086@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D3086@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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>

On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
 
> We had previously agreed that if these state objects were not specific to
> physical entities then they should not have this prefix. We seem to be back
> to not agreeing that they are specific to physical entities. 
 
> I don't think they are and I don't think they should be. What specifically
> about them do people view as being specific to physical entities?

I am not so sure how much agreement there has been on this issue. I
understand that you have a strong opinion here, I am less sure that 
this opinion has become WG consensus. 

As I said before: If these TCs are generic, they must go into a separate 
module since I do not want depend on an extension of the entity MIB and
hence also on the entity MIB just because I want to use these generic 
TCs in another MIB. If the TCs are not generic (or we do not know yet), 
lets be conversative and give the names the Ent... prefix.

/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


From exim@www1.ietf.org  Thu Mar 25 11:52:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06411
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:52:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Y5R-0002iT-PX
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:52:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGq9r9010430
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:52:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Y5Q-0002hr-G9; Thu, 25 Mar 2004 11:52:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Y4y-0002eD-35
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:51:40 -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 LAA06375
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:51:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Y4w-0006XF-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:51:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Y4A-0006Tw-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:50:51 -0500
Received: from merkur.iu-bremen.de ([212.201.44.27])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Y3Z-0006PI-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:50:13 -0500
Received: from localhost (localhost [127.0.0.1])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id D2F6B894E2; Thu, 25 Mar 2004 17:49:42 +0100 (CET)
Received: from james.eecs.iu-bremen.de (unknown [212.201.46.228])
	by merkur.iu-bremen.de (Postfix) with ESMTP
	id 58DA9894D3; Thu, 25 Mar 2004 17:49:37 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 3B1C3851E; Thu, 25 Mar 2004 17:49:37 +0100 (CET)
Date: Thu, 25 Mar 2004 17:49:37 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Message-ID: <20040325164937.GD1194@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A9D3086@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D3086@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by AMaViS 0.3.12pre8
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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>

On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
 
> We had previously agreed that if these state objects were not specific to
> physical entities then they should not have this prefix. We seem to be back
> to not agreeing that they are specific to physical entities. 
 
> I don't think they are and I don't think they should be. What specifically
> about them do people view as being specific to physical entities?

I am not so sure how much agreement there has been on this issue. I
understand that you have a strong opinion here, I am less sure that 
this opinion has become WG consensus. 

As I said before: If these TCs are generic, they must go into a separate 
module since I do not want depend on an extension of the entity MIB and
hence also on the entity MIB just because I want to use these generic 
TCs in another MIB. If the TCs are not generic (or we do not know yet), 
lets be conversative and give the names the Ent... prefix.

/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



From entmib-admin@ietf.org  Thu Mar 25 11:53:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03818
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 11:07:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XNl-0006HC-8i; Thu, 25 Mar 2004 11:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XN4-0006BX-Uo
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:06:18 -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 LAA03755
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:06:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XN2-0003VS-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:06:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XM6-0003PX-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:05:19 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XKj-0002zJ-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:03:53 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PG3Lg14022
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:03:21 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KCBJ>; Thu, 25 Mar 2004 11:03:21 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Thu, 25 Mar 2004 11:03:21 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #322 -  Textual Convention Names (Prefix)
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>

hi

Ok, so what would be the proper prefix? I think we have ruled out 'Entity'
and 'ITU'. 

There have been some suggestions about creating a new MIB module to house
the TCs. I've personally seen a lot of interest in using the TCs, so I think
it would be worth the effort. Of course if we deviate too far away from the
well-deployed OSI model, there may be less demand, but it is probably still
worth doing.

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Thursday, March 25, 2004 10:34 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] Entity comments


In hindsight (after having seen discussion over the last 2 days) and based
on:
<clip>
> 
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

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


From entmib-admin@ietf.org  Thu Mar 25 12:05:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07064
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 12:05:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YHs-00045c-Ra; Thu, 25 Mar 2004 12:05:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YHE-00042d-5f
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 12:04:20 -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 MAA06951
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:04:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YHC-0007Gl-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:04:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YGC-0007Bd-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:03:16 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YF3-00075v-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:02:13 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PH1Kc16250
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:01:20 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KDW3>; Thu, 25 Mar 2004 12:01:20 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D30D5@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 12:01:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

I've seen it in-house. I can't remember anything other than general interest
in IETF or elsewhere about this. I want to say there was something discussed
at the last IETF meeting, but I think that was about one of the Alarm TCs. 

I'm speculating there would be lots of use in those places if we get the
state stuff right. Pretty much everything can have state and people seem to
like defining objects for it. Plus, other working groups have shown interest
in the probable cause object we did in a separate Alarm TC MIB which has
come as big surprise to me. All the other TCs we did in that work have also
come in handy in-house.

I might be able to dig some people out, but it might help in convincing them
if I knew specifically what info you were looking for. I know there was
specific interest in the AlarmStatus and StandbyStatus TCs.

Sharon

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Thursday, March 25, 2004 11:40 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)


On Thu, Mar 25, 2004 at 11:03:21AM -0500, Sharon Chisholm wrote:
 
> There have been some suggestions about creating a new MIB module to 
> house the TCs. I've personally seen a lot of interest in using the 
> TCs, so I think it would be worth the effort. Of course if we deviate 
> too far away from the well-deployed OSI model, there may be less 
> demand, but it is probably still worth doing.

Where did you see this interest? Inhouse, other companies, WG in the IETF?
ITU? And can these people speak up or is this "confidential" interest in
these TCs?

/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


From exim@www1.ietf.org  Thu Mar 25 12:05:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07081
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 12:05:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YHx-00047W-NG
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 12:05:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PH55f7015837
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 12:05:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YHs-00045c-Ra; Thu, 25 Mar 2004 12:05:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YHE-00042d-5f
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 12:04:20 -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 MAA06951
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:04:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YHC-0007Gl-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:04:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YGC-0007Bd-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:03:16 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YF3-00075v-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:02:13 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PH1Kc16250
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:01:20 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6KDW3>; Thu, 25 Mar 2004 12:01:20 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D30D5@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 12:01:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

I've seen it in-house. I can't remember anything other than general interest
in IETF or elsewhere about this. I want to say there was something discussed
at the last IETF meeting, but I think that was about one of the Alarm TCs. 

I'm speculating there would be lots of use in those places if we get the
state stuff right. Pretty much everything can have state and people seem to
like defining objects for it. Plus, other working groups have shown interest
in the probable cause object we did in a separate Alarm TC MIB which has
come as big surprise to me. All the other TCs we did in that work have also
come in handy in-house.

I might be able to dig some people out, but it might help in convincing them
if I knew specifically what info you were looking for. I know there was
specific interest in the AlarmStatus and StandbyStatus TCs.

Sharon

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Thursday, March 25, 2004 11:40 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)


On Thu, Mar 25, 2004 at 11:03:21AM -0500, Sharon Chisholm wrote:
 
> There have been some suggestions about creating a new MIB module to 
> house the TCs. I've personally seen a lot of interest in using the 
> TCs, so I think it would be worth the effort. Of course if we deviate 
> too far away from the well-deployed OSI model, there may be less 
> demand, but it is probably still worth doing.

Where did you see this interest? Inhouse, other companies, WG in the IETF?
ITU? And can these people speak up or is this "confidential" interest in
these TCs?

/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



From exim@www1.ietf.org  Thu Mar 25 12:13:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04709
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:20:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XaM-000871-KB
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:20:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGK2Lp031173
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 11:20:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XaL-00086U-Jc; Thu, 25 Mar 2004 11:20:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xa6-00085Q-1W
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 11:19:46 -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 LAA04609
	for <entmib@ietf.org>; Thu, 25 Mar 2004 11:19:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xa2-0004Uw-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:19:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XYv-0004Rn-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:18:33 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XYS-0004OY-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:18:04 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2PGHwb18879;
	Thu, 25 Mar 2004 08:17:58 -0800
Message-Id: <5.2.0.9.2.20040325081635.02334c78@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 25 Mar 2004 08:17:47 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D2FEB@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

Tell me again why a prefix of "EntityPhys" doesn't work?

At 11:03 AM 3/25/2004 -0500, Sharon Chisholm wrote:
>hi
>
>Ok, so what would be the proper prefix? I think we have ruled out 'Entity'
>and 'ITU'. 
>
>There have been some suggestions about creating a new MIB module to house
>the TCs. I've personally seen a lot of interest in using the TCs, so I think
>it would be worth the effort. Of course if we deviate too far away from the
>well-deployed OSI model, there may be less demand, but it is probably still
>worth doing.
>
>Sharon
>
>-----Original Message-----
>From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
>Sent: Thursday, March 25, 2004 10:34 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
>Subject: RE: [Entmib] Entity comments
>
>
>In hindsight (after having seen discussion over the last 2 days) and based
>on:
><clip>
>> 
>It seems that a ITU is NOT the proper prefix.
>But some prefix does make sense.
>
>Bert
Regards,
/david t. perkins 


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



From entmib-admin@ietf.org  Thu Mar 25 12:24:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09070
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 12:24:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Yac-0006yi-EA; Thu, 25 Mar 2004 12:24:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YaB-0006vd-Al
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 12:23:55 -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 MAA08935
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:23:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Ya9-00022X-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:23:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YZF-0001un-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:22:58 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YYO-0001gq-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:22:04 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PHLXc18247
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:21:33 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6K1C0>; Thu, 25 Mar 2004 12:21:33 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 12:21:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

I don't remember anyone objecting to Bert's Post:

"In general, when a TC is clearly generic, then using the most 
intuitive and generic name makes sense. In most cases, such a TC would 
be better specified in a generic/independent document 
(or at least a separate MIB module).

As soon as a TC is specific to some technology or to some WG, then 
prefixing it with the wg or technology-specific acronym is the way to 
go."

Are you suggesting this doesn't reflect working group consensus? This is
what I referred to as the consensus, not the following bit that was
preference with "I think". If it wasn't clear enough that I was expressing
my opinion at that point and not my assessment of working group consensus,
then I can certainly prefix all personal opinions with "personal" like I did
in a recent email and all the others with 'editor'.

Sharon

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Thursday, March 25, 2004 11:50 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)


On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
 
> We had previously agreed that if these state objects were not specific 
> to physical entities then they should not have this prefix. We seem to 
> be back to not agreeing that they are specific to physical entities.
 
> I don't think they are and I don't think they should be. What 
> specifically about them do people view as being specific to physical 
> entities?

I am not so sure how much agreement there has been on this issue. I
understand that you have a strong opinion here, I am less sure that 
this opinion has become WG consensus. 

As I said before: If these TCs are generic, they must go into a separate 
module since I do not want depend on an extension of the entity MIB and
hence also on the entity MIB just because I want to use these generic 
TCs in another MIB. If the TCs are not generic (or we do not know yet), 
lets be conversative and give the names the Ent... prefix.

/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


From exim@www1.ietf.org  Thu Mar 25 13:00:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11288
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 13:00:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z8y-00033D-Sh
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 12:59:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PHxq0r011677
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 12:59:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z8K-000319-Jr; Thu, 25 Mar 2004 12:59:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z6c-0002sc-NN
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 12:57:26 -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 MAA11165
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:57:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z6a-0004Jv-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:57:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Z5n-0004Hs-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:56:36 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z56-0004F8-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:55:53 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2PHtgb20501;
	Thu, 25 Mar 2004 09:55:42 -0800
Message-Id: <5.2.0.9.2.20040325095035.02316988@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 25 Mar 2004 09:55:36 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

I don't think that you would find anyone that has knowledge and experience
in the SMI to disagree with the below quote from Bert. However, many of
us would have problems with classifying the TCs in the ent-phys-state
MIB document as generic.

And by the way, if anyone who has not yet read X.731, X.721, and X.732
(yes, you really need all 3) and could not get a copy, sent me private
email and I'll help you get a copy.

At 12:21 PM 3/25/2004 -0500, Sharon Chisholm wrote:
>hi
>
>I don't remember anyone objecting to Bert's Post:
>
>"In general, when a TC is clearly generic, then using the most 
>intuitive and generic name makes sense. In most cases, such a TC would 
>be better specified in a generic/independent document 
>(or at least a separate MIB module).
>
>As soon as a TC is specific to some technology or to some WG, then 
>prefixing it with the wg or technology-specific acronym is the way to 
>go."
>
>Are you suggesting this doesn't reflect working group consensus? This is
>what I referred to as the consensus, not the following bit that was
>preference with "I think". If it wasn't clear enough that I was expressing
>my opinion at that point and not my assessment of working group consensus,
>then I can certainly prefix all personal opinions with "personal" like I did
>in a recent email and all the others with 'editor'.
>
>Sharon
>
>-----Original Message-----
>From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
>Sent: Thursday, March 25, 2004 11:50 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Cc: entmib@ietf.org
>Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)
>
>
>On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
> 
>> We had previously agreed that if these state objects were not specific 
>> to physical entities then they should not have this prefix. We seem to 
>> be back to not agreeing that they are specific to physical entities.
> 
>> I don't think they are and I don't think they should be. What 
>> specifically about them do people view as being specific to physical 
>> entities?
>
>I am not so sure how much agreement there has been on this issue. I
>understand that you have a strong opinion here, I am less sure that 
>this opinion has become WG consensus. 
>
>As I said before: If these TCs are generic, they must go into a separate 
>module since I do not want depend on an extension of the entity MIB and
>hence also on the entity MIB just because I want to use these generic 
>TCs in another MIB. If the TCs are not generic (or we do not know yet), 
>lets be conversative and give the names the Ent... prefix.
>
>/js
>
>-- 
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany

Regards,
/david t. perkins 


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



From exim@www1.ietf.org  Thu Mar 25 13:08:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11941
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 13:08:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZGr-0004Mo-K9
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 13:08:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PI81pD016776
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 13:08:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZGr-0004MR-ES; Thu, 25 Mar 2004 13:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZF6-00040G-Ud
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 13:06:12 -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 NAA11777
	for <entmib@ietf.org>; Thu, 25 Mar 2004 13:06:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZF5-0005Es-00
	for entmib@ietf.org; Thu, 25 Mar 2004 13:06:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZE1-000551-00
	for entmib@ietf.org; Thu, 25 Mar 2004 13:05:06 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZD9-0004sW-00
	for entmib@ietf.org; Thu, 25 Mar 2004 13:04:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PI3dk19553
	for <entmib@ietf.org>; Thu, 25 Mar 2004 13:03:40 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6K19N>; Thu, 25 Mar 2004 13:03:40 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D3186@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 13:03:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Editor: Yes, that is the bit I'm trying to gage consensus on and understand.
For those who disagree the TCs are generic, is the problem

1. That you don't think we should be creating general TCs
2. There is something in the current TCs that would prevent them from being
used generically

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Thursday, March 25, 2004 12:56 PM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] #322 - Textual Convention Names (Prefix)


HI,

I don't think that you would find anyone that has knowledge and experience
in the SMI to disagree with the below quote from Bert. However, many of us
would have problems with classifying the TCs in the ent-phys-state MIB
document as generic.

And by the way, if anyone who has not yet read X.731, X.721, and X.732 (yes,
you really need all 3) and could not get a copy, sent me private email and
I'll help you get a copy.

At 12:21 PM 3/25/2004 -0500, Sharon Chisholm wrote:
>hi
>
>I don't remember anyone objecting to Bert's Post:
>
>"In general, when a TC is clearly generic, then using the most
>intuitive and generic name makes sense. In most cases, such a TC would 
>be better specified in a generic/independent document 
>(or at least a separate MIB module).
>
>As soon as a TC is specific to some technology or to some WG, then
>prefixing it with the wg or technology-specific acronym is the way to 
>go."
>
>Are you suggesting this doesn't reflect working group consensus? This 
>is what I referred to as the consensus, not the following bit that was 
>preference with "I think". If it wasn't clear enough that I was 
>expressing my opinion at that point and not my assessment of working 
>group consensus, then I can certainly prefix all personal opinions with 
>"personal" like I did in a recent email and all the others with 
>'editor'.
>
>Sharon
>
>-----Original Message-----
>From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de]
>Sent: Thursday, March 25, 2004 11:50 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Cc: entmib@ietf.org
>Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)
>
>
>On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
> 
>> We had previously agreed that if these state objects were not 
>> specific
>> to physical entities then they should not have this prefix. We seem to 
>> be back to not agreeing that they are specific to physical entities.
> 
>> I don't think they are and I don't think they should be. What
>> specifically about them do people view as being specific to physical 
>> entities?
>
>I am not so sure how much agreement there has been on this issue. I 
>understand that you have a strong opinion here, I am less sure that 
>this opinion has become WG consensus.
>
>As I said before: If these TCs are generic, they must go into a 
>separate
>module since I do not want depend on an extension of the entity MIB and
>hence also on the entity MIB just because I want to use these generic 
>TCs in another MIB. If the TCs are not generic (or we do not know yet), 
>lets be conversative and give the names the Ent... prefix.
>
>/js
>
>-- 
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany

Regards,
/david t. perkins 


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



From exim@www1.ietf.org  Thu Mar 25 13:13:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09071
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 12:24:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Yac-0006z6-SJ
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 12:24:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PHOMjd026848
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 12:24:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Yac-0006yi-EA; Thu, 25 Mar 2004 12:24:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6YaB-0006vd-Al
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 12:23:55 -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 MAA08935
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:23:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Ya9-00022X-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:23:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6YZF-0001un-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:22:58 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6YYO-0001gq-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:22:04 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PHLXc18247
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:21:33 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6K1C0>; Thu, 25 Mar 2004 12:21:33 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 12:21:32 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

I don't remember anyone objecting to Bert's Post:

"In general, when a TC is clearly generic, then using the most 
intuitive and generic name makes sense. In most cases, such a TC would 
be better specified in a generic/independent document 
(or at least a separate MIB module).

As soon as a TC is specific to some technology or to some WG, then 
prefixing it with the wg or technology-specific acronym is the way to 
go."

Are you suggesting this doesn't reflect working group consensus? This is
what I referred to as the consensus, not the following bit that was
preference with "I think". If it wasn't clear enough that I was expressing
my opinion at that point and not my assessment of working group consensus,
then I can certainly prefix all personal opinions with "personal" like I did
in a recent email and all the others with 'editor'.

Sharon

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
Sent: Thursday, March 25, 2004 11:50 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)


On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
 
> We had previously agreed that if these state objects were not specific 
> to physical entities then they should not have this prefix. We seem to 
> be back to not agreeing that they are specific to physical entities.
 
> I don't think they are and I don't think they should be. What 
> specifically about them do people view as being specific to physical 
> entities?

I am not so sure how much agreement there has been on this issue. I
understand that you have a strong opinion here, I am less sure that 
this opinion has become WG consensus. 

As I said before: If these TCs are generic, they must go into a separate 
module since I do not want depend on an extension of the entity MIB and
hence also on the entity MIB just because I want to use these generic 
TCs in another MIB. If the TCs are not generic (or we do not know yet), 
lets be conversative and give the names the Ent... prefix.

/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



From entmib-admin@ietf.org  Thu Mar 25 13:48:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11289
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 13:00:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z8K-000319-Jr; Thu, 25 Mar 2004 12:59:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Z6c-0002sc-NN
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 12:57:26 -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 MAA11165
	for <entmib@ietf.org>; Thu, 25 Mar 2004 12:57:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z6a-0004Jv-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:57:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Z5n-0004Hs-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:56:36 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Z56-0004F8-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:55:53 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2PHtgb20501;
	Thu, 25 Mar 2004 09:55:42 -0800
Message-Id: <5.2.0.9.2.20040325095035.02316988@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 25 Mar 2004 09:55:36 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

I don't think that you would find anyone that has knowledge and experience
in the SMI to disagree with the below quote from Bert. However, many of
us would have problems with classifying the TCs in the ent-phys-state
MIB document as generic.

And by the way, if anyone who has not yet read X.731, X.721, and X.732
(yes, you really need all 3) and could not get a copy, sent me private
email and I'll help you get a copy.

At 12:21 PM 3/25/2004 -0500, Sharon Chisholm wrote:
>hi
>
>I don't remember anyone objecting to Bert's Post:
>
>"In general, when a TC is clearly generic, then using the most 
>intuitive and generic name makes sense. In most cases, such a TC would 
>be better specified in a generic/independent document 
>(or at least a separate MIB module).
>
>As soon as a TC is specific to some technology or to some WG, then 
>prefixing it with the wg or technology-specific acronym is the way to 
>go."
>
>Are you suggesting this doesn't reflect working group consensus? This is
>what I referred to as the consensus, not the following bit that was
>preference with "I think". If it wasn't clear enough that I was expressing
>my opinion at that point and not my assessment of working group consensus,
>then I can certainly prefix all personal opinions with "personal" like I did
>in a recent email and all the others with 'editor'.
>
>Sharon
>
>-----Original Message-----
>From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de] 
>Sent: Thursday, March 25, 2004 11:50 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Cc: entmib@ietf.org
>Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)
>
>
>On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
> 
>> We had previously agreed that if these state objects were not specific 
>> to physical entities then they should not have this prefix. We seem to 
>> be back to not agreeing that they are specific to physical entities.
> 
>> I don't think they are and I don't think they should be. What 
>> specifically about them do people view as being specific to physical 
>> entities?
>
>I am not so sure how much agreement there has been on this issue. I
>understand that you have a strong opinion here, I am less sure that 
>this opinion has become WG consensus. 
>
>As I said before: If these TCs are generic, they must go into a separate 
>module since I do not want depend on an extension of the entity MIB and
>hence also on the entity MIB just because I want to use these generic 
>TCs in another MIB. If the TCs are not generic (or we do not know yet), 
>lets be conversative and give the names the Ent... prefix.
>
>/js
>
>-- 
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany

Regards,
/david t. perkins 


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


From entmib-admin@ietf.org  Thu Mar 25 13:53:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11940
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 13:08:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZGr-0004MR-ES; Thu, 25 Mar 2004 13:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ZF6-00040G-Ud
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 13:06:12 -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 NAA11777
	for <entmib@ietf.org>; Thu, 25 Mar 2004 13:06:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZF5-0005Es-00
	for entmib@ietf.org; Thu, 25 Mar 2004 13:06:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ZE1-000551-00
	for entmib@ietf.org; Thu, 25 Mar 2004 13:05:06 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ZD9-0004sW-00
	for entmib@ietf.org; Thu, 25 Mar 2004 13:04:11 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2PI3dk19553
	for <entmib@ietf.org>; Thu, 25 Mar 2004 13:03:40 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6K19N>; Thu, 25 Mar 2004 13:03:40 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A9D3186@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Thu, 25 Mar 2004 13:03:37 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

hi

Editor: Yes, that is the bit I'm trying to gage consensus on and understand.
For those who disagree the TCs are generic, is the problem

1. That you don't think we should be creating general TCs
2. There is something in the current TCs that would prevent them from being
used generically

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Thursday, March 25, 2004 12:56 PM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] #322 - Textual Convention Names (Prefix)


HI,

I don't think that you would find anyone that has knowledge and experience
in the SMI to disagree with the below quote from Bert. However, many of us
would have problems with classifying the TCs in the ent-phys-state MIB
document as generic.

And by the way, if anyone who has not yet read X.731, X.721, and X.732 (yes,
you really need all 3) and could not get a copy, sent me private email and
I'll help you get a copy.

At 12:21 PM 3/25/2004 -0500, Sharon Chisholm wrote:
>hi
>
>I don't remember anyone objecting to Bert's Post:
>
>"In general, when a TC is clearly generic, then using the most
>intuitive and generic name makes sense. In most cases, such a TC would 
>be better specified in a generic/independent document 
>(or at least a separate MIB module).
>
>As soon as a TC is specific to some technology or to some WG, then
>prefixing it with the wg or technology-specific acronym is the way to 
>go."
>
>Are you suggesting this doesn't reflect working group consensus? This 
>is what I referred to as the consensus, not the following bit that was 
>preference with "I think". If it wasn't clear enough that I was 
>expressing my opinion at that point and not my assessment of working 
>group consensus, then I can certainly prefix all personal opinions with 
>"personal" like I did in a recent email and all the others with 
>'editor'.
>
>Sharon
>
>-----Original Message-----
>From: Juergen Schoenwaelder [mailto:j.schoenwaelder@iu-bremen.de]
>Sent: Thursday, March 25, 2004 11:50 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Cc: entmib@ietf.org
>Subject: Re: [Entmib] #322 - Textual Convention Names (Prefix)
>
>
>On Thu, Mar 25, 2004 at 11:39:39AM -0500, Sharon Chisholm wrote:
> 
>> We had previously agreed that if these state objects were not 
>> specific
>> to physical entities then they should not have this prefix. We seem to 
>> be back to not agreeing that they are specific to physical entities.
> 
>> I don't think they are and I don't think they should be. What
>> specifically about them do people view as being specific to physical 
>> entities?
>
>I am not so sure how much agreement there has been on this issue. I 
>understand that you have a strong opinion here, I am less sure that 
>this opinion has become WG consensus.
>
>As I said before: If these TCs are generic, they must go into a 
>separate
>module since I do not want depend on an extension of the entity MIB and
>hence also on the entity MIB just because I want to use these generic 
>TCs in another MIB. If the TCs are not generic (or we do not know yet), 
>lets be conversative and give the names the Ent... prefix.
>
>/js
>
>-- 
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany

Regards,
/david t. perkins 


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


From entmib-admin@ietf.org  Thu Mar 25 14:36:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15486
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 14:36:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6adv-0005bm-1M; Thu, 25 Mar 2004 14:35:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6abU-0005OZ-A7
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 14:33:24 -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 OAA15268
	for <entmib@ietf.org>; Thu, 25 Mar 2004 14:33:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6abR-00027w-00
	for entmib@ietf.org; Thu, 25 Mar 2004 14:33:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6aaT-00024D-00
	for entmib@ietf.org; Thu, 25 Mar 2004 14:32:21 -0500
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6aZU-00021q-00
	for entmib@ietf.org; Thu, 25 Mar 2004 14:31:21 -0500
Received: from h-68-164-78-44.snvacaid.dynamic.covad.net ([68.164.78.44] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B6aZU-0004ih-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:31:20 -0800
Message-ID: <002601c412a0$1f0f9a00$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com>
Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
Date: Thu, 25 Mar 2004 11:33:38 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: <entmib@ietf.org>
> Sent: Thursday, March 25, 2004 8:33 AM
> Subject: [Entmib] #355: OSI State to Something New Spectrum
...
> Co-Editor: As indicated, if we deviate too much we need to provide a mapping
> back to the OSI model much like we have done with other state objects.

Such deviation seems contrary to the whole point of developing this MIB
module in the first place.  The more closely the semantics are aligned
with the OSI ones (within the constraints imposed by the differing object
models), the better.

...
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Thursday, March 25, 2004 10:34 AM
> To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
> Subject: RE: [Entmib] Entity comments
>
>
> In hindsight (after having seen discussion over the last 2 days) and based
> on:
> <clip>
> >
> > 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.
...

I'd have no problem with EntState as a prefix for the TCs, although I'd
also have no objection to leaving them un-prefixed, but in a separate
MIB module in the same document.

Randy



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


From exim@www1.ietf.org  Thu Mar 25 14:36:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15489
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 14:36:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6adv-0005cu-VN
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 14:35:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PJZtOt021616
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 14:35:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6adv-0005bm-1M; Thu, 25 Mar 2004 14:35:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6abU-0005OZ-A7
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 14:33:24 -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 OAA15268
	for <entmib@ietf.org>; Thu, 25 Mar 2004 14:33:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6abR-00027w-00
	for entmib@ietf.org; Thu, 25 Mar 2004 14:33:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6aaT-00024D-00
	for entmib@ietf.org; Thu, 25 Mar 2004 14:32:21 -0500
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6aZU-00021q-00
	for entmib@ietf.org; Thu, 25 Mar 2004 14:31:21 -0500
Received: from h-68-164-78-44.snvacaid.dynamic.covad.net ([68.164.78.44] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B6aZU-0004ih-00
	for entmib@ietf.org; Thu, 25 Mar 2004 11:31:20 -0800
Message-ID: <002601c412a0$1f0f9a00$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com>
Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
Date: Thu, 25 Mar 2004 11:33:38 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: <entmib@ietf.org>
> Sent: Thursday, March 25, 2004 8:33 AM
> Subject: [Entmib] #355: OSI State to Something New Spectrum
...
> Co-Editor: As indicated, if we deviate too much we need to provide a mapping
> back to the OSI model much like we have done with other state objects.

Such deviation seems contrary to the whole point of developing this MIB
module in the first place.  The more closely the semantics are aligned
with the OSI ones (within the constraints imposed by the differing object
models), the better.

...
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Thursday, March 25, 2004 10:34 AM
> To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
> Subject: RE: [Entmib] Entity comments
>
>
> In hindsight (after having seen discussion over the last 2 days) and based
> on:
> <clip>
> >
> > 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.
...

I'd have no problem with EntState as a prefix for the TCs, although I'd
also have no objection to leaving them un-prefixed, but in a separate
MIB module in the same document.

Randy



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



From entmib-admin@ietf.org  Thu Mar 25 15:08:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17128
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 15:08:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b8t-0007Nn-4B; Thu, 25 Mar 2004 15:07:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b6W-0005ZB-CS
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:05:28 -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 PAA16839
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:05:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b6T-0003xh-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:05:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6b5Y-0003wK-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:04:29 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b5L-0003ue-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:04:15 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2PK4Cb28048;
	Thu, 25 Mar 2004 12:04:12 -0800
Message-Id: <5.2.0.9.2.20040325115604.023269f8@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 25 Mar 2004 12:04:04 -0800
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, <entmib@ietf.org>
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
In-Reply-To: <002601c412a0$1f0f9a00$7f1afea9@oemcomputer>
References: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

Randy - it gets back to a fundamental question, which is 
"Is the ITU model and the specification for it worthwhile?"
In the 10+ years that I have asked this question, I have NEVER
gotten an answer. NEVER! In my own extensive analysis
(which included creating both state and alarm MIB modules
that are MUCH closer to the ITU models and specs than the
documents created in the IETF), it just isn't forth it.
Now, if someone would volunteer to show me an implementation
where the benefits surpass the costs, I'll create time to
learn from them, and change my tune. But pointing me to
documents and manuals just doesn't cut it. Is this clear?

At 11:33 AM 3/25/2004 -0800, Randy Presuhn wrote:
>Hi -
>
>> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
>> To: <entmib@ietf.org>
>> Sent: Thursday, March 25, 2004 8:33 AM
>> Subject: [Entmib] #355: OSI State to Something New Spectrum
>...
>> Co-Editor: As indicated, if we deviate too much we need to provide a mapping
>> back to the OSI model much like we have done with other state objects.
>
>Such deviation seems contrary to the whole point of developing this MIB
>module in the first place.  The more closely the semantics are aligned
>with the OSI ones (within the constraints imposed by the differing object
>models), the better.
>
>...
>> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
>> Sent: Thursday, March 25, 2004 10:34 AM
>> To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
>> Subject: RE: [Entmib] Entity comments
>>
>>
>> In hindsight (after having seen discussion over the last 2 days) and based
>> on:
>> <clip>
>> >
>> > 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.
>...
>
>I'd have no problem with EntState as a prefix for the TCs, although I'd
>also have no objection to leaving them un-prefixed, but in a separate
>MIB module in the same document.
>
>Randy

Regards,
/david t. perkins 


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


From exim@www1.ietf.org  Thu Mar 25 15:09:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17340
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 15:09:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bAD-0007wt-Hu
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:09:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PK9HTJ030474
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:09:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bAB-0007v1-OP; Thu, 25 Mar 2004 15:09:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b8c-00077q-CA
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:07:38 -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 PAA17063
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:07:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b8Z-00045X-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:07:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6b7d-00042L-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:06:38 -0500
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b72-0003zE-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:06:00 -0500
Received: from h-68-164-78-44.snvacaid.dynamic.covad.net ([68.164.78.44] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B6b72-0000qk-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:06:00 -0800
Message-ID: <004501c412a4$f73e2c80$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340A9D2E92@zcard0ka.ca.nortel.com>
Subject: Re: [Entmib] Entity comments
Date: Thu, 25 Mar 2004 12:08:40 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: <entmib@ietf.org>
> Sent: Thursday, March 25, 2004 6:35 AM
> Subject: RE: [Entmib] Entity comments
...
> <Dave>
>
> In general, it has seemed to me that in the beginning and at the last few
> ENITITY MIB WG meetings that the consensus desire was to have a simple
> extension to the entity physical table with the following:
>   adminState - to indicate the administrative state of a physical
>                component, and allow change
>   operState - to indicate the operational state of a physical component
>   backupState - to indicate if a physical component was backing up
>                   another physical component
>   alarmStatus - to indicate current fault conditions (if any) were
>                   present on a physical component
> A small minority wanted to base the definitions on X.731 definitions.
> However, the majority felt that was OK only if the above needs were not
> impacted, and the cost to support the objects on an agent was not
> significantly impacted.
> </Dave>

This list really needs usageState to be internally consistent.

> 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.

I'd rather not see an ITU prefix, even though I prefer that the semantics be
aligned as closely as practical with the ISO / ITU semantics.

> 2. Renaming state values. While I don't really see the value in changing the
> name of the state values, if that is consensus, then that it what we should
> do. If we do go down this path, we will have to add a section that describes
> the mapping from OSI states.

This seems unnecessarily confusing.

> Where do people think we should be?
...

I think that differences in the underlying object models will prevent perfect
equivalence.  However, we can come pretty close to matching the semantics
of the core of X.731.  These attributes have proven useful in the many years
they've been in use.  I think the document is on the right track.

Randy



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



From entmib-admin@ietf.org  Thu Mar 25 15:09:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17339
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 15:09:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bAB-0007v1-OP; Thu, 25 Mar 2004 15:09:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b8c-00077q-CA
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:07:38 -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 PAA17063
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:07:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b8Z-00045X-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:07:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6b7d-00042L-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:06:38 -0500
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b72-0003zE-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:06:00 -0500
Received: from h-68-164-78-44.snvacaid.dynamic.covad.net ([68.164.78.44] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B6b72-0000qk-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:06:00 -0800
Message-ID: <004501c412a4$f73e2c80$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340A9D2E92@zcard0ka.ca.nortel.com>
Subject: Re: [Entmib] Entity comments
Date: Thu, 25 Mar 2004 12:08:40 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: <entmib@ietf.org>
> Sent: Thursday, March 25, 2004 6:35 AM
> Subject: RE: [Entmib] Entity comments
...
> <Dave>
>
> In general, it has seemed to me that in the beginning and at the last few
> ENITITY MIB WG meetings that the consensus desire was to have a simple
> extension to the entity physical table with the following:
>   adminState - to indicate the administrative state of a physical
>                component, and allow change
>   operState - to indicate the operational state of a physical component
>   backupState - to indicate if a physical component was backing up
>                   another physical component
>   alarmStatus - to indicate current fault conditions (if any) were
>                   present on a physical component
> A small minority wanted to base the definitions on X.731 definitions.
> However, the majority felt that was OK only if the above needs were not
> impacted, and the cost to support the objects on an agent was not
> significantly impacted.
> </Dave>

This list really needs usageState to be internally consistent.

> 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.

I'd rather not see an ITU prefix, even though I prefer that the semantics be
aligned as closely as practical with the ISO / ITU semantics.

> 2. Renaming state values. While I don't really see the value in changing the
> name of the state values, if that is consensus, then that it what we should
> do. If we do go down this path, we will have to add a section that describes
> the mapping from OSI states.

This seems unnecessarily confusing.

> Where do people think we should be?
...

I think that differences in the underlying object models will prevent perfect
equivalence.  However, we can come pretty close to matching the semantics
of the core of X.731.  These attributes have proven useful in the many years
they've been in use.  I think the document is on the right track.

Randy



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


From entmib-admin@ietf.org  Thu Mar 25 15:16:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18131
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 15:16:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bGj-0001oC-3N; Thu, 25 Mar 2004 15:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bGD-0001ej-Ts
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:15:29 -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 PAA18033
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:15:27 -0500 (EST)
Resent-From: j.schoenwaelder@iu-bremen.de
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bGC-0004Xi-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:15:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6bFL-0004VD-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:14:35 -0500
Received: from g4a25.g.pppool.de ([80.185.74.37] helo=james.eecs.iu-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bEe-0004SW-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:13:53 -0500
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 3DEE5851E; Thu, 25 Mar 2004 21:13:51 +0100 (CET)
Resent-Date: Thu, 25 Mar 2004 21:13:51 +0100
Resent-Message-ID: <20040325201351.GB1447@iu-bremen.de>
Resent-To: entmib@ietf.org, schishol@nortelnetworks.com
X-Original-To: j.schoenwaelder@iu-bremen.de
Received: from localhost (localhost [127.0.0.1])
	by merkur.iu-bremen.de (Postfix) with ESMTP id DE561894F7
	for <j.schoenwaelder@iu-bremen.de>; Thu, 25 Mar 2004 21:11:10 +0100 (CET)
Received: from james.eecs.iu-bremen.de (G4a25.g.pppool.de [80.185.74.37])
	by merkur.iu-bremen.de (Postfix) with ESMTP id D844C8929E
	for <j.schoenwaelder@iu-bremen.de>; Thu, 25 Mar 2004 21:11:07 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 3E565851E; Thu, 25 Mar 2004 21:11:02 +0100 (CET)
Date: Thu, 25 Mar 2004 21:11:01 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Message-ID: <20040325201101.GA1447@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by AMaViS 0.3.12pre8
Resent-Date: Thu, 25 Mar 2004 15:13:53 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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>

On Thu, Mar 25, 2004 at 12:21:32PM -0500, Sharon Chisholm wrote:

> I don't remember anyone objecting to Bert's Post:
> 
> "In general, when a TC is clearly generic, then using the most 
> intuitive and generic name makes sense. In most cases, such a TC would 
> be better specified in a generic/independent document 
> (or at least a separate MIB module).
> 
> As soon as a TC is specific to some technology or to some WG, then 
> prefixing it with the wg or technology-specific acronym is the way to 
> go."
> 
> Are you suggesting this doesn't reflect working group consensus?

Sharon, you wrote the following:

> > We had previously agreed that if these state objects were not specific 
> > to physical entities then they should not have this prefix. We seem to 
> > be back to not agreeing that they are specific to physical entities.

I think this is not a fair summary of what Bert said (see the quote 
above) since you leave out more than half of his message which I 
consider important. And this is why I wrote:

> I am not sure how much agreement there has been on this issue

Clear now?

[I think my position on this issue is rather well documented now 
 and unless real new arguments come up, I really prefer to stay out 
 of this debate.]

/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


From exim@www1.ietf.org  Thu Mar 25 15:16:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18134
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 15:16:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bGj-0001of-A2
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:16:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PKG1Tf006962
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:16:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bGj-0001oC-3N; Thu, 25 Mar 2004 15:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bGD-0001ej-Ts
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:15:29 -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 PAA18033
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:15:27 -0500 (EST)
Resent-From: j.schoenwaelder@iu-bremen.de
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bGC-0004Xi-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:15:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6bFL-0004VD-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:14:35 -0500
Received: from g4a25.g.pppool.de ([80.185.74.37] helo=james.eecs.iu-bremen.de)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bEe-0004SW-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:13:53 -0500
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 3DEE5851E; Thu, 25 Mar 2004 21:13:51 +0100 (CET)
Resent-Date: Thu, 25 Mar 2004 21:13:51 +0100
Resent-Message-ID: <20040325201351.GB1447@iu-bremen.de>
Resent-To: entmib@ietf.org, schishol@nortelnetworks.com
X-Original-To: j.schoenwaelder@iu-bremen.de
Received: from localhost (localhost [127.0.0.1])
	by merkur.iu-bremen.de (Postfix) with ESMTP id DE561894F7
	for <j.schoenwaelder@iu-bremen.de>; Thu, 25 Mar 2004 21:11:10 +0100 (CET)
Received: from james.eecs.iu-bremen.de (G4a25.g.pppool.de [80.185.74.37])
	by merkur.iu-bremen.de (Postfix) with ESMTP id D844C8929E
	for <j.schoenwaelder@iu-bremen.de>; Thu, 25 Mar 2004 21:11:07 +0100 (CET)
Received: by james.eecs.iu-bremen.de (Postfix, from userid 1000)
	id 3E565851E; Thu, 25 Mar 2004 21:11:02 +0100 (CET)
Date: Thu, 25 Mar 2004 21:11:01 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Sharon Chisholm <schishol@nortelnetworks.com>
Cc: entmib@ietf.org
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Message-ID: <20040325201101.GA1447@iu-bremen.de>
Reply-To: j.schoenwaelder@iu-bremen.de
Mail-Followup-To: Sharon Chisholm <schishol@nortelnetworks.com>,
	entmib@ietf.org
References: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3549C09B853DD5119B540002A52CDD340A9D310C@zcard0ka.ca.nortel.com>
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by AMaViS 0.3.12pre8
Resent-Date: Thu, 25 Mar 2004 15:13:53 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 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>

On Thu, Mar 25, 2004 at 12:21:32PM -0500, Sharon Chisholm wrote:

> I don't remember anyone objecting to Bert's Post:
> 
> "In general, when a TC is clearly generic, then using the most 
> intuitive and generic name makes sense. In most cases, such a TC would 
> be better specified in a generic/independent document 
> (or at least a separate MIB module).
> 
> As soon as a TC is specific to some technology or to some WG, then 
> prefixing it with the wg or technology-specific acronym is the way to 
> go."
> 
> Are you suggesting this doesn't reflect working group consensus?

Sharon, you wrote the following:

> > We had previously agreed that if these state objects were not specific 
> > to physical entities then they should not have this prefix. We seem to 
> > be back to not agreeing that they are specific to physical entities.

I think this is not a fair summary of what Bert said (see the quote 
above) since you leave out more than half of his message which I 
consider important. And this is why I wrote:

> I am not sure how much agreement there has been on this issue

Clear now?

[I think my position on this issue is rather well documented now 
 and unless real new arguments come up, I really prefer to stay out 
 of this debate.]

/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



From entmib-admin@ietf.org  Thu Mar 25 15:30:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18920
	for <entmib-archive@lists.ietf.org>; Thu, 25 Mar 2004 15:30:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bUH-0004Y3-EB; Thu, 25 Mar 2004 15:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bTx-0004WY-2T
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:29:41 -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 PAA18899
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:29:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bTl-0005DA-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:29:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6bSu-0005Bc-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:28:37 -0500
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bSc-00059H-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:28:18 -0500
Received: from h-68-164-78-44.snvacaid.dynamic.covad.net ([68.164.78.44] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B6bSb-0005uI-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:28:17 -0800
Message-ID: <005a01c412a8$145a89a0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com> <5.2.0.9.2.20040325115604.023269f8@127.0.0.1>
Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
Date: Thu, 25 Mar 2004 12:30:57 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "David T. Perkins" <dperkins@dsperkins.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; <entmib@ietf.org>
> Sent: Thursday, March 25, 2004 12:04 PM
> Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
...
> Randy - it gets back to a fundamental question, which is
> "Is the ITU model and the specification for it worthwhile?"
> In the 10+ years that I have asked this question, I have NEVER
> gotten an answer. NEVER! In my own extensive analysis
> (which included creating both state and alarm MIB modules
> that are MUCH closer to the ITU models and specs than the
> documents created in the IETF), it just isn't forth it.
> Now, if someone would volunteer to show me an implementation
> where the benefits surpass the costs, I'll create time to
> learn from them, and change my tune. But pointing me to
> documents and manuals just doesn't cut it. Is this clear?
...

I think the difference here is in our understanding of "the ITU model".
It sounds like your understand it to mean *all* the stuff in X.731.
However, that's *not* how X.731 was meant to be used.   It provides
a core (Administrative/Usage/Operational states) of rather wide
applicability, and a bunch of other knobs and dials that an object
definer can use when appropriate.  I'm arguing to keep this thing
simple, i.e., not add anything (even from X.731) unless there is
a clear need for it.

So, if one were defining an object class using X.731, and only
operational state was meaningful, then objects of that class simply
wouldn't have administrative or usage states.  This maps well to
using the TCs in this MIB module.  From my perspective, this alone
would be useful.  When one has to do this in something
like the entity state table, it is not as nice.  The workaround of adding
additional "not applicable" values to the enumerations is ugly, but it's
the kind of ugliness we're accustomed to in the SNMP world.

Returning to your question: is having operational state worthwhile?
Absolutely, for the objects that need it.  Is having administrative state
worthwhile?  Same answer.  This is how X.731 was designed to be
used.

Randy



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


From exim@www1.ietf.org  Thu Mar 25 15:53:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17130
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 15:08:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b8t-0007Oj-RU
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:07:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PK7tbR028435
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:07:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b8t-0007Nn-4B; Thu, 25 Mar 2004 15:07:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6b6W-0005ZB-CS
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:05:28 -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 PAA16839
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:05:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b6T-0003xh-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:05:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6b5Y-0003wK-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:04:29 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6b5L-0003ue-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:04:15 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2PK4Cb28048;
	Thu, 25 Mar 2004 12:04:12 -0800
Message-Id: <5.2.0.9.2.20040325115604.023269f8@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 25 Mar 2004 12:04:04 -0800
To: "Randy Presuhn" <randy_presuhn@mindspring.com>, <entmib@ietf.org>
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
In-Reply-To: <002601c412a0$1f0f9a00$7f1afea9@oemcomputer>
References: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

Randy - it gets back to a fundamental question, which is 
"Is the ITU model and the specification for it worthwhile?"
In the 10+ years that I have asked this question, I have NEVER
gotten an answer. NEVER! In my own extensive analysis
(which included creating both state and alarm MIB modules
that are MUCH closer to the ITU models and specs than the
documents created in the IETF), it just isn't forth it.
Now, if someone would volunteer to show me an implementation
where the benefits surpass the costs, I'll create time to
learn from them, and change my tune. But pointing me to
documents and manuals just doesn't cut it. Is this clear?

At 11:33 AM 3/25/2004 -0800, Randy Presuhn wrote:
>Hi -
>
>> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
>> To: <entmib@ietf.org>
>> Sent: Thursday, March 25, 2004 8:33 AM
>> Subject: [Entmib] #355: OSI State to Something New Spectrum
>...
>> Co-Editor: As indicated, if we deviate too much we need to provide a mapping
>> back to the OSI model much like we have done with other state objects.
>
>Such deviation seems contrary to the whole point of developing this MIB
>module in the first place.  The more closely the semantics are aligned
>with the OSI ones (within the constraints imposed by the differing object
>models), the better.
>
>...
>> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
>> Sent: Thursday, March 25, 2004 10:34 AM
>> To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
>> Subject: RE: [Entmib] Entity comments
>>
>>
>> In hindsight (after having seen discussion over the last 2 days) and based
>> on:
>> <clip>
>> >
>> > 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.
>...
>
>I'd have no problem with EntState as a prefix for the TCs, although I'd
>also have no objection to leaving them un-prefixed, but in a separate
>MIB module in the same document.
>
>Randy

Regards,
/david t. perkins 


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



From exim@www1.ietf.org  Thu Mar 25 16:18:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18924
	for <entmib-archive@odin.ietf.org>; Thu, 25 Mar 2004 15:30:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bUL-0004Yo-Ic
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:30:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PKU5PG017500
	for entmib-archive@odin.ietf.org; Thu, 25 Mar 2004 15:30:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bUH-0004Y3-EB; Thu, 25 Mar 2004 15:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6bTx-0004WY-2T
	for entmib@optimus.ietf.org; Thu, 25 Mar 2004 15:29:41 -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 PAA18899
	for <entmib@ietf.org>; Thu, 25 Mar 2004 15:29:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bTl-0005DA-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:29:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6bSu-0005Bc-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:28:37 -0500
Received: from snipe.mail.pas.earthlink.net ([207.217.120.62])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6bSc-00059H-00
	for entmib@ietf.org; Thu, 25 Mar 2004 15:28:18 -0500
Received: from h-68-164-78-44.snvacaid.dynamic.covad.net ([68.164.78.44] helo=oemcomputer)
	by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B6bSb-0005uI-00
	for entmib@ietf.org; Thu, 25 Mar 2004 12:28:17 -0800
Message-ID: <005a01c412a8$145a89a0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340A9D3071@zcard0ka.ca.nortel.com> <5.2.0.9.2.20040325115604.023269f8@127.0.0.1>
Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
Date: Thu, 25 Mar 2004 12:30:57 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "David T. Perkins" <dperkins@dsperkins.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>; <entmib@ietf.org>
> Sent: Thursday, March 25, 2004 12:04 PM
> Subject: Re: [Entmib] #355: OSI State to Something New Spectrum
...
> Randy - it gets back to a fundamental question, which is
> "Is the ITU model and the specification for it worthwhile?"
> In the 10+ years that I have asked this question, I have NEVER
> gotten an answer. NEVER! In my own extensive analysis
> (which included creating both state and alarm MIB modules
> that are MUCH closer to the ITU models and specs than the
> documents created in the IETF), it just isn't forth it.
> Now, if someone would volunteer to show me an implementation
> where the benefits surpass the costs, I'll create time to
> learn from them, and change my tune. But pointing me to
> documents and manuals just doesn't cut it. Is this clear?
...

I think the difference here is in our understanding of "the ITU model".
It sounds like your understand it to mean *all* the stuff in X.731.
However, that's *not* how X.731 was meant to be used.   It provides
a core (Administrative/Usage/Operational states) of rather wide
applicability, and a bunch of other knobs and dials that an object
definer can use when appropriate.  I'm arguing to keep this thing
simple, i.e., not add anything (even from X.731) unless there is
a clear need for it.

So, if one were defining an object class using X.731, and only
operational state was meaningful, then objects of that class simply
wouldn't have administrative or usage states.  This maps well to
using the TCs in this MIB module.  From my perspective, this alone
would be useful.  When one has to do this in something
like the entity state table, it is not as nice.  The workaround of adding
additional "not applicable" values to the enumerations is ugly, but it's
the kind of ugliness we're accustomed to in the SNMP world.

Returning to your question: is having operational state worthwhile?
Absolutely, for the objects that need it.  Is having administrative state
worthwhile?  Same answer.  This is how X.731 was designed to be
used.

Randy



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



From entmib-admin@ietf.org  Mon Mar 29 09:51:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04975
	for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 09:51:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7y6O-00063O-Sq; Mon, 29 Mar 2004 09:51:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7y5v-00062l-91
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 09:50:31 -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 JAA04940
	for <entmib@ietf.org>; Mon, 29 Mar 2004 09:50:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7y5t-0005Jg-00
	for entmib@ietf.org; Mon, 29 Mar 2004 09:50:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7y4x-0005Cn-00
	for entmib@ietf.org; Mon, 29 Mar 2004 09:49:31 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7y4W-00054X-00
	for entmib@ietf.org; Mon, 29 Mar 2004 09:49:04 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TEmRV15683
	for <entmib@ietf.org>; Mon, 29 Mar 2004 09:48:28 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6LMX4>; Mon, 29 Mar 2004 09:48:28 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA422E3@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 09:48:19 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] Entity State MIB Status
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>

hi

<co-editor hat>

Ok, there were no objections to the proposed resolutions to the following
issues by the Friday date that Margaret had set, so I've moved these ones to
resolved: 306, 327

I think for most of the issues we are pretty close to rough consensus except
for those that are related to issue #355 "OSI State to Something New
Spectrum". I think we are in limbo until we agree on this and I think this
issue is the source of most frustration currently within the working group.
This relates to issues 308, 309, 312, 326, 330(editorial only I think) and
332.
	
There were a few issues where people restated their original opinions rather
than objecting to the proposed resolution. While I interpret this as
objecting to the proposed resolution, I may need to come back and ask some
annoying clarifying questions, so I would appreciate it if people could
respond to those.

</co-editor hat>

Thanks

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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


From exim@www1.ietf.org  Mon Mar 29 09:51:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04979
	for <entmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 09:51:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7y6P-00063o-45
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 09:51:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TEp1fr023282
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 09:51:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7y6O-00063O-Sq; Mon, 29 Mar 2004 09:51:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7y5v-00062l-91
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 09:50:31 -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 JAA04940
	for <entmib@ietf.org>; Mon, 29 Mar 2004 09:50:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7y5t-0005Jg-00
	for entmib@ietf.org; Mon, 29 Mar 2004 09:50:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7y4x-0005Cn-00
	for entmib@ietf.org; Mon, 29 Mar 2004 09:49:31 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7y4W-00054X-00
	for entmib@ietf.org; Mon, 29 Mar 2004 09:49:04 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TEmRV15683
	for <entmib@ietf.org>; Mon, 29 Mar 2004 09:48:28 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6LMX4>; Mon, 29 Mar 2004 09:48:28 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA422E3@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 09:48:19 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] Entity State MIB Status
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>

hi

<co-editor hat>

Ok, there were no objections to the proposed resolutions to the following
issues by the Friday date that Margaret had set, so I've moved these ones to
resolved: 306, 327

I think for most of the issues we are pretty close to rough consensus except
for those that are related to issue #355 "OSI State to Something New
Spectrum". I think we are in limbo until we agree on this and I think this
issue is the source of most frustration currently within the working group.
This relates to issues 308, 309, 312, 326, 330(editorial only I think) and
332.
	
There were a few issues where people restated their original opinions rather
than objecting to the proposed resolution. While I interpret this as
objecting to the proposed resolution, I may need to come back and ask some
annoying clarifying questions, so I would appreciate it if people could
respond to those.

</co-editor hat>

Thanks

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



From entmib-admin@ietf.org  Mon Mar 29 10:07:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06012
	for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 10:07:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yLv-000242-Eh; Mon, 29 Mar 2004 10:07:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yLh-0001zQ-Ch
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:06:49 -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 KAA05915
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:06:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yLf-0007Ym-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:06:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7yKn-0007Pp-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:05:54 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yK8-0007F5-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:05:12 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TF4YA08187
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:04:34 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6LNMJ>; Mon, 29 Mar 2004 10:04:35 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA42345@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:04:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #307: 'notSupported' is semantically wrong
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>

hi

<co-editor>
It seems the two sides of this has converged on 'unknown'
<co-editor>

<Sharon>
The only bit I had an opinion on was the English text 'is unable to
report'. If we go with 'unknown' in the DESCRIPTION, then I worry a bit
about the unknown to whom aspect. I guess text like 'A value of 'unknown'
means that the Foo state of this resource is not known to the management
services' might work.
</Sharon>

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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


From exim@www1.ietf.org  Mon Mar 29 10:07:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06014
	for <entmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 10:07:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yLv-00024a-JY
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 10:07:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TF73nS007950
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 10:07:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yLv-000242-Eh; Mon, 29 Mar 2004 10:07:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yLh-0001zQ-Ch
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:06:49 -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 KAA05915
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:06:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yLf-0007Ym-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:06:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7yKn-0007Pp-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:05:54 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yK8-0007F5-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:05:12 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TF4YA08187
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:04:34 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6LNMJ>; Mon, 29 Mar 2004 10:04:35 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA42345@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:04:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #307: 'notSupported' is semantically wrong
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>

hi

<co-editor>
It seems the two sides of this has converged on 'unknown'
<co-editor>

<Sharon>
The only bit I had an opinion on was the English text 'is unable to
report'. If we go with 'unknown' in the DESCRIPTION, then I worry a bit
about the unknown to whom aspect. I guess text like 'A value of 'unknown'
means that the Foo state of this resource is not known to the management
services' might work.
</Sharon>

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



From entmib-admin@ietf.org  Mon Mar 29 10:31:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08096
	for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 10:31:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yj8-00081N-Nk; Mon, 29 Mar 2004 10:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yiY-0007yj-SN
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:30:26 -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 KAA08055
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:30:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yiW-0003aD-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:30:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7yhZ-0003Px-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:29:26 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7ygf-0003B6-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:28:29 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TFRvA11499
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:27:57 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6L3F5>; Mon, 29 Mar 2004 10:27:58 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:27:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #322 -  Textual Convention Names (Prefix)
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>

hi

<co-editor>
I'm not sure if consensus is fully formed yet, but I wanted to test a view
that it seems to be leaning  in the direction of creating a separate MIB
within this ID to house to textual conventions who's prefix we have not yet
determined? Is that were people are or is more discussion required?
</co-editor>

<Sharon>
I think the term 'Entity' is too limiting if we agree we are going for a
more generic set of TCs. It occurs to be that we use the term 'resource' in
the Alarm MIB when we introduced the concept of a 'ResourceId' as well as
within the description clauses of the TCs in this MIB. Would a prefix of
'ResourceState' work?
</Sharon>

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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


From exim@www1.ietf.org  Mon Mar 29 10:31:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08118
	for <entmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 10:31:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yjA-00082Q-Od
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 10:31:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TFV449030876
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 10:31:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yj8-00081N-Nk; Mon, 29 Mar 2004 10:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7yiY-0007yj-SN
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:30:26 -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 KAA08055
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:30:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7yiW-0003aD-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:30:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7yhZ-0003Px-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:29:26 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7ygf-0003B6-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:28:29 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TFRvA11499
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:27:57 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6L3F5>; Mon, 29 Mar 2004 10:27:58 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:27:51 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #322 -  Textual Convention Names (Prefix)
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>

hi

<co-editor>
I'm not sure if consensus is fully formed yet, but I wanted to test a view
that it seems to be leaning  in the direction of creating a separate MIB
within this ID to house to textual conventions who's prefix we have not yet
determined? Is that were people are or is more discussion required?
</co-editor>

<Sharon>
I think the term 'Entity' is too limiting if we agree we are going for a
more generic set of TCs. It occurs to be that we use the term 'resource' in
the Alarm MIB when we introduced the concept of a 'ResourceId' as well as
within the description clauses of the TCs in this MIB. Would a prefix of
'ResourceState' work?
</Sharon>

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



From exim@www1.ietf.org  Mon Mar 29 10:57:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09868
	for <entmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 10:57:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7z8H-0001s1-74
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 10:57:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TFv1Z3007186
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 10:57:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7z8G-0001rc-O8; Mon, 29 Mar 2004 10:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7z7n-0001ql-Ea
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:56:31 -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 KAA09833
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:56:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7z7i-0007l5-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:56:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7z6m-0007bq-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:55:29 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7z5u-0007M0-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:54:34 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TFs2A15641
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:54:02 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6LPDB>; Mon, 29 Mar 2004 10:54:02 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA4243E@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:53:55 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #310: Alarm State Issues
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>

hi

<Sharon>
I'm fine with adding an 'underTest' bit. Building on what is there for
'underRepair' but fixing an odd typo and building on what Dave suggests
below, I propose the following
          " When no bits of this attribute are set, then there
            are no outstanding alarms against this resource and
            it is not under repair or test. If the value of under 
            repair is set, the resource is currently being repaired. 
            If the value of 'underTest' is set, then this resource
            is currently under test. If 'underTest' or 'underRepair' bits
            are set, depending on the implementation, may make the other 
            values in this bit string unreliable."

And in the description of the entStateAlarm object
	"If the value of the 'underTest' bit is set, then the entStateOper
       object MUST have a value of 'testing'."

</Sharon>      

David T. Perkins [dperkins@dsperkins.com]

" The resolution must include a value when the operState value is
'testing'. The resulting BITs should be something like:
unknown - status unknown (if set, then no other bits may be set)
underRepair - item under repair
underTest - item being tested
critial - one or more critical fault conditions present
major - one or more major fault conditions present
minor - one or more minor fault conditions present
warning - one or more warning fault conditions present
indeterminate - one or more indeterminate fault conditions 
present 
Note: when 'underRepair' or 'underTest' BITs are set, then
the manager should probably "discount" the importance
of any outstanding fault conditions
" 

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



From entmib-admin@ietf.org  Mon Mar 29 10:57:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09867
	for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 10:57:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7z8G-0001rc-O8; Mon, 29 Mar 2004 10:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7z7n-0001ql-Ea
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 10:56:31 -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 KAA09833
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:56:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7z7i-0007l5-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:56:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7z6m-0007bq-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:55:29 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7z5u-0007M0-00
	for entmib@ietf.org; Mon, 29 Mar 2004 10:54:34 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i2TFs2A15641
	for <entmib@ietf.org>; Mon, 29 Mar 2004 10:54:02 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GXT6LPDB>; Mon, 29 Mar 2004 10:54:02 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340AA4243E@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Mon, 29 Mar 2004 10:53:55 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] #310: Alarm State Issues
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>

hi

<Sharon>
I'm fine with adding an 'underTest' bit. Building on what is there for
'underRepair' but fixing an odd typo and building on what Dave suggests
below, I propose the following
          " When no bits of this attribute are set, then there
            are no outstanding alarms against this resource and
            it is not under repair or test. If the value of under 
            repair is set, the resource is currently being repaired. 
            If the value of 'underTest' is set, then this resource
            is currently under test. If 'underTest' or 'underRepair' bits
            are set, depending on the implementation, may make the other 
            values in this bit string unreliable."

And in the description of the entStateAlarm object
	"If the value of the 'underTest' bit is set, then the entStateOper
       object MUST have a value of 'testing'."

</Sharon>      

David T. Perkins [dperkins@dsperkins.com]

" The resolution must include a value when the operState value is
'testing'. The resulting BITs should be something like:
unknown - status unknown (if set, then no other bits may be set)
underRepair - item under repair
underTest - item being tested
critial - one or more critical fault conditions present
major - one or more major fault conditions present
minor - one or more minor fault conditions present
warning - one or more warning fault conditions present
indeterminate - one or more indeterminate fault conditions 
present 
Note: when 'underRepair' or 'underTest' BITs are set, then
the manager should probably "discount" the importance
of any outstanding fault conditions
" 

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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


From entmib-admin@ietf.org  Mon Mar 29 12:06:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12522
	for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 12:06:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80D3-0007CR-Kk; Mon, 29 Mar 2004 12:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80CX-00078Q-RI
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 12:05:30 -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 MAA12487
	for <entmib@ietf.org>; Mon, 29 Mar 2004 12:05:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80CW-0001jf-00
	for entmib@ietf.org; Mon, 29 Mar 2004 12:05:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B80BZ-0001bV-00
	for entmib@ietf.org; Mon, 29 Mar 2004 12:04:30 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80Ad-0001Tq-00
	for entmib@ietf.org; Mon, 29 Mar 2004 12:03:31 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2TH3Cb07618;
	Mon, 29 Mar 2004 09:03:12 -0800
Message-Id: <5.2.0.9.2.20040329081533.02290ba8@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 29 Mar 2004 09:01:57 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
In-Reply-To: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

X.731 defines a "generic" state module and defines attributes that
describe that state module. This was done so that "any" appropriate
object class (in SNMP, a table) that supported the state model
could support the attributes defined in X.731. Because there is
such a wide range of resources including both hardware to software,
the model in X.731 is quite general and not all of it is applicable
to each resource type. With OSI's GDMO specification format, it is
suppose to be easy to specify for an object class the specific
support and behavior of generic attributes. (And, the theory is
that it this approach eases writing management applications.)

With SNMP, "reusing" attributes is not done the same way as that
in GDMO. The definition of an SNMP MIB generally follows the approach of 
specifying the core set of attributes, getting operational experience,
and then extending it if needed.

So, addressing your proposal, it is not clear to me that a generic
model and attributes is useful. Perhaps if you could provide several
examples, it might help. Note that there are several ways to accomplish
the goal of application of a generic model, such as
to specify in an informational RFC a "design pattern" that can be
used by future MIB designers tailored for each application. This
is the approach used in most existing MIB modules. (However, the
design pattern is specified in the first usage of it instead
of a separate RFC.)


At 10:27 AM 3/29/2004 -0500, Sharon Chisholm wrote:
>hi
>
><co-editor>
>I'm not sure if consensus is fully formed yet, but I wanted to test a view
>that it seems to be leaning  in the direction of creating a separate MIB
>within this ID to house to textual conventions who's prefix we have not yet
>determined? Is that were people are or is more discussion required?
></co-editor>
>
><Sharon>
>I think the term 'Entity' is too limiting if we agree we are going for a
>more generic set of TCs. It occurs to be that we use the term 'resource' in
>the Alarm MIB when we introduced the concept of a 'ResourceId' as well as
>within the description clauses of the TCs in this MIB. Would a prefix of
>'ResourceState' work?
></Sharon>
>
>Sharon Chisholm
>Portfolio Integration
>Nortel Networks
>Ottawa, Canada

Regards,
/david t. perkins 


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


From exim@www1.ietf.org  Mon Mar 29 12:06:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12542
	for <entmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 12:06:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80D4-0007Cr-OV
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 12:06:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TH62nk027701
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 12:06:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80D3-0007CR-Kk; Mon, 29 Mar 2004 12:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80CX-00078Q-RI
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 12:05:30 -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 MAA12487
	for <entmib@ietf.org>; Mon, 29 Mar 2004 12:05:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80CW-0001jf-00
	for entmib@ietf.org; Mon, 29 Mar 2004 12:05:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B80BZ-0001bV-00
	for entmib@ietf.org; Mon, 29 Mar 2004 12:04:30 -0500
Received: from shell4.bayarea.net ([209.128.82.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80Ad-0001Tq-00
	for entmib@ietf.org; Mon, 29 Mar 2004 12:03:31 -0500
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1])
	by shell4.bayarea.net (8.11.6/8.11.6) with ESMTP id i2TH3Cb07618;
	Mon, 29 Mar 2004 09:03:12 -0800
Message-Id: <5.2.0.9.2.20040329081533.02290ba8@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 29 Mar 2004 09:01:57 -0800
To: "Sharon Chisholm" <schishol@nortelnetworks.com>, entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
In-Reply-To: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

HI,

X.731 defines a "generic" state module and defines attributes that
describe that state module. This was done so that "any" appropriate
object class (in SNMP, a table) that supported the state model
could support the attributes defined in X.731. Because there is
such a wide range of resources including both hardware to software,
the model in X.731 is quite general and not all of it is applicable
to each resource type. With OSI's GDMO specification format, it is
suppose to be easy to specify for an object class the specific
support and behavior of generic attributes. (And, the theory is
that it this approach eases writing management applications.)

With SNMP, "reusing" attributes is not done the same way as that
in GDMO. The definition of an SNMP MIB generally follows the approach of 
specifying the core set of attributes, getting operational experience,
and then extending it if needed.

So, addressing your proposal, it is not clear to me that a generic
model and attributes is useful. Perhaps if you could provide several
examples, it might help. Note that there are several ways to accomplish
the goal of application of a generic model, such as
to specify in an informational RFC a "design pattern" that can be
used by future MIB designers tailored for each application. This
is the approach used in most existing MIB modules. (However, the
design pattern is specified in the first usage of it instead
of a separate RFC.)


At 10:27 AM 3/29/2004 -0500, Sharon Chisholm wrote:
>hi
>
><co-editor>
>I'm not sure if consensus is fully formed yet, but I wanted to test a view
>that it seems to be leaning  in the direction of creating a separate MIB
>within this ID to house to textual conventions who's prefix we have not yet
>determined? Is that were people are or is more discussion required?
></co-editor>
>
><Sharon>
>I think the term 'Entity' is too limiting if we agree we are going for a
>more generic set of TCs. It occurs to be that we use the term 'resource' in
>the Alarm MIB when we introduced the concept of a 'ResourceId' as well as
>within the description clauses of the TCs in this MIB. Would a prefix of
>'ResourceState' work?
></Sharon>
>
>Sharon Chisholm
>Portfolio Integration
>Nortel Networks
>Ottawa, Canada

Regards,
/david t. perkins 


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



From entmib-admin@ietf.org  Mon Mar 29 16:49:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28645
	for <entmib-archive@lists.ietf.org>; Mon, 29 Mar 2004 16:49:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84cv-000789-0o; Mon, 29 Mar 2004 16:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84ce-00074z-4u
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 16:48:44 -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 QAA28617
	for <entmib@ietf.org>; Mon, 29 Mar 2004 16:48:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B84cc-0004g4-00
	for entmib@ietf.org; Mon, 29 Mar 2004 16:48:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B84bc-0004Xp-00
	for entmib@ietf.org; Mon, 29 Mar 2004 16:47:40 -0500
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B84ai-0004Q8-00
	for entmib@ietf.org; Mon, 29 Mar 2004 16:46:45 -0500
Received: from h-68-164-76-126.snvacaid.dynamic.covad.net ([68.164.76.126] helo=oemcomputer)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B84ai-0004Qm-00
	for entmib@ietf.org; Mon, 29 Mar 2004 13:46:44 -0800
Message-ID: <006a01c415d7$b8df2440$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.nortel.com>
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Mon, 29 Mar 2004 13:49:33 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: <entmib@ietf.org>
> Sent: Monday, March 29, 2004 7:27 AM
> Subject: [Entmib] #322 - Textual Convention Names (Prefix)
...
> <co-editor>
> I'm not sure if consensus is fully formed yet, but I wanted to test a view
> that it seems to be leaning  in the direction of creating a separate MIB
> within this ID to house to textual conventions who's prefix we have not yet
> determined? Is that were people are or is more discussion required?
> </co-editor>

This seems reasonable to me.
I agree with Dave Perkins' message in this thread that attribute
re-use in the SNMP world is much more difficult than in GDMO-land.
However, it is still possible, and I think the TCs that've been
crafted here do have good potential for giving us some useful re-use
within the constraints of the SNMP SMI.

> <Sharon>
> I think the term 'Entity' is too limiting if we agree we are going for a
> more generic set of TCs. It occurs to be that we use the term 'resource' in
> the Alarm MIB when we introduced the concept of a 'ResourceId' as well as
> within the description clauses of the TCs in this MIB. Would a prefix of
> 'ResourceState' work?
> </Sharon>

I'd strongly prefer "EntityState" as a prefix.  The word "entity"
is just the college and sci-fi equivalent of "thingie", so I don't see how it
would be limiting.

Randy



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


From exim@www1.ietf.org  Mon Mar 29 17:39:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28647
	for <entmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 16:49:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84cv-00078U-GP
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 16:49:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TLn1Wb027420
	for entmib-archive@odin.ietf.org; Mon, 29 Mar 2004 16:49:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84cv-000789-0o; Mon, 29 Mar 2004 16:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B84ce-00074z-4u
	for entmib@optimus.ietf.org; Mon, 29 Mar 2004 16:48:44 -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 QAA28617
	for <entmib@ietf.org>; Mon, 29 Mar 2004 16:48:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B84cc-0004g4-00
	for entmib@ietf.org; Mon, 29 Mar 2004 16:48:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B84bc-0004Xp-00
	for entmib@ietf.org; Mon, 29 Mar 2004 16:47:40 -0500
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B84ai-0004Q8-00
	for entmib@ietf.org; Mon, 29 Mar 2004 16:46:45 -0500
Received: from h-68-164-76-126.snvacaid.dynamic.covad.net ([68.164.76.126] helo=oemcomputer)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1B84ai-0004Qm-00
	for entmib@ietf.org; Mon, 29 Mar 2004 13:46:44 -0800
Message-ID: <006a01c415d7$b8df2440$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <entmib@ietf.org>
References: <3549C09B853DD5119B540002A52CDD340AA423AB@zcard0ka.ca.nortel.com>
Subject: Re: [Entmib] #322 -  Textual Convention Names (Prefix)
Date: Mon, 29 Mar 2004 13:49:33 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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>

Hi -

> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: <entmib@ietf.org>
> Sent: Monday, March 29, 2004 7:27 AM
> Subject: [Entmib] #322 - Textual Convention Names (Prefix)
...
> <co-editor>
> I'm not sure if consensus is fully formed yet, but I wanted to test a view
> that it seems to be leaning  in the direction of creating a separate MIB
> within this ID to house to textual conventions who's prefix we have not yet
> determined? Is that were people are or is more discussion required?
> </co-editor>

This seems reasonable to me.
I agree with Dave Perkins' message in this thread that attribute
re-use in the SNMP world is much more difficult than in GDMO-land.
However, it is still possible, and I think the TCs that've been
crafted here do have good potential for giving us some useful re-use
within the constraints of the SNMP SMI.

> <Sharon>
> I think the term 'Entity' is too limiting if we agree we are going for a
> more generic set of TCs. It occurs to be that we use the term 'resource' in
> the Alarm MIB when we introduced the concept of a 'ResourceId' as well as
> within the description clauses of the TCs in this MIB. Would a prefix of
> 'ResourceState' work?
> </Sharon>

I'd strongly prefer "EntityState" as a prefix.  The word "entity"
is just the college and sci-fi equivalent of "thingie", so I don't see how it
would be limiting.

Randy



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



From exim@www1.ietf.org  Tue Mar 30 18:52:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06855
	for <entmib-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:52:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riy-0006ZK-9t
	for entmib-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i12MM2He024451
	for entmib-archive@odin.ietf.org; Mon, 2 Feb 2004 17:22:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnmSA-0006MB-2c; Mon, 02 Feb 2004 17:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AnmS6-0006Kz-9p
	for entmib@optimus.ietf.org; Mon, 02 Feb 2004 17:21:58 -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 RAA18075
	for <entmib@ietf.org>; Mon, 2 Feb 2004 17:21:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnmS4-0005Iz-00
	for entmib@ietf.org; Mon, 02 Feb 2004 17:21:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnmRD-0005DA-00
	for entmib@ietf.org; Mon, 02 Feb 2004 17:21:03 -0500
Received: from smtp.exodus.net ([66.35.230.236])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnmQi-00055U-00; Mon, 02 Feb 2004 17:20:34 -0500
Received: from ms101.mail1.com (ms101.mail1.com [209.1.5.174])
	by smtp.exodus.net (8.12.8/8.12.8) with ESMTP id i12Nwtw3017189;
	Mon, 2 Feb 2004 15:59:01 -0800
Received: from ala-mrwtemp.thingmagic.com (unverified [66.228.91.169]) by accounting.espmail.com
 (Rockliffe SMTPRA 5.2.5) with ESMTP id <B0018133137@ms101.mail1.com>;
 Mon, 2 Feb 2004 14:19:47 -0800
Message-Id: <5.1.0.14.2.20040202171225.04dcbe18@ms101.mail1.com>
X-Sender: margaret@thingmagic.com@ms101.mail1.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 02 Feb 2004 17:15:10 -0500
To: iesg-secretary@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Cc: Bert Wijnen <bwijnen@lucent.com>, David Kessens <david.kessens@nokia.com>,
        entmib@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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
Subject: [Entmib] Publication Request: Entity MIB to Draft Standard
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>



I would like to request, on behalf of the Entity MIB WG that
draft-ietf-entmib-v3-04.txt be published as a Draft Standard.

The latest version of this document can be found at:

http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-04.txt

Our implementation report can be found at:

http://www.psg.com/~mrw/EntMIB-Impl-Report-Sep03.html

Please let me know if you need further information to process
this request.

Thanks,
Margaret Wasserman
Entity MIB (entmib) WG Chair


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



From exim@www1.ietf.org  Tue Mar 30 18:56:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08082
	for <entmib-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:56:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riw-0006ZK-1d
	for entmib-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1DM19c6001203
	for entmib-archive@odin.ietf.org; Fri, 13 Feb 2004 17:01:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArlMz-0000JE-MB; Fri, 13 Feb 2004 17:01:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ArlMC-0008Vd-43
	for entmib@optimus.ietf.org; Fri, 13 Feb 2004 17:00:20 -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 RAA09483
	for <entmib@ietf.org>; Fri, 13 Feb 2004 17:00:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArlM9-0001cp-00
	for entmib@ietf.org; Fri, 13 Feb 2004 17:00:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1ArlLH-0001Xi-00
	for entmib@ietf.org; Fri, 13 Feb 2004 16:59:24 -0500
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ArlKa-0001Q4-00
	for entmib@ietf.org; Fri, 13 Feb 2004 16:58:40 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1DLw9n21202
	for <entmib@ietf.org>; Fri, 13 Feb 2004 16:58:09 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1FNH8RAX>; Fri, 13 Feb 2004 16:58:10 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A2A7110@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] FW: [psg.com #310] AutoReply: Alarm State Issues
Date: Fri, 13 Feb 2004 16:58:09 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

Hi

All we need to do is refer to the definitions in the Alarm MIB and we should
be good.

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com] 
Sent: Friday, February 13, 2004 12:51 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]; entmib@ietf.org
Subject: Re: [Entmib] FW: [psg.com #310] AutoReply: Alarm State Issues


HI,

The Alarm Status (not state) brings up the unsettled definition of what is
"an alarm" and what is "clearing an alarm". The definition 
of an alarm MUST be specified for the TC and object to be useful. Or another
term must be used (and, of course, that term must be 
well defined).
I suggest that the term "alarm" be replaced by "fault". And the following be
used for the TC and object definitions:

  FaultStatus  ::=  TEXTUAL-CONVENTION                                
     STATUS         current                                           
     DESCRIPTION                                                      
          "The fault status, which is a bit string.

          When all the bits are zero, then no faults are present.

          The bit 'unavailable(0)' indicates that the fault status
          is unknown. When set, all bits other than 'underRepair(1)'
          must be zero. The 'underRepair(1)' indicates that the
          an item is under repair.

          The following bits are one when one or more faults of
          the perceived severity exist. The value is zero for
          a bit when there is no existing fault of the perceived
          severity. The bits and faults are:
             'critical(2)'
             'major(3)'
             'minor(4)'
             'warning(5)'
             'indeterminate(6)' (the perceived severity cannot
                                 be determined)

          The entity may continue to operate while a fault
          condition exists."
      SYNTAX         BITS                                        
              {
              unavailable(0),                                      
              underRepair(1),                                         
              critical(2),                                            
              major(3),                                               
              minor(4),                                               
              -- The following are not defined in X.733               
              warning(6),                                            
              indeterminate(7)                                       
              }                                         

  entStateFault OBJECT-TYPE                                         
        SYNTAX      FaultStatus                                     
        MAX-ACCESS  read-only                                       
        STATUS      current                                         
        DESCRIPTION                                                 
             "The fault status for this entity. It does not include 
             the faults raised on entities within its       
             containment hierarchy. These are entities that
             specify this entity as the value for object
             entPhysicalContainedIn directly and indirectly."
        ::= { entStateEntry 5 }                                     



At 02:44 PM 2/11/2004 -0500, Sharon Chisholm wrote:
>The following is the proposed resolution to entstate-310. The issue 
>will be considered closed pending the proposed edit being done.
>
>In the description of AlarmStatus replace
>
>"            When the
>             value of under repair is set, the resource is currently
>             being repaired."
>
>With
>
>"            When the
>             value of under repair is set, the resource is currently
>             being repaired, which depending on the implementation, 
>             may make the other values in this bit string unreliable."
>
>
>And replace
>
>"
>             When the value of 'alarmOutstanding' is set, one or more
>             alarms is active against the resource. The fault may or may
>             not be disabling. "
>
>With
>
>"
>             When the value of 'alarmOutstanding' is set, one or more
>             alarms is active against the resource. The fault may or may
>             not be disabling. This bit provides a high-level summary that 
>             can be used to determine whether or not to examine the rest of
>             the values."
>
>
>An explanation on the difference between raw and computed state, as 
>defined in section 2.1 was previously provided in relation to the 
>severity of alarms issue. No change appears to be necessary on that 
>particular issue.
>
>Sharon
>
>
>-----Original Message-----
>From: entity-state [mailto:rt+entity-state@rt.psg.com]
>Sent: Tuesday, January 13, 2004 2:58 AM
>To: Chisholm, Sharon [CAR:0S00:EXCH]
>Subject: [psg.com #310] AutoReply: Alarm State Issues
>
><clip>
>
>-----------------------------------------------------------------------
>--
>Keith McCloghrie [kzm@cisco.com]
>
>">   'underRepair' is an operState, not an AlarmState.
>> 
>>   from what perspective are the alarms classified as
>critical/major/minor/etc.
>>   e.g., does a particular fault have the same alarm status
>in 'coldStandby'
>>   as it does in 'hotStandby' or in 'providingService' ??  (hint: the
>answer
>>   is no!!).
>"
>
>    
>
>Juergen Schoenwaelder [j.schoenwaelder@iu-bremen.de]
>
>"6) AlarmStatus TC: I do not really understand the alarmOutStanding 
>bit. It seems like this is set whenever one of critical, major, minor, 
>warning and indeterminate is set. But if this is true, I think the bit 
>is not really terrible useful.
>
>Perhaps the bit has some other meaning. If so, please clarify."
Regards,
/david t. perkins 


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



From exim@www1.ietf.org  Tue Mar 30 18:57:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08192
	for <entmib-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:57:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riv-0006ZK-Rz
	for entmib-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i1IFnICI026594
	for entmib-archive@odin.ietf.org; Wed, 18 Feb 2004 10:49:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtTwr-0006u1-LR; Wed, 18 Feb 2004 10:49:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AtTvr-0006q9-6Q
	for entmib@optimus.ietf.org; Wed, 18 Feb 2004 10:48:15 -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 KAA23292
	for <entmib@ietf.org>; Wed, 18 Feb 2004 10:48:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtTvd-0004Pq-00
	for entmib@ietf.org; Wed, 18 Feb 2004 10:48:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AtTug-0004MR-00
	for entmib@ietf.org; Wed, 18 Feb 2004 10:47:03 -0500
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AtTtt-0004E7-00
	for entmib@ietf.org; Wed, 18 Feb 2004 10:46:13 -0500
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i1IFjXV02113
	for <entmib@ietf.org>; Wed, 18 Feb 2004 10:45:33 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <1FNH02F2>; Wed, 18 Feb 2004 10:45:27 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD340A38C647@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Date: Wed, 18 Feb 2004 10:45:25 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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
Subject: [Entmib] Entity State MIB Issue Summary & Status
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>

Hi

Ok, the new draft is out, but there are still three unresolved issues to
deal with.

Unresolved

308 Shutting Down Admin State 
310 Alarm State Issues open entity-state 
329 Usage State Scope 

Resolved

306 entStateTrap rename/oid to entStateNotifs 
307 'notSupported' is semantically wrong open  
309 Operational State Names and Concepts  
311 DateAndTimeOrZero ? open entity-state
312 Locked Admin State open entity-state 
322 Textual Convention Names (Prefix)  
325  OID Structure
326 Too many state 
327 More Editorial Issues  
328 Containment Hierach and entPhysicalContainedin 
330 Notification Varbinds 
332 More Standby State/Status Issues 
333 Relationship with Alarm MIB  
334 Table, Index Descriptions 
335 Notification Comments 

As always, the details can be found at http://rt.psg.com (ietf, ietf)

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada

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



