Re: [v6ops] draft-pauly-v6ops-happy-eyeballs-update-01

Philip Homburg <pch-v6ops-7@u-1.phicoh.com> Thu, 30 March 2017 09:29 UTC

Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88C14129413 for <v6ops@ietfa.amsl.com>; Thu, 30 Mar 2017 02:29:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 s2Ys6KBbNZx4 for <v6ops@ietfa.amsl.com>; Thu, 30 Mar 2017 02:29:21 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 0515E126C89 for <v6ops@ietf.org>; Thu, 30 Mar 2017 02:29:19 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1ctWOM-0000IOC; Thu, 30 Mar 2017 11:29:18 +0200
Message-Id: <m1ctWOM-0000IOC@stereo.hq.phicoh.net>
To: v6ops@ietf.org
From: Philip Homburg <pch-v6ops-7@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <CAD6AjGSxKftRXGfJ67rYN6Ccr961HMuU69Y=SSwnemvmsqddNQ@mail.gmail.com> <34A0BBC1-E9C9-4856-BBB5-F6A2B9F4C72F@consulintel.es> <alpine.DEB.2.02.1703300845190.30226@uplift.swm.pp.se>
In-reply-to: Your message of "Thu, 30 Mar 2017 08:59:44 +0200 (CEST) ." <alpine.DEB.2.02.1703300845190.30226@uplift.swm.pp.se>
Date: Thu, 30 Mar 2017 11:29:17 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/b9IWZEUchM_8Rx5qlBP1kUYp-Ck>
Subject: Re: [v6ops] draft-pauly-v6ops-happy-eyeballs-update-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 30 Mar 2017 09:29:24 -0000

>I agree with both Lorenzo and Jordi here, there are multiple problems that 
>won't get fixed, having "hard" failures doesn't seem to help that much at 
>this time, but with the PMTUD failure mode as well (which might not be 
>discovered until TCP handshake is already done), what about adding 
>additional methods to try?
>
>"normal HE mode with IPv4/IPv6"
>If these fails, let's say 500ms
>"try NAT64 method" (what Lorenzo proposed)
>
>if these succeed but I'm not getting any data (for instance my GET / seems 
>to time out, no data for 5 seconds)
>
>then I try again but with TCP MSS 1200 and PMTU 1280 (I purposely went 
>below MSS 1220, perhaps there is no reason to).

I was very surprised to hear it, but there are already middle boxes close to
the customer edge (or in the CPE) that do MSS clamping for IPv6.

It is hard to quantify, but in IPv4 lots of potential PMTU problems are masked
by MSS clamping. 

Given that on the whole we failed to have PMTU blackhole detection/avoidance
deployed at large on the server side, using MSS clamping will be the most
effective way to deal with this problem.