Re: [v6ops] PMTUD issue discussion

joel jaeggli <joelja@bogus.com> Mon, 01 September 2014 16:35 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D621A041C for <v6ops@ietfa.amsl.com>; Mon, 1 Sep 2014 09:35:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level:
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.668] autolearn=ham
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 qRLS9c4TEosf for <v6ops@ietfa.amsl.com>; Mon, 1 Sep 2014 09:35:29 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72CF11A035E for <v6ops@ietf.org>; Mon, 1 Sep 2014 09:35:29 -0700 (PDT)
Received: from mb-aye.local (c-67-188-0-113.hsd1.ca.comcast.net [67.188.0.113]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s81GZHrs004907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 1 Sep 2014 16:35:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <5404A041.4070203@bogus.com>
Date: Mon, 01 Sep 2014 09:35:13 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Thunderbird/32.0
MIME-Version: 1.0
To: Andrew 👽 Yourtchenko <ayourtch@gmail.com>
References: <0D370E74-688B-4EB3-A691-309A03AF20BA@cisco.com> <53FBA174.2040302@isi.edu> <53FBA6E1.90905@bogus.com> <CAPi140PMeM9omtm11+NHa2ywUfof_tE7HknKExtoEb32mm7L_w@mail.gmail.com>
In-Reply-To: <CAPi140PMeM9omtm11+NHa2ywUfof_tE7HknKExtoEb32mm7L_w@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="w5gHftNF9d1nINQprPO12pNb35CKUIpI0"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Mon, 01 Sep 2014 16:35:17 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/bVyX-PBeENUINCWxsrwC7NXWA8s
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] PMTUD issue discussion
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2014 16:35:34 -0000

I think this is worthwhile and I will work to incorporate the observation.

On 8/26/14 2:50 AM, Andrew 👽  Yourtchenko wrote:
> Joel,
> 
> On 8/25/14, joel jaeggli <joelja@bogus.com> wrote:
>> On 8/25/14 1:49 PM, Joe Touch wrote:
>>> Hi, all,
>>>
>>> Speaking from TCPM-land, I would observe the following:
>>>
>>> - PMTUD already has many known problems, which is why PLMTUD is
>>> recommended instead
>>
>> I agree, operationally however I'm trying not to break existing devices
>> attempting to connect to me, is the motivation for the note.
>>
> 
> During the presentation in the v6ops session I made a comment about
> sysctl net.ipv4.tcp_mtu_probing. Since then I had a chance to test it
> - and indeed, it affects the behavior of TCP over IPv6 as well.
> 
> However, the value of 1 causes a large value of MSS to be used,
> resulting in about 1.5 second hiccup. So, yeah it "works" but for
> barely acceptable values of "works"
> 
> Setting the value to 2 causes the initial MSS to be 512, which
> "mitigates" the problem and avoided the hiccups on a 100kb file I was
> testing with - at the expense of almost 3x more packets of course.
> 
> I think it would be useful to see the discussion of this measure and
> its applicability/tradeoffs in the draft.
> 
> --a
>