[Cbor] Protocol Action: 'Concise Binary Object Representation (CBOR)' to Internet Standard (draft-ietf-cbor-7049bis-16.txt)

The IESG <iesg-secretary@ietf.org> Wed, 30 September 2020 17:05 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Cc: barryleiba@gmail.com, Francesca Palombini <francesca.palombini@ericsson.com>, rfc-editor@rfc-editor.org, draft-ietf-cbor-7049bis@ietf.org, cbor-chairs@ietf.org, cbor@ietf.org, francesca.palombini@ericsson.com, The IESG <iesg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160148552994.8062.6127718243791719665@ietfa.amsl.com>
Date: Wed, 30 Sep 2020 10:05:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/Eistj3f7o4qQOSE-qXsA8k6dT14>
Subject: [Cbor] Protocol Action: 'Concise Binary Object Representation (CBOR)' to Internet Standard (draft-ietf-cbor-7049bis-16.txt)

The IESG has approved the following document:
- 'Concise Binary Object Representation (CBOR)'
  (draft-ietf-cbor-7049bis-16.txt) as Internet Standard

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

The IESG contact persons are Murray Kucherawy and Barry Leiba.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-cbor-7049bis/




Technical Summary:

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.

Working Group Summary:

It is worth noting the controversy about the text on how generic decoders
handle duplicate map keys. While RFC7049 stated that decoders cannot
prescribe a specific handling of duplicated map keys, except it might consider
the map malformed, part of the working group wanted the document to state
more precisely what the decoder should do, and possibly what the protocol
using CBOR should do (e.g. use first entry). This was considered, but would
have made existing implementation non-compliant with this specification.
Consensus was difficult to call, but in the end some text was added to explain
the different options (reject the map, accept the map including the duplicates,
lose some entries) and give guidance to implementations on what is expected of
the application in every one of these cases. (See section 5.6)

Document Quality:

There exist a significant number of implementations of this specification, see
https://cbor.io/impls.html for a non-exhaustive list.
Several of the working group participants have provided continuous reviews to
the document, and have agreed that the document is ready for publication.

Personnel:

Francesca Palombini is the Document Shepherd.
Barry Leiba is the Responsible Area Director.

[Cbor] Protocol Action: 'Concise Binary Object Re… The IESG