IETF Logo Mail Archive

Re: [iccrg] TCP behavior across WiFi pointers ?

Marie-Jose Montpetit <marie@mjmontpetit.com> Wed, 08 November 2017 18:37 UTC

Return-Path: <marie@mjmontpetit.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 2DA72129AD5 for <tsv-area@ietfa.amsl.com>; Wed, 8 Nov 2017 10:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mjmontpetit-com.20150623.gappssmtp.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 KaDJ5TvlY9zc for <tsv-area@ietfa.amsl.com>; Wed, 8 Nov 2017 10:37:39 -0800 (PST)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 90114129AC5 for <tsv-area@ietf.org>; Wed, 8 Nov 2017 10:37:39 -0800 (PST)
Received: by mail-it0-x230.google.com with SMTP id p138so8041584itp.2 for <tsv-area@ietf.org>; Wed, 08 Nov 2017 10:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mjmontpetit-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nWEu4s74hjAHpYEPQC9fp5kKJ3jEGDFL0SKNFiwcMZ0=; b=psicQKWTv3Y3rLgZ7gLfjEuCfRTzRzZ2AVfgVxbCuLb0tGGVHl1qtK1tbn1oM2lxel R/GcrOXhCjbP3wFdFqQTZz57ZB/2Ai9HWR0vBe13SzUGo270tbljNDm1K5npElV/G/Ph Iv4j6wbkLFOpLEJMs1mpTvZ6Tc7uk8MpoEi7y6vE23hvSU4MhtTYX8MGKx19La46tgyl xPwJdNupGYWBxBILHrz8bwIb8dyJnVMx0mxptbDlNyJEU3TW4+HwlICT9Hf8gCPT2Hs6 Ehwa7v38b3QUd4ovPQWpcfC6qfMADHIR2QSqdKUOIVXLg6nFT9IdzX5fs8/zVycXsbKI wxNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=nWEu4s74hjAHpYEPQC9fp5kKJ3jEGDFL0SKNFiwcMZ0=; b=WCN6r9LnwY3ZMTM0PNAvnHPbotu8MTV7nDPZEMnzgvH4qP/dPV5srb2rhZvThTILEB EwRoiVdK1K/2pze8qWLVVpu0TKPsce5ht4auMlMDL/AyYFh649XJnxEBOmkGtBCFItHV 8lUsoRKkNYQO+zkATyPuzcJwDXKppA/1JqhUoJs7qLBiws7QqsTAbo6HiS7OR1Agv2d4 g/iRDDLCznwEMxAnIvkkicM8nKAflE5e2hOBE2zSqLywYldg7tOwGB7T8qcUa1H2a3nG thw6XVSKm+koyq+E1ExpqZR984PbKFzo+GoE+8HKV9tVAcXWUMGstd/pG5Y9b47gNEFN lULw==
X-Gm-Message-State: AJaThX6nGXoQT362w03Bq23oA7DooWBjKgWuJ7s9K577mUPrQ9kFaO5L vPs1UaY6jAO6vcor2NuC7dfgzXTO9hg=
X-Google-Smtp-Source: ABhQp+RQRtP2v8bQO7Be6+iweaKU6XlAlo/NpJejV5CkFwE239MjxeP3JlgUwUSWY4GidVZ7jgJPaw==
X-Received: by 10.36.82.204 with SMTP id d195mr1909365itb.23.1510166258748; Wed, 08 Nov 2017 10:37:38 -0800 (PST)
Received: from [10.189.108.71] ([192.54.222.28]) by smtp.gmail.com with ESMTPSA id s129sm2515442itb.22.2017.11.08.10.37.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 08 Nov 2017 10:37:38 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [iccrg] TCP behavior across WiFi pointers ?
From: Marie-Jose Montpetit <marie@mjmontpetit.com>
In-Reply-To: <A69003DC-9573-4139-BAB1-3C2289565D87@ifi.uio.no>
Date: Wed, 08 Nov 2017 13:37:37 -0500
Cc: Toerless Eckert <tte+ietf@cs.fau.de>, iccrg IRTF list <iccrg@irtf.org>, tsv-area@ietf.org, nwcrg@irtf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F98AEC5-9313-437C-8E7B-246BB2238A8C@mjmontpetit.com>
References: <20171108174247.GM19390@faui40p.informatik.uni-erlangen.de> <A69003DC-9573-4139-BAB1-3C2289565D87@ifi.uio.no>
To: Michael Welzl <michawe@ifi.uio.no>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-area/hv1zOe4W48SBDStBBC5eBCqwLtQ>
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:37:42 -0000

I also copy the nwcrg list where a ton of people have looked at TCP over wifi.

mjm
> On Nov 8, 2017, at 1:32 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

v2.23.0 | Report a Bug | By Email