From mailman-owner@ietf.org  Mon Jul  1 05:52:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17312
	for <entmib-archive@odin.ietf.org>; Mon, 1 Jul 2002 05:52:16 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA23143
	for <entmib-archive@lists.ietf.org>; Mon, 1 Jul 2002 05:53:03 -0400 (EDT)
Date: Mon, 1 Jul 2002 05:53:03 -0400 (EDT)
Message-Id: <200207010953.FAA23143@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: entmib-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

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@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@lists.ietf.org


From entmib-admin@ietf.org  Thu Jul  4 07:41:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14788
	for <entmib-archive@odin.ietf.org>; Thu, 4 Jul 2002 07:41:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14002;
	Thu, 4 Jul 2002 07:41:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA13980
	for <entmib@optimus.ietf.org>; Thu, 4 Jul 2002 07:41:34 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14775
	for <entmib@ietf.org>; Thu, 4 Jul 2002 07:40:44 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g64Bf1O05522;
	Thu, 4 Jul 2002 07:41:02 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NYVB0W5K>; Thu, 4 Jul 2002 07:41:01 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Cc: duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com, kzm@cisco.com
Subject: RE: [Entmib] State, Status and URL info
Date: Thu, 4 Jul 2002 07:41:00 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

hi

I agree with Dave that the entity MIB needs state/status information.

When we discussed this last summer in London, I believe we
were thinking of a separate MIB with state extensions. Now
I'm beginning to think we might be more successful if we can
put a couple simple state objects in the existing MIB, especially
since it is currently being edited. By successful, I mean that 
the objects actually get implemented by managed elements and that
management tools are developed or enhanced to take advantage of
these objects - not that we define the perfect state MIB.

A minimalist approach would be to add an oper and admin state,
although a computed state based on the alarm state of the given
object and all of its subcomponents would be rather useful.

For those unfamiliar with the ITU model, here's a MIB I quickly
threw together last summer. It's rough, but it compiles.

-- Draft Version

ENTITY-STATE-MIB 

DEFINITIONS ::= BEGIN

   IMPORTS
       MODULE-IDENTITY, Unsigned32
           FROM SNMPv2-SMI
       TEXTUAL-CONVENTION, DisplayString, TruthValue
           FROM SNMPv2-TC;

   entityStateMIB MODULE-IDENTITY
       LAST-UPDATED "000004260000Z"
       ORGANIZATION "IETF Entity MIB Working Group"
       CONTACT-INFO
               "  "

       DESCRIPTION
               "This MIB defines a state extension to the entity MIB " 
       REVISION    "200103250000Z"
       DESCRIPTION
           ""     
       ::= { mib-2 XX } 
  -- Textual conventions
                      

   ItuAdminState  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the various possible administrative states 
               (ITU-T X.731)."
     SYNTAX         INTEGER
                       {
                        locked(1),
                        shuttingDown(2),
                        unlocked(3)
                       }


   ItuOperState  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of operational states 
               (ITU-T X.731)."
     SYNTAX         INTEGER
                       {
                        disabled(1),
                        enabled(2)
                       }


   ItuUnknownStatusValue  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the unknown status value to be true / false (ITU-T
X.731). 
               This indicates whether the  management system is able to
               maintain OAM communications with the managed entity or not."
     SYNTAX         TruthValue 
                    --  INTEGER {true(1), false(2)} 

   ItuUsageState  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of usage states
               (ITU-T X.731)."
     SYNTAX         INTEGER
                       {
                        idle(1),
                        active(2),
                        busy(3)
                       }


  ItuAlarmStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of alarm status
               (ITU-T X.731)."
           SYNTAX         INTEGER
                          {
                           under-repair(1),
                           critical(2),
                           major(3),
                           minor(4),
                           alarm-outstanding(5)
                          }


  ItuProcStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of procedural status
               (ITU-T X.731)."

           SYNTAX         INTEGER
                          {
                           initialization-required(1),
                           not-initialized(2),
                           initializing(3),
                           reporting(4),
                           terminating(5)
                          }


  ItuAvailStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of availability status
               (ITU-T X.731)."

           SYNTAX         INTEGER
                          {
                           in-test(1),
                           failed(2),
                           power-off(3),
                           off-line(4),
                           off-duty(5),
                           dependency(6),
                           degraded(7),
                           not-installed(8),
                           log-full(9)
                          }


  ItuControlStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of control status
               (ITU-T X.731)."

           SYNTAX         INTEGER
                          {
                           subject-to-test(1),
                           part-of-services-locked(2),
                           reserved-for-test(3),
                           suspended(4)
                          }


   ItuStandbyStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of standby status
               (IU-T X.731)."

           SYNTAX         INTEGER
                          {
                           hot-standby(1),
                           cold-standby(2),
                           providing-service(3)
                          }      

   entityStateTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF EntityStateEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of information about state/status of entities.
         "
    ::= { entityState 1 }
                          
                          
     entityStateEntry OBJECT-TYPE
        SYNTAX      EntityStateEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION ""
        AUGMENTS       { entityPhysicaEntry }
        ::= { entityStateTable 1 }

     EntityStateEntry ::= SEQUENCE {
         entityStateAdmin 	ItuAdminState,
         entityStateOper    ItuOperState,
         entityStateUnknownValue  ItuUnknownStatusValue,
         entityStateUsage  	ItuUsageState,
         entityStateAlarm	ItuAlarmStatus,
         entityStateProc    ItuProcStatus,
         entityStateAvail 	ItuAvailStatus, 
         entityStateControl ItuControlStatus,
         entityStateStandby ItuStandbyStatus,
         entityStateComputed INTEGER
        }                      
        
 entityStateAdmin OBJECT-TYPE
        SYNTAX      ItuAdminState
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 1 }     
        
  entityStateOper OBJECT-TYPE
        SYNTAX      ItuOperState
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 2 }  
 
  entityStateUnknownValue OBJECT-TYPE
        SYNTAX      ItuUnknownStatusValue
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 3 }     
        
  entityStateUsage OBJECT-TYPE
        SYNTAX      ItuUsageState
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 4 } 
        
  entityStateAlarm OBJECT-TYPE
        SYNTAX      ItuAlarmStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 5 }     
        
  entityStateProc OBJECT-TYPE
        SYNTAX      ItuProcStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 6 } 
        
 entityStateAvail OBJECT-TYPE
        SYNTAX      ItuAvailStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 7 }     
        
 entityStateControl OBJECT-TYPE
        SYNTAX      ItuControlStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 8 }         
                
 entityStateStandby OBJECT-TYPE
   		SYNTAX ItuStandbyStatus
   		MAX-ACCESS read-only
   		STATUS current
   		DESCRIPTION ""
   ::= { entityStateEntry 9 }         
        
 entityStateComputed OBJECT-TYPE
 		SYNTAX INTEGER    {   
 		  other (1),
 		  clear (2),
 		  warning (3),
 		  minor (4),
 		  major (5),
 		  critical (6)
 		}
 		MAX-ACCESS read-only
 		STATUS current
 		DESCRIPTION
 		"The state of this physical entity computed from its
 		raw states and the raw state of its child entities"
 ::= { entityStateEntry 10 }     
        

END              

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com]
Sent: Tuesday, April 09, 2002 2:22 PM
To: Keith McCloghrie; entmib@ietf.org
Cc: duane.baldwin@us.ibm.com; gop@us.ibm.com; dap@cisco.com;
kzm@cisco.com
Subject: Re: [Entmib] State, Status and URL info


HI,

The entity MIB for a long time has needed state and status info.
There are very complex models for this, and very simple models.
The below two objects seem a little too simple to me.

The third object looks like a "scratch pad object". It seems
very problematic when you consider how it would be used when
there are multiple managers.

Probably the best resources on this issue are the following
documents:
1)  Telcordia's GR-1093 - Generic State Requirements for Network Elements
    Issue 2, June 2000

2)  ISO/IEC 10164-2 (and ITU-T X.731) - State Management Functions
    August 1991

3)  ITU-T M.3100 - Generic Network Information Model 
    Version 2, 1995

Dave Sidor from the ITU-T community has made available the ITU-T documents
to the IETF community for no fee. But I do not know if Telcordia has
made available any of their documents, which have a fee, to the IETF
community for no fee.

In general, the IETF has a loosely defined generic model for state/status
that was (I believe) first used in the IF table based on admin state
and oper state. This model has been loosely copied to other MIB modules.

The ITU-T and Telcordia models are rigorously defined, and are different
from the IETF model in one important aspect. That is, in the IETF model,
the oper state "follows" (if possible) the the admin state; where in
the ITU-T model, the oper state is independent of the admin state.
The ITU-T model is richer than the IETF model. For example, it
supports redundancy. 


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


From daemon@optimus.ietf.org  Thu Jul  4 08:39:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14796
	for <entmib-archive@odin.ietf.org>; Thu, 4 Jul 2002 07:41:03 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA14026
	for entmib-archive@odin.ietf.org; Thu, 4 Jul 2002 07:41:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14002;
	Thu, 4 Jul 2002 07:41:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA13980
	for <entmib@optimus.ietf.org>; Thu, 4 Jul 2002 07:41:34 -0400 (EDT)
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14775
	for <entmib@ietf.org>; Thu, 4 Jul 2002 07:40:44 -0400 (EDT)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g64Bf1O05522;
	Thu, 4 Jul 2002 07:41:02 -0400 (EDT)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <NYVB0W5K>; Thu, 4 Jul 2002 07:41:01 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Cc: duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com, kzm@cisco.com
Subject: RE: [Entmib] State, Status and URL info
Date: Thu, 4 Jul 2002 07:41:00 -0400 
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

hi

I agree with Dave that the entity MIB needs state/status information.

When we discussed this last summer in London, I believe we
were thinking of a separate MIB with state extensions. Now
I'm beginning to think we might be more successful if we can
put a couple simple state objects in the existing MIB, especially
since it is currently being edited. By successful, I mean that 
the objects actually get implemented by managed elements and that
management tools are developed or enhanced to take advantage of
these objects - not that we define the perfect state MIB.

A minimalist approach would be to add an oper and admin state,
although a computed state based on the alarm state of the given
object and all of its subcomponents would be rather useful.

For those unfamiliar with the ITU model, here's a MIB I quickly
threw together last summer. It's rough, but it compiles.

-- Draft Version

ENTITY-STATE-MIB 

DEFINITIONS ::= BEGIN

   IMPORTS
       MODULE-IDENTITY, Unsigned32
           FROM SNMPv2-SMI
       TEXTUAL-CONVENTION, DisplayString, TruthValue
           FROM SNMPv2-TC;

   entityStateMIB MODULE-IDENTITY
       LAST-UPDATED "000004260000Z"
       ORGANIZATION "IETF Entity MIB Working Group"
       CONTACT-INFO
               "  "

       DESCRIPTION
               "This MIB defines a state extension to the entity MIB " 
       REVISION    "200103250000Z"
       DESCRIPTION
           ""     
       ::= { mib-2 XX } 
  -- Textual conventions
                      

   ItuAdminState  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the various possible administrative states 
               (ITU-T X.731)."
     SYNTAX         INTEGER
                       {
                        locked(1),
                        shuttingDown(2),
                        unlocked(3)
                       }


   ItuOperState  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of operational states 
               (ITU-T X.731)."
     SYNTAX         INTEGER
                       {
                        disabled(1),
                        enabled(2)
                       }


   ItuUnknownStatusValue  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the unknown status value to be true / false (ITU-T
X.731). 
               This indicates whether the  management system is able to
               maintain OAM communications with the managed entity or not."
     SYNTAX         TruthValue 
                    --  INTEGER {true(1), false(2)} 

   ItuUsageState  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of usage states
               (ITU-T X.731)."
     SYNTAX         INTEGER
                       {
                        idle(1),
                        active(2),
                        busy(3)
                       }


  ItuAlarmStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of alarm status
               (ITU-T X.731)."
           SYNTAX         INTEGER
                          {
                           under-repair(1),
                           critical(2),
                           major(3),
                           minor(4),
                           alarm-outstanding(5)
                          }


  ItuProcStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of procedural status
               (ITU-T X.731)."

           SYNTAX         INTEGER
                          {
                           initialization-required(1),
                           not-initialized(2),
                           initializing(3),
                           reporting(4),
                           terminating(5)
                          }


  ItuAvailStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of availability status
               (ITU-T X.731)."

           SYNTAX         INTEGER
                          {
                           in-test(1),
                           failed(2),
                           power-off(3),
                           off-line(4),
                           off-duty(5),
                           dependency(6),
                           degraded(7),
                           not-installed(8),
                           log-full(9)
                          }


  ItuControlStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of control status
               (ITU-T X.731)."

           SYNTAX         INTEGER
                          {
                           subject-to-test(1),
                           part-of-services-locked(2),
                           reserved-for-test(3),
                           suspended(4)
                          }


   ItuStandbyStatus  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the possible values of standby status
               (IU-T X.731)."

           SYNTAX         INTEGER
                          {
                           hot-standby(1),
                           cold-standby(2),
                           providing-service(3)
                          }      

   entityStateTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF EntityStateEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "A table of information about state/status of entities.
         "
    ::= { entityState 1 }
                          
                          
     entityStateEntry OBJECT-TYPE
        SYNTAX      EntityStateEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION ""
        AUGMENTS       { entityPhysicaEntry }
        ::= { entityStateTable 1 }

     EntityStateEntry ::= SEQUENCE {
         entityStateAdmin 	ItuAdminState,
         entityStateOper    ItuOperState,
         entityStateUnknownValue  ItuUnknownStatusValue,
         entityStateUsage  	ItuUsageState,
         entityStateAlarm	ItuAlarmStatus,
         entityStateProc    ItuProcStatus,
         entityStateAvail 	ItuAvailStatus, 
         entityStateControl ItuControlStatus,
         entityStateStandby ItuStandbyStatus,
         entityStateComputed INTEGER
        }                      
        
 entityStateAdmin OBJECT-TYPE
        SYNTAX      ItuAdminState
        MAX-ACCESS  read-write
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 1 }     
        
  entityStateOper OBJECT-TYPE
        SYNTAX      ItuOperState
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 2 }  
 
  entityStateUnknownValue OBJECT-TYPE
        SYNTAX      ItuUnknownStatusValue
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 3 }     
        
  entityStateUsage OBJECT-TYPE
        SYNTAX      ItuUsageState
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 4 } 
        
  entityStateAlarm OBJECT-TYPE
        SYNTAX      ItuAlarmStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 5 }     
        
  entityStateProc OBJECT-TYPE
        SYNTAX      ItuProcStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 6 } 
        
 entityStateAvail OBJECT-TYPE
        SYNTAX      ItuAvailStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 7 }     
        
 entityStateControl OBJECT-TYPE
        SYNTAX      ItuControlStatus
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION ""
        ::= { entityStateEntry 8 }         
                
 entityStateStandby OBJECT-TYPE
   		SYNTAX ItuStandbyStatus
   		MAX-ACCESS read-only
   		STATUS current
   		DESCRIPTION ""
   ::= { entityStateEntry 9 }         
        
 entityStateComputed OBJECT-TYPE
 		SYNTAX INTEGER    {   
 		  other (1),
 		  clear (2),
 		  warning (3),
 		  minor (4),
 		  major (5),
 		  critical (6)
 		}
 		MAX-ACCESS read-only
 		STATUS current
 		DESCRIPTION
 		"The state of this physical entity computed from its
 		raw states and the raw state of its child entities"
 ::= { entityStateEntry 10 }     
        

