Hi Changwang，
Thank you for writing draft-lin-opsawg-ipfix-quic-header. I have given a review to it and have the following questions, 1) The first quesiton is about the meaning of 'flow', this draft defines new IPFIX Information Elements to identify a set of QUIC related information, it uses the term of 'flow', QUIC (RFC9000) and IPFIX also uses the term of "flow", are the meanings of 'flow' in QUIC, IPFIX and your draft the same? 2) In section 4, it illustrates how to represent a QUIC flow in two different cases, for Short Header Packet and long header packet, but the packets with a long header is used during connection establishment, I guess there is no service flow in this case. Is it necessary to represent a flow in this case? 3) Also in section 4, it says "How many packets are forwarded or dropped using QUIC in a network? If dropped, for which reasons?", I think this has also been discussed by draft-ietf-opsawg-discardmodel and draft-evans-opsawg-ipfix-discard-class-ie. Is it better to mention them in your draft? 4) In this draft, new IE of "quicSourceConnectionID" is defined to represent "Source connection ID", it is known that in QUIC client uses the Source Connection ID supplied by the server as the Destination Connection ID , which is used to provide routing, this means the "Source connection ID" has changed to "Destination connection ID", do we need to define such an IE? I'd like to know whether you can give your feedback? Best regards Chongfeng
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
