[Ns-developers] DelayBox - ns-3
Mathieu Lacage
mathieu.lacage at sophia.inria.fr
Mon Apr 7 09:18:34 PDT 2008
On Mon, 2008-04-07 at 09:42 -0400, George Riley wrote:
> >
> >>>>
> >>>>
> > connection basis. Since this is the case, it seems that the most
> > logical thing to do would be to add functionality to the TCP Socket
> > code. This added functionality would allow the code using the socket
> > to assign a flowid to that socket. The socket would then assign its
> > flowid to each packet that it generates.
> Yes, i agree; I will add a way to individually tag a flow with a flow
> identifier.
> This is quite useful in debugging and performance analysis.
While, it is certainly possible to add this at the socket layer in each
socket implementation, it is also possible to add the flowid tagging
outside of that layer and leave this decision to the user. I think that
the latter would make this functionality more useful since it would be
re-usable across various types of sockets and, even potentially without
sockets to tag other kinds of traffic for other kinds of purposes.
i.e., for example, I might want to tag the traffic generated by a
certain application with a wifi AC_VO category tag to ensure that it is
sent over the wireless network with a certain QoS. The only difference
here is the type and content of the tag I want to attach to the traffic
so, the only thing you need to be able to do this is to delegate the
tagging to the user in a trace sink (or some other mechanism).
regards,
Mathieu
More information about the Ns-developers
mailing list