[Cbor] RFC 8610 on Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
rfc-editor@rfc-editor.org Wed, 12 June 2019 23:39 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 33BDC120152; Wed, 12 Jun 2019 16:39:48 -0700 (PDT)
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=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 eovIkeo5rNfn; Wed, 12 Jun 2019 16:39:46 -0700 (PDT)
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 1D1E8120139; Wed, 12 Jun 2019 16:39:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D212AB80083; Wed, 12 Jun 2019 16:39:30 -0700 (PDT)
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: <20190612233930.D212AB80083@rfc-editor.org>
Date: Wed, 12 Jun 2019 16:39:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/FQVzHwXXRBjciqt4WvQC8VIr46g>
Subject: [Cbor] RFC 8610 on Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures
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: Wed, 12 Jun 2019 23:39:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8610
Title: Concise Data Definition Language (CDDL):
A Notational Convention to Express Concise
Binary Object Representation (CBOR) and JSON
Data Structures
Author: H. Birkholz,
C. Vigano,
C. Bormann
Status: Standards Track
Stream: IETF
Date: June 2019
Mailbox: henk.birkholz@sit.fraunhofer.de,
christoph.vigano@uni-bremen.de,
cabo@tzi.org
Pages: 64
Characters: 125233
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-cbor-cddl-08.txt
URL: https://www.rfc-editor.org/info/rfc8610
DOI: 10.17487/RFC8610
This document proposes a notational convention to express Concise
Binary Object Representation (CBOR) data structures (RFC 7049). Its
main goal is to provide an easy and unambiguous way to express
structures for protocol messages and data formats that use CBOR or
JSON.
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