Hello everyone.
It would great to have route marking on connection level. Internally RoS acting as Linux and have marks for connections and packets. But in RoS only packet mark divided by two bitfields, one represents for us as "route-mark" and the second one as "packet-mark" and both of it affected to packets. I want to have the same thing on the connection level. One field corresponding to a route-mark and second one to a packet-mark. And I want to have a function to copy values from a connection to packet mark and vice versa.

You mean to stick routing mark to connection mark, to save rules that assign routing marks based on connection marks? It does sound useful, but if I understand it correctly, you'd need to have packet-based routing marks and then different connection-based routing marks, which could be a little "confusing" (it's not the best word, maybe complicated, i.e. I'm not sure if the end result would be really simpler).

It is necessary for complex traffic routing and QoS same time. Just imagine, you need to track traffic routes and QoS marks and you have just one connection mark. If I could copy route and QoS information from connection mark it is cut off tons of silly rules, without that I have to compare one connection mark with all combination of my ISP route and QoS types just for set route mark on a packet or change DCSP mark. For example, I have 7 ISP and 12 QoS types which divided to 8 queues, and finally, I construct connection mark like ISP2-EF (for second ISP and VoIP traffic). It forces me to have around 1000 rules to workaround "single connection mark", but when I had use Linux box for routing purpose I have around 200 rules for the same situation.