RFC 6868: Parameter Value Encoding in iCalendar and vCard
In plain English — editorial summary, not part of the RFC
This specification updates the data formats for iCalendar (RFC 5545) and vCard (RFC 6350) to allow parameter values to include certain characters forbidden by the existing specifications.
Document record
- Document ID
- RFC6868
- Published
- February 2013
- Authors
- C. Daboo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6638Scheduling Extensions to CalDAVUpdated
June 2012
- RFC 6352CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)Updated
August 2011
- RFC 7451Extension Registry for the Extensible Provisioning ProtocolCurrent
February 2015
- RFC 5733Extensible Provisioning Protocol (EPP) Contact MappingCurrent
August 2009
- RFC 5546iCalendar Transport-Independent Interoperability Protocol (iTIP)Updated
December 2009
- RFC 4791Calendaring Extensions to WebDAV (CalDAV)Updated
March 2007
- RFC 8984JSCalendar: A JSON Representation of Calendar DataCurrent
July 2021
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 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?