END              

Sharon

-----Original Message-----
From: David T. Perkins [mailto:dperkins@dsperkins.com]
Sent: Tuesday, April 09, 2002 2:22 PM
To: Keith McCloghrie; entmib@ietf.org
Cc: duane.baldwin@us.ibm.com; gop@us.ibm.com; dap@cisco.com;
kzm@cisco.com
Subject: Re: [Entmib] State, Status and URL info


HI,

The entity MIB for a long time has needed state and status info.
There are very complex models for this, and very simple models.
The below two objects seem a little too simple to me.

The third object looks like a "scratch pad object". It seems
very problematic when you consider how it would be used when
there are multiple managers.

Probably the best resources on this issue are the following
documents:
1)  Telcordia's GR-1093 - Generic State Requirements for Network Elements
    Issue 2, June 2000

2)  ISO/IEC 10164-2 (and ITU-T X.731) - State Management Functions
    August 1991

3)  ITU-T M.3100 - Generic Network Information Model 
    Version 2, 1995

Dave Sidor from the ITU-T community has made available the ITU-T documents
to the IETF community for no fee. But I do not know if Telcordia has
made available any of their documents, which have a fee, to the IETF
community for no fee.

In general, the IETF has a loosely defined generic model for state/status
that was (I believe) first used in the IF table based on admin state
and oper state. This model has been loosely copied to other MIB modules.

The ITU-T and Telcordia models are rigorously defined, and are different
from the IETF model in one important aspect. That is, in the IETF model,
the oper state "follows" (if possible) the the admin state; where in
the ITU-T model, the oper state is independent of the admin state.
The ITU-T model is richer than the IETF model. For example, it
supports redundancy. 


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



From entmib-admin@ietf.org  Thu Jul  4 13:36:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21741
	for <entmib-archive@odin.ietf.org>; Thu, 4 Jul 2002 13:36:10 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01992;
	Thu, 4 Jul 2002 13:36:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01964
	for <entmib@optimus.ietf.org>; Thu, 4 Jul 2002 13:36:47 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21737
	for <entmib@ietf.org>; Thu, 4 Jul 2002 13:35:58 -0400 (EDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g64HaG39003984;
	Thu, 4 Jul 2002 10:36:16 -0700 (PDT)
Received: from PC2.cisco.com (sjc-vpn1-987.cisco.com [10.21.99.219]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA10405; Thu, 4 Jul 2002 10:36:15 -0700 (PDT)
Message-Id: <5.1.0.14.2.20020704102020.026885e0@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 04 Jul 2002 10:33:28 -0700
To: "Sharon Chisholm" <schishol@nortelnetworks.com>
From: Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] State, Status and URL info
Cc: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
        kzm@cisco.com
In-Reply-To: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

At 04:41 AM 7/4/2002, Sharon Chisholm wrote:
>hi
>
>I agree with Dave that the entity MIB needs state/status information.

I have no objections to a separate RFC for this MIB. Some comments:

The entityStateTable should be a sparse augments, not AUGMENTS, because
an agent should not be required to support this level of
status information for every physical entity. EntityStateAdmin
should be MIN-ACCESS read-only, because not every physical
component can be controlled with the 3 enums
                        locked(1),
                        shuttingDown(2),
                        unlocked(3)
(2) looks like an operState, not an adminState. I would also replace
(1) and (3) with enabled and disabled.  Looking through the MIB,
there are lots of enum values that do not appear to be generally
applicable to all entPhysicalClass values either. (This just means
lots of use case text needs to be included in the RFC.)

Andy



>When we discussed this last summer in London, I believe we
>were thinking of a separate MIB with state extensions. Now
>I'm beginning to think we might be more successful if we can
>put a couple simple state objects in the existing MIB, especially
>since it is currently being edited. By successful, I mean that 
>the objects actually get implemented by managed elements and that
>management tools are developed or enhanced to take advantage of
>these objects - not that we define the perfect state MIB.
>
>A minimalist approach would be to add an oper and admin state,
>although a computed state based on the alarm state of the given
>object and all of its subcomponents would be rather useful.
>
>For those unfamiliar with the ITU model, here's a MIB I quickly
>threw together last summer. It's rough, but it compiles.
>
>-- Draft Version
>
>ENTITY-STATE-MIB 
>
>DEFINITIONS ::= BEGIN
>
>   IMPORTS
>       MODULE-IDENTITY, Unsigned32
>           FROM SNMPv2-SMI
>       TEXTUAL-CONVENTION, DisplayString, TruthValue
>           FROM SNMPv2-TC;
>
>   entityStateMIB MODULE-IDENTITY
>       LAST-UPDATED "000004260000Z"
>       ORGANIZATION "IETF Entity MIB Working Group"
>       CONTACT-INFO
>               "  "
>
>       DESCRIPTION
>               "This MIB defines a state extension to the entity MIB " 
>       REVISION    "200103250000Z"
>       DESCRIPTION
>           ""     
>       ::= { mib-2 XX } 
>  -- Textual conventions
>                      
>
>   ItuAdminState  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the various possible administrative states 
>               (ITU-T X.731)."
>     SYNTAX         INTEGER
>                       {
>                        locked(1),
>                        shuttingDown(2),
>                        unlocked(3)
>                       }
>
>
>   ItuOperState  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of operational states 
>               (ITU-T X.731)."
>     SYNTAX         INTEGER
>                       {
>                        disabled(1),
>                        enabled(2)
>                       }
>
>
>   ItuUnknownStatusValue  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the unknown status value to be true / false (ITU-T
>X.731). 
>               This indicates whether the  management system is able to
>               maintain OAM communications with the managed entity or not."
>     SYNTAX         TruthValue 
>                    --  INTEGER {true(1), false(2)} 
>
>   ItuUsageState  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of usage states
>               (ITU-T X.731)."
>     SYNTAX         INTEGER
>                       {
>                        idle(1),
>                        active(2),
>                        busy(3)
>                       }
>
>
>  ItuAlarmStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of alarm status
>               (ITU-T X.731)."
>           SYNTAX         INTEGER
>                          {
>                           under-repair(1),
>                           critical(2),
>                           major(3),
>                           minor(4),
>                           alarm-outstanding(5)
>                          }
>
>
>  ItuProcStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of procedural status
>               (ITU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           initialization-required(1),
>                           not-initialized(2),
>                           initializing(3),
>                           reporting(4),
>                           terminating(5)
>                          }
>
>
>  ItuAvailStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of availability status
>               (ITU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           in-test(1),
>                           failed(2),
>                           power-off(3),
>                           off-line(4),
>                           off-duty(5),
>                           dependency(6),
>                           degraded(7),
>                           not-installed(8),
>                           log-full(9)
>                          }
>
>
>  ItuControlStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of control status
>               (ITU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           subject-to-test(1),
>                           part-of-services-locked(2),
>                           reserved-for-test(3),
>                           suspended(4)
>                          }
>
>
>   ItuStandbyStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of standby status
>               (IU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           hot-standby(1),
>                           cold-standby(2),
>                           providing-service(3)
>                          }      
>
>   entityStateTable OBJECT-TYPE
>    SYNTAX      SEQUENCE OF EntityStateEntry
>    MAX-ACCESS  not-accessible
>    STATUS      current
>    DESCRIPTION
>        "A table of information about state/status of entities.
>         "
>    ::= { entityState 1 }
>                          
>                          
>     entityStateEntry OBJECT-TYPE
>        SYNTAX      EntityStateEntry
>        MAX-ACCESS  not-accessible
>        STATUS      current
>        DESCRIPTION ""
>        AUGMENTS       { entityPhysicaEntry }
>        ::= { entityStateTable 1 }
>
>     EntityStateEntry ::= SEQUENCE {
>         entityStateAdmin       ItuAdminState,
>         entityStateOper    ItuOperState,
>         entityStateUnknownValue  ItuUnknownStatusValue,
>         entityStateUsage       ItuUsageState,
>         entityStateAlarm       ItuAlarmStatus,
>         entityStateProc    ItuProcStatus,
>         entityStateAvail       ItuAvailStatus, 
>         entityStateControl ItuControlStatus,
>         entityStateStandby ItuStandbyStatus,
>         entityStateComputed INTEGER
>        }                      
>        
> entityStateAdmin OBJECT-TYPE
>        SYNTAX      ItuAdminState
>        MAX-ACCESS  read-write
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 1 }     
>        
>  entityStateOper OBJECT-TYPE
>        SYNTAX      ItuOperState
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 2 }  
> 
>  entityStateUnknownValue OBJECT-TYPE
>        SYNTAX      ItuUnknownStatusValue
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 3 }     
>        
>  entityStateUsage OBJECT-TYPE
>        SYNTAX      ItuUsageState
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 4 } 
>        
>  entityStateAlarm OBJECT-TYPE
>        SYNTAX      ItuAlarmStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 5 }     
>        
>  entityStateProc OBJECT-TYPE
>        SYNTAX      ItuProcStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 6 } 
>        
> entityStateAvail OBJECT-TYPE
>        SYNTAX      ItuAvailStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 7 }     
>        
> entityStateControl OBJECT-TYPE
>        SYNTAX      ItuControlStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 8 }         
>                
> entityStateStandby OBJECT-TYPE
>                SYNTAX ItuStandbyStatus
>                MAX-ACCESS read-only
>                STATUS current
>                DESCRIPTION ""
>   ::= { entityStateEntry 9 }         
>        
> entityStateComputed OBJECT-TYPE
>                SYNTAX INTEGER    {   
>                  other (1),
>                  clear (2),
>                  warning (3),
>                  minor (4),
>                  major (5),
>                  critical (6)
>                }
>                MAX-ACCESS read-only
>                STATUS current
>                DESCRIPTION
>                "The state of this physical entity computed from its
>                raw states and the raw state of its child entities"
> ::= { entityStateEntry 10 }     
>        
>
>END              
>
>Sharon
>
>-----Original Message-----
>From: David T. Perkins [mailto:dperkins@dsperkins.com]
>Sent: Tuesday, April 09, 2002 2:22 PM
>To: Keith McCloghrie; entmib@ietf.org
>Cc: duane.baldwin@us.ibm.com; gop@us.ibm.com; dap@cisco.com;
>kzm@cisco.com
>Subject: Re: [Entmib] State, Status and URL info
>
>
>HI,
>
>The entity MIB for a long time has needed state and status info.
>There are very complex models for this, and very simple models.
>The below two objects seem a little too simple to me.
>
>The third object looks like a "scratch pad object". It seems
>very problematic when you consider how it would be used when
>there are multiple managers.
>
>Probably the best resources on this issue are the following
>documents:
>1)  Telcordia's GR-1093 - Generic State Requirements for Network Elements
>    Issue 2, June 2000
>
>2)  ISO/IEC 10164-2 (and ITU-T X.731) - State Management Functions
>    August 1991
>
>3)  ITU-T M.3100 - Generic Network Information Model 
>    Version 2, 1995
>
>Dave Sidor from the ITU-T community has made available the ITU-T documents
>to the IETF community for no fee. But I do not know if Telcordia has
>made available any of their documents, which have a fee, to the IETF
>community for no fee.
>
>In general, the IETF has a loosely defined generic model for state/status
>that was (I believe) first used in the IF table based on admin state
>and oper state. This model has been loosely copied to other MIB modules.
>
>The ITU-T and Telcordia models are rigorously defined, and are different
>from the IETF model in one important aspect. That is, in the IETF model,
>the oper state "follows" (if possible) the the admin state; where in
>the ITU-T model, the oper state is independent of the admin state.
>The ITU-T model is richer than the IETF model. For example, it
>supports redundancy. 
>
>
>_______________________________________________
>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 daemon@optimus.ietf.org  Thu Jul  4 13:36:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21750
	for <entmib-archive@odin.ietf.org>; Thu, 4 Jul 2002 13:36:10 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA02008
	for entmib-archive@odin.ietf.org; Thu, 4 Jul 2002 13:36:59 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01992;
	Thu, 4 Jul 2002 13:36:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA01964
	for <entmib@optimus.ietf.org>; Thu, 4 Jul 2002 13:36:47 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21737
	for <entmib@ietf.org>; Thu, 4 Jul 2002 13:35:58 -0400 (EDT)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g64HaG39003984;
	Thu, 4 Jul 2002 10:36:16 -0700 (PDT)
Received: from PC2.cisco.com (sjc-vpn1-987.cisco.com [10.21.99.219]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA10405; Thu, 4 Jul 2002 10:36:15 -0700 (PDT)
Message-Id: <5.1.0.14.2.20020704102020.026885e0@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 04 Jul 2002 10:33:28 -0700
To: "Sharon Chisholm" <schishol@nortelnetworks.com>
From: Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] State, Status and URL info
Cc: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
        kzm@cisco.com
In-Reply-To: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

At 04:41 AM 7/4/2002, Sharon Chisholm wrote:
>hi
>
>I agree with Dave that the entity MIB needs state/status information.

I have no objections to a separate RFC for this MIB. Some comments:

The entityStateTable should be a sparse augments, not AUGMENTS, because
an agent should not be required to support this level of
status information for every physical entity. EntityStateAdmin
should be MIN-ACCESS read-only, because not every physical
component can be controlled with the 3 enums
                        locked(1),
                        shuttingDown(2),
                        unlocked(3)
(2) looks like an operState, not an adminState. I would also replace
(1) and (3) with enabled and disabled.  Looking through the MIB,
there are lots of enum values that do not appear to be generally
applicable to all entPhysicalClass values either. (This just means
lots of use case text needs to be included in the RFC.)

Andy



