ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules
Extracted elements (12)
The object identifiers used in the ComponentMatching module were assigned by Adacel Technologies under an arc assigned to Adacel by Standards Australia, rather than being assigned through IANA. This reflects the pre-existing OID assignments from RFC 3687 that this document consolidates without modification.
This document updates RFC 3687 by collecting all ASN.1 definitions of the component matching rules into a single, appropriately identified ASN.1 module. The motivation is to allow other specifications to reference the component matching rule definitions from within their own ASN.1 modules, which was not possible before this consolidation.
allComponentsMatch is a MATCHING-RULE with OID { 1 2 36 79672281 1 13 6 }, defined without an explicit SYNTAX clause. It is used to match against all components of an attribute value.
ComponentAssertion is a SEQUENCE with an optional ComponentReference field (SIZE 1..MAX), a useDefaultValues BOOLEAN defaulting to TRUE, a rule field of type MATCHING-RULE.&id, and a value field of type MATCHING-RULE.&AssertionType. It represents a single component-level assertion against a directory attribute value.
ComponentFilter is a CHOICE type supporting four alternatives: item [0] ComponentAssertion (a leaf assertion), and [1] SEQUENCE OF ComponentFilter (conjunction), or [2] SEQUENCE OF ComponentFilter (disjunction), and not [3] ComponentFilter (negation). This enables Boolean combinations of component assertions.
componentFilterMatch is a MATCHING-RULE with SYNTAX ComponentFilter and OID { 1 2 36 79672281 1 13 2 }. It is the primary matching rule for evaluating ComponentFilter expressions against attribute values.
ComponentReference is defined as a UTF8String, used to identify a specific component within a complex attribute value for matching purposes.
directoryComponentsMatch is a MATCHING-RULE with OID { 1 2 36 79672281 1 13 7 }, defined without an explicit SYNTAX clause. It provides matching for directory-typed components of attribute values.
presentMatch is an additional useful MATCHING-RULE with SYNTAX NULL and OID { 1 2 36 79672281 1 13 5 }. It tests whether a component is present within an attribute value.
rdnMatch is an additional useful MATCHING-RULE with SYNTAX RelativeDistinguishedName and OID { 1 2 36 79672281 1 13 3 }. It supports matching against RDN-typed components within attribute values.
The ComponentMatching ASN.1 module is identified by OID {iso(1) 2 36 79672281 xed(3) module(0) component-matching(4)}. It uses EXPLICIT TAGS and EXTENSIBILITY IMPLIED, and imports MATCHING-RULE and RelativeDistinguishedName from the InformationFramework module defined in X.501.
This document makes no changes to the component matching rule definitions; it only collects them into an ASN.1 module. All security considerations are inherited from RFC 3687, which implementors must consult for the security implications of using component matching rules.