Network Working Group T. Howes
Request for Comments: 2425 M. Smith
Category: Standards Track Netscape Communications Corp.
F. Dawson
Lotus Development Corporation
September 1998
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内容类型。该定义独立于任何特定的目录服务或协议。文本/目录内容类型定义用于保存各种目录信息，例如名称、电子邮件地址或徽标。文本/目录内容类型也可以用作多部分/相关内容类型中的根主体部分，用于处理更复杂的情况，尤其是那些已经具有自然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).
text/directory内容类型定义了一个通用框架和格式，用于以简单的“Type:value”形式保存目录信息。在此上下文中，我们指的是“类型”，意思是与值关联的属性或属性。机制被定义为指定替代语言、编码和其他元信息。本文档还定义了定义和注册用于在文本/目录内容类型中承载应用程序特定信息的特定格式（称为概要文件）的过程，以及此类格式必须遵循的约定。预计将编制其他文件，为各种应用程序（如白页）定义此类格式。
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[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
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
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内容类型中表示目录信息的方案有两部分。首先，定义文本/目录内容类型，用于保存单个正文部分中的目录信息，例如名称、标题或电子邮件地址。在其最简单的形式中，该格式使用“type:value”方法，现有MIME实现应该可以轻松解析该方法，并且用户可以理解该方法。更复杂的情况也可以表现出来。本文档定义了内容类型中的信息应具有的一般形式，以及定义特定应用程序的特定类型和值（属性）的过程。该框架足够通用，可以处理来自任意数量的终端目录服务的信息，包括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]中定义的多部分/相关内容类型来处理。此类型的根组件是一个文本/目录体部分，指定任何行内信息，对于其他内容类型中包含的信息，则指定这些部分的内容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].
文本/目录内容类型用于保存基本目录信息和引用其他信息的URI，包括保存补充或非文本目录信息（如图像或声音）的其他MIME正文部分。使用[RFC-2048]中的MIME媒体类型注册模板，其定义如下。
To: ietf-types@uninett.no
Subject: Registration of MIME media type text/directory
To: ietf-types@uninett.no
Subject: Registration of MIME media type text/directory
MIME media type name: text
MIME媒体类型名称：text
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.
“字符集”参数如[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.
“profile”参数用于传递目录信息所属的实体类型以及与实体相关的可能信息集。本手册仅作为解释身体部位所含信息的应用指南。除非配置文件定义特别要求此行为，否则不应使用它来排除或要求特定的信息。除非特定概要文件定义明确禁止，否则文本/目录内容类型可以包含任意属性/值对。
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").
“profile”参数的值定义如下。配置文件名称不区分大小写（即，配置文件名称“vCard”与“vCard”和“vCard”相同）。
profile = x-name / iana-token
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.
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>
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比特。否则，按内容传输编码头字段指定。
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.
描述：这是一个存在于长行上的长描述。
It could also be represented as:
它还可以表示为：
DESCRIPTION:This is a long descrip tion that exists o n a long line.
描述：这是一个存在于长行上的长描述。
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或空格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.
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 / "-")
group = 1*(ALPHA / DIGIT / "-")
name = x-name / iana-token
name = x-name / iana-token
iana-token = 1*(ALPHA / DIGIT / "-")
; identifier registered with IANA
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.
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 = param-name "=" param-value *("," param-value)
param-name = x-name / iana-token
param-name = x-name / iana-token
param-value = ptext / quoted-string
param-value = ptext / quoted-string
ptext = *SAFE-CHAR
ptext = *SAFE-CHAR
value = *VALUE-CHAR
/ valuespec ; valuespec defined in section 5.8.4
value = *VALUE-CHAR
/ valuespec ; valuespec defined in section 5.8.4
quoted-string = DQUOTE *QSAFE-CHAR DQUOTE
quoted string=DQUOTE*QSAFE-CHAR DQUOTE
NON-ASCII = %x80-FF
; use restricted by charset parameter
; on outer MIME object (UTF-8 preferred)
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
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, ";", ":", ","
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
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
predefined-param = encodingparm
/ valuetypeparm
/ languageparm
/ contextparm
encodingparm = "encoding" "=" encodingtype
encodingparm=“encoding”“=”编码类型
encodingtype = "b" ; from RFC 2047
/ iana-token ; registered as described in
; section 15 of this document
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
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”“=”语言标记；语言标记在RFC1766第2节中定义
contextparm = "context" "=" context
contextparm=“context”“=”上下文
context = x-name / iana-token
上下文=x-name/iana令牌
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].
“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.
“context”类型参数用于标识用于解释值的上下文（例如，协议）。例如，这在下面定义的“源”类型中使用。
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.
“encoding”类型参数用于指定值的替代编码。如果该值包含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标头字段用于指定身体部位作为一个整体使用的编码。“encoding”类型参数用于指定特定值（例如证书）的编码。在这种情况下，内容传输编码头可能指定“8bit”，而一个证书值可能通过“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.
内容传输编码和“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.
“value”参数是可选的，用于标识值的值类型（数据类型）和格式。即使未明确使用值参数，也鼓励使用这些预定义格式。通过定义一组标准的值类型及其格式，可以利用现有的解析和处理代码。
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.
定义了与上述预定义valuetype规范对应的值的格式。
valuespec = text-list
/ genericurl ; from section 5 of RFC 1738
/ date-list
/ time-list
/ date-time-list
/ boolean
/ integer-list
/ float-list
/ iana-valuespec
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 = *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.
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)
日期时间列表=日期“T”时间*（“，”日期“T”时间）
boolean = "TRUE" / "FALSE"
boolean = "TRUE" / "FALSE"
integer-list = integer *("," integer)
整数列表=整数*（“，”整数）
integer = [sign] 1*DIGIT
integer = [sign] 1*DIGIT
float-list = float *("," float)
浮动列表=浮动*（“，”浮动）
float = [sign] 1*DIGIT ["." 1*DIGIT]
float = [sign] 1*DIGIT ["." 1*DIGIT]
sign = "+" / "-"
sign = "+" / "-"
date = date-fullyear ["-"] date-month ["-"] date-mday
日期=日期整年[“-”]日期月[“-”]日期mday
date-fullyear = 4 DIGIT
date-fullyear = 4 DIGIT
date-month = 2 DIGIT ;01-12
日期月份=2位数字；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
;based on month/year
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)
时间秒=2位；00-60（闰秒）
time-secfrac = "," 1*DIGIT
时间secfrac=“，”1*位
time-zone = "Z" / time-numzone
时区=“Z”/timenumzone
time-numzome = sign time-hour [":"] time-minute
time numzome=签署时间小时[“：”]时间分钟
iana-valuespec = <a publicly-defined valuetype format, registered
with IANA, as defined in section 15 of this
document>
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.
“文本”：应使用“文本”值类型来标识包含人类可读文本的值。表示文本的字符集和语言由字符集内容头、语言类型参数和内容头控制。
Examples for "text": 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:
例如，多行描述值为：
Mythical Manager Hyjinx Software Division BabsCo, Inc.
Hyjinx软件部神话经理BabsCo，Inc。
could be represented as:
可以表示为：
DESCRIPTION:Mythical Manager\nHyjinx Software Division\n BabsCo\, Inc.\n
描述：Mythical Manager\nHyjinx软件部门\n BabsCo\，Inc.\n
demonstrating the \n literal formatted line break technique, the CRLF-followed-by-space line folding technique, and the backslash escape technique.
演示\n文字格式的换行技术、CRLF后跟空格折线技术和反斜杠转义技术。
"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引用的值（包括内容ID uri），而不是行内编码的值。如果值太大或不希望直接包含，则可以使用这些值引用。URI的格式如RFC 1738中所定义。
Examples for "uri":
http://www.foobar.com/my/picture.jpg
ldap://ldap.foobar.com/cn=babs%20jensen
Examples for "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-051996-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 "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
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
例子：真假真
"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+1234556790432109876
"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.
“浮点”：浮点值类型用于表示实数。如果未指定符号，则该值假定为正“+”。除非受到配置文件的限制，否则可以使用逗号分隔符号指定多个“浮点”值。
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 howes@netscape.com +1 415 937 3419
Tim Howes Netscape Communications Corp.美国加利福尼亚州山景城东米德菲尔德路501号，邮编94041howes@netscape.com +1 415 937 3419
Intended usage: COMMON
预期用途：普通
Tim Howes Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA howes@netscape.com +1 415 937 3419
Tim Howes Netscape Communications Corp.美国加利福尼亚州山景城东米德菲尔德路501号，邮编94041howes@netscape.com +1 415 937 3419
Mark Smith Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA mcs@netscape.com +1 415 937 3477
马克·史密斯网景通信公司，美国加利福尼亚州山景城东米德菲尔德路501号，邮编94041mcs@netscape.com +1 415 937 3477
Frank Dawson Lotus Development Corporation 6544 Battleford Drive Raleigh, NC 27613-3502 USA frank_dawson@lotus.com +1-919-676-9515
弗兰克·道森莲花开发公司美国北卡罗来纳州罗利市巴特福德大道6544号，邮编：27613-3502弗兰克_dawson@lotus.com +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: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type SOURCE
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type SOURCE
Type name: SOURCE
类型名称：源
Type purpose: To identify the source of directory information contained in the content type.
类型用途：标识内容类型中包含的目录信息的源。
Type encoding: 8bit
类型编码：8位
Type valuetype: uri
类型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.
类型特别说明：源类型用于提供一种方法，通过该方法，给定目录服务协议中已知的应用程序可以从目录服务获取更多或更多最新信息。它包含[RFC-1738]中定义的URI和/或引用该信息所属的目录实体的其他信息。当目录信息来自多个源时，发送实体可以选择它认为最好的源，或者可以包括多个源类型。源类型值的解释可能取决于上下文类型参数的设置。上下文类型参数的值必须与uri前缀的值兼容。
Type example:
SOURCE;CONTEXT=LDAP:ldap://ldap.host/cn=Babs%20Jensen,
%20o=Babsco,%20c=US
Type example:
SOURCE;CONTEXT=LDAP:ldap://ldap.host/cn=Babs%20Jensen,
%20o=Babsco,%20c=US
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type NAME
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type NAME
Type 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.
类型特殊注释：名称类型用于传递目录信息所属实体的显示名称。
Type example: NAME:Babs Jensen's Contact Information
类型示例：名称：Babs Jensen的联系信息
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type PROFILE
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type PROFILE
Type name: PROFILE
类型名称：配置文件
Type purpose: To identify the type of directory entity to which information in the content type pertains.
类型用途：标识内容类型中的信息所属的目录实体的类型。
Type encoding: 8bit
类型编码：8位
Type valuetype: A profile name, registered as described in Section 9 of this document or bilaterally agreed upon as described in Section 5.
类型valuetype：按照本文件第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”标题参数相同（如果存在）。
Type example: PROFILE:vCard
类型示例：配置文件：vCard
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type BEGIN
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type BEGIN
Type name: BEGIN
类型名称：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.
Type valuetype：文本，包含配置文件名称，按照本文件第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.
类型特殊说明：开始类型与结束类型结合使用，用于在文本/目录内容类型中分隔包含一组相关属性的概要文件。这个构造可以用来代替或补充在附加MIME头中包装单独的信息集。它适用于希望定义可以在同一文本/目录内容类型中包含多个实体的内容或定义可以在MIME环境之外识别的内容的应用程序。
Type example: BEGIN:VCARD
类型示例：开始：VCARD
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type END
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type END
Type name: END
类型名称：END
Type purpose: To denote the end 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.
Type valuetype：文本，包含配置文件名称，按照本文件第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.
类型特殊说明：结束类型与开始类型结合使用，用于限定包含文本/目录内容类型中相关属性集的概要文件。这个构造可以用来代替或补充在附加MIME头中包装单独的信息集。它适用于希望定义可以在同一文本/目录内容类型中包含多个实体的内容或定义可以在MIME环境之外识别的内容的应用程序。
Type example: END: VCARD
类型示例：END: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.
多部分/相关内容类型可用于保存由文本和非文本信息组成的目录信息，或已具有自然MIME表示形式的目录信息。根据[RFC-2112]中的定义，通过“开始”参数指定多部分/相关主体部分中的根主体部分，或者在没有此类参数的情况下，它是第一个主体部分。根主体部分的内容类型必须为“text/directory”。本部分保存内联信息，并通过其内容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.
第一个示例演示了文本/目录内容类型的简单用法。请注意，没有给出“profile”参数，因此应用程序可能不知道该信息应用于哪种目录实体。还应注意使用假设的官方和双边商定的类型。
From: Whomever@wherever.com
To: Someone@somewhere.com
Subject: whatever
MIME-Version: 1.0
Message-ID: <id1@host.net>
Content-Type: text/directory
Content-ID: <id2@host.com>
From: Whomever@wherever.com
To: Someone@somewhere.com
Subject: whatever
MIME-Version: 1.0
Message-ID: <id1@host.net>
Content-Type: text/directory
Content-ID: <id2@host.com>
cn:Babs Jensen
cn:Barbara J Jensen
sn:Jensen
email:babs@umich.edu
phone:+1 313 747-4454
x-id:1234567890
cn:Babs Jensen
cn:Barbara J Jensen
sn:Jensen
email:babs@umich.edu
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字符，以及使用可选的“名称”和“源”类型。它还说明了如何使用“encoding”类型参数对“b”中的证书值进行编码。示例中使用了“vCard”配置文件[MIME-vCard]。
Content-Type: text/directory;
charset="iso-8859-1";
profile="vCard"
Content-ID: <id3@host.com>
Content-Transfer-Encoding: Quoted-Printable
Content-Type: text/directory;
charset="iso-8859-1";
profile="vCard"
Content-ID: <id3@host.com>
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:bjorn@umich.edu
tel;type=work,voice,msg:+1 313 747-4454
key;type=x509;encoding=B:dGhpcyBjb3VsZCBiZSAKbXkgY2VydGlmaWNhdGUK
end:VCARD
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:bjorn@umich.edu
tel;type=work,voice,msg:+1 313 747-4454
key;type=x509;encoding=B:dGhpcyBjb3VsZCBiZSAKbXkgY2VydGlmaWNhdGUK
end:VCARD
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: <id3@host.com>
Content-Transfer-Encoding: Quoted-Printable
Content-Type: text/directory; profile="vcard"; charset=iso-8859-1
Content-ID: <id3@host.com>
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:mb@goerlitz.de
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
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:mb@goerlitz.de
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
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.
最后一个示例演示了如何使用多部分/相关内容类型，通过“uri”编码包含非文本目录数据，以引用同一消息中的其他正文部分或外部值。请注意，没有给出“profile”参数，因此应用程序可能不知道该信息应用于哪种目录实体。还应注意使用假设的官方和双边商定的类型。
Content-Type: multipart/related;
boundary=woof;
type="text/directory";
start="<id5@host.com>"
Content-ID: <id4@host.com>
Content-Type: multipart/related;
boundary=woof;
type="text/directory";
start="<id5@host.com>"
Content-ID: <id4@host.com>
--woof
Content-Type: text/directory; charset="iso-8859-1"
Content-ID: <id5@host.com>
Content-Transfer-Encoding: Quoted-Printable
--woof
Content-Type: text/directory; charset="iso-8859-1"
Content-ID: <id5@host.com>
Content-Transfer-Encoding: Quoted-Printable
source:ldap://cn=Bjorn%20Jensen,o=University%20of%20Michigan,c=US
cn:Bj=F8rn Jensen
sn:Jensen
email:bjorn@umich.edu
image;value=uri:cid:id6@host.com
image;value=uri;format=jpeg:ftp://some.host/some/path.jpg
sound;value=uri:cid:id7@host.com
phone:+1 313 747-4454
source:ldap://cn=Bjorn%20Jensen,o=University%20of%20Michigan,c=US
cn:Bj=F8rn Jensen
sn:Jensen
email:bjorn@umich.edu
image;value=uri:cid:id6@host.com
image;value=uri;format=jpeg:ftp://some.host/some/path.jpg
sound;value=uri:cid:id7@host.com
phone:+1 313 747-4454
--woof
Content-Type: image/jpeg
Content-ID: <id6@host.com>
--woof
Content-Type: image/jpeg
Content-ID: <id6@host.com>
<...image data...>
<…图像数据…>
--woof
Content-Type: message/external-body;
name="myvoice.au";
site="myhost.com";
access-type=ANON-FTP;
directory="pub/myname";
mode="image"
--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: <id7@host.com>
Content-Type: audio/basic
Content-ID: <id7@host.com>
--woof--
--纬--
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: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME profile XXX
To: ietf-mime-direct@imc.org
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”头参数中的配置文件名称，或预定义的“Profile”类型名称。
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.
配置文件特殊注释：有关配置文件、如何使用配置文件等的任何特殊注释。模板的此部分还可用于定义内容类型中出现的类型的排序（如果需要此类排序）。
The profile description must be posted to the new profile discussion list, ietf-mime-direct@imc.org
配置文件描述必须发布到新的配置文件讨论列表ietf mime-direct@imc.org
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: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type XXX
To: ietf-mime-direct@imc.org
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内容类型“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内容类型的正文中必须包含类型值的默认编码。
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.
Type valuetype：文本/目录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, ietf-mime-direct@imc.org
类型描述必须发布到新类型讨论列表ietf mime-direct@imc.org
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） 清单或其他地方提出的技术缺陷尚未得到解决。概要审查员拒绝某一类型的决定可由投标人向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: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME type parameter XXX
To: ietf-mime-direct@imc.org
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内容类型中。
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, ietf-mime-direct@imc.org
参数说明必须发布到新参数讨论列表ietf mime中-direct@imc.org
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
一旦两周的评论期结束，且投标人确信已就参数达成共识，则应将注册申请提交给概要审查人批准。配置文件审查员由应用区域主管指定，可以接受或拒绝参数注册。概要文件审阅者将接受的注册信息传递给IANA，以便将其包含在正式的IANA参数注册表中。注册可能因以下任何原因而被拒绝。1） 评论期不足；2） 未达成共识；3） 清单或其他地方提出的技术缺陷尚未得到解决。投标人可以向IESG就概要文件审查人拒绝概要文件的决定提出上诉，也可以撤销提出的异议
addressed by the proposer and the parameter registration resubmitted.
由投标人提出，并重新提交参数注册。
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注册表中删除，但是那些被认为不再有用的参数可以通过更改其“预期用途”字段宣布为过时。
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: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME value type XXX
To: ietf-mime-direct@imc.org
Subject: Registration of text/directory MIME value type XXX
value type name:
值类型名称：
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内容类型中的值类型的名称。
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, ietf-mime-direct@imc.org
值类型描述必须发布到新的值类型讨论列表ietf mime-direct@imc.org
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
一旦两周的评论期结束，且投标人确信已就价值类型达成共识，则应将注册申请提交给概要审查员批准。配置文件审查员由应用区域主管指定，可以接受或拒绝值类型注册。概要文件审查员应将已接受的注册信息传递给IANA，以便将其纳入正式的IANA值类型注册表。注册可能因以下任何原因而被拒绝。1） 评论期不足；2） 未达成共识；3） 清单或其他地方提出的技术缺陷尚未得到解决。概要文件审阅者拒绝
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.
投标人可向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).
Internet邮件会受到许多众所周知的安全攻击，包括监视、重播和伪造。任何目录服务在允许信息离开服务范围时都应该小心，因为在服务范围内，任何访问控制都不再能够得到保证。应用程序还应注意在“安全”环境中显示目录数据（例如，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财团的贡献。克里斯·纽曼特别有助于了解阿布尼复杂的故事。
[RFC-1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory Access Protocol", RFC 1777, March 1995.
[RFC-1777]Yeong，W.，Howes，T.，和S.Kille，“轻量级目录访问协议”，RFC 17771995年3月。
[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.，和C.Robbins，“标准属性语法的字符串表示”，RFC 17781995年3月。
[RFC-822] Crocker, D., "Standard for the Format of ARPA Internet Text Messages", STD 11, RFC 822, August 1982.
[RFC-822]Crocker，D.，“ARPA互联网文本信息格式标准”，STD 11，RFC 822，1982年8月。
[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，“多用途Internet邮件扩展（MIME）第一部分：Internet邮件正文格式”，RFC 20451996年11月。
[RFC-2046] Moore, K., "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types", RFC 2046, November 1996.
[RFC-2046]Moore，K.，“多用途互联网邮件扩展（MIME）第二部分：媒体类型”，RFC 2046，1996年11月。
[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.，和J.Postel，“多用途互联网邮件扩展（MIME）第四部分：注册程序”，RFC 2048，1996年11月。
[RFC-1766] Alvestrand, H., "Tags for the Identification of Languages", RFC 1766, March 1995.
[RFC-1766]Alvestrand，H.，“语言识别标签”，RFC 1766，1995年3月。
[RFC-2112] Levinson, E., "The MIME Multipart/Related Content-type", RFC 2112, March 1997.
[RFC-2112]Levinson，E.“MIME多部分/相关内容类型”，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-11988。
[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.，和C.Weider，“WHOIS++服务的体系结构”，RFC 18351995年8月。
[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.，和M.McCahill，“统一资源定位器（URL）”，RFC 17381994年12月。
[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，一九九六年九月。
[RFC-2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC-2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC-2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
[RFC-2234]Crocker，D.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。
Tim Howes Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA
Tim Howes Netscape Communications Corp.美国加利福尼亚州山景城东米德菲尔德路501号，邮编94041
Phone: +1.415.937.3419
EMail: howes@netscape.com
Phone: +1.415.937.3419
EMail: howes@netscape.com
Mark Smith Netscape Communications Corp. 501 East Middlefield Rd. Mountain View, CA 94041 USA
马克·史密斯网景通信公司，美国加利福尼亚州山景城东米德菲尔德路501号，邮编94041
Phone: +1.415.937.3477
EMail: mcs@netscape.com
Phone: +1.415.937.3477
EMail: mcs@netscape.com
Frank Dawson Lotus Development Corporation 6544 Battleford Drive Raleigh, NC 27613 USA
美国北卡罗来纳州罗利市巴特福德大道6544号法兰克道森莲花开发公司，邮编：27613
Phone: +1-919-676-9515
EMail: frank_dawson@lotus.com
Phone: +1-919-676-9515
EMail: frank_dawson@lotus.com
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。