CBOR-encoded Form Data
draft-hartke-t2trg-cbor-forms-00

Document Type Active Internet-Draft (individual)
Last updated 2016-10-31
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Thing-to-Thing Research Group                                  K. Hartke
Internet-Draft                                   Universitaet Bremen TZI
Intended status: Experimental                           October 31, 2016
Expires: May 4, 2017

                         CBOR-encoded Form Data
                    draft-hartke-t2trg-cbor-forms-00

Abstract

   This document describes a media type to encode form data in CBOR
   format.

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 May 4, 2017.

Copyright Notice

   Copyright (c) 2016 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.

Hartke                     Expires May 4, 2017                  [Page 1]
Internet-Draft           CBOR-encoded Form Data             October 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Form Body Syntax  . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Form Data Syntax  . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Media Type  . . . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  CoAP Content-Format . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   This document describes a media type to encode form data in CBOR
   [RFC7049] format, similar to the well-known "application/x-www-form-
   urlencoded" [W3C.REC-html5-20141028] and "multipart/form-data"
   [RFC7578] media types.  The use of a compact, binary representation
   format enables the processing of form submissions on systems with
   very limited memory, processor power, and instruction sets [RFC7228].

1.1.  Terminology

   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].

2.  Form Body Syntax

   CoRAL [I-D.hartke-t2trg-coral] provides a representation format for
   forms that is suitable for constrained systems.  However, it does not
   provide a syntax for specifying the fields of a form in the form body
   and leaves this task to other specifications.  This section defines
   such a syntax.

   A form body in this syntax consists of one or more form fields.  Each
   form field consists of a field name and a type.  The field name is an
   arbitrary text string.  The field type is a text string that matches
   the ABNF rule "type" from [I-D.greevenbosch-appsawg-cbor-cddl].

   Form fields can be combined with two combinators, ALL and ANY.  The
   ALL combinator indicates that the form submitter MUST submit all the
   members of the expression.  The ANY combinator indicates that the
   form submitter MUST submit exactly one member of the expression.

Hartke                     Expires May 4, 2017                  [Page 2]
Internet-Draft           CBOR-encoded Form Data             October 2016
Show full document text