[Cbor] RFC 9277 on On Stable Storage for Items in Concise Binary Object Representation (CBOR)
rfc-editor@rfc-editor.org Wed, 31 August 2022 01:15 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 22FCFC14CE33; Tue, 30 Aug 2022 18:15:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nouq8gvaJKWx; Tue, 30 Aug 2022 18:15:22 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B448C15271C; Tue, 30 Aug 2022 18:15:22 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 512914C29A; Tue, 30 Aug 2022 18:15:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20220831011522.512914C29A@rfcpa.amsl.com>
Date: Tue, 30 Aug 2022 18:15:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/t3rycadNawHqeP2ZHs8v7-_5GjA>
Subject: [Cbor] RFC 9277 on On Stable Storage for Items in Concise Binary Object Representation (CBOR)
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 31 Aug 2022 01:15:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9277
Title: On Stable Storage for Items in
Concise Binary Object Representation (CBOR)
Author: M. Richardson,
C. Bormann
Status: Standards Track
Stream: IETF
Date: August 2020
Mailbox: mcr+ietf@sandelman.ca,
cabo@tzi.org
Pages: 18
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cbor-file-magic-12.txt
URL: https://www.rfc-editor.org/info/rfc9277
DOI: 10.17487/RFC9277
This document defines a stored ("file") format for Concise Binary
Object Representation (CBOR) data items that is friendly to common
systems that recognize file types, such as the Unix file(1) command.
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