[rfc-dist] RFC 8710 on Multipart Content-Format for the Constrained Application Protocol (CoAP)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Feb 28 14:53:36 PST 2020

A new Request for Comments is now available in online RFC libraries.

        RFC 8710

        Title:      Multipart Content-Format for the Constrained 
                    Application Protocol (CoAP) 
        Author:     T. Fossati,
                    K. Hartke,
                    C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    thomas.fossati at arm.com, 
                    klaus.hartke at ericsson.com, 
                    cabo at tzi.org
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-multipart-ct-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8710

        DOI:        10.17487/RFC8710

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.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

More information about the rfc-dist mailing list