>When we discussed this last summer in London, I believe we
>were thinking of a separate MIB with state extensions. Now
>I'm beginning to think we might be more successful if we can
>put a couple simple state objects in the existing MIB, especially
>since it is currently being edited. By successful, I mean that 
>the objects actually get implemented by managed elements and that
>management tools are developed or enhanced to take advantage of
>these objects - not that we define the perfect state MIB.
>
>A minimalist approach would be to add an oper and admin state,
>although a computed state based on the alarm state of the given
>object and all of its subcomponents would be rather useful.
>
>For those unfamiliar with the ITU model, here's a MIB I quickly
>threw together last summer. It's rough, but it compiles.
>
>-- Draft Version
>
>ENTITY-STATE-MIB 
>
>DEFINITIONS ::= BEGIN
>
>   IMPORTS
>       MODULE-IDENTITY, Unsigned32
>           FROM SNMPv2-SMI
>       TEXTUAL-CONVENTION, DisplayString, TruthValue
>           FROM SNMPv2-TC;
>
>   entityStateMIB MODULE-IDENTITY
>       LAST-UPDATED "000004260000Z"
>       ORGANIZATION "IETF Entity MIB Working Group"
>       CONTACT-INFO
>               "  "
>
>       DESCRIPTION
>               "This MIB defines a state extension to the entity MIB " 
>       REVISION    "200103250000Z"
>       DESCRIPTION
>           ""     
>       ::= { mib-2 XX } 
>  -- Textual conventions
>                      
>
>   ItuAdminState  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the various possible administrative states 
>               (ITU-T X.731)."
>     SYNTAX         INTEGER
>                       {
>                        locked(1),
>                        shuttingDown(2),
>                        unlocked(3)
>                       }
>
>
>   ItuOperState  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of operational states 
>               (ITU-T X.731)."
>     SYNTAX         INTEGER
>                       {
>                        disabled(1),
>                        enabled(2)
>                       }
>
>
>   ItuUnknownStatusValue  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the unknown status value to be true / false (ITU-T
>X.731). 
>               This indicates whether the  management system is able to
>               maintain OAM communications with the managed entity or not."
>     SYNTAX         TruthValue 
>                    --  INTEGER {true(1), false(2)} 
>
>   ItuUsageState  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of usage states
>               (ITU-T X.731)."
>     SYNTAX         INTEGER
>                       {
>                        idle(1),
>                        active(2),
>                        busy(3)
>                       }
>
>
>  ItuAlarmStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of alarm status
>               (ITU-T X.731)."
>           SYNTAX         INTEGER
>                          {
>                           under-repair(1),
>                           critical(2),
>                           major(3),
>                           minor(4),
>                           alarm-outstanding(5)
>                          }
>
>
>  ItuProcStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of procedural status
>               (ITU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           initialization-required(1),
>                           not-initialized(2),
>                           initializing(3),
>                           reporting(4),
>                           terminating(5)
>                          }
>
>
>  ItuAvailStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of availability status
>               (ITU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           in-test(1),
>                           failed(2),
>                           power-off(3),
>                           off-line(4),
>                           off-duty(5),
>                           dependency(6),
>                           degraded(7),
>                           not-installed(8),
>                           log-full(9)
>                          }
>
>
>  ItuControlStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of control status
>               (ITU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           subject-to-test(1),
>                           part-of-services-locked(2),
>                           reserved-for-test(3),
>                           suspended(4)
>                          }
>
>
>   ItuStandbyStatus  ::=  TEXTUAL-CONVENTION
>     STATUS         current
>     DESCRIPTION
>             " Represents the possible values of standby status
>               (IU-T X.731)."
>
>           SYNTAX         INTEGER
>                          {
>                           hot-standby(1),
>                           cold-standby(2),
>                           providing-service(3)
>                          }      
>
>   entityStateTable OBJECT-TYPE
>    SYNTAX      SEQUENCE OF EntityStateEntry
>    MAX-ACCESS  not-accessible
>    STATUS      current
>    DESCRIPTION
>        "A table of information about state/status of entities.
>         "
>    ::= { entityState 1 }
>                          
>                          
>     entityStateEntry OBJECT-TYPE
>        SYNTAX      EntityStateEntry
>        MAX-ACCESS  not-accessible
>        STATUS      current
>        DESCRIPTION ""
>        AUGMENTS       { entityPhysicaEntry }
>        ::= { entityStateTable 1 }
>
>     EntityStateEntry ::= SEQUENCE {
>         entityStateAdmin       ItuAdminState,
>         entityStateOper    ItuOperState,
>         entityStateUnknownValue  ItuUnknownStatusValue,
>         entityStateUsage       ItuUsageState,
>         entityStateAlarm       ItuAlarmStatus,
>         entityStateProc    ItuProcStatus,
>         entityStateAvail       ItuAvailStatus, 
>         entityStateControl ItuControlStatus,
>         entityStateStandby ItuStandbyStatus,
>         entityStateComputed INTEGER
>        }                      
>        
> entityStateAdmin OBJECT-TYPE
>        SYNTAX      ItuAdminState
>        MAX-ACCESS  read-write
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 1 }     
>        
>  entityStateOper OBJECT-TYPE
>        SYNTAX      ItuOperState
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 2 }  
> 
>  entityStateUnknownValue OBJECT-TYPE
>        SYNTAX      ItuUnknownStatusValue
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 3 }     
>        
>  entityStateUsage OBJECT-TYPE
>        SYNTAX      ItuUsageState
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 4 } 
>        
>  entityStateAlarm OBJECT-TYPE
>        SYNTAX      ItuAlarmStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 5 }     
>        
>  entityStateProc OBJECT-TYPE
>        SYNTAX      ItuProcStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 6 } 
>        
> entityStateAvail OBJECT-TYPE
>        SYNTAX      ItuAvailStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 7 }     
>        
> entityStateControl OBJECT-TYPE
>        SYNTAX      ItuControlStatus
>        MAX-ACCESS  read-only
>        STATUS      current
>        DESCRIPTION ""
>        ::= { entityStateEntry 8 }         
>                
> entityStateStandby OBJECT-TYPE
>                SYNTAX ItuStandbyStatus
>                MAX-ACCESS read-only
>                STATUS current
>                DESCRIPTION ""
>   ::= { entityStateEntry 9 }         
>        
> entityStateComputed OBJECT-TYPE
>                SYNTAX INTEGER    {   
>                  other (1),
>                  clear (2),
>                  warning (3),
>                  minor (4),
>                  major (5),
>                  critical (6)
>                }
>                MAX-ACCESS read-only
>                STATUS current
>                DESCRIPTION
>                "The state of this physical entity computed from its
>                raw states and the raw state of its child entities"
> ::= { entityStateEntry 10 }     
>        
>
>END              
>
>Sharon
>
>-----Original Message-----
>From: David T. Perkins [mailto:dperkins@dsperkins.com]
>Sent: Tuesday, April 09, 2002 2:22 PM
>To: Keith McCloghrie; entmib@ietf.org
>Cc: duane.baldwin@us.ibm.com; gop@us.ibm.com; dap@cisco.com;
>kzm@cisco.com
>Subject: Re: [Entmib] State, Status and URL info
>
>
>HI,
>
>The entity MIB for a long time has needed state and status info.
>There are very complex models for this, and very simple models.
>The below two objects seem a little too simple to me.
>
>The third object looks like a "scratch pad object". It seems
>very problematic when you consider how it would be used when
>there are multiple managers.
>
>Probably the best resources on this issue are the following
>documents:
>1)  Telcordia's GR-1093 - Generic State Requirements for Network Elements
>    Issue 2, June 2000
>
>2)  ISO/IEC 10164-2 (and ITU-T X.731) - State Management Functions
>    August 1991
>
>3)  ITU-T M.3100 - Generic Network Information Model 
>    Version 2, 1995
>
>Dave Sidor from the ITU-T community has made available the ITU-T documents
>to the IETF community for no fee. But I do not know if Telcordia has
>made available any of their documents, which have a fee, to the IETF
>community for no fee.
>
>In general, the IETF has a loosely defined generic model for state/status
>that was (I believe) first used in the IF table based on admin state
>and oper state. This model has been loosely copied to other MIB modules.
>
>The ITU-T and Telcordia models are rigorously defined, and are different
>from the IETF model in one important aspect. That is, in the IETF model,
>the oper state "follows" (if possible) the the admin state; where in
>the ITU-T model, the oper state is independent of the admin state.
>The ITU-T model is richer than the IETF model. For example, it
>supports redundancy. 
>
>
>_______________________________________________
>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  Fri Jul  5 08:25:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21529
	for <entmib-archive@odin.ietf.org>; Fri, 5 Jul 2002 08:25:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28388;
	Fri, 5 Jul 2002 08:26:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28364
	for <entmib@optimus.ietf.org>; Fri, 5 Jul 2002 08:26:32 -0400 (EDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21519
	for <entmib@ietf.org>; Fri, 5 Jul 2002 08:25:40 -0400 (EDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g65CQIR0022469;
	Fri, 5 Jul 2002 14:26:18 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g65CQIS07055;
	Fri, 5 Jul 2002 14:26:18 +0200
Date: Fri, 5 Jul 2002 14:26:18 +0200
Message-Id: <200207051226.g65CQIS07055@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: schishol@nortelnetworks.com
CC: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
        kzm@cisco.com
In-reply-to: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
	(schishol@nortelnetworks.com)
Subject: Re: [Entmib] State, Status and URL info
References:  <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


>>>>> Sharon Chisholm writes:

Sharon> I agree with Dave that the entity MIB needs state/status
Sharon> information.

[...]

Sharon> For those unfamiliar with the ITU model, here's a MIB I
Sharon> quickly threw together last summer. It's rough, but it
Sharon> compiles.

   ItuUnknownStatusValue  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the unknown status value to be true / false 
	       (ITU-T X.731). 
               This indicates whether the  management system is able to
               maintain OAM communications with the managed entity or not."
     SYNTAX         TruthValue 
                    --  INTEGER {true(1), false(2)} 

Not sure I understand how this can be useful or implementable with the
average ENTITY-MIB implementation I have seen. But perhaps I just do
not understand the description at all.

I also believe that in the case of many interrelated state variables,
we need to be specific how the various values relate to each other.
For example, if a physical entity is cold-standby(2), can it also be
initializing(3) and busy(3)? (Since these are all different variables,
one can imagine such an entry in the state table.)

On a the more editorial side, I would suggest to replace the prefix
"entityState" with "entPhysicalState" since the ENTITY-MIB
distinguishes between physical and logical entities.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>



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


From daemon@optimus.ietf.org  Fri Jul  5 09:24:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21537
	for <entmib-archive@odin.ietf.org>; Fri, 5 Jul 2002 08:25:53 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA28409
	for entmib-archive@odin.ietf.org; Fri, 5 Jul 2002 08:26:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28388;
	Fri, 5 Jul 2002 08:26:33 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA28364
	for <entmib@optimus.ietf.org>; Fri, 5 Jul 2002 08:26:32 -0400 (EDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21519
	for <entmib@ietf.org>; Fri, 5 Jul 2002 08:25:40 -0400 (EDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g65CQIR0022469;
	Fri, 5 Jul 2002 14:26:18 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g65CQIS07055;
	Fri, 5 Jul 2002 14:26:18 +0200
Date: Fri, 5 Jul 2002 14:26:18 +0200
Message-Id: <200207051226.g65CQIS07055@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: schishol@nortelnetworks.com
CC: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
        kzm@cisco.com
In-reply-to: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
	(schishol@nortelnetworks.com)
Subject: Re: [Entmib] State, Status and URL info
References:  <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


>>>>> Sharon Chisholm writes:

Sharon> I agree with Dave that the entity MIB needs state/status
Sharon> information.

[...]

Sharon> For those unfamiliar with the ITU model, here's a MIB I
Sharon> quickly threw together last summer. It's rough, but it
Sharon> compiles.

   ItuUnknownStatusValue  ::=  TEXTUAL-CONVENTION
     STATUS         current
     DESCRIPTION
             " Represents the unknown status value to be true / false 
	       (ITU-T X.731). 
               This indicates whether the  management system is able to
               maintain OAM communications with the managed entity or not."
     SYNTAX         TruthValue 
                    --  INTEGER {true(1), false(2)} 

Not sure I understand how this can be useful or implementable with the
average ENTITY-MIB implementation I have seen. But perhaps I just do
not understand the description at all.

I also believe that in the case of many interrelated state variables,
we need to be specific how the various values relate to each other.
For example, if a physical entity is cold-standby(2), can it also be
initializing(3) and busy(3)? (Since these are all different variables,
one can imagine such an entry in the state table.)

On a the more editorial side, I would suggest to replace the prefix
"entityState" with "entPhysicalState" since the ENTITY-MIB
distinguishes between physical and logical entities.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>



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



From entmib-admin@ietf.org  Mon Jul  8 18:17:21 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14077
	for <entmib-archive@odin.ietf.org>; Mon, 8 Jul 2002 18:17:21 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA02000;
	Mon, 8 Jul 2002 18:18:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16881
	for <entmib@optimus.ietf.org>; Wed, 26 Jun 2002 06:41:04 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10199;
	Wed, 26 Jun 2002 06:40:17 -0400 (EDT)
Message-Id: <200206261040.GAA10199@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: entmib@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 26 Jun 2002 06:40:17 -0400
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-v3-00.txt
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Entity MIB Working Group of the IETF.

	Title		: Entity MIB (Version 3)
	Author(s)	: K. McCloghrie, A. Bierman
	Filename	: draft-ietf-entmib-v3-00.txt
	Pages		: 63
	Date		: 25-Jun-02
	
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for managing multiple
logical and physical entities managed by a single SNMP agent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-entmib-v3-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-v3-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020625141548.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-entmib-v3-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-entmib-v3-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020625141548.I-D@ietf.org>

--OtherAccess--

--NextPart--




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


From daemon@optimus.ietf.org  Mon Jul  8 18:17:22 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14087
	for <entmib-archive@odin.ietf.org>; Mon, 8 Jul 2002 18:17:21 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA02019
	for entmib-archive@odin.ietf.org; Mon, 8 Jul 2002 18:18:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA02000;
	Mon, 8 Jul 2002 18:18:05 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA16881
	for <entmib@optimus.ietf.org>; Wed, 26 Jun 2002 06:41:04 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10199;
	Wed, 26 Jun 2002 06:40:17 -0400 (EDT)
Message-Id: <200206261040.GAA10199@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: entmib@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Wed, 26 Jun 2002 06:40:17 -0400
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-v3-00.txt
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Entity MIB Working Group of the IETF.

	Title		: Entity MIB (Version 3)
	Author(s)	: K. McCloghrie, A. Bierman
	Filename	: draft-ietf-entmib-v3-00.txt
	Pages		: 63
	Date		: 25-Jun-02
	
This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community.  In
particular, it describes managed objects used for managing multiple
logical and physical entities managed by a single SNMP agent.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-entmib-v3-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-v3-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20020625141548.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-entmib-v3-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-entmib-v3-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20020625141548.I-D@ietf.org>

--OtherAccess--

--NextPart--




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



From entmib-admin@ietf.org  Tue Jul  9 17:22:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18029
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 17:22:50 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10265;
	Tue, 9 Jul 2002 17:23:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10237
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 17:23:34 -0400 (EDT)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18010
	for <entmib@ietf.org>; Tue, 9 Jul 2002 17:22:38 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g69LRS411960
	for <entmib@ietf.org>; Tue, 9 Jul 2002 16:27:28 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA14130
	for entmib@ietf.org; Tue, 9 Jul 2002 14:21:09 -0700 (PDT)
Date: Tue, 9 Jul 2002 14:21:09 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207092121.OAA14130@dorothy.bmc.com>
To: entmib@ietf.org
Subject: RE: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 7bit

Hi -

> Message-ID: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: entmib@ietf.org
> Cc: duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com, kzm@cisco.com
> Subject: RE: [Entmib] State, Status and URL info
> Date: Thu, 4 Jul 2002 07:41:00 -0400 
...
>   ItuAlarmStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of alarm status
>                (ITU-T X.731)."
>            SYNTAX         INTEGER
>                           {
>                            under-repair(1),
>                            critical(2),
>                            major(3),
>                            minor(4),
>                            alarm-outstanding(5)
>                           }

This one should probably be BITS rather than INTEGER in order to
match the semantics in X.731 (clause 8.1.2.1); note that the
corresponding syntax in X.721 is a set type.  This might be
problematic. CMIP allows specific members of a SET to be added
or removed, thus avoiding multi-manager race conditions that
can happen with read-write BITS.

(Consider the case where manager sets "under-repair" for a
minor alarm, and "critical" is asserted between the read and
the write.)

>   ItuProcStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of procedural status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            initialization-required(1),
>                            not-initialized(2),
>                            initializing(3),
>                            reporting(4),
>                            terminating(5)
>                           }

Same problem.  Should be BITS; semantics in X.731 clause 8.1.2.2;
note that the corresponding syntax in X.721 is a set type.

>   ItuAvailStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of availability status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            in-test(1),
>                            failed(2),
>                            power-off(3),
>                            off-line(4),
>                            off-duty(5),
>                            dependency(6),
>                            degraded(7),
>                            not-installed(8),
>                            log-full(9)
>                           }

Same problem.  Should be BITS; semantics in X.731 clause 8.1.2.3;
note that the corresponding syntax in X.721 is a set type.

>   ItuControlStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of control status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            subject-to-test(1),
>                            part-of-services-locked(2),
>                            reserved-for-test(3),
>                            suspended(4)
>                           }
...

Same problem.  Should be BITS; semantics in X.731 clause 8.1.2.4;
note that the corresponding syntax in X.721 is a set type.  This
might pose a problem; CMIP allows specific members of a SET to
be added or removed, thus avoiding multi-manager race conditions
that can happen with read-write BITS.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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


From daemon@optimus.ietf.org  Tue Jul  9 17:22:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18042
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 17:22:51 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA10281
	for entmib-archive@odin.ietf.org; Tue, 9 Jul 2002 17:23:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10265;
	Tue, 9 Jul 2002 17:23:35 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA10237
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 17:23:34 -0400 (EDT)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18010
	for <entmib@ietf.org>; Tue, 9 Jul 2002 17:22:38 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g69LRS411960
	for <entmib@ietf.org>; Tue, 9 Jul 2002 16:27:28 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA14130
	for entmib@ietf.org; Tue, 9 Jul 2002 14:21:09 -0700 (PDT)
Date: Tue, 9 Jul 2002 14:21:09 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207092121.OAA14130@dorothy.bmc.com>
To: entmib@ietf.org
Subject: RE: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 7bit

Hi -

> Message-ID: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.nortel.com>
> From: "Sharon Chisholm" <schishol@nortelnetworks.com>
> To: entmib@ietf.org
> Cc: duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com, kzm@cisco.com
> Subject: RE: [Entmib] State, Status and URL info
> Date: Thu, 4 Jul 2002 07:41:00 -0400 
...
>   ItuAlarmStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of alarm status
>                (ITU-T X.731)."
>            SYNTAX         INTEGER
>                           {
>                            under-repair(1),
>                            critical(2),
>                            major(3),
>                            minor(4),
>                            alarm-outstanding(5)
>                           }

This one should probably be BITS rather than INTEGER in order to
match the semantics in X.731 (clause 8.1.2.1); note that the
corresponding syntax in X.721 is a set type.  This might be
problematic. CMIP allows specific members of a SET to be added
or removed, thus avoiding multi-manager race conditions that
can happen with read-write BITS.

(Consider the case where manager sets "under-repair" for a
minor alarm, and "critical" is asserted between the read and
the write.)

>   ItuProcStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of procedural status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            initialization-required(1),
>                            not-initialized(2),
>                            initializing(3),
>                            reporting(4),
>                            terminating(5)
>                           }

