[Cbor] Charter update
Jim Schaad <ietf@augustcellars.com> Thu, 16 May 2019 22:32 UTC
Return-Path: <ietf@augustcellars.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 DE601120303 for <cbor@ietfa.amsl.com>; Thu, 16 May 2019 15:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 pXz8E1Ap2rAh for <cbor@ietfa.amsl.com>; Thu, 16 May 2019 15:32:56 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4751B1200C7 for <cbor@ietf.org>; Thu, 16 May 2019 15:32:56 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 16 May 2019 15:32:50 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: cbor@ietf.org
Date: Thu, 16 May 2019 15:32:48 -0700
Message-ID: <032801d50c37$4b8a3120$e29e9360$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdUMNvx+utiu9f6DTDG4DK5fEMrymQ==
Content-Language: en-us
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/wJowENZcJ6NAQMwxIhjr3t3utdo>
Subject: [Cbor] Charter update
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: Thu, 16 May 2019 22:32:59 -0000
Francesca and I have gotten together and cobbled together a revised charter for the working group. I have created a github project https://github.com/cbor-wg/charter for editing of the charter. We will monitor the mailing list as well and create pull requests from that, but feel free to create your own. Here is a copy Concise Binary Object Representation (CBOR, RFC 7049) extends the JavaScript Object Notation (JSON, RFC 7159) data interchange format to include binary data and an extensibility model, using a binary representation format that is easy to parse correctly. It has been picked up by a number of IETF efforts (e.g., CORE, ANIMA GRASP) as a message format. The CBOR working group will update RFC 7049 to fix verified errata. Security issues and clarifications may be addressed, but changes to the document will ensure backward compatibility for popular deployed codebases. The resulting document will be targeted at becoming a Full Internet Standard. After that, the CBOR working group will monitor issues found with the CBOR specification and, if needed, will produce an updated document. Similar to the way ABNF (RFC 5234/7405) can be used to describe the set of valid messages in a text representation, it is useful for protocol specifications to use a description format for the data in CBOR-encoded messages. The Concise Data Definition Language (CDDL) is such a description technique that has already been used in CORE, ANIMA, CDNI, and efforts outside the IETF. The first version of CDDL has been published as RFC XXXX. While this version has been completed, several new features were raised during the update process that were not included in this version, in order not to delay publication, and to allow publication in the Standards Track. One example of such a feature is the ability to combine multiple CDDL files together using a mechanism other that manually concatenating them together for processing. The working group will collect these features as well as other features that are raised by users of CDDL, evaluate their utility and add to a second version of the specification if warranted. The working group will evaluate the necessity of providing advice and guidance for developers using CBOR and CDDL. It is currently expected that this would be done using a Wiki of some type. This work would not be expected to be published by the IETF. There are a number of extensions to CBOR types that are either currently adopted by the working group, other working groups, or individual submissions. Additionally, there are expected to be other such documents that will come to the attention of the working group. In some cases the working group expects to adopt and publish these proposals. The working group will evaluate and place proposals in one of the following categories using a dispatch like process: * General purpose extensions that are expected to have broad usage: The working group will normally adopt and publish such proposals. Examples of proposals in this category are CBOR Sequence (draft-bormann-cbor-sequence) and Error Indications (draft-richter-cbor-error-tag). * Internet wide specific purpose extensions: The working group may decide to adopt these proposals, but typically it would just provide input and recommend that they be published either as an Independent Submission or by a different working group. * Narrow purpose extensions: The working group may provide evaluation of such proposals, but typically would not support Working Group adoption, and could recommend publication in a different forum. An example of this might be portions of draft-bormann-cbor-tags-oid dealing with some of the more esoteric types such as regular expressions
- [Cbor] Charter update Jim Schaad
- Re: [Cbor] Charter update Carsten Bormann
- Re: [Cbor] Charter update Jim Schaad