Network Working Group T. Small
Request for Comments: 2739 XpertSite.Com
Category: Standards Track D. Hennessy
ISOCOR
F. Dawson
Lotus
January 2000
Network Working Group T. Small
Request for Comments: 2739 XpertSite.Com
Category: Standards Track D. Hennessy
ISOCOR
F. Dawson
Lotus
January 2000
Calendar Attributes for vCard and LDAP
vCard和LDAP的日历属性
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 (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
Abstract
摘要
When scheduling a calendar entity, such as an event, it is a prerequisite that an organizer has the calendar address of each attendee that will be invited to the event. Additionally, access to an attendee's current "busy time" provides an a priori indication of whether the attendee will be free to participate in the event.
安排日历实体（如活动）时，组织者必须具有将被邀请参加活动的每个与会者的日历地址。此外，访问与会者当前的“繁忙时间”可以预先指示与会者是否可以自由参加活动。
In order to meet these challenges, a calendar user agent (CUA) needs a mechanism to locate (URI) individual user's calendar and free/busy time.
为了应对这些挑战，日历用户代理（CUA）需要一种机制来定位（URI）单个用户的日历和忙/闲时间。
This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. These include:
此备忘录定义了三种机制，用于获取用户日历和忙/闲时间的URI。这些措施包括：
- Manual transfer of the information;
- 人工传递信息；
- Personal data exchange using the vCard format; and
- 使用vCard格式交换个人数据；和
- Directory lookup using the LDAP protocol.
- 使用LDAP协议进行目录查找。
Table of Contents
目录
1 CALENDARING AND SCHEDULING URIS...................................3
1.1 FREE/BUSY URI (FBURL) .........................................3
1.2 CALENDAR ACCESS URI (CAPURI) ..................................4
1.3 CALENDAR URI (CALURI) .........................................4
1.4 DEFAULT URIS ..................................................4
2 DISTRIBUTION......................................................4
2.1 MANUAL TRANSFER ...............................................5
2.2 PERSONAL DATA EXCHANGE USING A VCARD ..........................5
2.3 VCARD SCHEMA EXTENSIONS .......................................5
2.3.1 FBURL Property IANA Registration ...........................6
2.3.2 CALADRURI Property IANA Registration .......................7
2.3.3 CAPURI Property IANA Registration ......................... 8
2.3.4 CALURI Property IANA Registration ......................... 8
2.4 DIRECTORY LOOKUP USING THE LDAP V3 PROTOCOL .................. 9
2.4.1 LDAP Schema Extensions .................................... 9
2.4.2 Notation ..................................................10
2.4.3 Object Definitions ........................................10
2.4.3.1 calEntry ..............................................10
2.4.4 Attribute Definitions .....................................10
2.4.4.1 calCalURI .............................................10
2.4.4.2 calFBURL ..............................................10
2.4.4.3 calCAPURI .............................................11
2.4.4.4 calCalAdrURI ..........................................11
2.4.4.5 calOtherCalURIs .......................................11
2.4.4.6 calOtherFBURLs ........................................11
2.4.4.7 calOtherCAPURIs .......................................12
2.4.4.8 calOtherCalAdrURIs ....................................12
3 IANA Considerations..............................................12
4 Security Considerations..........................................12
5 Acknowledgments..................................................13
6 Authors' Addresses...............................................13
7 Bibliography.....................................................15
8 Full Copyright Statement.........................................16
1 CALENDARING AND SCHEDULING URIS...................................3
1.1 FREE/BUSY URI (FBURL) .........................................3
1.2 CALENDAR ACCESS URI (CAPURI) ..................................4
1.3 CALENDAR URI (CALURI) .........................................4
1.4 DEFAULT URIS ..................................................4
2 DISTRIBUTION......................................................4
2.1 MANUAL TRANSFER ...............................................5
2.2 PERSONAL DATA EXCHANGE USING A VCARD ..........................5
2.3 VCARD SCHEMA EXTENSIONS .......................................5
2.3.1 FBURL Property IANA Registration ...........................6
2.3.2 CALADRURI Property IANA Registration .......................7
2.3.3 CAPURI Property IANA Registration ......................... 8
2.3.4 CALURI Property IANA Registration ......................... 8
2.4 DIRECTORY LOOKUP USING THE LDAP V3 PROTOCOL .................. 9
2.4.1 LDAP Schema Extensions .................................... 9
2.4.2 Notation ..................................................10
2.4.3 Object Definitions ........................................10
2.4.3.1 calEntry ..............................................10
2.4.4 Attribute Definitions .....................................10
2.4.4.1 calCalURI .............................................10
2.4.4.2 calFBURL ..............................................10
2.4.4.3 calCAPURI .............................................11
2.4.4.4 calCalAdrURI ..........................................11
2.4.4.5 calOtherCalURIs .......................................11
2.4.4.6 calOtherFBURLs ........................................11
2.4.4.7 calOtherCAPURIs .......................................12
2.4.4.8 calOtherCalAdrURIs ....................................12
3 IANA Considerations..............................................12
4 Security Considerations..........................................12
5 Acknowledgments..................................................13
6 Authors' Addresses...............................................13
7 Bibliography.....................................................15
8 Full Copyright Statement.........................................16
1 Calendaring and Scheduling URIs
1日历和计划URI
This memo defines four classes of URIs. URIs are more useful if it is understood what the URIs point to. Here is a brief description:
本备忘录定义了四类URI。如果理解URI所指向的内容，则URI更有用。以下是简要说明：
The free/busy URI is defined to be a transport independent location where a client can obtain information about when a user is busy. At the present time, this URI only points to busy time data. Future revisions of this specification may provide for the extended capability of publishing free time data.
忙/闲URI被定义为与传输无关的位置，客户机可以在其中获取有关用户忙时的信息。目前，此URI仅指向繁忙时间数据。本规范的未来版本可能提供发布自由时间数据的扩展功能。
If a calendaring and scheduling client (i.e., CUA) were to retrieve data from this location using FTP or HTTP, it would get back an iCalendar object [4] containing one or more "VFREEBUSY" calendar components. If a MIME transport is being used, the response will be contained within a "text/calendar" MIME body part as specified in the iCalendar specification [4]. For example:
如果日历和调度客户端（即CUA）使用FTP或HTTP从该位置检索数据，它将返回包含一个或多个“VFREEBUSY”日历组件的iCalendar对象[4]。如果使用MIME传输，响应将包含在iCalendar规范[4]中指定的“文本/日历”MIME正文部分中。例如：
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VFREEBUSY
ATTENDEE:MAILTO:jane_doe@host1.com
DTSTART:19971013T050000Z
DTEND:19971124T050000Z
DTSTAMP:19970901T083000Z
FREEBUSY:19971015T133000Z/19971015T180000Z
FREEBUSY:19971015T190000Z/19971015T220000Z
FBURL:http://www.host.com/calendar/busy/jdoe.ifb
END:VFREEBUSY
END:VCALENDAR
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH
BEGIN:VFREEBUSY
ATTENDEE:MAILTO:jane_doe@host1.com
DTSTART:19971013T050000Z
DTEND:19971124T050000Z
DTSTAMP:19970901T083000Z
FREEBUSY:19971015T133000Z/19971015T180000Z
FREEBUSY:19971015T190000Z/19971015T220000Z
FBURL:http://www.host.com/calendar/busy/jdoe.ifb
END:VFREEBUSY
END:VCALENDAR
The amount of busy time data pointed to by the FBURL will generally be pre-determined; for example one month of busy time data. As a guideline, it is recommended that the previous six weeks of busy time data be published at the location associated with the FBURL. If this URI points to a file resource, it is recommended that the file extension be "ifb" to distinguish it from an arbitrary iCalendar object (e.g., with the "ics" file extension).
FBURL指向的繁忙时间数据量通常是预先确定的；例如，一个月的繁忙时间数据。作为指导原则，建议在与FBURL关联的位置发布前六周的繁忙时间数据。如果此URI指向文件资源，建议文件扩展名为“ifb”，以将其与任意iCalendar对象（例如，具有“ics”文件扩展名）区分开来。
The Calendar Access URI is defined to be a protocol independent location from which a calendaring and scheduling client (i.e., CUA) can communicate with a user's entire calendar.
日历访问URI被定义为独立于协议的位置，日历和调度客户端（即CUA）可以从该位置与用户的整个日历进行通信。
The semantics for using this URI as an access protocol locator are yet to be defined by the IETF CALSCH Working Group. This will be addressed in the "Calendar Access Protocol" specification.
IETF CALSCH工作组尚未定义将此URI用作访问协议定位器的语义。这将在“日历访问协议”规范中解决。
The Calendar URI is defined to be a protocol independent location from which a calendaring and scheduling client (i.e. CUA) can retrieve an entire copy of a user's calendar. Retrieving data from this URI obtains a published "snapshot" of the user's calendar.
日历URI定义为独立于协议的位置，日历和调度客户端（即CUA）可以从中检索用户日历的整个副本。从该URI检索数据将获得用户日历的已发布“快照”。
HTTP URI -- If the URI is an HTTP URI, then the content returned with a GET should be a "text/calendar" MIME body part containing one or more iCalendar object.
HTTP URI——如果URI是HTTP URI，那么GET返回的内容应该是包含一个或多个iCalendar对象的“文本/日历”MIME主体部分。
FTP URI -- If the URI is an FTP URI, then the resource pointed to should be a file with an "ics" file extension containing one or more iCalendar objects.
FTP URI——如果URI是FTP URI，那么指向的资源应该是具有“ics”文件扩展名的文件，其中包含一个或多个iCalendar对象。
There are many cases where a user may have more than one calendar. In these cases, a user may have multiple URIs, each URI pointing to a calendar or free/busy data.
在许多情况下，用户可能有多个日历。在这些情况下，用户可能有多个URI，每个URI都指向日历或忙/闲数据。
To make the case of multiple calendars simpler for clients, the concept of the "default" calendar is introduced. A "default" calendar is one that the user has designated as the calendar that other users should look at when accessing the user's calendar, or retrieving the user's free/busy time.
为了简化客户端使用多个日历的情况，引入了“默认”日历的概念。“默认”日历是用户指定为其他用户在访问用户日历或检索用户的忙/闲时间时应查看的日历。
The default calendar may, in fact, include rolled-up information from all the user's other calendars. The other calendars may only exist for organizational purposes.
事实上，默认日历可能包括来自用户所有其他日历的汇总信息。其他日历可能仅用于组织目的。
2 Distribution
2分布
These four URIs provide valuable pointers to calendaring and scheduling data that other users need in order to know when to schedule meetings, etc. There are several possibilities on how users can communicate these URIs to other users. The following section outlines how these URIs can be distributed to other users.
这四个URI为其他用户提供了宝贵的日历和日程安排数据指针，其他用户需要这些数据才能知道何时安排会议等。关于用户如何与其他用户交流这些URI，存在多种可能性。以下部分概述了如何将这些URI分发给其他用户。
The simplest way to obtain these URIs is for a user to communicate the URIs using some out-of-band mechanism such as verbally, or in an e-mail message, or by printing these URIs on a paper business card.
获取这些URI的最简单方法是用户使用一些带外机制（如口头、电子邮件消息）或通过将这些URI打印在纸制名片上来与URI通信。
When using this mechanism, the user obtains these URIs using an out-of-band mechanism and then enters these URIs into their calendaring software manually.
使用此机制时，用户使用带外机制获取这些URI，然后手动将这些URI输入其日历软件。
A more sophisticated way to obtain these URIs is for users to publish vCards containing these URIs. The vCard object can be transferred between one another. Since many e-mail clients allow a user to automatically include a vCard with every message that the user sends, this provides a simple, transparent way for a user to distribute their calendaring and scheduling URIs.
获取这些URI的更复杂的方法是用户发布包含这些URI的vCard。vCard对象可以在彼此之间传输。由于许多电子邮件客户端允许用户在发送的每封邮件中自动包含vCard，因此这为用户分发日历和计划URI提供了一种简单、透明的方式。
On the receiving end, an e-mail client that provides an integrated vCard database can provide a way to lookup calendaring URIs for users whose vCards are stored locally.
在接收端，提供集成vCard数据库的电子邮件客户端可以为其vCard存储在本地的用户提供查找日历URI的方法。
Since the vCard [3] specification doesn't specify how to encode calendaring URIs in a vCard, this section is provided as an extension to vCard which specifies how to encode calendaring URIs within a vCard.
由于vCard[3]规范未指定如何在vCard中编码日历URI，因此本节作为vCard的扩展提供，该扩展指定如何在vCard中编码日历URI。
Inside a vCard object, four new properties are defined: "CALURI", "CAPURI", "CALADRURI", and "FBURL", as defined above.
在vCard对象中，定义了四个新属性：“CALURI”、“CAPURI”、“CALADRURI”和“FBURL”，如上所述。
Any vCard can have one or more of these properties, each representing a calendar or free/busy time that is associated with the user.
任何vCard都可以具有一个或多个这些属性，每个属性表示与用户关联的日历或忙/闲时间。
One of these properties can be designated as the "default" by adding the "PREF" parameter.
通过添加“PREF”参数，可以将其中一个属性指定为“默认”。
Here is a simple example of a vCard containing a "FBURL" and a "CALURI".
下面是一个包含“FBURL”和“CALURI”的vCard的简单示例。
BEGIN:VCARD
VERSION:3.0
N:Dun;Alec
FN:Alec Dun
ORG:Microsoft Corporation
ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way;
Redmond;WA;98052-6399;USA
TEL;WORK;MSG:+1-206-936-4544
TEL;WORK;FAX:+1-206-936-7329
EMAIL;INTERNET:user@host1.com
CALADRURI;PREF:mailto:user@host1.com
CALURI;PREF:http://cal.host1.com/user/cal.ics
FBURL;PREF:http://cal.host1.com/user/fb.ifb
CALURI:http://cal.company.com/projectA/pjtA.ics
FBURL:http://cal.company.com/projectA/pjtAfb.ifb
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Dun;Alec
FN:Alec Dun
ORG:Microsoft Corporation
ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way;
Redmond;WA;98052-6399;USA
TEL;WORK;MSG:+1-206-936-4544
TEL;WORK;FAX:+1-206-936-7329
EMAIL;INTERNET:user@host1.com
CALADRURI;PREF:mailto:user@host1.com
CALURI;PREF:http://cal.host1.com/user/cal.ics
FBURL;PREF:http://cal.host1.com/user/fb.ifb
CALURI:http://cal.company.com/projectA/pjtA.ics
FBURL:http://cal.company.com/projectA/pjtAfb.ifb
END:VCARD
To: ietf-mime-directory@imc.org
致：ietf mime-directory@imc.org
Subject: Registration of FBURL type for text/directory MIME type vCard profile.
主题：为文本/目录MIME类型vCard配置文件注册FBURL类型。
Type name: FBURL
类型名称：FBURL
Type purpose: To specify the URI for a user's busy time in a vCard object.
类型用途：在vCard对象中指定用户繁忙时间的URI。
Type encoding: 8bit
类型编码：8位
Type value: A single URI value.
类型值：单个URI值。
Type special notes: Where multiple FBURL properties are specified, the default FBURL property is indicated with the PREF parameter. The FTP or HTTP type of URI points to an iCalendar object associated with a snapshot of the last six weeks of the user's busy time data. If the iCalendar object is represented as a file or document, it's file type should be "ifb".
键入特殊注释：如果指定了多个FBURL属性，则默认FBURL属性将使用PREF参数指示。FTP或HTTP类型的URI指向一个iCalendar对象，该对象与用户最近六周繁忙时间数据的快照关联。如果iCalendar对象表示为文件或文档，则其文件类型应为“ifb”。
Intended usage: Refer to section 1.1.
预期用途：参考第1.1节。
Type examples:
类型示例：
FBURL;PREF:http://www.host1.com/busy/janedoe
FBURL:FTP://ftp.host.com/busy/project-a.ifb
FBURL;PREF:http://www.host1.com/busy/janedoe
FBURL:FTP://ftp.host.com/busy/project-a.ifb
To: ietf-mime-directory@imc.org
致：ietf mime-directory@imc.org
Subject: Registration of CALADRURI type for application/directory MIME type vCard profile.
主题：为应用程序/目录MIME类型vCard配置文件注册CALADRURI类型。
Type name: CALADRURI
类型名称：CALADRURI
Type purpose: To specify the location to which an event request should be sent for the user.
类型用途：指定为用户发送事件请求的位置。
Type encoding: 8bit
类型编码：8位
Type value: A single URI value.
类型值：单个URI值。
Type special notes: Where multiple CALADRURI properties are specified, the default CALADRURI property is indicated with the PREF parameter.
键入特殊注释：如果指定了多个CALADRURI属性，则默认的CALADRURI属性用PREF参数表示。
Intended usage: Refer to section 1.2.
预期用途：参考第1.2节。
Type examples:
类型示例：
CALADRURI;PREF:mailto:janedoe@host.com
CALADRURI;PREF:mailto:janedoe@host.com
To: ietf-mime-directory@imc.org
致：ietf mime-directory@imc.org
Subject: Registration of CAPURI type for application/directory MIME type vCard profile.
主题：为应用程序/目录MIME类型vCard配置文件注册CAPURI类型。
Type name: CAPURI
类型名称：CAPURI
Type purpose: To specify a protocol independent location from which a calendaring and scheduling client (i.e., CUA) can communicate with a user's entire calendar.
类型用途：指定独立于协议的位置，日历和调度客户端（即CUA）可以从该位置与用户的整个日历进行通信。
Type encoding: 8bit
类型编码：8位
Type value: A single URI value.
类型值：单个URI值。
Type special notes: Where multiple CAPURI properties are specified, the default CAPURI property is indicated with the PREF parameter.
键入特殊注释：如果指定了多个CAPURI属性，则默认的CAPURI属性用PREF参数表示。
Intended usage: Refer to section 1.3.
预期用途：参考第1.3节。
To: ietf-mime-directory@imc.org
致：ietf mime-directory@imc.org
Subject: Registration of CALURI type for text/directory MIME type vCard profile.
主题：为文本/目录MIME类型vCard配置文件注册CALURI类型。
Type name: CALURI
类型名称：CALURI
Type purpose: To specify the URI for a user's calendar in a vCard object.
类型用途：在vCard对象中指定用户日历的URI。
Type encoding: 8bit
类型编码：8位
Type value type: A single URI value.
类型值类型：单个URI值。
Type special notes: Where multiple CALURI properties are specified, the default CALURI property is indicated with the PREF parameter. The property should contain a URI pointing to an iCalendar object associated with a snapshot of the user's calendar store. If the iCalendar object is represented as a file or document, it's file type should be "ics".
键入特殊注释：如果指定了多个CALURI属性，则默认的CALURI属性用PREF参数表示。属性应包含一个URI，该URI指向与用户日历存储快照关联的iCalendar对象。如果iCalendar对象表示为文件或文档，则其文件类型应为“ics”。
Intended usage: Refer to section 1.4.
预期用途：参考第1.4节。
Type examples:
类型示例：
CALURI;PREF:http://cal.host1.com/calA
CALURI:ftp://ftp.host1.com/calA.ics
CALURI;PREF:http://cal.host1.com/calA
CALURI:ftp://ftp.host1.com/calA.ics
Another way to obtain these URIs is to look them up in a directory using the LDAP protocol [1].
获取这些URI的另一种方法是使用LDAP协议[1]在目录中查找它们。
If a user's URIs can be found using directory lookup (i.e., searching for one of the LDAP schema extensions defined below), they should, in general, be considered "more up-to-date" than URIs in any vCards that are stored locally.
如果可以使用目录查找（即，搜索下面定义的LDAP模式扩展之一）找到用户的URI，则通常应将其视为比本地存储的任何vCard中的URI“更为最新”。
In order to encode the calendaring URIs in the directory, the following are defined:
为了对目录中的日历URI进行编码，定义了以下内容：
- One object class:
- 一个对象类：
- calEntry
- 卡伦特里
- Eight attributes:
- 八个属性：
- calCalURI
- 钙质
- calFBURL
- 牛犊
- calCAPURI
- 卡尔卡普里
- calCalAdrURI
- 卡尔卡德鲁里
- calOtherCalURIs
- calOtherCalURIs
- calOtherFBURLs
- calOtherFBURLs
- calOtherCAPURIs
- 钙热卡普里斯
- calOtherCalAdrURIs
- 卡拉德鲁里斯酒店
The calCalURI contains the URI to a snapshot of the user's entire default calendar. The calFBURL contains the URI to the user's default busy time data. The calCAPURI represents contains a URI that can be used to communicate with the user's calendar. The calCalAdrURI contains a URI that points to the location to which event requests should be sent for that user.
calCalURI包含用户整个默认日历快照的URI。calFBURL包含用户默认繁忙时间数据的URI。calCAPURI表示包含一个URI，可用于与用户的日历通信。calCalAdrURI包含一个URI，该URI指向应该为该用户发送事件请求的位置。
The calOtherCalURIs is a multi-valued property containing URIs to snapshots of other calendars that the user may have. The calOtherFBURLs is a multi-valued property containing URIs to other free/busy data that the user may have. The calOtherCAPURIs attribute is a multi-valued property containing URIs to other calendars that the user may have. The calOtherCalAdrURIs attribute is a multi-valued property containing URIs to other locations that a user may want event requests sent to.
CalotherCalURI是一个多值属性，包含用户可能拥有的其他日历快照的URI。CalotherFBURL是一个多值属性，包含用户可能拥有的其他忙/闲数据的URI。calOtherCAPURIs属性是一个多值属性，包含用户可能拥有的其他日历的URI。calOtherCalAdrURIs属性是一个多值属性，包含用户可能希望将事件请求发送到的其他位置的URI。
There is no predetermined order to the values in either multi-valued property.
两个多值属性中的值都没有预定顺序。
The notation used in this memo is the same as that used in [2].
本备忘录中使用的符号与[2]中使用的符号相同。
The Calendar Entry is a class derived from "TOP" [2], which contains the four calendaring attributes.
日历项是从“TOP”[2]派生的类，它包含四个日历属性。
(1.2.840.113556.1.5.87 NAME 'calEntry' TOP AUXILIARY MAY (calCalURI calFBURL calOtherCalURIs calOtherFBURLs calCAPURI calOtherCAPURLs) )
（1.2.840.113556.1.5.87名称“calEntry”顶部辅助可能（calCalURI CalfUrl calOtherCalURIs CalotherfUrls CalotherfUrls Calapuri calOtherCAPURLs））
(1.2.840.113556.1.4.478 NAME 'calCalURI' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )
（1.2.840.113556.1.4.478名称'calCalURI'相等caseIgnoreMatch子字符串caseIgnoreMatch语法'IA5String'用法用户应用程序）
(1.2.840.113556.1.4.479 NAME 'calFBURL' EQUALITY caseIgnoreMatch
（1.2.840.113556.1.4.479名称“calFBURL”相等caseIgnoreMatch
SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )
子字符串caseIgnoreMatch语法“IA5String”用法（用户应用程序）
(1.2.840.113556.1.4.480 NAME 'calCAPURI' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )
（1.2.840.113556.1.4.480名称'Calapuri'相等caseIgnoreMatch子字符串caseIgnoreMatch语法'IA5String'用法用户应用程序）
(1.2.840.113556.1.4.481 NAME 'calCalAdrURI' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )
（1.2.840.113556.1.4.481名称'calCalAdrURI'相等caseIgnoreMatch子字符串caseIgnoreMatch语法'IA5String'用法用户应用程序）
(1.2.840.113556.1.4.482 NAME 'calOtherCalURIs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )
（1.2.840.113556.1.4.482名称“calOtherCalURIs”相等caseIgnoreMatch子字符串caseIgnoreMatch语法“IA5String”多值用法用户应用程序）
(1.2.840.113556.1.4.483 NAME 'calOtherFBURLs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )
（1.2.840.113556.1.4.483名称“calOtherFBURLs”相等caseIgnoreMatch子字符串caseIgnoreMatch语法“IA5String”多值用法用户应用程序）
(1.2.840.113556.1.4.484 NAME 'calOtherCAPURIs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )
（1.2.840.113556.1.4.484名称“calOtherCAPURIs”相等caseIgnoreMatch子字符串caseIgnoreMatch语法“IA5String”多值用法用户应用程序）
(1.2.840.113556.1.4.485 NAME 'calOtherCalAdrURIs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )
（1.2.840.113556.1.4.485名称'calOtherCalAdrURIs'相等caseIgnoreMatch子字符串caseIgnoreMatch语法'IA5String'多值用法用户应用程序）
3 IANA Considerations
3 IANA考虑因素
This memo defines IANA registered extensions to the attributes defined by LDAP [1] and vCard [3].
此备忘录定义了由LDAP[1]和vCard[3]定义的属性的IANA注册扩展。
IANA registration proposals for vCard are to be emailed to the registration agent for the "text/directory" MIME content-type, <MAILTO: ietf-mime-directory@imc.org> using the format defined in [3].
将通过电子邮件向注册代理发送vCard的IANA注册建议，内容类型为“text/directory”MIME，<MAILTO:ietf MIME-directory@imc.org>使用[3]中定义的格式。
4 Security Considerations
4安全考虑
Standard vCard and LDAP security rules and support apply for the extensions described in this document, and there are no special security issues for these extensions.
标准vCard和LDAP安全规则和支持适用于本文档中描述的扩展，这些扩展没有特殊的安全问题。
Please note, though, that LDAP servers may permit anonymous clients to refresh entries which they did not create. Servers are also permitted to control a refresh access to an entry by requiring clients to bind before issuing a RefreshRequest. This will have implications on the server performance and scalability.
但请注意，LDAP服务器可能允许匿名客户端刷新它们没有创建的条目。服务器还可以通过要求客户端在发出刷新请求之前绑定来控制对条目的刷新访问。这将对服务器性能和可伸缩性产生影响。
Please also note, though, that vCard objects may have been created by an entity other than that represented by the vCard. Recipients should be certain of the source that generated the vCard.
但也请注意，vCard对象可能是由vCard表示的实体以外的实体创建的。收件人应确定生成vCard的来源。
Also, care should be taken in making use of information obtained from directory servers that has been supplied by client, as it may now be out of date. In many networks, for example, IP addresses are automatically assigned when a host connects to the network, and may be reassigned if that host later disconnects. An IP address obtained from the directory may no longer be assigned to the host that placed the address in the directory. This issue is not specific to LDAP or dynamic directories.
此外，在使用从客户机提供的目录服务器获得的信息时应注意，因为这些信息现在可能已过时。例如，在许多网络中，当主机连接到网络时，IP地址会自动分配，如果该主机稍后断开连接，IP地址可能会重新分配。从目录中获取的IP地址可能不再分配给将该地址放置在该目录中的主机。此问题不特定于LDAP或动态目录。
5 Acknowledgments
5致谢
The authors wish to acknowledge the work of Alec Dun, who acted as an author for the early drafts of this memo. In addition, this document received input from the various participants in the IETF CALSCH Working Group discussions.
作者希望感谢Alec Dun的工作，他是本备忘录早期草稿的作者。此外，本文件还收到了IETF CALSCH工作组讨论会各参与者的意见。
6 Authors' Addresses
6作者地址
The following address information is provided in a vCard v3.0 [3], Electronic Business Card, format.
以下地址信息以vCard v3.0[3]电子名片格式提供。
BEGIN:VCARD
VERSION:3.0
N:Small;Tony
FN:Tony Small
ORG:XpertSite.Com
ADR;TYPE=WORK,POSTAL,PARCEL:;;4700 42nd Ave. SW, Suite 440;
Seattle;WA;98116;USA
TEL;TYPE=WORK,MSG:+1-206-937-9972
TEL;TYPE=WORK,FAX:+1-206-936-7329
EMAIL;TYPE=INTERNET:tony@xpertsite.com
CALADRURI:MAILTO:tony@xpertsite.com
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Small;Tony
FN:Tony Small
ORG:XpertSite.Com
ADR;TYPE=WORK,POSTAL,PARCEL:;;4700 42nd Ave. SW, Suite 440;
Seattle;WA;98116;USA
TEL;TYPE=WORK,MSG:+1-206-937-9972
TEL;TYPE=WORK,FAX:+1-206-936-7329
EMAIL;TYPE=INTERNET:tony@xpertsite.com
CALADRURI:MAILTO:tony@xpertsite.com
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Hennessy;Denis
FN:Denis Hennessy
ORG:ISOCOR
ADR;TYPE=WORK,POSTAL,PARCEL:;;42-47 Lower Mount St;
Dublin 2;Ireland
TEL;TYPE=WORK,MSG:+353-1-676-0366
TEL;TYPE=WORK,FAX:+353-1-676-0856
EMAIL;TYPE=INTERNET:denis.hennessy@isocor.com
CALADRURI:MAILTO:denis.hennessy@isocor.com
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Hennessy;Denis
FN:Denis Hennessy
ORG:ISOCOR
ADR;TYPE=WORK,POSTAL,PARCEL:;;42-47 Lower Mount St;
Dublin 2;Ireland
TEL;TYPE=WORK,MSG:+353-1-676-0366
TEL;TYPE=WORK,FAX:+353-1-676-0856
EMAIL;TYPE=INTERNET:denis.hennessy@isocor.com
CALADRURI:MAILTO:denis.hennessy@isocor.com
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Dawson;Frank
FN:Frank Dawson
ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive;
Raleigh;NC;27613-3502;USA
TEL;TYPE=WORK,PREF:+1-617-693-8728
TEL;TYPE=WORK,MSG:+1-919-676-9515
TEL;TYPE=FAX:+1-617-693-8728
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net
CALADRURI;TYPE=PREF:MAILTO:Frank_Dawson@Lotus.com
CALADRURI:MAILTO:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Dawson;Frank
FN:Frank Dawson
ORG:Lotus Development Corporation
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive;
Raleigh;NC;27613-3502;USA
TEL;TYPE=WORK,PREF:+1-617-693-8728
TEL;TYPE=WORK,MSG:+1-919-676-9515
TEL;TYPE=FAX:+1-617-693-8728
EMAIL;TYPE=INTERNET,PREF:Frank_Dawson@Lotus.com
EMAIL;TYPE=INTERNET:fdawson@earthlink.net
CALADRURI;TYPE=PREF:MAILTO:Frank_Dawson@Lotus.com
CALADRURI:MAILTO:fdawson@earthlink.net
URL:http://home.earthlink.net/~fdawson
END:VCARD
This memo is a result of the work of the Internet Engineering Task Force Calendaring and scheduling Working Group. The chairman of that working group is:
本备忘录是互联网工程任务组日历和日程安排工作组工作的结果。该工作组的主席是：
BEGIN:VCARD
VERSION:3.0
N:Egen;Pat
FN:Pat Egen
ORG:Engan Consulting
ADR;TYPE=WORK:;;803 Creek Overlook;Chattanooga;TN;37415;USA
TEL;TYPE=WORK,VOICE:423.875.2652
TEL;TYPE=WORK,FAX:423.875.2017
EMAIL:pregen@egenconsulting.com
URL:http://www.egenconsulting.com
CALADRURI:MAILTO:pregen@egenconsulting.com
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Egen;Pat
FN:Pat Egen
ORG:Engan Consulting
ADR;TYPE=WORK:;;803 Creek Overlook;Chattanooga;TN;37415;USA
TEL;TYPE=WORK,VOICE:423.875.2652
TEL;TYPE=WORK,FAX:423.875.2017
EMAIL:pregen@egenconsulting.com
URL:http://www.egenconsulting.com
CALADRURI:MAILTO:pregen@egenconsulting.com
END:VCARD
7 Bibliography
7参考书目
[1] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3)", RFC 2251, December 1997.
[1] Wahl，M.，Howes，T.和S.Kille，“轻量级目录访问协议（v3）”，RFC 2251，1997年12月。
[2] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997.
[2] Wahl，M.，Coulbeck，A.，Howes，T.和S.Kille，“轻量级目录访问协议（v3）：属性语法定义”，RFC2252，1997年12月。
[3] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998.
[3] Dawson，F.和T.Howes，“vCard MIME目录配置文件”，RFC24261998年9月。
[4] Dawson, F. and D. Stenerson, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1997.
[4] Dawson，F.和D.Stenerson，“互联网日历和调度核心对象规范（iCalendar）”，RFC 24451997年11月。
[5] Dawson, F. and S. Mansour, "iCalendar Message-Based Interopability Protocal (iMIP)", RFC 2447, November 1997.
[5] Dawson，F.和S.Mansour，“iCalendar基于消息的互操作性协议（iMIP）”，RFC 2447，1997年11月。
8 Full Copyright Statement
8完整版权声明
Copyright (C) The Internet Society (2000). All Rights Reserved.
版权所有（C）互联网协会（2000年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。