FW: [psg.com #308] AutoReply: Shutting Down Admin State

The following is the proposed resolution to entstate-308. The issue will be
considered closed with no changes made to the document.

The following explanations were provided and no questions were raised.

"
1. Is shutting down really more an operational state?

The state refers more to whether your administrative model allows 
systems to be shut down gracefully or not. The idea being that if it 
does, you would still have the options to bring it down less 
gracefully. We have allowed in the description of the object for 
systems that don't support this value for the state.

2. Would 'noNewUsage' be a better term. 

Well, except that the idea is that once all the existing 'users' are 
gone, the system will shut down. The term 'noNewUsage' does not really 
reflect that."

Sharon


-----Original Message-----
From: entity-state [mailto:[email protected]] 
Sent: Tuesday, January 13, 2004 2:55 AM
To: Chisholm, Sharon [CAR:0S00:EXCH]
Subject: [psg.com #308] AutoReply: Shutting Down Admin State
<clip>

-------------------------------------------------------------------------
Keith McCloghrie [[email protected]]

"

the term 'shuttingDown' suggests that the action of shutting down is
>   in progress, which of course is an operational condition, not an
admin
>   state.  A term more reflective of what the AdminState DESCRIPTION
appears
>   to define would be 'noNewUsage'.  In any case, this concept
of 'usage'
>   is almost always a higher-level usage (e.g., a new ATM connection
on an
>   ATM interface, a new Unix login on a cpu module, etc.) and thus
don't
>   belong at the physical layer (i.e., don't apply to
> entPhysicalIndex).
"