I have reviewed the -03 version of this draft, and I support this as a
proposed standard.
As an exercise for review, I implemented a large part of the draft (in
plain Python) and found the description completely adequate to produce
working code that parsed the examples in the draft correctly, and could
generate many of them.
On 28 July 2013 07:30, Zach Shelby <zach(_at_)sensinode(_dot_)com> wrote:
I have reviewed this version of the CBOR draft, and am fully supportive of
this as a proposed standard.
For IoT applications over CoAP and other protocols, there is a clear need
for a standard binary object representation with a straightforward mapping
to JSON that is suitable for constrained devices and networks. This is it.
I have not yet implemented CBOR, but plan to do so for use with several
commercial CoAP implementations. Furthermore, JSON based formats used in
this field such as SenML, or standards from other SDOs like OMA Lightweight
M2M that use JSON, will clearly benefit from standardising CBOR.
I found the document to be well written and concise.
Zach Shelby
On Jul 16, 2013, at 9:58 PM, The IESG <iesg-secretary(_at_)ietf(_dot_)org>
wrote:
The IESG has received a request from an individual submitter to consider
the following document:
- 'Concise Binary Object Representation (CBOR)'
<draft-bormann-cbor-04.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf(_at_)ietf(_dot_)org mailing lists by 2013-08-13. Exceptionally,
comments may
be
sent to iesg(_at_)ietf(_dot_)org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.
Abstract
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.
The file can be obtained via
http://datatracker.ietf.org/doc/draft-bormann-cbor/
IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-bormann-cbor/ballot/
No IPR declarations have been submitted directly on this I-D.
--
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com @SensinodeIoT
Mobile: +358 40 7796297
Twitter: @zach_shelby
LinkedIn: http://fi.linkedin.com/in/zachshelby
6LoWPAN Book: http://6lowpan.net
--
Andrew McGregor | SRE | andrewmcgr(_at_)google(_dot_)com | +61 4 8143 7128