Reading the current draft, I find one small issue regarding packet
types. The draft mentions in section 2.1 that packet types are defined
in the Version1 specification. Section 3.1.2 correctly warns against
using packet types for heuristics because they may changed in further
version, and section 3.4.1 correctly conditions inspection of Initial
packet to recognizing version 1. However, I am concerned that
middle-boxes might ignore these caveats. Could we add a note somewhere,
maybe in section 2.1, that different versions of QUIC might encode
packet types differently? Indeed, the version 2 draft
(https://datatracker.ietf.org/doc/draft-ietf-quic-v2/) uses different
encodings for the packet types.
-- Christian Huitema
On 1/24/2022 5:49 AM, The IESG wrote:
The IESG has received a request from the QUIC WG (quic) to consider the
following document: - 'Applicability of the QUIC Transport Protocol'
<draft-ietf-quic-applicability-14.txt> as Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@xxxxxxxx mailing lists by 2022-02-07. Exceptionally, comments may
be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.
Abstract
This document discusses the applicability of the QUIC transport
protocol, focusing on caveats impacting application protocol
development and deployment over QUIC. Its intended audience is
designers of application protocol mappings to QUIC, and implementors
of these application protocols.
The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-quic-applicability/
No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@xxxxxxxx
https://www.ietf.org/mailman/listinfo/ietf-announce
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
