ietf
[Top] [All Lists]

Re: Last Call: <draft-bormann-cbor-04.txt> (Concise Binary Object Representation (CBOR)) to Proposed Standard

2013-07-28 21:55:03
The question I want an answer to is whether this is going to be the only
standard for a binary version of JSON allowed.

I have an alternative proposal which is designed to be compatible with JSON
so that existing encoder and decoder implementations can be used and so
that a single decoder can handle the binary features as a superset of the
existing JSON specification.

http://tools.ietf.org/html/draft-hallambaker-jsonbcd-00

What is the process here?

So far I have been led to believe that this is a personal submission that
is not going to be the last chance we get to discuss this in IETF. Now I
see it being a proposed standard. And I am pretty sure that people are
going to be telling other people that this is the agreed IETF standard that
we all have to use because it is what was decided.


There are existing specs that does what CBOR does just as well that have
actual users. There are requirements that the individuals proposing this
chose not to address.





On Tue, Jul 16, 2013 at 3: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.





-- 
Website: http://hallambaker.com/