[core] multipart/core

[Michael Richardson <[e-mail]>]

Jaime...

Carsten, Thomas and Klaus have just updated:
   <https://tools.ietf.org/html/draft-fossati-core-multipart-ct-04>
which says very succintly:

   The collection is encoded as a CBOR [RFC7049] array with an even
   number of elements.  The second, fourth, sixth, etc. element is a
   byte string containing a representation, or the value "null" if an
   optional part is indicated as not given.  The first, third,
   fifth, etc. element is an unsigned integer specifying the content format ID
   of the representation following it.

   For example, a collection containing two representations, one with
   content format ID 42 and one with content format ID 0, looks like
   this in CBOR diagnostic notation:

      [42, h'0123456789abcdef', 0, h'3031323334']


EST-COAP (in the ACE WG) needs a multipart reply for the corner case of
server generated (private) keys. Servergen is supported in RFC7030, greatly
desired by some parties, although some parties deem it a mis-feature.

I can't see anything wrong with the draft as it is, and I'd like to see it
quickly adopted and WGLC'ed....

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [