Browse Prior Art Database

MIME Directory Profile for LDAP Schema (RFC2927)

IP.com Disclosure Number: IPCOM000005109D
Original Publication Date: 2000-Sep-01
Included in the Prior Art Database: 2001-Aug-15
Document File: 11 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Wahl: AUTHOR

Abstract

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 text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 20% of the total text.

Network Working Group M. Wahl Request for Comments: 2927 Sun Microsystems, Inc. Category: Informational September 2000

MIME Directory Profile for LDAP Schema

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

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.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [4].

1. Overview

This document defines how a MIME type may be used to transfer a single LDAPv3 schema definition.

A schema for use with LDAPv3 consists of any number of object class, attribute type, matching rule and syntax definitions. These concepts are defined in the LDAPv3 protocol definition [2]. The schema MAY have a numeric OID assigned to it by a schema listing or registration service.

A schema may import definitions from another schema. Schema imports are not, however, transitive.

For example, a schema contains a definition for a "modem" object class, which is to be defined as a subclass of the X.521 "device" object class. In this case, the schema MUST import the definitions of X.521.

Wahl Informational [Page 1]

RFC 2927 MIME Directory Profile for LDAP Schema September 2000

2. The "schema-ldap-0" MIME Directory Profile Registration

This profile is identified by the following registration template information.

To: ietf-mime-direct@imc.org Subject: Registration of text/directory MIME profile "schema-ldap-0"

Profile name: schema-ldap-0

Profile purpose: To represent a schema defined for use with LDAPv3 servers.

Profile types: SOURCE, ldapSchemas, attributeTypes, matchingRules, objectClasses, matchingRuleUse, ldapSyntaxes

Profile special notes:

The charset parameter MUST be present on the MIME content, and the value of this parameter MUST be "utf-8". This ensures that schema values can be used in LDAPv3 attribute values without a character set translation.

Neither the "BEGIN" and "END" types nor type grouping are used in contents of this profile.

All of the types in this profile with the exception of ldapSchemas may be multi-valued. Each value is present on its own contentline. Values may be present in any order, and need not be arranged by type.

The "SOURCE" type is optional, and if values are present they SHOULD be URIs of the "ldap" form. If the URI is of the "ldap" form, the object indicated by the URI is a subschema en...