Re: [media-types] Review requested for draft-bormann-cbor-04

[Bjoern Hoehrmann <[e-mail]>]

* Paul Hoffman wrote:
>At 09:09 15-07-2013, Bjoern Hoehrmann wrote:
>* John R Levine wrote:
>>>  Encoding considerations:  none; CBOR is a binary format
>> 
>> Then it's 'binary', not 'none'.
>
>I have seen it done as "none" more often than "binary". Can this group 
>give us a definitive answer for the choice? We're happy to do what the 
>group wants, but right now I can't tell which it should be.

See <http://tools.ietf.org/html/rfc6838#section-4.8>. RFC 2048 did not
list particular values to use, but RFC 4288 and its successor let you
choose only among the four values listed, and "none" is not among them.

>>>  Security considerations:  Same as for the base document
>> 
>> This could use an additional sentence explaining why there is and what
>> is a "base document" in this context, and why the higher-level format
>> does not introduce any new security considerations.
>
>This registration is part of an Internet-Draft this is likely to become 
>an RFC; the registration won't live on its own or, if it does, that 
>should say "the registration comes from RFC wxyz". If this group has a 
>preferred way of saying that, we'd be happy to use it.

In RFC 4329 I used "See section 5." if that is the intended meaning.

>>>  Applications that use this media type:  None yet, but it is expected
>>>     that this format will be deployed in many protocols and
>>>     applications.
>> 
>> This should provide more contextual detail than "many".
>
>Your faith in our predictive abilities is appreciated, but badly misplaced. We will simply remove "many".
>
>> Is there a
>> particular kind of application that would use it, like backup and
>> archival software or 3d modeling applications or Office programs?
>
>Again, that's defined in the Internet-Draft.

The field is supposed to give readers an idea in what context the type
fits in. You could say something like "an application- and protocol-
independent data serialization format for storage and exchange between
systems" if that sounds about right.
-- 
Björn Höhrmann · mailto:[e-mail] · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: [phone] · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/