RFC 2739 - Calendar Attributes for vCard and LDAP 中文翻译

原文URL : https://datatracker.ietf.org/doc/html/rfc2739
文档标题 : RFC 2739 - vCard 和 LDAP 的日历属性
翻译方式 : 自动生成

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）。本备忘录的分发不受限制。

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

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 就会更有用。下面是简要说明：

1.1 Free/Busy URI (FBURL)

1.1 空闲/繁忙 URI (FBURL)

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 从该位置检索数据，它将得到一个 iCalendar 对象 [4]，其中包含一个或多个 "VFREEBUSY "日历组件。如果使用的是 MIME 传输，响应将包含在 iCalendar 规范 [4] 中指定的 "text/calendar "MIME 主体部分中。例如

      BEGIN:VCALENDAR
      VERSION:2.0
      PRODID:-//hacksw/handcal//NONSGML v1.0//EN
      METHOD:PUBLISH
      BEGIN:VFREEBUSY
      ATTENDEE:MAILTO:[email protected]
      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"）。

1.2 Calendar Access URI (CAPURI)

1.2 日历访问 URI (CAPURI)

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.

将此 URI 用作访问协议定位器的语义尚未由 IETF CALSCH 工作组定义。这将在 "日历访问协议 "规范中解决。

1.3 Calendar URI (CALURI)

1.3 日历 URI (CALURI)

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 对象的 "text/calendar "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 对象。

1.4 Default URIs

1.4 默认 URI

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。

2.1 Manual Transfer

2.1 手动传输

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。

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 输入其日历软件。

2.2 Personal Data Exchange Using A vCard

2.2 使用 vCard 交换个人数据

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 的方法。

2.3 vCard Schema Extensions

2.3 vCard 模式扩展

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:[email protected]
      CALADRURI;PREF:mailto:[email protected]
      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

2.3.1 FBURL Property IANA Registration

2.3.1 FBURL 属性 IANA 注册

To: [email protected]

收件人：[email protected]

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

2.3.2 CALADRURI Property IANA Registration

2.3.2 CALADRURI 属性 IANA 注册

To: [email protected]

收件人：[email protected]

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:[email protected]

2.3.3 CAPURI Property IANA Registration

2.3.3 CAPURI 属性 IANA 注册

To: [email protected]

收件人：[email protected]

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 节。

2.3.4 CALURI Property IANA Registration

2.3.4 CALURI 属性 IANA 注册

To: [email protected]

收件人：[email protected]

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，指向与用户日历存储快照相关联的 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

2.4 Directory Lookup Using The LDAP v3 Protocol

2.4 使用 LDAP v3 协议进行目录查询

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.

如果用户的 URI 可以通过目录查找（即搜索下面定义的 LDAP 模式扩展之一）找到，一般来说，这些 URI 应被视为比本地存储的任何 vCard 中的 URI 更 "最新"。

2.4.1 LDAP Schema Extensions

2.4.1 LDAP 模式扩展

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

- 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，指向应为该用户发送事件请求的位置。

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.

calOtherCalURIs 是一个多值属性，包含用户可能拥有的其他日历快照的 URI。calOtherFBURLs 属性是一个多值属性，包含用户可能拥有的其他空闲/忙时数据的 URI。calOtherCAPURIs 属性是一个多值属性，包含用户可能拥有的其他日历的 URI。calOtherCalAdrURIs 属性是一个多值属性，包含用户希望将事件请求发送到的其他位置的 URI。

There is no predetermined order to the values in either multi-valued property.

多值属性中的值都没有预定顺序。

2.4.2 Notation

2.4.2 符号

The notation used in this memo is the same as that used in [2].

本备忘录中使用的符号与 [2] 中使用的符号相同。

2.4.3 Object Definitions

2.4.3 对象定义

2.4.3.1 calEntry

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' 顶部辅助 MAY (calCalURI calFBURL calOtherCalURIs calOtherFBURLs calCAPURI calOtherCAPURLs) )

2.4.4 Attribute Definitions

2.4.4 属性定义

2.4.4.1 calCalURI

(1.2.840.113556.1.4.478 NAME 'calCalURI' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )

2.4.4.2 calFBURL

(1.2.840.113556.1.4.479 NAME 'calFBURL' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )

2.4.4.3 calCAPURI

(1.2.840.113556.1.4.480 NAME 'calCAPURI' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )

2.4.4.4 calCalAdrURI

(1.2.840.113556.1.4.481 NAME 'calCalAdrURI' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' USAGE userApplications )

2.4.4.5 calOtherCalURIs

(1.2.840.113556.1.4.482 NAME 'calOtherCalURIs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )

2.4.4.6 calOtherFBURLs

(1.2.840.113556.1.4.483 NAME 'calOtherFBURLs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )

2.4.4.7 calOtherCAPURIs

(1.2.840.113556.1.4.484 NAME 'calOtherCAPURIs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )

2.4.4.8 calOtherCalAdrURIs

(1.2.840.113556.1.4.485 NAME 'calOtherCalAdrURIs' EQUALITY caseIgnoreMatch SUBSTRING caseIgnoreMatch SYNTAX 'IA5String' MULTI-VALUE USAGE userApplications )

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: [email protected]> using the format defined in [3].

vCard 的 IANA 注册建议应使用 [3] 中定义的格式，通过电子邮件发送给 "文本/目录 "MIME 内容类型的注册代理，<MAILTO: [email protected]>。

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 服务器可能允许匿名客户端刷新并非由其创建的条目。服务器也可以通过要求客户端在发出 RefreshRequest 之前进行绑定来控制条目的刷新访问权限。这将对服务器的性能和可扩展性产生影响。

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:[email protected]
   CALADRURI:MAILTO:[email protected]
   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:[email protected]
   CALADRURI:MAILTO:[email protected]
   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:[email protected]
   EMAIL;TYPE=INTERNET:[email protected]
   CALADRURI;TYPE=PREF:MAILTO:[email protected]
   CALADRURI:MAILTO:[email protected]
   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:

本备忘录是互联网工程任务组（Internet Engineering Task Force Calendaring and scheduling Working Group）的工作成果。该工作组的主席是

   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:[email protected]
   URL:http://www.egenconsulting.com
   CALADRURI:MAILTO:[email protected]
   END:VCARD

7 Bibliography

7 参考书目

[1] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access Protocol (v3)", RFC 2251, December 1997.

[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. and S. Kille, "Lightweight Directory Access Protocol (v3)：属性语法定义"，RFC 2252，1997 年 12 月。

[3] Dawson, F. and T. Howes, "vCard MIME Directory Profile", RFC 2426, September 1998.

[4] Dawson, F. and D. Stenerson, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1997.

[4] Dawson, F. 和 D. Stenerson, "Internet Calendaring and Scheduling Core Object Specification (iCalendar)", RFC 2445, November 1997.

[5] Dawson, F. and S. Mansour, "iCalendar Message-Based Interopability Protocal (iMIP)", RFC 2447, November 1997.

8 Full Copyright Statement

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 编辑职能的经费目前由互联网协会提供。