Question on RowStatus

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

In the MPLS LSR mib, I see:

mplsInSegmentStorageType OBJECT-TYPE
   SYNTAX        StorageType
   MAX-ACCESS    read-only
   STATUS        current
   DESCRIPTION
       "This variable indicates the storage type for this
        object. If this object is set to readOnly(5), and the
        corresponding LFIB entry is removed, then the agent
        MUST remove this row shortly thereafter [RFC2579].
        The agent MUST ensure that this object's value
        remains consistent with the associated mplsXCEntry.
        The default value is volatile(2)."
   DEFVAL { volatile }
   ::= { mplsInSegmentEntry 11 }

My questions:
- I think that it is OK that an agent can remove such readOnly rows
  when the underlying data ceases to exist. If anyone thinks that
  is not correct, pls holler.
- The sentence about an agent needing to keep the object consistent
  with one or more stoargeTypes in other tables worries me.
  I guess it is OK. Maybe what I want them to do is to add text aka:
        If a SET request tries to set a vlue that is inconsistent
        with that associated mplsXCentry, then a inconcistentValue
        error should be returned.

Comments pls

Thanks,
Bert