| 1 |
<pre>Network Working Group T. Small |
| 2 |
Request for Comments: 2739 XpertSite.Com |
| 3 |
Category: Standards Track D. Hennessy |
| 4 |
ISOCOR |
| 5 |
F. Dawson |
| 6 |
Lotus |
| 7 |
January 2000 |
| 8 |
|
| 9 |
|
| 10 |
<span class="h1">Calendar Attributes for vCard and LDAP</span> |
| 11 |
|
| 12 |
|
| 13 |
Status of this Memo |
| 14 |
|
| 15 |
This document specifies an Internet standards track protocol for the |
| 16 |
Internet community, and requests discussion and suggestions for |
| 17 |
improvements. Please refer to the current edition of the "Internet |
| 18 |
Official Protocol Standards" (STD 1) for the standardization state |
| 19 |
and status of this protocol. Distribution of this memo is unlimited. |
| 20 |
|
| 21 |
Copyright Notice |
| 22 |
|
| 23 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 24 |
|
| 25 |
Abstract |
| 26 |
|
| 27 |
When scheduling a calendar entity, such as an event, it is a |
| 28 |
prerequisite that an organizer has the calendar address of each |
| 29 |
attendee that will be invited to the event. Additionally, access to |
| 30 |
an attendee's current "busy time" provides an a priori indication of |
| 31 |
whether the attendee will be free to participate in the event. |
| 32 |
|
| 33 |
In order to meet these challenges, a calendar user agent (CUA) needs |
| 34 |
a mechanism to locate (URI) individual user's calendar and free/busy |
| 35 |
time. |
| 36 |
|
| 37 |
This memo defines three mechanisms for obtaining a URI to a user's |
| 38 |
calendar and free/busy time. These include: |
| 39 |
|
| 40 |
- Manual transfer of the information; |
| 41 |
|
| 42 |
- Personal data exchange using the vCard format; and |
| 43 |
|
| 44 |
- Directory lookup using the LDAP protocol. |
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Small, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a> CALENDARING AND SCHEDULING URIS...................................<a href="#page-3">3</a> |
| 60 |
<a href="#section-1.1">1.1</a> FREE/BUSY URI (FBURL) .........................................<a href="#page-3">3</a> |
| 61 |
<a href="#section-1.2">1.2</a> CALENDAR ACCESS URI (CAPURI) ..................................<a href="#page-4">4</a> |
| 62 |
<a href="#section-1.3">1.3</a> CALENDAR URI (CALURI) .........................................<a href="#page-4">4</a> |
| 63 |
<a href="#section-1.4">1.4</a> DEFAULT URIS ..................................................<a href="#page-4">4</a> |
| 64 |
<a href="#section-2">2</a> DISTRIBUTION......................................................<a href="#page-4">4</a> |
| 65 |
<a href="#section-2.1">2.1</a> MANUAL TRANSFER ...............................................<a href="#page-5">5</a> |
| 66 |
<a href="#section-2.2">2.2</a> PERSONAL DATA EXCHANGE USING A VCARD ..........................<a href="#page-5">5</a> |
| 67 |
<a href="#section-2.3">2.3</a> VCARD SCHEMA EXTENSIONS .......................................<a href="#page-5">5</a> |
| 68 |
<a href="#section-2.3.1">2.3.1</a> FBURL Property IANA Registration ...........................<a href="#page-6">6</a> |
| 69 |
<a href="#section-2.3.2">2.3.2</a> CALADRURI Property IANA Registration .......................<a href="#page-7">7</a> |
| 70 |
<a href="#section-2.3.3">2.3.3</a> CAPURI Property IANA Registration ......................... <a href="#page-8">8</a> |
| 71 |
<a href="#section-2.3.4">2.3.4</a> CALURI Property IANA Registration ......................... <a href="#page-8">8</a> |
| 72 |
<a href="#section-2.4">2.4</a> DIRECTORY LOOKUP USING THE LDAP V3 PROTOCOL .................. <a href="#page-9">9</a> |
| 73 |
<a href="#section-2.4.1">2.4.1</a> LDAP Schema Extensions .................................... <a href="#page-9">9</a> |
| 74 |
<a href="#section-2.4.2">2.4.2</a> Notation ..................................................<a href="#page-10">10</a> |
| 75 |
<a href="#section-2.4.3">2.4.3</a> Object Definitions ........................................<a href="#page-10">10</a> |
| 76 |
<a href="#section-2.4.3.1">2.4.3.1</a> calEntry ..............................................<a href="#page-10">10</a> |
| 77 |
<a href="#section-2.4.4">2.4.4</a> Attribute Definitions .....................................<a href="#page-10">10</a> |
| 78 |
<a href="#section-2.4.4.1">2.4.4.1</a> calCalURI .............................................<a href="#page-10">10</a> |
| 79 |
<a href="#section-2.4.4.2">2.4.4.2</a> calFBURL ..............................................<a href="#page-10">10</a> |
| 80 |
<a href="#section-2.4.4.3">2.4.4.3</a> calCAPURI .............................................<a href="#page-11">11</a> |
| 81 |
<a href="#section-2.4.4.4">2.4.4.4</a> calCalAdrURI ..........................................<a href="#page-11">11</a> |
| 82 |
<a href="#section-2.4.4.5">2.4.4.5</a> calOtherCalURIs .......................................<a href="#page-11">11</a> |
| 83 |
<a href="#section-2.4.4.6">2.4.4.6</a> calOtherFBURLs ........................................<a href="#page-11">11</a> |
| 84 |
<a href="#section-2.4.4.7">2.4.4.7</a> calOtherCAPURIs .......................................<a href="#page-12">12</a> |
| 85 |
<a href="#section-2.4.4.8">2.4.4.8</a> calOtherCalAdrURIs ....................................<a href="#page-12">12</a> |
| 86 |
<a href="#section-3">3</a> IANA Considerations..............................................<a href="#page-12">12</a> |
| 87 |
<a href="#section-4">4</a> Security Considerations..........................................<a href="#page-12">12</a> |
| 88 |
<a href="#section-5">5</a> Acknowledgments..................................................<a href="#page-13">13</a> |
| 89 |
<a href="#section-6">6</a> Authors' Addresses...............................................<a href="#page-13">13</a> |
| 90 |
<a href="#section-7">7</a> Bibliography.....................................................<a href="#page-15">15</a> |
| 91 |
<a href="#section-8">8</a> Full Copyright Statement.........................................<a href="#page-16">16</a> |
| 92 |
|
| 93 |
|
| 94 |
|
| 95 |
|
| 96 |
|
| 97 |
|
| 98 |
|
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Small, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Calendaring and Scheduling URIs</span> |
| 114 |
|
| 115 |
This memo defines four classes of URIs. URIs are more useful if it is |
| 116 |
understood what the URIs point to. Here is a brief description: |
| 117 |
|
| 118 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Free/Busy URI (FBURL)</span> |
| 119 |
|
| 120 |
The free/busy URI is defined to be a transport independent location |
| 121 |
where a client can obtain information about when a user is busy. At |
| 122 |
the present time, this URI only points to busy time data. Future |
| 123 |
revisions of this specification may provide for the extended |
| 124 |
capability of publishing free time data. |
| 125 |
|
| 126 |
If a calendaring and scheduling client (i.e., CUA) were to retrieve |
| 127 |
data from this location using FTP or HTTP, it would get back an |
| 128 |
iCalendar object [<a href="#ref-4" title=""Internet Calendaring and Scheduling Core Object Specification (iCalendar)"">4</a>] containing one or more "VFREEBUSY" calendar |
| 129 |
components. If a MIME transport is being used, the response will be |
| 130 |
contained within a "text/calendar" MIME body part as specified in the |
| 131 |
iCalendar specification [<a href="#ref-4" title=""Internet Calendaring and Scheduling Core Object Specification (iCalendar)"">4</a>]. For example: |
| 132 |
|
| 133 |
BEGIN:VCALENDAR |
| 134 |
VERSION:2.0 |
| 135 |
PRODID:-//hacksw/handcal//NONSGML v1.0//EN |
| 136 |
METHOD:PUBLISH |
| 137 |
BEGIN:VFREEBUSY |
| 138 |
ATTENDEE:MAILTO:[email protected] |
| 139 |
DTSTART:19971013T050000Z |
| 140 |
DTEND:19971124T050000Z |
| 141 |
DTSTAMP:19970901T083000Z |
| 142 |
FREEBUSY:19971015T133000Z/19971015T180000Z |
| 143 |
FREEBUSY:19971015T190000Z/19971015T220000Z |
| 144 |
FBURL:http://www.host.com/calendar/busy/jdoe.ifb |
| 145 |
END:VFREEBUSY |
| 146 |
END:VCALENDAR |
| 147 |
|
| 148 |
The amount of busy time data pointed to by the FBURL will generally |
| 149 |
be pre-determined; for example one month of busy time data. As a |
| 150 |
guideline, it is recommended that the previous six weeks of busy time |
| 151 |
data be published at the location associated with the FBURL. If this |
| 152 |
URI points to a file resource, it is recommended that the file |
| 153 |
extension be "ifb" to distinguish it from an arbitrary iCalendar |
| 154 |
object (e.g., with the "ics" file extension). |
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Small, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a> Calendar Access URI (CAPURI)</span> |
| 170 |
|
| 171 |
The Calendar Access URI is defined to be a protocol independent |
| 172 |
location from which a calendaring and scheduling client (i.e., CUA) |
| 173 |
can communicate with a user's entire calendar. |
| 174 |
|
| 175 |
The semantics for using this URI as an access protocol locator are |
| 176 |
yet to be defined by the IETF CALSCH Working Group. This will be |
| 177 |
addressed in the "Calendar Access Protocol" specification. |
| 178 |
|
| 179 |
<span class="h3"><a class="selflink" id="section-1.3" href="#section-1.3">1.3</a> Calendar URI (CALURI)</span> |
| 180 |
|
| 181 |
The Calendar URI is defined to be a protocol independent location |
| 182 |
from which a calendaring and scheduling client (i.e. CUA) can |
| 183 |
retrieve an entire copy of a user's calendar. Retrieving data from |
| 184 |
this URI obtains a published "snapshot" of the user's calendar. |
| 185 |
|
| 186 |
HTTP URI -- If the URI is an HTTP URI, then the content returned with |
| 187 |
a GET should be a "text/calendar" MIME body part containing one or |
| 188 |
more iCalendar object. |
| 189 |
|
| 190 |
FTP URI -- If the URI is an FTP URI, then the resource pointed to |
| 191 |
should be a file with an "ics" file extension containing one or more |
| 192 |
iCalendar objects. |
| 193 |
|
| 194 |
<span class="h3"><a class="selflink" id="section-1.4" href="#section-1.4">1.4</a> Default URIs</span> |
| 195 |
|
| 196 |
There are many cases where a user may have more than one calendar. In |
| 197 |
these cases, a user may have multiple URIs, each URI pointing to a |
| 198 |
calendar or free/busy data. |
| 199 |
|
| 200 |
To make the case of multiple calendars simpler for clients, the |
| 201 |
concept of the "default" calendar is introduced. A "default" calendar |
| 202 |
is one that the user has designated as the calendar that other users |
| 203 |
should look at when accessing the user's calendar, or retrieving the |
| 204 |
user's free/busy time. |
| 205 |
|
| 206 |
The default calendar may, in fact, include rolled-up information from |
| 207 |
all the user's other calendars. The other calendars may only exist |
| 208 |
for organizational purposes. |
| 209 |
|
| 210 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Distribution</span> |
| 211 |
|
| 212 |
These four URIs provide valuable pointers to calendaring and |
| 213 |
scheduling data that other users need in order to know when to |
| 214 |
schedule meetings, etc. There are several possibilities on how users |
| 215 |
can communicate these URIs to other users. The following section |
| 216 |
outlines how these URIs can be distributed to other users. |
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Small, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 223 |
|
| 224 |
|
| 225 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Manual Transfer</span> |
| 226 |
|
| 227 |
The simplest way to obtain these URIs is for a user to communicate |
| 228 |
the URIs using some out-of-band mechanism such as verbally, or in an |
| 229 |
e-mail message, or by printing these URIs on a paper business card. |
| 230 |
|
| 231 |
When using this mechanism, the user obtains these URIs using an out- |
| 232 |
of-band mechanism and then enters these URIs into their calendaring |
| 233 |
software manually. |
| 234 |
|
| 235 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Personal Data Exchange Using A vCard</span> |
| 236 |
|
| 237 |
A more sophisticated way to obtain these URIs is for users to publish |
| 238 |
vCards containing these URIs. The vCard object can be transferred |
| 239 |
between one another. Since many e-mail clients allow a user to |
| 240 |
automatically include a vCard with every message that the user sends, |
| 241 |
this provides a simple, transparent way for a user to distribute |
| 242 |
their calendaring and scheduling URIs. |
| 243 |
|
| 244 |
On the receiving end, an e-mail client that provides an integrated |
| 245 |
vCard database can provide a way to lookup calendaring URIs for users |
| 246 |
whose vCards are stored locally. |
| 247 |
|
| 248 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> vCard Schema Extensions</span> |
| 249 |
|
| 250 |
Since the vCard [<a href="#ref-3" title=""vCard MIME Directory Profile"">3</a>] specification doesn't specify how to encode |
| 251 |
calendaring URIs in a vCard, this section is provided as an extension |
| 252 |
to vCard which specifies how to encode calendaring URIs within a |
| 253 |
vCard. |
| 254 |
|
| 255 |
Inside a vCard object, four new properties are defined: "CALURI", |
| 256 |
"CAPURI", "CALADRURI", and "FBURL", as defined above. |
| 257 |
|
| 258 |
Any vCard can have one or more of these properties, each representing |
| 259 |
a calendar or free/busy time that is associated with the user. |
| 260 |
|
| 261 |
One of these properties can be designated as the "default" by adding |
| 262 |
the "PREF" parameter. |
| 263 |
|
| 264 |
|
| 265 |
|
| 266 |
|
| 267 |
|
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Small, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 279 |
|
| 280 |
|
| 281 |
Here is a simple example of a vCard containing a "FBURL" and a |
| 282 |
"CALURI". |
| 283 |
|
| 284 |
BEGIN:VCARD |
| 285 |
VERSION:3.0 |
| 286 |
N:Dun;Alec |
| 287 |
FN:Alec Dun |
| 288 |
ORG:Microsoft Corporation |
| 289 |
ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way; |
| 290 |
Redmond;WA;98052-6399;USA |
| 291 |
TEL;WORK;MSG:+1-206-936-4544 |
| 292 |
TEL;WORK;FAX:+1-206-936-7329 |
| 293 |
EMAIL;INTERNET:[email protected] |
| 294 |
CALADRURI;PREF:mailto:[email protected] |
| 295 |
CALURI;PREF:http://cal.host1.com/user/cal.ics |
| 296 |
FBURL;PREF:http://cal.host1.com/user/fb.ifb |
| 297 |
CALURI:http://cal.company.com/projectA/pjtA.ics |
| 298 |
FBURL:http://cal.company.com/projectA/pjtAfb.ifb |
| 299 |
END:VCARD |
| 300 |
|
| 301 |
<span class="h4"><a class="selflink" id="section-2.3.1" href="#section-2.3.1">2.3.1</a> FBURL Property IANA Registration</span> |
| 302 |
|
| 303 |
To: [email protected] |
| 304 |
|
| 305 |
Subject: Registration of FBURL type for text/directory MIME type |
| 306 |
vCard profile. |
| 307 |
|
| 308 |
Type name: FBURL |
| 309 |
|
| 310 |
Type purpose: To specify the URI for a user's busy time in a vCard |
| 311 |
object. |
| 312 |
|
| 313 |
Type encoding: 8bit |
| 314 |
|
| 315 |
Type value: A single URI value. |
| 316 |
|
| 317 |
Type special notes: Where multiple FBURL properties are specified, |
| 318 |
the default FBURL property is indicated with the PREF parameter. The |
| 319 |
FTP or HTTP type of URI points to an iCalendar object associated with |
| 320 |
a snapshot of the last six weeks of the user's busy time data. If the |
| 321 |
iCalendar object is represented as a file or document, it's file type |
| 322 |
should be "ifb". |
| 323 |
|
| 324 |
Intended usage: Refer to <a href="#section-1.1">section 1.1</a>. |
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Small, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 335 |
|
| 336 |
|
| 337 |
Type examples: |
| 338 |
|
| 339 |
FBURL;PREF:http://www.host1.com/busy/janedoe |
| 340 |
FBURL:FTP://ftp.host.com/busy/project-a.ifb |
| 341 |
|
| 342 |
<span class="h4"><a class="selflink" id="section-2.3.2" href="#section-2.3.2">2.3.2</a> CALADRURI Property IANA Registration</span> |
| 343 |
|
| 344 |
To: [email protected] |
| 345 |
|
| 346 |
Subject: Registration of CALADRURI type for application/directory |
| 347 |
MIME type vCard profile. |
| 348 |
|
| 349 |
Type name: CALADRURI |
| 350 |
|
| 351 |
Type purpose: To specify the location to which an event request |
| 352 |
should be sent for the user. |
| 353 |
|
| 354 |
Type encoding: 8bit |
| 355 |
|
| 356 |
Type value: A single URI value. |
| 357 |
|
| 358 |
Type special notes: Where multiple CALADRURI properties are |
| 359 |
specified, the default CALADRURI property is indicated with the PREF |
| 360 |
parameter. |
| 361 |
|
| 362 |
Intended usage: Refer to <a href="#section-1.2">section 1.2</a>. |
| 363 |
|
| 364 |
Type examples: |
| 365 |
|
| 366 |
CALADRURI;PREF:mailto:[email protected] |
| 367 |
|
| 368 |
|
| 369 |
|
| 370 |
|
| 371 |
|
| 372 |
|
| 373 |
|
| 374 |
|
| 375 |
|
| 376 |
|
| 377 |
|
| 378 |
|
| 379 |
|
| 380 |
|
| 381 |
|
| 382 |
|
| 383 |
|
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Small, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 391 |
|
| 392 |
|
| 393 |
<span class="h4"><a class="selflink" id="section-2.3.3" href="#section-2.3.3">2.3.3</a> CAPURI Property IANA Registration</span> |
| 394 |
|
| 395 |
To: [email protected] |
| 396 |
|
| 397 |
Subject: Registration of CAPURI type for application/directory MIME |
| 398 |
type vCard profile. |
| 399 |
|
| 400 |
Type name: CAPURI |
| 401 |
|
| 402 |
Type purpose: To specify a protocol independent location from which a |
| 403 |
calendaring and scheduling client (i.e., CUA) can communicate with a |
| 404 |
user's entire calendar. |
| 405 |
|
| 406 |
Type encoding: 8bit |
| 407 |
|
| 408 |
Type value: A single URI value. |
| 409 |
|
| 410 |
Type special notes: Where multiple CAPURI properties are specified, |
| 411 |
the default CAPURI property is indicated with the PREF parameter. |
| 412 |
|
| 413 |
Intended usage: Refer to <a href="#section-1.3">section 1.3</a>. |
| 414 |
|
| 415 |
<span class="h4"><a class="selflink" id="section-2.3.4" href="#section-2.3.4">2.3.4</a> CALURI Property IANA Registration</span> |
| 416 |
|
| 417 |
To: [email protected] |
| 418 |
|
| 419 |
Subject: Registration of CALURI type for text/directory MIME type |
| 420 |
vCard profile. |
| 421 |
|
| 422 |
Type name: CALURI |
| 423 |
|
| 424 |
Type purpose: To specify the URI for a user's calendar in a vCard |
| 425 |
object. |
| 426 |
|
| 427 |
Type encoding: 8bit |
| 428 |
|
| 429 |
Type value type: A single URI value. |
| 430 |
|
| 431 |
Type special notes: Where multiple CALURI properties are specified, |
| 432 |
the default CALURI property is indicated with the PREF parameter. The |
| 433 |
property should contain a URI pointing to an iCalendar object |
| 434 |
associated with a snapshot of the user's calendar store. If the |
| 435 |
iCalendar object is represented as a file or document, it's file type |
| 436 |
should be "ics". |
| 437 |
|
| 438 |
Intended usage: Refer to <a href="#section-1.4">section 1.4</a>. |
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Small, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 447 |
|
| 448 |
|
| 449 |
Type examples: |
| 450 |
|
| 451 |
CALURI;PREF:http://cal.host1.com/calA |
| 452 |
CALURI:ftp://ftp.host1.com/calA.ics |
| 453 |
|
| 454 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Directory Lookup Using The LDAP v3 Protocol</span> |
| 455 |
|
| 456 |
Another way to obtain these URIs is to look them up in a directory |
| 457 |
using the LDAP protocol [<a href="#ref-1" title=""Lightweight Directory Access Protocol (v3)"">1</a>]. |
| 458 |
|
| 459 |
If a user's URIs can be found using directory lookup (i.e., searching |
| 460 |
for one of the LDAP schema extensions defined below), they should, in |
| 461 |
general, be considered "more up-to-date" than URIs in any vCards that |
| 462 |
are stored locally. |
| 463 |
|
| 464 |
<span class="h4"><a class="selflink" id="section-2.4.1" href="#section-2.4.1">2.4.1</a> LDAP Schema Extensions</span> |
| 465 |
|
| 466 |
In order to encode the calendaring URIs in the directory, the |
| 467 |
following are defined: |
| 468 |
|
| 469 |
- One object class: |
| 470 |
|
| 471 |
- calEntry |
| 472 |
|
| 473 |
- Eight attributes: |
| 474 |
|
| 475 |
- calCalURI |
| 476 |
|
| 477 |
- calFBURL |
| 478 |
|
| 479 |
- calCAPURI |
| 480 |
|
| 481 |
- calCalAdrURI |
| 482 |
|
| 483 |
- calOtherCalURIs |
| 484 |
|
| 485 |
- calOtherFBURLs |
| 486 |
|
| 487 |
- calOtherCAPURIs |
| 488 |
|
| 489 |
- calOtherCalAdrURIs |
| 490 |
|
| 491 |
The calCalURI contains the URI to a snapshot of the user's entire |
| 492 |
default calendar. The calFBURL contains the URI to the user's default |
| 493 |
busy time data. The calCAPURI represents contains a URI that can be |
| 494 |
used to communicate with the user's calendar. The calCalAdrURI |
| 495 |
contains a URI that points to the location to which event requests |
| 496 |
should be sent for that user. |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Small, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 503 |
|
| 504 |
|
| 505 |
The calOtherCalURIs is a multi-valued property containing URIs to |
| 506 |
snapshots of other calendars that the user may have. The |
| 507 |
calOtherFBURLs is a multi-valued property containing URIs to other |
| 508 |
free/busy data that the user may have. The calOtherCAPURIs attribute |
| 509 |
is a multi-valued property containing URIs to other calendars that |
| 510 |
the user may have. The calOtherCalAdrURIs attribute is a multi-valued |
| 511 |
property containing URIs to other locations that a user may want |
| 512 |
event requests sent to. |
| 513 |
|
| 514 |
There is no predetermined order to the values in either multi-valued |
| 515 |
property. |
| 516 |
|
| 517 |
<span class="h4"><a class="selflink" id="section-2.4.2" href="#section-2.4.2">2.4.2</a> Notation</span> |
| 518 |
|
| 519 |
The notation used in this memo is the same as that used in [<a href="#ref-2" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">2</a>]. |
| 520 |
|
| 521 |
<span class="h4"><a class="selflink" id="section-2.4.3" href="#section-2.4.3">2.4.3</a> Object Definitions</span> |
| 522 |
|
| 523 |
<span class="h5"><a class="selflink" id="section-2.4.3.1" href="#section-2.4.3.1">2.4.3.1</a> calEntry</span> |
| 524 |
|
| 525 |
The Calendar Entry is a class derived from "TOP" [<a href="#ref-2" title=""Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions"">2</a>], which contains |
| 526 |
the four calendaring attributes. |
| 527 |
|
| 528 |
(1.2.840.113556.1.5.87 |
| 529 |
NAME 'calEntry' |
| 530 |
TOP |
| 531 |
AUXILIARY |
| 532 |
MAY (calCalURI calFBURL calOtherCalURIs calOtherFBURLs calCAPURI |
| 533 |
calOtherCAPURLs) |
| 534 |
) |
| 535 |
|
| 536 |
<span class="h4"><a class="selflink" id="section-2.4.4" href="#section-2.4.4">2.4.4</a> Attribute Definitions</span> |
| 537 |
|
| 538 |
<span class="h5"><a class="selflink" id="section-2.4.4.1" href="#section-2.4.4.1">2.4.4.1</a> calCalURI</span> |
| 539 |
|
| 540 |
(1.2.840.113556.1.4.478 |
| 541 |
NAME 'calCalURI' |
| 542 |
EQUALITY caseIgnoreMatch |
| 543 |
SUBSTRING caseIgnoreMatch |
| 544 |
SYNTAX 'IA5String' |
| 545 |
USAGE userApplications |
| 546 |
) |
| 547 |
|
| 548 |
<span class="h5"><a class="selflink" id="section-2.4.4.2" href="#section-2.4.4.2">2.4.4.2</a> calFBURL</span> |
| 549 |
|
| 550 |
(1.2.840.113556.1.4.479 |
| 551 |
NAME 'calFBURL' |
| 552 |
EQUALITY caseIgnoreMatch |
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Small, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 559 |
|
| 560 |
|
| 561 |
SUBSTRING caseIgnoreMatch |
| 562 |
SYNTAX 'IA5String' |
| 563 |
USAGE userApplications |
| 564 |
) |
| 565 |
|
| 566 |
<span class="h5"><a class="selflink" id="section-2.4.4.3" href="#section-2.4.4.3">2.4.4.3</a> calCAPURI</span> |
| 567 |
|
| 568 |
(1.2.840.113556.1.4.480 |
| 569 |
NAME 'calCAPURI' |
| 570 |
EQUALITY caseIgnoreMatch |
| 571 |
SUBSTRING caseIgnoreMatch |
| 572 |
SYNTAX 'IA5String' |
| 573 |
USAGE userApplications |
| 574 |
) |
| 575 |
|
| 576 |
<span class="h5"><a class="selflink" id="section-2.4.4.4" href="#section-2.4.4.4">2.4.4.4</a> calCalAdrURI</span> |
| 577 |
|
| 578 |
(1.2.840.113556.1.4.481 |
| 579 |
NAME 'calCalAdrURI' |
| 580 |
EQUALITY caseIgnoreMatch |
| 581 |
SUBSTRING caseIgnoreMatch |
| 582 |
SYNTAX 'IA5String' |
| 583 |
USAGE userApplications |
| 584 |
) |
| 585 |
|
| 586 |
<span class="h5"><a class="selflink" id="section-2.4.4.5" href="#section-2.4.4.5">2.4.4.5</a> calOtherCalURIs</span> |
| 587 |
|
| 588 |
(1.2.840.113556.1.4.482 |
| 589 |
NAME 'calOtherCalURIs' |
| 590 |
EQUALITY caseIgnoreMatch |
| 591 |
SUBSTRING caseIgnoreMatch |
| 592 |
SYNTAX 'IA5String' |
| 593 |
MULTI-VALUE |
| 594 |
USAGE userApplications |
| 595 |
) |
| 596 |
|
| 597 |
<span class="h5"><a class="selflink" id="section-2.4.4.6" href="#section-2.4.4.6">2.4.4.6</a> calOtherFBURLs</span> |
| 598 |
|
| 599 |
(1.2.840.113556.1.4.483 |
| 600 |
NAME 'calOtherFBURLs' |
| 601 |
EQUALITY caseIgnoreMatch |
| 602 |
SUBSTRING caseIgnoreMatch |
| 603 |
SYNTAX 'IA5String' |
| 604 |
MULTI-VALUE |
| 605 |
USAGE userApplications |
| 606 |
) |
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Small, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h5"><a class="selflink" id="section-2.4.4.7" href="#section-2.4.4.7">2.4.4.7</a> calOtherCAPURIs</span> |
| 618 |
|
| 619 |
(1.2.840.113556.1.4.484 |
| 620 |
NAME 'calOtherCAPURIs' |
| 621 |
EQUALITY caseIgnoreMatch |
| 622 |
SUBSTRING caseIgnoreMatch |
| 623 |
SYNTAX 'IA5String' |
| 624 |
MULTI-VALUE |
| 625 |
USAGE userApplications |
| 626 |
) |
| 627 |
|
| 628 |
<span class="h5"><a class="selflink" id="section-2.4.4.8" href="#section-2.4.4.8">2.4.4.8</a> calOtherCalAdrURIs</span> |
| 629 |
|
| 630 |
(1.2.840.113556.1.4.485 |
| 631 |
NAME 'calOtherCalAdrURIs' |
| 632 |
EQUALITY caseIgnoreMatch |
| 633 |
SUBSTRING caseIgnoreMatch |
| 634 |
SYNTAX 'IA5String' |
| 635 |
MULTI-VALUE |
| 636 |
USAGE userApplications |
| 637 |
) |
| 638 |
|
| 639 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> IANA Considerations</span> |
| 640 |
|
| 641 |
This memo defines IANA registered extensions to the attributes |
| 642 |
defined by LDAP [<a href="#ref-1" title=""Lightweight Directory Access Protocol (v3)"">1</a>] and vCard [<a href="#ref-3" title=""vCard MIME Directory Profile"">3</a>]. |
| 643 |
|
| 644 |
IANA registration proposals for vCard are to be emailed to the |
| 645 |
registration agent for the "text/directory" MIME content-type, |
| 646 |
<MAILTO: [email protected]> using the format defined in |
| 647 |
[<a href="#ref-3" title=""vCard MIME Directory Profile"">3</a>]. |
| 648 |
|
| 649 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Security Considerations</span> |
| 650 |
|
| 651 |
Standard vCard and LDAP security rules and support apply for the |
| 652 |
extensions described in this document, and there are no special |
| 653 |
security issues for these extensions. |
| 654 |
|
| 655 |
Please note, though, that LDAP servers may permit anonymous clients |
| 656 |
to refresh entries which they did not create. Servers are also |
| 657 |
permitted to control a refresh access to an entry by requiring |
| 658 |
clients to bind before issuing a RefreshRequest. This will have |
| 659 |
implications on the server performance and scalability. |
| 660 |
|
| 661 |
Please also note, though, that vCard objects may have been created by |
| 662 |
an entity other than that represented by the vCard. Recipients should |
| 663 |
be certain of the source that generated the vCard. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Small, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 671 |
|
| 672 |
|
| 673 |
Also, care should be taken in making use of information obtained from |
| 674 |
directory servers that has been supplied by client, as it may now be |
| 675 |
out of date. In many networks, for example, IP addresses are |
| 676 |
automatically assigned when a host connects to the network, and may |
| 677 |
be reassigned if that host later disconnects. An IP address obtained |
| 678 |
from the directory may no longer be assigned to the host that placed |
| 679 |
the address in the directory. This issue is not specific to LDAP or |
| 680 |
dynamic directories. |
| 681 |
|
| 682 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> Acknowledgments</span> |
| 683 |
|
| 684 |
The authors wish to acknowledge the work of Alec Dun, who acted as an |
| 685 |
author for the early drafts of this memo. In addition, this document |
| 686 |
received input from the various participants in the IETF CALSCH |
| 687 |
Working Group discussions. |
| 688 |
|
| 689 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> Authors' Addresses</span> |
| 690 |
|
| 691 |
The following address information is provided in a vCard v3.0 [<a href="#ref-3" title=""vCard MIME Directory Profile"">3</a>], |
| 692 |
Electronic Business Card, format. |
| 693 |
|
| 694 |
BEGIN:VCARD |
| 695 |
VERSION:3.0 |
| 696 |
N:Small;Tony |
| 697 |
FN:Tony Small |
| 698 |
ORG:XpertSite.Com |
| 699 |
ADR;TYPE=WORK,POSTAL,PARCEL:;;4700 42nd Ave. SW, Suite 440; |
| 700 |
Seattle;WA;98116;USA |
| 701 |
TEL;TYPE=WORK,MSG:+1-206-937-9972 |
| 702 |
TEL;TYPE=WORK,FAX:+1-206-936-7329 |
| 703 |
EMAIL;TYPE=INTERNET:[email protected] |
| 704 |
CALADRURI:MAILTO:[email protected] |
| 705 |
END:VCARD |
| 706 |
|
| 707 |
BEGIN:VCARD |
| 708 |
VERSION:3.0 |
| 709 |
N:Hennessy;Denis |
| 710 |
FN:Denis Hennessy |
| 711 |
ORG:ISOCOR |
| 712 |
ADR;TYPE=WORK,POSTAL,PARCEL:;;42-47 Lower Mount St; |
| 713 |
Dublin 2;Ireland |
| 714 |
TEL;TYPE=WORK,MSG:+353-1-676-0366 |
| 715 |
TEL;TYPE=WORK,FAX:+353-1-676-0856 |
| 716 |
EMAIL;TYPE=INTERNET:[email protected] |
| 717 |
CALADRURI:MAILTO:[email protected] |
| 718 |
END:VCARD |
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Small, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 727 |
|
| 728 |
|
| 729 |
BEGIN:VCARD |
| 730 |
VERSION:3.0 |
| 731 |
N:Dawson;Frank |
| 732 |
FN:Frank Dawson |
| 733 |
ORG:Lotus Development Corporation |
| 734 |
ADR;TYPE=WORK,POSTAL,PARCEL:;;6544 Battleford Drive; |
| 735 |
Raleigh;NC;27613-3502;USA |
| 736 |
TEL;TYPE=WORK,PREF:+1-617-693-8728 |
| 737 |
TEL;TYPE=WORK,MSG:+1-919-676-9515 |
| 738 |
TEL;TYPE=FAX:+1-617-693-8728 |
| 739 |
EMAIL;TYPE=INTERNET,PREF:[email protected] |
| 740 |
EMAIL;TYPE=INTERNET:[email protected] |
| 741 |
CALADRURI;TYPE=PREF:MAILTO:[email protected] |
| 742 |
CALADRURI:MAILTO:[email protected] |
| 743 |
URL:http://home.earthlink.net/~fdawson |
| 744 |
END:VCARD |
| 745 |
|
| 746 |
This memo is a result of the work of the Internet Engineering Task |
| 747 |
Force Calendaring and scheduling Working Group. The chairman of that |
| 748 |
working group is: |
| 749 |
|
| 750 |
BEGIN:VCARD |
| 751 |
VERSION:3.0 |
| 752 |
N:Egen;Pat |
| 753 |
FN:Pat Egen |
| 754 |
ORG:Engan Consulting |
| 755 |
ADR;TYPE=WORK:;;803 Creek Overlook;Chattanooga;TN;37415;USA |
| 756 |
TEL;TYPE=WORK,VOICE:423.875.2652 |
| 757 |
TEL;TYPE=WORK,FAX:423.875.2017 |
| 758 |
EMAIL:[email protected] |
| 759 |
URL:http://www.egenconsulting.com |
| 760 |
CALADRURI:MAILTO:[email protected] |
| 761 |
END:VCARD |
| 762 |
|
| 763 |
|
| 764 |
|
| 765 |
|
| 766 |
|
| 767 |
|
| 768 |
|
| 769 |
|
| 770 |
|
| 771 |
|
| 772 |
|
| 773 |
|
| 774 |
|
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Small, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 783 |
|
| 784 |
|
| 785 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> Bibliography</span> |
| 786 |
|
| 787 |
[<a id="ref-1">1</a>] Wahl, M., Howes, T. and S. Kille, "Lightweight Directory Access |
| 788 |
Protocol (v3)", <a href="./rfc2251">RFC 2251</a>, December 1997. |
| 789 |
|
| 790 |
[<a id="ref-2">2</a>] Wahl, M., Coulbeck, A., Howes, T. and S. Kille, "Lightweight |
| 791 |
Directory Access Protocol (v3): Attribute Syntax Definitions", |
| 792 |
<a href="./rfc2252">RFC 2252</a>, December 1997. |
| 793 |
|
| 794 |
[<a id="ref-3">3</a>] Dawson, F. and T. Howes, "vCard MIME Directory Profile", <a href="./rfc2426">RFC</a> |
| 795 |
<a href="./rfc2426">2426</a>, September 1998. |
| 796 |
|
| 797 |
[<a id="ref-4">4</a>] Dawson, F. and D. Stenerson, "Internet Calendaring and Scheduling |
| 798 |
Core Object Specification (iCalendar)", <a href="./rfc2445">RFC 2445</a>, November 1997. |
| 799 |
|
| 800 |
[<a id="ref-5">5</a>] Dawson, F. and S. Mansour, "iCalendar Message-Based |
| 801 |
Interopability Protocal (iMIP)", <a href="./rfc2447">RFC 2447</a>, November 1997. |
| 802 |
|
| 803 |
|
| 804 |
|
| 805 |
|
| 806 |
|
| 807 |
|
| 808 |
|
| 809 |
|
| 810 |
|
| 811 |
|
| 812 |
|
| 813 |
|
| 814 |
|
| 815 |
|
| 816 |
|
| 817 |
|
| 818 |
|
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Small, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc2739">RFC 2739</a> Locating a Calendar User January 2000</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Full Copyright Statement</span> |
| 842 |
|
| 843 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 844 |
|
| 845 |
This document and translations of it may be copied and furnished to |
| 846 |
others, and derivative works that comment on or otherwise explain it |
| 847 |
or assist in its implementation may be prepared, copied, published |
| 848 |
and distributed, in whole or in part, without restriction of any |
| 849 |
kind, provided that the above copyright notice and this paragraph are |
| 850 |
included on all such copies and derivative works. However, this |
| 851 |
document itself may not be modified in any way, such as by removing |
| 852 |
the copyright notice or references to the Internet Society or other |
| 853 |
Internet organizations, except as needed for the purpose of |
| 854 |
developing Internet standards in which case the procedures for |
| 855 |
copyrights defined in the Internet Standards process must be |
| 856 |
followed, or as required to translate it into languages other than |
| 857 |
English. |
| 858 |
|
| 859 |
The limited permissions granted above are perpetual and will not be |
| 860 |
revoked by the Internet Society or its successors or assigns. |
| 861 |
|
| 862 |
This document and the information contained herein is provided on an |
| 863 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 864 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 865 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 866 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 867 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 868 |
|
| 869 |
Acknowledgement |
| 870 |
|
| 871 |
Funding for the RFC Editor function is currently provided by the |
| 872 |
Internet Society. |
| 873 |
|
| 874 |
|
| 875 |
|
| 876 |
|
| 877 |
|
| 878 |
|
| 879 |
|
| 880 |
|
| 881 |
|
| 882 |
|
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
Small, et al. Standards Track [Page 16] |
| 893 |
</pre> |