LDAP
Click on the red underlined text to get to the source
...
The Lightweight Directory Access Protocol (LDAP) [1] requires that
the contents of AttributeValue ...
... LDAPv3, and the
rules by which attribute values of these syntaxes are represented as
octet strings for transmission in the LDAP protocol. The syntaxes
defined in this document are referenced by this and other documents
that define attribute types. This document also defines the set of
attribute ...
... defined in this document are referenced by this and other documents
that define attribute types. This document also defines the set of
attribute types which LDAP servers should support.
...
... (where assigned and known by the implementation) SHOULD be used in
preference to numeric oids to the greatest extent possible. Examples
of object descriptors in LDAP are attribute type, object class and
matching rule ...
... Schema developers MUST NOT create attribute definitions whose names
conflict with attributes defined for use with LDAP in existing
standards-track RFCs.
...
... that the syntax field in an AttributeTypeDescription be a string
representation of an OBJECT IDENTIFIER for the LDAP string syntax
definition, and an optional indication of the maximum length of a
value of this attribute (defined in section 4.3.2).
...
...
This section defines general requirements for LDAP attribute value
syntax encodings. All documents defining attribute syntax encodings ...
... encodings. All documents defining attribute syntax encodings
for use with LDAP are expected to conform to these requirements.
...
... defining non-binary values should produce strings that can be
displayed with little or no translation by clients implementing LDAP.
There are a few cases (e.g. audio) however, when it is not sensible
...
... binary encoding is requested by
the client for an attribute, or if the attribute syntax name is
"1.3.6.1.4.1.1466.115.121.1.5". The contents of the LDAP
AttributeValue or AssertionValue ...
...
Syntaxes for use with LDAP are named by OBJECT IDENTIFIERs, which are
dotted-decimal strings. These are not intended to be displayed to
...
... JPEG N 1.3.6.1.4.1.1466.115.121.1.28
LDAP Syntax Description Y 1.3.6.1.4.1.1466.115.121.1.54
LDAP Schema Definition Y 1.3.6.1.4.1.1466.115.121.1.56
...
... LDAP Syntax Description Y 1.3.6.1.4.1.1466.115.121.1.54
LDAP Schema Definition Y 1.3.6.1.4.1.1466.115.121.1.56
LDAP Schema Description Y 1.3.6.1.4.1.1466.115.121.1.57
...
... LDAP Schema Definition Y 1.3.6.1.4.1.1466.115.121.1.56
LDAP Schema Description Y 1.3.6.1.4.1.1466.115.121.1.57
Master And Shadow Access Points Y 1.3.6.1.4.1.1466.115.121.1.29
...
...
These are described as sample values for the subschema
"objectClasses" attribute for a server which implements the LDAP
schema. While lines have been folded for readability, the values
transferred in protocol would not contain newlines.
...
... create object class definitions whose
names conflict with attributes defined for use with LDAP in existing
standards-track RFCs.
...
...
All LDAP server implementations MUST recognize the attribute types
defined in this section.
...
... LDAP Operational Attributes ...
... contexts which this
server masters or shadows. If the server does not master any
information (e.g. it is an LDAP gateway to a public X.500 directory)
...
... Clients may cache this information in case their preferred
LDAP server later becomes unavailable.
...
...
The values of this attribute are the versions of the LDAP protocol
which the server implements.
...
... LDAP Subschema Attribute ...
... LDAP Syntax Description ...
...
( 1.3.6.1.4.1.1466.115.121.1.54 DESC 'LDAP Syntax Description' )
...
... AttributeValue value from its X.501 form to
an LDAP string representation are not always reversible back to the
same BER ...
... RDN with one AVA,
in which the type is commonName and the value is of the TeletexString
choice with the letters 'Sam' would be represented in LDAP as the
string CN=Sam. Another distinguished name ...
... value SHOULD NOT use the string representation of attribute syntaxes
when converting a value to LDAP format. Instead it SHOULD use the
...