Hi Chongfeng, Sorry for the late reply to the email due to my vacation this week. Thank you for your valuable comments. Please find the detailed response below.
Thanks, Changwang 发件人: [email protected] <[email protected]> 发送时间: 2026年5月2日 11:07 收件人: opsawg <[email protected]> 抄送: linchangwang (RD) <[email protected]> 主题: Comments on draft-lin-opsawg-ipfix-sr-policy Hi Changwang, Zhenqiang I have given a review of draft-lin-opsawg-ipfix-sr-policy. It mentions that "These IEs enable Exporting Processes to report which SR policy was applied to each flow, providing crucial visibility into the relationship between traffic and network policies. For IPFix-related draft, Benoit mentioned at IETF 125， “A draft was needed only if it included more than just IPFIX IEs ― such as use case explanations, key or non-key field definitions, or links to document modules.” So to effectively push forward this draft in the future, I suggest that it could be expanded on use cases, including defining what 'flow' means in specific use cases，especially the benefits such an "VISIBILITY" brings to network operations, as well as the shortcomings of other similar solutions." [Changwang] We appreciate the feedback. Use cases will be incorporated into the subsequent revision of this document to illustrate the benefits that the described Information Elements provide to network operators, and to highlight limitations observed in alternative approaches. In addition, there is one sentence in the draft, "For srPolicyEndpointIPv4 and srPolicyEndpointIPv6 IE, A value of 0.0.0.0 for IPv4 address and ::0 for IPv6 address indicates that no SR Policy with an IPv4 or IPv6 endpoint was applied, or the endpoint is unknown.. " I guess "::/0" here should be "::0/128". [Changwang] Yes, ::0 should be changed to ::/128, and it will be modified in the next version. In section 5, it says that, " While SR Policy attributes themselves don't directly identify individuals, they could be combined with other flow data to infer sensitive information about network usage patterns." Do you mean it will bring potential risks? From the perspective of network operations, I think this approach is beneficial. [Changwang] This should be the purpose of defining IEs in this document―to express benefits for network providers, rather than potential risks. 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]
