Network Working Group M. Wahl
Request for Comments: 2927 Sun Microsystems, Inc.
Category: Informational September 2000
Network Working Group M. Wahl
Request for Comments: 2927 Sun Microsystems, Inc.
Category: Informational September 2000
MIME Directory Profile for LDAP Schema
LDAP架构的MIME目录配置文件
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.
版权所有（C）互联网协会（2000年）。版权所有。
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.
本文档定义了一个多用途internet邮件扩展（MIME）目录配置文件，用于保存轻量级目录访问协议（LDAP）架构。它用于与Internet模式列表服务通信。
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[4]中所述进行解释。
This document defines how a MIME type may be used to transfer a single LDAPv3 schema definition.
本文档定义了如何使用MIME类型传输单个LDAPv3架构定义。
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.
与LDAPv3一起使用的模式由任意数量的对象类、属性类型、匹配规则和语法定义组成。这些概念在LDAPv3协议定义[2]中定义。模式列表或注册服务可以为其分配数字OID。
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.
例如，模式包含“调制解调器”对象类的定义，该对象类将被定义为X.521“设备”对象类的子类。在这种情况下，模式必须导入X.521的定义。
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"
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME profile "schema-ldap-0"
Profile name: schema-ldap-0
配置文件名称：schema-ldap-0
Profile purpose: To represent a schema defined for use with LDAPv3 servers.
概要文件用途：表示为与LDAPv3服务器一起使用而定义的架构。
Profile types: SOURCE, ldapSchemas, attributeTypes, matchingRules, objectClasses, matchingRuleUse, ldapSyntaxes
配置文件类型：源、ldapSchemas、AttributeType、matchingRules、ObjectClass、matchingRuleUse、LDAPSyntax
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.
字符集参数必须出现在MIME内容上，并且该参数的值必须为“utf-8”。这确保了架构值可以在LDAPv3属性值中使用，而无需进行字符集转换。
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.
此配置文件中的所有类型（ldapSchemas除外）都可能是多值的。每个值都存在于其自己的内容行中。值可以以任何顺序出现，无需按类型排列。
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 entry. The use of other forms are reserved for future applications.
“源”类型是可选的，如果存在值，则它们应该是“ldap”形式的URI。如果URI是“ldap”形式，则URI指示的对象是子模式条目。其他表格的使用保留供将来使用。
In this version of the profile, exactly one value of the ldapSchemas type MUST be present. (Later versions of the profile may permit multiple ldapSchemas values to be present in a content.)
在此版本的配置文件中，必须仅存在一个ldapSchemas类型的值。（配置文件的更高版本可能允许内容中存在多个ldapSchemas值。）
Implementors should note that there will likely be values of the profile types in most contents much longer than 76 bytes. In addition, there may be non-ASCII characters and embedded CRLFs inside of values, which could require either quoting of the value or use of a content transfer encoding.
实现者应该注意，在大多数内容中可能会有超过76字节的概要文件类型值。此外，值中可能有非ASCII字符和嵌入的CRLF，这可能需要引用值或使用内容传输编码。
If a contentline in a particular content contains a "context" parameter and the value of that parameter is not "ldap", then that contentline SHOULD be ignored.
如果特定内容中的内容行包含“context”参数，且该参数的值不是“ldap”，则应忽略该内容行。
Intended usage: COMMON
预期用途：普通
This document defines all the types, with the exception of "SOURCE" used in the schema-ldap-0 profile. The "SOURCE" type is defined in [1]. These types are primarily intended for use in the "schema-ldap-0" directory profile, although they may be applicable to other profiles defined in the future.
本文档定义了所有类型，schema-ldap-0概要文件中使用的“SOURCE”除外。[1]中定义了“源”类型。这些类型主要用于“schema-ldap-0”目录配置文件，尽管它们可能适用于将来定义的其他配置文件。
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type ldapSchemas
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type ldapSchemas
Type name: ldapSchemas
类型名称：ldapSchemas
Type purpose: To represent the LDAPv3 attribute "ldapSchemas", defined in section A.1.
类型用途：表示第A.1节中定义的LDAPv3属性“ldapSchemas”。
Type encoding: 8bit
类型编码：8位
Type valuetype: text, encoded according to the BNF of section A.2.
类型值类型：文本，根据第A.2节的BNF编码。
Type special notes: Each value of this type specifies the contents of an LDAP schema definition. A definition of each object class, attribute, matching rule, matching rule use and syntax referenced in a value of ldapSchemas MUST either be defined in one of the schemas referenced in the "IMPORTS" field, or present in the content containing this value.
类型特殊注释：此类型的每个值都指定LDAP模式定义的内容。ldapSchemas值中引用的每个对象类、属性、匹配规则、匹配规则使用和语法的定义必须在“导入”字段中引用的模式之一中定义，或出现在包含此值的内容中。
Intended usage: COMMON
预期用途：普通
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type attributeTypes
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type attributeTypes
Type name: attributeTypes
类型名称：AttributeType
Type purpose: To represent the LDAPv3 attribute "attributeTypes", defined in section 5.1.6 of [4].
类型用途：表示[4]第5.1.6节中定义的LDAPv3属性“AttributeType”。
Type encoding: 8bit
类型编码：8位
Type valuetype: text, encoded according to the BNF of "AttributeTypeDescription" given in section 4.2 of [4].
Type valuetype：文本，根据[4]第4.2节中给出的“AttributeTypeDescription”的BNF编码。
Type special notes: Each value of the type specifies one LDAPv3 attribute type definition. The syntax and matching rules referenced in a value of attributeTypes MUST either be present in this content, or defined in one of the schemas referenced in the "IMPORTS" field of the ldapSchemas line.
类型特殊说明：该类型的每个值指定一个LDAPv3属性类型定义。AttributeType值中引用的语法和匹配规则必须在此内容中存在，或者在ldapSchemas行的“IMPORTS”字段中引用的模式之一中定义。
Intended usage: COMMON
预期用途：普通
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type matchingRules
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type matchingRules
Type name: matchingRules
类型名称：匹配规则
Type purpose: To represent the LDAPv3 attribute "matchingRules", defined in section 5.1.8 of [4].
类型用途：表示[4]第5.1.8节中定义的LDAPv3属性“matchingRules”。
Type encoding: 8bit
类型编码：8位
Type valuetype: text, encoded according to the BNF of "MatchingRuleDescription" given in section 4.5 of [4].
类型值类型：文本，根据[4]第4.5节中给出的“MatchingRuleDescription”的BNF编码。
Type special notes: Each value of the type specifies one matching rule definition. The syntax reference in a value of matchingRules MUST either be present in this content, or defined in one of the schemas referenced in the "IMPORTS" field of the ldapSchemas line.
类型特殊注释：类型的每个值指定一个匹配规则定义。matchingRules值中的语法引用必须在此内容中存在，或者在ldapSchemas行的“IMPORTS”字段中引用的模式之一中定义。
Intended usage: COMMON
预期用途：普通
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type objectClasses
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type objectClasses
Type name: objectClasses
类型名称：objectClasses
Type purpose: To represent the LDAPv3 attribute "objectClasses", defined in section 5.1.7 of [4].
类型用途：表示[4]第5.1.7节中定义的LDAPv3属性“ObjectClass”。
Type encoding: 8bit
类型编码：8位
Type valuetype: text, encoded according to the BNF of "ObjectClassDescription" given in section 4.4 of [4].
类型值类型：文本，根据[4]第4.4节中给出的“ObjectClassDescription”的BNF编码。
Type special notes: Each value of the type specifies one LDAPv3 object class definition. The attributes and object classes referenced in a value of objectClasses MUST either be present in this content, or defined in one of the schema referenced in the "IMPORTS" field of the ldapSchemas line.
类型特殊说明：该类型的每个值指定一个LDAPv3对象类定义。ObjectClass值中引用的属性和对象类必须在此内容中存在，或者在ldapSchemas行的“IMPORTS”字段中引用的模式之一中定义。
Intended usage: COMMON
预期用途：普通
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type matchingRuleUse
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type matchingRuleUse
Type name: matchingRuleUse
类型名称：matchingRuleUse
Type purpose: To represent the LDAPv3 attribute "matchingRuleUse", defined in section 5.1.9 of [4].
类型用途：表示[4]第5.1.9节中定义的LDAPv3属性“matchingRuleUse”。
Type encoding: 8bit
类型编码：8位
Type valuetype: text, encoded according to the BNF of "MatchingRuleUseDescription" given in section 4.5 of [4].
类型值类型：文本，根据[4]第4.5节中给出的“MatchingRuleUseDescription”的BNF编码。
Type special notes: Each value of the type specifies a relationship between a matching rule and attribute types. The matching rule and attribute types referenced in a value of matchingRuleUse MUST either be present in this content, or defined in one of the schemas referenced in the "IMPORTS" statement of the ldapSchemas line.
类型特殊注释：类型的每个值指定匹配规则和属性类型之间的关系。matchingRuleUse值中引用的匹配规则和属性类型必须在此内容中存在，或者在ldapSchemas行的“IMPORTS”语句中引用的模式之一中定义。
Intended usage: COMMON
预期用途：普通
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type ldapSyntaxes
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type ldapSyntaxes
Type name: ldapSyntaxes
类型名称：ldapSyntaxes
Type purpose: To represent the LDAPv3 attribute "ldapSyntaxes", defined in section 5.3.1 of [3].
类型用途：表示[3]第5.3.1节中定义的LDAPv3属性“ldapSyntaxes”。
Type encoding: 8bit
类型编码：8位
Type valuetype: text, encoded according to the BNF of "SyntaxDescription" given in section 4.3.3 of [3].
类型值类型：文本，根据[3]第4.3.3节中给出的“SyntaxDescription”的BNF编码。
Type special notes: Each value of this type specifies a single LDAPv3 attribute value syntax.
类型特殊说明：此类型的每个值都指定一个LDAPv3属性值语法。
Intended usage: COMMON
预期用途：普通
From: Whomever@wherever.com
To: Someone@somewhere.com
Subject: schema information
MIME-Version: 1.0
Message-Id: <ids1@wherever.com>
Content-Type: text/directory; profile="schema-ldap-0";charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable
ldapSchemas: ( 1.2.3.4 NAME 'bogus schema' CLASSES ( top $ thing ) =
ATTRIBUTES ( objectClass $ name ) SYNTAXES ( =
1.3.6.1.4.1.1466.115.121.1.38 $ 1.3.6.1.4.1.1466.115.121.1.15 ) )
attributeTypes: ( 2.5.4.0 NAME 'objectClass' SYNTAX =
1.3.6.1.4.1.1466.115.121.1.38 )
objectClasses: ( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass )
attributeTypes: ( 2.5.4.41 NAME 'name' SYNTAX =
1.3.6.1.4.1.1466.115.121.1.15{32768} )
objectClasses: ( 2.5.6.999 NAME 'thing' MUST name )
ldapSyntaxes: ( 1.3.6.1.4.1.1466.115.121.1.15 DESC 'String' )
ldapSyntaxes: ( 1.3.6.1.4.1.1466.115.121.1.38 DESC 'OID' )
From: Whomever@wherever.com
To: Someone@somewhere.com
Subject: schema information
MIME-Version: 1.0
Message-Id: <ids1@wherever.com>
Content-Type: text/directory; profile="schema-ldap-0";charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable
ldapSchemas: ( 1.2.3.4 NAME 'bogus schema' CLASSES ( top $ thing ) =
ATTRIBUTES ( objectClass $ name ) SYNTAXES ( =
1.3.6.1.4.1.1466.115.121.1.38 $ 1.3.6.1.4.1.1466.115.121.1.15 ) )
attributeTypes: ( 2.5.4.0 NAME 'objectClass' SYNTAX =
1.3.6.1.4.1.1466.115.121.1.38 )
objectClasses: ( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass )
attributeTypes: ( 2.5.4.41 NAME 'name' SYNTAX =
1.3.6.1.4.1.1466.115.121.1.15{32768} )
objectClasses: ( 2.5.6.999 NAME 'thing' MUST name )
ldapSyntaxes: ( 1.3.6.1.4.1.1466.115.121.1.15 DESC 'String' )
ldapSyntaxes: ( 1.3.6.1.4.1.1466.115.121.1.38 DESC 'OID' )
A MIME body part containing an text/directory of the schema-ldap-0 profile may be incorporated in a digitally signed MIME content, which can be used to verify that the body part has not been modified in transit. When the signer has been certified by a trusted third party service, it may also be possible to verify the origin of the content.
包含schema-ldap-0配置文件的文本/目录的MIME正文部分可以合并到数字签名的MIME内容中，该内容可用于验证正文部分在传输过程中未被修改。当签名者已通过可信第三方服务认证时，还可以验证内容的来源。
[1] Howes, T., Smith, M. and F. Dawson, "A MIME Content-Type for Directory Information", RFC 2425, September 1998.
[1] Howes，T.，Smith，M.和F.Dawson，“目录信息的MIME内容类型”，RFC2425，1998年9月。
[2] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3)", RFC 2251, December 1997.
[2] Wahl，M.，Howes，T.和S.Kille，“轻量级目录访问协议（v3）”，RFC 2251，1997年12月。
[3] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997.
[3] Wahl，M.，Coulbeck，A.，Howes，T.和S.Kille，“轻量级目录访问协议（v3）：属性语法定义”，RFC2252，1997年12月。
[4] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[4] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
Mark Wahl Sun Microsystems, Inc. 8911 Capital of Texas Hwy Suite 4140 Austin, TX 78759 USA
Mark Wahl Sun Microsystems，Inc.德克萨斯州首府8911号高速公路4140室德克萨斯州奥斯汀78759
EMail: Mark.Wahl@sun.com
EMail: Mark.Wahl@sun.com
This appendix defines two new attributes which could be present in an subschema entry. These attributes could be added to a future revision of the LDAP attribute definition [3].
本附录定义了子模式条目中可能存在的两个新属性。这些属性可以添加到LDAP属性定义的未来版本中[3]。
( 1.3.6.1.4.1.1466.101.120.17 NAME 'ldapSchemas' SYNTAX 1.3.6.1.4.1.1466.115.121.1.56 USAGE directoryOperation )
（1.3.6.1.4.1.1466.101.120.17名称“ldapSchemas”语法1.3.6.1.4.1.1466.115.121.1.56使用指南操作）
Each value of the ldapSchemas attribute defines one schema. Its syntax, given in section A.2, contains the elements needed for an LDAPv3 server to correctly process operations which use the definitions from this syntax.
ldapSchemas属性的每个值定义一个模式。其语法（见A.2节）包含LDAPv3服务器正确处理使用此语法定义的操作所需的元素。
( 1.3.6.1.4.1.1466.115.121.1.56 DESC 'LDAP Schema Definition' )
（1.3.6.1.4.1.1466.115.121.1.56描述“LDAP模式定义”）
Values in this syntax are represented according to the following BNF:
此语法中的值根据以下BNF表示：
LdapSchema = "(" whsp
numericoid whsp
[ "NAME" qdescrs ]
[ "OBSOLETE" whsp ]
[ "IMPORTS" oids ]
[ "CLASSES" oids ]
[ "ATTRIBUTES" oids ]
[ "MATCHING-RULES" oids ]
[ "SYNTAXES" oids ]
whsp ")"
LdapSchema = "(" whsp
numericoid whsp
[ "NAME" qdescrs ]
[ "OBSOLETE" whsp ]
[ "IMPORTS" oids ]
[ "CLASSES" oids ]
[ "ATTRIBUTES" oids ]
[ "MATCHING-RULES" oids ]
[ "SYNTAXES" oids ]
whsp ")"
The numericoid field uniquely identifies the schema. A new OID should be assigned if any of the fields of the schema change. It is not possible to import definitions from a schema until an OID has been assigned to it.
numericoid字段唯一标识架构。如果架构的任何字段发生更改，则应分配新的OID。在为架构分配OID之前，无法从架构导入定义。
The "NAME" field contains optional human-readable labels for the schema.
“NAME”字段包含模式的可选人类可读标签。
The "OBSOLETE" field is present if the schema is obsolete.
如果架构已过时，则会出现“过时”字段。
The "IMPORTS" field lists the OIDs of other schemas which are to be incorporated by reference into this schema. It is an error to have an attribute type or object class defined in a schema with the same name but a different OID as an attribute type or object class in an
“IMPORTS”字段列出了要通过引用合并到此架构中的其他架构的OID。在架构中定义的属性类型或对象类的名称与架构中的属性类型或对象类的名称相同，但OID不同，这是错误的
imported schema. It is also an error to import from two schema definitions in which there are attribute types or object classes with the same names but different OIDs.
导入的架构。从两个模式定义导入时也会出错，在这两个模式定义中，属性类型或对象类的名称相同，但OID不同。
The "CLASSES" field lists the OIDs of object classes defined in this schema. A schema need not contain any object class definitions. A schema must not contain two object class definitions of the same name but with different OIDs.
“类”字段列出了在此模式中定义的对象类的OID。架构不需要包含任何对象类定义。架构不能包含两个同名但OID不同的对象类定义。
The "ATTRIBUTES" field lists the OIDs of attribute types defined in this schema. A schema need not contain any object class definitions. A schema must not contain two attribute type definitions of the same name but with different OIDs.
“ATTRIBUTES”（属性）字段列出此架构中定义的属性类型的OID。架构不需要包含任何对象类定义。架构不能包含两个同名但OID不同的属性类型定义。
The "MATCHING-RULES" field lists the OIDs of matching rules defined in this schema. A schema need not contain any matching rules.
“MATCHING-RULES”字段列出了在此架构中定义的匹配规则的OID。架构不需要包含任何匹配规则。
The "SYNTAXES" field lists the OIDs of syntaxes defined in this schema. A schema need not contain any syntaxes.
“语法”字段列出此架构中定义的语法的OID。模式不需要包含任何语法。
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。