Re: [core] A question on handling of option parameters defined in HTTP

[DOI Yusuke <[e-mail]>]

Hi Klaus, and all,

As a weekend work, I wrote a draft and just submitted as proposal to
solve parameter problem in some use cases.  (including my EXI
content/schema negotiation)

>	Title           : CoAP Option Parameter Option
>	Author(s)       : Yusuke Doi
>	Filename        : draft-doi-core-parameter-option-00.txt
>	Pages           : 7
>	Date            : 2012-08-21

Any comments are appriciated. 

A trick is to make three options with identical functionarity
(Parameter-Option 1, 2, 3). This is because parameter options need
index to another option, and calculation of option index could be
dirty code if the parameter option is before the other option. I think
there was rough agreement to make three partitions of option number in
the last F2F, I made a parameter option per partition.

A concern is to have complex data type (1-octet integer, 2-octet
integer, string). I don't know other options with complex type. Is
there any reason to avoid it?

Regards,

// Yusuke DOI <[e-mail]>, TOSHIBA R&D Center


From: Klaus Hartke <[e-mail]>
Subject: Re: [core] A question on handling of option parameters defined in HTTP
Date: Mon, 20 Aug 2012 12:34:11 +0300

> Yusuke DOI wrote:
> > If it's not too late, I'll write up some proposal draft(s) for arbtrary
> > parameter option (by number and by string).
> 
> I think it would be a good idea to explore this a bit. Maybe don't go
> into details yet, just describe the the problem, give a few motivating
> examples, and outline your solution. Doesn't have to be a draft if
> it's not too long.
> 
> 
> Klaus