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

Document Type Active Internet-Draft (core WG)
Last updated 2019-08-21
Replaces draft-fossati-core-multipart-ct, draft-bormann-core-maybe
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 IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has a DISCUSS. Has enough positions to pass once DISCUSS positions are resolved.
Responsible AD Alexey Melnikov
Send notices to Jaime Jimenez <jaime.jimenez@ericsson.com>
IANA IANA review state Version Changed - Review Needed
CoRE                                                          T. Fossati
Internet-Draft                                                       ARM
Intended status: Standards Track                               K. Hartke
Expires: February 22, 2020                                      Ericsson
                                                              C. Bormann
                                                 Universitaet Bremen TZI
                                                         August 21, 2019

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

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 February 22, 2020.

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 February 22, 2020               [Page 1]
Internet-Draft      Multipart Content-Format for CoAP        August 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 . . . . . . . . . . . . . .   4
   3.  Usage Example: Observing Resources  . . . . . . . . . . . . .   4
   4.  Implementation Hints  . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Registration of media type application/multipart-core . .   6
     5.2.  Registration of a Content-Format identifier for
           application/multipart-core  . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

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, each along with a CoAP Content-
   Format identifier, into a single representation, with minimal framing
   overhead.  This combined representation may then be carried in a
   single message, such as a CoAP [RFC7252] request or response body.

   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.

   As the name of the media-type suggests, it is inspired by the
   multipart media types that started to be defined with the original
   set of MIME specifications [RFC2046].  However, while those needed to
   focus on the syntactic aspects of integrating multiple
   representations into one e-mail, transfer protocols providing full
   data transparency such as CoAP as well as readily available encoding
   formats such as the Concise Binary Object Representation (CBOR)
   [RFC7049] shift the focus towards the intended use of the combined
   representations.  In this respect, the basic intent of the
   application/multipart-core media type is like that of multipart/mixed
   (Section 5.1.3 of [RFC2046]).  The detailed semantics of the
Show full document text