Mike,
Are there some particular deliverables in the group that you’re
> especially interested in? Just curious to hear your thoughts on which align
> well with the problems you’re trying to solve in your own development and
> the specific user needs/priorities you’re working to address.
>
These d
Hi Martin,
Thanks so much for your comment. I understand that there will be no problem
when any UA will accept "aesgcm".
> Firefox will support aesgcm128 for several releases once "aesgcm" is
> done (something I expect to happen in 48).
Good. I'm looking forward to seeing it will happen.
On Fr
On 4 March 2016 at 18:07, Tomoyuki SHIMIZU wrote:
> On the other hand, it could be renamed according to encryption spec update
> (e.g. changing from "aesgcm128" to "aesgcm"[2][3]). It might suggest each UA
> might support different types or versions of Content-Encoding in the future.
Firefox will
