Subject: RE: LDP MIB

From: "Cucchiara, Joan" <[email-masked]>
Date: Wed, 21 Jun 2000 09:26:33 -0400

-----Original Message-----
> From: Santosh Gupta [mailto:[email-masked]]
> Sent: Wednesday, June 21, 2000 1:42 AM
> To: [email-masked]
> Subject: LDP MIB
>

Hi Santosh,

All of the issues below (except the question on StorageType) were
raised during the LDP MIB last call.  I'll recap where we are
going with these for the next rev.

>
> Hello 
>     I have  a few doubts regarding draft-ietf-mpls-ldp-mib-05. Could
someone > clarify these.
> 
> 1. mplsLdpEntityOperStatus
> What is the use of this field in mplsLdpEntityTable ?

The idea is to represent the Actual state of the entry.
For example, you can set a state to up in the admin status
object, but that doesn't mean that the actual entity is 
working, the operstatus gives an indication of what the
actual state is.   The circumstances under which an OperStatus
is down and an AdminStatus is up is left to specific implementations
but for example, if there isn't enough system resources to support
another entity then operStatus may be down.  

> 
> 2. mplsLdpEntityHopCount
> The draft says this value specifies the "Initial Hop Count for this
Entity". > What could be the use of such assignment when we know that Hop
Count is
> decided online depending  on the path on which the LSP is setup ?

This will be reworked similarly to what Piers Finlayson suggested in
email c. 3/11/00.

Essentially combine both the HopCountLoopDetection and
HopCount objects into an object similar to:   

      "mplsLdpEntityHopCounterLimit OBJECT-TYPE 
          SYNTAX       Integer32 (0..255)
          MAX-ACCESS   read-create 
          STATUS       current 
          DESCRIPTION 
              "If the value of this object is 0 (zero),
              then Loop Detection using Hop Counters is
              disabled.
              If the value of this object is greater than
              0 (zero) then Loop Detection using Hop
              Counters is enabled, and this object
              specifies this Entity's maximum allowable
              value for the Hop Count.
              Also, the value of the object
              mplsLdpLsrLoopDetectionCapable must be set
              to either 'hopCount(3)' or
              'hopCountAndPathVector(5)' if this object
              has a value greater than 0 (zero)."
          ::= { mplsLdpEntityEntry 15 }" 

> 
> 3. mplsLdpEntityStorageType 
> Not clear what it means and what is  it's use.

This is used as described in RFC2579.  It is an
SMIv2 Textual Convention which is used to indicate
if/how the configured information is stored in 
nonvolatile storage.  It was thought appropriate that
LDP entity configuration include this as a way to
indicate if the configuration was stored in non-volatile
memory or not.

> 
> 4. mplsLdpEntityRowStatus 
> What is the need for this field when mplsLdpEntityAdminStatus field  is 
> serving the same purpose?

Granted these objects do overlap in function somewhat (not completely).
The idea is that some users may be allowed to manipulate admin status, 
but NOT rowStatus. For example, deleting a row may only be granted to 
a specific user, whereas admin status capabilities (which are less
drastic than deleting a row, may be granted to more users.)

   -Joan

> santosh