Re: TCP behavior across WiFi pointers ?

Aaron Falk <aaron.falk@gmail.com> Wed, 29 November 2017 15:17 UTC

Return-Path: <aaron.falk@gmail.com>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F12A124B18 for <tsv-area@ietfa.amsl.com>; Wed, 29 Nov 2017 07:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zo800A8Us-aD for <tsv-area@ietfa.amsl.com>; Wed, 29 Nov 2017 07:17:49 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45B9A1275C5 for <tsv-area@ietf.org>; Wed, 29 Nov 2017 07:17:49 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id t8so6974771wmc.3 for <tsv-area@ietf.org>; Wed, 29 Nov 2017 07:17:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/v8JQ+cDlxP1A0SQgSkgrEqFtLbZwUIzp5zXCF+Qjuo=; b=VMvjDHmPnEiP6cfT6/X3wpCPdKSNvqJ5vUwN9dRbtHXfu+gHGx4goFhlYxWJg8c5RC Z+khQY3RgY8odhiROaZ3gprcfkYrPUwGfaSm5d7BPu7rFqHw+nGe/TOiDrUDL1+ugaiD X16TTr8xODJtIbqr3p+3BHGWluj7Qw2NyG7apDHJ336EVEZSDQVJ/pg+dzeVRnMOt1Bq HE24HJ0YMZrne/naBrXEEH4mLpslmVv9t8uC+9as3/ep4aGeynZcz8mk1jEsqS365EaV xcnUwBz/ge4vwdFDYtakD1X8m7SIS2PIrjjMWsLMYELWM767nMQBeJPSnv4JIiPEC6PH 6SHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/v8JQ+cDlxP1A0SQgSkgrEqFtLbZwUIzp5zXCF+Qjuo=; b=Vb5DqMAYwlGy4KLf3FFvnfMP895H83eiK8/CLgTxjp7M0Nx7YQTtsrfauen+mWSIF/ 2hmwwuqjxkcg2vdBh3nJ0YNYSsjg6TFRHRxWQTTlvYVEucszziliEU8Zj2S6lYSl+USz CWNgNIVkQJ3n4GU6Xiunu6wjL4WfaYhsYAJt96mFfanW5R1IswsO7z0wz13dv7W/KmAD eF2MvZq/fHluE3NHWaMaIp05yzDqUGYWi5zIJHre95+DMF/rEnhH+khRiUg4BxTTdT2x hdWIZGPyIxkFyVlZqnWh7zAjxI54YIW5vc5rtLoE8ip3D/+QRBfxeGDmVkb6oUI/3WT0 v3kw==
X-Gm-Message-State: AJaThX6we3IHlcKuR0+I0Z8RLenJM1zNJv9ejQdYMvGFeml47VuP0Xlx yEDtP3ppdHqqwf6B6YHOUGdjlV08YwGQcoJynSc=
X-Google-Smtp-Source: AGs4zMbKYZpn/0SmrLOVrFoj7DG3pFzBjpfDMxWbg5JctBJOH9/kSztGKqCG1yqujoU8hLk28IznFEMBHdwX1g1+YBY=
X-Received: by 10.80.180.18 with SMTP id b18mr8308213edh.136.1511968666765; Wed, 29 Nov 2017 07:17:46 -0800 (PST)
MIME-Version: 1.0
References: <20171108174247.GM19390@faui40p.informatik.uni-erlangen.de> <A69003DC-9573-4139-BAB1-3C2289565D87@ifi.uio.no>
In-Reply-To: <A69003DC-9573-4139-BAB1-3C2289565D87@ifi.uio.no>
From: Aaron Falk <aaron.falk@gmail.com>
Date: Wed, 29 Nov 2017 15:17:35 +0000
Message-ID: <CAD62q9U91daDSTb2v2df_17iO+1vTCegTqd0Da5qPgMQDw4bPw@mail.gmail.com>
Subject: Re: TCP behavior across WiFi pointers ?
To: Mark Allman <mallman@icir.org>
Cc: Toerless Eckert <tte+ietf@cs.fau.de>, Michael Welzl <michawe@ifi.uio.no>, iccrg@irtf.org, tsv-area@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c1b58c64b4fca055f20a336"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/Cz7CwO0HjdKdpncjARslV9etPzo>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Nov 2017 15:17:50 -0000

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