Calendar users often wish to allow other users to see their busy time information, without viewing the other details of the calendar components (e.g., location, summary, attendees). This allows a significant amount of privacy while still allowing other users to schedule meetings at times when the user is likely to be free.


read-free-busy privilege controls which calendar collections, regular collections, and calendar object resources are examined when a CALDAV:free-busy-query REPORT request is processed (see Section 7.10). This privilege can be granted on calendar collections, regular collections, or calendar object resources.

Servers MUST support this privilege on all calendar collections, regular collections, and calendar object resources.


read-free-busy privilege MUST be aggregated in the DAV read privilege. Servers MUST allow the CALDAV:read-free-busy to be granted without the DAV:read privilege being granted.

Clients should note that when only the CALDAV:read-free-busy privilege has been granted on a resource, access to GET, HEAD, OPTIONS, and PROPFIND on the resource is not implied (those operations are governed by the DAV:read privilege).

This document was automatically converted to XHTML using an RFC to HTML converter with the original text document at the Internet Engineering Task Force web site at .  The original text document should be referred to if there are any errors or discrepancies found in this document.

Need to test your iCalendar feeds? The iCalendar Validator provides developers and testers a method to validate their iCalendar feeds, which can take data from either a URL, file or text snippet and compare it against the RFC 5545 specification.  We believe we have one of the best iCalendar validation tools available on the internet. More information about the validator can be found here.