Differentiating garbage/zero paddings in the datagram vs actual invalid packet headers

[errorxyz]

As per quicwg/base-drafts#3333 we can have garbage/zeroes padded to the UDP datagram for INITIAL packets to maintain the MTU size. We also have #332 to handle this. But how do we differentiate if we've received a malformed packet header v/s a garbage/zero paddings which we should ignore? aioquic currently logs an error in both cases.

My usecase is currently to parse fragmented QUIC client hellos for mitmproxy. (mitmproxy/mitmproxy#7869)

Thank you for maintaining this wonderful project :)