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

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, jaime.jimenez@ericsson.com, draft-ietf-core-multipart-ct@ietf.org, Jaime Jimenez <jaime.jimenez@ericsson.com>, core@ietf.org, alexey.melnikov@isode.com, core-chairs@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Multipart Content-Format for CoAP' to Proposed Standard (draft-ietf-core-multipart-ct-03.txt)

The IESG has approved the following document:
- 'Multipart Content-Format for CoAP'
  (draft-ietf-core-multipart-ct-03.txt) as Proposed Standard

This document is the product of the Constrained RESTful Environments Working
Group.

The IESG contact persons are Adam Roach, Alexey Melnikov and Ben Campbell.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-core-multipart-ct/


Technical Summary

   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.

Working Group Summary

   The document has gone through multiple expert reviews and
   has been discussed at multiple face-to-face IETF meetings.
   This document was not controversial.

Document Quality

   At least a couple of implementations are interested in implementing
   this document.

Personnel

   Document Shepherd: Jaime Jiménez, <jaime.jimenez@ericsson.com>
   Area Director: Alexey Melnikov, <aamelnikov@fastmail.fm>