Hi,
Thank you for working on the I-D.
This is a must-have and I am looking forward to seeing it
standardized. H2O will implement this specification.
One question: is the name `early-data` a good choice?
The reason I raise the concern is because what the header suggest is
if the endpoint has not
Hi Kazuho,
On Mon, Jun 26, 2017 at 04:03:24PM +0900, Kazuho Oku wrote:
> One question: is the name `early-data` a good choice?
>
> The reason I raise the concern is because what the header suggest is
> if the endpoint has not yet seen a proof (i.e. ClientFinished). The
> name "early-data" might b
On Sun, Jun 25, 2017 at 11:43 PM, Ilari Liusvaara
wrote:
> I understood that the cache probing attack requires much less replays
> than the other side-channel ones. And furthermore, distributing the
> replays among zones makes the attack easier (because replay with the
> cached data hot doesn't t
OK, I'll move this out of the "if you can do a lot of replays" section
On Mon, Jun 26, 2017 at 10:25 AM, Colm MacCárthaigh
wrote:
>
>
> On Sun, Jun 25, 2017 at 11:43 PM, Ilari Liusvaara <
> ilariliusva...@welho.com> wrote:
>
>> I understood that the cache probing attack requires much less replay
> On 27 Jun 2017, at 3:25 am, Colm MacCárthaigh wrote:
>
>
>
> On Sun, Jun 25, 2017 at 11:43 PM, Ilari Liusvaara
> wrote:
> I understood that the cache probing attack requires much less replays
> than the other side-channel ones. And furthermore, distributing the
> replays among zones makes
Hi Willy,
2017-06-26 17:01 GMT+09:00 Willy Tarreau :
> Hi Kazuho,
>
> On Mon, Jun 26, 2017 at 04:03:24PM +0900, Kazuho Oku wrote:
>> One question: is the name `early-data` a good choice?
>>
>> The reason I raise the concern is because what the header suggest is
>> if the endpoint has not yet seen
