> On Sep 26, 2017, at 7:17 PM, Dave Täht <notificati...@github.com> wrote:
> 
> with a seqno it might also be possible to see ooo packets.

It will be there. Since they’re in seqno order in the JSON, any processing to 
measure OOO will have to look at the arrival timestamps.

I’ve got on the list to add a simple OOO metric- the number of arriving packets 
with smaller seqnos than the one that arrived before it. Ah, just noticed RFC 
4737, likely to shred me up some more.

> To really complexify your (our) life at one point, I've been dying for a
> decent videoconferencing emulation. Typical behaviors are a burst on a
> keyframe, a long sparser string of updates to that keyframe, and
> bandwidth probing behavior.
> 
> And yes, there is a working group (rmcat), and RFCs and papers on it
> (the google congestion control one is pretty good, scream is also worth
> reading) BUT: Don't listen to me on this, just keep coding.....

Oh boy. One of the things I toyed with but ix-nayed early on was adding a 
Scheduler interface that could schedule the send time and packet sizes, where 
the isochronous one would be the default. There were a host of questions that 
came up with that, so I put the piton in the rock, as it were.

The next questions become, can the server no longer be dumb and have 
independent send schedules from the client? Can we record measurements on both 
sides? Now you’re writing a generic traffic simulator, which I probably don’t 
want IRTT to become. Plus, IPDV, with what information I have available to me, 
is best measured with constant size packets. (Maybe even constant interval 
packets? Not sure about that though.)

I may be open to it later as a different project. My intuition is to limit the 
scope of this one and make it bulletproof first, if that is possible!



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/106#issuecomment-332301189
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org

Reply via email to