Multipart Content-Format for CoAP
draft-ietf-core-multipart-ct-03

Document Type Active Internet-Draft (core WG)
Last updated 2019-03-18 (latest revision 2019-03-08)
Replaces draft-bormann-core-maybe, draft-fossati-core-multipart-ct
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jaime Jimenez
Shepherd write-up Show (last changed 2019-03-20)
IESG IESG state In Last Call (ends 2019-04-08)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to Jaime Jimenez <jaime.jimenez@ericsson.com>
IANA IANA review state IANA - Review Needed
IANA action state None
CoRE                                                          T. Fossati
Internet-Draft                                                       ARM
Intended status: Standards Track                               K. Hartke
Expires: September 9, 2019                                      Ericsson
                                                              C. Bormann
                                                 Universitaet Bremen TZI
                                                          March 08, 2019

                   Multipart Content-Format for CoAP
                    draft-ietf-core-multipart-ct-03

Abstract

   This memo defines application/multipart-core, an application-
   independent media-type that can be used to combine representations of
   zero or more different media types into a single message, such as a
   CoAP request or response body, with minimal framing overhead, each
   along with a CoAP Content-Format identifier.

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 https://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 September 9, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Fossati, et al.         Expires September 9, 2019               [Page 1]
Internet-Draft      Multipart Content-Format for CoAP         March 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Multipart Content-Format Encoding . . . . . . . . . . . . . .   3
   3.  Usage Examples  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Observing Resources . . . . . . . . . . . . . . . . . . .   4
   4.  Implementation hints  . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
     5.1.  Registration of media type application/multipart-core . .   5
     5.2.  Registration of a Content-Format identifier for
           application/multipart-core  . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This memo defines application/multipart-core, an application-
   independent media-type that can be used to combine representations of
   zero or more different media types into a single message, such as a
   CoAP [RFC7252] request or response body, with minimal framing
   overhead, each along with a CoAP Content-Format identifier.

   This simple and efficient binary framing mechanism can be employed to
   create application specific request and response bodies which build
   on multiple already existing media types.

   The individual representations in an application/multipart-core body
   occur in a sequence, which may be employed by an application where
   such a sequence is natural, e.g. for a number of audio snippets in
   different formats to be played out in that sequence.

   In other cases, an application may be more interested in a bag of
   representations, which are distinguished by their Content-Format
   identifier, such as an audio snippet and a text representation
   accompanying it.  In such a case, the sequence in which these occur
   may not be relevant to the application.  This specification allows to
   indicate that an optional part is not present by substituting a null
   value for the representation of the part.

Fossati, et al.         Expires September 9, 2019               [Page 2]
Show full document text