This was a point of discussion in the REP thread. Originally, I had this as using the SensorDataQoS profile which is unreliable transmission for both pub and sub. It was pointed out to me that as long as the Durability is volatile, the publisher can be marked as reliable and the subscriber can be marked as best-effort so that the subscription can drop the data.