[Date Prev][Date Next]
Re: AttributeTypeValue and binary
There is no string encoding for userCertificate, thus binary is used. I'll amend the statement to reflect that the default encoding is used regardless of whether it's a string encoding or otherwise.
>>> "Kurt D. Zeilenga" <Kurt@OpenLDAP.org> 1/24/01 6:12:14 PM >>>
At 05:52 PM 1/24/01 -0700, Jim Sermersheim wrote:
>My suggested change is the result of trying to keep the existing wording intact as much as possible, and also not address any issues other than the wrapper confusion. Another wordy possibility is:
>A field of type AttributeValue is an OCTET STRING containing an encoding of the value syntax of the companion attribute type. When the syntax of an attribute type defines a string encoding, that encoding is used unless an option is present in the companion AttributeDescription which overrides the string-based encoding. For example, if the "binary" option is present, the value will be the binary encoding of the value.
>This addresses the "wrapper" issue, the "default encoding" issue, and the "future encodings" issue.
This has the problem in that the default encoding for certificate
is binary. That is, when all attributes are requested and the
entry contains a userCertificate attribute, the attribute should
be returned as userCertificate;binary.