Hi Chongfeng,
Thank you for your valuable feedback. My response is as follows. 1. RFC7011 does indeed define the traffic flow as the observation object. In our draft, we compare the prefix and AS information carried in BGP Updates against the local RPKI VRP cache to obtain the validation state, which is then made available to the IPFIX collector. We think we focus on valid BGP routes, which correspond to the traffic flows derived from those routes. The BGP POV validation state exported in this draft can serve as a route validity attribute for the corresponding BGP flows. As an operator, I think this can offer better visibility into the security of in-network traffic, helping to prevent route leaks or hijacks. 2. The currently referenced ID 294 is indeed based on the validation field defined in RFC 8097. We have already adopted the suggestions from Jeff on the mailing list (a revised version will be submitted after this Sunday), and are incorporating considerations from RFC 8893 (which enhances RFC 6811). Our focus is on the local validation result between BGP POV and RPKI, which addresses a different scope than ID 294. We also would greatly appreciate further input from the working group for this question. Best Regards Yisong ----邮件原文----发件人：Chongfeng Xie <[email protected]>收件人：Yisong Liu <[email protected]>,opsawg <[email protected]>抄 送: (无)发送时间：2026-03-12 10:19:00主题：Re: [OPSAWG]Fw:New Version Notification for draft-liu-opsawg-ipfix-bgp-pov-00.txtHi Yisong and other co-authors, I have given a review to your draft and have the following questions, 1) As you mentioned, this draft defines a new IPFIX Information Element specifically for monitoring RPKI-based BGP Prefix Origin Validation states. Since IPFIX is used to transmit Traffic Flow information from an Exporting Process to a Collecting Process [RFC7011], so I39d like to know the approach you defined is related to " traffic flow"? If yes, how to define the "traffic flow" in this case? 2) For the purpose you mentioned, why not use the existing “IPFIX Information Element bgpValidityState (Element ID 294, see IANA-IPFIX),"？ The bgpValidityState IE is used to describe the "validity state" of the BGP route correspondent source or destination IP address. What I mean is that PRKI provides the result of BGP Prefix Origin Validation，then the result is carried in bgpValidityState IE for transmission, Is there any problems? Best regards Chongfeng From: Yisong Liu Date: 2026-02-12 17:18 To: opsawg CC: draft-liu-opsawg-ipf Subject: [OPSAWG]Fw:New Version Notification for draft-liu-opsawg-ipfix-bgp-pov-00.txt Dear WG, This draft defines a new IPFIX Information Element specifically for monitoring RPKI-based BGP Prefix Origin Validation states (valid, invalid, not-found). Currently, operators lack standardized ways to collect and observe these critical route validation states across their networks. Our proposal fills this gap, enabling better visibility into potential route hijacking and enhancing network security observability. We believe this work would greatly benefit from the working group39s collective expertise.We would sincerely appreciate your review comments and feedback on the draft. Your insights will be invaluable in helping us refine the technical details and strengthen the proposal for the next revision. Thank you very much for your time and consideration. Best Regards,Yisong Liu ----邮件原文----发件人：internet-drafts <[email protected]>收件人：Taoran Zhou <[email protected]>,Xueyan Song <[email protected]>,Yisong Liu <[email protected]>抄 送: (无)发送时间：2026-02-11 14:12:36主题：New Version Notification for draft-liu-opsawg-ipfix-bgp-pov-00.txtA new version of Internet-Draft draft-liu-opsawg-ipfix-bgp-pov-00.txt has beensuccessfully submitted by Yisong Liu and posted to theIETF repository.Name: draft-liu-opsawg-ipfix-bgp-povRevision: 00Title: Export of BGP Prefix Origin Validation in IP Flow Information Export (IPFIX)Date: 2026-02-10Group: Individual SubmissionPages: 8URL: https://www.ietf.org/archive/id/draft-liu-opsawg-ipfix-bgp-pov-00.txtStatus: https://datatracker.ietf.org/doc/draft-liu-opsawg-ipfix-bgp-pov/HTML: https://www.ietf.org/archive/id/draft-liu-opsawg-ipfix-bgp-pov-00.htmlHTMLized: https://datatracker.ietf.org/doc/html/draft-liu-opsawg-ipfix-bgp-povAbstract: This document defines an IP Flow Information Export (IPFIX) Information Element for monitoring the state of Resource Public Key Infrastructure (RPKI) based BGP Prefix Origin Validation. The Information Element enables network operators to collect and analyze BGP route validation states (valid, invalid, not-found) to facilitate the detection of potential route hijacks improving network observability and security.The IETF SecretariatSubject：New Version Notification for draft-liu-opsawg-ipfix-bgp-pov-00.txtA new version of Internet-Draft draft-liu-opsawg-ipfix-bgp-pov-00.txt has beensuccessfully submitted by Yisong Liu and posted to theIETF repository.Name: draft-liu-opsawg-ipfix-bgp-povRevision: 00Title: Export of BGP Prefix Origin Validation in IP Flow Information Export (IPFIX)Date: 2026-02-10Group: Individual SubmissionPages: 8URL: https://www.ietf.org/archive/id/draft-liu-opsawg-ipfix-bgp-pov-00.txtStatus: https://datatracker.ietf.org/doc/draft-liu-opsawg-ipfix-bgp-pov/HTML: https://www.ietf.org/archive/id/draft-liu-opsawg-ipfix-bgp-pov-00.htmlHTMLized: https://datatracker.ietf.org/doc/html/draft-liu-opsawg-ipfix-bgp-povAbstract: This document defines an IP Flow Information Export (IPFIX) Information Element for monitoring the state of Resource Public Key Infrastructure (RPKI) based BGP Prefix Origin Validation. The Information Element enables network operators to collect and analyze BGP route validation states (valid, invalid, not-found) to facilitate the detection of potential route hijacks improving network observability and security.The IETF Secretariat
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
