Re: [v6ops] PMTUD issue discussion

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 26 August 2014 14:59 UTC

Return-Path: <Fred.L.Templin@boeing.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 D704C1A86EC for <v6ops@ietfa.amsl.com>; Tue, 26 Aug 2014 07:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.569
X-Spam-Level:
X-Spam-Status: No, score=-4.569 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] 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 70KbLADMbXcU for <v6ops@ietfa.amsl.com>; Tue, 26 Aug 2014 07:59:45 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B71081A86E2 for <v6ops@ietf.org>; Tue, 26 Aug 2014 07:59:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s7QExiVO004502; Tue, 26 Aug 2014 09:59:45 -0500
Received: from XCH-PHX-213.sw.nos.boeing.com (xch-phx-213.sw.nos.boeing.com [130.247.25.142]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s7QExIDL003987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 26 Aug 2014 09:59:38 -0500
Received: from XCH-BLV-102.nw.nos.boeing.com (2002:82f7:1975::82f7:1975) by XCH-PHX-213.sw.nos.boeing.com (2002:82f7:198e::82f7:198e) with Microsoft SMTP Server (TLS) id 14.3.181.6; Tue, 26 Aug 2014 07:59:35 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.6]) by XCH-BLV-102.nw.nos.boeing.com ([169.254.2.84]) with mapi id 14.03.0181.006; Tue, 26 Aug 2014 07:59:33 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Andrew 👽 Yourtchenko <ayourtch@gmail.com>, joel jaeggli <joelja@bogus.com>
Thread-Topic: [v6ops] PMTUD issue discussion
Thread-Index: AQHPwRMa3jcR+fTlj0+il5BtQavN3Zvi+baA
Date: Tue, 26 Aug 2014 14:59:32 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832CFC84D@XCH-BLV-504.nw.nos.boeing.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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/YafyTEMfGEHWM0ajU9hxPbXmuAo
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: Tue, 26 Aug 2014 14:59:48 -0000

Hi Andrew,

> -----Original Message-----
> From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Andrew ?? Yourtchenko
> Sent: Tuesday, August 26, 2014 2:50 AM
> To: joel jaeggli
> Cc: IPv6 Ops WG
> Subject: Re: [v6ops] PMTUD issue discussion
> 
> 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.

PTB message loss is also a concern for IPv6, and not just for IPv4.
 
> 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 that implementation was added to the linux kernel a long
time ago, and I am not sure if anyone is still maintaining it. Is
this a problem that should be reported to netdev?

Thanks - Fred
fred.l.templin@boeing.com
 
> I think it would be useful to see the discussion of this measure and
> its applicability/tradeoffs in the draft.
> 
> --a
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops