Parameter Value Encoding in iCalendar and vCard
draft-daboo-ical-vcard-parameter-encoding-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-07-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           C. Daboo
Internet-Draft                                                     Apple
Updates: 5545,6350 (if approved)                            July 7, 2012
Intended status: Standards Track
Expires: January 8, 2013

            Parameter Value Encoding in iCalendar and vCard
              draft-daboo-ical-vcard-parameter-encoding-00

Abstract

   This specification defines an extension to iCalendar and vCard data
   formats to allow parameter values to include certain characters
   forbidden by the existing specifications.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 8, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Daboo                    Expires January 8, 2013                [Page 1]
Internet-Draft             Parameter Encoding                  July 2012

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Conventions Used in This Document . . . . . . . . . . . . . . . 3
   3.  Parameter Value Encoding Scheme . . . . . . . . . . . . . . . . 3
     3.1.  iCalendar Example . . . . . . . . . . . . . . . . . . . . . 4
     3.2.  vCard Examples  . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   6.  Normative References  . . . . . . . . . . . . . . . . . . . . . 5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 5

Daboo                    Expires January 8, 2013                [Page 2]
Internet-Draft             Parameter Encoding                  July 2012

1.  Introduction

   The iCalendar [RFC5545] specification defines a standard way to
   describe calendar data.  The vCard [RFC6350] specification defines a
   standard way to describe contact data.  Both of these use a similar
   textual data format.  Each iCalendar and vCard data object can
   include "properties" which have "parameters" and a "value".  The
   value of a "parameter" is typically a token or URI value, but a
   "generic" text value is also allowed.  However, the syntax rules for
   both iCalendar and vCard prevent the use of a double-quote character
   or control characters in such values.

   As more and more extensions are being developed for these data
   formats, there is a need to allow at least double-quotes, line feeds
   and tabs to be included in parameter values.  The \-escaping
   mechanism used for property text values is not defined for use with
   parameter values and cannot be easily used in a backwards compatible
   manner.  Thus this specification defines a new character escaping
   mechanism that is compatible with existing parsers and chosen to
   minimise any impact on existing data.

2.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

3.  Parameter Value Encoding Scheme

   This specification defines the ^ character (U+005E - Circumflex
   Accent) as an escape character in parameter values whose value type
Show full document text