Re: [tsvwg] L4S and the RACK requirement

Wesley Eddy <wes@mti-systems.com> Sat, 23 February 2019 00:03 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD179130E85 for <tsvwg@ietfa.amsl.com>; Fri, 22 Feb 2019 16:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mti-systems-com.20150623.gappssmtp.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 JtLlXLyZu9yC for <tsvwg@ietfa.amsl.com>; Fri, 22 Feb 2019 16:03:41 -0800 (PST)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 07F8012D4F0 for <tsvwg@ietf.org>; Fri, 22 Feb 2019 16:03:41 -0800 (PST)
Received: by mail-qt1-x82b.google.com with SMTP id j36so4554207qta.7 for <tsvwg@ietf.org>; Fri, 22 Feb 2019 16:03:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=jevImJ6tgkm7KiUdd9vXHxXYQfolCdwUuAiYT1h35kE=; b=QRa29ybbwT5oywdj5Qa8moDWUMJ9Aid03ylCcQySGswJ9CwaaSY8wO5K5qSoAv2cUy Wxuc+mqegiO7aOxgue8+EtRSw7mKy9CUUd24R9fdLKVaukXnE2wybjAChNOEVsB1QBty TdAjoatEEheSNaZw0MgX3dyWZ89+TNOpGJl359NxA8XzBbIc33oKl/ngBLJOJW2xWiyM 0h/w5MJAPUVfAVvU5jDJfsnZ9LO/7hutxdodcAWldZC6Mn7WrMEJ8B21oYe1CaZF8G+L BFMYWWUkvyYEjvS6ru5pulQOxuTA4Hji9VzPW66WqDzW8Hz8pQ/fO+nOIKcwIHefOjg1 gcqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=jevImJ6tgkm7KiUdd9vXHxXYQfolCdwUuAiYT1h35kE=; b=H2hSiVJw2TCH9y6ZfQtwsEodRQUgOy7rD4vvZ31s5+kSr2y4P1Gs9R70RNDSijaOiX PqZfOvv6BYo1QkacKyOc61mbSdG1AKRqqPuGXpUZAHQIdhEJaGqB3ZcCiMYs1WAe46d0 /LNLOqDDqxZAU0qDvkpTxzi8W9hVyprz64pLIkSi/M0OUMp9h4TfPYo4WP/h6kka/B98 1XYzFOLPNn9yga4liOpw9e9X9VJrRd7Yd8JGN81MFOdII4iZZjsEJV/cW3Hb/NbgufVa NOEIDyBzmVg74lK9VXLCI7/EiSUc1zh6zQxDkcXIBYFQc/JLEjTqnhhM/620wbn5akBi pyhQ==
X-Gm-Message-State: AHQUAuYE/0yFO9oUoU+HMVRxYuNGrW3sLTtbk6HZMpvLfy0Vm3HkRgSn dgeS7T+P9/NBxYhmgFFO53U7uXE6/EE=
X-Google-Smtp-Source: AHgI3IYMlutF79/qnz9ooAERA+MukGL/L50geLZ/VPRDOAd5s5S7Ax01qvQFMiRVhPl0jw5OMaNHPQ==
X-Received: by 2002:ac8:3770:: with SMTP id p45mr5268578qtb.275.1550880219359; Fri, 22 Feb 2019 16:03:39 -0800 (PST)
Received: from [192.168.1.14] (user-12l31c7.cable.mindspring.com. [69.81.133.135]) by smtp.gmail.com with ESMTPSA id a133sm1775260qkg.66.2019.02.22.16.03.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Feb 2019 16:03:38 -0800 (PST)
To: lloyd.wood@yahoo.co.uk, Tsvwg IETF List <tsvwg@ietf.org>
References: <fb6d2979-a6a4-b122-a90e-4a0732ee89fa@mti-systems.com> <1316285020.1534460.1550493368197@mail.yahoo.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <a535883e-6812-1ca5-9ce2-c005d534a0ba@mti-systems.com>
Date: Fri, 22 Feb 2019 19:03:36 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <1316285020.1534460.1550493368197@mail.yahoo.com>
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/tsvwg/4jQ9F0CnETI8Zmr2K79mjhoa1zM>
Subject: Re: [tsvwg] L4S and the RACK requirement
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2019 00:03:44 -0000

On 2/18/2019 7:36 AM, lloyd.wood@yahoo.co.uk wrote:
> Am I the only person who remembers Savage attacks from ack splitting 
> and packet counting?
>
> http://cseweb.ucsd.edu/~savage/papers/CCR99.pdf
>
> there's the support for the MUST NOT, at least. I's not the lack of 
> scale that is the major issue there, it's being open to abuse. ack 
> counting didn't work...
>
I think it's only sort-of related, but not really.

The tricks described there are ways to get a sender to be overly 
aggressive if it doesn't implement ABC (or other mitigations) so is 
growing a congestion window based on units of packets rather than 
bytes.  The L4S requirement here is about retransmission / loss 
detection though (reducing the window) happening based on units of time 
vs packets (rather than bytes vs packets).