[Date Prev][Date Next]
;binary and *
There needs to a clarification regarding transfer encoding
to use when the attribute was not requested by attribute
description. E.g., by * or an empty attribute list.
I suggest that if "foo" is to returned (when not requested
by attribute description), that the server is to use the
"native" transfer encoding if the server supports such for
that attribute. Otherwise, the server may choose to return
the attribute in any one of the transfer encodings it does
support OR not return the attribute.
Additionally, the TS should say that clients MUST NOT
expect any particular transfer encoding of attributes
which are not requested by attribute description. Where
a client desires a particular transfer encoding, including
the native encoding, the client SHOULD request the
attribute using an attribute description indicating
the desired transfer encoding.
In examples, please avoid use of userCertificate and other
attributes which mandate use of particular transfer