Choose literal, base64 or referenced values
03The punctuation after an attribute name selects how its value is represented. Base64 is a reversible encoding of bytes; it does not encrypt them.
photo:< file:///qa/photo.bin refers to bytes outside the LDIF file. A processor may include those bytes, not the URL text. The picture uses an inert fictional reference and performs no fetch; reading a file still requires deliberate application safety policy.
Source for this drawing: RFC 2849 · Read RFC source: Syntax notes 4–10 and examples 3–5 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
name: introduces a direct safe value; name:: introduces base64; name:< introduces a URL reference. Attribute values containing NUL, CR, LF, non-ASCII bytes or an unsafe initial SPACE, colon or < MUST be base64-encoded when included directly.
- name: introduces a direct safe value; name:: introduces base64; name:< introduces a URL reference. Attribute values containing NUL, CR, LF, non-ASCII bytes or an unsafe initial SPACE, colon or < MUST be base64-encoded when included directly.
- Other direct values MAY be base64-encoded. A trailing SPACE SHOULD be encoded. DirectoryString values and names MUST be valid UTF-8; LDIF generation MUST NOT output invalid UTF-8 for them.
- Base64 has no MIME 76-character wrapping requirement here; only LDIF folding is allowed and extraneous characters are forbidden. File URLs SHOULD be supported, other URL formats MAY be supported with documented semantics. Treat external references as untrusted.
Fictional directory data. Fragments illustrate the format; no file, URL or directory is accessed. Import outcomes still depend on schema, permissions and server support.
Read the RFC section ↗