RFC 2739: Calendar Attributes for vCard and LDAP
In plain English — editorial summary, not part of the RFC
This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2739
- Published
- January 2000
- Authors
- T. Small; D. Hennessy; F. Dawson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 16
- Also known as
- —
- Updated by:
- RFC 6350
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2649An LDAP Control and Schema for Holding Operation SignaturesCurrent
August 1999
- RFC 2891LDAP Control Extension for Server Side Sorting of Search ResultsCurrent
August 2000
- RFC 2247Using Domains in LDAP/X.500 Distinguished NamesUpdated
January 1998
- RFC 3876Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)Current
September 2004
- RFC 3928Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP)Current
October 2004
- RFC 2849The LDAP Data Interchange Format (LDIF) - Technical SpecificationCurrent
June 2000
- RFC 2559Internet X.509 Public Key Infrastructure Operational Protocols - LDAPv2Obsoleted
April 1999
- RFC 3296Named Subordinate References in Lightweight Directory Access Protocol (LDAP) DirectoriesCurrent
July 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?