From: Dave Taht <dave.taht@gmail.com>
To: Tim Higgins <tim@timhiggins.com>
Cc: Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] some review needed
Date: Mon, 13 Apr 2020 16:53:08 -0700 [thread overview]
Message-ID: <CAA93jw7ZEgoTKv=h-v5YHAAseuzUt3a95u5dgEWk4PUZtk+4rw@mail.gmail.com> (raw)
In-Reply-To: <ac74b8de-9842-3a62-5539-6bf1e1c0feca@timhiggins.com>
On Mon, Apr 13, 2020 at 8:00 AM Tim Higgins <tim@timhiggins.com> wrote:
>
>
>
> On 4/12/2020 1:17 PM, Dave Taht wrote:
>
> https://tools.ietf.org/html/draft-ietf-rmcat-wireless-tests-11
>
> I'm more interested in testing with actual APs and STAs than simulators.
Me too! Also, trying to figure out where a standardized test and
testing environment veers from reality too much.
> What are folks using to generate RTP video traffic for testing?
I've only begun to research this subject again. Back in the good ole
days (2002!)
I worked on asterisk and had a ton of rtp tools. Today, all the rtp
information is
encrypted so you can't get at it easily unless you instrument your own server.
There's been some really good webrtc work I've begun to look over -
everything from
janus from meetecho, to jitsi, to BBB, to something juliusz just
whipped up over the weekend.
and I had at one point (2014?) worked on google congestion control for
rmcat and kind of understood how both NADA and scream were supposed to
work.
>
> The spec seems light on expected results for Wi-Fi cases.
>
> 3.2.4, bullet 1: "The end-to-end delay and packet loss ratio experienced by each flow should be within an acceptable range for real-time multimedia applications". And what would those be?
> It also specs no video stats, like dropped frames
I can't say it's that much of an rfc either. I vastly prefer ieee
802.11 specs to ietf's, and
in part, why flent exists, was to actually be able to look hard at
this kind of stuff.
But the place for feedback is on the relevant ietf list, it's just
that sometimes easier to get
the attention of experts, here....
>
>
>
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-04-13 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 17:17 Dave Taht
2020-04-12 18:20 ` Tim Higgins
2020-04-13 23:53 ` Dave Taht [this message]
2020-04-14 14:15 ` Tim Higgins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7ZEgoTKv=h-v5YHAAseuzUt3a95u5dgEWk4PUZtk+4rw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=tim@timhiggins.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox