[core] About draft-doi-core-parameter-option

[Yusuke DOI <[e-mail]>]

Dear core folks,

Because I have had no time to explain about my proposal on CoAP, please
let me do it on the ML.

CoAP uses (discrete) content-format to describe combination of
content-type and media type parameters. Content-Format is also used by
Accept option and I suppose more than 99% of expected communications in
CoAP is okay. However, some communications that requires free-format
parameter on media types (including EXI schema nego that is used in
ZigBee SEP2.0) is not possible in CoAP. Of course, there is a workaround
to define 'per-resource' parameter and put it on URI path. However, this
hinders (for example) use of CoAP-HTTP GW without per-resource knowledge
on media type parameter and resource parameter mapping.

My proposal update is now focused on server side content negotiation and
thus it only defines parameter options for the Accept option. Because
CoAP now has only one Accept option, the format is also simplified
(previous proposal has index to specify a parameter option to [i]th
Accept option).

FYI: There is a proposal on NetConf to use EXI. Currently, there is no
adpotion of CoAP on NetConf (there is another proposal on RESTful API of
NetConf). But I think this could be an interesting combination: NetConf
RESTful API transported over CoAP.

Any comments are welcome.

-- 
// Yusuke DOI <[e-mail]>