Lines Matching refs:syntax
34 protocol, has a defined syntax that constrains the structure and
36 syntax are not part of the syntax definition but are instead provided
38 argument, an assertion value, which also has a defined syntax. This
148 LDAP protocol [RFC4511], has a defined syntax (i.e., data type) that
150 semantics for values of a syntax are not part of the syntax
153 value, which also has a defined syntax. This document defines a base
200 ABNF rule specified in [RFC4512], except that the syntax and matching
233 The description of each syntax specifies how attribute or assertion
234 values conforming to the syntax are to be represented when
240 The LDAP-specific encoding of a given attribute syntax always
245 specific encoding of a value of an unrecognized syntax is a human-
247 syntax) when it is not reasonable to produce a human-readable
250 Each LDAP syntax is uniquely identified with an object identifier
257 attribute value with a string-based syntax, or the number of octets
259 bound inside of curly braces following the syntax's OBJECT IDENTIFIER
261 [RFC4512]). Such a bound is not considered part of the syntax
268 Directory String syntax can be encoded in more than one octet, since
274 The following ABNF rules are used in a number of the syntax
302 A value of the Attribute Type Description syntax is the definition of
304 syntax is defined by the <AttributeTypeDescription> rule in
309 Type Description syntax. (Note: Line breaks have been added for
320 The LDAP definition for the Attribute Type Description syntax is:
324 This syntax corresponds to the AttributeTypeDescription ASN.1 type
329 A value of the Bit String syntax is a sequence of binary digits. The
330 LDAP-specific encoding of a value of this syntax is defined by the
348 The LDAP definition for the Bit String syntax is:
352 This syntax corresponds to the BIT STRING ASN.1 type from [ASN.1].
356 A value of the Boolean syntax is one of the Boolean values, true or
357 false. The LDAP-specific encoding of a value of this syntax is
362 The LDAP definition for the Boolean syntax is:
366 This syntax corresponds to the BOOLEAN ASN.1 type from [ASN.1].
370 A value of the Country String syntax is one of the two-character
372 specific encoding of a value of this syntax is defined by the
384 The LDAP definition for the Country String syntax is:
388 This syntax corresponds to the following ASN.1 type from [X.520]:
401 A value of the Delivery Method syntax is a sequence of items that
404 encoding of a value of this syntax is defined by the following ABNF:
416 The LDAP definition for the Delivery Method syntax is:
420 This syntax corresponds to the following ASN.1 type from [X.520]:
436 A value of the Directory String syntax is a string of one or more
439 encoding of a value of this syntax is the UTF-8 encoding [RFC3629] of
462 Attribute type definitions using the Directory String syntax should
465 described by ABNF. A new syntax should be defined in such cases.
467 The LDAP definition for the Directory String syntax is:
471 This syntax corresponds to the DirectoryString parameterized ASN.1
492 A value of the DIT Content Rule Description syntax is the definition
494 specific encoding of a value of this syntax is defined by the
511 The LDAP definition for the DIT Content Rule Description syntax is:
516 This syntax corresponds to the DITContentRuleDescription ASN.1 type
521 A value of the DIT Structure Rule Description syntax is the
523 value of this syntax is defined by the <DITStructureRuleDescription>
529 The LDAP definition for the DIT Structure Rule Description syntax is:
534 This syntax corresponds to the DITStructureRuleDescription ASN.1 type
539 A value of the DN syntax is the (purported) distinguished name (DN)
541 syntax is defined by the <distinguishedName> rule from the string
552 The LDAP definition for the DN syntax is:
556 The DN syntax corresponds to the DistinguishedName ASN.1 type from
574 A value of the Enhanced Guide syntax suggests criteria, which consist
577 classes. The Enhanced Guide syntax improves upon the Guide syntax by
580 The LDAP-specific encoding of a value of this syntax is defined by
605 The LDAP definition for the Enhanced Guide syntax is:
612 The Enhanced Guide syntax corresponds to the EnhancedGuide ASN.1 type
629 A value of the Facsimile Telephone Number syntax is a subscriber
631 network. The LDAP-specific encoding of a value of this syntax is
650 The LDAP definition for the Facsimile Telephone Number syntax is:
654 The Facsimile Telephone Number syntax corresponds to the
659 A value of the Fax syntax is an image that is produced using the
661 memo. The LDAP-specific encoding of a value of this syntax is the
664 The LDAP definition for the Fax syntax is:
668 The ASN.1 type corresponding to the Fax syntax is defined as follows,
687 A value of the Generalized Time syntax is a character string
689 of this syntax is a restriction of the format defined in [ISO8601],
721 this syntax.
751 The LDAP definition for the Generalized Time syntax is:
755 This syntax corresponds to the GeneralizedTime ASN.1 type from
761 A value of the Guide syntax suggests criteria, which consist of
764 classes. The Guide syntax is obsolete and should not be used for
767 The LDAP-specific encoding of a value of this syntax is defined by
775 The LDAP definition for the Guide syntax is:
779 The Guide syntax corresponds to the Guide ASN.1 type from [X.520].
793 A value of the IA5 String syntax is a string of zero, one, or more
796 encoding of a value of this syntax is the unconverted string of
799 The LDAP definition for the IA5 String syntax is:
803 This syntax corresponds to the IA5String ASN.1 type from [ASN.1].
807 A value of the Integer syntax is a whole number of unlimited
808 magnitude. The LDAP-specific encoding of a value of this syntax is
819 The LDAP definition for the Integer syntax is:
823 This syntax corresponds to the INTEGER ASN.1 type from [ASN.1].
827 A value of the JPEG syntax is an image in the JPEG File Interchange
829 a value of this syntax is the sequence of octets of the JFIF encoding
832 The LDAP definition for the JPEG syntax is:
836 The JPEG syntax corresponds to the following ASN.1 type:
853 A value of the LDAP Syntax Description syntax is the description of
854 an LDAP syntax. The LDAP-specific encoding of a value of this syntax
857 The LDAP definition for the LDAP Syntax Description syntax is:
861 The above LDAP definition for the LDAP Syntax Description syntax is
862 itself a legal value of the LDAP Syntax Description syntax.
864 The ASN.1 type corresponding to the LDAP Syntax Description syntax is
878 A value of the Matching Rule Description syntax is the definition of
880 syntax is defined by the <MatchingRuleDescription> rule in [RFC4512].
887 the syntax.
889 The LDAP definition for the Matching Rule Description syntax is:
893 This syntax corresponds to the MatchingRuleDescription ASN.1 type
905 A value of the Matching Rule Use Description syntax indicates the
908 of a value of this syntax is defined by the
914 The LDAP definition for the Matching Rule Use Description syntax is:
919 This syntax corresponds to the MatchingRuleUseDescription ASN.1 type
924 A value of the Name and Optional UID syntax is the distinguished name
929 The LDAP-specific encoding of a value of this syntax is defined by
946 The LDAP definition for the Name and Optional UID syntax is:
959 This syntax corresponds to the NameAndOptionalUID ASN.1 type from
964 A value of the Name Form Description syntax is the definition of a
966 specific encoding of a value of this syntax is defined by the
972 The LDAP definition for the Name Form Description syntax is:
976 This syntax corresponds to the NameFormDescription ASN.1 type from
981 A value of the Numeric String syntax is a sequence of one or more
983 syntax is the unconverted string of characters, which conforms to the
993 The LDAP definition for the Numeric String syntax is:
997 This syntax corresponds to the NumericString ASN.1 type from [ASN.1].
1001 A value of the Object Class Description syntax is the definition of
1003 syntax is defined by the <ObjectClassDescription> rule in [RFC4512].
1020 the syntax.
1022 The LDAP definition for the Object Class Description syntax is:
1026 This syntax corresponds to the ObjectClassDescription ASN.1 type from
1031 A value of the Octet String syntax is a sequence of zero, one, or
1033 syntax is the unconverted sequence of octets, which conforms to the
1038 The <OCTET> rule is defined in [RFC4512]. Values of this syntax are
1041 The LDAP definition for the Octet String syntax is:
1045 This syntax corresponds to the OCTET STRING ASN.1 type from [ASN.1].
1049 A value of the OID syntax is an object identifier: a sequence of two
1054 The LDAP-specific encoding of a value of this syntax is defined by
1061 The LDAP definition for the OID syntax is:
1073 This syntax corresponds to the OBJECT IDENTIFIER ASN.1 type from
1078 A value of the Other Mailbox syntax identifies an electronic mailbox,
1080 value of this syntax is defined by the following ABNF:
1092 The LDAP definition for the Other Mailbox syntax is:
1096 The ASN.1 type corresponding to the Other Mailbox syntax is defined
1106 A value of the Postal Address syntax is a sequence of strings of one
1110 The LDAP-specific encoding of a value of this syntax is defined by
1149 The LDAP definition for the Postal Address syntax is:
1153 This syntax corresponds to the PostalAddress ASN.1 type from [X.520];
1164 A value of the Printable String syntax is a string of one or more
1168 The LDAP-specific encoding of a value of this syntax is the
1183 The LDAP definition for the PrintableString syntax is:
1187 This syntax corresponds to the PrintableString ASN.1 type from
1192 A value of the Substring Assertion syntax is a sequence of zero, one,
1199 The LDAP-specific encoding of a value of this syntax is defined by
1222 The Substring Assertion syntax is used only as the syntax of
1224 attribute syntax, or in the SubstringFilter [RFC4511].
1226 The LDAP definition for the Substring Assertion syntax is:
1239 This syntax corresponds to the SubstringAssertion ASN.1 type from
1244 A value of the Telephone Number syntax is a string of printable
1248 The LDAP-specific encoding of a value of this syntax is the
1257 The LDAP definition for the Telephone Number syntax is:
1261 The Telephone Number syntax corresponds to the following ASN.1 type
1271 A value of this syntax specifies the identifier and (optionally)
1274 The LDAP-specific encoding of a value of this syntax is defined by
1300 The LDAP definition for the Teletex Terminal Identifier syntax is:
1305 This syntax corresponds to the TeletexTerminalIdentifier ASN.1 type
1310 A value of the Telex Number syntax specifies the telex number,
1313 The LDAP-specific encoding of a value of this syntax is defined by
1325 The LDAP definition for the Telex Number syntax is:
1329 This syntax corresponds to the TelexNumber ASN.1 type from [X.520].
1333 A value of the UTC Time syntax is a character string representing a
1336 value of this syntax follows the format defined in [ASN.1] for the
1359 strings SHOULD be considered invalid for this syntax.
1369 The LDAP definition for the UTC Time syntax is:
1373 Note: This syntax is deprecated in favor of the Generalized Time
1374 syntax.
1376 The UTC Time syntax corresponds to the UTCTime ASN.1 type from
1413 matching rule specifies the syntax for the assertion value. The
1414 syntax of the assertion value is typically, but not necessarily, the
1415 same as the syntax of the attribute values to which the matching rule
1417 [RFC4511] conforms to the assertion syntax of the equality matching
1418 rule for the attribute type rather than to the assertion syntax of
1425 corresponding ASN.1 type of a candidate attribute syntax must
1463 syntax of the matching rule is the same as the value syntax of the
1509 syntax to an attribute value of a syntax (e.g., the Bit String
1510 syntax) whose corresponding ASN.1 type is BIT STRING.
1519 If the corresponding ASN.1 type of the attribute syntax does not have
1521 syntax), then the rule evaluates to TRUE if and only if the attribute
1539 syntax to an attribute value of a syntax (e.g., the Boolean syntax)
1555 String syntax to an attribute value of a syntax (e.g., the IA5 String
1556 syntax) whose corresponding ASN.1 type is IA5String.
1585 String syntax to an attribute value of a syntax (e.g., the Directory
1586 String, Printable String, Country String, or Telephone Number syntax)
1589 (the other alternatives do not correspond to any syntax defined in
1612 Directory String syntax to an attribute value of a syntax (e.g., the
1614 Number syntax) whose corresponding ASN.1 type is DirectoryString or
1646 Substring Assertion syntax to an attribute value of a syntax (e.g.,
1648 Number syntax) whose corresponding ASN.1 type is DirectoryString or
1676 String syntax to an attribute value of a syntax (e.g., the IA5 String
1677 syntax) whose corresponding ASN.1 type is IA5String.
1707 the Substring Assertion syntax to an attribute value of a syntax
1708 (e.g., the IA5 String syntax) whose corresponding ASN.1 type is
1734 sequence of strings to an attribute value of a syntax (e.g., the
1743 Postal Address syntax) whose corresponding ASN.1 type is a SEQUENCE
1751 In [X.520], the assertion syntax for this matching rule is defined to
1757 Address syntax. The choice of the Postal Address syntax for the
1758 assertion syntax of the caseIgnoreListMatch in LDAP should not be
1760 the Postal Address syntax.
1772 the Substring Assertion syntax to an attribute value of a syntax
1773 (e.g., the Postal Address syntax) whose corresponding ASN.1 type is a
1785 Address syntax, the concatenated string omits the <DOLLAR> line
1806 String syntax to an attribute value of a syntax (e.g., the Directory
1807 String, Printable String, Country String, or Telephone Number syntax)
1831 Directory String syntax to an attribute value of a syntax (e.g., the
1833 Number syntax) whose corresponding ASN.1 type is DirectoryString or
1863 Substring Assertion syntax to an attribute value of a syntax (e.g.,
1865 Number syntax) whose corresponding ASN.1 type is DirectoryString or
1893 value of the Directory String syntax to an attribute value of a
1894 syntax whose corresponding ASN.1 type is a SEQUENCE with a mandatory
1897 Note that the assertion syntax of this matching rule differs from the
1898 attribute syntax of attributes for which this is the equality
1923 attribute values (of an applicable syntax), an assertion value must
1931 syntax to an attribute value of a syntax (e.g., the DN syntax) whose
1970 Generalized Time syntax to an attribute value of a syntax (e.g., the
1971 Generalized Time syntax) whose corresponding ASN.1 type is
1990 an assertion value of the Generalized Time syntax to an attribute
1991 value of a syntax (e.g., the Generalized Time syntax) whose
2008 the Integer syntax to an attribute value of a syntax (e.g., the DIT
2009 Structure Rule Description syntax) whose corresponding ASN.1 type is
2023 Note that the assertion syntax of this matching rule differs from the
2024 attribute syntax of attributes for which this is the equality
2038 (of an applicable syntax), an assertion value must first be derived
2046 syntax to an attribute value of a syntax (e.g., the Integer syntax)
2062 Integer syntax to an attribute value of a syntax (e.g., the Integer
2063 syntax) whose corresponding ASN.1 type is INTEGER.
2087 String syntax to an attribute value of a syntax (e.g., the Directory
2088 String syntax) whose corresponding ASN.1 type is DirectoryString.
2103 Numeric String syntax to an attribute value of a syntax (e.g., the
2104 Numeric String syntax) whose corresponding ASN.1 type is
2138 the Numeric String syntax to an attribute value of a syntax (e.g.,
2139 the Numeric String syntax) whose corresponding ASN.1 type is
2167 the Substring Assertion syntax to an attribute value of a syntax
2168 (e.g., the Numeric String syntax) whose corresponding ASN.1 type is
2205 value of the OID syntax to an attribute value of a syntax (e.g., the
2209 syntax) whose corresponding ASN.1 type is a SEQUENCE with a mandatory
2212 Note that the assertion syntax of this matching rule differs from the
2213 attribute syntax of attributes for which this is the equality
2228 attribute values (of an applicable syntax), an assertion value must
2236 syntax to an attribute value of a syntax (e.g., the OID syntax) whose
2267 String syntax to an attribute value of a syntax (e.g., the Octet
2268 String or JPEG syntax) whose corresponding ASN.1 type is the OCTET
2285 Octet String syntax to an attribute value of a syntax (e.g., the
2286 Octet String or JPEG syntax) whose corresponding ASN.1 type is the
2318 Telephone Number syntax to an attribute value of a syntax (e.g., the
2319 Telephone Number syntax) whose corresponding ASN.1 type is a
2342 of the Substring Assertion syntax to an attribute value of a syntax
2343 (e.g., the Telephone Number syntax) whose corresponding ASN.1 type is
2381 And Optional UID syntax to an attribute value of a syntax (e.g., the
2382 Name And Optional UID syntax) whose corresponding ASN.1 type is
2418 String syntax to an attribute value of a syntax (e.g., the Directory
2419 String syntax) whose corresponding ASN.1 type is DirectoryString.
2760 3. BNF descriptions of syntax formats have been replaced by ABNF
2788 10. The corresponding ASN.1 type for the Other Mailbox syntax has
2791 11. A corresponding ASN.1 type for the LDAP Syntax Description syntax
2794 12. The Binary syntax has been removed because it was not adequately
2819 Identifier syntax has been defined.
2823 [RFC4523] (as is the Supported Algorithm syntax from RFC 2256).
2825 18. The MHS OR Address syntax has been removed since its
2828 19. The DL Submit Permission syntax has been removed as it depends on
2829 the MHS OR Address syntax.
2831 20. The Presentation Address syntax has been removed since its
2841 22. The LDAP Schema Definition syntax (defined in RFC 2927) and the
2842 Mail Preference syntax have been removed on the grounds that they
2873 depends on an assertion syntax (Presentation Address) that is not
2877 depends on an undefined assertion syntax (Protocol Information).