Re: [tcpm] Exceeding value in MSS option?

Frode Kileng <frodek@tele.no> Fri, 23 October 2020 08:37 UTC

Return-Path: <frodek@tele.no>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD3F3A0A62 for <tcpm@ietfa.amsl.com>; Fri, 23 Oct 2020 01:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level:
X-Spam-Status: No, score=-2.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.247, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tele.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 UlCZmZpLyNVW for <tcpm@ietfa.amsl.com>; Fri, 23 Oct 2020 01:37:51 -0700 (PDT)
Received: from gorgon.tele.no (gorgon.tele.no [IPv6:2001:700:800::70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B6813A0A60 for <tcpm@ietf.org>; Fri, 23 Oct 2020 01:37:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tele.no; s=20180731; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:References:Cc:To:Subject:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Dtskecs7WRfazdceonoE64BPAZrj8g4QBNkg0QSzN3M=; b=b5Rm2IyHad9v7bBV2JopoVSKFw 8QDE5JyssaBykBP4kd8Zw1vdoTu85Nejz0/Ka6wEONdlds307WEEsLGJxN4WZ7Yhbu2GhYRXVH3Jc qRpj2GUNitxST3EqTsBG79GKGioXoVBn145sMlQIgj90GFlhHxVs/Q7r0MtdaEpBHcgAWfXrwxR9D JiXU2GQSrER1+LvxHJBp9Lc6fugMByidAnLi8gVl/mvYB77q177KUBXIx4oQkvDRCgl/FU1QQYd6u 0MV6WJlaB7byrCnV0mP2iHE4tywPlf4NnO82VLcDxzjqodJ3cSDLJ9DTJG98PTpHaqXhMo9auVlws hCapMNfQ==;
Received: from pilt2.tele.no ([2001:700:800::21] helo=[IPv6:::1]) by gorgon.tele.no with esmtp (Exim 4.92) (envelope-from <frodek@tele.no>) id 1kVsa0-00006m-Vm; Fri, 23 Oct 2020 10:37:45 +0200
From: Frode Kileng <frodek@tele.no>
To: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
References: <BB0640E4-C7A9-4E1C-9F29-BD373A220BAB@ericsson.com> <247D753D-DA2C-47EF-9C38-C2B5E274FD8F@erg.abdn.ac.uk>
Message-ID: <f3ca83de-6962-56c4-e1d2-839bf074dbca@tele.no>
Date: Fri, 23 Oct 2020 10:37:44 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1
MIME-Version: 1.0
In-Reply-To: <247D753D-DA2C-47EF-9C38-C2B5E274FD8F@erg.abdn.ac.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/3IR-br2EJH6RhKHNE-9BC2a9xjk>
Subject: Re: [tcpm] Exceeding value in MSS option?
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 08:37:55 -0000

Hi,

please see below

On 20 Oct 2020, at 13:56, Mirja Kuehlewind 
<mirja.kuehlewind@ericsson.com> wrote:
> Hi Martin, hi Gorry,
>
> I think Gorry’s paper does indicate that at least for MSS, there are 
> middleboxes that add this option. However, I don’t think there is 
> evidence that there is a general problem about middlebox adding option 
> (rather than removing them). I also reviewed the draft in tsv-art 
> review and given that they say it’s actually not recommended and 
> should only be done with care, I thought that text is okay. However, I 
> guess there is room to improve the wording and explain a bit better, 
> when and if this might be consider or not.
>
Although maybe not  a "general problem",  a study of MSS middlebox 
manipluation in  23 European and Asian mobile networks did reveal some 
issues:

- 20 of 23 networks always inserts MSS. Value for IPv4 varies from 1360 
to 1420 and the value typically seems to reflect  vendor defaults

- The 3 network that didn't clamp MSS do reduce an end-point specified 
values  if it's higher than some network specific threshold

- 2 Networks overrode a end-point specified lower MSS value and changed 
it to the higher network specific default! I.e. a potential source of 
problems.

- 1 Network did not clamp if some other TCP options was used (MPTCP, 
TFO, etc)! Also a source of problems.

I'm afraid that the results from this study has not been published.


Best regards

Frode Kileng