IETF Logo Mail Archive

Re: TCP behavior across WiFi pointers ?

Michael Welzl <michawe@ifi.uio.no> Wed, 08 November 2017 18:33 UTC

Return-Path: <michawe@ifi.uio.no>
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 39CB7129ABD; Wed, 8 Nov 2017 10:33:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ESKaAZd3D6jm; Wed, 8 Nov 2017 10:33:07 -0800 (PST)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF58B129AAD; Wed, 8 Nov 2017 10:32:49 -0800 (PST)
Received: from mail-mx04.uio.no ([129.240.10.25]) by mail-out02.uio.no with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1eCV9c-0005aO-0n; Wed, 08 Nov 2017 19:32:48 +0100
Received: from 93-58-133-64.ip158.fastwebnet.it ([93.58.133.64] helo=[10.0.0.6]) by mail-mx04.uio.no with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) user michawe (Exim 4.82_1-5b7a7c0-XX) (envelope-from <michawe@ifi.uio.no>) id 1eCV9b-0003lR-GV; Wed, 08 Nov 2017 19:32:47 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: TCP behavior across WiFi pointers ?
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <20171108174247.GM19390@faui40p.informatik.uni-erlangen.de>
Date: Wed, 08 Nov 2017 19:32:47 +0100
Cc: tsv-area@ietf.org, iccrg@irtf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A69003DC-9573-4139-BAB1-3C2289565D87@ifi.uio.no>
References: <20171108174247.GM19390@faui40p.informatik.uni-erlangen.de>
To: Toerless Eckert <tte+ietf@cs.fau.de>
X-Mailer: Apple Mail (2.3273)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx04.uio.no: 93.58.133.64 is neither permitted nor denied by domain of ifi.uio.no) client-ip=93.58.133.64; envelope-from=michawe@ifi.uio.no; helo=[10.0.0.6];
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, AWL=0.043, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 21BAF2EF7BF26A53AD3613DAC7D1F9C1179A4BA2
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/-9E3Z7HdA4WTPr9jZTAoDo7NmwQ>
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, 08 Nov 2017 18:33:10 -0000

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
>

v2.23.0 | Report a Bug | By Email