RFC 3727

ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules

📅 published February 2004, from ietf

RFC 3727 📜 ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules 🎀

Okay bestie, here's the title block tea ☕:

RFC number: 3727
Title: ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules
Author: Steven Legg, Adacel Technologies
Category: Standards Track
Date: February 2004
Updates: RFC 3687 (the component matching rules spec)
Obsoletes: nothing listed in the header

Status of This Memo 🌸

This is an Internet standards track protocol document for the Internet community, and it's asking everyone for discussion and suggestions for improvements 🫶. For the current standardization state and status, check the "Internet Official Protocol Standards" (STD 1) doc. Distribution of this memo is unlimited, so share away 💖.

Copyright Notice 🦋

Abstract ✨

Okay so this doc updates the component matching rules spec for LDAP and X.500 directories (RFC3687) 💅. The move is basically gathering all the Abstract Syntax Notation One (ASN.1) definitions of those rules into one properly labeled ASN.1 module, so other specs can reference the rule definitions from inside their own ASN.1 modules. It's giving organization, honestly 🗂️✨.

1. Introduction 🧚

So, the structure or data type of the data stored in an attribute of a Lightweight Directory Access Protocol (LDAP) [LDAP] or X.500 [X500] directory is described by that attribute's syntax. Syntaxes go all over the place 🌈. You've got simple stuff like text strings, integers, and booleans, and then the super complicated ones, like the syntaxes for directory schema operational attributes 🤯. RFC 3687 [CMR] defines a generic way to match user-selected components inside a directory attribute value, no matter how complex the attribute syntax is. Iconic behavior 👑.

This document updates RFC 3687 by collecting the Abstract Syntax Notation One (ASN.1) [ASN1] definitions from RFC 3687 into one properly identified ASN.1 module. That way, other specs can reference these definitions from their own ASN.1 modules. Main character energy for the definitions 🎀.

2. Module Definition for Component Matching 💜

Here's the module, bestie. Every line is copied exactly as written:

   ComponentMatching
       {iso(1) 2 36 79672281 xed(3) module(0) component-matching(4)}

   --  Copyright (C) The Internet Society (2004).  This version of
   --  this ASN.1 module is part of RFC 3727; see the RFC itself
   --  for full legal notices.

   DEFINITIONS
   EXPLICIT TAGS
   EXTENSIBILITY IMPLIED ::= BEGIN

   IMPORTS
       MATCHING-RULE,
       RelativeDistinguishedName
           FROM InformationFramework
               {joint-iso-itu-t ds(5) module(1)
                   informationFramework(1) 4} ;

   ComponentAssertion ::= SEQUENCE {
       component         ComponentReference (SIZE(1..MAX)) OPTIONAL,
       useDefaultValues  BOOLEAN DEFAULT TRUE,
       rule              MATCHING-RULE.&id,
       value             MATCHING-RULE.&AssertionType }

   ComponentReference ::= UTF8String

   ComponentFilter ::= CHOICE {
       item  [0] ComponentAssertion,
       and   [1] SEQUENCE OF ComponentFilter,
       or    [2] SEQUENCE OF ComponentFilter,
       not   [3] ComponentFilter }

   componentFilterMatch MATCHING-RULE ::= {
       SYNTAX  ComponentFilter
       ID      { 1 2 36 79672281 1 13 2 } }

   allComponentsMatch MATCHING-RULE ::= {
       ID      { 1 2 36 79672281 1 13 6 } }

   directoryComponentsMatch MATCHING-RULE ::= {
       ID      { 1 2 36 79672281 1 13 7 } }


   -- Additional Useful Matching Rules --

   rdnMatch MATCHING-RULE ::= {

       SYNTAX  RelativeDistinguishedName
       ID      { 1 2 36 79672281 1 13 3 } }

   presentMatch MATCHING-RULE ::= {
       SYNTAX  NULL
       ID      { 1 2 36 79672281 1 13 5 } }

   END

The InformationFramework ASN.1 module, where MATCHING-RULE and RelativeDistinguishedName get imported from, is defined in X.501 [X501] ✨.

The object identifiers in this doc were assigned for component matching rules by Adacel Technologies. They sit under an arc that Standards Australia gave to Adacel 🇦🇺🫶.

3. Security Considerations 🔐

⚠️ Serious security note, bestie: this document just gathers the ASN.1 definitions of the component matching rules into one module. It does NOT change those definitions in any way. For security considerations of using the component matching rules, see RFC 3687 [CMR]. Go read that one, no skipping 😭.

4. References 📚

4.1. Normative References

   [CMR]   Legg, S., "Lightweight Directory Access Protocol (LDAP) and
           X.500 Component Matching Rules", RFC 3687, February 2004.

   [X501]  ITU-T Recommendation X.501 (1993) | ISO/IEC 9594-2:1994,
           Information Technology - Open Systems Interconnection - The
           Directory: Models

   [ASN1]  ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1:2002,
           Information technology - Abstract Syntax Notation One
           (ASN.1): Specification of basic notation

4.2. Informative References

   [LDAP]  Hodges, J. and R. Morgan, "Lightweight Directory Access
           Protocol (v3): Technical Specification", RFC 3377, September
           2002.

   [X500]  ITU-T Recommendation X.500 (1993) | ISO/IEC 9594-1:1994,
           Information Technology - Open Systems Interconnection - The
           Directory: Overview of concepts, models and services

5. Author's Address 🏡

   Steven Legg
   Adacel Technologies Ltd.
   250 Bay Street
   Brighton, Victoria 3186
   AUSTRALIA

   Phone: +61 3 8530 7710
   Fax:   +61 3 8530 7888
   EMail: steven.legg@adacel.com.au

6. Full Copyright Statement 💅

Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions in BCP 78. Except as set out there, the authors keep all their rights 🔥.

This document and the information in it are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Intellectual Property 🌈

The IETF doesn't take a position on whether any Intellectual Property Rights or other rights claimed to cover the tech in this doc are valid or in scope, or whether licenses for them are available. It also doesn't claim to have independently looked for any such rights 🙈. Info on how RFC rights work is in BCP 78 and BCP 79.

Copies of IPR disclosures sent to the IETF Secretariat, plus any assurances of licenses, or the results of attempts to get a general license for implementers or users of this spec, can be found in the IETF's online IPR repository at http://www.ietf.org/ipr 💜.

The IETF invites anyone to flag any copyrights, patents, patent applications, or other proprietary rights that might cover tech needed to implement this standard. Send that info to the IETF at ietf-ipr@ietf.org 🫶.

Acknowledgement 🍓

Funding for the RFC Editor function is currently provided by the Internet Society. Thank you, Internet Society 🙏✨.

📦 where this page comes from

ietf: rfc3727 2004-02
💖 girlified by claude-haiku-5-5 on 2026-10-16: a language model's rewrite of the original, under its terms