![]() ![]() This will beĪddressed in the "Calendar Access Protocol" specification. Yet to be defined by the IETF CALSCH Working Group. The semantics for using this URI as an access protocol locator are ![]() Location from which a calendaring and scheduling client (i.e., CUA)Ĭan communicate with a user's entire calendar. The Calendar Access URI is defined to be a protocol independent RFC 2739 Locating a Calendar User January 2000 1.2 Calendar Access URI (CAPURI) Object (e.g., with the "ics" file extension). URI points to a file resource, it is recommended that the fileĮxtension be "ifb" to distinguish it from an arbitrary iCalendar Guideline, it is recommended that the previous six weeks of busy timeĭata be published at the location associated with the FBURL. PRODID:-//hacksw/handcal//NONSGML amount of busy time data pointed to by the FBURL will generallyīe pre-determined for example one month of busy time data. If a MIME transport is being used, the response will beĬontained within a "text/calendar" MIME body part as specified in the ICalendar object containing one or more "VFREEBUSY" calendarĬomponents. If a calendaring and scheduling client (i.e., CUA) were to retrieveĭata from this location using FTP or HTTP, it would get back an Revisions of this specification may provide for the extended The present time, this URI only points to busy time data. Where a client can obtain information about when a user is busy. The free/busy URI is defined to be a transport independent location RFC 2739 Locating a Calendar User January 2000 1 Calendaring and Scheduling URIs 8 2.4 DIRECTORY LOOKUP USING THE LDAP V3 PROTOCOL. 8 2.3.4 CALURI Property IANA Registration. 7 2.3.3 CAPURI Property IANA Registration. 6 2.3.2 CALADRURI Property IANA Registration. 5 2.3.1 FBURL Property IANA Registration. 5 2.2 PERSONAL DATA EXCHANGE USING A VCARD. RFC 2739 Locating a Calendar User January 2000ġ CALENDARING AND SCHEDULING URIS. Directory lookup using the LDAP protocol. Personal data exchange using the vCard format and This memo defines three mechanisms for obtaining a URI to a user'sĬalendar and free/busy time. In order to meet these challenges, a calendar user agent (CUA) needsĪ mechanism to locate (URI) individual user's calendar and free/busy Whether the attendee will be free to participate in the event. Additionally, access toĪn attendee's current "busy time" provides an a priori indication of Prerequisite that an organizer has the calendar address of eachĪttendee that will be invited to the event. When scheduling a calendar entity, such as an event, it is a Distribution of this memo is unlimited.Ĭopyright (C) The Internet Society (2000). Official Protocol Standards" (STD 1) for the standardization stateĪnd status of this protocol. Please refer to the current edition of the "Internet Internet community, and requests discussion and suggestions for This document specifies an Internet standards track protocol for the Updated by: 6350 Errata Exist Network Working Group T. RFC 2739: Calendar Attributes for vCard and LDAP ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |