Re: implementation quiz: ;binary

["Timothy Hahn" <hahnt@us.ibm.com>]

Kurt,

Please provide a separate response for each application of
interest.  There is no need to respond if you have not
implemented ;binary transfer of attribute types.  This is
only a partial quiz aimed at getting a general idea of the
level of interoperability.

Implementor: IBM
Application:  SecureWay Directory (AIX, NT, Solaris, OS/400, OS/390, z/OS)
Application Class: [X] client, [X] server

Have you implemented ;binary transfer of attributes?
Yes

Is this support specific to particular syntaxes and/or attributes?
If so, which syntaxes and attributes?
Yes,
 attributeCertificate,
 authorityRevocationList,
 caCertificate,
 certificateRevocationList,
 crossCertificatePair,
 deltaRevocationList,
 supportedAlgorithms,
 userCertificate,
 userSMIMECertificate only

Do you support non-;binary transfer for any syntax and/or
attribute which you support ;binary transfer for?
No,
 The attributes can be requested without the ";binary"
 option, but what is returned is the binary data for each
 of the values.

Does your application ensure values it sends using ;binary are
restricted to a valid BER encoding of the attribute's syntax?
No.
 Whatever is stored (during the add/modify operation) is what
 is returned.  The values are not checked for a valid BER encoding.

Does your application treat non-BER encoded values received
using ;binary as an error?  If so, what error?
No.

Does your application treat BER encoding of values of incorrect
using ;binary as an error?  If so, what error?
No.

Does your application expect values to be encoded using a
subset of BER?  If so, which subset?
No.

Comments:
It is possible to mark other attributes (Binary syntax only) such
that ";binary" can be requested for those attributes.  This is done
by modifying the schema definition for those attributes.


Regards,
Tim Hahn

Internet: hahnt@us.ibm.com
Internal: Timothy Hahn/Endicott/IBM@IBMUS or IBMUSM00(HAHNT)
phone: 607.752.6388     tie-line: 8/852.6388
fax: 607.752.3681