Hi Lijie, Yes, it is common for operators to carry multiple services with different policies over links.
That text is for the use cases that an operator would like to measure the packets for the paths(identified by its segment list) within its Policy. But on the egress node, the node will get the aggregated statistics of packets since different services may reuse the same segment list/path. In the cases that operator would like to measure the paths in different policies/services, same segment list/path in a specific policy should be identified, and differentiated with the same segment list in other policies. By using different Path Segment ID, same segment List/path can be differentiated, so that the traffic can be measured alone. Otherwise, only the aggregated result will be produced on the egress node. Hope I make it clear. Thank you for your comment. We may need to add some text in this section? You are welcome to share your proposal. Thanks, Cheng From: LiJie Deng <denglijie1...@gmail.com> Sent: Thursday, September 5, 2024 11:08 AM To: spring@ietf.org Subject: [spring] Re: spring Digest, Vol 129, Issue 43 Hi Cheng, I have a question about the draft. There is this sentence in the "introduction" section: "Furthermore, different SRv6 policies may use the same segment list for different candidate paths, so the traffic of different SRv6 policies are merged, resulting in the inability to measure the performance of the specific path." - I don’t see the issue with "merged traffic of different SRv6 policies", and how it relates to "the inability to measure the performance of the specific path". For operators, it’s very common to carry multiple services with different policies over links. In addition, there are many methods to measure service performance, such as IOAM. BR, Lijie
_______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
