You think about something like flow sampling, correct? From FPC protocol point of view, I don’t see issues with adding such properties. AFAIK there is even some support from data plane nodes, so enforcement of these properties should work.
Now, I understand you’re requesting control on which traffic should be probed. In that case a new property should be added. The associated attribute should then also indicate how often packets should be probed (Every 1min, ever 1000th packet, whatever). Since the forwarding of the copy packet is different than for the actual data packet, the probe property should also indicate a destination, where the copy should be sent to. That’s the protocol part and it should be feasible if wanted. Is it the C-Plane function that is aware of policies for packet probes? To exploit such extension, it should be, otherwise the probe configuration may be accomplished via a different interface. Thanks, Marco From: Lyle Bertz [mailto:lyleb551...@gmail.com] Sent: Dienstag, 6. Oktober 2015 17:38 To: draft-ietf-dmm-fpc-c...@ietf.org; dmm@ietf.org Subject: Copying Traffic in FPC When looking at the latest draft I was curious about how copying for the purpose of troubleshooting / probes would be supported? My thought would be some sort of property on a port that copies the traffic and notes the PRT that it could be forwarded to. Could we support this use case (I am not married to the suggestion above) in the specification given its importance to trouble management? This is easy enough to support in underlying DPN technologies such as SDN and I see no reason to not specify it in FPC and avoid using yet another protocol for forwarding. Comments / Thoughts would be appreciated on this matter. Thank you. Lyle
_______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
