From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Fwd: Re: [iccrg] TCP behavior across WiFi pointers ?
Date: Thu, 30 Nov 2017 00:04:45 -0800 [thread overview]
Message-ID: <CAA93jw4kcc8xDqXKBKO8JghEHxw8t=RxxY4OYsAEQhK_O5teLg@mail.gmail.com> (raw)
In-Reply-To: <87lgionrl5.fsf@toke.dk>
wow. *median* of 7 interfering APs at 2.4ghz. 10% with more than 29 interferers.
On Wed, Nov 29, 2017 at 11:39 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> The folks over at Meraki had a paper at this year's IMC talking about
> TCP over WiFi.
>
> -Toke
>
>
>
> ---------- Forwarded message ----------
> From: Simon Barber <simon@superduper.net>
> To: Aaron Falk <aaron.falk@gmail.com>
> Cc: Toerless Eckert <tte+ietf@cs.fau.de>, iccrg@irtf.org, tsv-area@ietf.org, Michael Welzl <michawe@ifi.uio.no>, Mark Allman <mallman@icir.org>
> Bcc:
> Date: Wed, 29 Nov 2017 16:41:04 -0800
> Subject: Re: [iccrg] TCP behavior across WiFi pointers ?
> We’ve been doing some studies and work in this area at Meraki.
>
> https://conferences.sigcomm.org/imc/2017/papers/imc17-final203.pdf
>
> Simon
>
>
> On Nov 29, 2017, at 7:17 AM, Aaron Falk <aaron.falk@gmail.com> wrote:
>
> Hey Mark-
>
> Didn't you do some work on TCP over wifi a while ago?
>
> --aaron
>
> On Wed, Nov 8, 2017 at 1:33 PM Michael Welzl <michawe@ifi.uio.no> wrote:
>>
>> I would think that 1) there are probably pointers, and 2) the people who have them should be on the ICCRG list, which I’m cc’ing.
>>
>> I suggest for this to be the last email that includes tsvarea so that the thread entirely moves to ICCRG.
>>
>>
>> > On Nov 8, 2017, at 6:42 PM, Toerless Eckert <tte+ietf@cs.fau.de> wrote:
>> >
>> > Any pointers to work analyzing the differences in behavior when TCP is run
>> > across WiFi as opposed to wired ? Especially with WiFi in the home ?
>> >
>> > I am primarily thinking that there could be a higher demand for
>> > TCP (end-to-end) retransmissions when using WiFi because the L2/WiFi
>> > local retransmissions are insufficient. And if so, what the characteristics
>> > of those end-to-end retransmissions is (would assume they would be larger
>> > than N msec, where N is whatever the L2/wifi protection window is, which
>> > unfortunately i don't know).
>> >
>> > Asking because we've got the poor "must-sit-in-back-of-the-bus" traffic
>> > called IP multicast that is not protected by L2/wifi retransmissions at
>> > all and now we're wondering if carrying it over TCP as a workaround
>> > could help, and therefore trying to educate myself on specific known
>> > issue left when running traffic over TCP over WiFi.
>> >
>> > If any other TSV or other WG mailing list might be a better place to
>> > ask. pls. let me know.
>> >
>> > Thank!
>> > Toerless
>> >
>>
> _______________________________________________
> iccrg mailing list
> iccrg@irtf.org
> https://www.irtf.org/mailman/listinfo/iccrg
>
>
>
> _______________________________________________
> iccrg mailing list
> iccrg@irtf.org
> https://www.irtf.org/mailman/listinfo/iccrg
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2017-11-30 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 7:39 Toke Høiland-Jørgensen
2017-11-30 8:04 ` Dave Taht [this message]
2017-11-30 8:07 ` Dave Taht
2017-11-30 8:21 ` Jonathan Morton
2017-11-30 8:52 ` Toke Høiland-Jørgensen
2017-11-30 22:35 ` Simon Barber
2017-11-30 22:50 ` Toke Høiland-Jørgensen
2017-11-30 22:59 ` Simon Barber
2017-12-01 12:48 ` Toke Høiland-Jørgensen
2017-12-01 14:57 ` Dave Taht
2017-11-30 9:03 ` Sebastian Moeller
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='CAA93jw4kcc8xDqXKBKO8JghEHxw8t=RxxY4OYsAEQhK_O5teLg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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