Same problem.  Should be BITS; semantics in X.731 clause 8.1.2.2;
note that the corresponding syntax in X.721 is a set type.

>   ItuAvailStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of availability status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            in-test(1),
>                            failed(2),
>                            power-off(3),
>                            off-line(4),
>                            off-duty(5),
>                            dependency(6),
>                            degraded(7),
>                            not-installed(8),
>                            log-full(9)
>                           }

Same problem.  Should be BITS; semantics in X.731 clause 8.1.2.3;
note that the corresponding syntax in X.721 is a set type.

>   ItuControlStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of control status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            subject-to-test(1),
>                            part-of-services-locked(2),
>                            reserved-for-test(3),
>                            suspended(4)
>                           }
...

Same problem.  Should be BITS; semantics in X.731 clause 8.1.2.4;
note that the corresponding syntax in X.721 is a set type.  This
might pose a problem; CMIP allows specific members of a SET to
be added or removed, thus avoiding multi-manager race conditions
that can happen with read-write BITS.

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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



From entmib-admin@ietf.org  Tue Jul  9 17:34:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18697
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 17:34:58 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA12430;
	Tue, 9 Jul 2002 17:35:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA12404
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 17:35:39 -0400 (EDT)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18680
	for <entmib@ietf.org>; Tue, 9 Jul 2002 17:34:43 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g69LdYi16005
	for <entmib@ietf.org>; Tue, 9 Jul 2002 16:39:34 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA14160
	for entmib@ietf.org; Tue, 9 Jul 2002 14:33:14 -0700 (PDT)
Date: Tue, 9 Jul 2002 14:33:14 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207092133.OAA14160@dorothy.bmc.com>
To: entmib@ietf.org
Subject: RE: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 7bit

Hi -

> Message-Id: <5.1.0.14.2.20020704102020.026885e0@fedex.cisco.com>
> Date: Thu, 04 Jul 2002 10:33:28 -0700
> To: "Sharon Chisholm" <schishol@nortelnetworks.com>
> From: Andy Bierman <abierman@cisco.com>
> Subject: RE: [Entmib] State, Status and URL info
> Cc: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
>         kzm@cisco.com
> In-Reply-To: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.norte
>  l.com>
...
>                         locked(1),
>                         shuttingDown(2),
>                         unlocked(3)
> (2) looks like an operState, not an adminState. I would also replace
> (1) and (3) with enabled and disabled.  Looking through the MIB,
...

