[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: I-D ACTION:draft-ietf-ldapbis-bcp64-00.txt



This is first cut at revising BCP 64.  Aside from numerous
editorial changes, it incorporates the change (descriptors
SHOULD be registered, descriptors in RFCs MUST be registered)
previously detailed in [Models, 6.2] to Section 3.3.

Kurt

At 04:00 AM 6/24/2003, 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           : IANA Considerations for LDAP
>        Author(s)       : K. Zeilenga
>        Filename        : draft-ietf-ldapbis-bcp64-00.txt
>        Pages           : 15
>        Date            : 2003-6-23
>        
>This document provides procedures for registering extensible elements
>of Lightweight Directory Access Protocol (LDAP).  The document also
>provides guidelines to Internet Assigned Numbers Authority (IANA)
>describing conditions under which new values can be assigned.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-bcp64-00.txt
>
>To remove yourself from the IETF Announcement list, send a message to 
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>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-bcp64-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html 
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
>        mailserv@ietf.org.
>In the body type:
>        "FILE /internet-drafts/draft-ietf-ldapbis-bcp64-00.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
>Internet-Draft.
>Content-Type: text/plain
>Content-ID:     <2003-6-23142526.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-ldapbis-bcp64-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-bcp64-00.txt>