Party MIB

[Aleksey Y Romanov <[e-mail]>]

I am a little bit puzzled by Party MIB document. My guess is that it has
some typos.

1. From Textual Conventions for ... :
>                              NOTE WELL
> 
>                 This textual convention may be used for a MIB
>                 table, irrespective of whether the values of
>                 that table's conceptual rows are able to be
>                 modified while it is active, or whether its
>                 conceptual rows must be taken out of service
>                 in order to be modified.  That is, it is the
>                 responsibility of the DESCRIPTION clause of
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>                 the status column to specify whether the
                                    ^^^^^^^^^^
>                 status column must be `notInService' in order
>                 for the value of some other column of the
>                 same conceptual row to be modified.
 
2. From Party MIB for ... :

>           partyStatus OBJECT-TYPE
>               SYNTAX      RowStatus
>               MAX-ACCESS  read-create
>               STATUS      current
>               DESCRIPTION
>                       "The status of this conceptual row in the
>                       partyTable.
> 
>                       A party is not qualified for activation until
>                       instances of all columns of its partyEntry row
>                       have an appropriate value.  In particular:
> 
>                         A value must be written to the Party's
>                         partyCloneFrom object.
> 
>                         If the Party's partyAuthProtocol object has the
>                         value md5AuthProtocol, then the corresponding
>                         instance of partyAuthPrivate must contain a
>                         secret of the appropriate length.  Further, at
>                         least one management protocol set operation
>                         updating the value of the party's
>                         partyAuthPrivate object must be successfully
>                         processed, before the partyAuthPrivate column is
>                         considered appropriately configured.
> 
>                         If the Party's partyPrivProtocol object has the
>                         value desPrivProtocol, then the corresponding
>                         instance of partyPrivPrivate must contain a
>                         secret of the appropriate length.  Further, at
>                         least one management protocol set operation
>                         updating the value of the party's
>                         partyPrivPrivate object must be successfully
>                         processed, before the partyPrivPrivate column is
>                         considered appropriately configured.
> 
>                      Until instances of all corresponding columns are
>                      appropriately configured, the value of the
>                      corresponding instance of the partyStatus column is
>                      `notReady'."
>               ::= { partyEntry 17 }

I do not see a signle word about whether or not it is possible
to change values of the existing party entry without setting partyStatus
to notInService.

>           contextStatus OBJECT-TYPE
>               SYNTAX      RowStatus
>               MAX-ACCESS  read-create
>               STATUS      current
>               DESCRIPTION
>                       "The status of this conceptual row in the
>                       contextTable.
> 
>                       A context is not qualified for activation until
>                       instances of all corresponding columns have the
>                       appropriate value.  In  particular, if the
>                       context's contextViewIndex is greater than zero,
>                       then the viewStatus column of the associated
>                       conceptual row(s) in the viewTable must have the
>                       value `active'.  Until instances of all
>                       corresponding columns are appropriately
>                       configured, the value of the corresponding
>                       instance of the contextStatus column is
>                       `notReady'."
>               ::= { contextEntry 11 }
> 

The same about contextTable

> 
>           aclStatus OBJECT-TYPE
>               SYNTAX      RowStatus
>               MAX-ACCESS  read-create
>               STATUS      current
>               DESCRIPTION
>                       "The status of this conceptual row in the
>                       aclTable."
>               ::= { aclEntry 6 }
> 
The same about aclTable

>           viewStatus OBJECT-TYPE
>               SYNTAX      RowStatus
>               MAX-ACCESS  read-create
>               STATUS      current
>               DESCRIPTION
>                       "The status of this conceptual row in the
>                       viewTable."
>               ::= { viewEntry 6 }
> 
The same about viewTable


I will ask authors of the Party MIB document would they please
to clarify what policy is implied by current interpretation of this
document in advance, before RFC will be released.

Aleksey