RFC 2927 on MIME Directory Profile for LDAP Schema

RFC Editor <rfc-ed@ISI.EDU> Fri, 22 September 2000 23:35 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28611; Fri, 22 Sep 2000 19:35:46 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id TAA19926 for ietf-123-outbound.10@ietf.org; Fri, 22 Sep 2000 19:25:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA19861 for <all-ietf@loki.ietf.org>; Fri, 22 Sep 2000 19:14:32 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA28270 for <all-ietf@ietf.org>; Fri, 22 Sep 2000 19:14:30 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id QAA08340; Fri, 22 Sep 2000 16:14:31 -0700 (PDT)
Message-Id: <200009222314.QAA08340@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2927 on MIME Directory Profile for LDAP Schema
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 22 Sep 2000 16:14:31 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2927

        Title:	    MIME Directory Profile for LDAP Schema
        Author(s):  M. Wahl
        Status:     Informational
	Date:       September 2000
        Mailbox:    M.Wahl@innosoft.com
        Pages:      10
        Characters: 16122
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-schema-ldap-01.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2927.txt


This document defines a multipurpose internet mail extensions (MIME)
directory profile for holding a lightweight directory access protocol
(LDAP) schema.  It is intended for communication with the Internet
schema listing service.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.
ftp://ftp.isi.edu/in-notes/rfc2927.txt"><ftp://ftp.isi.edu/in-notes/rfc2927.txt>