draft-ietf-calsch-locating-00.txt   draft-ietf-calsch-locating-01.txt 
Network Working Group Tony Small, Microsoft Corporation
Network Working Group Tony Small, Microsoft Corporation
INTERNET-DRAFT Denis Hennessy, ISOCOR INTERNET-DRAFT Denis Hennessy, ISOCOR
Calendaring and Scheduling Working Group Calendaring and Scheduling Working Group Frank Dawson, Lotus
Frank Dawson, Lotus Expires six months from September 22, 1998
Expires six months from June 11, 1998
Calendar attributes for vCard and LDAP Calendar attributes for vCard and LDAP
draft-ietf-calsch-locating-00.txt draft-ietf-calsch-locating-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months.
and may be updated, replaced, or obsoleted by other documents at any Internet-Drafts may be updated, replaced, or made obsolete by other
time. It is inappropriate to use Internet-Drafts as reference material documents at any time. It is not appropriate to use Internet-Drafts as
or to cite them other than as "work in progress." reference material or to cite them other than as a "working draft" or
"work in progress".
To view the entire list of current Internet-Drafts, please check To learn the current status of any Internet-Draft, please check the 1id-
the "1id-abstracts.txt" listing contained in the Internet-Drafts abstracts.txt listing contained in the Internet-Drafts Shadow
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
(Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
(US West Coast). Distribution of this document is unlimited.
Copyright (C) The Internet Society 1998. All Rights Reserved.
Abstract Abstract
When scheduling a calendar entity, such as an event, it is a When scheduling a calendar entity, such as an event, it is a
prerequisite that an organizer has the calendar address of each prerequisite that an organizer has the calendar address of each attendee
attendee that will be invited to the event. Additionally, access to an that will be invited to the event. Additionally, access to an attendee's
attendee's current "busy time" provides an a priori indication of current "busy time" provides an a priori indication of whether the
whether the attendee will be free to participate in the event. attendee will be free to participate in the event.
In order to meet these challenges, a calendar user agent (CUA) needs a In order to meet these challenges, a calendar user agent (CUA) needs a
mechanism to locate (URI) individual user's calendar and free/busy mechanism to locate (URI) individual user's calendar and free/busy time.
time.
This draft defines three mechanisms for obtaining a URI to a user's This draft defines three mechanisms for obtaining a URI to a user's
calendar and free/busy time. These include: calendar and free/busy time. These include:
- Manual transfer of the information; - Manual transfer of the information;
Small, Hennessy, Dawson -- Page 1 -- Expires March 1999
- Personal data exchange using the vCard format; and - Personal data exchange using the vCard format; and
- Directory lookup using the LDAP protocol. - Directory lookup using the LDAP protocol.
1. URIs Small, Hennessy, Dawson -- Page 2 -- Expires March 1999
This draft defines four classes of URIs. URIs are more useful if it is Table of Contents
1. CALENDARING AND SCHEDULING URIS.....................................4
1.1 FREE/BUSY URI (FBURL) ............................................4
1.2 CALENDAR ADDRESS URI (CALADRURI) .................................5
1.3 CALENDAR ACCESS URI (CAPURI) .....................................5
1.4 CALENDAR URI (CALURI) ............................................5
1.5 DEFAULT URIS .....................................................6
2. DISTRIBUTION........................................................6
2.1 MANUAL TRANSFER ..................................................6
2.2 PERSONAL DATA EXCHANGE USING A VCARD .............................6
2.3 VCARD SCHEMA EXTENSIONS ..........................................7
2.3.1 FBURL Property IANA Registration ..............................7
2.3.2 CALADRURI Property IANA Registration ..........................8
2.3.3 CAPURI Property IANA Registration .............................9
2.3.4 CALURI Property IANA Registration .............................9
2.4 DIRECTORY LOOKUP USING THE LDAP V3 PROTOCOL .....................10
2.4.1 LDAP Schema Extensions .......................................10
2.4.2 Notation .....................................................11
2.4.3 Object Definitions ...........................................11
2.4.3.1 calEntry .................................................11
2.4.4 Attribute Definitions ........................................11
2.4.4.1 calCalURI ................................................11
2.4.4.2 calFBURL .................................................12
2.4.4.3 calCAPURI ................................................12
2.4.4.4 calCalAdrURI .............................................12
2.4.4.5 calOtherCalURIs ..........................................12
2.4.4.6 calOtherFBURLs ...........................................13
2.4.4.7 calOtherCAPURIs ..........................................13
2.4.4.8 calOtherCalAdrURIs .......................................13
3. AUTHORS'S ADDRESSES................................................13
4. BIBLIOGRAPHY.......................................................15
5. FULL COPYRIGHT STATEMENTS..........................................15
Small, Hennessy, Dawson -- Page 3 -- Expires March 1999
1. Calendaring and Scheduling URIs
This draft defines four classes of URIs. URIs are more useful if it is
understood what the URIs point to. Here is a brief description: understood what the URIs point to. Here is a brief description:
1.1. Free/Busy URI (FBURL) 1.1 Free/Busy URI (FBURL)
The free/busy URI is defined to be a transport independent location 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 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 present time, this URI only points to busy time data. Future revisions
of this specification may provide for the extended capability of of this specification may provide for the extended capability of
publishing free time data. publishing free time data.
If a calendaring and scheduling client (i.e., CUA) were to retrieve If a calendaring and scheduling client (i.e., CUA) were to retrieve data
data from this location using FTP or HTTP, it would get back an from this location using FTP or HTTP, it would get back an iCalendar
iCalendar object [10] containing one or more "VFREEBUSY" calendar object [4] containing one or more "VFREEBUSY" calendar components. If a
components. If a MIME transport is being used, the response will be MIME transport is being used, the response will be contained within a
contained within a "text/calendar" MIME body part as specified in the "text/calendar" MIME body part as specified in the iCalendar
iCalendar specification [10]. For example: specification [4]. For example:
BEGIN:VCALENDAR BEGIN:VCALENDAR
VERSION:2.0 VERSION:2.0
PRODID:-//hacksw/handcal//NONSGML v1.0//EN PRODID:-//hacksw/handcal//NONSGML v1.0//EN
METHOD:PUBLISH METHOD:PUBLISH
BEGIN:VFREEBUSY BEGIN:VFREEBUSY
ATTENDEE:MAILTO:jane_doe@host1.com ATTENDEE:MAILTO:jane_doe@host1.com
DTSTART:19971013T050000Z DTSTART:19971013T050000Z
DTEND:19971124T050000Z DTEND:19971124T050000Z
DTSTAMP:19970901T083000Z DTSTAMP:19970901T083000Z
FREEBUSY:19971015T133000Z/19971015T180000Z FREEBUSY:19971015T133000Z/19971015T180000Z
FREEBUSY:19971015T190000Z/19971015T220000Z FREEBUSY:19971015T190000Z/19971015T220000Z
FBURL:http://www.host.com/calendar/busy/jdoe.ifb FBURL:http://www.host.com/calendar/busy/jdoe.ifb
END:VFREEBUSY END:VFREEBUSY
END:VCALENDAR END:VCALENDAR
The amount of busy time data pointed to by the FBURL will generally be The amount of busy time data pointed to by the FBURL will generally be
pre-determined; for example one month of free/busy inforation. As a pre-determined; for example one month of free/busy inforation. As a
guideline, it is recommended that the previous six weeks of busy time guideline, it is recommended that the previous six weeks of busy time
data be published at the location associated with the FBURL. If this data be published at the location associated with the FBURL. If this URI
URI points to a file resource, it is recommended that the file points to a file resource, it is recommended that the file extension be
extension be "ifb" to distinguish it from an arbitrary iCalendar "ifb" to distinguish it from an arbitrary iCalendar object (e.g., with
object. the "ics" file extension).
Small, Hennessy, Dawson -- Page 4 -- Expires March 1999
1.2 Calendar Address URI (CALADRURI) 1.2 Calendar Address URI (CALADRURI)
The calendar address URI is defined to be a transport independent The calendar address URI is defined to be a transport independent
communication end-point for a user. The organizer's calendaring and communication end-point for a user. The organizer's calendaring and
scheduling client (ie. CUA) would use this URI to determine where to scheduling client (ie. CUA) would use this URI to determine where to
send an event request when organizing a meeting with a particular send an event request when organizing a meeting with a particular
attendee. attendee.
If the user prefers to receive event requests via iMIP, then the user If the user prefers to receive event requests via iMIP, then the user
would provide a "mailto" URI containing the user's e-mail address. [13] would provide a "mailto" URI containing the user's e-mail address. [5]
For example: For example:
"mailto:user@host1.com" "mailto:user@host1.com"
The URI for an iRIP user is yet to be defined, but that is another The URI for an iRIP user is yet to be defined, but that is another
possible URI value in this property. [14] possible URI value in this property. [6]
1.3. Calendar Access URI (CAPURI) 1.3 Calendar Access URI (CAPURI)
The Calendar Access URI is defined to be a protocol independent The Calendar Access URI is defined to be a protocol independent location
location from which a calendaring and scheduling client (i.e., CUA) can from which a calendaring and scheduling client (i.e., CUA) can
communicate with a user's entire calendar. communicate with a user's entire calendar.
The semantics for using this URI as an access protocol locator are yet 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 to be defined by the IETF CALSCH Working Group. This will be addressed
in the "Calendar Access Protocol" specification. in the "Calendar Access Protocol" specification.
1.4 Calendar URI (CALURI) 1.4 Calendar URI (CALURI)
The Calendar URI is defined to be a protocol independent location from The Calendar URI is defined to be a protocol independent location from
which a calendaring and scheduling client (ie. CUA) can retrieve an which a calendaring and scheduling client (ie. CUA) can retrieve an
entire copy of a user's calendar. Retrieving data from this URI entire copy of a user's calendar. Retrieving data from this URI obtains
obtains a published "snapshot" of the user's calendar. a published "snapshot" of the user's calendar.
HTTP URI -- If the URI is an HTTP URI, then the content returned with a 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 GET should be a "text/calendar" MIME body part containing one or more
iCalendar object. iCalendar object.
FTP URI -- If the URI is an FTP URI, then the resource pointed to FTP URI -- If the URI is an FTP URI, then the resource pointed to should
should be a file with an "ics" file extension containing one or more be a file with an "ics" file extension containing one or more iCalendar
iCalendar objects. objects.
1.5. Default URIs Small, Hennessy, Dawson -- Page 5 -- Expires March 1999
1.5 Default URIs
There are many cases where a user may have more than one calendar. In 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 these cases, a user may have multiple URIs, each URI pointing to a
calendar or free/busy data. calendar or free/busy data.
To make the case of multiple calendars simpler for clients, the concept To make the case of multiple calendars simpler for clients, the concept
of the "default" calendar is introduced. A "default" calendar is one of the "default" calendar is introduced. A "default" calendar is one
that the user has designated as the calendar that other users should 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 look at when accessing the user's calendar, or retrieving the user's
free/busy time. free/busy time.
The default calendar may, in fact, include rolled-up information from The default calendar may, in fact, include rolled-up information from
all the user's other calendars. The other calendars may only exist for all the user's other calendars. The other calendars may only exist for
organizational purposes. organizational purposes.
2. Distribution 2. Distribution
These four URIs provide valuable pointers to calendaring and scheduling These four URIs provide valuable pointers to calendaring and scheduling
data that other users need in order to know when to schedule meetings, data that other users need in order to know when to schedule meetings,
etc. There are several possibilities on how users can communicate etc. There are several possibilities on how users can communicate these
these URIs to other users. The following section outlines how these URIs to other users. The following section outlines how these URIs can
URIs can be distributed to other users. be distributed to other users.
2.1. Manual Transfer 2.1 Manual Transfer
The simplest way to obtain these URIs is for a user to communicate the 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 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. message, or by printing these URIs on a paper business card.
When using this mechanism, the user obtains these URIs using an out-of- When using this mechanism, the user obtains these URIs using an out-of-
band mechanism and then enters these URIs into their calendaring band mechanism and then enters these URIs into their calendaring
software manually. software manually.
2.2. Personal Data Exchange Using A vCard 2.2 Personal Data Exchange Using a vCard
A more sophisticated way to obtain these URIs is for users to publish A more sophisticated way to obtain these URIs is for users to publish
vCards containing these URIs. The vCard object can be transferred vCards containing these URIs. The vCard object can be transferred
between one another. Since many e-mail clients allow a user to between one another. Since many e-mail clients allow a user to
automatically include a vCard with every message that the user sends, automatically include a vCard with every message that the user sends,
this provides a simple, transparent way for a user to distribute their this provides a simple, transparent way for a user to distribute their
calendaring and scheduling URIs. calendaring and scheduling URIs.
On the receiving end, an e-mail client that provides an integrated On the receiving end, an e-mail client that provides an integrated vCard
vCard database can provide a way to lookup calendaring URIs for users database can provide a way to lookup calendaring URIs for users whose
whose vCards are stored locally. vCards are stored locally.
2.2.1. vCard Schema Extensions Small, Hennessy, Dawson -- Page 6 -- Expires March 1999
Since the vCard [8] specification doesn't specify how to encode 2.3 vCard Schema Extensions
calendaring URIs in a vCard, this section is provided as an extension
to vCard which specifies how to encode calendaring URIs within a 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.
Inside a vCard object, four new properties are defined: "CALURI", Inside a vCard object, four new properties are defined: "CALURI",
_CAPURI_, _CALADRURI_, and "FBURL", as defined above. "CAPURI", "CALADRURI", and "FBURL", as defined above.
Any vCard can have one or more of these properties, each representing a Any vCard can have one or more of these properties, each representing a
calendar or free/busy time that is associated with the user. calendar or free/busy time that is associated with the user.
One of these properties can be designated as the "default" by adding One of these properties can be designated as the "default" by adding the
the "PREF" parameter. "PREF" parameter.
Here is a simple example of a vCard containing a "FBURL" and a Here is a simple example of a vCard containing a "FBURL" and a "CALURI".
"CALURI".
BEGIN:VCARD BEGIN:VCARD
VERSION:3.0 VERSION:3.0
FN:Alec Dun
N:Dun;Alec N:Dun;Alec
FN:Alec Dun
ORG:Microsoft Corporation ORG:Microsoft Corporation
ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way; ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way;
Redmond;WA;98052-6399;USA Redmond;WA;98052-6399;USA
TEL;WORK;MSG:+1-206-936-4544 TEL;WORK;MSG:+1-206-936-4544
TEL;WORK;FAX:+1-206-936-7329 TEL;WORK;FAX:+1-206-936-7329
EMAIL;INTERNET:user@host1.com EMAIL;INTERNET:user@host1.com
CALADRURI;PREF:mailto:user@host1.com CALADRURI;PREF:mailto:user@host1.com
CALURI;PREF:http://cal.host1.com/user/cal.ics CALURI;PREF:http://cal.host1.com/user/cal.ics
FBURL;PREF:http://cal.host1.com/user/fb.ifb FBURL;PREF:http://cal.host1.com/user/fb.ifb
CALURI:http://cal.company.com/projectA/pjtA.ics CALURI:http://cal.company.com/projectA/pjtA.ics
FBURL:http://cal.company.com/projectA/pjtAfb.ifb FBURL:http://cal.company.com/projectA/pjtAfb.ifb
END:VCARD END:VCARD
2.2.1.1 FBURL Property IANA Registration 2.3.1 FBURL Property IANA Registration
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of FBURL type for text/directory MIME type
vCard profile. Subject: Registration of FBURL type for text/directory MIME type vCard
profile.
Type name: FBURL Type name: FBURL
Type purpose: To specify the URI for a user's busy time in a vCard Type purpose: To specify the URI for a user's busy time in a vCard
object. object.
Small, Hennessy, Dawson -- Page 7 -- Expires March 1999
Type encoding: 8bit Type encoding: 8bit
Type value: A single URI value. Type value: A single URI value.
Type special notes: Where multiple FBURL properties are specified,
the default FBURL property is indicated with the PREF Type special notes: Where multiple FBURL properties are specified, the
parameter. The FTP or HTTP type of URI points to an iCalendar default FBURL property is indicated with the PREF parameter. The FTP or
object associated with a snapshot of the last six weeks of the HTTP type of URI points to an iCalendar object associated with a
user's busy time data. If the iCalendar object is represented snapshot of the last six weeks of the user's busy time data. If the
as a file or document, it's file type should be "ifb". iCalendar object is represented as a file or document, it's file type
should be "ifb".
Intended usage: Refer to section 1.1. Intended usage: Refer to section 1.1.
Type examples: Type examples:
FBURL;PREF:http://www.host1.com/busy/janedoe FBURL;PREF:http://www.host1.com/busy/janedoe
FBURL:FTP://ftp.host.com/busy/project-a.ifb FBURL:FTP://ftp.host.com/busy/project-a.ifb
2.2.1.2 CALADRURI Property IANA Registration 2.3.2 CALADRURI Property IANA Registration
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of CALADRURI type for application/directory
MIME type vCard profile. Subject: Registration of CALADRURI type for application/directory MIME
type vCard profile.
Type name: CALADRURI Type name: CALADRURI
Type purpose: To specify the location to which an event request
should be sent for the user. Type purpose: To specify the location to which an event request should
be sent for the user.
Type encoding: 8bit Type encoding: 8bit
Type value: A single URI value. Type value: A single URI value.
Type special notes: Where multiple CALADRURI properties are
specified, the default CALADRURI property is indicated with the Type special notes: Where multiple CALADRURI properties are specified,
PREF parameter. the default CALADRURI property is indicated with the PREF parameter.
Intended usage: Refer to section 1.2. Intended usage: Refer to section 1.2.
Type examples: Type examples:
CALADRURI;PREF:mailto:janedoe@host.com CALADRURI;PREF:mailto:janedoe@host.com
2.2.1.3 CAPURI Property IANA Registration Small, Hennessy, Dawson -- Page 8 -- Expires March 1999
2.3.3 CAPURI Property IANA Registration
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of CAPURI type for application/directory MIME
type vCard profile. Subject: Registration of CAPURI type for application/directory MIME type
vCard profile.
Type name: CAPURI Type name: CAPURI
Type purpose: To specify a protocol independent location from which
a calendaring and scheduling client (i.e., CUA) can communicate Type purpose: To specify a protocol independent location from which a
with a user's entire calendar. calendaring and scheduling client (i.e., CUA) can communicate with a
user's entire calendar.
Type encoding: 8bit Type encoding: 8bit
Type value: A single URI value. Type value: A single URI value.
Type special notes: Where multiple CAPURI properties are specified,
the default CAPURI property is indicated with the PREF Type special notes: Where multiple CAPURI properties are specified, the
parameter. default CAPURI property is indicated with the PREF parameter.
Intended usage: Refer to section 1.3. Intended usage: Refer to section 1.3.
2.2.1.4 CALURI Property IANA Registration 2.3.4 CALURI Property IANA Registration
To: ietf-mime-directory@imc.org To: ietf-mime-directory@imc.org
Subject: Registration of CALURI type for text/directory MIME type
vCard profile. Subject: Registration of CALURI type for text/directory MIME type vCard
profile.
Type name: CALURI Type name: CALURI
Type purpose: To specify the URI for a user's calendar in a vCard Type purpose: To specify the URI for a user's calendar in a vCard
object. object.
Type encoding: 8bit Type encoding: 8bit
Type valuetype: A single URI value. Type valuetype: A single URI value.
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".
Intended usage: Refer to section 1.4.
Type examples: Type special notes: Where multiple CALURI properties are specified, the
CALURI;PREF:http://cal.host1.com/calA default CALURI property is indicated with the PREF parameter. The
CALURI:ftp://ftp.host1.com/calA.ics 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".
2.3. Directory Lookup Using The LDAP v3 Protocol Intended usage: Refer to section 1.4.
Another way to obtain these URIs is to look them up in a directory Small, Hennessy, Dawson -- Page 9 -- Expires March 1999
using the LDAP protocol.
If an organizer knows an attendee's e-mail address, then using DNS, Type examples:
the attendee's directory server can be found. The mechanism for this
is described in detail in [7]. From the directory server, the client
can look up the URLs for a user's calendar. Here's a summary of how it
works. For more detail, please see the draft [7].
The client first parses the domain name out from the rfc822 mailbox CALURI;PREF:http://cal.host1.com/calA
name. For the fictitious mailbox "janedoe@host1.com", the domain name CALURI:ftp://ftp.host1.com/calA.ics
would be "host1.com".
Given the domain name, the client prepends "ldap.tcp" to the domain 2.4 Directory Lookup Using The LDAP v3 Protocol
name and formulating a host. Next the client retrieves the queries the
DNS server for the SRV record for "ldap.tcp.host1.com". The mechanism
for adding "ldap.tcp" onto the original domain name is described in
detail in [5]. The DNS server returns the IP address for the
associated server for 'ldap.tcp.host1.com'.
Once the IP address for the LDAP server has been obtained, the client Another way to obtain these URIs is to look them up in a directory using
constructs a DN from which to search using the DNS name. In this case, the LDAP protocol [1].
it would be "DC=host1,DC=COM". The mechanism to construct the DN is
described in detail in [6]. With the IP address and the DN, the client
issues a search request to the server where the attribute named "mail"
[4] "equalityMatch"es the user's email address. From the first
matching entry, client obtains the calendaring and scheduling URLs.
If a user's URIs can be found using directory lookup, they should, in 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 general, be considered "more up-to-date" than URIs in any vCards that
are stored locally. are stored locally.
2.3.1. LDAP Schema Extensions 2.4.1 LDAP Schema Extensions
In order to encode the calendaring URIs in the directory, the following In order to encode the calendaring URIs in the directory, the following
are defined: are defined:
one object class: - One object class:
@ calEntry - calEntry
and eight attributes: - Eight attributes:
@ calCalURI - calCalURI
@ calFBURL
@ calCAPURI - calFBURL
@ calCalAdrURI
@ calOtherCalURIs - calCAPURI
@ calOtherFBURLs
@ calOtherCAPURIs - calCalAdrURI
@ calOtherCalAdrURIs
- calOtherCalURIs
- calOtherFBURLs
- calOtherCAPURIs
- calOtherCalAdrURIs
The calCalURI contains the URI to a snapshot of the user's entire 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 default calendar. The calFBURL contains the URI to the user's default
busy time data. The calCAPURI represents contains a URI that can be busy time data. The calCAPURI represents contains a URI that can be used
used to communicate with the user's calendar. The calCalAdrURI
contains a URI that points to the location to which event requests Small, Hennessy, Dawson -- Page 10 -- Expires March 1999
should be sent for that user.
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.
The calOtherCalURIs is a multi-valued property containing URIs to The calOtherCalURIs is a multi-valued property containing URIs to
snapshots of other calendars that the user may have. The snapshots of other calendars that the user may have. The calOtherFBURLs
calOtherFBURLs is a multi-valued property containing URIs to other is a multi-valued property containing URIs to other free/busy data that
free/busy data that the user may have. The calOtherCAPURIs attribute the user may have. The calOtherCAPURIs attribute is a multi-valued
is a multi-valued property containing URIs to other calendars that the property containing URIs to other calendars that the user may have. The
user may have. The calOtherCalAdrURIs attribute is a multi-valued calOtherCalAdrURIs attribute is a multi-valued property containing URIs
property containing URIs to other locations that a user may want event to other locations that a user may want event requests sent to.
requests sent to.
There is no predetermined order to the values in either multi-valued There is no predetermined order to the values in either multi-valued
property. property.
2.3.2. Notation 2.4.2 Notation
The notation used in this document is the same as that used in [2]. The notation used in this document is the same as that used in [2].
2.3.3. Object Definitions 2.4.3 Object Definitions
2.3.3.1. calEntry 2.4.3.1 calEntry
The Calendar Entry is a class derived from _TOP_ [2], which contains The Calendar Entry is a class derived from "TOP" [2], which contains the
the four calendaring attributes. four calendaring attributes.
( 1.2.840.113556.1.5.87 ( 1.2.840.113556.1.5.87
NAME 'calEntry' NAME 'calEntry'
TOP TOP
AUXILIARY AUXILIARY
MAY (calCalURI calFBURL calOtherCalURIs calOtherFBURLs MAY (calCalURI calFBURL calOtherCalURIs calOtherFBURLs calCAPURI
calCAPURI calOtherCAPURLs) calOtherCAPURLs)
) )
2.3.4. Attribute Definitions 2.4.4 Attribute Definitions
2.3.4.1. calCalURI 2.4.4.1 calCalURI
( 1.2.840.113556.1.4.478 ( 1.2.840.113556.1.4.478
NAME 'calCalURI' NAME 'calCalURI'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
USAGE userApplications USAGE userApplications
Small, Hennessy, Dawson -- Page 11 -- Expires March 1999
) )
2.3.4.2. calFBURL 2.4.4.2 calFBURL
( 1.2.840.113556.1.4.479 ( 1.2.840.113556.1.4.479
NAME 'calFBURL' NAME 'calFBURL'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
USAGE userApplications USAGE userApplications
) )
2.3.4.3. calCAPURI 2.4.4.3 calCAPURI
( 1.2.840.113556.1.4.480 ( 1.2.840.113556.1.4.480
NAME 'calCAPURI' NAME 'calCAPURI'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
USAGE userApplications USAGE userApplications
) )
2.3.4.4. calCalAdrURI 2.4.4.4 calCalAdrURI
( 1.2.840.113556.1.4.481 ( 1.2.840.113556.1.4.481
NAME 'calCalAdrURI' NAME 'calCalAdrURI'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
USAGE userApplications USAGE userApplications
) )
2.3.4.5. calOtherCalURIs 2.4.4.5 calOtherCalURIs
( 1.2.840.113556.1.4.482 ( 1.2.840.113556.1.4.482
NAME 'calOtherCalURIs' NAME 'calOtherCalURIs'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
MULTI-VALUE MULTI-VALUE
USAGE userApplications USAGE userApplications
) )
2.3.4.6. calOtherFBURLs Small, Hennessy, Dawson -- Page 12 -- Expires March 1999
2.4.4.6 calOtherFBURLs
( 1.2.840.113556.1.4.483 ( 1.2.840.113556.1.4.483
NAME 'calOtherFBURLs' NAME 'calOtherFBURLs'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
MULTI-VALUE MULTI-VALUE
USAGE userApplications USAGE userApplications
) )
2.3.4.7. calOtherCAPURIs 2.4.4.7 calOtherCAPURIs
( 1.2.840.113556.1.4.484 ( 1.2.840.113556.1.4.484
NAME 'calOtherCAPURIs' NAME 'calOtherCAPURIs'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
MULTI-VALUE MULTI-VALUE
USAGE userApplications USAGE userApplications
) )
2.3.4.8. calOtherCalAdrURIs 2.4.4.8 calOtherCalAdrURIs
( 1.2.840.113556.1.4.485 ( 1.2.840.113556.1.4.485
NAME 'calOtherCalAdrURIs' NAME 'calOtherCalAdrURIs'
EQUALITY caseIgnoreMatch EQUALITY caseIgnoreMatch
SUBSTRING caseIgnoreMatch SUBSTRING caseIgnoreMatch
SYNTAX 'Directory String' SYNTAX 'IA5String'
MULTI-VALUE MULTI-VALUE
USAGE userApplications USAGE userApplications
) )
Authors' Addresses 3. Authors's Addresses
The following address information is provided in a vCard v3.0 [3],
Electronic Business Card, format.
BEGIN:VCARD BEGIN:VCARD
VERSION:2.1 VERSION:3.0
N:Small;Tony N:Small;Tony
FN:Tony Small FN:Tony Small
Small, Hennessy, Dawson -- Page 13 -- Expires March 1999
ORG:Microsoft Corporation ORG:Microsoft Corporation
ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way; ADR;WORK;POSTAL;PARCEL:;;One Microsoft Way;
Redmond;WA;98052-6399;USA Redmond;WA;98052-6399;USA
TEL;WORK;MSG:+1-425-703-2190 TEL;WORK;MSG:+1-425-703-2190
TEL;WORK;FAX:+1-206-936-7329 TEL;WORK;FAX:+1-206-936-7329
EMAIL;INTERNET:tonysm@Microsoft.com EMAIL;INTERNET:tonysm@Microsoft.com
CALADRURI:MAIL-TO:tonysm@Microsoft.com CALADRURI:MAILTO:tonysm@Microsoft.com
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:2.1 VERSION:3.0
N:Hennessy;Denis N:Hennessy;Denis
FN:Denis Hennessy FN:Denis Hennessy
ORG:ISOCOR ORG:ISOCOR
ADR;WORK;POSTAL;PARCEL:;;42-47 Lower Mount St; ADR;WORK;POSTAL;PARCEL:;;42-47 Lower Mount St;
Dublin 2;Ireland Dublin 2;Ireland
TEL;WORK;MSG:+353-1-676-0366 TEL;WORK;MSG:+353-1-676-0366
TEL;WORK;FAX:+353-1-676-0856 TEL;WORK;FAX:+353-1-676-0856
EMAIL;INTERNET:denis.hennessy@isocor.com EMAIL;INTERNET:denis.hennessy@isocor.com
CALADRURI:MAIL-TO:denis.hennessy@isocor.com CALADRURI:MAILTO:denis.hennessy@isocor.com
END:VCARD END:VCARD
BEGIN:VCARD BEGIN:VCARD
VERSION:2.1 VERSION:3.0
N:Dawson;Frank N:Dawson;Frank
FN:Frank Dawson FN:Frank Dawson
ORG:Lotus Development Corporation ORG:Lotus Development Corporation
ADR;WORK;POSTAL;PARCEL:;;6544 Battleford Drive; ADR;WORK;POSTAL;PARCEL:;;6544 Battleford Drive;
Raleigh;NC;27613-3502;USA Raleigh;NC;27613-3502;USA
TEL;WORK;PREF:+1-617-693-8728
TEL;WORK;MSG:+1-919-676-9515 TEL;WORK;MSG:+1-919-676-9515
TEL;WORK;FAX:+1-919-676-9564
EMAIL;INTERNET;PREF:Frank_Dawson@Lotus.com EMAIL;INTERNET;PREF:Frank_Dawson@Lotus.com
EMAIL;INTERNET:fdawson@earthlink.net EMAIL;INTERNET:fdawson@earthlink.net
CALADRURI;PREF:MAIL-TO:Frank_Dawson@Lotus.com CALADRURI;PREF:MAILTO:Frank_Dawson@Lotus.com
CALADRURI:MAIL-TO:fdawson@earthlink.net CALADRURI:MAILTO:fdawson@earthlink.net
URI:http://home.earthlink.net/~fdawson URI:http://home.earthlink.net/~fdawson
END:VCARD END:VCARD
Bibliography This memo is a result of the work of the Internet Engineering Task Force
Calendaring and scheduling Working Group. The chairmen of that working
group are:
BEGIN:VCARD
VERSION:3.0
Small, Hennessy, Dawson -- Page 14 -- Expires March 1999
N:Ganguly;Anik
FN:Anik Ganguly
ORG:OnTime, Inc.
ADR;WORK;POSTAL;PARCEL:10 Floor;;21700 Northwestern
Highway;Southfield;MI;48075;USA
TEL;WORK;MSG:+1-810-559-5955
TEL;WORK;FAX:+1-810-559-5034
EMAIL;INTERNET:anik@ontime.com
END:VCARD
BEGIN:VCARD
VERSION:3.0
N:Moskowitz;Robert
FN:Robert Moskowitz
EMAIL;INTERNET:rgm-ietf@htt-consult.com
END:VCARD
4. Bibliography
[1] M. Wahl, T. Howes, S. Kille, 'Lightweight Directory Access [1] M. Wahl, T. Howes, S. Kille, 'Lightweight Directory Access
Protocol (v3)', RFC 2251, December 1997, Protocol (v3)', RFC 2251, December 1997,
<URL:ftp://ds.internic.net/rfc/rfc2251.txt> <URL:ftp://ds.internic.net/rfc/rfc2251.txt>
[2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, 'Lightweight Directory [2] M. Wahl, A. Coulbeck, T. Howes, S. Kille, 'Lightweight Directory
Access Protocol (v3): Attribute Syntax Definitions', RFC 2252, Access Protocol (v3): Attribute Syntax Definitions', RFC 2252,
December 1997, <URL:ftp://ds.internic.net/rfc/rfc2252.txt> December 1997, <URL:ftp://ds.internic.net/rfc/rfc2252.txt>
[3] M. Wahl, A Summary of the X.500(96) User Schema for use with [3] F. Dawson, T. Howes, 'vCard MIME Directory Profile', RFC 2426,
LDAPv3', September 1998, <URL:ftp://ds.internic.net/rfc/rfc2426.txt>
RFC 2256, December 1997,
<URL:ftp://ds.internic.net/rfc/rfc2256.txt>
[4] The Directory: Selected Attribute Types. ITU-T Recommendation
X.520, 1993.
[5] The Directory: Selected Object Classes. ITU-T Recommendation
X.521, 1993.
[6] P. Leach `Selecting a server from among many replicas',
INTERNET DRAFT <draft-ietf-asid-replica-selection-00.txt>,
February 1997
[7] P. Leach `Locating Native Internet LDAP Servers',
INTERNET DRAFT <draft-leach-asid-ldap-locating-00.txt>,
[8] F. Dawson, T. Howes, 'vCard MIME Directory Profile',
INTERNET-DRAFT <draft-ietf-asid-mime-vcard-03.txt>,
[9] A. Gulbrandsen, P. Vixie, "A DNS RR for specifying the location
of services (DNS SRV)", RFC 2052,
<ftp://ds.internic.net/rfc/rfc2052.txt>, October 1996.
[10] F. Dawson, D. Stenerson 'Internet Calendaring and Scheduling
Core Ojbect Specification (iCalendar)', Nov 1997,
<URL:ftp://www.ietf.org/internet-drafts/draft-ietf-calsch-ical-
05.txt
> [4] F. Dawson, D. Stenerson 'Internet Calendaring and Scheduling Core
Ojbect Specification (iCalendar)', RFC xxxx, To be published
[11] Mockapetris, P., "Domain Names - Implementation and [5] F. Dawson, S. Mansour `iCalendar Message-Based Interopability
Specification", STD 13, RFC 1035, USC/Information Sciences Protocal (iMIP)', RFC xxxx, To be published
Institute, November 1987.
<URL:ftp://ds.internic.net/rfc/rfc1035.txt>
[12] Network Applications Consortium 'Lightweight Internet Person [6] A. Courtemanche, S. Mansour, P. O'Leary `iCalendar Real-Time
Schema', April 1997, <URL:http://www.netapps.org> Interopability Protocol (iRIP)', August 1998, <URL:
ftp://www.ietf.org/internet-drafts/draft-ietf-calsch-irip-01.txt>
[13] F. Dawson, S. Mansour `iCalendar Message-Based Interopability 5. Full Copyright Statements
Protocal (iMIP)', March 1998,
<URL: ftp://www.ietf.org/internet- Copyright (C) The Internet Society (1998). All Rights Reserved.
drafts/draft-ietf-calsch-imip-04.txt Small, Hennessy, Dawson -- Page 15 -- Expires March 1999
> 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.
[14] A. The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
Courtemanche, S. Mansour, P. O'Leary `iCalendar Real-Time This document and the information contained herein is provided on an "AS
Interopability Protocol ( 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.
iRIP)', November 1997, <URL: Small, Hennessy, Dawson -- Page 16 -- Expires March 1999
ftp://www.ietf.org/internet-drafts/draft-ietf-calsch-irip-00.txt>
 End of changes. 120 change blocks. 
226 lines changed or deleted 324 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/