Hi Victor,
It seems my brain skipped over "ALPS in HTTPS" [1] when you mentioned in
your original email. I was reading it in the context of David Benjamin's
thread on Client Hint Reliability [2]. There's a couple of things that
surprised me when reading both drafts:
1. ALPS in HTTPS actually supp
On Mon, 20 Jul 2020, 21:38 David Benjamin, wrote:
> On Mon, Jul 20, 2020 at 3:33 PM Victor Vasiliev 40google@dmarc.ietf.org> wrote:
>
>> On Mon, Jul 20, 2020 at 3:10 PM Lucas Pardue
>> wrote:
>>
>>> Hi Victor,
>>>
>>> It seems my brain
On Mon, Jul 20, 2020 at 10:42 PM David Benjamin
wrote:
> On Mon, Jul 20, 2020 at 5:00 PM Lucas Pardue
> wrote:
>
>>
>> That makes sense but I guess I don't see the point in defining a new
>> thing that contains frames that are never sent on streams. That is, if
As I understood things in ALPS, each application protocol has its own
settings so I don't see there being too much problem with the disjoint
number spaces. It is a bit fussy but it avoids having to rework existing
stacks to parse frames that don't belong to any streams. From the stacks
that I'm ex
The meeting is over now
On Wed, Nov 10, 2021 at 7:37 PM Lars Eggert wrote:
> Hi,
>
> On 2021-11-10, at 17:20, Martin Duke wrote:
> > This is a reminder that we are holding a side meeting on openSSL and
> QUIC shortly after the third session today:
> >
> > https://trac.ietf.org/trac/ietf/meeting
Hi Rory,
I echo Watson and Martin, lets discuss this in the HTTP WG.
As for a very brief technical response. In general I'm supportive of the
idea of more agility of the static table but I think my motivations would
be different than the ones behind this proposal. For me, I'd like more
domain-spe
list as described in the
guidance below.
Cheers,
Lars, Lucas and Mark
QUIC WG Chairs
-- Forwarded message -
From: Lucas Pardue
Date: Wed, Jun 10, 2020 at 2:36 AM
Subject: Working Group Last Call: QUIC protocol drafts
To: QUIC WG
Hello,
After more than three and a half years
patterns are similar.". But that's a decision that must be weighed against
> many other factors, from consolidation pressure to infrastructure budget, so
> it seemed best to just mention the math and let the operator choose as they
> will.
That seems OK. I have no inspir
Reviewer: Lucas Pardue
Review result: Ready
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more
