Re: [Tsv-art] ECMP [Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 11 December 2018 22:39 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8091F128BCC; Tue, 11 Dec 2018 14:39:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Dv_EzcpHjk_3; Tue, 11 Dec 2018 14:39:05 -0800 (PST)
Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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 5F17D124D68; Tue, 11 Dec 2018 14:39:05 -0800 (PST)
Received: by mail-pf1-x42e.google.com with SMTP id b7so7826049pfi.8; Tue, 11 Dec 2018 14:39:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=S/JHE4u1MczeAhG5aBu71/3AlxvbLentof7IL7N0tAQ=; b=tKJS/icgVoDDPmG8c92Sh0fQswsK6PuL5O2Xa6UiEPUgyTY8WVQ8CrQXW9PvWFQgI+ NGWeeUmPIqZX1bAXheBMNDR4oTR/5ba3S4zkF84yXeBiOk4BwV6jpBvRle6RGEJi1Ryf IyzC8uoqtBPIRWifuEt/Fmef75E8X5MTLz+Ogb1jrO3QHqfT83fqX7TqMSYVY+4wixoC tlXeQ7P5AELurt35Y2mv5u//hHj8OrDPGEayk61kcJxYsCJ5DxDTwsVdnXKOqKzxexX/ ofvU6mwGY6lzTeTW45aXiyk9cvuejYyBxxNuBAMeICaSV4uOz9Q7O5F7qyQ0o+kwdQtd Wtdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=S/JHE4u1MczeAhG5aBu71/3AlxvbLentof7IL7N0tAQ=; b=uTggJy2P7Td/R/M7F4k65NCviqs5QhotjlSKn3d/+38a0TGQcqLULIz/ASW9JZ2R0D v3avkKV68+Hc5BxEedsItGbunBs7b4V8DVKzCrw9O+P8AGUEzWo33DTcThdu38KzG8mA YPcA8JpzsfVSsEY/d2Kt9mtx29VNA12sFIoW/bYtNWz9/APq2hv1KPbo36ds3kH+omG9 Nh3WvyAgX9Nh/ZduNRSkvxmotQjjG2dnHxP8b+TSYPepx/l56oXGYrnSpmWPV1qv6/aw pnEotb35AXinYIxvEos71y0Jd5EZ1ayfvNtulr59jRJdLYOy+Tm3lL+UO7HHvv0FzKXG 5cnQ==
X-Gm-Message-State: AA+aEWbl9shSlDcC8Ds/TGvikpgPk5Z61seJqqG7zFu1BJCPogJIOifA OzCQfDttnFa9IDQkp5MG+Xcz3KroPM4=
X-Google-Smtp-Source: AFSGD/Vs4g8TW1xaDFEVuZ5hU/shOovpC5HdfPZBRttGrnAYSDy31z0vISn2PXTxcUfyHt3OoO2Nlg==
X-Received: by 2002:a63:2d46:: with SMTP id t67mr16636700pgt.140.1544567944740; Tue, 11 Dec 2018 14:39:04 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id i193sm27869016pgc.22.2018.12.11.14.39.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Dec 2018 14:39:03 -0800 (PST)
To: Wes Hardaker <wjhns1@hardakers.net>
Cc: Nick Hilliard <nick@foobar.org>, tsv-art <tsv-art@ietf.org>, OPSEC <opsec@ietf.org>, draft-ietf-opsec-ipv6-eh-filtering.all@ietf.org
References: <CAL9jLaYHVdHr+rVoWeNtXTXgLxbTaX8V9gn3424tvsLW60Kvow@mail.gmail.com> <5E70C208-0B31-4333-BB8C-4D45E678E878@isc.org> <CAN-Dau0go6_Puf0A9e7KBpk0ApJBUvcxYtezxnwNc-8pKJ3PwQ@mail.gmail.com> <4D69FA8E-FB8A-4A16-9CA6-690D8AE33C9E@strayalpha.com> <20181205122142.GJ1543@Space.Net> <F17C4944-09EC-4AAC-84A0-B660E36AAE89@strayalpha.com> <20181205133821.GL1543@Space.Net> <B6280E0C-6B20-43C1-BB34-170FB06F1EF7@strayalpha.com> <20181205135723.GN1543@Space.Net> <54C715AE-8931-4FA9-AA01-2311EB0055F0@employees.org> <20181205164558.GQ1543@Space.Net> <CCFEFC5B-53AE-4079-B64A-A72A71274FAD@employees.org> <cda0e10e-a56d-4598-dcd4-eabeeac52fb0@gmail.com> <a1b478a7-4396-3d9e-0282-c8c66250526c@gmail.com> <f86a07c8-c421-56db-005c-4db3ce4f3fe0@gmail.com> <3744b28c-3a5a-1ce4-9ff7-5374804d332e@gmail.com> <35277330-4743-4690-8ae0-9a9ab7e34f05@foobar.org> <3a182a82-b933-2d9b-52a8-24805717879b@gmail.com> <ybl4lbjsu9a.fsf@w7.hardakers.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d970fa54-f36b-13fd-7442-b301813567fb@gmail.com>
Date: Wed, 12 Dec 2018 11:38:58 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3
MIME-Version: 1.0
In-Reply-To: <ybl4lbjsu9a.fsf@w7.hardakers.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/H73L4O87d8VmFVu4l_Ea6NeCocI>
Subject: Re: [Tsv-art] ECMP [Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06]
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2018 22:39:08 -0000

(Cc:s trimmed)

On 2018-12-12 09:06, Wes Hardaker wrote:
> Brian E Carpenter <brian.e.carpenter@gmail.com>; writes:
> 
>> "By in large, this flow label changing behaviour has been traced to
>> IPv6 supporting CPE/firewalls, which change the flow label between the
>> initial syn and the ack."
>>
>> Broken middleboxes can prevent anything from working properly.
> 
> With my <operator> hat on, we have indeed run into a problem where a
> small (~ 2%) of IPv6 TCP sessions to us were failing due to FlowLabels
> being used in ECMP hashing.  We had to turn off the usage of FlowLabel
> in the hashing because of even a small real world impact to end-users.

It's a shame. Can you characterise those sessions in any way?

(This shouldn't invalidate ECMP/LAG usage as described in RFC6438,
since there it is the operator that sets the flow label.)

   Brian