[Ns-developers] DelayBox - ns-3

[George Riley]

>
>>>>
>>>>
> 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.

George

>
>
> If you still want to make some general classifier (to be used by any
> code which handles a packet) that can classify individual packets, I
> have several questions & concerns about how that should work.
>
>> We also miss some sort of generic system to apply actions on packets
>> which belong to a certain flow. I don't really know what this should
>> look like but, I am sure you could either ignore this part of the
>> problem and provide a DelayBox-only solution for now, or look at
>> existing cisco router configuration APIs to get an idea of what  
>> such a
>> thing would look like.
>
> I'll be working on a DelayBox-only solution for now, where DelayBox is
> an extension of NetDevice.
> I'll be sure to use the current propagation delay and error models.
>
>> I hope that the above answers some of your questions and I look  
>> forward
>> to hear from you.
>> Mathieu
>>
>>