RFC 4518 on Lightweight Directory Access Protocol (LDAP): Internationalized String Preparation

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

        
        RFC 4518

        Title:      Lightweight Directory Access Protocol (LDAP): 
                    Internationalized String Preparation 
        Author:     K. Zeilenga
        Status:     Standards Track
        Date:       June 2006
        Mailbox:    [email protected]
        Pages:      14
        Characters: 28166
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ldapbis-strprep-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4518.txt

The previous Lightweight Directory Access Protocol (LDAP) technical
specifications did not precisely define how character string matching
is to be performed.  This led to a number of usability and
interoperability problems.  This document defines string preparation
algorithms for character-based matching rules defined for use in LDAP.  [STANDARDS TRACK]

This document is a product of the LDAP (v3) Revision
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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 [email protected].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [email protected].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [email protected] with the message body 

help: ways_to_get_rfcs. For example:

        To: [email protected]
        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 [email protected].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[email protected].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


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

...



_______________________________________________
IETF-Announce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ietf-announce