FW: Protocol Action: 'ASN.1 Module Definition for the LDAP & X.5

simao.campos at ITU.INT simao.campos at ITU.INT
Tue Feb 24 05:03:15 EST 2004

Dear colleagues,



-----Original Message-----
From: rfc-editor at rfc-editor.org [mailto:rfc-editor at rfc-editor.org]
Sent: 10 February 2004 19:28
Cc: rfc-editor at rfc-editor.org
Subject: RFC 3687 on Lightweight Directory Access Protocol (LDAP) and
X.500 Component Matching Rules

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

        RFC 3687

        Title:      Lightweight Directory Access Protocol (LDAP)
                    and X.500 Component Matching Rules
        Author(s):  S. Legg
        Status:     Standards Track
        Date:       February 2004
        Mailbox:    steven.legg at adacel.com.au
        Pages:      42
        Characters: 96256
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-legg-ldapext-component-matching-11.txt

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

The syntaxes of attributes in a Lightweight Directory Access Protocol
(LDAP) or X.500 directory range from simple data types, such as text
string, integer, or boolean, to complex structured data types, such as
the syntaxes of the directory schema operational attributes.  Matching
rules defined for the complex syntaxes usually only
provide the most immediately useful matching capability.  This
document defines generic matching rules that can match any user
selected component parts in an attribute value of any arbitrarily
complex attribute syntax.

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 at 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 at RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info at 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 at 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 at 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.

More information about the sg16-avd mailing list