metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8710: Multipart Content-Format for the Constrained Application Protocol (CoAP)

In plain English — editorial summary, not part of the RFC

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 with a Constrained Application Protocol (CoAP) Content-Format identifier) into a single representation, with minimal framing overhead.

Document record

Document ID
RFC8710
Published
February 2020
Authors
T. Fossati; K. Hartke; C. Bormann
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
9
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/8710-multipart-content-format-for-the-constrained-application-protocol-coap