RFC 8742 on Concise Binary Object Representation (CBOR) Sequences

rfc-editor@rfc-editor.org Wed, 19 February 2020 22:57 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 920F1120926; Wed, 19 Feb 2020 14:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable 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 MKT-XnHsp1Fs; Wed, 19 Feb 2020 14:57:17 -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 50F06120945; Wed, 19 Feb 2020 14:57:17 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 33AA0F40738; Wed, 19 Feb 2020 14:57:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3NDIgb24gQ29uY2lzZSBCaW5hcnkgT2JqZWN0IFJlcHJlc2VudGF0aW9uIChDQk9SKSBTZXF1ZW5jZXM=?=
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, cbor@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200219225713.33AA0F40738@rfc-editor.org>
Date: Wed, 19 Feb 2020 14:57:13 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/MoCBwHcvZXGdKGT5jjy0uwcjB74>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2020 22:57:25 -0000

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

        
        RFC 8742

        Title:      Concise Binary Object Representation (CBOR) 
                    Sequences 
        Author:     C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    cabo@tzi.org
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cbor-sequence-02.txt

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

        DOI:        10.17487/RFC8742

This document describes the Concise Binary Object Representation
(CBOR) Sequence format and associated media type
"application/cbor-seq".  A CBOR Sequence consists of any number of
encoded CBOR data items, simply concatenated in sequence.

Structured syntax suffixes for media types allow other media types to
build on them and make it explicit that they are built on an existing
media type as their foundation.  This specification defines and
registers "+cbor-seq" as a structured syntax suffix for CBOR
Sequences.

This document is a product of the Concise Binary Object Representation Maintenance and Extensions 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