[core] RFC 8710 on Multipart Content-Format for the Constrained Application Protocol (CoAP)
rfc-editor@rfc-editor.org Fri, 28 February 2020 22:53 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FC43A1FB9; Fri, 28 Feb 2020 14:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94c9vceH8_7K; Fri, 28 Feb 2020 14:53:52 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29C2E3A0DBA; Fri, 28 Feb 2020 14:53:52 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6346FF40714; Fri, 28 Feb 2020 14:53:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200228225336.6346FF40714@rfc-editor.org>
Date: Fri, 28 Feb 2020 14:53:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/bzt2JpW3ibsJnLsMnPglx_j9maE>
Subject: [core] RFC 8710 on Multipart Content-Format for the Constrained Application Protocol (CoAP)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Feb 2020 22:54:01 -0000
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@arm.com,
klaus.hartke@ericsson.com,
cabo@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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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@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