[Cbor] STD 94, RFC 8949 on Concise Binary Object Representation (CBOR)

rfc-editor@rfc-editor.org Sat, 05 December 2020 00:41 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E33913A103E; Fri, 4 Dec 2020 16:41:06 -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=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 tIoFaTm9_rmB; Fri, 4 Dec 2020 16:41:05 -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 ABBD33A10A9; Fri, 4 Dec 2020 16:41:01 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1EA1BF40726; Fri, 4 Dec 2020 16:40:56 -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, cbor@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20201205004056.1EA1BF40726@rfc-editor.org>
Date: Fri, 4 Dec 2020 16:40:56 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/3dJ3YPWb-8z4CwpitcyKGx_ogOo>
Subject: [Cbor] =?utf-8?q?STD_94=2C_RFC_8949_on_Concise_Binary_Object_Rep?= =?utf-8?q?resentation_=28CBOR=29?=
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2020 00:41:07 -0000

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

        STD 94        
        RFC 8949

        Title:      Concise Binary Object Representation (CBOR) 
        Author:     C. Bormann,
                    P. Hoffman
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2020
        Mailbox:    cabo@tzi.org, 
                    paul.hoffman@icann.org
        Pages:      66
        Obsoletes:  RFC 7049
        See Also:   STD 94

        I-D Tag:    draft-ietf-cbor-7049bis-16.txt

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

        DOI:        10.17487/RFC8949

The Concise Binary Object Representation (CBOR) is a data format
whose design goals include the possibility of extremely small code
size, fairly small message size, and extensibility without the need
for version negotiation. These design goals make it different from
earlier binary serializations such as ASN.1 and MessagePack.

This document obsoletes RFC 7049, providing editorial improvements,
new details, and errata fixes while keeping full compatibility with
the interchange format of RFC 7049.  It does not create a new version
of the format.

This document is a product of the Concise Binary Object Representation Maintenance and Extensions Working Group of the IETF.

This is now an Internet 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