Network Working Group T. Howes
Request for Comments: 2425 M. Smith
Category: Standards Track Netscape Communications Corp.
F. Dawson
Lotus Development Corporation
September 1998
A MIME Content-Type for Directory Information
目录信息的 MIME 内容类型
Status of this Memo
本备忘录的地位
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件为互联网社区规定了一个互联网标准跟踪协议，并请求讨论和提出改进建议。有关本协议的标准化状况和状态，请参阅当前版本的 "互联网官方协议标准"（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权声明
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有 (C) 互联网协会 (1998)。保留所有权利。
This document defines a MIME Content-Type for holding directory information. The definition is independent of any particular directory service or protocol. The text/directory Content-Type is defined for holding a variety of directory information, for example, name, or email address, or logo. The text/directory Content-Type can also be used as the root body part in a multipart/related Content-Type for handling more complicated situations, especially those in which non-textual information that already has a natural MIME representation, for example, a photograph or sound, is to be represented.
本文件定义了一种用于保存目录信息的 MIME 内容类型。该定义与任何特定的目录服务或协议无关。文本/目录内容类型被定义为用于保存各种目录信息，如名称、电子邮件地址或徽标。文本/目录内容类型还可用作多art/相关内容类型的根主体部分，用于处理更复杂的情况，特别是那些已经有自然 MIME 表示法的非文本信息（如照片或声音）需要表示的情况。
The text/directory Content-Type defines a general framework and format for holding directory information in a simple "type:value" form. We refer to "type" in this context meaning a property or attribute with which the value is associated. Mechanisms are defined to specify alternate languages, encodings and other meta-information. This document also defines the procedure by which particular formats, called profiles, for carrying application-specific information within a text/directory Content-Type can be defined and registered, and the conventions such formats must follow. It is expected that other documents will be produced that define such formats for various applications (e.g., white pages).
文本/目录 Content-Type 定义了以简单的 "类型：值 "形式保存目录信息的一般框架和格式。这里的 "类型 "指的是与值相关联的属性或属性。本文件定义了指定替代语言、编码和其他元信息的机制。本文件还定义了在文本/目录 Content-Type 中承载特定应用信息的特定格式（称为配置文件）的定义和注册过程，以及这些格式必须遵循的约定。预计还将编制其他文件，为各种应用（如白页）定义此类格式。
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].
本文档中的关键词 "MUST"、"MUST NOT"、"REQUIRED"、"SHALL"、"SHALL NOT"、"SHOULD"、"SHOULD NOT"、"RECOMMENDED"、"MAY "和 "OPTIONAL "应按照 [RFC-2119] 中的描述进行解释。
Status of the Memo................................................ 1
Copyright Notice.................................................. 1
1. Abstract...................................................... 1
2. Table of Contents............................................. 2
3. Need for a MIME Directory Type................................ 3
4. Overview...................................................... 4
5. The text/directory Content-Type............................... 4
5.1. MIME media type name........................................ 4
5.2. MIME subtype name........................................... 5
5.3. Required parameters......................................... 5
5.4. Optional parameters......................................... 5
5.5. Encoding considerations..................................... 5
5.6. Security considerations..................................... 6
5.7. Interoperability considerations............................. 6
5.8. Published specification..................................... 6
5.8.1. Line delimiting and folding............................... 6
5.8.2. ABNF content-type definition.............................. 7
5.8.3. Pre-defined Parameters.................................... 9
5.8.4. Pre-defined Value Types...................................11
5.9. Applications which use this media type......................14
5.10. Additional information.....................................14
5.11. Person & email address to contact for further information..14
5.12. Intended usage.............................................14
5.13. Author/Change controller...................................15
6. Predefined Types..............................................15
6.1. SOURCE Type Definition......................................15
6.2. NAME Type Definition........................................16
6.3. PROFILE Type Definition.....................................16
6.4. BEGIN Type Definition.......................................17
6.5. END Type Definition.........................................17
7. Use of the multipart/related Content-Type.....................18
8. Examples.......................................................18
8.1. Example 1...................................................19
8.2. Example 2...................................................19
8.3. Example 3...................................................20
8.4. Example 4...................................................21
9. Registration of new profiles..................................22
9.1. Define the profile..........................................22
9.2. Post the profile definition.................................23
9.3. Allow a comment period......................................23
9.4. Submit the profile for approval.............................23
10. Profile Change Control.......................................23
11. Registration of new types....................................24
11.1. Define the type............................................24
11.2. Post the type definition...................................25
11.3. Allow a comment period.....................................25
11.4. Submit the type for approval...............................25
12. Type Change Control..........................................25
13. Registration of new parameters...............................26
13.1. Define the parameter.......................................26
13.2. Post the parameter definition..............................27
13.3. Allow a comment period.....................................27
13.4. Submit the parameter for approval..........................27
14. Parameter Change Control.....................................28
15. Registration of new value types..............................28
15.1. Define the value type......................................28
15.2. Post the value type definition.............................29
15.3. Allow a comment period.....................................29
15.4. Submit the value type for approval.........................29
16. Security Considerations......................................30
17. Acknowledgements..............................................30
18. References....................................................30
19. Authors' Addresses...........................................32
20. Full Copyright Statement......................................33
For purposes of this document, a directory is a special-purpose database that contains typed information. A directory usually supports both read and search of the information it contains, and can support creation and modification of the information as well. Directory information is usually accessed far more often than it is updated. Directories can be local or global in scope. They can be distributed or centralized. The information they contain can be replicated, with weak or strong consistency requirements.
在本文件中，目录是一种包含键入信息的特殊用途数据库。目录通常支持对所含信息的读取和搜索，也支持信息的创建和修改。目录信息的访问频率通常远远高于更新频率。目录的范围可以是本地的，也可以是全球的。目录可以是分布式的，也可以是集中式的。目录所包含的信息可以复制，一致性要求可以很弱，也可以很强。
There are several situations in which users of Internet mail might wish to exchange directory information: the email analogy of a "business card" exchange; the conveyance of directory information to a user having only email access to the Internet; the provision of machine-parseable address information when purchasing goods or services over the Internet; etc. As MIME [RFC-2045, RFC-2046] is used increasingly by other protocols, most notably HTTP, it can also be useful for these protocols to carry directory information in MIME format. Such a format, for example, could be used to represent URC (uniform resource characteristics) information about resources on the World Wide Web, or to provide a rudimentary directory service over HTTP.
互联网邮件用户可能希望在以下几种情况下交换目录信息：通过电子邮件交换 "名片"；向只能通过电子邮件访问互联网的用户传递目录信息；在通过互联网购买商品或服务时提供机器可解析的地址信息等。由于 MIME [RFC-2045, RFC-2046]越来越多地被其他协议（尤其是 HTTP）使用，因此这些协议以 MIME 格式传输目录信息也是非常有用的。例如，这种格式可用于表示有关万维网资源的 URC（统一资源特征）信息，或通过 HTTP 提供基本的目录服务。
The scheme defined here for representing directory information in a MIME Content-Type has two parts. First, the text/directory Content-Type is defined for use in holding directory information within a single body part, for example name, title, or email address. In its simplest form, the format uses a "type:value" approach, which should be easily parseable by existing MIME implementations and understandable by users. More complicated situations can be represented also. This document defines the general form the information in the Content-Type should have, and the procedure by which specific types and values (properties) for particular applications can be defined. The framework is general enough to handle information from any number of end directory services, including LDAP [RFC-1777, RFC-1778], WHOIS++ [RFC-1835], and X.500 [X500].
这里定义的在 MIME 内容类型中表示目录信息的方案包括两个部分。首先，文本/目录内容类型（text/directory Content-Type）是为在单个主体部分（如名称、标题或电子邮件地址）中保存目录信息而定义的。该格式最简单的形式是使用 "类型：值 "方法，现有的 MIME 实现应能轻松解析，用户也能理解。更复杂的情况也可以表示。本文件定义了内容类型（Content-Type）中信息的一般形式，以及为特定应用定义具体类型和值（属性）的程序。该框架的通用性足以处理来自任何终端目录服务的信息，包括 LDAP [RFC-1777, RFC-1778]、WHOIS++ [RFC-1835] 和 X.500 [X500]。
Directory entries can include far more than just textual information. Some such information (e.g., an image or sound) overlaps with predefined MIME Content-Types. In these cases it can be desirable to include the information in its well-known MIME format. This situation is handled by using a multipart/related Content-Type as defined in [RFC-2112]. The root component of this type is a text/directory body part specifying any in-line information, and for information contained in other Content-Types, the Content-IDs (in URI form) of those parts.
目录条目可包含的信息远不止文本信息。有些信息（如图像或声音）与预定义的 MIME 内容类型重叠。在这种情况下，最好能以众所周知的 MIME 格式包含这些信息。这种情况可以使用 [RFC-2112] 中定义的 multipart/related Content-Type 来处理。该类型的根组件是一个文本/目录主体部分，其中指定了任何内联信息，而对于包含在其他内容类型中的信息，则是这些部分的内容 ID（URI 形式）。
In some applications, it can be useful to include a pointer (e.g, a URI) to some directory information rather than the information itself. This document defines a general mechanism for accomplishing this.
在某些应用中，包含指向某些目录信息的指针（如 URI）而不是信息本身可能是有用的。本文件定义了实现这一目的的一般机制。
The text/directory Content-Type is used to hold basic directory information and URIs referencing other information, including other MIME body parts holding supplementary or non-textual directory information, such as an image or sound. It is defined as follows, using the MIME media type registration template from [RFC-2048].
文本/目录内容类型（text/directory Content-Type）用于保存基本目录信息和引用其他信息的 URI，包括保存补充或非文本目录信息（如图像或声音）的其他 MIME 主体部分。它使用 [RFC-2048] 中的 MIME 媒体类型注册模板定义如下。
To: [email protected] Subject: Registration of MIME media type text/directory
MIME media type name: text
MIME 媒体类型名称：文本
MIME subtype name: directory
MIME 子类型名称：目录
Required parameters: charset
所需参数：字符集
The "charset" parameter is as defined in [RFC-2046] for other body parts. It is used to identify the default character set used within the body part.
charset "参数的定义与[RFC-2046]中其他主体部分的定义相同。它用于标识正文部分中使用的默认字符集。
Optional parameters: profile
可选参数：配置文件
The "profile" parameter is used to convey the type(s) of entity(ies) to which the directory information pertains and the likely set of information associated with the entity(ies). It is intended only as a guide to applications interpreting the information contained within the body part. It SHOULD NOT be used to exclude or require particular pieces of information unless a profile definition specifically calls for this behavior. Unless specifically forbidden by a particular profile definition, a text/directory content type can contain arbitrary attribute/value pairs.
配置文件 "参数用于传达与目录信息相关的实体类型以及与实体相关的可能信息集。其目的只是为解释主体部分所含信息的应用程序提供指导。它不应被用于排除或要求特定的信息片段，除非配置文件定义特别要求这种行为。文本/目录内容类型可包含任意属性/值对，除非特定规范定义特别禁止。
The value of the "profile" parameter is defined as follows. Profile names are case insensitive (i.e., the profile name "vCard" is the same as "VCARD" and "vcard" and "vcArD").
配置文件 "参数的值定义如下。配置文件名称不区分大小写（例如，配置文件名称 "vCard "与 "VCARD"、"vcard "和 "vcArD "相同）。
profile = x-name / iana-token
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names beginning with "x-" or "X-" are
; reserved for experimental use not intended for released
; products, or for use in bilateral agreements.
iana-token = <a publicly-defined extension token, registered
with IANA, as specified in Section 9 of this
document>
The default encoding is 8bit. Otherwise, as specified by the Content-Transfer-Encoding header field.
默认编码为 8 位。否则，按 Content-Transfer-Encoding 标头字段指定。
Directory information can be public or it can be protected from unauthorized access by the directory service in which it resides. Once the information leaves its native service, there can be no guarantee that the same care will be taken by all services handling the information. Furthermore, this specification defines no access control mechanism by which information can be protected, or by which access control information can be conveyed. Note that the integrity and privacy of a text/directory body part can be protected by enclosing it within an appropriate MIME-based security mechanism.
目录信息可以是公开的，也可以由其所在的目录服务加以保护，防止未经授权的访问。一旦信息离开其本地服务，就不能保证所有处理信息的服务都会采取同样的保护措施。此外，本规范没有定义用于保护信息或传递访问控制信息的访问控制机制。请注意，文本/目录主体部分的完整性和隐私性可以通过将其封装在适当的基于 MIME 的安全机制中来保护。
In order to make sense of directory information, applications must share a common understanding of the types of information contained within the Content-Type (the directory schema). This schema information is not defined in this document, but rather in companion documents (e.g., [MIME-VCARD]) that follow the requirements specified in this document, or in bilateral agreements between communicating parties.
为了理解目录信息，应用程序必须对内容类型（目录模式）中包含的信息类型有共同的理解。这种模式信息不在本文档中定义，而是在遵循本文档规定的要求的配套文档（如 [MIME-VCARD]）或通信双方的双边协议中定义。
The text/directory Content-Type contains directory information, typically pertaining to a single directory entity or group of entities. The content consists of one or more lines in the format given below.
文本/目录内容类型包含目录信息，通常与单个目录实体或实体组有关。内容由一行或多行组成，格式如下。
Individual lines within the MIME text/directory Content Type body are delimited by the [RFC-822] line break, which is a CRLF sequence (ASCII decimal 13, followed by ASCII decimal 10). Long logical lines of text can be split into a multiple-physical-line representation using the following folding technique.
MIME 文本/目录内容类型正文中的各行由 [RFC-822] 换行符分隔，换行符是 CRLF 序列（ASCII 十进制 13，后接 ASCII 十进制 10）。长逻辑行文本可通过以下折叠技术拆分成多物理行表示。
A logical line MAY be continued on the next physical line anywhere between two characters by inserting a CRLF immediately followed by a single white space character (space, ASCII decimal 32, or horizontal tab, ASCII decimal 9). At least one character must be present on the folded line. Any sequence of CRLF followed immediately by a single white space character is ignored (removed) when processing the content type. For example the line:
逻辑行可以在两个字符之间的任意位置插入一个 CRLF，紧接着是一个空格字符（空格，ASCII 十进制 32 位，或水平制表符，ASCII 十进制 9 位），从而在下一个物理行上延续。折叠行上必须至少有一个字符。在处理内容类型时，任何紧跟一个空格字符的 CRLF 序列都将被忽略（删除）。例如
DESCRIPTION:This is a long description that exists on a long line.
说明：这是一段长长的描述，存在于长长的一行中。
Can be represented as: DESCRIPTION:This is a long description that exists on a long line.
可表示为DESCRIPTION:这是一个长行描述。
It could also be represented as:
也可以表示为
DESCRIPTION:This is a long descrip tion that exists o n a long line.
DESCRIPTION：这是一个长长的描述，存在于一条长线上。
The process of moving from this folded multiple-line representation of a type definition to its single line representation is called unfolding. Unfolding is accomplished by regarding CRLF immediately followed by a white space character (namely HTAB ASCII decimal 9 or SPACE ASCII decimal 32) as equivalent to no characters at all (i.e., the CRLF and single white space character are removed).
从类型定义的多行折叠表示法到单行表示法的过程称为展开。展开的方法是将紧跟 CRLF 之后的空白字符（即 HTAB ASCII 十进制 9 或 SPACE ASCII 十进制 32）视为等同于没有任何字符（即去掉 CRLF 和单个空白字符）。
The following ABNF uses the notation of RFC 2234, which also defines CRLF, WSP, DQUOTE, VCHAR, ALPHA, and DIGIT. After the unfolding of any folded lines as described above, the syntax for a line of this content type is as follows:
以下 ABNF 使用 RFC 2234 的符号，其中还定义了 CRLF、WSP、DQUOTE、VCHAR、ALPHA 和 DIGIT。在对任何折叠行进行上述展开后，该内容类型行的语法如下：
contentline = [group "."] name *(";" param) ":" value CRLF
; When parsing a content line, folded lines MUST first
; be unfolded according to the unfolding procedure
; described above.
; When generating a content line, lines longer than 75
; characters SHOULD be folded according to the folding
; procedure described above.
group = 1*(ALPHA / DIGIT / "-")
name = x-name / iana-token
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
x-name = "x-" 1*(ALPHA / DIGIT / "-")
; Names that begin with "x-" or "X-" are
; reserved for experimental use, not intended for released
; products, or for use in bilateral agreements.
param = param-name "=" param-value *("," param-value)
param-name = x-name / iana-token
param-value = ptext / quoted-string
ptext = *SAFE-CHAR
value = *VALUE-CHAR
/ valuespec ; valuespec defined in section 5.8.4
quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
引号字符串 = DQUOTE *QSAFE-CHAR DQUOTE
NON-ASCII = %x80-FF
; use restricted by charset parameter
; on outer MIME object (UTF-8 preferred)
QSAFE-CHAR = WSP / %x21 / %x23-7E / NON-ASCII
; Any character except CTLs, DQUOTE
SAFE-CHAR = WSP / %x21 / %x23-2B / %x2D-39 / %x3C-7E / NON-ASCII
; Any character except CTLs, DQUOTE, ";", ":", ","
VALUE-CHAR = WSP / VCHAR / NON-ASCII
; any textual character
A line that begins with a white space character is a continuation of the previous line, as described above. The white space character and immediately preceeding CRLF should be discarded when reconstructing the original line. Note that this line-folding convention differs from that found in RFC 822, in that the sequence <CRLF><WSP> found anywhere in the content indicates a continued line and should be removed.
如上所述，以空格字符开头的行是前一行的延续。在重建原始行时，应丢弃空白字符和紧接其后的 CRLF。需要注意的是，这种折行约定与 RFC 822 中的约定不同，在内容中任何地方出现的 <CRLF><WSP> 序列都表示续行，应予以删除。
Various type names and the format of the corresponding values are defined as specified in Section 11. Specifications MAY impose ordering on the type constructs within a body part, though none is required by default. The various x-name constructs are used for bilaterally-agreed upon type names, parameter names and parameter values, or for use in experimental settings.
第 11 节规定了各种类型名称和相应值的格式。规范可以对主体部分中的类型结构体进行排序，但默认情况下不需要。各种 x-name 结构用于双边商定的类型名称、参数名称和参数值，或用于实验设置。
Type names and parameter names are case insensitive (e.g., the type name "fn" is the same as "FN" and "Fn"). Parameter values MAY be case sensitive or case insensitive, depending on their definition.
类型名和参数名不分大小写（例如，类型名 "fn "与 "FN "和 "Fn "相同）。参数值可以区分大小写，也可以不区分大小写，具体取决于其定义。
The group construct is used to group related attributes together. The group name is a syntactic convention used to indicate that all type names prefaced with the same group name SHOULD be grouped together when displayed by an application. It has no other significance. Implementations that do not understand or support grouping MAY simply strip off any text before a "." to the left of the type name and present the types and values as normal.
组结构用于将相关属性分组。组名是一种语法约定，用于表示应用程序显示时，所有以相同组名为前缀的类型名都应组合在一起。它没有其他意义。不理解或不支持分组的实现可以简单地去掉类型名左边". "之前的任何文本，并按正常方式显示类型和值。
Each attribute defined in the text/directory body MAY have multiple values, if allowed in the definition of the profile in which the attribute is used. The general rule for encoding multi-valued items is to simply create a new content line for each value (including the type name). However, it should be noted that some value types support encoding multiple values in a single content line by separating the values with a comma ",". This approach has been taken for several of the content types defined below (date, time, integer, float), for space-saving reasons.
如果使用属性的配置文件定义允许，文本/目录正文中定义的每个属性都可以有多个值。多值项编码的一般规则是为每个值（包括类型名称）创建一个新的内容行。但需要注意的是，有些值类型支持在单个内容行中编码多个值，方法是用逗号", "分隔这些值。出于节省空间的考虑，下面定义的几种内容类型（日期、时间、整数、浮点数）都采用了这种方法。
The following parameters and value types are defined for general use.
以下参数和数值类型是为一般使用而定义的。
predefined-param = encodingparm
/ valuetypeparm
/ languageparm
/ contextparm
encodingparm = "encoding" "=" encodingtype
encodingparm = "encoding" "=" encodingtype
encodingtype = "b" ; from RFC 2047
/ iana-token ; registered as described in
; section 15 of this document
valuetypeparm = "value" "=" valuetype
valuetypeparm = "value" "=" valuetype
valuetype = "uri" ; genericurl from secion 5 of RFC 1738
/ "text"
/ "date"
/ "time"
/ "date-time" ; date time
/ "integer"
/ "boolean"
/ "float"
/ x-name
/ iana-token ; registered as described in
; section 15 of this document
languageparm = "language" "=" Language-Tag ; Language-Tag is defined in section 2 of RFC 1766
languageparm = "language" "=" Language-Tag ; Language-Tag 在 RFC 1766 第 2 节中定义
contextparm = "context" "=" context
contextparm = "context" "=" context
context = x-name / iana-token
context = x-name / iana-token
The "language" type parameter is used to identify data in multiple languages. There is no concept of "default" language, except as specified by any "Content-Language" MIME header parameter that is present. The value of the "language" type parameter is a language tag as defined in Section 2 of [RFC-1766].
语言 "类型参数用于识别多种语言的数据。没有 "默认 "语言的概念，除非有任何 "Content-Language（内容语言）"MIME 标头参数。语言 "类型参数的值是 [RFC-1766] 第 2 节中定义的语言标记。
The "context" type parameter is used to identify a context (e.g., a protocol) used in interpreting the value. This is used, for example, in the "source" type, defined below.
上下文 "类型参数用于标识用于解释值的上下文（如协议）。例如，在下文定义的 "来源 "类型中就使用了这一参数。
The "encoding" type parameter is used to specify an alternate encoding for a value. If the value contains a CRLF, it must be encoded, since CRLF is used to separate lines in the content-type itself. Currently, only the "b" encoding is supported.
编码 "类型参数用于指定值的替代编码。如果值包含 CRLF，则必须进行编码，因为 CRLF 在内容类型本身中用于分隔行。目前只支持 "b "编码。
The "b" encoding can also be useful for binary values that are mixed with other text information in the body part (e.g., a certificate). Using a per-value "b" encoding in this case leaves the other information in a more readable form. The encoded base 64 value can be split across multiple physical lines in the content type by using the line folding technique described above.
b" 编码也适用于正文部分（如证书）中与其他文本信息混合的二进制值。在这种情况下，使用按值 "b "编码会使其他信息更易阅读。通过使用上述折行技术，可以将编码后的基 64 值分割到内容类型的多个物理行中。
The Content-Transfer-Encoding header field is used to specify the encoding used for the body part as a whole. The "encoding" type parameter is used to specify an encoding for a particular value (e.g., a certificate). In this case, the Content-Transfer-Encoding header might specify "8bit", while the one certificate value might specify an encoding of "b" via an "encoding=b" type parameter.
Content-Transfer-Encoding 标头字段用于指定整个正文部分使用的编码。编码 "类型参数用于指定特定值（如证书）的编码。在这种情况下，Content-Transfer-Encoding 头可能指定 "8 位"，而一个证书值可能通过 "encoding=b "类型参数指定 "b "编码。
The Content-Transfer-Encoding and the encodings of individual types given by the "encoding" type parameter are independent of one another. When encoding a text/directory body part for transmission, individual type encodings are performed first, then the entire body part is encoded according to the Content-Transfer-Encoding. When decoding a text/directory body part, the Content-Transfer-Encoding is decoded first, and then any individual types with an "encoding" type parameter are decoded.
内容传输编码（Content-Transfer-Encoding）和 "编码 "类型参数给出的单个类型编码是相互独立的。为传输文本/目录正文部分编码时，首先进行单个类型编码，然后根据 Content-Transfer-Encoding 对整个正文部分进行编码。对文本/目录正文部分解码时，首先对 Content-Transfer-Encoding 进行解码，然后对带有 "编码 "类型参数的任何单个类型进行解码。
The "value" parameter is optional, and is used to identify the value type (data type) and format of the value. The use of these predefined formats is encouraged even if the value parameter is not explicity used. By defining a standard set of value types and their formats, existing parsing and processing code can be leveraged.
值 "参数是可选参数，用于确定值的类型（数据类型）和格式。即使没有明确使用值参数，也鼓励使用这些预定义格式。通过定义一套标准的值类型及其格式，可以充分利用现有的解析和处理代码。
Including the value type explicitly as part of each property provides an extra hint to keep parsing simple and support more generalized applications. For example a search engine would not have to know the particular value types for all of the items for which it is searching. Because the value type is explicit in the definition, the search engine could look for dates in any item type and provide results that can still be interpreted.
将值类型显式地作为每个属性的一部分提供了额外的提示，使解析过程更简单，并支持更通用的应用。例如，搜索引擎不必知道它要搜索的所有项目的特定值类型。由于值类型在定义中是显式的，搜索引擎可以在任何项目类型中查找日期，并提供仍然可以解释的结果。
The format for values corresponding to the predefined valuetype specifications given above are defined.
定义了与上述预定义值类型规范相对应的值的格式。
valuespec = text-list
/ genericurl ; from section 5 of RFC 1738
/ date-list
/ time-list
/ date-time-list
/ boolean
/ integer-list
/ float-list
/ iana-valuespec
text-list = *TEXT-LIST-CHAR *("," *TEXT-LIST-CHAR)
TEXT-LIST-CHAR = "\\" / "\," / "\n"
/ <any VALUE-CHAR except , or \ or newline>
; Backslashes, newlines, and commas must be encoded.
; \n or \N can be used to encode a newline.
date-list = date *("," date)
time-list = time *("," time)
date-time-list = date "T" time *("," date "T" time)
boolean = "TRUE" / "FALSE"
integer-list = integer *("," integer)
integer = [sign] 1*DIGIT
float-list = float *("," float)
float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-"
date = date-fullyear ["-"] date-month ["-"] date-mday
date = date-fullyear ["-"] date-month ["-"] date-mday
date-fullyear = 4 DIGIT
date-month = 2 DIGIT ;01-12
date-mday = 2 DIGIT ;01-28, 01-29, 01-30, 01-31 ;based on month/year
date-mday = 2 DIGIT ;01-28, 01-29, 01-30, 01-31 ;基于月份/年份
time = time-hour [":"] time-minute [":"] time-second [time-secfrac] [time-zone]
time = time-hour [":"] time-minute [":"] time-second [time-secfrac] [time-zone] 时区
time-hour = 2 DIGIT ;00-23
时间-小时 = 2 个数字 ;00-23
time-minute = 2 DIGIT ;00-59
时间-分钟 = 2 个数字；00-59
time-second = 2 DIGIT ;00-60 (leap second)
time-second = 2 个数字；00-60（闰秒）
time-secfrac = "," 1*DIGIT
time-secfrac = "," 1*DIGIT
time-zone = "Z" / time-numzone
时区 = "Z" / 时数区
time-numzome = sign time-hour [":"] time-minute
time-numzome = sign time-hour [":"] time-minute
iana-valuespec = <a publicly-defined valuetype format, registered
with IANA, as defined in section 15 of this
document>
Some specific notes on the value types and formats:
关于数值类型和格式的一些具体说明：
"text": The "text" value type should be used to identify values that contain human-readable text. The character set and language in which the text is represented is controlled by the charset content-header and the language type parameter and content-header.
"文本"：文本 "值类型应用于标识包含人类可读文本的值。表示文本的字符集和语言由 charset 内容头和语言类型参数及内容头控制。
Examples for "text": this is a text value this is one value,this is another this is a single value\, with a comma encoded
文本 "示例： this is a text value this is one value,this is another this is a single value\,with a comma encoded（这是一个文本值，这是另一个值）。
A formatted text line break in a text value type MUST be represented as the character sequence backslash (ASCII decimal 92) followed by a Latin small letter n (ASCII decimal 110) or a Latin capital letter N (ASCII decimal 78), that is "\n" or "\N".
文本值类型中的格式化文本换行符必须用字符序列反斜杠（ASCII 十进制 92）表示，后面跟一个拉丁小写字母 n（ASCII 十进制 110）或一个拉丁大写字母 N（ASCII 十进制 78），即"\n "或"\N"。
For example a multiple line DESCRIPTION value of:
例如，多行 DESCRIPTION 值为：
Mythical Manager Hyjinx Software Division BabsCo, Inc.
Mythical Manager Hyjinx Software Division BabsCo, Inc.
could be represented as: DESCRIPTION:Mythical Manager\nHyjinx Software Division\n BabsCo\, Inc.\n
可以表示为描述： Mythical Manager\nHyjinx Software Division\n BabsCo\, Inc.
demonstrating the \n literal formatted line break technique, the CRLF-followed-by-space line folding technique, and the backslash escape technique.
演示了字面格式化换行技术、CRLF-followed-by-space 折叠行技术和反斜杠转义技术。
"uri": The "uri" value type should be used to identify values that are referenced by a URI (including a Content-ID URI), instead of encoded in-line. These value references might be used if the value is too large, or otherwise undesirable to include directly. The format for the URI is as defined in RFC 1738.
"uri"：uri "值类型应用于标识由 URI（包括 Content-ID URI）引用的值，而不是行内编码的值。如果值过大或不宜直接包含，则可使用这些值引用。RFC 1738 中定义了 URI 的格式。
Examples for "uri": http://www.foobar.com/my/picture.jpg ldap://ldap.foobar.com/cn=babs%20jensen
uri "的示例： http://www.foobar.com/my/picture.jpg ldap://ldap.foobar.com/cn=babs%20jensen
"date", "time", and "date-time": Each of these value types is based on a subset of the definitions in ISO 8601 standard. Profiles MAY place further restrictions on "date" and "time" values. Multiple "date" and "time" values can be specified using the comma-separated notation, unless restricted by a profile.
"日期"、"时间 "和 "日期-时间"：每种值类型都基于 ISO 8601 标准中的定义子集。预案可以对 "日期 "和 "时间 "值做进一步限制。可以使用逗号分隔符指定多个 "日期 "和 "时间 "值，除非受到规范的限制。
Examples for "date": 1985-04-12 1996-08-05,1996-11-11 19850412
日期 "的示例：1985-04-12 1996-08-05,1996-11-11 19850412
Examples for "time":
10:22:00
102200
10:22:00.33
10:22:00.33Z
10:22:33,11:22:00
10:22:00-08:00
Examples for "date-time":
1996-10-22T14:00:00Z
1996-08-11T12:34:56Z
19960811T123456Z
1996-10-22T14:00:00Z,1996-08-11T12:34:56Z
"boolean": The "boolean" value type is used to express boolen values. These values are case insensitive.
"布尔"：布尔 "值类型用于表达布尔值。这些值不区分大小写。
Examples: TRUE false True
示例：TRUE 假 True 真
"integer": The "integer" value type is used to express signed integers in decimal format. If sign is not specified, the value is assumed positive "+". Multiple "integer" values can be specified using the comma-separated notation, unless restricted by a profile.
"整数"：整数 "值类型用于表示十进制格式的有符号整数。如果未指定符号，则假定值为正 "+"。可以使用逗号分隔符指定多个 "整数 "值，除非受到配置文件的限制。
Examples: 1234567890 -1234556790 +1234556790,432109876
例如：1234567890 -1234556790 +1234556790,4321098761234567890 -1234556790 +1234556790,432109876
"float": The "float" value type is used to express real numbers. If sign is not specified, the value is assumed positive "+". Multiple "float" values can be specified using the comma-separated notation, unless restricted by a profile.
"浮点数"：float "值类型用于表示实数。如果未指定符号，则假定值为正 "+"。可以使用逗号分隔符指定多个 "float "值，除非受到配置文件的限制。
Examples: 20.30 1000000.0000001 1.333,3.14
例如20.30 1000000.0000001 1.333,3.14
Applications which use this media type: Various
使用这种介质类型的应用程序：各种
Additional information: None
其他信息：无
Tim Howes Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA [email protected] +1 415 937 3419
Tim Howes 网景通信公司 501 East Middlefield Rd.Mountain View, CA 94041 USA [email protected] +1 415 937 3419
Intended usage: COMMON
预期用途：通用
Tim Howes Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA [email protected] +1 415 937 3419
Tim Howes 网景通信公司 501 East Middlefield Rd.Mountain View, CA 94041 USA [email protected] +1 415 937 3419
Mark Smith Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA [email protected] +1 415 937 3477
Mark Smith 网景通信公司 501 East Middlefield Rd.Mountain View, CA 94041 USA [email protected] +1 415 937 3477
Frank Dawson Lotus Development Corporation 6544 Battleford Drive Raleigh, NC 27613-3502 USA [email protected] +1-919-676-9515
Frank Dawson Lotus Development Corporation 6544 Battleford Drive Raleigh, NC 27613-3502 USA [email protected] +1-919-676-9515
The following types are generally useful regardless of the profile being carried and are defined below using the text/directory MIME type registration template defined in Section 11.1 of this document. These types MAY be included in any profile, unless explicitly forbidden in the profile definition.
无论使用何种预案，以下类型通常都是有用的，并使用本文档第 11.1 节中定义的文本/目录 MIME 类型注册模板进行定义。这些类型可以包含在任何预案中，除非在预案定义中明确禁止。
To: [email protected] Subject: Registration of text/directory MIME type SOURCE
Type name: SOURCE
类型名称： SOURCE
Type purpose: To identify the source of directory information contained in the content type.
类型目的：确定内容类型中包含的目录信息的来源。
Type encoding: 8bit
类型编码：8 位
Type valuetype: uri Type special notes: The SOURCE type is used to provide the means by which applications knowledgable in the given directory service protocol can obtain additional or more up-to-date information from the directory service. It contains a URI as defined in [RFC-1738] and/or other information referencing the directory entity or entities to which the information pertains. When directory information is available from more than one source, the sending entity can pick what it considers to be the best source, or multiple SOURCE types can be included. The interpretation of the value for a SOURCE type can depend on the setting of the CONTEXT type parameter. The value of the CONTEXT type parameter MUST be compatible with the value of the uri prefix.
类型 valueetype：uri 类型特殊说明：SOURCE 类型用于提供一种方法，使熟悉给定目录服务协议的应用程序能够从目录服务中获取更多或更新的信息。它包含[RFC-1738]中定义的 URI 和/或其他信息，其中引用了与信息相关的一个或多个目录实体。当目录信息可从多个来源获得时，发送实体可以选择它认为最好的来源，也可以包含多个 SOURCE 类型。对 SOURCE 类型值的解释取决于 CONTEXT 类型参数的设置。CONTEXT 类型参数的值必须与 uri 前缀的值兼容。
Type example:
SOURCE;CONTEXT=LDAP:ldap://ldap.host/cn=Babs%20Jensen,
%20o=Babsco,%20c=US
To: [email protected] Subject: Registration of text/directory MIME type NAME
Type name: NAME
类型名称： NAME
Type purpose: To identify the displayable name of the directory entity to which information in the content type pertains.
类型目的：确定内容类型中的信息所涉及的目录实体的可显示名称。
Type encoding: 8bit
类型编码：8 位
Type valuetype: text
类型 值类型：文本
Type special notes: The NAME type is used to convey the display name of the entity to which the directory information pertains.
类型特别说明：NAME 类型用于传达目录信息相关实体的显示名称。
Type example: NAME:Babs Jensen's Contact Information
键入示例：姓名：巴勃斯-詹森的联系信息
To: [email protected] Subject: Registration of text/directory MIME type PROFILE
Type name: PROFILE
类型名称： PROFILE
Type purpose: To identify the type of directory entity to which information in the content type pertains.
类型目的：确定内容类型中的信息所涉及的目录实体类型。
Type encoding: 8bit Type valuetype: A profile name, registered as described in Section 9 of this document or bilaterally agreed upon as described in Section 5.
类型编码：8bit 类型 valueetype：配置文件名称，按本文件第 9 节所述注册或按第 5 节所述双边协议注册。
Type special notes: The PROFILE type is used to convey the type of the entity to which the directory information in the rest of the body part pertains. It should be the same as the "profile" header parameter, if present.
类型特别说明：PROFILE 类型用于表达主体部分其余部分的目录信息所涉及的实体类型。它应与 "profile "标头参数（如果有）相同。
Type example: PROFILE:vCard
类型示例：PROFILE:vCard
To: [email protected] Subject: Registration of text/directory MIME type BEGIN
Type name: BEGIN
类型名称： 开始
Type purpose: To denote the beginning of a syntactic entity within a text/directory content-type.
类型目的：表示文本/目录内容类型中语法实体的开始。
Type encoding: 8bit
类型编码：8 位
Type valuetype: text, containing a profile name, registered as described in Section 9 of this document or bilaterally-agreed upon as described in Section 5.
类型 valueetype：文本，包含一个配置文件名称，按本文件第 9 节所述登记或按第 5 节所述双边商定。
Type special notes: The BEGIN type is used in conjunction with the END type to delimit a profile containing a related set of properties within an text/directory content-type. This construct can be used instead of or in addition to wrapping separate sets of information inside additional MIME headers. It is provided for applications that wish to define content that can contain multiple entities within the same text/directory content-type or to define content that can be identifiable outside of a MIME environment.
类型特别说明：BEGIN 类型与 END 类型结合使用，用于在文本/目录内容类型中对包含相关属性集的配置文件进行定界。这种结构可用于替代或补充在附加 MIME 标头中包装独立信息集的做法。它适用于希望在同一文本/目录内容类型中定义包含多个实体的内容，或定义可在 MIME 环境之外识别的内容的应用程序。
Type example: BEGIN:VCARD
键入示例：BEGIN:VCARD
To: [email protected] Subject: Registration of text/directory MIME type END
Type name: END Type purpose: To denote the end of a syntactic entity within a text/directory content-type.
类型名称：END 类型目的：表示文本/目录内容类型中语法实体的结束。
Type encoding: 8bit
类型编码：8 位
Type valuetype: text, containing a profile name, registered as described in Section 9 of this document or bilaterally-agreed upon as described in Section 5.
类型 valueetype：文本，包含一个配置文件名称，按本文件第 9 节所述登记或按第 5 节所述双边商定。
Type special notes: The END type is used in conjunction with the BEGIN type to delimit a profile containing a related set of properties within an text/directory content-type. This construct can be used instead of or in addition to wrapping separate sets of information inside additional MIME headers. It is provided for applications that wish to define content that can contain multiple entities within the same text/directory content-type or to define content that can be identifiable outside of a MIME environment.
类型特别说明：END（END）类型与 BEGIN（BEGIN）类型结合使用，用于在文本/目录内容类型中对包含相关属性集的配置文件进行定界。这种结构可用于替代或补充在附加 MIME 标头中包装独立信息集的做法。它适用于希望在同一文本/目录内容类型中定义包含多个实体的内容，或定义可在 MIME 环境之外识别的内容的应用程序。
Type example: END: VCARD
键入示例：结束：VCARD
The multipart/related Content-Type can be used to hold directory information comprised of both text and non-text information or directory information that already has a natural MIME representation. The root body part within the multipart/related body part is specified as defined in [RFC-2112] by a "start" parameter, or it is the first body part in the absence of such a parameter. The root body part must have a Content-Type of "text/directory". This part holds inline information and makes reference to subsequent body parts holding additional text or non-text directory information via their Content-ID URIs as explained in Section 5.
multipart/related Content-Type 可用于保存由文本和非文本信息组成的目录信息，或已具有自然 MIME 表示形式的目录信息。根据 [RFC-2112] 的定义，multipart/related 主体部分中的根主体部分由 "start "参数指定，如果没有 "start "参数，则根主体部分是第一个主体部分。根主体部分的 Content-Type 必须是 "text/directory"。该部分包含内联信息，并通过其 Content-ID URI（如第 5 节所述）引用包含附加文本或非文本目录信息的后续主体部分。
The body parts referred to do not have to be in any particular order, except as noted above for the root body part.
所指的身体部位不一定要按特定顺序排列，但上文提到的身体根部除外。
The following examples are for illustrative purposes only and are not part of the definition.
以下示例仅供参考，不构成定义的一部分。
The first example illustrates simple use of the text/directory Content-Type. Note that no "profile" parameter is given, so an application may not know what kind of directory entity the information applies to. Note also the use of both hypothetical official and bilaterally agreed upon types.
第一个示例说明了文本/目录 Content-Type 的简单用法。注意没有给出 "配置文件 "参数，因此应用程序可能不知道该信息适用于哪种目录实体。还请注意假设官方类型和双边商定类型的使用。
From: [email protected]
To: [email protected]
Subject: whatever
MIME-Version: 1.0
Message-ID: <[email protected]>
Content-Type: text/directory
Content-ID: <[email protected]>
cn:Babs Jensen
cn:Barbara J Jensen
sn:Jensen
email:[email protected]
phone:+1 313 747-4454
x-id:1234567890
The next example illustrates the use of the Quoted-Printable transfer encoding defined in [RFC 2045] to include non-ASCII character in some of the information returned, and the use of the optional "name" and "source" types. It also illustrates the use of an "encoding" type parameter to encode a certificate value in "b". A "vCard" profile [MIME- VCARD] is used for the example.
下一个示例说明了如何使用 [RFC 2045] 中定义的引用-可打印传输编码，在返回的某些信息中加入非 ASCII 字符，以及如何使用可选的 "名称 "和 "来源 "类型。它还说明了如何使用 "编码 "类型参数对证书值进行 "b "编码。示例中使用了 "vCard "配置文件[MIME- VCARD]。
Content-Type: text/directory;
charset="iso-8859-1";
profile="vCard"
Content-ID: <[email protected]>
Content-Transfer-Encoding: Quoted-Printable
begin:VCARD source:ldap://cn=bjorn%20Jensen, o=university%20of%20Michigan, c=US name:Bjorn Jensen fn:Bj=F8rn Jensen n:Jensen;Bj=F8rn email;type=internet:[email protected] tel;type=work,voice,msg:+1 313 747-4454 key;type=x509;encoding=B:dGhpcyBjb3VsZCBiZSAKbXkgY2VydGlmaWNhdGUK end:VCARD 8.3. Example 3
The next example illustrates the use of multi-valued type parameters, the "language" type parameter, the "value" type parameter, folding of long lines, the \n encoding for formatted lines, attribute grouping, and the inline "b" encoding. A "vCard" profile [MIME-VCARD] is used for the example.
下一个示例说明了多值类型参数、"语言 "类型参数、"值 "类型参数、长行折叠、格式化行的 \n 编码、属性分组和内联 "b "编码的使用。示例中使用了 "vCard "配置文件[MIME-VCARD]。
Content-Type: text/directory; profile="vcard"; charset=iso-8859-1 Content-ID: <[email protected]> Content-Transfer-Encoding: Quoted-Printable
begin:vcard source:ldap://cn=Meister%20Berger,o=Universitaet%20Goerlitz,c=DE name:Meister Berger fn:Meister Berger n:Berger;Meister bday;value=date:1963-09-21 o:Universit=E6t G=F6rlitz title:Mayor title;language=de;value=text:Burgermeister note:The Mayor of the great city of Goerlitz in the great country of Germany. email;internet:[email protected] home.tel;type=fax,voice,msg:+49 3581 123456 home.label:Hufenshlagel 1234\n 02828 Goerlitz\n Deutschland key;type=X509;encoding=b:MIICajCCAdOgAwIBAgICBEUwDQYJKoZIhvcNAQEEBQ AwdzELMAkGA1UEBhMCVVMxLDAqBgNVBAoTI05ldHNjYXBlIENvbW11bmljYXRpb25zI ENvcnBvcmF0aW9uMRwwGgYDVQQLExNJbmZvcm1hdGlvbiBTeXN0ZW1zMRwwGgYDVQQD ExNyb290Y2EubmV0c2NhcGUuY29tMB4XDTk3MDYwNjE5NDc1OVoXDTk3MTIwMzE5NDc 1OVowgYkxCzAJBgNVBAYTAlVTMSYwJAYDVQQKEx1OZXRzY2FwZSBDb21tdW5pY2F0aW 9ucyBDb3JwLjEYMBYGA1UEAxMPVGltb3RoeSBBIEhvd2VzMSEwHwYJKoZIhvcNAQkBF hJob3dlc0BuZXRzY2FwZS5jb20xFTATBgoJkiaJk/IsZAEBEwVob3dlczBcMA0GCSqG SIb3DQEBAQUAA0sAMEgCQQC0JZf6wkg8pLMXHHCUvMfL5H6zjSk4vTTXZpYyrdN2dXc oX49LKiOmgeJSzoiFKHtLOIboyludF90CgqcxtwKnAgMBAAGjNjA0MBEGCWCGSAGG+E IBAQQEAwIAoDAfBgNVHSMEGDAWgBT84FToB/GV3jr3mcau+hUMbsQukjANBgkqhkiG9 w0BAQQFAAOBgQBexv7o7mi3PLXadkmNP9LcIPmx93HGp0Kgyx1jIVMyNgsemeAwBM+M SlhMfcpbTrONwNjZYW8vJDSoi//yrZlVt9bJbs7MNYZVsyF1unsqaln4/vy6Uawfg8V UMk1U7jt8LYpo4YULU7UZHPYVUaSgVttImOHZIKi4hlPXBOhcUQ== end:vcard 8.4. Example 4
The final example illustrates the use of the multipart/related Content-Type to include non-textual directory data via the "uri" encoding to refer to other body parts within the same message, or to external values. Note that no "profile" parameter is given, so an application may not know what kind of directory entity the information applies to. Note also the use of both hypothetical official and bilaterally agreed upon types.
最后一个示例说明了如何使用 multipart/related Content-Type 通过 "uri "编码包含非文本目录数据，以引用同一报文中的其他主体部分或外部值。请注意，这里没有给出 "配置文件 "参数，因此应用程序可能不知道这些信息适用于哪种目录实体。还请注意假定官方类型和双边商定类型的使用。
Content-Type: multipart/related;
boundary=woof;
type="text/directory";
start="<[email protected]>"
Content-ID: <[email protected]>
--woof Content-Type: text/directory; charset="iso-8859-1" Content-ID: <[email protected]> Content-Transfer-Encoding: Quoted-Printable
source:ldap://cn=Bjorn%20Jensen,o=University%20of%20Michigan,c=US cn:Bj=F8rn Jensen sn:Jensen email:[email protected] image;value=uri:cid:[email protected] image;value=uri;format=jpeg:ftp://some.host/some/path.jpg sound;value=uri:cid:[email protected] phone:+1 313 747-4454
--woof Content-Type: image/jpeg Content-ID: <[email protected]>
<...image data...>
<...图像数据...>
--woof
Content-Type: message/external-body;
name="myvoice.au";
site="myhost.com";
access-type=ANON-FTP;
directory="pub/myname";
mode="image"
Content-Type: audio/basic Content-ID: <[email protected]>
--woof--9. Registration of new profiles
--woof--9.注册新档案
This section defines procedures by which new profiles are registered with the IANA and made available to the Internet community. Note that non-IANA profiles can be used by bilateral agreement, provided the associated profile names follow the "X-" convention defined above.
本节定义了向 IANA 注册新配置文件并向互联网社区提供的程序。请注意，非 IANA 预案可通过双边协议使用，但相关预案名称须遵循上文定义的 "X-"约定。
The procedures defined here are designed to allow public comment and review of new profiles, while posing only a small impediment to the definition of new profiles.
此处定义的程序旨在允许公众对新的简介发表意见和进行审查，同时对新简介的定义只造成很小的障碍。
Registration of a new profile is accomplished by the following steps.
通过以下步骤完成新配置文件的注册。
A profile is defined by completing the following template.
填写以下模板即可定义个人资料。
To: [email protected]
Subject: Registration of text/directory MIME profile XXX
Profile name:
档案名称：
Profile purpose:
简介目的：
Profile types:
轮廓类型
Profile special notes (optional):
简介特别说明（可选）：
Intended usage: (one of COMMON, LIMITED USE or OBSOLETE)
预期用途：(常用、限用或废弃之一）。
The explanation of what goes in each field in the template follows.
下面将解释模板中每个字段的内容。
Profile name: The name of the profile as it will appear in the text/directory MIME Content-Type "profile" header parameter, or the predefined "profile" type name.
配置文件名称：将出现在文本/目录 MIME 内容类型 "配置文件 "标头参数中的配置文件名称，或预定义的 "配置文件 "类型名称。
Profile purpose: The purpose of the profile (e.g., to represent information about people, printers, documents, etc.). Give a short but clear description.
配置文件的目的：配置文件的目的（例如，表示有关人员、打印机、文档等的信息）。给出简短但清晰的描述。
Profile types: The list of types associated with the profile. This list of types is to be expected but not required in the profile, unless otherwise noted in the profile definition. Other types not mentioned in the profile definition MAY also be present. Note that any new types referenced by the profile MUST be defined separately as described in Section 10.
配置文件类型：与预案相关的类型列表。除非在规范定义中另有说明，否则该类型列表在规范中是预期的，但不是必须的。预案定义中未提及的其他类型也可能存在。请注意，描述文件引用的任何新类型都必须按第 10 节所述单独定义。
Profile special notes: Any special notes about the profile, how it is to be used, etc. This section of the template can also be used to define an ordering on the types that appear in the Content-Type, if such an ordering is required.
简介特别说明：关于配置文件、使用方法等的任何特殊说明。如果需要对内容类型（Content-Type）中出现的类型进行排序，模板的这一部分也可用于定义排序。
The profile description must be posted to the new profile discussion list, [email protected]
简介说明必须发布到新简介讨论列表 [email protected]
Discussion on the new profile must be allowed to take place on the list for a minimum of two weeks. Consensus must be reached on the profile before proceeding to step 4.
必须允许在名单上对新简介进行至少两周的讨论。在进入第 4 步之前，必须就简介达成共识。
Once the two-week comment period has elapsed, and the proposer is convinced consensus has been reached on the profile, the registration application should be submitted to the Profile Reviewer for approval. The Profile Reviewer is appointed by the Application Area Directors and can either accept or reject the profile registration. An accepted registration is passed on by the Profile Reviewer to the IANA for inclusion in the official IANA profile registry. The registration may be rejected for any of the following reasons. 1) Insufficient comment period; 2) Consensus not reached; 3) Technical deficiencies raised on the list or elsewhere have not been addressed. The Profile Reviewer's decision to reject a profile can be appealed by the proposer to the IESG, or the objections raised can be addressed by the proposer and the profile resubmitted.
一旦两周的评论期结束，且提议者确信已就简介达成共识，则应将注册申请提交简介审核员批准。简介审核员由申请区主任任命，可以接受或拒绝简介注册。被接受的注册将由配置文件审查员转交给 IANA，以便纳入正式的 IANA 配置文件注册表。注册可因以下原因被拒绝。1) 评论期不足； 2) 未达成共识； 3) 列表或其他地方提出的技术缺陷未得到解决。对于配置文件审查员拒绝配置文件的决定，提议者可向 IESG 提出上诉，或由提议者解决所提出的异议并重新提交配置文件。
Existing profiles can be changed using the same process by which they were registered.
现有配置文件可通过与注册时相同的程序进行更改。
Define the change
确定变革
Post the change
发布变更
Allow a comment period
允许评论期
Submit the changed profile for approval
提交已更改的配置文件以供审批
Note that the original author or any other interested party can propose a change to an existing profile, but that such changes should only be proposed when there are serious omissions or errors in the published specification. The Profile Reviewer can object to a change if it is not backwards compatible, but is not required to do so.
请注意，原作者或任何其他相关方都可以提议修改现有的规范，但只有在已发布的规范存在严重遗漏或错误时才可提议修改。如果变更不向后兼容，配置文件审核员可以反对，但并不要求这样做。
Profile definitions can never be deleted from the IANA registry, but profiles which are no longer believed to be useful can be declared OBSOLETE by a change to their "intended use" field.
配置文件定义永远不能从 IANA 注册表中删除，但认为不再有用的配置文件可以通过更改其 "预期用途 "字段来宣布其为 "已废弃"。
This section defines procedures by which new types are registered with the IANA. Note that non-IANA types can be used by bilateral agreement, provided the associated types names follow the "X-" convention defined above.
本节定义了向 IANA 注册新类型的程序。请注意，可以通过双边协议使用非 IANA 类型，但相关类型名称必须遵循上文定义的 "X-"约定。
The procedures defined here are designed to allow public comment and review of new types, while posing only a small impediment to the definition of new types.
此处定义的程序旨在允许公众对新类型提出意见和进行审查，同时对新类型的定义只造成很小的障碍。
Registration of a new type is accomplished by the following steps.
新类型的注册通过以下步骤完成。
A type is defined by completing the following template.
完成以下模板即可定义一个类型。
To: [email protected]
Subject: Registration of text/directory MIME type XXX
Type name:
类型名称：
Type purpose:
类型用途：
Type encoding:
类型编码：
Type valuetype:
值类型：
Type special notes (optional):
输入特殊说明（可选）：
Intended usage: (one of COMMON, LIMITED USE or OBSOLETE)
预期用途：(通用、限用或废弃之一）。
The meaning of each field in the template is as follows.
模板中每个字段的含义如下。
Type name: The name of the type, as it will appear in the body of an text/directory MIME Content-Type "type: value" line to the left of the colon ":".
类型名称：类型名称，它将出现在文本/目录 MIME Content-Type "type: value"（类型：值）行的正文中，在冒号": "的左边。
Type purpose: The purpose of the type (e.g., to represent a name, postal address, IP address, etc.). Give a short but clear description.
类型目的：类型的目的（如表示名称、邮政地址、IP 地址等）。给出简短但清晰的描述。
Type encoding: The default encoding a value of the type must have in the body of a text/directory MIME Content-Type.
类型编码：类型值在文本/目录 MIME Content-Type 正文中必须使用的默认编码。
Type valuetype: The format a value of the type must have in the body of a text/directory MIME Content-Type. This description must be precise and must not violate the general encoding rules defined in section 5 of this document.
类型 valueetype：类型值在文本/目录 MIME 内容类型正文中必须具有的格式。该描述必须精确，不得违反本文件第 5 节中定义的一般编码规则。
Type special notes: Any special notes about the type, how it is to be used, etc.
类型特别说明：关于类型、使用方法等的任何特殊说明。
The type description must be posted to the new type discussion list, [email protected]
类型描述必须发布到新类型讨论列表 [email protected]
Discussion on the new type must be allowed to take place on the list for a minimum of two weeks. Consensus must be reached on the type before proceeding to step 4.
必须允许在名单上对新类型进行至少两周的讨论。在进入第 4 步之前，必须就类型达成共识。
Once the two-week comment period has elapsed, and the proposer is convinced consensus has been reached on the type, the registration application should be submitted to the Profile Reviewer for approval. The Profile Reviewer is appointed by the Application Area Directors and can either accept or reject the type registration. An accepted registration is passed on by the Profile Reviewer to the IANA for inclusion in the official IANA profile registry. The registration can be rejected for any of the following reasons. 1) Insufficient comment period; 2) Consensus not reached; 3) Technical deficiencies raised on the list or elsewhere have not been addressed. The Profile Reviewer's decision to reject a type can be appealed by the proposer to the IESG, or the objections raised can be addressed by the proposer and the type resubmitted.
一旦两周的评论期结束，且提议者确信已就类型达成共识，注册申请应提交给简介审核员批准。概况审查员由申请区主任任命，可以接受或拒绝类型注册。被接受的注册将由配置文件审查员转交给 IANA，以便纳入正式的 IANA 配置文件注册表。注册可因以下原因被拒绝。1) 评论期不足； 2) 未达成共识； 3) 列表或其他地方提出的技术缺陷未得到解决。对于 Profile Reviewer 拒绝类型的决定，提议者可向 IESG 提出上诉，或由提议者解决所提出的异议并重新提交类型。
Existing types can be changed using the same process by which they were registered.
现有类型可通过与注册时相同的程序进行更改。
Define the change
确定变革
Post the change
发布变更
Allow a comment period
允许评论期
Submit the type for approval
提交类型供审批
Note that the original author or any other interested party can propose a change to an existing type, but that such changes should only be proposed when there are serious omissions or errors in the published specification. The Profile Reviewer can object to a change if it is not backwards compatible, but is not required to do so.
请注意，原作者或任何其他相关方都可以提议更改现有类型，但只有在已发布的规范存在严重遗漏或错误时才可提议更改。如果某项更改不具有向后兼容性，简介审核员可以反对，但并不要求这样做。
Type definitions can never be deleted from the IANA registry, but types which are nolonger believed to be useful can be declared OBSOLETE by a change to their "intended use" field.
类型定义永远不能从 IANA 注册表中删除，但如果认为类型不再有用，可以通过更改其 "预期用途 "字段来宣布其为 "废止 "类型。
This section defines procedures by which new parameters are registered with the IANA and made available to the Internet community. Note that non-IANA parameters can be used by bilateral agreement, provided the associated parameters names follow the "X-" convention defined above.
本节定义了向 IANA 注册新参数并将其提供给互联网社区的程序。请注意，可以通过双边协议使用非 IANA 参数，但相关参数名称必须遵循上文定义的 "X-"约定。
The procedures defined here are designed to allow public comment and review of new parameters, while posing only a small impediment to the definition of new parameters.
此处规定的程序旨在允许公众对新参数发表意见和进行审查，同时对新参数的定义只造成很小的障碍。
Registration of a new parameter is accomplished by the following steps.
注册新参数的步骤如下。
A parameter is defined by completing the following template.
完成以下模板即可定义一个参数。
To: [email protected]
Subject: Registration of text/directory MIME type parameter XXX
Parameter name:
参数名称：
Parameter purpose: Parameter values:
参数用途： 参数值：
Parameter special notes (optional):
参数特别说明（可选）：
Intended usage: (one of COMMON, LIMITED USE or OBSOLETE)
预期用途：(通用、限用或废弃之一）。
The explanation of what goes in each field in the template follows.
下面将解释模板中每个字段的内容。
Parameter name: The name of the parameter as it will appear in the text/directory MIME Content-Type.
参数名称： 在文本/目录中显示的参数名称 MIME Content-Type.
Parameter purpose: The purpose of the parameter (e.g., to represent the format of an image, type of a phone number, etc.). Give a short but clear description. If defining a general paramemter like "format" or "type" keep in mind that other applications might wish to extend its use.
参数目的：参数的目的（如表示图像格式、电话号码类型等）。给出简短但清晰的描述。如果定义的是 "格式 "或 "类型 "等通用参数，请注意其他应用程序可能希望扩展其用途。
Parameter values: The list or description of values associated with the parameter.
参数值：参数相关值的列表或说明。
Parameter special notes: Any special notes about the parameter, how it is to be used, etc.
参数特别说明：关于参数的任何特殊说明、使用方法等。
The parameter description must be posted to the new parameter discussion list, [email protected]
参数说明必须发布到新参数讨论列表 [email protected]。
Discussion on the new parameter must be allowed to take place on the list for a minimum of two weeks. Consensus must be reached on the parameter before proceeding to step 4.
必须允许在名单上对新参数进行至少两周的讨论。在进入第 4 步之前，必须就参数达成共识。
Once the two-week comment period has elapsed, and the proposer is convinced consensus has been reached on the parameter, the registration application should be submitted to the Profile Reviewer for approval. The Profile Reviewer is appointed by the Application Area Directors and can either accept or reject the parameter registration. An accepted registration is passed on by the Profile Reviewer to the IANA for inclusion in the official IANA parameter registry. The registration can be rejected for any of the following reasons. 1) Insufficient comment period; 2) Consensus not reached; 3) Technical deficiencies raised on the list or elsewhere have not been addressed. The Profile Reviewer's decision to reject a profile can be appealed by the proposer to the IESG, or the objections raised can be addressed by the proposer and the parameter registration resubmitted.
一旦两周的评论期结束，且提议者确信已就参数达成共识，则应将注册申请提交给简介审核员审批。简介审核员由应用领域主任任命，可以接受或拒绝参数注册。被接受的注册将由配置文件审核员转交给 IANA，以便纳入官方的 IANA 参数注册表。注册可因以下原因被拒绝。1) 评论期不足；2) 未达成共识；3) 列表或其他地方提出的技术缺陷未得到解决。对于配置文件审查员拒绝配置文件的决定，提议者可向 IESG 提出上诉，或由提议者解决提出的异议，并重新提交参数注册。
Existing parameters can be changed using the same process by which they were registered.
现有参数可通过与注册参数相同的程序进行更改。
Define the change
确定变革
Post the change
发布变更
Allow a comment period
允许评论期
Submit the parameter for approval
将参数提交审批
Note that the original author or any other interested party can propose a change to an existing parameter, but that such changes should only be proposed when there are serious omissions or errors in the published specification. The Profile Reviewer can object to a change if it is not backwards compatible, but is not required to do so.
请注意，原作者或任何其他相关方均可提议更改现有参数，但只有在已发布的规范存在严重遗漏或错误时才可提议更改。如果更改不向后兼容，配置文件审核员可以反对，但并不要求这样做。
Parameter definitions can never be deleted from the IANA registry, but parameters which are nolonger believed to be useful can be declared OBSOLETE by a change to their "intended use" field.
参数定义永远不能从 IANA 注册表中删除，但可以通过更改 "预期用途 "字段来宣布不再有用的参数为 OBSOLETE。
This section defines procedures by which new value types are registered with the IANA and made available to the Internet community. Note that non-IANA value types can be used by bilateral agreement, provided the associated value types names follow the "X-" convention defined above.
本节定义了向 IANA 注册并向互联网社区提供新值类型的程序。请注意，可以通过双边协议使用非 IANA 值类型，但相关值类型名称必须遵循上文定义的 "X-"约定。
The procedures defined here are designed to allow public comment and review of new value types, while posing only a small impediment to the definition of new value types.
此处定义的程序旨在允许公众对新的价值类型发表意见和进行审查，同时对新价值类型的定义只造成很小的障碍。
Registration of a new value types is accomplished by the following steps.
新值类型的注册通过以下步骤完成。
A value type is defined by completing the following template.
值类型是通过完成以下模板定义的。
To: [email protected] Subject: Registration of text/directory MIME value type XXX value type name:
收件人： [email protected] 主题注册文本/目录 MIME 值类型 XXX 值类型名称：
value type purpose:
值类型的目的：
value type format:
值类型格式：
value type special notes (optional):
值类型特殊说明（可选）：
Intended usage: (one of COMMON, LIMITED USE or OBSOLETE)
预期用途：(通用、限用或废弃之一）。
The explanation of what goes in each field in the template follows.
下面将解释模板中每个字段的内容。
value type name: The name of the value type as it will appear in the text/directory MIME Content-Type.
值类型名称：值类型的名称，该名称将出现在文本/目录 MIME Content-Type 中。
value type purpose: The purpose of the value type. Give a short but clear description.
值类型目的：值类型的目的。给出简短但清晰的描述。
value type format: The definition of the format for the value, usually using ABNF grammar.
值类型格式：值的格式定义，通常使用 ABNF 语法。
value type special notes: Any special notes about the value type, how it is to be used, etc.
值类型特殊说明：关于值类型、使用方法等的任何特殊说明。
The value type description must be posted to the new value type discussion list, [email protected]
值类型说明必须发布到新值类型讨论列表 [email protected]
Discussion on the new value type must be allowed to take place on the list for a minimum of two weeks. Consensus must be reached before proceeding to step 4.
关于新值类型的讨论必须在名单上进行至少两周。在进入第 4 步之前，必须达成共识。
Once the two-week comment period has elapsed, and the proposer is convinced consensus has been reached on the value type, the registration application should be submitted to the Profile Reviewer for approval. The Profile Reviewer is appointed by the Application Area Directors and can either accept or reject the value type registration. An accepted registration should be passed on by the Profile Reviewer to the IANA for inclusion in the official IANA value type registry. The registration can be rejected for any of the following reasons. 1) Insufficient comment period; 2) Consensus not reached; 3) Technical deficiencies raised on the list or elsewhere have not been addressed. The Profile Reviewer's decision to reject a profile can be appealed by the proposer to the IESG, or the objections raised can be addressed by the proposer and the value type registration resubmitted.
一旦两周的评论期结束，且提议者确信已就价值类型达成共识，则应将注册申请提交给简介审核员审批。简介审核员由应用领域总监任命，可以接受或拒绝价值类型注册。被接受的注册应由简介审核员转交给 IANA，以便纳入官方的 IANA 值类型注册表。注册可因以下原因被拒绝。1) 评论期不足；2) 未达成共识；3) 列表或其他地方提出的技术缺陷未得到解决。对于配置文件审核员拒绝配置文件的决定，提议者可向 IESG 提出上诉，或由提议者解决提出的异议，并重新提交值类型注册。
Internet mail is subject to many well known security attacks, including monitoring, replay, and forgery. Care should be taken by any directory service in allowing information to leave the scope of the service itself, where any access controls can no longer be guaranteed. Applications should also take care to display directory data in a "safe" environment (e.g., PostScript-valued types).
互联网邮件受到许多众所周知的安全攻击，包括监控、重放和伪造。任何目录服务在允许信息离开服务本身的范围时都应小心谨慎，因为在这种情况下，任何访问控制都不再能得到保证。应用程序还应注意在 "安全 "的环境中显示目录数据（如 PostScript 值类型）。
The registration procedures defined here were shamelessly lifted from the MIME registration RFC.
这里定义的注册程序是从 MIME 注册 RFC 中无耻摘录的。
The many valuable comments contributed by members of the IETF ASID working group are gratefully acknowledged, as are the contributions of the Versit Consortium. Chris Newman was especially helpful in navigating the intricacies of ABNF lore.
IETF ASID 工作组成员提出了许多宝贵意见，Versit 财团也做出了贡献，在此一并表示感谢。克里斯-纽曼（Chris Newman）对我们了解错综复杂的 ABNF 知识尤其有帮助。
[RFC-1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory Access Protocol", RFC 1777, March 1995.
[RFC-1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory Access Protocol", RFC 1777, March 1995.
[RFC-1778] Howes, T., Kille, S., Yeong, W., and C. Robbins, "The String Representation of Standard Attribute Syntaxes", RFC 1778, March 1995.
[RFC-1778] Howes, T., Kille, S., Yeong, W., and C. Robbins, "The String Representation of Standard Attribute Syntaxes", RFC 1778, March 1995.
[RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822, August 1982.
[RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822, August 1982.
[RFC-2045] Borenstein, N., and N. Freed, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[RFC-2045] Borenstein, N. 和 N. Freed, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies", RFC 2045, November 1996.
[RFC-2046] Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[RFC-2046] Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[RFC-2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures", RFC 2048, November 1996.
[RFC-2048] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet Mail Extensions (MIME) Part Four：注册程序"，RFC 2048，1996 年 11 月。
[RFC-1766] Alvestrand, H., "Tags for the Identification of Languages", RFC 1766, March 1995.
[RFC-1766] Alvestrand, H., "Tags for Identification of Languages", RFC 1766, March 1995.
[RFC-2112] Levinson, E., "The MIME Multipart/Related Content-type", RFC 2112, March 1997.
[RFC-2112] Levinson, E., "The MIME Multipart/Related Content-type", RFC 2112, 1997 年 3 月。
[X500] "Information Processing Systems - Open Systems Interconnection - The Directory: Overview of Concepts, Models and Services", ISO/IEC JTC 1/SC21, International Standard 9594-1, 1988.
[X500] "信息处理系统--开放系统互连--目录：概念、模型和服务概述》，ISO/IEC JTC 1/SC21，国际标准 9594-1，1988 年。
[RFC-1835] Deutsch, P., Schoultz, R., Faltstrom, P., and C. Weider, "Architecture of the WHOIS++ service", RFC 1835, August 1995.
[RFC-1835] Deutsch, P., Schoultz, R., Faltstrom, P., and C. Weider, "Architecture of WHOIS++ service", RFC 1835, August 1995.
[RFC-1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[RFC-1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform Resource Locators (URL)", RFC 1738, December 1994.
[MIME-VCARD] Dawson, F., and T. Howes, "VCard MIME Directory Profile", RFC 2426, September 1998.
[MIME-VCARD] Dawson、F. 和 T. Howes，"VCard MIME 目录简介"，RFC 2426，1998 年 9 月。
[VCARD] Internet Mail Consortium, "vCard - The Electronic Business Card", Version 2.1, http://www.imc.com/pdi/vcard-21.txt, September, 1996.
[VCARD] 互联网邮件联盟，"vCard - 电子名片"，2.1 版，http://www.imc.com/pdi/vcard-21.txt，1996 年 9 月。
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[RFC-2234] Crocker, D. 和 P. Overell, "Augmented BNF for Syntax Specifications：ABNF"，RFC 2234，1997 年 11 月。
Tim Howes Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA
Tim Howes 网景通讯公司 501 East Middlefield Rd.美国加利福尼亚州山景城 94041
Phone: +1.415.937.3419 EMail: [email protected]
Mark Smith Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA
Mark Smith 网景通讯公司 501 East Middlefield Rd.美国加利福尼亚州山景城 94041
Phone: +1.415.937.3477 EMail: [email protected]
Frank Dawson Lotus Development Corporation 6544 Battleford Drive Raleigh, NC 27613 USA
Frank Dawson Lotus Development Corporation 6544 Battleford Drive Raleigh, NC 27613 USA
Phone: +1-919-676-9515 EMail: [email protected]
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有 (C) 互联网协会 (1998)。保留所有权利。
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.
本文件及其包含的信息按 "原样 "提供，互联网协会和互联网工程工作组不作任何明示或暗示的保证、包括但不限于使用本网站信息不侵犯任何权利的保证或适销性或特定用途适用性的默示保证。