On Tue, Nov 17, 2020 at 4:38 PM Kazuho Oku <[email protected]> wrote:
> > That said, I am not sure if we have to change the greasing scheme at this > point. When we noticed that the ack-delay extension was colliding with the > greasing ID, I created the PR below, that detects such misuse at compile > time: > > https://github.com/h2o/quicly/pull/416 > > It might just be sufficient if other endpoints implement this type of > detection scheme as well. > Google's implementation does something similar, though at compile time: https://source.chromium.org/chromium/chromium/src/+/master:net/third_party/quiche/src/quic/core/crypto/transport_parameters.cc;l=1039;drc=f50df03b5c021e63d80ecf09ea452fa9976071ea;bpv=1;bpt=1 . >