No, these really are administrative controls.  Setting the
attribute to locked(1) kicks off any users of the service.
Setting the attributed to shuttingDown(2) prevents new users
from using the service, but does not kick off the current
users.  This way both graceful and abrupt shutdown are possible.
When the last user leaves, shuttingDown transitions automatically
to locked. Figure 6 in X.731 shows the relationship between the
administrative and usage states.  (Figure 4 gives a combined state
diagram that's really quite nice, if a bit harder to digest.)

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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


From daemon@optimus.ietf.org  Tue Jul  9 17:34:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18703
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 17:34:58 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA12456
	for entmib-archive@odin.ietf.org; Tue, 9 Jul 2002 17:35:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA12430;
	Tue, 9 Jul 2002 17:35:40 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA12404
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 17:35:39 -0400 (EDT)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18680
	for <entmib@ietf.org>; Tue, 9 Jul 2002 17:34:43 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g69LdYi16005
	for <entmib@ietf.org>; Tue, 9 Jul 2002 16:39:34 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA14160
	for entmib@ietf.org; Tue, 9 Jul 2002 14:33:14 -0700 (PDT)
Date: Tue, 9 Jul 2002 14:33:14 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207092133.OAA14160@dorothy.bmc.com>
To: entmib@ietf.org
Subject: RE: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 7bit

Hi -

> Message-Id: <5.1.0.14.2.20020704102020.026885e0@fedex.cisco.com>
> Date: Thu, 04 Jul 2002 10:33:28 -0700
> To: "Sharon Chisholm" <schishol@nortelnetworks.com>
> From: Andy Bierman <abierman@cisco.com>
> Subject: RE: [Entmib] State, Status and URL info
> Cc: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
>         kzm@cisco.com
> In-Reply-To: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.norte
>  l.com>
...
>                         locked(1),
>                         shuttingDown(2),
>                         unlocked(3)
> (2) looks like an operState, not an adminState. I would also replace
> (1) and (3) with enabled and disabled.  Looking through the MIB,
...

No, these really are administrative controls.  Setting the
attribute to locked(1) kicks off any users of the service.
Setting the attributed to shuttingDown(2) prevents new users
from using the service, but does not kick off the current
users.  This way both graceful and abrupt shutdown are possible.
When the last user leaves, shuttingDown transitions automatically
to locked. Figure 6 in X.731 shows the relationship between the
administrative and usage states.  (Figure 4 gives a combined state
diagram that's really quite nice, if a bit harder to digest.)

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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



From entmib-admin@ietf.org  Tue Jul  9 18:47:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20737
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 18:47:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA17817;
	Tue, 9 Jul 2002 18:47:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA17785
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 18:47:58 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20730
	for <entmib@ietf.org>; Tue, 9 Jul 2002 18:47:04 -0400 (EDT)
Received: from fedex.cisco.com (IDENT:mirapoint@fedex.cisco.com [171.69.17.28])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g69MlM39023155;
	Tue, 9 Jul 2002 15:47:22 -0700 (PDT)
Received: from cisco.com (abierman-u10.cisco.com [128.107.164.52])
	by fedex.cisco.com (Mirapoint)
	with ESMTP id ACL19262;
	Tue, 9 Jul 2002 15:44:16 -0700 (PDT)
Message-ID: <3D2B67F9.E7958F35@cisco.com>
Date: Tue, 09 Jul 2002 15:47:21 -0700
From: Andy Bierman <abierman@cisco.com>
Organization: Cisco Systems, Inc.
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
CC: entmib@ietf.org
Subject: Re: [Entmib] State, Status and URL info
References: <200207092133.OAA14160@dorothy.bmc.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 8bit

Randy Presuhn wrote:
> 
> Hi -
> 
> > Message-Id: <5.1.0.14.2.20020704102020.026885e0@fedex.cisco.com>
> > Date: Thu, 04 Jul 2002 10:33:28 -0700
> > To: "Sharon Chisholm" <schishol@nortelnetworks.com>
> > From: Andy Bierman <abierman@cisco.com>
> > Subject: RE: [Entmib] State, Status and URL info
> > Cc: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
> >         kzm@cisco.com
> > In-Reply-To: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.norte
> >  l.com>
> ...
> >                         locked(1),
> >                         shuttingDown(2),
> >                         unlocked(3)
> > (2) looks like an operState, not an adminState. I would also replace
> > (1) and (3) with enabled and disabled.  Looking through the MIB,
> ...
> 
> No, these really are administrative controls.  Setting the
> attribute to locked(1) kicks off any users of the service.
> Setting the attributed to shuttingDown(2) prevents new users
> from using the service, but does not kick off the current
> users.  This way both graceful and abrupt shutdown are possible.
> When the last user leaves, shuttingDown transitions automatically
> to locked. Figure 6 in X.731 shows the relationship between the
> administrative and usage states.  (Figure 4 gives a combined state
> diagram that's really quite nice, if a bit harder to digest.)

Well the enum names are misleading.  You mention that these
are administrative states applied to services. In that case,
how does this object (maybe the whole MIB) apply to
physical entities?  It sounds like this should apply to
logical entities.

> 
>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  1-3141
>  randy_presuhn@bmc.com  2141 North First Street
>  Tel: +1 408 546-1006   San José, California 95131  USA
>  ------------------------------------------------------
>  My opinions and BMC's are independent variables.
>  ------------------------------------------------------
> 
> _______________________________________________
> Entmib mailing list
> Entmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/entmib

Andy

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


From daemon@optimus.ietf.org  Tue Jul  9 18:47:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20743
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 18:47:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA17837
	for entmib-archive@odin.ietf.org; Tue, 9 Jul 2002 18:48:08 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA17817;
	Tue, 9 Jul 2002 18:47:59 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA17785
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 18:47:58 -0400 (EDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20730
	for <entmib@ietf.org>; Tue, 9 Jul 2002 18:47:04 -0400 (EDT)
Received: from fedex.cisco.com (IDENT:mirapoint@fedex.cisco.com [171.69.17.28])
	by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g69MlM39023155;
	Tue, 9 Jul 2002 15:47:22 -0700 (PDT)
Received: from cisco.com (abierman-u10.cisco.com [128.107.164.52])
	by fedex.cisco.com (Mirapoint)
	with ESMTP id ACL19262;
	Tue, 9 Jul 2002 15:44:16 -0700 (PDT)
Message-ID: <3D2B67F9.E7958F35@cisco.com>
Date: Tue, 09 Jul 2002 15:47:21 -0700
From: Andy Bierman <abierman@cisco.com>
Organization: Cisco Systems, Inc.
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
CC: entmib@ietf.org
Subject: Re: [Entmib] State, Status and URL info
References: <200207092133.OAA14160@dorothy.bmc.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 8bit

Randy Presuhn wrote:
> 
> Hi -
> 
> > Message-Id: <5.1.0.14.2.20020704102020.026885e0@fedex.cisco.com>
> > Date: Thu, 04 Jul 2002 10:33:28 -0700
> > To: "Sharon Chisholm" <schishol@nortelnetworks.com>
> > From: Andy Bierman <abierman@cisco.com>
> > Subject: RE: [Entmib] State, Status and URL info
> > Cc: entmib@ietf.org, duane.baldwin@us.ibm.com, gop@us.ibm.com, dap@cisco.com,
> >         kzm@cisco.com
> > In-Reply-To: <3549C09B853DD5119B540002A52CDD3403FA7CEE@zcard0ka.ca.norte
> >  l.com>
> ...
> >                         locked(1),
> >                         shuttingDown(2),
> >                         unlocked(3)
> > (2) looks like an operState, not an adminState. I would also replace
> > (1) and (3) with enabled and disabled.  Looking through the MIB,
> ...
> 
> No, these really are administrative controls.  Setting the
> attribute to locked(1) kicks off any users of the service.
> Setting the attributed to shuttingDown(2) prevents new users
> from using the service, but does not kick off the current
> users.  This way both graceful and abrupt shutdown are possible.
> When the last user leaves, shuttingDown transitions automatically
> to locked. Figure 6 in X.731 shows the relationship between the
> administrative and usage states.  (Figure 4 gives a combined state
> diagram that's really quite nice, if a bit harder to digest.)

Well the enum names are misleading.  You mention that these
are administrative states applied to services. In that case,
how does this object (maybe the whole MIB) apply to
physical entities?  It sounds like this should apply to
logical entities.

> 
>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  1-3141
>  randy_presuhn@bmc.com  2141 North First Street
>  Tel: +1 408 546-1006   San José, California 95131  USA
>  ------------------------------------------------------
>  My opinions and BMC's are independent variables.
>  ------------------------------------------------------
> 
> _______________________________________________
> Entmib mailing list
> Entmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/entmib

Andy

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



From entmib-admin@ietf.org  Tue Jul  9 19:04:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21092
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 19:04:00 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19126;
	Tue, 9 Jul 2002 19:04:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19101
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 19:04:48 -0400 (EDT)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21083
	for <entmib@ietf.org>; Tue, 9 Jul 2002 19:03:55 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g69N8pA18343
	for <entmib@ietf.org>; Tue, 9 Jul 2002 18:08:51 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA14648
	for entmib@ietf.org; Tue, 9 Jul 2002 16:02:31 -0700 (PDT)
Date: Tue, 9 Jul 2002 16:02:31 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207092302.QAA14648@dorothy.bmc.com>
To: entmib@ietf.org
Subject: Re: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 8bit

Hi -

> Message-ID: <3D2B67F9.E7958F35@cisco.com>
> Date: Tue, 09 Jul 2002 15:47:21 -0700
> From: Andy Bierman <abierman@cisco.com>
> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
> Cc: entmib@ietf.org
> Subject: Re: [Entmib] State, Status and URL info
> References: <200207092133.OAA14160@dorothy.bmc.com>
...
> Well the enum names are misleading.  You mention that these
> are administrative states applied to services. In that case,
> how does this object (maybe the whole MIB) apply to
> physical entities?  It sounds like this should apply to
> logical entities.
...

I think X.731 clause 7.1 sums it up nicely:

| Three primary factors affect the management state of a managed
| object with regard to its corresponding rsources' availability.
| Some managed objects may not be affected by all three of these
| factors.  These are
|
|  - operability: whether or not the resource is physically
|    installed and working, if applicable;
|  - usage: whether or not the resource is actively in use at
|    a specific instant, and if so, whether or not it has spare
|    capacity for additional users at that instant.  A resource
|    is said to be "in use" when it has received one or more
|    requests for service that it has not yet completed or
|    otherwise discharged, or when some part of its capacity
|    has been allocated, and not yet recalimed, as a result of
|    a previous service request;
|  - administration: permission to use or prohibition against
|    using the resource, imposed through the management services.
|
| The state of a managed object does not affect its ability to
| respond to management operations.

As a practical matter, this means that these may be applicable
to both physical and logical entities, and there will be some
entities to which some of these may not apply.  I agree with
your earlier comment about the augmentation being sparse.

This is one of the reasons why X.731 clause 8.1.3 defines the
"state" attribute group.  This lets a CMIP manager ask an
object to return "whatever your state attribute(s) are".

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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


From daemon@optimus.ietf.org  Tue Jul  9 19:04:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21099
	for <entmib-archive@odin.ietf.org>; Tue, 9 Jul 2002 19:04:01 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA19145
	for entmib-archive@odin.ietf.org; Tue, 9 Jul 2002 19:04:53 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19126;
	Tue, 9 Jul 2002 19:04:49 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA19101
	for <entmib@optimus.ietf.org>; Tue, 9 Jul 2002 19:04:48 -0400 (EDT)
Received: from babbler.bmc.com (camaro.bmc.com [198.207.223.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21083
	for <entmib@ietf.org>; Tue, 9 Jul 2002 19:03:55 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g69N8pA18343
	for <entmib@ietf.org>; Tue, 9 Jul 2002 18:08:51 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id QAA14648
	for entmib@ietf.org; Tue, 9 Jul 2002 16:02:31 -0700 (PDT)
Date: Tue, 9 Jul 2002 16:02:31 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207092302.QAA14648@dorothy.bmc.com>
To: entmib@ietf.org
Subject: Re: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 8bit

Hi -

> Message-ID: <3D2B67F9.E7958F35@cisco.com>
> Date: Tue, 09 Jul 2002 15:47:21 -0700
> From: Andy Bierman <abierman@cisco.com>
> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
> Cc: entmib@ietf.org
> Subject: Re: [Entmib] State, Status and URL info
> References: <200207092133.OAA14160@dorothy.bmc.com>
...
> Well the enum names are misleading.  You mention that these
> are administrative states applied to services. In that case,
> how does this object (maybe the whole MIB) apply to
> physical entities?  It sounds like this should apply to
> logical entities.
...

I think X.731 clause 7.1 sums it up nicely:

| Three primary factors affect the management state of a managed
| object with regard to its corresponding rsources' availability.
| Some managed objects may not be affected by all three of these
| factors.  These are
|
|  - operability: whether or not the resource is physically
|    installed and working, if applicable;
|  - usage: whether or not the resource is actively in use at
|    a specific instant, and if so, whether or not it has spare
|    capacity for additional users at that instant.  A resource
|    is said to be "in use" when it has received one or more
|    requests for service that it has not yet completed or
|    otherwise discharged, or when some part of its capacity
|    has been allocated, and not yet recalimed, as a result of
|    a previous service request;
|  - administration: permission to use or prohibition against
|    using the resource, imposed through the management services.
|
| The state of a managed object does not affect its ability to
| respond to management operations.

As a practical matter, this means that these may be applicable
to both physical and logical entities, and there will be some
entities to which some of these may not apply.  I agree with
your earlier comment about the augmentation being sparse.

This is one of the reasons why X.731 clause 8.1.3 defines the
"state" attribute group.  This lets a CMIP manager ask an
object to return "whatever your state attribute(s) are".

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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



From entmib-admin@ietf.org  Wed Jul 10 02:50:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22946
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 02:50:54 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01146;
	Wed, 10 Jul 2002 02:51:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01122
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 02:51:39 -0400 (EDT)
Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22940
	for <entmib@ietf.org>; Wed, 10 Jul 2002 02:50:45 -0400 (EDT)
Received: from host.dsperkins.com (shell4.BAYAREA.NET [209.128.82.1])
	by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id XAA26326
	for <entmib@ietf.org>; Tue, 9 Jul 2002 23:51:36 -0700 (PDT)
	(envelope-from dperkins@dsperkins.com)
Message-Id: <5.1.0.14.2.20020709234620.03a69a70@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 09 Jul 2002 23:50:42 -0700
To: entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] State, Status and URL info
In-Reply-To: <200207092302.QAA14648@dorothy.bmc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

HI,

One of the biggest differences between the ITU model and the "IETF model"
is that in the IETF model the "oper state" follows the admin state,
where in the ITU model the oper state is independent of the admin state.

Resolving the differences (or at least documenting them) between the
ITU and the IETF models (including the physical models (as specified
in M.3100), I believe are the most important and would provide a
great benefit to the SNMP community. But I repeat myself. Sorry.

At 04:02 PM 7/9/2002 -0700, Randy Presuhn wrote:
>Hi -
>
>> Message-ID: <3D2B67F9.E7958F35@cisco.com>
>> Date: Tue, 09 Jul 2002 15:47:21 -0700
>> From: Andy Bierman <abierman@cisco.com>
>> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
>> Cc: entmib@ietf.org
>> Subject: Re: [Entmib] State, Status and URL info
>> References: <200207092133.OAA14160@dorothy.bmc.com>
>...
>> Well the enum names are misleading.  You mention that these
>> are administrative states applied to services. In that case,
>> how does this object (maybe the whole MIB) apply to
>> physical entities?  It sounds like this should apply to
>> logical entities.
>...
>
>I think X.731 clause 7.1 sums it up nicely:
>
>| Three primary factors affect the management state of a managed
>| object with regard to its corresponding rsources' availability.
>| Some managed objects may not be affected by all three of these
>| factors.  These are
>|
>|  - operability: whether or not the resource is physically
>|    installed and working, if applicable;
>|  - usage: whether or not the resource is actively in use at
>|    a specific instant, and if so, whether or not it has spare
>|    capacity for additional users at that instant.  A resource
>|    is said to be "in use" when it has received one or more
>|    requests for service that it has not yet completed or
>|    otherwise discharged, or when some part of its capacity
>|    has been allocated, and not yet recalimed, as a result of
>|    a previous service request;
>|  - administration: permission to use or prohibition against
>|    using the resource, imposed through the management services.
>|
>| The state of a managed object does not affect its ability to
>| respond to management operations.
>
>As a practical matter, this means that these may be applicable
>to both physical and logical entities, and there will be some
>entities to which some of these may not apply.  I agree with
>your earlier comment about the augmentation being sparse.
>
>This is one of the reasons why X.731 clause 8.1.3 defines the
>"state" attribute group.  This lets a CMIP manager ask an
>object to return "whatever your state attribute(s) are".

Regards,
/david t. perkins


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


From daemon@optimus.ietf.org  Wed Jul 10 02:50:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22955
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 02:50:55 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA01170
	for entmib-archive@odin.ietf.org; Wed, 10 Jul 2002 02:51:48 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01146;
	Wed, 10 Jul 2002 02:51:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id CAA01122
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 02:51:39 -0400 (EDT)
Received: from postman.bayarea.net (postman.bayarea.net [205.219.84.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22940
	for <entmib@ietf.org>; Wed, 10 Jul 2002 02:50:45 -0400 (EDT)
Received: from host.dsperkins.com (shell4.BAYAREA.NET [209.128.82.1])
	by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id XAA26326
	for <entmib@ietf.org>; Tue, 9 Jul 2002 23:51:36 -0700 (PDT)
	(envelope-from dperkins@dsperkins.com)
Message-Id: <5.1.0.14.2.20020709234620.03a69a70@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 09 Jul 2002 23:50:42 -0700
To: entmib@ietf.org
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] State, Status and URL info
In-Reply-To: <200207092302.QAA14648@dorothy.bmc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

HI,

One of the biggest differences between the ITU model and the "IETF model"
is that in the IETF model the "oper state" follows the admin state,
where in the ITU model the oper state is independent of the admin state.

Resolving the differences (or at least documenting them) between the
ITU and the IETF models (including the physical models (as specified
in M.3100), I believe are the most important and would provide a
great benefit to the SNMP community. But I repeat myself. Sorry.

At 04:02 PM 7/9/2002 -0700, Randy Presuhn wrote:
>Hi -
>
>> Message-ID: <3D2B67F9.E7958F35@cisco.com>
>> Date: Tue, 09 Jul 2002 15:47:21 -0700
>> From: Andy Bierman <abierman@cisco.com>
>> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
>> Cc: entmib@ietf.org
>> Subject: Re: [Entmib] State, Status and URL info
>> References: <200207092133.OAA14160@dorothy.bmc.com>
>...
>> Well the enum names are misleading.  You mention that these
>> are administrative states applied to services. In that case,
>> how does this object (maybe the whole MIB) apply to
>> physical entities?  It sounds like this should apply to
>> logical entities.
>...
>
>I think X.731 clause 7.1 sums it up nicely:
>
>| Three primary factors affect the management state of a managed
>| object with regard to its corresponding rsources' availability.
>| Some managed objects may not be affected by all three of these
>| factors.  These are
>|
>|  - operability: whether or not the resource is physically
>|    installed and working, if applicable;
>|  - usage: whether or not the resource is actively in use at
>|    a specific instant, and if so, whether or not it has spare
>|    capacity for additional users at that instant.  A resource
>|    is said to be "in use" when it has received one or more
>|    requests for service that it has not yet completed or
>|    otherwise discharged, or when some part of its capacity
>|    has been allocated, and not yet recalimed, as a result of
>|    a previous service request;
>|  - administration: permission to use or prohibition against
>|    using the resource, imposed through the management services.
>|
>| The state of a managed object does not affect its ability to
>| respond to management operations.
>
>As a practical matter, this means that these may be applicable
>to both physical and logical entities, and there will be some
>entities to which some of these may not apply.  I agree with
>your earlier comment about the augmentation being sparse.
>
>This is one of the reasons why X.731 clause 8.1.3 defines the
>"state" attribute group.  This lets a CMIP manager ask an
>object to return "whatever your state attribute(s) are".

Regards,
/david t. perkins


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



From entmib-admin@ietf.org  Wed Jul 10 05:51:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26276
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 05:51:43 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12170;
	Wed, 10 Jul 2002 05:52:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12145
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 05:52:28 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26262;
	Wed, 10 Jul 2002 05:51:33 -0400 (EDT)
Received: from kenawang ([192.168.1.46])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id CAA01904;
	Wed, 10 Jul 2002 02:50:09 -0700 (PDT)
Message-Id: <4.2.2.20020709210457.0174fc90@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 09 Jul 2002 21:27:33 -0400
To: agenda@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Cc: entmib@ietf.org, Bert Wijnen <bwijnen@lucent.com>,
        Randy Bush <randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Entmib] Entity MIB Agenda
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org



Entity MIB WG (entmib)
Tuesday, July 16, 0215-0315
===========================

CHAIR:  Margaret Wasserman <mrw@windriver.com>

AGENDA:

Introduction and Agenda Bashing (5 min)

Entity MIB Updates and Open Issues -- Andy Bierman (10 min)
<http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-00.txt>

Sensor Entity MIB Status and Open Issues -- Andy Bierman (5 min)
<http://www.ietf.org/internet-drafts/draft-ietf-entmib-sensor-mib-00.txt>

State/Status Information for Entity MIB -- Sharon Chisholm (15 min)
<See email to entmib@ietf.org dated 4-Jul-02>

Next Steps -- Margaret (10 min)







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


From daemon@optimus.ietf.org  Wed Jul 10 05:51:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26287
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 05:51:43 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA12199
	for entmib-archive@odin.ietf.org; Wed, 10 Jul 2002 05:52:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12170;
	Wed, 10 Jul 2002 05:52:30 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12145
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 05:52:28 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26262;
	Wed, 10 Jul 2002 05:51:33 -0400 (EDT)
Received: from kenawang ([192.168.1.46])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id CAA01904;
	Wed, 10 Jul 2002 02:50:09 -0700 (PDT)
Message-Id: <4.2.2.20020709210457.0174fc90@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 09 Jul 2002 21:27:33 -0400
To: agenda@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Cc: entmib@ietf.org, Bert Wijnen <bwijnen@lucent.com>,
        Randy Bush <randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Entmib] Entity MIB Agenda
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org



Entity MIB WG (entmib)
Tuesday, July 16, 0215-0315
===========================

CHAIR:  Margaret Wasserman <mrw@windriver.com>

AGENDA:

Introduction and Agenda Bashing (5 min)

Entity MIB Updates and Open Issues -- Andy Bierman (10 min)
<http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-00.txt>

Sensor Entity MIB Status and Open Issues -- Andy Bierman (5 min)
<http://www.ietf.org/internet-drafts/draft-ietf-entmib-sensor-mib-00.txt>

State/Status Information for Entity MIB -- Sharon Chisholm (15 min)
<See email to entmib@ietf.org dated 4-Jul-02>

Next Steps -- Margaret (10 min)







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



From entmib-admin@ietf.org  Wed Jul 10 12:36:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10363
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 12:36:12 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18443;
	Wed, 10 Jul 2002 12:37:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18419
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 12:36:59 -0400 (EDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10356
	for <entmib@ietf.org>; Wed, 10 Jul 2002 12:36:04 -0400 (EDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g6AGaYR0006975;
	Wed, 10 Jul 2002 18:36:34 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g6AGaXc30334;
	Wed, 10 Jul 2002 18:36:33 +0200
Date: Wed, 10 Jul 2002 18:36:33 +0200
Message-Id: <200207101636.g6AGaXc30334@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: rpresuhn@dorothy.bmc.com
CC: entmib@ietf.org
In-reply-to: <200207092121.OAA14130@dorothy.bmc.com> (message from Randy
	Presuhn on Tue, 9 Jul 2002 14:21:09 -0700 (PDT))
Subject: Re: [Entmib] State, Status and URL info
References:  <200207092121.OAA14130@dorothy.bmc.com>
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


I am ignorant of the details in the X.731 / X.721 documents. So from
the ignorant point of view, I am a bit puzzled...

>   ItuProcStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of procedural status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            initialization-required(1),
>                            not-initialized(2),
>                            initializing(3),
>                            reporting(4),
>                            terminating(5)
>                           }

Randy> Same problem.  Should be BITS; semantics in X.731 clause
Randy> 8.1.2.2; note that the corresponding syntax in X.721 is a set
Randy> type.

So I can be initializing(3) and terminating(5) at the same time? Or is
there some state machine that defines which bits may be set?

In short: It would be extremely helpful for people like me if someone
can provide a description of the model behind the proposal.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>



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


From daemon@optimus.ietf.org  Wed Jul 10 12:36:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10368
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 12:36:13 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA18477
	for entmib-archive@odin.ietf.org; Wed, 10 Jul 2002 12:37:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18443;
	Wed, 10 Jul 2002 12:37:00 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18419
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 12:36:59 -0400 (EDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10356
	for <entmib@ietf.org>; Wed, 10 Jul 2002 12:36:04 -0400 (EDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g6AGaYR0006975;
	Wed, 10 Jul 2002 18:36:34 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g6AGaXc30334;
	Wed, 10 Jul 2002 18:36:33 +0200
Date: Wed, 10 Jul 2002 18:36:33 +0200
Message-Id: <200207101636.g6AGaXc30334@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: rpresuhn@dorothy.bmc.com
CC: entmib@ietf.org
In-reply-to: <200207092121.OAA14130@dorothy.bmc.com> (message from Randy
	Presuhn on Tue, 9 Jul 2002 14:21:09 -0700 (PDT))
Subject: Re: [Entmib] State, Status and URL info
References:  <200207092121.OAA14130@dorothy.bmc.com>
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


I am ignorant of the details in the X.731 / X.721 documents. So from
the ignorant point of view, I am a bit puzzled...

>   ItuProcStatus  ::=  TEXTUAL-CONVENTION
>      STATUS         current
>      DESCRIPTION
>              " Represents the possible values of procedural status
>                (ITU-T X.731)."
> 
>            SYNTAX         INTEGER
>                           {
>                            initialization-required(1),
>                            not-initialized(2),
>                            initializing(3),
>                            reporting(4),
>                            terminating(5)
>                           }

Randy> Same problem.  Should be BITS; semantics in X.731 clause
Randy> 8.1.2.2; note that the corresponding syntax in X.721 is a set
Randy> type.

So I can be initializing(3) and terminating(5) at the same time? Or is
there some state machine that defines which bits may be set?

In short: It would be extremely helpful for people like me if someone
can provide a description of the model behind the proposal.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>



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



From entmib-admin@ietf.org  Wed Jul 10 13:32:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12384
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 13:32:28 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23650;
	Wed, 10 Jul 2002 13:33:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23624
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 13:33:18 -0400 (EDT)
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12381
	for <entmib@ietf.org>; Wed, 10 Jul 2002 13:32:23 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g6AHbKr10968
	for <entmib@ietf.org>; Wed, 10 Jul 2002 12:37:20 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA17125
	for entmib@ietf.org; Wed, 10 Jul 2002 10:31:00 -0700 (PDT)
Date: Wed, 10 Jul 2002 10:31:00 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207101731.KAA17125@dorothy.bmc.com>
To: entmib@ietf.org
Subject: Re: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 7bit

Hi -

> Date: Wed, 10 Jul 2002 18:36:33 +0200
> Message-Id: <200207101636.g6AGaXc30334@haerke.ibr.cs.tu-bs.de>
> From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
> To: rpresuhn@dorothy.bmc.com
> Cc: entmib@ietf.org
> In-reply-to: <200207092121.OAA14130@dorothy.bmc.com> (message from Randy
> 	Presuhn on Tue, 9 Jul 2002 14:21:09 -0700 (PDT))
> Subject: Re: [Entmib] State, Status and URL info
> References:  <200207092121.OAA14130@dorothy.bmc.com>
> 
> 
> I am ignorant of the details in the X.731 / X.721 documents. So from
> the ignorant point of view, I am a bit puzzled...
> 
> >   ItuProcStatus  ::=  TEXTUAL-CONVENTION
> >      STATUS         current
> >      DESCRIPTION
> >              " Represents the possible values of procedural status
> >                (ITU-T X.731)."
> > 
> >            SYNTAX         INTEGER
> >                           {
> >                            initialization-required(1),
> >                            not-initialized(2),
> >                            initializing(3),
> >                            reporting(4),
> >                            terminating(5)
> >                           }
> 
> Randy> Same problem.  Should be BITS; semantics in X.731 clause
> Randy> 8.1.2.2; note that the corresponding syntax in X.721 is a set
> Randy> type.
> 
> So I can be initializing(3) and terminating(5) at the same time? Or is
> there some state machine that defines which bits may be set?

Rec. X.731 clause 8.1.2.2 spells out constraints.

> In short: It would be extremely helpful for people like me if someone
> can provide a description of the model behind the proposal.
...

| The procedural status attribute is supported only by those classes
| of managed objects that represent some procedure (e.g., a test
| process) which progresses through a sequence of phases.  Depending
| upon the managed object class definition, the procedure may be
| required to reach certain phases for the resource to be operational
| and available for use (i.e. for the managed object to be enabled).
| Not all phases may be applicable to every class of managed object.
| If the value of this attribute is an empty set the managed object
| is ready, for example, the initialization is complete.

X.731 then provides more detailed descriptions of each of the
possible values in the set, along with their relationship to
the operational state attribute.  For example:

|  - terminating: The resource is in a termination phase.  If the
|    resource does not reinitialize itself autonomously, the
|    Initialization Required condition is also present and the
|    operational state is disabled.  Otherwise, the operational
|    state may be either disabled or enabled, depending on the
|    managed object class definition.

If the WG is seriously considering this proposal, it'd
be a good idea for participants to read through X.731,
since it goes into considerable detail about the model.
Pages 5-17 (in the 1992 version I have, sections 7 and 8
(model and generic definitions)) are the most important
for this discussion.  The document is available for (free)
download from the ITU web site http://www.itu.int/

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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


From daemon@optimus.ietf.org  Wed Jul 10 13:32:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12389
	for <entmib-archive@odin.ietf.org>; Wed, 10 Jul 2002 13:32:29 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA23671
	for entmib-archive@odin.ietf.org; Wed, 10 Jul 2002 13:33:23 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23650;
	Wed, 10 Jul 2002 13:33:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23624
	for <entmib@optimus.ietf.org>; Wed, 10 Jul 2002 13:33:18 -0400 (EDT)
Received: from babbler.bmc.com (firebird.bmc.com [198.207.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA12381
	for <entmib@ietf.org>; Wed, 10 Jul 2002 13:32:23 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by babbler.bmc.com (8.10.2/8.10.2) with ESMTP id g6AHbKr10968
	for <entmib@ietf.org>; Wed, 10 Jul 2002 12:37:20 -0500 (CDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id KAA17125
	for entmib@ietf.org; Wed, 10 Jul 2002 10:31:00 -0700 (PDT)
Date: Wed, 10 Jul 2002 10:31:00 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200207101731.KAA17125@dorothy.bmc.com>
To: entmib@ietf.org
Subject: Re: [Entmib] State, Status and URL info
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org
Content-Transfer-Encoding: 7bit

Hi -

> Date: Wed, 10 Jul 2002 18:36:33 +0200
> Message-Id: <200207101636.g6AGaXc30334@haerke.ibr.cs.tu-bs.de>
> From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
> To: rpresuhn@dorothy.bmc.com
> Cc: entmib@ietf.org
> In-reply-to: <200207092121.OAA14130@dorothy.bmc.com> (message from Randy
> 	Presuhn on Tue, 9 Jul 2002 14:21:09 -0700 (PDT))
> Subject: Re: [Entmib] State, Status and URL info
> References:  <200207092121.OAA14130@dorothy.bmc.com>
> 
> 
> I am ignorant of the details in the X.731 / X.721 documents. So from
> the ignorant point of view, I am a bit puzzled...
> 
> >   ItuProcStatus  ::=  TEXTUAL-CONVENTION
> >      STATUS         current
> >      DESCRIPTION
> >              " Represents the possible values of procedural status
> >                (ITU-T X.731)."
> > 
> >            SYNTAX         INTEGER
> >                           {
> >                            initialization-required(1),
> >                            not-initialized(2),
> >                            initializing(3),
> >                            reporting(4),
> >                            terminating(5)
> >                           }
> 
> Randy> Same problem.  Should be BITS; semantics in X.731 clause
> Randy> 8.1.2.2; note that the corresponding syntax in X.721 is a set
> Randy> type.
> 
> So I can be initializing(3) and terminating(5) at the same time? Or is
> there some state machine that defines which bits may be set?

Rec. X.731 clause 8.1.2.2 spells out constraints.

> In short: It would be extremely helpful for people like me if someone
> can provide a description of the model behind the proposal.
...

| The procedural status attribute is supported only by those classes
| of managed objects that represent some procedure (e.g., a test
| process) which progresses through a sequence of phases.  Depending
| upon the managed object class definition, the procedure may be
| required to reach certain phases for the resource to be operational
| and available for use (i.e. for the managed object to be enabled).
| Not all phases may be applicable to every class of managed object.
| If the value of this attribute is an empty set the managed object
| is ready, for example, the initialization is complete.

X.731 then provides more detailed descriptions of each of the
possible values in the set, along with their relationship to
the operational state attribute.  For example:

|  - terminating: The resource is in a termination phase.  If the
|    resource does not reinitialize itself autonomously, the
|    Initialization Required condition is also present and the
|    operational state is disabled.  Otherwise, the operational
|    state may be either disabled or enabled, depending on the
|    managed object class definition.

If the WG is seriously considering this proposal, it'd
be a good idea for participants to read through X.731,
since it goes into considerable detail about the model.
Pages 5-17 (in the 1992 version I have, sections 7 and 8
(model and generic definitions)) are the most important
for this discussion.  The document is available for (free)
download from the ITU web site http://www.itu.int/

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------

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



From entmib-admin@ietf.org  Tue Jul 16 17:41:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00468
	for <entmib-archive@odin.ietf.org>; Tue, 16 Jul 2002 17:41:26 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23635;
	Tue, 16 Jul 2002 17:42:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23607
	for <entmib@optimus.ietf.org>; Tue, 16 Jul 2002 17:42:13 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00465
	for <Entmib@ietf.org>; Tue, 16 Jul 2002 17:41:17 -0400 (EDT)
Received: from kenawang ([192.168.1.84])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA05093
	for <Entmib@ietf.org>; Tue, 16 Jul 2002 14:39:58 -0700 (PDT)
Message-Id: <4.2.2.20020716092126.00e38800@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 16 Jul 2002 09:30:09 -0400
To: Entmib@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Entmib] Fwd: Draft Minutes
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org



Hi All,

Here are the draft minutes from the Entity MIB meeting this afternoon.
Please let me know if you have any comments.

We seemed to have consensus on the following points in the meeting:

	- The changes to the Entity MIB document properly reflect
		the feedback from last meeting
	- We want to do work on state/status additions to the Entity
		MIB
	- The changes should be contained in a separate table that
		is a sparse augments of the current Entity MIB table(s)
	- The changes should be included in the same document with the
		Entity MIB -- the Entity MIB will not be re-published
		as a PS until these changes are completed.

Folks on the list, please let us know if you disagree with these
decisions.

Thanks,
Margaret


Entity MIB Minutes -- DRAFT
IETF54 Yokohama, Japan
Tuesday, July 15, 2002

Status of current work
	Entity Sensor MIB has been submitted to the IESG for PS
	Entity MIB updates completed as agreed at last meeting.

Consensus that the Entity MIB changes accurately reflect feedback from 
last meeting.

Entity State discussion

	<Sharon Chisholm presented State/Status proposal>

	Discussion of whether we should add redundancy support
	to the requirements for State/Status.  For instance,
	the ability to indicate the index of the entity for
	which this is redundant.  May be more complex to handle
	N+N and N+M redundancy.  Or would support for 1+1 
	redundancy be a 90% solution.

Options:

	- Add objects to the Entity MIB tables
	- Add a state table to the Entity MIB
	- Create a new MIB with state info

	What model to use?

David Perkins:  Glad we are doing this.  Has worked on this
	before -- a compromise IETF-like version.

Andy:  Could be done with 4 or 5 objects.

Randy Presuhn:  By definition, this is sparse.  Some entities
	won't have some state objects

	Need to be careful, when we define state objects and
	descriptions that we actually get everything that we 
	need.  Current ITU document cover a 3-dimensional
	state model that considers usage information.  If
	we want to compress to two dimensions, need to be
	careful.

Margaret:  Prefers to do separate MIB.

Sharon:  May turn into a big project that way.

Andy:  Whole new MIB module requires taking a charter update
	to the IESG.  Perhaps not worth it, when it will only
	require a few objects.

David Perkins:  Don't need the Entity MIB for v3 because you
	use a context in v3 and a community string in v1/v2.

Consensus to do work on State/Status additions to the Entity MIB

Andy:  What MIB we do it in depends on whether we will need to 
	cycle the Entity MIB at proposed.

Randy Presuhn:  Look at what we are trying to accomplish --
	common way of managing state/status info across different
	types of widgets.  Should we do this in a MIB, or in
	the enhanced data modeling features of SMIng?

	Pros and Cons to each choice:  Adding the information
	model is aesthetically more appealing, having a MIB is
	more operational appealing.

Sharon:  Benefit of doing it in the Entity MIB is that you can
	look in one place for the op/admin status of everything.
	Don't need to know about all sorts of other tables.

Andy:  One table gives a good place to look for alarming and
	thresholding in DisMan MIB

Consensus to do as separate Sparse Augments table.

Consensus to add state/status variables to the current document.

Sharon will write up a proposal for what we can add to the
current Entity MIB.

Andy:  If we rathole on the stand-by thing, we should leave
it out.



















   



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


From daemon@optimus.ietf.org  Tue Jul 16 17:41:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00476
	for <entmib-archive@odin.ietf.org>; Tue, 16 Jul 2002 17:41:26 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA23650
	for entmib-archive@odin.ietf.org; Tue, 16 Jul 2002 17:42:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23635;
	Tue, 16 Jul 2002 17:42:15 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23607
	for <entmib@optimus.ietf.org>; Tue, 16 Jul 2002 17:42:13 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00465
	for <Entmib@ietf.org>; Tue, 16 Jul 2002 17:41:17 -0400 (EDT)
Received: from kenawang ([192.168.1.84])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA05093
	for <Entmib@ietf.org>; Tue, 16 Jul 2002 14:39:58 -0700 (PDT)
Message-Id: <4.2.2.20020716092126.00e38800@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 16 Jul 2002 09:30:09 -0400
To: Entmib@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Entmib] Fwd: Draft Minutes
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org



Hi All,

Here are the draft minutes from the Entity MIB meeting this afternoon.
Please let me know if you have any comments.

We seemed to have consensus on the following points in the meeting:

	- The changes to the Entity MIB document properly reflect
		the feedback from last meeting
	- We want to do work on state/status additions to the Entity
		MIB
	- The changes should be contained in a separate table that
		is a sparse augments of the current Entity MIB table(s)
	- The changes should be included in the same document with the
		Entity MIB -- the Entity MIB will not be re-published
		as a PS until these changes are completed.

Folks on the list, please let us know if you disagree with these
decisions.

Thanks,
Margaret


Entity MIB Minutes -- DRAFT
IETF54 Yokohama, Japan
Tuesday, July 15, 2002

Status of current work
	Entity Sensor MIB has been submitted to the IESG for PS
	Entity MIB updates completed as agreed at last meeting.

Consensus that the Entity MIB changes accurately reflect feedback from 
last meeting.

Entity State discussion

	<Sharon Chisholm presented State/Status proposal>

	Discussion of whether we should add redundancy support
	to the requirements for State/Status.  For instance,
	the ability to indicate the index of the entity for
	which this is redundant.  May be more complex to handle
	N+N and N+M redundancy.  Or would support for 1+1 
	redundancy be a 90% solution.

Options:

	- Add objects to the Entity MIB tables
	- Add a state table to the Entity MIB
	- Create a new MIB with state info

	What model to use?

David Perkins:  Glad we are doing this.  Has worked on this
	before -- a compromise IETF-like version.

Andy:  Could be done with 4 or 5 objects.

Randy Presuhn:  By definition, this is sparse.  Some entities
	won't have some state objects

	Need to be careful, when we define state objects and
	descriptions that we actually get everything that we 
	need.  Current ITU document cover a 3-dimensional
	state model that considers usage information.  If
	we want to compress to two dimensions, need to be
	careful.

Margaret:  Prefers to do separate MIB.

Sharon:  May turn into a big project that way.

Andy:  Whole new MIB module requires taking a charter update
	to the IESG.  Perhaps not worth it, when it will only
	require a few objects.

David Perkins:  Don't need the Entity MIB for v3 because you
	use a context in v3 and a community string in v1/v2.

Consensus to do work on State/Status additions to the Entity MIB

Andy:  What MIB we do it in depends on whether we will need to 
	cycle the Entity MIB at proposed.

Randy Presuhn:  Look at what we are trying to accomplish --
	common way of managing state/status info across different
	types of widgets.  Should we do this in a MIB, or in
	the enhanced data modeling features of SMIng?

	Pros and Cons to each choice:  Adding the information
	model is aesthetically more appealing, having a MIB is
	more operational appealing.

Sharon:  Benefit of doing it in the Entity MIB is that you can
	look in one place for the op/admin status of everything.
	Don't need to know about all sorts of other tables.

Andy:  One table gives a good place to look for alarming and
	thresholding in DisMan MIB

Consensus to do as separate Sparse Augments table.

Consensus to add state/status variables to the current document.

Sharon will write up a proposal for what we can add to the
current Entity MIB.

Andy:  If we rathole on the stand-by thing, we should leave
it out.



















   



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



From entmib-admin@ietf.org  Wed Jul 17 04:15:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09472
	for <entmib-archive@odin.ietf.org>; Wed, 17 Jul 2002 04:15:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21279;
	Wed, 17 Jul 2002 04:15:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21248
	for <entmib@optimus.ietf.org>; Wed, 17 Jul 2002 04:15:56 -0400 (EDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09465
	for <Entmib@ietf.org>; Wed, 17 Jul 2002 04:14:58 -0400 (EDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g6H8FqR0030987;
	Wed, 17 Jul 2002 10:15:53 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g6H8Fpl19293;
	Wed, 17 Jul 2002 10:15:51 +0200
Date: Wed, 17 Jul 2002 10:15:51 +0200
Message-Id: <200207170815.g6H8Fpl19293@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Entmib@ietf.org
CC: mrw@windriver.com
In-reply-to: <4.2.2.20020716092126.00e38800@mail.windriver.com> (message from
	Margaret Wasserman on Tue, 16 Jul 2002 09:30:09 -0400)
Subject: Re: [Entmib] Fwd: Draft Minutes
References:  <4.2.2.20020716092126.00e38800@mail.windriver.com>
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


>>>>> Margaret Wasserman writes:

Margaret> We seemed to have consensus on the following points in the
Margaret> meeting:

: - The changes to the Entity MIB document properly reflect
:	the feedback from last meeting
: - We want to do work on state/status additions to the Entity MIB
: - The changes should be contained in a separate table that
:	is a sparse augments of the current Entity MIB table(s)
: - The changes should be included in the same document with the
:	Entity MIB -- the Entity MIB will not be re-published
:	as a PS until these changes are completed.

Margaret> Folks on the list, please let us know if you disagree with
Margaret> these decisions.

Sounds very good to me.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

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


From daemon@optimus.ietf.org  Wed Jul 17 05:19:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09487
	for <entmib-archive@odin.ietf.org>; Wed, 17 Jul 2002 04:15:16 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA21306
	for entmib-archive@odin.ietf.org; Wed, 17 Jul 2002 04:16:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21279;
	Wed, 17 Jul 2002 04:15:58 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21248
	for <entmib@optimus.ietf.org>; Wed, 17 Jul 2002 04:15:56 -0400 (EDT)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09465
	for <Entmib@ietf.org>; Wed, 17 Jul 2002 04:14:58 -0400 (EDT)
Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g6H8FqR0030987;
	Wed, 17 Jul 2002 10:15:53 +0200
Received: (from schoenw@localhost)
	by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g6H8Fpl19293;
	Wed, 17 Jul 2002 10:15:51 +0200
Date: Wed, 17 Jul 2002 10:15:51 +0200
Message-Id: <200207170815.g6H8Fpl19293@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Entmib@ietf.org
CC: mrw@windriver.com
In-reply-to: <4.2.2.20020716092126.00e38800@mail.windriver.com> (message from
	Margaret Wasserman on Tue, 16 Jul 2002 09:30:09 -0400)
Subject: Re: [Entmib] Fwd: Draft Minutes
References:  <4.2.2.20020716092126.00e38800@mail.windriver.com>
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


>>>>> Margaret Wasserman writes:

Margaret> We seemed to have consensus on the following points in the
Margaret> meeting:

: - The changes to the Entity MIB document properly reflect
:	the feedback from last meeting
: - We want to do work on state/status additions to the Entity MIB
: - The changes should be contained in a separate table that
:	is a sparse augments of the current Entity MIB table(s)
: - The changes should be included in the same document with the
:	Entity MIB -- the Entity MIB will not be re-published
:	as a PS until these changes are completed.

Margaret> Folks on the list, please let us know if you disagree with
Margaret> these decisions.

Sounds very good to me.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

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



From entmib-admin@ietf.org  Tue Jul 30 05:59:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10716
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 05:59:15 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA15035;
	Tue, 30 Jul 2002 06:00:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA14997
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 06:00:08 -0400 (EDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10710
	for <entmib@ietf.org>; Tue, 30 Jul 2002 05:59:00 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6U9xau19975
	for <entmib@ietf.org>; Tue, 30 Jul 2002 05:59:36 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <P71CHBRR>; Tue, 30 Jul 2002 11:59:31 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E938142@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Entmib-wg (E-mail)" <entmib@ietf.org>
Date: Tue, 30 Jul 2002 11:59:30 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Entmib] sensor mib
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

I reviewed draft-ietf-entmib-sensor-mib-00.txt in
preparation for IETF Last Call.

I have some nits.

- in the abstract section one should not use references/citations
  It is OK to replace [RFC2737] by (RFC 2737)
  I know... but look at http://www.rfc-editor.org/policy.html

- RFC-Editor wants separation of Normative and informative
  references. Same rfc-editor policy page for details.
  I know we need to find a generic split for the SNMP Framework
  section. Proposals are welcome. (I suggest to do the generic
  discussion on the mib mailing list: mibs@ops.ietf.org).

- you talk about "augments" (sect 5), "conceptually extend" 
  (sect 5.2), "SPARSE-AUGMENTS" (comment in MIB itself).
  Might be better to be consistent in our terminology, no?

- Section 6: there seems to be still an "OPEN ISSUE" ?? for
  entSensorType. My take: instead of IANA registered OIDs.
  we could also choose an IANA-maintained TC with the ENUMs.

- Would it not be better to rename entSensorStatus to 
  entSensorOperStatus ???

- if you are going to edit, then I would change

    REVISION        "200201180000Z"
    DESCRIPTION
            "Initial version of the Entity Sensor MIB module."
    ::= { mib-2 xxx } -- unassigned

  into

    REVISION        "200201180000Z"
    DESCRIPTION
            "Initial version of the Entity Sensor MIB module,
             publsihed as RFC xxxx." -- RFC-Editor assigns xxxx
    ::= { mib-2 xxx } -- IANA needs to assign xxx

- I wonder why entitySensorNotifications is defined, it is not used
  and there are no notifcations specified.

- I guess that the contact info for KC needs to be updated.

Would it make sense to (quickly) do a revision to address the above?

Thanks,
Bert 

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


From daemon@optimus.ietf.org  Tue Jul 30 05:59:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10724
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 05:59:15 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA15140
	for entmib-archive@odin.ietf.org; Tue, 30 Jul 2002 06:00:22 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA15035;
	Tue, 30 Jul 2002 06:00:09 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA14997
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 06:00:08 -0400 (EDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10710
	for <entmib@ietf.org>; Tue, 30 Jul 2002 05:59:00 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6U9xau19975
	for <entmib@ietf.org>; Tue, 30 Jul 2002 05:59:36 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <P71CHBRR>; Tue, 30 Jul 2002 11:59:31 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E938142@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Entmib-wg (E-mail)" <entmib@ietf.org>
Date: Tue, 30 Jul 2002 11:59:30 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Entmib] sensor mib
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

I reviewed draft-ietf-entmib-sensor-mib-00.txt in
preparation for IETF Last Call.

I have some nits.

- in the abstract section one should not use references/citations
  It is OK to replace [RFC2737] by (RFC 2737)
  I know... but look at http://www.rfc-editor.org/policy.html

- RFC-Editor wants separation of Normative and informative
  references. Same rfc-editor policy page for details.
  I know we need to find a generic split for the SNMP Framework
  section. Proposals are welcome. (I suggest to do the generic
  discussion on the mib mailing list: mibs@ops.ietf.org).

- you talk about "augments" (sect 5), "conceptually extend" 
  (sect 5.2), "SPARSE-AUGMENTS" (comment in MIB itself).
  Might be better to be consistent in our terminology, no?

- Section 6: there seems to be still an "OPEN ISSUE" ?? for
  entSensorType. My take: instead of IANA registered OIDs.
  we could also choose an IANA-maintained TC with the ENUMs.

- Would it not be better to rename entSensorStatus to 
  entSensorOperStatus ???

- if you are going to edit, then I would change

    REVISION        "200201180000Z"
    DESCRIPTION
            "Initial version of the Entity Sensor MIB module."
    ::= { mib-2 xxx } -- unassigned

  into

    REVISION        "200201180000Z"
    DESCRIPTION
            "Initial version of the Entity Sensor MIB module,
             publsihed as RFC xxxx." -- RFC-Editor assigns xxxx
    ::= { mib-2 xxx } -- IANA needs to assign xxx

- I wonder why entitySensorNotifications is defined, it is not used
  and there are no notifcations specified.

- I guess that the contact info for KC needs to be updated.

Would it make sense to (quickly) do a revision to address the above?

Thanks,
Bert 

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



From entmib-admin@ietf.org  Tue Jul 30 10:04:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18878
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:04:36 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27761;
	Tue, 30 Jul 2002 10:05:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27734
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:05:13 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18862
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:04:05 -0400 (EDT)
Received: from kenawang ([147.11.233.33])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id HAA24000;
	Tue, 30 Jul 2002 07:04:37 -0700 (PDT)
Message-Id: <4.2.2.20020730100024.02261e60@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 30 Jul 2002 10:03:42 -0400
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: [Entmib] sensor mib
Cc: "Entmib-wg (E-mail)" <entmib@ietf.org>
In-Reply-To: <A451D5E6F15FD211BABC0008C7FAD7BC0E938142@nl0006exch003u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


Good comments, Bert.  Thanks.

Andy, KC & Dan, could you work on an update to address these
issues?

Some specific thoughts and questions:

>- RFC-Editor wants separation of Normative and informative
>   references. Same rfc-editor policy page for details.
>   I know we need to find a generic split for the SNMP Framework
>   section. Proposals are welcome. (I suggest to do the generic
>   discussion on the mib mailing list: mibs@ops.ietf.org).

I'll take a shot at this later today or tomorrow (unless
someone beats me to it).  

>- Section 6: there seems to be still an "OPEN ISSUE" ?? for
>   entSensorType. My take: instead of IANA registered OIDs.
>   we could also choose an IANA-maintained TC with the ENUMs.

This sounds good.  Are there any other MIBs that do this?

Margaret


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


From daemon@optimus.ietf.org  Tue Jul 30 10:04:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18886
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:04:36 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA27810
	for entmib-archive@odin.ietf.org; Tue, 30 Jul 2002 10:05:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27761;
	Tue, 30 Jul 2002 10:05:14 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA27734
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:05:13 -0400 (EDT)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18862
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:04:05 -0400 (EDT)
Received: from kenawang ([147.11.233.33])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id HAA24000;
	Tue, 30 Jul 2002 07:04:37 -0700 (PDT)
Message-Id: <4.2.2.20020730100024.02261e60@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Tue, 30 Jul 2002 10:03:42 -0400
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Margaret Wasserman <mrw@windriver.com>
Subject: Re: [Entmib] sensor mib
Cc: "Entmib-wg (E-mail)" <entmib@ietf.org>
In-Reply-To: <A451D5E6F15FD211BABC0008C7FAD7BC0E938142@nl0006exch003u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


Good comments, Bert.  Thanks.

Andy, KC & Dan, could you work on an update to address these
issues?

Some specific thoughts and questions:

>- RFC-Editor wants separation of Normative and informative
>   references. Same rfc-editor policy page for details.
>   I know we need to find a generic split for the SNMP Framework
>   section. Proposals are welcome. (I suggest to do the generic
>   discussion on the mib mailing list: mibs@ops.ietf.org).

I'll take a shot at this later today or tomorrow (unless
someone beats me to it).  

>- Section 6: there seems to be still an "OPEN ISSUE" ?? for
>   entSensorType. My take: instead of IANA registered OIDs.
>   we could also choose an IANA-maintained TC with the ENUMs.

This sounds good.  Are there any other MIBs that do this?

Margaret


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



From entmib-admin@ietf.org  Tue Jul 30 10:11:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19339
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:11:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28220;
	Tue, 30 Jul 2002 10:12:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28191
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:11:58 -0400 (EDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19273
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:10:50 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6UEBSh16142
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:11:28 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <P71CHQHY>; Tue, 30 Jul 2002 16:11:27 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E938273@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Margaret Wasserman <mrw@windriver.com>
Cc: "Entmib-wg (E-mail)" <entmib@ietf.org>
Subject: RE: [Entmib] sensor mib
Date: Tue, 30 Jul 2002 16:11:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

> Some specific thoughts and questions:
> 
> >- RFC-Editor wants separation of Normative and informative
> >   references. Same rfc-editor policy page for details.
> >   I know we need to find a generic split for the SNMP Framework
> >   section. Proposals are welcome. (I suggest to do the generic
> >   discussion on the mib mailing list: mibs@ops.ietf.org).
> 
> I'll take a shot at this later today or tomorrow (unless
> someone beats me to it).  
> 
In fact I think Randy Presuhn has already taken a shot at it.
Need to dig it up.

> >- Section 6: there seems to be still an "OPEN ISSUE" ?? for
> >   entSensorType. My take: instead of IANA registered OIDs.
> >   we could also choose an IANA-maintained TC with the ENUMs.
> 
> This sounds good.  Are there any other MIBs that do this?
> 
The ianaIfType MIB for example.

And by the way, I also found:

  EntitySensorDataScale ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
            "An object using this data type represents a data scaling
            factor, represented with an International System of Units
            (SI) prefix.  The actual data units are determined by
            examining an object of this type together with the
            associated EntitySensorDataType object.

            An object of this type SHOULD be defined together with
            objects of type EntitySensorDataType and
            EntitySensorPrecision.  Together, associated objects of
            these three types are used to identify the semantics of an
            object of type EntitySensorValue."
    REFERENCE
===>      "TBD"

Either remove the reference or decide what it is going to be, pls

Bert

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


From daemon@optimus.ietf.org  Tue Jul 30 10:11:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19347
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:11:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA28306
	for entmib-archive@odin.ietf.org; Tue, 30 Jul 2002 10:12:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28220;
	Tue, 30 Jul 2002 10:12:01 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA28191
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:11:58 -0400 (EDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19273
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:10:50 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6UEBSh16142
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:11:28 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <P71CHQHY>; Tue, 30 Jul 2002 16:11:27 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E938273@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Margaret Wasserman <mrw@windriver.com>
Cc: "Entmib-wg (E-mail)" <entmib@ietf.org>
Subject: RE: [Entmib] sensor mib
Date: Tue, 30 Jul 2002 16:11:25 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

> Some specific thoughts and questions:
> 
> >- RFC-Editor wants separation of Normative and informative
> >   references. Same rfc-editor policy page for details.
> >   I know we need to find a generic split for the SNMP Framework
> >   section. Proposals are welcome. (I suggest to do the generic
> >   discussion on the mib mailing list: mibs@ops.ietf.org).
> 
> I'll take a shot at this later today or tomorrow (unless
> someone beats me to it).  
> 
In fact I think Randy Presuhn has already taken a shot at it.
Need to dig it up.

> >- Section 6: there seems to be still an "OPEN ISSUE" ?? for
> >   entSensorType. My take: instead of IANA registered OIDs.
> >   we could also choose an IANA-maintained TC with the ENUMs.
> 
> This sounds good.  Are there any other MIBs that do this?
> 
The ianaIfType MIB for example.

And by the way, I also found:

  EntitySensorDataScale ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
            "An object using this data type represents a data scaling
            factor, represented with an International System of Units
            (SI) prefix.  The actual data units are determined by
            examining an object of this type together with the
            associated EntitySensorDataType object.

            An object of this type SHOULD be defined together with
            objects of type EntitySensorDataType and
            EntitySensorPrecision.  Together, associated objects of
            these three types are used to identify the semantics of an
            object of type EntitySensorValue."
    REFERENCE
===>      "TBD"

Either remove the reference or decide what it is going to be, pls

Bert

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



From entmib-admin@ietf.org  Tue Jul 30 10:26:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20200
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:26:37 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29039;
	Tue, 30 Jul 2002 10:27:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29021
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:27:04 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20155
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:25:55 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g6UEQO9V014872;
	Tue, 30 Jul 2002 07:26:24 -0700 (PDT)
Received: from nisser.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g6UEQbdk004750;
	Tue, 30 Jul 2002 07:26:38 -0700 (PDT)
Received: from PC2.cisco.com (sjc-vpn1-863.cisco.com [10.21.99.95]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id HAA06931; Tue, 30 Jul 2002 07:26:31 -0700 (PDT)
Message-Id: <5.1.0.14.2.20020730071538.02511028@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 30 Jul 2002 07:23:43 -0700
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] sensor mib
Cc: Margaret Wasserman <mrw@windriver.com>,
        "Entmib-wg (E-mail)" <entmib@ietf.org>
In-Reply-To: <A451D5E6F15FD211BABC0008C7FAD7BC0E938273@nl0006exch003u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

At 07:11 AM 7/30/2002, Wijnen, Bert (Bert) wrote:
>> Some specific thoughts and questions:
>> 
>> >- RFC-Editor wants separation of Normative and informative
>> >   references. Same rfc-editor policy page for details.
>> >   I know we need to find a generic split for the SNMP Framework
>> >   section. Proposals are welcome. (I suggest to do the generic
>> >   discussion on the mib mailing list: mibs@ops.ietf.org).
>> 
>> I'll take a shot at this later today or tomorrow (unless
>> someone beats me to it).  
>> 
>In fact I think Randy Presuhn has already taken a shot at it.
>Need to dig it up.

I've made an attempt at a split in draft-ietf-sming-ds-00.txt,
based on comments from Randy.  Here are the RFCs from the
boilerplate:

Normative        Informative
----------       ------------
 1905                1155
 1906                1157
 2026                1212
 2119                1215
 2571                1901
 2572                2570
 2573
 2574
 2575
 2578
 2579
 2580

We should finalize this soon, and update the template,
so MIB authors will start using the correct text.


>> >- Section 6: there seems to be still an "OPEN ISSUE" ?? for
>> >   entSensorType. My take: instead of IANA registered OIDs.
>> >   we could also choose an IANA-maintained TC with the ENUMs.
>> 
>> This sounds good.  Are there any other MIBs that do this?
>> 
>The ianaIfType MIB for example.
>
>And by the way, I also found:
>
>  EntitySensorDataScale ::= TEXTUAL-CONVENTION
>    STATUS       current
>    DESCRIPTION
>            "An object using this data type represents a data scaling
>            factor, represented with an International System of Units
>            (SI) prefix.  The actual data units are determined by
>            examining an object of this type together with the
>            associated EntitySensorDataType object.
>
>            An object of this type SHOULD be defined together with
>            objects of type EntitySensorDataType and
>            EntitySensorPrecision.  Together, associated objects of
>            these three types are used to identify the semantics of an
>            object of type EntitySensorValue."
>    REFERENCE
>===>      "TBD"
>
>Either remove the reference or decide what it is going to be, pls

okay -- I will do an update based on all your edits ASAP


>Bert

Andy


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


From daemon@optimus.ietf.org  Tue Jul 30 10:26:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20210
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:26:38 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA29140
	for entmib-archive@odin.ietf.org; Tue, 30 Jul 2002 10:27:45 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29039;
	Tue, 30 Jul 2002 10:27:06 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29021
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:27:04 -0400 (EDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20155
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:25:55 -0400 (EDT)
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g6UEQO9V014872;
	Tue, 30 Jul 2002 07:26:24 -0700 (PDT)
Received: from nisser.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g6UEQbdk004750;
	Tue, 30 Jul 2002 07:26:38 -0700 (PDT)
Received: from PC2.cisco.com (sjc-vpn1-863.cisco.com [10.21.99.95]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id HAA06931; Tue, 30 Jul 2002 07:26:31 -0700 (PDT)
Message-Id: <5.1.0.14.2.20020730071538.02511028@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 30 Jul 2002 07:23:43 -0700
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] sensor mib
Cc: Margaret Wasserman <mrw@windriver.com>,
        "Entmib-wg (E-mail)" <entmib@ietf.org>
In-Reply-To: <A451D5E6F15FD211BABC0008C7FAD7BC0E938273@nl0006exch003u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

At 07:11 AM 7/30/2002, Wijnen, Bert (Bert) wrote:
>> Some specific thoughts and questions:
>> 
>> >- RFC-Editor wants separation of Normative and informative
>> >   references. Same rfc-editor policy page for details.
>> >   I know we need to find a generic split for the SNMP Framework
>> >   section. Proposals are welcome. (I suggest to do the generic
>> >   discussion on the mib mailing list: mibs@ops.ietf.org).
>> 
>> I'll take a shot at this later today or tomorrow (unless
>> someone beats me to it).  
>> 
>In fact I think Randy Presuhn has already taken a shot at it.
>Need to dig it up.

I've made an attempt at a split in draft-ietf-sming-ds-00.txt,
based on comments from Randy.  Here are the RFCs from the
boilerplate:

Normative        Informative
----------       ------------
 1905                1155
 1906                1157
 2026                1212
 2119                1215
 2571                1901
 2572                2570
 2573
 2574
 2575
 2578
 2579
 2580

We should finalize this soon, and update the template,
so MIB authors will start using the correct text.


>> >- Section 6: there seems to be still an "OPEN ISSUE" ?? for
>> >   entSensorType. My take: instead of IANA registered OIDs.
>> >   we could also choose an IANA-maintained TC with the ENUMs.
>> 
>> This sounds good.  Are there any other MIBs that do this?
>> 
>The ianaIfType MIB for example.
>
>And by the way, I also found:
>
>  EntitySensorDataScale ::= TEXTUAL-CONVENTION
>    STATUS       current
>    DESCRIPTION
>            "An object using this data type represents a data scaling
>            factor, represented with an International System of Units
>            (SI) prefix.  The actual data units are determined by
>            examining an object of this type together with the
>            associated EntitySensorDataType object.
>
>            An object of this type SHOULD be defined together with
>            objects of type EntitySensorDataType and
>            EntitySensorPrecision.  Together, associated objects of
>            these three types are used to identify the semantics of an
>            object of type EntitySensorValue."
>    REFERENCE
>===>      "TBD"
>
>Either remove the reference or decide what it is going to be, pls

okay -- I will do an update based on all your edits ASAP


>Bert

Andy


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



From entmib-admin@ietf.org  Tue Jul 30 10:31:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20688
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:31:44 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29996;
	Tue, 30 Jul 2002 10:32:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29976
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:32:35 -0400 (EDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20673
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:31:27 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6UEW4h25108
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:32:04 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <P71CHSBL>; Tue, 30 Jul 2002 16:32:03 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E93829A@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Andy Bierman <abierman@cisco.com>
Cc: Margaret Wasserman <mrw@windriver.com>,
        "Entmib-wg (E-mail)"
	 <entmib@ietf.org>
Subject: RE: [Entmib] sensor mib
Date: Tue, 30 Jul 2002 16:32:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

> I've made an attempt at a split in draft-ietf-sming-ds-00.txt,
> based on comments from Randy.  Here are the RFCs from the
> boilerplate:
> 
> Normative        Informative
> ----------       ------------
>  1905                1155
>  1906                1157
>  2026                1212
>  2119                1215
>  2571                1901
>  2572                2570
>  2573
>  2574
>  2575
>  2578
>  2579
>  2580
> 
> We should finalize this soon, and update the template,
> so MIB authors will start using the correct text.
> 
The above sounds good to me.
I was sort of waiting till we have the updates to the documents
Remember, 1905/6/7, 2570-2575 will soon get new RFC numbers,

I will post the above to mibs@ops.ietf.org, which seems a better 
place for discussion this generic MIB document item.

Bert

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


From daemon@optimus.ietf.org  Tue Jul 30 10:31:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20694
	for <entmib-archive@odin.ietf.org>; Tue, 30 Jul 2002 10:31:45 -0400 (EDT)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA00038
	for entmib-archive@odin.ietf.org; Tue, 30 Jul 2002 10:32:52 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29996;
	Tue, 30 Jul 2002 10:32:36 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA29976
	for <entmib@optimus.ietf.org>; Tue, 30 Jul 2002 10:32:35 -0400 (EDT)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20673
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:31:27 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g6UEW4h25108
	for <entmib@ietf.org>; Tue, 30 Jul 2002 10:32:04 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <P71CHSBL>; Tue, 30 Jul 2002 16:32:03 +0200
Message-ID: <A451D5E6F15FD211BABC0008C7FAD7BC0E93829A@nl0006exch003u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Andy Bierman <abierman@cisco.com>
Cc: Margaret Wasserman <mrw@windriver.com>,
        "Entmib-wg (E-mail)"
	 <entmib@ietf.org>
Subject: RE: [Entmib] sensor mib
Date: Tue, 30 Jul 2002 16:32:02 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

> I've made an attempt at a split in draft-ietf-sming-ds-00.txt,
> based on comments from Randy.  Here are the RFCs from the
> boilerplate:
> 
> Normative        Informative
> ----------       ------------
>  1905                1155
>  1906                1157
>  2026                1212
>  2119                1215
>  2571                1901
>  2572                2570
>  2573
>  2574
>  2575
>  2578
>  2579
>  2580
> 
> We should finalize this soon, and update the template,
> so MIB authors will start using the correct text.
> 
The above sounds good to me.
I was sort of waiting till we have the updates to the documents
Remember, 1905/6/7, 2570-2575 will soon get new RFC numbers,

I will post the above to mibs@ops.ietf.org, which seems a better 
place for discussion this generic MIB document item.

Bert

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



