[rfc-dist] RFC 3727 on ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules

rfc-editor@rfc-editor.org rfc-editor@rfc-editor.org
Thu, 26 Feb 2004 18:10:02 -0800


A new Request for Comments is now available in online RFC libraries.

        RFC 3727

        Title:      ASN.1 Module Definition for the
                    LDAP and X.500 Component Matching Rules
        Author(s):  S. Legg
        Status:     Standards Track
        Date:       February 2004
        Mailbox:    steven.legg@adacel.com.au
        Pages:      5
        Characters: 8297
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-legg-ldap-cmr-module-00.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3727.txt

This document updates the specification of the component matching
rules for Lightweight Directory Access Protocol (LDAP) and X.500
directories (RFC3687) by collecting the Abstract Syntax Notation One
(ASN.1) definitions of the component matching rules into an
appropriately identified ASN.1 module so that other specifications may
reference the component matching rule definitions from within their
own ASN.1 modules.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

Content-Type: Multipart/Alternative; Boundary="OtherAccess"

Content-Type:  Message/External-body;

Content-Type: text/plain
Content-ID: <040226180848.RFC@RFC-EDITOR.ORG>

DOC-ID: rfc3727

Content-Type:   Message/External-body;

Content-Type: text/plain
Content-ID: <040226180848.RFC@RFC-EDITOR.ORG>