Re: [Roll] [dhcwg] MPL config draft (Re: I-D Action: draft-ietf-roll-mpl-parameter-configuration-01.txt)

[Yusuke DOI <[e-mail]>]

Hi Bernie,

(2014-07-09 5:59), Bernie Volz (volz) wrote:
> Hi:
>
> I don't have a great answer for you as I have no idea what the
> typical usages are likely to be. If there are likely to be many
> instances and the desire to configure most of the values (and for
> multiple domains), then one single option for each domain with all
> of the values is certainly a better idea.

Thanks, I'll add some note to describe expected use case. The options
are likely to be used as a set and I think open single option is easier
to implement.

> I think the main points here are to: - avoid compressing the data /
> developing new data types and use more standard elements (i.e., 16
> or 32-bit integers) - see RFC 7227. - group things logically (i.e.,
> alignment of the data, while making the picture easier to draw, is
> not a requirement [of course we assume it is octet (byte) aligned]).

I agree. In addition, I noticed 8bit common exponent (in other words, 
unit time of timers) for all timers will be much much simpler.

> There are many ways to format this data, each with pros and cons.
> Making those tradeoffs is something I am not in a good position to
> help you with.

Your comments are very helpful for me, thanks!

Regards,

Yusuke