Randall:
This direction seem fine to me, but I think you misunderstood my suggestion
(4). I am just suggesting a change in ordering, State the definition, and
then use the defined term.
Russ
> On Jan 31, 2022, at 5:59 PM, Randall Gellens
> wrote:
>
> (1) I'm fine with the Abstract as it
Reviewer: Matt Joras
Review result: Ready with Issues
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 wait for direction from your
document shepherd or AD before posting a ne
Dear Matt,
Thank you for your review!
We added QUIC to the draft during one of the BMWG sessions based on
suggestions from the attendees. The authors are a bit unsure how to fix
the draft that's up for approval so that it would be precise and fully
compliant with QUIC environments.
Do you
Hi Carsten,
I don't have a good answer unfortunately. In my opinion the mentions of
QUIC and HTTP/3 don't add a lot, and feel a bit bolted on so to speak. This
is of course understandable given the relatively recent standardization of
QUIC itself and the lack of testing experience with it and the
IMHO:
Just write down the current status of QUIC: Support and understanding of QUIC
in next-gen security devices is in its infancy, and so are details about the
test procedures in this document. Nevertheless, it is important enough that
it should not be ignored and is included as good as possible
