Hi Chongfeng Sorry, the previous email was mistakenly filtered. Thank you for the detailed and insightful review and comments. Please see my detailed responses below.
Thanks, Changwang 发件人: [email protected] <[email protected]> 发送时间: 2025年11月26日 9:55 收件人: linchangwang (RD) <[email protected]> 抄送: opsawg <[email protected]> 主题: Comments on draft-lin-opsawg-ipfix-quic-header 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? Changwang> It's the same. Thanks, we will add some text descriptions in the next version. 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? Changwang> According to RFC 9000, "a 0-RTT packet is used to carry 'early' data from the client to the server as part of the first flight, prior to handshake completion," and a 0-RTT packet uses a long header. This indicates that service data flow may occur during connection establishment. 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? Changwang> Thanks, the description will be added in the next version. 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? Changwang> It is necessary to define "quicSourceConnectionID", which refers to the "Source Connection ID field in this packet". It must be used in long header packets. I'd like to know whether you can give your feedback? Best regards Chongfeng ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
