Bugzilla – Bug 2241
Setting type of service in applications such that Wi-Fi QoS can read it
Last modified: 2016-07-14 15:09:02 EDT
In ns-3-dev, we do not have a way to express class of service at the application layer so that packets are prioritized in the Wi-Fi layer.
This is a proposal for how to pass PIEEE802.1p class of service value from IP layer (IPv4 only right now) to Wi-Fi so that Wi-Fi access category can be set without Wi-Fi having to peek at the IP header (Wi-Fi does not have an internet module dependency).
More details in the code review (suggest to gather comments there):
Another way to implement this:
Tom, what is the status of this?
I think you had the intention to include those changes in ns-3.25.
(In reply to sebastien.deronne from comment #2)
> Tom, what is the status of this?
> I think you had the intention to include those changes in ns-3.25.
I was waiting for the traffic control work to settle, as it has some bearing on the resolution of this.
I also was waiting for any more feedback about the desired approach; I implemented two alternatives:
1) PacketTag (which I would argue to replace Wifi QosTag with this new tag)
2) object aggregation to expose a special class-of-service-aware interface
The sentiment expressed, in discussion of the second approach, was that the second approach could be adapted to the traffic control layer once that is merged.
Any opinions against trying to adapt 2) for traffic control layer?
We should take actions here to have this included in ns-3.26.
Pushed by Stefano.