Re: [Isms] (D)TLS question (#1): selecting a client certificate to use

[Wes Hardaker <wjhns1 at hardakers.net>]

>>>>> On Tue, 30 Jun 2009 23:25:26 -0400, "Donati Andrew-MGIA0477" <adonati at motorola.com> said:

Donati,

Thanks for the response and the opinion.

DA> -- Since RowStatus and StorageType are already present the
DA> snmpTargetParams table, it may be conflicting to have these columns
DA> duplicated in the augmenting tlstmParams table.  

I don't think so.  Not every row in the snmpTargetParams table will have
an entry in the tlstmParamsTable so creation needs to be managed
independently.  It could be done either way, you're right but I think it
makes more sense to have a separate creation/deletion object.  Other
opinions are welcome on the subject though.

However, it shouldn't be an AUGMENT in the first place.  I've changed
the next to be an identical copy of the snmpTargetParamsTable index
since it's not a 1:1 mapping, which rules out AUGMENT usage in the first
place.

Regardless the fate sharing needs to be documented better than it is
currently so I'll work on the wording for that.

DA> Note that the tlstmParamsRowStatus description states that "The
DA> value of this object has no effect on whether other objects in this
DA> conceptual row can be modified" and the values for objects in the
DA> snmpTargetParams table cannot be set if the RowStatus is active.

Well, I suppose that I should copy that table's method of modification
method you're right.

DA> -- The tlstmParamsHashValue object may need to have a default value
DA> defined.    

Well, it'd have to default to "" which isn't helpful.  I think I'd
rather state that the row can't be made active unless the values are
legally set.  There is no sensible default value.


How's this for new text for the tlstmParamsRowStatus object:

tlstmParamsRowStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The status of this conceptual row.  This object may be used
        to create or remove rows from this table.

        To create a row in this table, a manager must
        set this object to either createAndGo(4) or
        createAndWait(5).

        Until instances of all corresponding columns are
        appropriately configured, the value of the
        corresponding instance of the tlstmParamsRowStatus
        column is 'notReady'.

        In particular, a newly created row cannot be made
        active until the corresponding
        tlstmParamsClientHashType,
        and tlstmParamsClientHashValue have both been set.

        The row may not be made active(1) if the
        tlstmParamsClientHashValue object is not of a length suitable
        for use with the corresponding tlstmParamsClientHashType.

        The following objects may not be modified while the
        value of this object is active(1):
            - tlstmParamsClientHashType
            - tlstmParamsClientHashValue
        An attempt to set these objects while the value of
        tlstmParamsRowStatus is active(1) will result in
        an inconsistentValue error.

        The value of this object has no effect on whether
        other objects in this conceptual row can be modified.

        If this row is deleted it has no effect on the corresponding
        row in the tlstmParamsTable.

	If the corresponding row in the tlstmParamsTable is deleted
	then this row must be automatically removed."

-- 
Wes Hardaker
Cobham Analytic Solutions