[Date Prev][Date Next]
Re: I-D ACTION:draft-ietf-ldapbis-roadmap-05.txt
In this revision, the following substantive changes were
- Added: Extensions are expected to be truly optional.
- Added: Prior LDAP TS includes RFC 3771
(this text is not well formed, will correct in next revision)
- Added: Added [Protocol] includes RFC 3771 portion of prior LDAP TS.
- Added: Other documents may be updated/replaced by portions of
LDAP TS as noted in documents detailing these portions.
(this text will be improved in next revision as well)
At 01:11 PM 6/8/2004, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
> Title : Lightweight Directory Access Protocol (LDAP):
> Technical Specification Road Map
> Author(s) : K. Zeilenga
> Filename : draft-ietf-ldapbis-roadmap-05.txt
> Pages : 7
> Date : 2004-6-8
>The Lightweight Directory Access Protocol (LDAP) is an Internet
>protocol for accessing distributed directory services which act in
>accordance with X.500 data and service models. This document provides
>a roadmap of the LDAP Technical Specification.
>A URL for this Internet-Draft is:
>To remove yourself from the I-D Announcement list, send a message to
>email@example.com with the word unsubscribe in the body of the message.
>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>to change your subscription settings.
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
> "get draft-ietf-ldapbis-roadmap-05.txt".
>A list of Internet-Drafts directories can be found in
>Internet-Drafts can also be obtained by e-mail.
>Send a message to:
>In the body type:
> "FILE /internet-drafts/draft-ietf-ldapbis-roadmap-05.txt".
>NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the