Lines Matching refs:binary

35    document defines an attribute option, the binary option, that can be
75    This document defines an attribute option, the binary option, which
82    The binary option was originally defined in RFC 2251 [RFC2251].  The
85    2251.  The binary option was not included in the revised LDAP
90    This document reintroduces the binary option for use with certain
93    the binary option with attributes of syntaxes that do not require its
106    The binary option is indicated with the attribute option string
107    "binary" in an attribute description.  Note that, like all attribute
108    options, the string representing the binary option is case
119    Where the binary option is present in an attribute description, the
126    In terms of the protocol [RFC4511], the binary option specifies that
131    The binary option is not a tagging option [RFC4512], so the presence
132    of the binary option does not specify an attribute subtype.  An
133    attribute description containing the binary option references exactly
134    the same attribute as the attribute description without the binary
137    of the binary option.
140    contains the binary option and the syntax of the attribute does not
144    The presence or absence of the binary option only affects the
153    syntaxes are said to have a binary transfer requirement.  The
155    algorithm syntaxes [RFC4523] are examples of syntaxes with a binary
159    the binary option.  In the absence of this requirement, LDAP clients
185    the binary option, but MUST NOT contain two attribute descriptions
187    only one of them has the binary option).  The binary option in an
192    Attributes of a syntax with the binary transfer requirement, if
193    returned, SHALL be returned in the binary form (i.e., with the binary
195    values BER encoded) regardless of whether the binary option was
199    Attributes of a syntax without the binary transfer requirement, if
202    contains the binary option, then the corresponding attribute in the
203    result SHOULD be in the binary form.  If the attribute description in
204    the request does not contain the binary option, then the
205    corresponding attribute in the result SHOULD NOT be in the binary
218    Attributes of a syntax with the binary transfer requirement, if
219    returned, SHALL be returned in the binary form.
231    Attributes of a syntax without the binary transfer requirement and
233    binary form.
235    Attributes of a syntax without the binary transfer requirement and
237    binary form or omitted from the result.
244    description string "*".  If the binary option is present in at least
246    the request with respect to binary transfer is implementation
264       Option Name: binary