
From nobody Mon Apr  1 08:44:20 2019
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AAA79120264; Mon,  1 Apr 2019 08:44:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: <tsvwg-chairs@ietf.org>, <draft-roca-tsvwg-tinymt32@ietf.org>, <tsvwg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155413345268.17110.4064603499271824993.idtracker@ietfa.amsl.com>
Date: Mon, 01 Apr 2019 08:44:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/D902Dx4V9-olqnwuYYGshIdiwhE>
Subject: [tsvwg] The TSVWG WG has placed draft-roca-tsvwg-tinymt32 in state "Adopted by a WG"
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 01 Apr 2019 15:44:19 -0000

The TSVWG WG has placed draft-roca-tsvwg-tinymt32 in state
Adopted by a WG (entered by Wesley Eddy)

The document is available at
https://datatracker.ietf.org/doc/draft-roca-tsvwg-tinymt32/

Comment:
This document was primarily split out from the RLC FEC draft in order to
address copyright questions that came up during IESG reviews.


From nobody Mon Apr  1 08:49:07 2019
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 DF28112029D for <tsvwg@ietfa.amsl.com>; Mon,  1 Apr 2019 08:49:05 -0700 (PDT)
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 LHBhp3Ce8l91 for <tsvwg@ietfa.amsl.com>; Mon,  1 Apr 2019 08:49:03 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 06491120297 for <tsvwg@ietf.org>; Mon,  1 Apr 2019 08:48:43 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id z16so11430089qtn.4 for <tsvwg@ietf.org>; Mon, 01 Apr 2019 08:48:42 -0700 (PDT)
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=0wMjMFATfAjMelZPP4aIdgUNM3JLXDO92xhgzICNNYw=; b=SKQJ5d+SS+3IyI4YgIDnZy5hFnD+P4jYVsXN64XizMisoZTGrJQOSsV77i0+/ko8o4 ziC6RBDoWZWSYmUfFr7xSHLyI6dMlvWK4PMYnYUabOof4pG9JrQBwKjxvk8HeaN4KFHR VpPjATBoncMalzCYWMM7+9b8TcBY1z8lBwmdpQFuxtu/PsvCZR9rbQ/SRlCMob6FXKeS UHJZjI6VxEIzeCX/fBe6qAakubgJ9upW07btkQPfgk6QE8tj67PYqQ8Ltl7W87Ctw9uf ZRfzPkrWRSdpswBNIPyEFcRltvgGN4ElP+QEJCHpLHmgursKzwetCfBXLkwQGJA415HU +YcA==
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=0wMjMFATfAjMelZPP4aIdgUNM3JLXDO92xhgzICNNYw=; b=YS+wC+aBccTtQLoFR1o8C56+WesyHARPGvk7/Re+Camrryai1SfoJC3cXaB+KTutU0 hKy2azHSmVCbqm9ajClTIRQFwEWt2z1JBpTmpaTh6uQuw6fjngPEC2xdU6bJKLebVH3w 5Lvp2aBG+OcWrmLtcYgKbPcKyBtjF07YiZm3QDzrxRCp0GBiVS1yt+8R/Pt1dwyBPULB BtQPpNOEo6ii7J22Z9izekdQhkxmGXeNSzgUnzzPGDofi8y3mD8TzAThLVSrG3cfSVdx dKxVquBQqIW3lsk6JglxluvKGZ2PbhAlXdZkQuBQbmRPrYxR+0SFMX3QOKULxa1lJLug b0zg==
X-Gm-Message-State: APjAAAUGzXKK6HT1pKS783XT4JqW3ztkAlKUN0FUAjKopyyyfr+YLAbZ thuHD7rQ7Rp+2wRLRdzsI8SxEpUqggY=
X-Google-Smtp-Source: APXvYqwOMbHVkIUPWlfWm+yL6v9EsX+Xuzyt0t8V4RbG+f/dJMI8GrJOk8FIUf/3fQlW9d+rQc3HOQ==
X-Received: by 2002:aed:3c0f:: with SMTP id t15mr34744614qte.282.1554133722024;  Mon, 01 Apr 2019 08:48:42 -0700 (PDT)
Received: from [192.168.1.119] (rrcs-69-135-1-122.central.biz.rr.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id 46sm6844107qtz.87.2019.04.01.08.48.41 for <tsvwg@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Apr 2019 08:48:41 -0700 (PDT)
To: tsvwg@ietf.org
References: <155413345268.17110.4064603499271824993.idtracker@ietfa.amsl.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <0e9af5c2-5adb-3efb-b8d0-733cdc5f6d49@mti-systems.com>
Date: Mon, 1 Apr 2019 11:48:39 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <155413345268.17110.4064603499271824993.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XexQcGk9OnP7ZsT6XWNJRhkzPvM>
Subject: Re: [tsvwg] The TSVWG WG has placed draft-roca-tsvwg-tinymt32 in state "Adopted by a WG"
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: Mon, 01 Apr 2019 15:49:06 -0000

FYI - following up on the adoption call last week on the list, I've 
marked this as a working group item in the tracker.

On 4/1/2019 11:44 AM, IETF Secretariat wrote:
> The TSVWG WG has placed draft-roca-tsvwg-tinymt32 in state
> Adopted by a WG (entered by Wesley Eddy)
>
> The document is available at
> https://datatracker.ietf.org/doc/draft-roca-tsvwg-tinymt32/
>
> Comment:
> This document was primarily split out from the RLC FEC draft in order to
> address copyright questions that came up during IESG reviews.


From nobody Tue Apr  2 07:52:00 2019
Return-Path: <gorry@erg.abdn.ac.uk>
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 B924712014B for <tsvwg@ietfa.amsl.com>; Tue,  2 Apr 2019 07:51:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, URIBL_BLOCKED=0.001] 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 fpqtngiRtmDh for <tsvwg@ietfa.amsl.com>; Tue,  2 Apr 2019 07:51:56 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id DAE8D12013B for <tsvwg@ietf.org>; Tue,  2 Apr 2019 07:51:55 -0700 (PDT)
Received: from G-MacBook.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id E14FF1B00280 for <tsvwg@ietf.org>; Tue,  2 Apr 2019 15:51:51 +0100 (BST)
Message-ID: <5CA37707.1040108@erg.abdn.ac.uk>
Date: Tue, 02 Apr 2019 15:51:51 +0100
From: G Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: tsvwg WG <tsvwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/xuXX8yQrRmsZiwjmfTP64f5ctsM>
Subject: [tsvwg] Draft notes from IETF-104 TSVWG meetings in Prague
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: Tue, 02 Apr 2019 14:51:59 -0000

The following link contains the draft notes. Please send 
comments/corrections to the chairs or the tsvwg mailing list.

https://datatracker.ietf.org/doc/minutes-104-tsvwg/

Best wishes,

Gorry, Wes and David.


From nobody Tue Apr  2 13:01:39 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B827112027B; Tue,  2 Apr 2019 13:01:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: tsvwg@ietf.org
Message-ID: <155423529765.6262.6113369982446210104@ietfa.amsl.com>
Date: Tue, 02 Apr 2019 13:01:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/4QkGevpd3dJuyWHtOza2tQ6kl2o>
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-tinymt32-00.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Apr 2019 20:01:38 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group WG of the IETF.

        Title           : TinyMT32 Pseudo Random Number Generator (PRNG)
        Authors         : Mutsuo Saito
                          Makoto Matsumoto
                          Vincent Roca
                          Emmanuel Baccelli
	Filename        : draft-ietf-tsvwg-tinymt32-00.txt
	Pages           : 10
	Date            : 2019-04-02

Abstract:
   This document describes the TinyMT32 Pseudo Random Number Generator
   (PRNG) that produces 32-bit pseudo-random unsigned integers and aims
   at having a simple-to-use and deterministic solution.  This PRNG is a
   small-sized variant of Mersenne Twister (MT) PRNG, also designed by
   M.  Saito and M.  Matsumoto.  The main advantage of TinyMT32 over MT
   is the use of a small internal state, compatible with most target
   platforms including embedded devices, while keeping a reasonably good
   randomness.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tsvwg-tinymt32-00
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-tinymt32-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Apr  2 23:14:50 2019
Return-Path: <liyizhou@huawei.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 50BB9120049 for <tsvwg@ietfa.amsl.com>; Tue,  2 Apr 2019 23:14:48 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 NiBQdD9VPmQP for <tsvwg@ietfa.amsl.com>; Tue,  2 Apr 2019 23:14:45 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 60A17120019 for <tsvwg@ietf.org>; Tue,  2 Apr 2019 23:14:45 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 32AB885DEB74F995B576 for <tsvwg@ietf.org>; Wed,  3 Apr 2019 07:14:13 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 3 Apr 2019 07:14:12 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.144]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0415.000; Wed, 3 Apr 2019 14:14:09 +0800
From: Liyizhou <liyizhou@huawei.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: New Non-WG Mailing List: LOOPS
Thread-Index: AQHU6W+GIfIXOh5YnEyQCX7JeO8Zk6Yp8vdg
Date: Wed, 3 Apr 2019 06:14:09 +0000
Message-ID: <D408889639FC5E4FADB4E00A3E01FA8FB03CD14C@nkgeml513-mbx.china.huawei.com>
References: <155422177532.6400.569642190649683451.idtracker@ietfa.amsl.com>
In-Reply-To: <155422177532.6400.569642190649683451.idtracker@ietfa.amsl.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.134.186.90]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/5p7GYqyyMq3txtf8rl5p0fQqiGE>
Subject: [tsvwg] FW: New Non-WG Mailing List: LOOPS
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: Wed, 03 Apr 2019 06:14:48 -0000

VG8gdGhvc2UgbWlnaHQgYmUgaW50ZXJlc3RlZCwgTE9PUFMgKExvY2FsIE9wdGltaXphdGlvbnMg
b24gUGF0aCBTZWdtZW50cykgbWFpbGluZyBsaXN0IHdhcyBjcmVhdGVkLg0KDQpSZ2RzLA0KWWl6
aG91DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBJRVRGLUFubm91bmNlIFtt
YWlsdG86aWV0Zi1hbm5vdW5jZS1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSUVURiBT
ZWNyZXRhcmlhdA0KU2VudDogV2VkbmVzZGF5LCBBcHJpbCAwMywgMjAxOSAxMjoxNiBBTQ0KVG86
IElFVEYgQW5ub3VuY2VtZW50IExpc3QgPGlldGYtYW5ub3VuY2VAaWV0Zi5vcmc+DQpDYzogY2Fi
b0B0emkub3JnDQpTdWJqZWN0OiBOZXcgTm9uLVdHIE1haWxpbmcgTGlzdDogTE9PUFMNCg0KQSBu
ZXcgSUVURiBub24td29ya2luZyBncm91cCBlbWFpbCBsaXN0IGhhcyBiZWVuIGNyZWF0ZWQuDQoN
Ckxpc3QgYWRkcmVzczogbG9vcHNAaWV0Zi5vcmcNCkFyY2hpdmU6IGh0dHBzOi8vbWFpbGFyY2hp
dmUuaWV0Zi5vcmcvYXJjaC9icm93c2UvbG9vcHMvDQpUbyBzdWJzY3JpYmU6IGh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbG9vcHMNCg0KUHVycG9zZToNClBlcmZvcm1hbmNl
IGVuaGFuY2luZyBmdW5jdGlvbnMgaW4gdGhlIG5ldHdvcmsgaW5jcmVhc2luZ2x5IG5vIGxvbmdl
ciBjYW4gcGVlayBpbnRvIGFuZCBtYW5pcHVsYXRlIGhpZ2hlciBsYXllciBpbmZvcm1hdGlvbiwg
YnV0IG5vdyBjYW4gYmUgYnVpbHQgb24gbW9yZSBwb3dlcmZ1bCBwbGF0Zm9ybXMuIFRoYXQgb3Bl
bnMgdGhlIG9wcG9ydHVuaXR5IHRvIHBlcmZvcm0gb3B0aW1pemF0aW9ucyBzdWNoIGFzIGxvc3Mg
cmVjb3ZlcnkgKHJldHJhbnNtaXNzaW9uLCByZWNvdmVyeSB2aWEgRkVDKSBiZXR3ZWVuIHRoZSBp
bmdyZXNzIGFuZCB0aGUgZWdyZXNzIG5vZGVzIG9mIGEgdHVubmVsIHRoYXQgc3BhbnMgYSBwYXRo
IHNlZ21lbnQuIExPT1BTIChMb2NhbCBPcHRpbWl6YXRpb25zIG9uIFBhdGggU2VnbWVudHMpIGlz
IGFuIGVmZm9ydCB0byBzdGFydCBhIHdvcmtpbmcgZ3JvdXAgdGhhdCBkZWZpbmVzIGEgcHJvdG9j
b2wgZm9yIHN1Y2ggYSBmdW5jdGlvbiBhbmQgYW4gaW5mb3JtYXRpb24gbW9kZWwgZm9yIHRoZSBk
YXRhIGV4Y2hhbmdlZCBiZXR3ZWVuIHRoZSB0dW5uZWwgZW5kcywgd2l0aCBiaW5kaW5ncyB0byBt
dWx0aXBsZSBlbmNhcHN1bGF0aW9uIHNjaGVtZXMuDQoNCk1vcmUgaW5mb3JtYXRpb24gY2FuIGJl
IGZvdW5kIGF0IGh0dHBzOi8vZ2l0aHViLmNvbS9sb29wcy13Zy8uDQoNClRoaXMgbGlzdCBiZWxv
bmcgSUVURiBhcmVhOiBUU1YNCg0KRm9yIGFkZGl0aW9uYWwgaW5mb3JtYXRpb24sIHBsZWFzZSBj
b250YWN0IHRoZSBsaXN0IGFkbWluaXN0cmF0b3JzLg0KDQo=


From nobody Wed Apr  3 10:40:43 2019
Return-Path: <in@bobbriscoe.net>
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 C75B9120153 for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 10:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=bobbriscoe.net
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 kkuaCPBpkIjU for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 10:40:38 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (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 16E0A120150 for <tsvwg@ietf.org>; Wed,  3 Apr 2019 10:40:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-Transfer-Encoding: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=SLYTYG+ADQGP5NcofMvANmjU0p30zbALcpDa97kqL64=; b=4BDnOhs5RaPmiCeq/WUG8N/Oi VLTVPQ8uT7nGk5GLDZuarK1beUHNssO8HW5iWRiXWU4M97/bAIK1zUm+fHtADMC6lSbVb8S59/nRy ma/P6etG4FYGp8ofZrYBbHPXNof498D65x3eWftxVGwlkXYlPHXTeQCdXkPoMjbhK/b0GjdxIg6Yl n8ZKsl7s2sSfMkRdXiMwFAI5mJKOM1EMfKGNjxXxRfCAlUP1VSfELpKQLLyNNnrWPbnUXtR2RScJL 3vyRllAAVhnn/1ZFA9L+t0I9eGACAw0Me9HzliJqCobjoVJiOl1lVbXDogJkCPYvInrWnGEtnhstF 2sq67CWzw==;
Received: from [31.185.128.56] (port=60372 helo=[192.168.0.9]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <in@bobbriscoe.net>) id 1hBjsJ-0007xY-OP; Wed, 03 Apr 2019 18:40:36 +0100
To: Sebastian Moeller <moeller0@gmx.de>, iccrg@irtf.org, tsvwg IETF list <tsvwg@ietf.org>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de>
From: Bob Briscoe <in@bobbriscoe.net>
Message-ID: <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net>
Date: Wed, 3 Apr 2019 18:40:34 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de>
Content-Type: multipart/alternative; boundary="------------66743B462A2761BB69551C52"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/dMG4JhZe7oY_yWvyr070dUEwF1Q>
Subject: Re: [tsvwg] [iccrg] IETF104 ICCRG TCP Prague presentation
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: Wed, 03 Apr 2019 17:40:41 -0000

This is a multi-part message in MIME format.
--------------66743B462A2761BB69551C52
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Sebastien, (adding tsvwg, given this is all part of the decision over 
L4S/SCE),

On 02/04/2019 12:38, Sebastian Moeller wrote:
> I finally got around to see the TCP Prague presentation, nice, especially the part around slide 11 "Fallback to Reno-friendly on Classic ECN" caught my interest.
>
> The claim made there is that L4S's inability to properly deduce the type of CE signal (normal ECN response expected versus DCTCP-like ECN response expected) would only matter in the case of ECN-marking single queue AQMs and not for flow-queueung AQMs, and I would like to argue that that should be measured rather than solved by declaration.
[BB] I don't know whether you just looked at my slides without the voice 
track. But the voice track makes it clear that is exactly what I've been 
setting up.

To save those who weren't in the room from having to sit through the 
audio, I said that there are two sets of contradictory measurements:

  * those from 'academic' active measurement studies that have found
    hardly any CE
  * those from Apple's passive measurements on Apple devices that have
    found significant localized amounts of CE.

My hypothesis is that the active measurements aren't seeing much CE, cos 
they don't generate enough traffic themselves to congestion the link and 
they would have to coincide with other traffic to see it passively.

I said, in short, I believe the active measurements are more likely 
wrong, and passive more likely right.

Nonetheless the CE that Apple measured could be consistent with classic 
ECN marking from FQ-CoDel, e.g. in OpenWRT devices, which would protect 
competing flows from L4S flows. Apple saw CE "mainly in the uplink", 
which is likely to be FQ-CoDel. And the smaller amount seen in the 
downlink could have been peer-to-peer flows that had been marked on 
entry to the uplink by an FQ-CoDel home router.

With the help of others, I've devised a test for FQ vs FIFO, but we need 
to find where the CE-marking routers are before we apply the test (a 
scatter-gun approach would be infeasible given the need to congest the 
link). In discussions with Apple folks, we think it's best to run tests 
at the CDN end, to identify the network prefixes where CE is appearing 
(the client end used in the original tests usually doesn't know its 
public IP address).

If we find any CE in the downlink from the CDN, that will disprove my 
peer-peer FQ hypothesis. But it won't prove that it's from a FIFO. The 
test for FQ vs FIFO is not straightforward, and I haven't yet worked out 
how we run it in the relevant direction over the paths where we find CE 
(not least 'cos that would involve collecting and identifying client IP 
addresses, which raises privacy concerns). I suspect we'll need to 
co-opt some volunteers in the affected localities, somehow.

An alternative to inline testing will be to find out whether the 
networks where CE is being seen have supplied their customers with 
routers with FQ-CoDel enabled. That won't prove conclusively that all 
the CE is coming from FQ-CoDel, but we can only go so far in trying to 
prove a negative.

>
>
> Consider the following case, that get's more and more common: traffic shaping for both ingress and egress somewhere on the end-customer side of an internet access link. For egress I agree with the rationale, that flow-queueing/fair-queueung should deal with flows that appear unresponsive sooner or later (but I note that this still will increase the memory required for the queueing and should not be considered ideal behavior).
> But for ingress shaping downstream of the "true" bottleneck (I am simplifying over some details here) this rationale falls apart, the unexpected packets the L4S sender kept sending since it misinterpreted the CE mark, will still hog valuable bandwidth of the internet access link, and hence fair queuing on the home end of the true bottleneck will not isolate that homenet from the L4S misunderstanding.
[BB] For the avoidance of doubt, I think you're using 'egress' to mean 
[home -> Internet] (I use it for the other direction, but I can work 
with your terminology).

In the [Internet -> home] direction, you are right that FQ on the home 
end would not isolate the access link from a misunderstanding of any CE 
marking. But I'm not suggesting it could or would. The question is about 
the machine at the Internet side of the access link (BRAS, CMTS, etc) 
that is queuing traffic into the access link towards the home. We can be 
nearly certain it is not doing FQ (these machines serve thousands of 
customers, so I don't believe any use FQ). The question is whether we 
can find one of these non-FQ machines that has an AQM enabled that does 
CE marking.

That's what we're trying to find. It's of course hard to prove a 
negative - that none exist. All we can hope to do is measure a sample of 
the paths we find.


A nit: DCTCP is not /unresponsive/. It responds to congestion, but as if 
it is equivalent to a number of 'classic' (Reno-friendly) TCP flows.

>
> I would be delighted to learn where my assumptions are wrong...
Regards



Bob

>
> Regards
> 	Sebastian Moeller
>
> _______________________________________________
> iccrg mailing list
> iccrg@irtf.org
> https://www.irtf.org/mailman/listinfo/iccrg

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------66743B462A2761BB69551C52
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Sebastien, (adding tsvwg, given this is all part of the decision
    over L4S/SCE),<br>
    <br>
    <div class="moz-cite-prefix">On 02/04/2019 12:38, Sebastian Moeller
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de">
      <pre class="moz-quote-pre" wrap="">
I finally got around to see the TCP Prague presentation, nice, especially the part around slide 11 "Fallback to Reno-friendly on Classic ECN" caught my interest.

The claim made there is that L4S's inability to properly deduce the type of CE signal (normal ECN response expected versus DCTCP-like ECN response expected) would only matter in the case of ECN-marking single queue AQMs and not for flow-queueung AQMs, and I would like to argue that that should be measured rather than solved by declaration.</pre>
    </blockquote>
    [BB] I don't know whether you just looked at my slides without the
    voice track. But the voice track makes it clear that is exactly what
    I've been setting up.<br>
    <br>
    To save those who weren't in the room from having to sit through the
    audio, I said that there are two sets of contradictory measurements:
    <br>
    <ul>
      <li>those from 'academic' active measurement studies that have
        found hardly any CE</li>
      <li>those from Apple's passive measurements on Apple devices that
        have found significant localized amounts of CE.</li>
    </ul>
    My hypothesis is that the active measurements aren't seeing much CE,
    cos they don't generate enough traffic themselves to congestion the
    link and they would have to coincide with other traffic to see it
    passively.<br>
    <br>
    I said, in short, I believe the active measurements are more likely
    wrong, and passive more likely right.<br>
    <br>
    Nonetheless the CE that Apple measured could be consistent with
    classic ECN marking from FQ-CoDel, e.g. in OpenWRT devices, which
    would protect competing flows from L4S flows. Apple saw CE "mainly
    in the uplink", which is likely to be FQ-CoDel. And the smaller
    amount seen in the downlink could have been peer-to-peer flows that
    had been marked on entry to the uplink by an FQ-CoDel home router.<br>
    <br>
    With the help of others, I've devised a test for FQ vs FIFO, but we
    need to find where the CE-marking routers are before we apply the
    test (a scatter-gun approach would be infeasible given the need to
    congest the link). In discussions with Apple folks, we think it's
    best to run tests at the CDN end, to identify the network prefixes
    where CE is appearing (the client end used in the original tests
    usually doesn't know its public IP address).<br>
    <br>
    If we find any CE in the downlink from the CDN, that will disprove
    my peer-peer FQ hypothesis. But it won't prove that it's from a
    FIFO. The test for FQ vs FIFO is not straightforward, and I haven't
    yet worked out how we run it in the relevant direction over the
    paths where we find CE (not least 'cos that would involve collecting
    and identifying client IP addresses, which raises privacy concerns).
    I suspect we'll need to co-opt some volunteers in the affected
    localities, somehow.<br>
    <br>
    An alternative to inline testing will be to find out whether the
    networks where CE is being seen have supplied their customers with
    routers with FQ-CoDel enabled. That won't prove conclusively that
    all the CE is coming from FQ-CoDel, but we can only go so far in
    trying to prove a negative.<br>
    <br>
    <blockquote type="cite"
      cite="mid:623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de">
      <pre class="moz-quote-pre" wrap="">


Consider the following case, that get's more and more common: traffic shaping for both ingress and egress somewhere on the end-customer side of an internet access link. For egress I agree with the rationale, that flow-queueing/fair-queueung should deal with flows that appear unresponsive sooner or later (but I note that this still will increase the memory required for the queueing and should not be considered ideal behavior).
But for ingress shaping downstream of the "true" bottleneck (I am simplifying over some details here) this rationale falls apart, the unexpected packets the L4S sender kept sending since it misinterpreted the CE mark, will still hog valuable bandwidth of the internet access link, and hence fair queuing on the home end of the true bottleneck will not isolate that homenet from the L4S misunderstanding.</pre>
    </blockquote>
    [BB] For the avoidance of doubt, I think you're using 'egress' to
    mean [home -&gt; Internet] (I use it for the other direction, but I
    can work with your terminology).<br>
    <br>
    In the [Internet -&gt; home] direction, you are right that FQ on the
    home end would not isolate the access link from a misunderstanding
    of any CE marking. But I'm not suggesting it could or would. The
    question is about the machine at the Internet side of the access
    link (BRAS, CMTS, etc) that is queuing traffic into the access link
    towards the home. We can be nearly certain it is not doing FQ (these
    machines serve thousands of customers, so I don't believe any use
    FQ). The question is whether we can find one of these non-FQ
    machines that has an AQM enabled that does CE marking.<br>
    <br>
    That's what we're trying to find. It's of course hard to prove a
    negative - that none exist. All we can hope to do is measure a
    sample of the paths we find.<br>
    <br>
    <br>
    A nit: DCTCP is not /unresponsive/. It responds to congestion, but
    as if it is equivalent to a number of 'classic' (Reno-friendly) TCP
    flows.<br>
    <br>
    <blockquote type="cite"
      cite="mid:623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de">
      <pre class="moz-quote-pre" wrap="">

I would be delighted to learn where my assumptions are wrong...</pre>
    </blockquote>
    Regards<br>
    <br>
    <br>
    <br>
    Bob<br>
    <br>
    <blockquote type="cite"
      cite="mid:623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de">
      <pre class="moz-quote-pre" wrap="">

Regards
	Sebastian Moeller

_______________________________________________
iccrg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:iccrg@irtf.org">iccrg@irtf.org</a>
<a class="moz-txt-link-freetext" href="https://www.irtf.org/mailman/listinfo/iccrg">https://www.irtf.org/mailman/listinfo/iccrg</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------66743B462A2761BB69551C52--


From nobody Wed Apr  3 11:28:24 2019
Return-Path: <chromatix99@gmail.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 C7EB0120165 for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 11:28:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 22YXlEN8_jdq for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 11:28:15 -0700 (PDT)
Received: from mail-lf1-x143.google.com (mail-lf1-x143.google.com [IPv6:2a00:1450:4864:20::143]) (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 4E331120163 for <tsvwg@ietf.org>; Wed,  3 Apr 2019 11:28:13 -0700 (PDT)
Received: by mail-lf1-x143.google.com with SMTP id b7so12429250lfg.9 for <tsvwg@ietf.org>; Wed, 03 Apr 2019 11:28:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=B3/XiLArPTiGC62q35XMfQxmVfdHb47pJrMK+diaIpE=; b=UB78FYCuVLazQd2j8xrxhLSdLndOjlLxAsRfXLhf5ln1hzDJXQh6Fxv6z1EAiiD92M 35zA/afRSWQ1VB16dWDRLnOhdr78IOTx45XS2MElM3svaoByWhG49UqNGvUADAvFaQr7 4KswqUsVFiW3vcTwEjytZZxe3CDR57layds/NHmvUXK6sHxdyT9iPbQ8sn/wpaDGPcvO 7EaN/kg16ppVvQw87agyfSzYmTLEXwKUYpJuZQo48p0w+dOX5TjDxKzYwMqasZIpdIvt v405OMBCtDgUg/5do94Lb3g8yzzsLuuu9skooe6ea2d//tBpKgHNoXflP31VgOa9UpGB Auow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=B3/XiLArPTiGC62q35XMfQxmVfdHb47pJrMK+diaIpE=; b=r6M5x9aleH91Ku4zVuEQ+RUsz4s693XLMOpK64TaUFIHDJY2rSQMcHKzJCXNPmUxqp 2yH5XwQZdmiStW/TwYTtykKIBZQpNSHjUdH4GKh07P5Fxp7AYC2TuUxeRB1TxZU8551x ZcTu1ZzTpjJ0RaMikB6q8Z+lpzh4/cMHMho/lAsHmcczxlSvebXAPqtxkoxa4QjTSPSO Iz5HX6o7VPWnrBYN2Ni/ni/ZKxAW7A7M/sWuYCuP5t9fVtzWUI+yv8cOp+JikhlLgXFI 6Nz9LVbs7OGMhToj24+V8xudDs/RmKmpW+EelOxLWrqKPhQ1BOsQV2if7ApNru/u1b6b GiVQ==
X-Gm-Message-State: APjAAAUaT5XYTA0/3h8LAHsZY+PkaQaO0OYGNA2H043xqj90ZrOLKpFA rnnIyhRpejVJW5srea6MadU=
X-Google-Smtp-Source: APXvYqx1em27SnKa51zs72ODp4Zmx/Xx3eSlUEcXOg6+XsZFF8s9ShblxD5vKRUYyy/rdzQ0mzgdeA==
X-Received: by 2002:ac2:4563:: with SMTP id k3mr633424lfm.101.1554316091565; Wed, 03 Apr 2019 11:28:11 -0700 (PDT)
Received: from jonathartonsmbp.lan (83-245-226-9-nat-p.elisa-mobile.fi. [83.245.226.9]) by smtp.gmail.com with ESMTPSA id q23sm3427319ljj.44.2019.04.03.11.28.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Apr 2019 11:28:10 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net>
Date: Wed, 3 Apr 2019 21:28:08 +0300
Cc: Sebastian Moeller <moeller0@gmx.de>, iccrg@irtf.org, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net>
To: Bob Briscoe <in@bobbriscoe.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/0yT20Vba5NN_SGJ0-jEIPghoZnk>
Subject: Re: [tsvwg] [iccrg] IETF104 ICCRG TCP Prague presentation
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: Wed, 03 Apr 2019 18:28:17 -0000

> On 3 Apr, 2019, at 8:40 pm, Bob Briscoe <in@bobbriscoe.net> wrote:
>=20
> To save those who weren't in the room from having to sit through the =
audio, I said that there are two sets of contradictory measurements:=20
> 	=E2=80=A2 those from 'academic' active measurement studies that =
have found hardly any CE
> 	=E2=80=A2 those from Apple's passive measurements on Apple =
devices that have found significant localized amounts of CE.
> My hypothesis is that the active measurements aren't seeing much CE, =
cos they don't generate enough traffic themselves to congestion the link =
and they would have to coincide with other traffic to see it passively.
>=20
> I said, in short, I believe the active measurements are more likely =
wrong, and passive more likely right.

This is actually reasonable.  However your slides were very unclear =
about this, which I think led to unnecessary confusion.

> Nonetheless the CE that Apple measured could be consistent with =
classic ECN marking from FQ-CoDel, e.g. in OpenWRT devices, which would =
protect competing flows from L4S flows. Apple saw CE "mainly in the =
uplink", which is likely to be FQ-CoDel. And the smaller amount seen in =
the downlink could have been peer-to-peer flows that had been marked on =
entry to the uplink by an FQ-CoDel home router.

It is actually common for OpenWRT devices to include "ingress shaping" =
to exert some control over bufferbloat on downloads.  The terminology, =
in fact, comes from this practice, as the port in question is facing the =
WAN link and has two qdiscs attached, one for egress traffic towards the =
Internet, and one for ingress traffic received from the Internet.

A lower rate of observed marking on downloads could be due to the =
greater difficulty of driving the download direction into saturation, =
especially given a backhaul network that may be oversubscribed in many =
ISPs during peak hours, and thus the greater difficulty of properly =
configuring an ingress shaper.  It is of course better for AQM to be =
installed on the upstream side of where the congestion actually occurs.

> In the [Internet -> home] direction, you are right that FQ on the home =
end would not isolate the access link from a misunderstanding of any CE =
marking. But I'm not suggesting it could or would. The question is about =
the machine at the Internet side of the access link (BRAS, CMTS, etc) =
that is queuing traffic into the access link towards the home. We can be =
nearly certain it is not doing FQ (these machines serve thousands of =
customers, so I don't believe any use FQ). The question is whether we =
can find one of these non-FQ machines that has an AQM enabled that does =
CE marking.

The motivating reason for ingress shaping is that, generally, the BRAS =
or equivalent device in the ISP does not perform AQM at all (though some =
do policing, which doesn't involve ECN).

In my experience there is often a "provisioning shaper" that is =
essentially a TBF with a dumb tail-dropping FIFO attached; I once =
suffered one on a rate-limited 3G service which had about 40 seconds of =
effective bloat.  If that had any sort of AQM installed, ECN or =
otherwise, flow-isolating or not, it would have resulted in vastly =
better service at essentially no cost to the ISP.  Indeed it may have =
saved them some money in reduced memory requirements on their =
provisioning shaper box.

On my present LTE connection, which varies wildly in available capacity =
on a minute-to-minute basis, I've set my ingress shaper to a flat 10Mbps =
rate.  It makes an enormous improvement to the quality of service I =
receive, even though it reduces my throughput to a fraction of what's =
available during off-hours.  Yes, it is a flow-isolating AQM shaper =
(Cake) which is broadly similar to fq_codel.

I did spend a few minutes today sketching out what happens if an L4S =
flow hits fq_codel on an ingress shaper.  The theoretical results are =
that, in congestion-avoidance mode, the L4S flow takes about twice as =
long to drain the dumb bottleneck queue as a Classic ECN flow after the =
onset of saturation.  But the real shocker is what happens in the =
terminal phase of slow-start, where a rapid correction is required after =
the minimum 2x overshoot in exponential growth (because it takes an RTT =
for the CE/ECE/CWR signal to circulate and take effect).

How many RTTs does it take for the cwnd to be halved in L4S, when the =
only CE signal is ramping up linearly at one-per-RTT-per-RTT?  Hopefully =
enough for L4S to detect the delay induced by the dumb FIFO and fall =
back to RFC-compliant behaviour.

(Yes, we have a real solution sketched out for SCE.  It will be tested =
soon.  We already have running code.)

 - Jonathan Morton


From nobody Wed Apr  3 13:27:46 2019
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 BA0241201EC for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 13:27:44 -0700 (PDT)
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 moa66-VBFV3B for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 13:27:42 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 8664912011C for <tsvwg@ietf.org>; Wed,  3 Apr 2019 13:27:42 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id b74so241682qkg.9 for <tsvwg@ietf.org>; Wed, 03 Apr 2019 13:27:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=/b5QsFLgrRZmMf2oejDKTEvmZULh1pfBc5NoqcHSxkg=; b=GCu44LFm7mOi3WckXsN/23tVkL/g8P0X0ucCiQr7q2SKccNJZzklJ3dCEUGMc1liXl nrOrgHbUwRFyLOliXySWFSGh1wg4rYKnqApYsHZwxy8PS+o3VG+muojbqOwNXehlVA47 mm49agE4zvIzLQOC8zS8grod+gV7eilQl74YCAe7xXngXWq9INY4cKscm47+yf14uz29 L55XouRu1WuS0osgmaTxJTxIGWWLw3UneuCQIKhSsUD+2IF6u2tuWzHH7/Vp2UXVmAW0 PqxfsA41IQ5gwFsTE4mZcxjKu3qTR40sfnUhRqWUOULXen8Ay4mTv//danAtsQafQLIW AtSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=/b5QsFLgrRZmMf2oejDKTEvmZULh1pfBc5NoqcHSxkg=; b=LpvZW6k6z1v4L+/OKhehNJZdvuCT4jo59ZVQ29j3GK+14hNlvvJXs0etxdiyywEdZy 3btOWRGmKXVM6wcsuG9CkcHzZxcycpKMV1zyouHdbuNWOLywY62lP4RI9SAy+kLu5Wtt VNB9aC8V73tH6mt62Corv+5cS8v1KaS+uF3qwikgJz0E5uIPZEM6oe5SWJzrFt2PsKot SNH5Ty9EwTlqFImWP3PAE1mkjgpj++yvXVMbFwB/aBsrTC1DwwrWqJLLNgrAGlsbO/Qg TarpJ94zrqNZufZ9X8+en8AjVPNGMe4Ve8TcmVTnbNew/7iblMUxVf3eCsczbMzID/53 WRQg==
X-Gm-Message-State: APjAAAUop/4YFYtr65sYVF8Cl6GOZt7VsIA1aDALr1Q6gfBfSegT58g6 HA8hfYrk00QGrufIq4rpPtg+zUsslBw=
X-Google-Smtp-Source: APXvYqwrX3ZDx7gJL/aMSOe2o8gQ6dvu5M+j8EXeEQoSepnb+Po/ORkw6RA6OOogXv1Osmlu9Kzl8w==
X-Received: by 2002:a37:c203:: with SMTP id i3mr1753086qkm.295.1554323261551;  Wed, 03 Apr 2019 13:27:41 -0700 (PDT)
Received: from [192.168.1.119] (rrcs-69-135-1-122.central.biz.rr.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id a8sm10310044qtc.19.2019.04.03.13.27.41 for <tsvwg@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Apr 2019 13:27:41 -0700 (PDT)
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <62d044d7-6925-4246-4430-33582b859e21@mti-systems.com>
Date: Wed, 3 Apr 2019 16:27:39 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
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/TsINO5lSzASBPzoAUIaB61J3ISc>
Subject: [tsvwg] WGLC for TinyMT32 draft
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: Wed, 03 Apr 2019 20:27:45 -0000

Hello, this email is to start a working group last call for the TinyMT32 
PRNG draft:

https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/

This was spun out from content that had been in the RLC FEC draft, which 
formerly went through working group last call.  This draft was created 
primarily in order to solve the copyright issue identified in IESG 
review.  As such, there are not major technical changes that we are 
expecting to need a lot of feedback on in this working group last call.  
However, please submit any comments that are pertinent.

We'll plan to collect WGLC comments through 4/15.

Thanks!



From nobody Wed Apr  3 16:28:54 2019
Return-Path: <g.white@CableLabs.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 AB45912016E for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 16:28:45 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 Mafzj2M-XBSO for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 16:28:42 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770125.outbound.protection.outlook.com [40.107.77.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7738E120155 for <tsvwg@ietf.org>; Wed,  3 Apr 2019 16:28:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=LxDRExzYACA6AN9rh5w5h7Dm2dkSmSNvacr4jI2GNtw=; b=qUByKoG5dLcjS9KrIVtKy4zWbYI6igxD5Soc7GCBCW6AlEhzjbrhmv/LMqHbCgjj20V/+4OUr/lKgl4OwMEAC+rCIvqCMCyLLnPP2VWSPOx5aaEHtl4g0GuxTOEiUxuSPE3oCISNfRq6JCjTu1tDUJzD6f4rSgvlbYC8hAHlm/c=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB4414.namprd06.prod.outlook.com (52.135.123.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.16; Wed, 3 Apr 2019 23:28:38 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c%6]) with mapi id 15.20.1750.021; Wed, 3 Apr 2019 23:28:38 +0000
From: Greg White <g.white@CableLabs.com>
To: Jonathan Morton <chromatix99@gmail.com>, Bob Briscoe <in@bobbriscoe.net>
CC: "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: [iccrg] [tsvwg]  IETF104 ICCRG TCP Prague presentation
Thread-Index: AQHU6ksFATQlV6AwuEyVhJCWJn+a66YrJhqA
Date: Wed, 3 Apr 2019 23:28:37 +0000
Message-ID: <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com>
In-Reply-To: <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.14.0.181208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com; 
x-originating-ip: [79.173.153.218]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 48842b8b-138f-4b6c-e3fc-08d6b88c196d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:SN6PR06MB4414; 
x-ms-traffictypediagnostic: SN6PR06MB4414:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <SN6PR06MB441442968BCBE80DC7CD2053EE570@SN6PR06MB4414.namprd06.prod.outlook.com>
x-forefront-prvs: 0996D1900D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(189003)(199004)(6506007)(83716004)(71190400001)(82746002)(14454004)(25786009)(6512007)(966005)(11346002)(66574012)(2906002)(76176011)(4326008)(305945005)(2616005)(106356001)(58126008)(7736002)(476003)(110136005)(8676002)(81156014)(105586002)(81166006)(3846002)(36756003)(33656002)(14444005)(86362001)(446003)(186003)(5024004)(229853002)(54906003)(486006)(99286004)(102836004)(53546011)(5660300002)(6306002)(68736007)(97736004)(498600001)(6246003)(6486002)(6116002)(66066001)(26005)(53936002)(6436002)(71200400001)(8936002)(256004)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB4414; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: fhqmksyHjarZyaCthf1cEEDoSc6oQeYg0eI4VHSrEgkdMGzNnkyDTMy7JQmCygX60WXmKIJlUsU6byKo35v3DjEboTcyquJzrdi+i229mmMXXY5EY/+62T49AuWF5jrRbyG7KE2jVf6AsSmNkmRiFiWjQwJ//y0aCTlmsPSwCdP2yFEK7xPfKqxR9/ZTygAl/Ywb7XKQ9skpj7tKE1HOZ25EVJss0pjtsI+SRCN3Hr1C6b7SsEWesQdzzb/W6VP5S4RSeiZFNw6hNhEkUOM6oyjWH9tvtNh0myvaPNmI4QeioHHAMIHYXyX59346S8E7v4NfKTGc3rp+Ri0X3iUoiwH0DL96dzp1hHD0vLJl2FLCnXeMndKzxTeRZjtZcK8VHfXeUanX1hykJQfcXyGRtHU9MVVFQliybPoT8IuZwdo=
Content-Type: text/plain; charset="utf-8"
Content-ID: <E4F65A8E89FC41408907FD60AB0143A2@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 48842b8b-138f-4b6c-e3fc-08d6b88c196d
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Apr 2019 23:28:38.0067 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB4414
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/7TExKcTqGcEC4uwhJR1kjqHj8bY>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Wed, 03 Apr 2019 23:28:45 -0000

T24gNC8zLzE5LCA3OjI4IFBNLCAiaWNjcmcgb24gYmVoYWxmIG9mIEpvbmF0aGFuIE1vcnRvbiIg
PGljY3JnLWJvdW5jZXNAaXJ0Zi5vcmcgb24gYmVoYWxmIG9mIGNocm9tYXRpeDk5QGdtYWlsLmNv
bT4gd3JvdGU6DQpbLi4uXQ0KICAgIEl0IGlzIGFjdHVhbGx5IGNvbW1vbiBmb3IgT3BlbldSVCBk
ZXZpY2VzIHRvIGluY2x1ZGUgImluZ3Jlc3Mgc2hhcGluZyIgdG8gZXhlcnQgc29tZSBjb250cm9s
IG92ZXIgYnVmZmVyYmxvYXQgb24gZG93bmxvYWRzLiAgVGhlIHRlcm1pbm9sb2d5LCBpbiBmYWN0
LCBjb21lcyBmcm9tIHRoaXMgcHJhY3RpY2UsIGFzIHRoZSBwb3J0IGluIHF1ZXN0aW9uIGlzIGZh
Y2luZyB0aGUgV0FOIGxpbmsgYW5kIGhhcyB0d28gcWRpc2NzIGF0dGFjaGVkLCBvbmUgZm9yIGVn
cmVzcyB0cmFmZmljIHRvd2FyZHMgdGhlIEludGVybmV0LCBhbmQgb25lIGZvciBpbmdyZXNzIHRy
YWZmaWMgcmVjZWl2ZWQgZnJvbSB0aGUgSW50ZXJuZXQuDQpbLi4uXQ0KICBJdCBpcyBvZiBjb3Vy
c2UgYmV0dGVyIGZvciBBUU0gdG8gYmUgaW5zdGFsbGVkIG9uIHRoZSB1cHN0cmVhbSBzaWRlIG9m
IHdoZXJlIHRoZSBjb25nZXN0aW9uIGFjdHVhbGx5IG9jY3Vycy4NClsuLi5dICAgIA0KICAgIFRo
ZSBtb3RpdmF0aW5nIHJlYXNvbiBmb3IgaW5ncmVzcyBzaGFwaW5nIGlzIHRoYXQsIGdlbmVyYWxs
eSwgdGhlIEJSQVMgb3IgZXF1aXZhbGVudCBkZXZpY2UgaW4gdGhlIElTUCBkb2VzIG5vdCBwZXJm
b3JtIEFRTSBhdCBhbGwgKHRob3VnaCBzb21lIGRvIHBvbGljaW5nLCB3aGljaCBkb2Vzbid0IGlu
dm9sdmUgRUNOKS4NCg0KW0dXXSBJdCB3aWxsIGJlIHRoZSBjYXNlIHRoYXQgbWFueSBzdWNoICJl
cXVpdmFsZW50IGRldmljZXMiIGNhbiAoYW5kIHdpbGwpIHN1cHBvcnQgYSBkdWFsLXF1ZXVlIEFR
TSAobm90IGZxKSwgd2hpY2ggKHdoZXJlIGF2YWlsYWJsZSkgd2lsbCBlbGltaW5hdGUgdGhlIG5l
ZWQgZm9yIGluZ3Jlc3Mgc2hhcGluZywgYW5kIHByb3ZpZGUgYSBiZXR0ZXIgcmVzdWx0LiAgICBJ
ZiBmcV9jb2RlbCAob3IgQ0FLRSkgd2VyZSB1cGRhdGVkIHRvIHV0aWxpemUgdGhlIEw0Uy1zdHls
ZSBvZiBFQ04gKG9yIGV2ZW4ganVzdCB0cmVhdCBFQ1QoMSkgYXMgbm9uLUVDVCksIHRoaXMgd291
bGQgYmUgYSBub24taXNzdWUuICAgSG93IGZlYXNpYmxlIHdvdWxkIHRoYXQgYmU/IA0KDQpbLi4u
XQ0KICAgIEkgZGlkIHNwZW5kIGEgZmV3IG1pbnV0ZXMgdG9kYXkgc2tldGNoaW5nIG91dCB3aGF0
IGhhcHBlbnMgaWYgYW4gTDRTIGZsb3cgaGl0cyBmcV9jb2RlbCBvbiBhbiBpbmdyZXNzIHNoYXBl
ci4gIFRoZSB0aGVvcmV0aWNhbCByZXN1bHRzIGFyZSB0aGF0LCBpbiBjb25nZXN0aW9uLWF2b2lk
YW5jZSBtb2RlLCB0aGUgTDRTIGZsb3cgdGFrZXMgYWJvdXQgdHdpY2UgYXMgbG9uZyB0byBkcmFp
biB0aGUgZHVtYiBib3R0bGVuZWNrIHF1ZXVlIGFzIGEgQ2xhc3NpYyBFQ04gZmxvdyBhZnRlciB0
aGUgb25zZXQgb2Ygc2F0dXJhdGlvbi4gIEJ1dCB0aGUgcmVhbCBzaG9ja2VyIGlzIHdoYXQgaGFw
cGVucyBpbiB0aGUgdGVybWluYWwgcGhhc2Ugb2Ygc2xvdy1zdGFydCwgd2hlcmUgYSByYXBpZCBj
b3JyZWN0aW9uIGlzIHJlcXVpcmVkIGFmdGVyIHRoZSBtaW5pbXVtIDJ4IG92ZXJzaG9vdCBpbiBl
eHBvbmVudGlhbCBncm93dGggKGJlY2F1c2UgaXQgdGFrZXMgYW4gUlRUIGZvciB0aGUgQ0UvRUNF
L0NXUiBzaWduYWwgdG8gY2lyY3VsYXRlIGFuZCB0YWtlIGVmZmVjdCkuDQogICAgSG93IG1hbnkg
UlRUcyBkb2VzIGl0IHRha2UgZm9yIHRoZSBjd25kIHRvIGJlIGhhbHZlZCBpbiBMNFMsIHdoZW4g
dGhlIG9ubHkgQ0Ugc2lnbmFsIGlzIHJhbXBpbmcgdXAgbGluZWFybHkgYXQgb25lLXBlci1SVFQt
cGVyLVJUVD8gIEhvcGVmdWxseSBlbm91Z2ggZm9yIEw0UyB0byBkZXRlY3QgdGhlIGRlbGF5IGlu
ZHVjZWQgYnkgdGhlIGR1bWIgRklGTyBhbmQgZmFsbCBiYWNrIHRvIFJGQy1jb21wbGlhbnQgYmVo
YXZpb3VyLg0KDQpbR1ddIE9uZSBvZiB0aGUgb3B0aW1pemF0aW9ucyBiZWluZyBpbnZlc3RpZ2F0
ZWQgZm9yIEw0UyAoYm90aCBUQ1AvUVVJQyBQcmFndWUgYW5kIChJIHRoaW5rKSBCQlJ2MikgaXMg
YSByZXZpc2VkIHN0YXJ0dXAgcHJvY2VzcyB0aGF0IGF2b2lkcyB0aGUgMnggb3ZlcnNob290IGZy
b20gc2xvdy1zdGFydC4gIE5vbmV0aGVsZXNzLCB5b3UgYXJlIHJpZ2h0IHRoYXQgYW4gaXNzdWUg
dG8gYmUgdW5kZXJzdG9vZCAoYW5kIGFkZHJlc3NlZD8pIHdpdGggVENQIFByYWd1ZSAvIGZxX2Nv
ZGVsIGNvbXBhdGliaWxpdHkgaXMgaG93IHRvIHByZXZlbnQgVENQIFByYWd1ZSBzZWVpbmcgd29y
c2UgbGF0ZW5jeSB0aGFuIGNsYXNzaWMgVENQIGF0IGZsb3cgc3RhcnR1cC4gIEFzIHlvdSBpbmRp
Y2F0ZWQsIG9uY2UgdGhlIFByYWd1ZSBzZW5kZXIgZmFsbHMgYmFjayB0byBSZW5vIGJlaGF2aW9y
LCB0aGluZ3MgYXJlIGZpbmUuICBJbiBmcV9jb2RlbC9DQUtFIGN1cnJlbnRseSwgZG9lcyB0aGUg
QVFNIHN3aXRjaCBmcm9tIENFIG1hcmsgdG8gcGFja2V0IGRyb3AgYXQgc29tZSBoaWdoZXIgdGhy
ZXNob2xkIG9mIHNvam91cm4gdGltZT8gIElmIHNvLCB3b3VsZCB0aGlzIHByb3ZpZGUgZm9yIGEg
ZmFzdGVyIGZhbGwtYmFjayB0byBSZW5vIHRoYW4geW91IGNvbnNpZGVyZWQgaW4geW91ciBhbmFs
eXNpcz8gIEFsdGVybmF0aXZlbHksIGlmIGZxX2NvZGVsL0NBS0Ugd2VyZSB0byB0cmVhdCBFQ1Qo
MSkgYXMgbm9uLUVDVCAob3IgaW1wbGVtZW50IHRoZSBMNFMgc3R5bGUgRUNOKSB0aGlzIHdvdWxk
IGFnYWluIG5vdCBiZSBhbiBpc3N1ZSwgSSBiZWxpZXZlLiAgDQogICAgDQpbLi4uXQ0KICAgIChZ
ZXMsIHdlIGhhdmUgYSByZWFsIHNvbHV0aW9uIHNrZXRjaGVkIG91dCBmb3IgU0NFLiAgSXQgd2ls
bCBiZSB0ZXN0ZWQgc29vbi4gIFdlIGFscmVhZHkgaGF2ZSBydW5uaW5nIGNvZGUuKQ0KDQogICAg
IC0gSm9uYXRoYW4gTW9ydG9uDQogICAgDQogICAgX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCiAgICBpY2NyZyBtYWlsaW5nIGxpc3QNCiAgICBpY2NyZ0Bp
cnRmLm9yZw0KICAgIGh0dHBzOi8vd3d3LmlydGYub3JnL21haWxtYW4vbGlzdGluZm8vaWNjcmcN
CiAgICANCg0K


From nobody Wed Apr  3 17:28:21 2019
Return-Path: <chromatix99@gmail.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 4650C12031C for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 17:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 EFh_0zCgH6QX for <tsvwg@ietfa.amsl.com>; Wed,  3 Apr 2019 17:28:17 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 682951201D7 for <tsvwg@ietf.org>; Wed,  3 Apr 2019 17:28:17 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id v22so449505lje.9 for <tsvwg@ietf.org>; Wed, 03 Apr 2019 17:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3DQ6ucOQOYGk6BYBO+8JrgtWalAO0YZVOGWaOQgQGBc=; b=DnjhgkQj/Zj5uAHjlnuTIwey+aLM+/zFgZRwtKUcoTFhWkH8AI7ykHyjqrDh5XgVgE 6hpocrzQLW+5LpEQkrxiSaa5/FsrOg5YcANeYKVooBmK5Kn+7xdy8CBJ5BFpQ/j/S+rW e/7hwjGBKgDI2CbSDiuMtS8jRDsP9k1siUUDr/czACnhDz6FU6AsMpTMnj7nz5a88QlR nJnBT01XpgEAmpsYHQ2lgH/jk3FyV3BDx8T2fOdnnV/CypmMBnic0CVdVU9C2AkdUhlH Cot9Qdq769rl35cJcKiQwzS6p61VA/rhkubb1kdXQEKVlwYxxNG8Qfdgi2RidavLCrWQ V3tg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3DQ6ucOQOYGk6BYBO+8JrgtWalAO0YZVOGWaOQgQGBc=; b=abi3qtl9QrXwGie1oYtj53S2xH0IwED4CLWjSnA073/LhTrsyGOLYQA4+wyPRU10WF NJk/6QACjsOTs0a+A0w7JFdaOYvcDaiRGT9W9zmUZaUSSZmVTPSGR/X5C9/8s8I8d4qj HZF8lvHUHs901d8eZ8EMrKP8HDqT9FFN2tf+zjWdT6WDMiJVXjyPLUfulTMzs+8JzWYa ro/+TaNIKxRXIwbC3St2iCs4SbrwhIEMsbYo4c4pFxRD2KgiaBFTMGH2amA7HfinmCi7 Xvi+VIhGCFpURtqvd7R3QBtLqnAldSGCtjXzXIYwoe15sjgC5AH4iLqMWgHuE3cUKOR7 a8hA==
X-Gm-Message-State: APjAAAWAHWYlUg06wZIOz346iSMuivdMyEJXoYxyOZlK7ZG5QmG12t4C ju6Jbn2qXtj0fFQQVBAaivQ=
X-Google-Smtp-Source: APXvYqwjcNx2raET8Ad2xNtWt3yrgZvjNs6WXkGbxovYu7w8fCULQdXPGN10HBxvxjNsJOb9xsGhMQ==
X-Received: by 2002:a2e:978c:: with SMTP id y12mr1496549lji.70.1554337695487;  Wed, 03 Apr 2019 17:28:15 -0700 (PDT)
Received: from jonathartonsmbp.lan (85-76-23-211-nat.elisa-mobile.fi. [85.76.23.211]) by smtp.gmail.com with ESMTPSA id e14sm3922109ljk.45.2019.04.03.17.28.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Apr 2019 17:28:14 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com>
Date: Thu, 4 Apr 2019 03:28:13 +0300
Cc: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/G9KOlDMqmyaGy_mzqUxZKjchJ1Q>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 00:28:19 -0000

> On 4 Apr, 2019, at 2:28 am, Greg White <g.white@CableLabs.com> wrote:
>=20
> It will be the case that many such "equivalent devices" can (and will) =
support a dual-queue AQM (not fq), which (where available) will =
eliminate the need for ingress shaping, and provide a better result.    =
If fq_codel (or CAKE) were updated to utilize the L4S-style of ECN (or =
even just treat ECT(1) as non-ECT), this would be a non-issue.   How =
feasible would that be?=20

The present out-of-tree version of Cake supports an L4S-style =
high-fidelity ECN marking method, simultaneously with conventional ECN =
marking.  It does so using the SCE signalling method, with ECT(1) being =
an output rather than an input.  This is, in fact, the running code we =
had at the time of our TSVWG presentation.

Since then we have adapted a pair of FreeBSD endpoints to understand =
this new signal and respond appropriately to it (using a response =
function very similar to DCTCP).  Crucially, they continue to respond =
normally, with TCP-friendly semantics, to non-SCE middleboxes and/or =
when conversing with non-SCE endpoints.  These are early results from =
early code, but they prove the concept. =20

This bears repeating: we have effectively *rehabilitated* DCTCP.

It took three developers one week to do this, amidst many distractions.

> In fq_codel/CAKE currently, does the AQM switch from CE mark to packet =
drop at some higher threshold of sojourn time?

Technically yes, there is a failsafe intended for handling flows =
unresponsive to ECN (eg. due to blackholes) or insufficiently responsive =
to Codel-induced drops on Non-ECT flows.  However, this only kicks in =
when the queue backlog limit is reached.  It is a simple implementation =
of the BLUE algorithm, which ignores ECN and just drops, and is =
self-resetting.

> If so, would this provide for a faster fall-back to Reno than you =
considered in your analysis?

Not normally; the backlog limit is typically set to many RTTs' worth of =
queuing delay.  The mechanism has been carefully tested and works well, =
but rarely activates in practice.

> Alternatively, if fq_codel/CAKE were to treat ECT(1) as non-ECT (or =
implement the L4S style ECN) this would again not be an issue, I =
believe.

Perhaps, but I thought FQ AQMs weren't much of a problem to begin with - =
aside from the ingress-queuing problem?  I'm also reluctant to interpret =
ECT(1) or CE incompatibly with RFC-3168, unless given very good reason - =
and I currently have a good counter-argument.  If I may quote from that =
document, it does specifically contemplate use of the fourth codepoint =
to signal "mild congestion":

>    One possibility might have been for the data sender to use the =
fourth
>    ECN codepoint to indicate an alternate semantics for ECN.  However,
>    this seems to us more appropriate to be signaled using a
>    differentiated services codepoint in the DS field.
>=20
>    A second possible use for the fourth ECN codepoint would have been =
to
>    give the router two separate codepoints for the indication of
>    congestion, CE(0) and CE(1), for mild and severe congestion
>    respectively.


It goes on to suggest problems with incremental deployment of such a =
scheme, but I believe SCE overcomes those problems elegantly.  As I have =
previously pointed out, the remaining benefits of L4S can be realised =
through assigning a DSCP to a PHB with the desired characteristics, and =
having something like DualQ implement that PHB.

I can't help noticing, meanwhile, that DualQ seems to be designed for =
use wherever a single-queue AQM would normally fit (though I have my =
doubts that it will work on much hardware already deployed at crucial =
locations).  Yet at the same time, you claim such single-queue AQMs are =
presently (and will remain) so rare that you haven't even developed a =
method of reliably detecting them.  This seems like an important =
discrepancy.

Meanwhile, work continues.

 - Jonathan Morton=


From nobody Thu Apr  4 02:40:52 2019
Return-Path: <g.white@CableLabs.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 9BF56120477 for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 02:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 WIXwKYgxt-sr for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 02:40:47 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-eopbgr740129.outbound.protection.outlook.com [40.107.74.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98838120005 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 02:40:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SOtI+jEaMAQUxtWpchge4LAD91SIs/s9Ig7x1QM9GZY=; b=p9nza11iKo3zguBm9RLHQYm+Ec/D31LinBaKxs/mOKD+CycDkSU4/JO8EFtLVe2GJIElBNex02sTkpZIWpP0jrZkmSiHMHj5RqEoSgQAxwwG+VA0awd2igQX1TNcOChbRUoejph6MuZSVLuncFTbVQcUasix5RyjL99r5hCJXFI=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB5070.namprd06.prod.outlook.com (52.135.110.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.20; Thu, 4 Apr 2019 09:40:44 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c%6]) with mapi id 15.20.1750.021; Thu, 4 Apr 2019 09:40:44 +0000
From: Greg White <g.white@CableLabs.com>
To: Jonathan Morton <chromatix99@gmail.com>
CC: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: [iccrg] [tsvwg]  IETF104 ICCRG TCP Prague presentation
Thread-Index: AQHU6ksFATQlV6AwuEyVhJCWJn+a66YrJhqA////44CAAKshgA==
Date: Thu, 4 Apr 2019 09:40:44 +0000
Message-ID: <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com>
In-Reply-To: <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.14.0.181208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com; 
x-originating-ip: [79.173.153.218]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0491f9bd-ee88-4c55-8068-08d6b8e19c0d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR06MB5070; 
x-ms-traffictypediagnostic: SN6PR06MB5070:
x-microsoft-antispam-prvs: <SN6PR06MB5070A8715997F44ED055FCA7EE500@SN6PR06MB5070.namprd06.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39850400004)(346002)(376002)(136003)(366004)(199004)(189003)(81166006)(2906002)(6916009)(8676002)(36756003)(81156014)(229853002)(25786009)(33656002)(6512007)(316002)(5660300002)(53936002)(54906003)(58126008)(3846002)(6116002)(14454004)(6486002)(83716004)(6506007)(2616005)(86362001)(71190400001)(102836004)(14444005)(97736004)(305945005)(7736002)(82746002)(8936002)(66574012)(99286004)(186003)(446003)(6436002)(93886005)(476003)(1411001)(6246003)(66066001)(76176011)(106356001)(68736007)(105586002)(11346002)(478600001)(4326008)(26005)(71200400001)(486006)(256004)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB5070; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: rz3ytdVRUJtbP9N34wHhciWm7Wnr/Lp/YoGA/clYJqMtft1ScvDnhB8Lgm1bjjg2WfEO0oh9bw594l1Jxkglzp4OdJ+WzMSxYNmKmPNQh3YgQ+P4KO6oYvS1RNqdo9KSU1FyLQ9jc6BuTjQvCsRHaR7OgzHjiJzpwVb/A+H566Gzay+y+Ee4Eh9JRtAG1BU8+s2Q6bkRMg3lepUG6drfHYOPKX40bCyJd0vjx8zMhkJnw4IpGQS2JesQw8sBE8yJwpCRuAYs//V58RJ1h6uRCWKwC9leCouhV9wLZZJQeU+6Y1DvjU1LZxcy1bT9G8J25/kwOUQ3BEhPUOq38awrZEqVWjawnIX4WuW2fB8a/mTOK7Ey73CN+vQTkVNRExAd1BFJBfh+XmdN/KyPZPtmvTSjJbfdCkJLsFWLqEa+XBc=
Content-Type: text/plain; charset="utf-8"
Content-ID: <358E3B2229DF46449A86510A0EB5D483@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0491f9bd-ee88-4c55-8068-08d6b8e19c0d
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 09:40:44.3005 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB5070
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/HBc7IlCnT8IW_AelzWoVjcf8l7M>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 09:40:51 -0000

DQoNCu+7v09uIDQvNC8xOSwgMToyOCBBTSwgIkpvbmF0aGFuIE1vcnRvbiIgPGNocm9tYXRpeDk5
QGdtYWlsLmNvbT4gd3JvdGU6DQpbLi4uXSAgICANCiAgICBUaGUgcHJlc2VudCBvdXQtb2YtdHJl
ZSB2ZXJzaW9uIG9mIENha2Ugc3VwcG9ydHMgYW4gTDRTLXN0eWxlIGhpZ2gtZmlkZWxpdHkgRUNO
IG1hcmtpbmcgbWV0aG9kLCBzaW11bHRhbmVvdXNseSB3aXRoIGNvbnZlbnRpb25hbCBFQ04gbWFy
a2luZy4gIEl0IGRvZXMgc28gdXNpbmcgdGhlIFNDRSBzaWduYWxsaW5nIG1ldGhvZCwgd2l0aCBF
Q1QoMSkgYmVpbmcgYW4gb3V0cHV0IHJhdGhlciB0aGFuIGFuIGlucHV0LiAgVGhpcyBpcywgaW4g
ZmFjdCwgdGhlIHJ1bm5pbmcgY29kZSB3ZSBoYWQgYXQgdGhlIHRpbWUgb2Ygb3VyIFRTVldHIHBy
ZXNlbnRhdGlvbi4NCiAgICANCltHV10gSGFzIGFueSBwcm9ncmVzcyBiZWVuIG1hZGUgb24gYSB2
YXJpYW50IG9mIENha2UgdGhhdCB1dGlsaXplcyB0aGUgTDRTIEVDVCgxKSBzZW1hbnRpYz8gIEl0
IHdvdWxkIGJlIHVzZWZ1bCBmb3IgY29tcGFyaXNvbiBwdXJwb3Nlcy4gIA0KDQpbLi4uXSAgICAN
CiAgICA+IEFsdGVybmF0aXZlbHksIGlmIGZxX2NvZGVsL0NBS0Ugd2VyZSB0byB0cmVhdCBFQ1Qo
MSkgYXMgbm9uLUVDVCAob3IgaW1wbGVtZW50IHRoZSBMNFMgc3R5bGUgRUNOKSB0aGlzIHdvdWxk
IGFnYWluIG5vdCBiZSBhbiBpc3N1ZSwgSSBiZWxpZXZlLg0KICAgIA0KICAgIFBlcmhhcHMsIGJ1
dCBJIHRob3VnaHQgRlEgQVFNcyB3ZXJlbid0IG11Y2ggb2YgYSBwcm9ibGVtIHRvIGJlZ2luIHdp
dGggLSBhc2lkZSBmcm9tIHRoZSBpbmdyZXNzLXF1ZXVpbmcgcHJvYmxlbT8gIA0KDQpbR1ddIFdl
bGwsIGEgZ29hbCB3b3VsZCBiZSBmb3IgRlEgQVFNcyB0byBwcm92aWRlIGFwcHJvcHJpYXRlIGhp
Z2gtZmlkZWxpdHkgY29uZ2VzdGlvbiBzaWduYWxzIHRvIEw0UyBmbG93cyBzbyB0aGF0IHRoZXkg
Y2FuIGFjaGlldmUgYWxsIGZvdXIgTHMgYW5kIHRoZSBTLiAgRmFpbGluZyB0aGF0LCB0byBub3Qg
cHJvdmlkZSB3ZWFrZXIgY29uZ2VzdGlvbiBzaWduYWxzIGZvciBMNFMgZmxvd3MgYXMgY29tcGFy
ZWQgdG8gY2xhc3NpYyBUQ1AuICBJdCBpc24ndCBhIHByb2JsZW0gZnJvbSBhIGZhaXJuZXNzIHBl
cnNwZWN0aXZlLCBidXQgdGhlIGdvYWwgaXMgbG93IGxhdGVuY3kgYWZ0ZXIgYWxsLiAgICBUaGlz
IHNlZW1zIGxpa2UgYSBmYWlybHkgc2ltcGxlIGNoYW5nZSB0byBGUS4NCg0KICAgIEknbSBhbHNv
IHJlbHVjdGFudCB0byBpbnRlcnByZXQgRUNUKDEpIG9yIENFIGluY29tcGF0aWJseSB3aXRoIFJG
Qy0zMTY4LCB1bmxlc3MgZ2l2ZW4gdmVyeSBnb29kIHJlYXNvbiAtIGFuZCBJIGN1cnJlbnRseSBo
YXZlIGEgZ29vZCBjb3VudGVyLWFyZ3VtZW50LiAgSWYgSSBtYXkgcXVvdGUgZnJvbSB0aGF0IGRv
Y3VtZW50LCBpdCBkb2VzIHNwZWNpZmljYWxseSBjb250ZW1wbGF0ZSB1c2Ugb2YgdGhlIGZvdXJ0
aCBjb2RlcG9pbnQgdG8gc2lnbmFsICJtaWxkIGNvbmdlc3Rpb24iOg0KICAgIA0KICAgID4gICAg
T25lIHBvc3NpYmlsaXR5IG1pZ2h0IGhhdmUgYmVlbiBmb3IgdGhlIGRhdGEgc2VuZGVyIHRvIHVz
ZSB0aGUgZm91cnRoDQogICAgPiAgICBFQ04gY29kZXBvaW50IHRvIGluZGljYXRlIGFuIGFsdGVy
bmF0ZSBzZW1hbnRpY3MgZm9yIEVDTi4gIEhvd2V2ZXIsDQogICAgPiAgICB0aGlzIHNlZW1zIHRv
IHVzIG1vcmUgYXBwcm9wcmlhdGUgdG8gYmUgc2lnbmFsZWQgdXNpbmcgYQ0KICAgID4gICAgZGlm
ZmVyZW50aWF0ZWQgc2VydmljZXMgY29kZXBvaW50IGluIHRoZSBEUyBmaWVsZC4NCiAgICA+IA0K
ICAgID4gICAgQSBzZWNvbmQgcG9zc2libGUgdXNlIGZvciB0aGUgZm91cnRoIEVDTiBjb2RlcG9p
bnQgd291bGQgaGF2ZSBiZWVuIHRvDQogICAgPiAgICBnaXZlIHRoZSByb3V0ZXIgdHdvIHNlcGFy
YXRlIGNvZGVwb2ludHMgZm9yIHRoZSBpbmRpY2F0aW9uIG9mDQogICAgPiAgICBjb25nZXN0aW9u
LCBDRSgwKSBhbmQgQ0UoMSksIGZvciBtaWxkIGFuZCBzZXZlcmUgY29uZ2VzdGlvbg0KICAgID4g
ICAgcmVzcGVjdGl2ZWx5Lg0KICAgIA0KW0dXXSBJIGRvbid0IGJlbGlldmUgdGhhdCB0aGUgUkZD
cyBhcmUgb24geW91ciBzaWRlIGhlcmUuICAgUkZDIDMxNjggY29udGVtcGxhdGVzLCBhbmQgcmVq
ZWN0cywgdGhhdCBkZWZpbml0aW9uIG9mIEVDVCgxKSwgc28gSSdtIG5vdCBzdXJlIGhvdyB5b3Ug
cmVhZCBpdCBhcyBzdXBwb3J0aW5nIHRoZSB1c2UuIFJGQyAzMTY4IGV4cGxpY2l0bHkgZGVmaW5l
cyBFQ1QoMSkgYXMgYmVpbmcgYSB0cmFuc3BvcnQgc2VuZGVyIHNpZ25hbCB0aGF0IGl0IGlzICJF
Q04gQ2FwYWJsZSBUcmFuc3BvcnQiLiAgSSBkb24ndCBzZWUgaG93IHlvdSBjYW4gY2xhaW0gYWRo
ZXJlbmNlIHRvIFJGQyAzMTY4LCB5ZXQgdXNlIEVDVCgxKSB0byBtZWFuIChTKUNFLiAgTW9yZW92
ZXIsIFJGQyAzMTY4IGhhcyBiZWVuIHVwZGF0ZWQgYnkgKFN0YW5kYXJkcy1UcmFjaykgUkZDIDgz
MTEsIHdoaWNoIGVuYWJsZXMgdGhlIEw0UyBleHBlcmltZW50cywgYW5kIHdoaWNoIHRoZSBTQ0Ug
YXBwcm9hY2ggYWxzbyB2aW9sYXRlcy4gIA0KDQpbLi4uXSANCiAgICBJIGNhbid0IGhlbHAgbm90
aWNpbmcsIG1lYW53aGlsZSwgdGhhdCBEdWFsUSBzZWVtcyB0byBiZSBkZXNpZ25lZCBmb3IgdXNl
IHdoZXJldmVyIGEgc2luZ2xlLXF1ZXVlIEFRTSB3b3VsZCBub3JtYWxseSBmaXQgKHRob3VnaCBJ
IGhhdmUgbXkgZG91YnRzIHRoYXQgaXQgd2lsbCB3b3JrIG9uIG11Y2ggaGFyZHdhcmUgYWxyZWFk
eSBkZXBsb3llZCBhdCBjcnVjaWFsIGxvY2F0aW9ucykuICANCg0KW0dXXSBXZSBoYXZlIHdvcmtl
ZCB2ZXJ5IGNsb3NlbHkgd2l0aCBhbGwgb2YgdGhlIERPQ1NJUyBlcXVpcG1lbnQgdmVuZG9ycyB0
byBlbnN1cmUgdGhhdCBMb3cgTGF0ZW5jeSBET0NTSVMgKGluY2x1ZGluZyBkdWFsLXF1ZXVlKSBp
cyBpbXBsZW1lbnRhYmxlIHZpYSBhIGZpcm13YXJlIHVwZGF0ZSB0byBBTEwgZXhpc3RpbmcgRE9D
U0lTIDMuMSBDTXMgYW5kIENNVFMgdGhhdCBhcmUgaW4gdGhlIGZpZWxkIHRvZGF5LiAgSW4gc29t
ZSBtYXJrZXRzIHRoYXQgaXMgbW9yZSB0aGFuIDkwJSBvZiBkZXBsb3llZCBDTVRTcy4gSSBvYnZp
b3VzbHkgY2FuJ3Qgc3BlYWsgdG8gb3RoZXIgYWNjZXNzIG5ldHdvcmsgdGVjaG5vbG9naWVzLCBi
dXQgdG8gdGhlIGV4dGVudCB0aGF0IGZvcndhcmRpbmcgYXJjaGl0ZWN0dXJlcyBhcmUgc2ltaWxh
ciwgSSB3b3VsZCBwcmVzdW1lIHRoYXQgZG91YmxpbmcgdGhlIG51bWJlciBvZiBxdWV1ZXMgaXMg
c2lnbmlmaWNhbnRseSBzaW1wbGVyIHRoYW4gbXVsdGlwbHlpbmcgYnkgMTAwMC4NCg0KICAgIFll
dCBhdCB0aGUgc2FtZSB0aW1lLCB5b3UgY2xhaW0gc3VjaCBzaW5nbGUtcXVldWUgQVFNcyBhcmUg
cHJlc2VudGx5IChhbmQgd2lsbCByZW1haW4pIHNvIHJhcmUgdGhhdCB5b3UgaGF2ZW4ndCBldmVu
IGRldmVsb3BlZCBhIG1ldGhvZCBvZiByZWxpYWJseSBkZXRlY3RpbmcgdGhlbS4gIFRoaXMgc2Vl
bXMgbGlrZSBhbiBpbXBvcnRhbnQgZGlzY3JlcGFuY3kuDQoNCltHV10gVGhlIGNvbmNlcm4gd291
bGQgYmUgc2luZ2xlLXF1ZXVlICpFQ04qIEFRTXMuIFNpbmdsZS1xdWV1ZSBwYWNrZXQgZHJvcCBB
UU1zIGRvIGV4aXN0Lg0KICAgIA0KICAgIE1lYW53aGlsZSwgd29yayBjb250aW51ZXMuDQoNCltH
V10gV2h5PyAgSXQgc2VlbXMgdG8gbWUgdGhhdCB0aGUgTDRTIGFwcHJvYWNoIGNhbiBiZSBpbXBs
ZW1lbnRlZCBlYXNpbHkgaW4gZnFfY29kZWwgYW5kIENBS0UsIGFzIHdlbGwgYXMgaW4gc3lzdGVt
cyB0aGF0IGNhbiBvbmx5IHJlYWxpc3RpY2FsbHkgc3VwcG9ydCBkdWFsLXF1ZXVlLiAgSXQgaGFz
IGJlZW4gZGVtb25zdHJhdGVkIHRvIHByb3ZpZGUgc2NhbGFibGUgdGhyb3VnaHB1dCBhbmQgdWx0
cmEtbG93IGxvc3MgYW5kIHF1ZXVpbmcgZGVsYXkgKHdoaWNoLCBJIHRoaW5rLCBpcyB0aGUgZ29h
bCBvZiBTQ0UgYXMgd2VsbCksIGFuZCBoYXMgcXVpdGUgYSBiaXQgb2Ygc3VwcG9ydCBhbmQgbW9t
ZW50dW0gYmVoaW5kIGl0LiBUaGUgcGhpbG9zb3BoaWNhbCBkZWJhdGUgYXMgdG8gd2hpY2ggaXMg
YmV0dGVyLCBkdWFscS1jb3VwbGVkLWFxbSBvciBGUSwgY2FuIGNvbnRpbnVlIGFuZCBpbXBsZW1l
bnRlcnMgY2FuIGNob29zZSB3aGljaGV2ZXIgdGhleSBsaWtlLiAgSSBkb24ndCBkb3VidCB0aGF0
IHRoZSBTQ0Ugc2lnbmFsaW5nIG1ldGhvZCBjb3VsZCBiZSB1c2VkIGluIGEgdmFyaWFudCBvZiBE
Q1RDUCwgYnV0IHRoZSAqaHVnZSogZG93bnNpZGUgaXMgdGhhdCBpdCBjYW4gb25seSB3b3JrIG9u
IGJvdHRsZW5lY2sgbGlua3MgdGhhdCBhcmUgYWJsZSAob3Igd2lsbGluZykgdG8gc3VwcG9ydCBG
USwgd2hpY2ggd2lsbCBiZSBwcmVjaW91cyBmZXcuICBJbiAyLTMgeWVhcnMnIHRpbWUsIDEwcyBv
ZiBtaWxsaW9ucyBvZiBhY3R1YWwgYm90dGxlbmVjayBsaW5rcyBpbiBicm9hZGJhbmQgbmV0d29y
a3Mgd2lsbCBiZSBzdXBwb3J0aW5nIGR1YWwtcXVldWUuICBJdCBzZWVtcyB0aGF0IHRoZSBvbmx5
IHJlYWwgYXJndW1lbnQgaW4gZmF2b3Igb2YgdGhlIFNDRSBzaWduYWxpbmcgbWV0aG9kIGlzIHRo
ZSBmYWxsYmFjayBpbiBwcmVzZW5jZSBvZiBzaW5nbGUtcXVldWUgY2xhc3NpYyBFQ04gKHVubGVz
cyB5b3UgdGhpbmsgYmxvY2tpbmcgaW1wbGVtZW50ZXJzIGZyb20gc3VwcG9ydGluZyBkdWFsLXF1
ZXVlIGlzIHNvbWUga2luZCBvZiBwZXJ2ZXJzZSBiZW5lZml0KS4gIEhlbHAgYW5hbHl6aW5nIChh
bmQgYWRkcmVzc2luZyBpZiBuZWVkIGJlKSB0aGF0IHNpdHVhdGlvbiB3b3VsZCBiZSB0aGUgbW9z
dCBlZmZlY3RpdmUgd2F5IG9mIGFjaGlldmluZyB0aGUgc2hhcmVkIGdvYWwgb2YgbG93IGxhdGVu
Y3kgc2NhbGFibGUgY29uZ2VzdGlvbiBjb250cm9sLiAgQ29udGludWluZyB0byBwdXNoIGZvciAo
b3Igd29yc2UsIGRlcGxveSkgYW4gaW5jb21wYXRpYmxlIHNvbHV0aW9uIGp1c3QgaW5jcmVhc2Vz
IHRoZSByaXNrIHRoYXQgbm8gb25lIHdpbGwgYmUgYWJsZSB0byBhY2hpZXZlIHRoYXQgZ29hbC4N
Cg0KICAgIA0KDQoNCg==


From nobody Thu Apr  4 03:06:40 2019
Return-Path: <moeller0@gmx.de>
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 431A812003F; Thu,  4 Apr 2019 03:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 Ove93leaC9O5; Thu,  4 Apr 2019 03:06:36 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 25D2E120005; Thu,  4 Apr 2019 03:06:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554372352; bh=4ZKzF+sQTaNE7Ww05KssCB+KDBI6j0/0u73Dhvndxjg=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=Kuo+G7CqIO+tC3zQr9T+T6kaJCz0SJsck3/n7FLkCVTl6gDqrgOZhFnrhUfwQ7ioW 0Uwh1CXWGSLhMPjpDkJIaTIFJJsefrK/5sDSBQ2W/SlXS9Qi8ZFTQ7VMy+TotNqFkX /6B3UC5KeoJVzZjDdvCKXajoG7UV/21abVcO7Q1s=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.12.10] ([134.76.241.253]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MCtql-1h3Ug709b9-009jLY; Thu, 04 Apr 2019 12:05:52 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net>
Date: Thu, 4 Apr 2019 12:05:49 +0200
Cc: iccrg@irtf.org, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB2A0424-E208-40B1-86DD-E74F786A1BE1@gmx.de>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net>
To: Bob Briscoe <in@bobbriscoe.net>
X-Mailer: Apple Mail (2.3445.9.1)
X-Provags-ID: V03:K1:68lDL8dIVSbspmH8pUIXcbp6BMJQs3vjlt+jIEjcHpxro2R6hVS 8NTFM/3fG0SI8xsDwt5L7SZWNvOStVho3CpOpCOAb/fxj3XuDYqTGlv/T2CP+0BWusTurna 48cnPxyTeo4imcf9EhF7uZFHKG/8OTM4QRnRqF8vdXm+ztYF+xZ1pr4OgvOM/qO7OQAc63O K8AHJrwS8IE6CJa9xYYKg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:wIi6VloXOlo=:GfHHDP56cignjfd+0R1CV3 RoA4+GWuWczPH/HzHcbzMUiASSVh6/iEtiFceZ9LazmRq8WZ0+B9ks89OSBcQCCd6MjD2ce5H YgUwse4dvL2B8v5kvrk5oTqzYXC5JAbK1E5HTgN9LOU3uTOzi6kquHRETdAmeUJTjcjBAnHVT pcBzpw0Bre7VhDf2fYeFamZniCy52QnszajjRDfbLUIRVYUQ3H0E+kAoTAllTsKkksZpp49j3 rUnSh9fCLrVGgrKCw7VzcbLqJph0vHl3Eeox0QTARnkz6/p3yzETSKH0eFKVLaiUQ4OBR3Vo6 x4OUpUgJvEHR1JRrZs961FUy7oFMGlBP0itycZ2h7A8+mGiyxKOIwWXSHaScxo8i7Gk2DpoUy i9SOih3eOng4Aro4rocR3lZa6xmH71kGQPPiVVi4VV4q4FUqgpv2CycsDvbGsS3c8tw13BZSj f+BGluf8NEUensaaJOgZy3OndtHrmg8Z11y0xydRTifTlY6WYp8bOMK9nVwm8JcUGmKZ2r+q5 TCccHiq/utjOl2mq9Np/otZILzMBcjQvGvtGg19/0AafE0xbkieUFfyb7lQXbOyoU93mwvGxg bjH7ta5IlRf/dJL0CMswwaewWoqgzRen6f4iK0X3MWCb3oIt8AeZ5SeZIb9DiflNdycidtpVa nP0AGu12GCfnD+hPnsshwiNnKWcdbXzvWcZGmLJiDdQw/TxWMWO0vfY905quWj5KieHDn+4zA jkykEu9HT3VkruT2zuyfJGt9g8an0IoFHD/nxo57G/kzTA/yL5VYTh1hdqX45Hl9rfXDUeO8l i9rHbWWaglAX01ydN5NySQrEmd8N1dEQ8av7+rEH4e85dE/wD991Fv7hUUcmCQSTbJlyycnLE 9WUVYwTEzz8ePD56xwH1xNOW+42fLEv+lU3CsyQSDYGrNuQJMIra1aFjAnXQ2cpan0C96PxEW rMUktgm9AEQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ksA5xW8JDUnmQbYjb3jKB4mz3zI>
Subject: Re: [tsvwg] [iccrg] IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 10:06:39 -0000

Hi Bob,

thanks for your detailed response.


> On Apr 3, 2019, at 19:40, Bob Briscoe <in@bobbriscoe.net> wrote:
>=20
> Sebastien, (adding tsvwg, given this is all part of the decision over =
L4S/SCE),
>=20
> On 02/04/2019 12:38, Sebastian Moeller wrote:
>> I finally got around to see the TCP Prague presentation, nice, =
especially the part around slide 11 "Fallback to Reno-friendly on =
Classic ECN" caught my interest.
>>=20
>> The claim made there is that L4S's inability to properly deduce the =
type of CE signal (normal ECN response expected versus DCTCP-like ECN =
response expected) would only matter in the case of ECN-marking single =
queue AQMs and not for flow-queueung AQMs, and I would like to argue =
that that should be measured rather than solved by declaration.
>>=20
> [BB] I don't know whether you just looked at my slides without the =
voice track. But the voice track makes it clear that is exactly what =
I've been setting up.

	I also listened to the video, but it seems I was confused (I am =
easily confused). So I whole heartedly agree with this approach.

>=20
> To save those who weren't in the room from having to sit through the =
audio, I said that there are two sets of contradictory measurements:=20
> 	=E2=80=A2 those from 'academic' active measurement studies that =
have found hardly any CE
> 	=E2=80=A2 those from Apple's passive measurements on Apple =
devices that have found significant localized amounts of CE.
> My hypothesis is that the active measurements aren't seeing much CE, =
cos they don't generate enough traffic themselves to congestion the link =
and they would have to coincide with other traffic to see it passively.

	I also note, that SQM for example defaults to ECN off on the =
path from the router towards the internet (rationale, with slow uplinks =
often seen at internet access links the serialization delay from a =
single packet can be painful already, this rationale might up for =
re-evaluation in the light of the newer graded types of responses to ECN =
marks at the core of the L4S/SCE proposals, but I digress). The =
consequence of this decision is that the likelyhood of seeing ECN marks =
is reduced making it harder to measure. If we had a significant number =
of sqm-devices in the field we might help with switching ECN on on the =
uplink as well, but we have no reliable way to estimate and no =
"telemetrics" from deployed instances

>=20
> I said, in short, I believe the active measurements are more likely =
wrong, and passive more likely right.
>=20
> Nonetheless the CE that Apple measured could be consistent with =
classic ECN marking from FQ-CoDel, e.g. in OpenWRT devices, which would =
protect competing flows from L4S flows.
> Apple saw CE "mainly in the uplink", which is likely to be FQ-CoDel. =
And the smaller amount seen in the downlink could have been peer-to-peer =
flows that had been marked on entry to the uplink by an FQ-CoDel home =
router.
>=20
> With the help of others, I've devised a test for FQ vs FIFO, but we =
need to find where the CE-marking routers are before we apply the test =
(a scatter-gun approach would be infeasible given the need to congest =
the link). In discussions with Apple folks, we think it's best to run =
tests at the CDN end, to identify the network prefixes where CE is =
appearing (the client end used in the original tests usually doesn't =
know its public IP address).

	Sounds reasonable, with the potential unhappyness of ISPs for =
the congestion, but then this is similar to what a speedtest does (or =
netalyzr).

>=20
> If we find any CE in the downlink from the CDN, that will disprove my =
peer-peer FQ hypothesis. But it won't prove that it's from a FIFO. The =
test for FQ vs FIFO is not straightforward, and I haven't yet worked out =
how we run it in the relevant direction over the paths where we find CE =
(not least 'cos that would involve collecting and identifying client IP =
addresses, which raises privacy concerns). I suspect we'll need to =
co-opt some volunteers in the affected localities, somehow.
>=20
> An alternative to inline testing will be to find out whether the =
networks where CE is being seen have supplied their customers with =
routers with FQ-CoDel enabled. That won't prove conclusively that all =
the CE is coming from FQ-CoDel, but we can only go so far in trying to =
prove a negative.

	I wonder how are reading out the CE marking at all? Is the idea =
to place measurement devices between CDN end-hosts and the CPE and look =
at the IP headers, or is the plan to use a specific application?

>=20
>>=20
>>=20
>> Consider the following case, that get's more and more common: traffic =
shaping for both ingress and egress somewhere on the end-customer side =
of an internet access link. For egress I agree with the rationale, that =
flow-queueing/fair-queueung should deal with flows that appear =
unresponsive sooner or later (but I note that this still will increase =
the memory required for the queueing and should not be considered ideal =
behavior).
>> But for ingress shaping downstream of the "true" bottleneck (I am =
simplifying over some details here) this rationale falls apart, the =
unexpected packets the L4S sender kept sending since it misinterpreted =
the CE mark, will still hog valuable bandwidth of the internet access =
link, and hence fair queuing on the home end of the true bottleneck will =
not isolate that homenet from the L4S misunderstanding.
>>=20
> [BB] For the avoidance of doubt, I think you're using 'egress' to mean =
[home -> Internet] (I use it for the other direction, but I can work =
with your terminology).

	Sorry, this really is not my field so my nomenclature is =
probably idiosyncratic, but yes, I see this from the vantage point of =
the home network, and upload traffic egress from my network, while =
download traffic ingresses, from the other side of the access links, =
these direction can be defines the other way around.

>=20
> In the [Internet -> home] direction, you are right that FQ on the home =
end would not isolate the access link from a misunderstanding of any CE =
marking. But I'm not suggesting it could or would.

	But that is the use-case I am concerned about, as with all the =
promises (better) AQM at the head-end brings, it will IMHO not eradicate =
the use of "ingress"-shaping on the customer side, as that is required =
to allow meaning-full prioritization and to establish the =
bandwidth-sharing model for the home network (whre typically =
per-flow-fairness is more desirable than no fairness, but where =
per-internal-IP-address-fairness might be even more desirable, =
Jonathan's cake actually offers that capability, but since this =
absolutely requires access to the internal-IP-addresses will require the =
AQM ti live inside the NAT typical for IPv4 access links).

> The question is about the machine at the Internet side of the access =
link (BRAS, CMTS, etc) that is queuing traffic into the access link =
towards the home. We can be nearly certain it is not doing FQ (these =
machines serve thousands of customers, so I don't believe any use FQ). =
The question is whether we can find one of these non-FQ machines that =
has an AQM enabled that does CE marking.
>=20
> That's what we're trying to find. It's of course hard to prove a =
negative - that none exist. All we can hope to do is measure a sample of =
the paths we find.

	Okay, but any idea what to do about my hobbyhorse, short of =
completely disabling L4S for all nodes in the home network (which seems =
heavy-handed, given that L4S's goal "low latency networking" is IMHO =
desirable for all end-users)? This kind of set-up is not as unique as it =
might seem, and typically users employing it are latency sensitive and =
hence certainly part of the audience which might like the L4S approach =
other-wise.

>=20
>=20
> A nit: DCTCP is not /unresponsive/. It responds to congestion, but as =
if it is equivalent to a number of 'classic' (Reno-friendly) TCP flows.

	I agree, hence the term "appear unresponsive", the problem isn't =
DCTCP here, but a misunderstanding between AQM and involved TCP.

>=20
>>=20
>> I would be delighted to learn where my assumptions are wrong...
>>=20
> Regards

	Thanks for your kind and informative response.

Best Regards
	Sebastian

>=20
>=20
>=20
> Bob
>=20
>>=20
>> Regards
>> 	Sebastian Moeller
>>=20
>> _______________________________________________
>> iccrg mailing list
>>=20
>> iccrg@irtf.org
>> https://www.irtf.org/mailman/listinfo/iccrg
>=20
> --=20
> ________________________________________________________________
> Bob Briscoe                              =20
> http://bobbriscoe.net/


From nobody Thu Apr  4 03:19:29 2019
Return-Path: <moeller0@gmx.de>
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 647BA12047E; Thu,  4 Apr 2019 03:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 GhtbkkigrOFz; Thu,  4 Apr 2019 03:19:25 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 7A90D1206A3; Thu,  4 Apr 2019 03:19:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554373120; bh=li62UTNTFNpGCY6IoKf+4NtPWjdUtB95yTH/hiroPdY=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=EkrrmycLF/lT3H20oA6V7/njIOjjR0Un010+epKGu+GrXwdI64I4E7uXWt4NcEmCa 7BI+uMQlJUTh21tWYi8obQWIE8K1gcFIdjm6vvz4U9l7Kv5WTrKKXbvh9nOJF+c0SM Qf9GaJD4bFw+gA2GtcPYvv+upZ1nxUUsfNaI3lcw=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.12.10] ([134.76.241.253]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MOx4J-1hFYEJ1Fep-006MtG; Thu, 04 Apr 2019 12:18:40 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com>
Date: Thu, 4 Apr 2019 12:18:38 +0200
Cc: Bob Briscoe <in@bobbriscoe.net>, iccrg@irtf.org, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8E5DB35-5352-4EC1-A242-ED670E02822C@gmx.de>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Provags-ID: V03:K1:R5wVuoNi8llvcrz4uPOJD3BJCzcOT3Q4NSOxiIwYw4Jl9QfC1Er SfZvnZIS+S+sAdtweUMv3am9LWRGgfuLZ0ouwqN0GoXVXDCCUkp9bDb79XOxM/nFMCXKabt xZmiHB6Xlmsn4euf/u2yhLceSaAupNenINPmdlRapCDNgSjjJcWkEuVnM5X8Up+MBaYSAeH hyU6cHnbVUskARFqtl+cw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:P3j8HRsHifY=:qzp76B3dYsN87Gx5OGMktj 3+rP+M/xktxEI9uE3gVaoVRLN4hH+Ch6ZTEW8IxIKM/Mg/cCAgBVR13Rpt+AgD4r8eWVULqkA H8AkVn923KK1pa84Ggk9XE/n2fvybyaMdAC3ujkTY1noMYeMxFFMA6DcvI+VaB2pj3S4lmNhu av8lbJ53hOmahszVkxJF6xn94Dk7cqLcTcHCEUHBfNwt4xzTnyQy1wMHFxR30fi/srlUZh/y0 MleP7lkYdhKXI8DBJqBlVM9pxd7GfkQXdRq+ZjjpMSZqane8WryqMWBdtvP+qOyQZiGHmXC75 QKbNPiblTgbUoSx8u7ovfMx/epmD3Knptimjy5U4TlWwEITEVz1+oGejGCn8n4ArdP0eBedWN opQAtMZEjXLK4nkwoI/COpCFQKkRoF8nJvQeerU8m2E+rnb+VZ3KhQN+wLLDa7xNfK1AUHr+b 2FTPaBTbCOXzHpnxH5gEVVqXlNaOVlAId5XojS3eW35ZrBDt2VwDKX3GzGVm+U4RjKUzFujTB hgnCaL5ODDVVEqeG2B2qVrs9E9xeNzHYgMM3KTKfWNMNfjw5GEPqbs+6DbOOS4wqw97HvSAEc +WqTKG3W9iUV6vMyRENXYBYTT1d/FpxRANIIXNrbyyaBTeXzCtuJpQTR8iOKK0e08ZtpO93+d T/5LA8U5Y+f8/EAWpAeeYoIqKv7oFZND6YrlnckJGrcvPJC6DI0ATdYf6X3DOxXaHSLAcfhO0 A0WuEWs8d4cCXmOI0KN1LN8Q0hpWSuwsR7i5P9a6UBrQvBkAUlDWcDyBKXa85OBzQ9UxTPM2k 1qWq4IfTVhk5h4oz3ATPbJ3R6AGw8UsbaM5uH9HK4e1jtQh0hF1k3HlI3O6dTb76A+3XLYuAI w+zdpRmRhIGvIYXRbAC3NYktpEYvaFBOHjTYAPd44j97DaWC/AMbOEvUdpiYVT+bdG/codKWX GzmsfmQLkrA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/arWy2HTiGOrD2QUAv4zckX_GTps>
Subject: Re: [tsvwg] [iccrg] IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 10:19:27 -0000

Hi Jonathan,


> On Apr 3, 2019, at 20:28, Jonathan Morton <chromatix99@gmail.com> =
wrote:
>=20
>> On 3 Apr, 2019, at 8:40 pm, Bob Briscoe <in@bobbriscoe.net> wrote:
>>=20
>> To save those who weren't in the room from having to sit through the =
audio, I said that there are two sets of contradictory measurements:=20
>> 	=E2=80=A2 those from 'academic' active measurement studies that =
have found hardly any CE
>> 	=E2=80=A2 those from Apple's passive measurements on Apple =
devices that have found significant localized amounts of CE.
>> My hypothesis is that the active measurements aren't seeing much CE, =
cos they don't generate enough traffic themselves to congestion the link =
and they would have to coincide with other traffic to see it passively.
>>=20
>> I said, in short, I believe the active measurements are more likely =
wrong, and passive more likely right.
>=20
> This is actually reasonable.  However your slides were very unclear =
about this, which I think led to unnecessary confusion.
>=20
>> Nonetheless the CE that Apple measured could be consistent with =
classic ECN marking from FQ-CoDel, e.g. in OpenWRT devices, which would =
protect competing flows from L4S flows. Apple saw CE "mainly in the =
uplink", which is likely to be FQ-CoDel. And the smaller amount seen in =
the downlink could have been peer-to-peer flows that had been marked on =
entry to the uplink by an FQ-CoDel home router.
>=20
> It is actually common for OpenWRT devices to include "ingress shaping" =
to exert some control over bufferbloat on downloads.  The terminology, =
in fact, comes from this practice, as the port in question is facing the =
WAN link and has two qdiscs attached, one for egress traffic towards the =
Internet, and one for ingress traffic received from the Internet.

	+1

>=20
> A lower rate of observed marking on downloads could be due to the =
greater difficulty of driving the download direction into saturation, =
especially given a backhaul network that may be oversubscribed in many =
ISPs during peak hours, and thus the greater difficulty of properly =
configuring an ingress shaper.  It is of course better for AQM to be =
installed on the upstream side of where the congestion actually occurs.

	It is a trade-off, since any upstream AQM will in all likely not =
be configurable by the end-user, even if one might dream of AQM as a =
service kind of thing... (there probably is no real market for that...)

>=20
>> In the [Internet -> home] direction, you are right that FQ on the =
home end would not isolate the access link from a misunderstanding of =
any CE marking. But I'm not suggesting it could or would. The question =
is about the machine at the Internet side of the access link (BRAS, =
CMTS, etc) that is queuing traffic into the access link towards the =
home. We can be nearly certain it is not doing FQ (these machines serve =
thousands of customers, so I don't believe any use FQ). The question is =
whether we can find one of these non-FQ machines that has an AQM enabled =
that does CE marking.
>=20
> The motivating reason for ingress shaping is that, generally, the BRAS =
or equivalent device in the ISP does not perform AQM at all (though some =
do policing, which doesn't involve ECN).

	I happen to believe that even if the upstream end would/will =
offer AQM there still is going to be a desire for detailed =
configuration, especially in light of on-line gaming (of the =
reaction-time bound variety; given that many games do not even offer =
IPv6, I see not flag-day change to L4S or alternatives, unless =
Microsoft/Sony are on board and will update their console OSs in a =
timely fashion).

>=20
> In my experience there is often a "provisioning shaper" that is =
essentially a TBF with a dumb tail-dropping FIFO attached; I once =
suffered one on a rate-limited 3G service which had about 40 seconds of =
effective bloat.  If that had any sort of AQM installed, ECN or =
otherwise, flow-isolating or not, it would have resulted in vastly =
better service at essentially no cost to the ISP.  Indeed it may have =
saved them some money in reduced memory requirements on their =
provisioning shaper box.

	Current ISP, offers up to 300ms delay during a simple speedtest, =
better than 4000ms, but certainly only useful as a worst-case limiter...

>=20
> On my present LTE connection, which varies wildly in available =
capacity on a minute-to-minute basis, I've set my ingress shaper to a =
flat 10Mbps rate.  It makes an enormous improvement to the quality of =
service I receive, even though it reduces my throughput to a fraction of =
what's available during off-hours.  Yes, it is a flow-isolating AQM =
shaper (Cake) which is broadly similar to fq_codel.
>=20
> I did spend a few minutes today sketching out what happens if an L4S =
flow hits fq_codel on an ingress shaper.  The theoretical results are =
that, in congestion-avoidance mode, the L4S flow takes about twice as =
long to drain the dumb bottleneck queue as a Classic ECN flow after the =
onset of saturation. =20

	As much as care, that probably is still sort of acceptable.

> But the real shocker is what happens in the terminal phase of =
slow-start, where a rapid correction is required after the minimum 2x =
overshoot in exponential growth (because it takes an RTT for the =
CE/ECE/CWR signal to circulate and take effect).
>=20
> How many RTTs does it take for the cwnd to be halved in L4S, when the =
only CE signal is ramping up linearly at one-per-RTT-per-RTT?  Hopefully =
enough for L4S to detect the delay induced by the dumb FIFO and fall =
back to RFC-compliant behaviour.

	It would be great to avoid that situation.

Sebastian Mioeller

>=20
> (Yes, we have a real solution sketched out for SCE.  It will be tested =
soon.  We already have running code.)
>=20
> - Jonathan Morton
>=20


From nobody Thu Apr  4 03:30:40 2019
Return-Path: <moeller0@gmx.de>
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 BE999120478; Thu,  4 Apr 2019 03:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 Ihry8sFcsFuY; Thu,  4 Apr 2019 03:30:38 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 7BBDB120041; Thu,  4 Apr 2019 03:30:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554373790; bh=wg9B1EaqSRX4HkLNVHwCQINawUVkh/7H655jYZzWagY=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=dAue2N5Eg54sSPARkJkb6/pVtZKu8nPpFdryIE5gYRQD6r32N0d4qh8l7FofGMqwu urTeTZbCHPzVFOOI0Zzhcr7eiwln1qcpOWx5yD6ddcnWoZupR9K8qGHwrGawzQK9UZ 0ScEh+SFR1hpEvBuiOV6YX5ivTYnd0L3Hi574EXU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.12.10] ([134.76.241.253]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M8pKi-1h4Jaz374m-00CANM; Thu, 04 Apr 2019 12:29:49 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com>
Date: Thu, 4 Apr 2019 12:29:47 +0200
Cc: Jonathan Morton <chromatix99@gmail.com>, Bob Briscoe <in@bobbriscoe.net>,  "iccrg@irtf.org" <iccrg@irtf.org>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <59D6B58C-C966-493C-B3B9-CAD3AD7AD5F9@gmx.de>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Provags-ID: V03:K1:fJDpCHWkTYS5QjLY4m7k5gsa/bgT/9iitFv11+xg1z2IwXdHoJD FIjAKxfLKlImDSBGzJMnptjKxWDZPPd3vD09Jt5N+5LOZrtn68gxXFDLJWuaEFClTSJXehi Ff5WQKW09VwUVBkMEgBc1LgCJliUQgfh3zTWUsT6c9u68B5CFfJdLFP3t1/I0qV8olvxuvT Bhg9BdqCaPs4z8N3WSCAQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:OEKIEd6VJR0=:ikXVq3Qz+NGltlndv667SS aBj2Ib4/IB6uQJjKCtQ23zEA1lL095A/EC+29waQs7JAit5hUGBBZN+mD6T85vZ/9ljGoAUmm EHe9Lsq90258vP36sFvsU9/ILLjB1lRcZGjkM3FHvWKgmt++MW7cQ++ntPrAPB8NdemnGQqFV uafOYVMXfG65+2aDxYfFpsDDhBhvMGef+i6uGoYmgKWJtPf9GYy8gFzLyI22/kDUrE6OyQyZ2 0EjnorhaohyfSmI4H1f85uYt7XOzecjSd1PEuB3NTjWukEnaAmARkYXpuWEVDIU9DEHQSo9GW EskMZ8meylD2Hs6jZ+PnIXrhaW7z4sIk25sf3mF2YEpLfsR/llCRVctv9nLl4xFPW4DjI2DNu 0z99b6gbFga6WB7inZuiAgYkyFS+ZfhFoH1fGYUF3AZNJweL5ka3j2ZUuf+01lkHbXEdT3PcM ZZf1aBxSFEC4yI/BoGc8yA036QYUZqHkDNUE/wV2lXNI3lSgAtWJPOv3oD6c6pq0+cSp+2tNh GWT6Im1ADD1Qfgb57tUhil+81sra/Du8/oIwc+/fExPGQfUsv1K3SN/Tw6yjlUWwlJN6IoPbN LpNv0Oc0LGMg80qoXSo/IAv3OmaL2g94ZBmG5wvPZPZ6ftYbE/BHppczBHPSp2I4AN1w5Bxov p2Ym9BGzTHSKUPPB4aRqOgXntFEguTKMhThkoANPdiF1DNO+rS5lHJjVyfNFh026u1STuCDNS Sbxo3WYxNqMWKEh9BrVszfW3VbeP295Dan2rUFWxonNNxEuXTsmqQ7HLPuoiLJC2IjJPdq6Fv tgBRPgwd1PFIWoGh9L+KaB+88ILWeLKBOQMGobQxqxSyAtWjHwh4H/zkZQvUAfXLqrSN//fki kbPYbIjyV2AcAEi4qfy/rA4rFtFfaEcc8hejzLlL8VuZwKHZ1QarvvdF60fD7CWa7TqwWfeSu 8SgXrXC9SwQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XwKnYLDe1FKk23EU1b6tIs68loA>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 10:30:40 -0000

Hi Greg,


> On Apr 4, 2019, at 01:28, Greg White <g.white@CableLabs.com> wrote:
>=20
> On 4/3/19, 7:28 PM, "iccrg on behalf of Jonathan Morton" =
<iccrg-bounces@irtf.org on behalf of chromatix99@gmail.com> wrote:
> [...]
>    It is actually common for OpenWRT devices to include "ingress =
shaping" to exert some control over bufferbloat on downloads.  The =
terminology, in fact, comes from this practice, as the port in question =
is facing the WAN link and has two qdiscs attached, one for egress =
traffic towards the Internet, and one for ingress traffic received from =
the Internet.
> [...]
>  It is of course better for AQM to be installed on the upstream side =
of where the congestion actually occurs.
> [...]   =20
>    The motivating reason for ingress shaping is that, generally, the =
BRAS or equivalent device in the ISP does not perform AQM at all (though =
some do policing, which doesn't involve ECN).
>=20
> [GW] It will be the case that many such "equivalent devices" can (and =
will) support a dual-queue AQM (not fq), which (where available) will =
eliminate the need for ingress shaping, and provide a better result.    =
If fq_codel (or CAKE) were updated to utilize the L4S-style of ECN (or =
even just treat ECT(1) as non-ECT), this would be a non-issue.   How =
feasible would that be?


[SM]: I happen to believe that head-end AQM will ameliorate the need for =
an ingress AQM for a lot of casual users, but all those that are =
constantly running against capacity limits (think ADSL) typically desire =
a more fine-grained prioritization than a head-end AQM is going to =
offer, includsing restricting bandwidth to certain proiorety classes to =
say keep latency increas for game traffic tightly bound. I believe in =
that case the guarantees L4S offers are not sufficient, as the gaming =
case requires "guaranteed bandwidth at a certain latency level" as =
compared to the low_queueung latency guarantee L4S offers (which =
basically moves the que back into the sending end-host, which is fine, =
but all it does not help if I need to send @ X Hz).


>=20
> [...]
>    I did spend a few minutes today sketching out what happens if an =
L4S flow hits fq_codel on an ingress shaper.  The theoretical results =
are that, in congestion-avoidance mode, the L4S flow takes about twice =
as long to drain the dumb bottleneck queue as a Classic ECN flow after =
the onset of saturation.  But the real shocker is what happens in the =
terminal phase of slow-start, where a rapid correction is required after =
the minimum 2x overshoot in exponential growth (because it takes an RTT =
for the CE/ECE/CWR signal to circulate and take effect).
>    How many RTTs does it take for the cwnd to be halved in L4S, when =
the only CE signal is ramping up linearly at one-per-RTT-per-RTT?  =
Hopefully enough for L4S to detect the delay induced by the dumb FIFO =
and fall back to RFC-compliant behaviour.
>=20
> [GW] One of the optimizations being investigated for L4S (both =
TCP/QUIC Prague and (I think) BBRv2) is a revised startup process that =
avoids the 2x overshoot from slow-start.  Nonetheless, you are right =
that an issue to be understood (and addressed?) with TCP Prague / =
fq_codel compatibility is how to prevent TCP Prague seeing worse latency =
than classic TCP at flow startup.  As you indicated, once the Prague =
sender falls back to Reno behavior, things are fine. =20
> In fq_codel/CAKE currently, does the AQM switch from CE mark to packet =
drop at some higher threshold of sojourn time?  If so, would this =
provide for a faster fall-back to Reno than you considered in your =
analysis?  Alternatively, if fq_codel/CAKE were to treat ECT(1) as =
non-ECT (or implement the L4S style ECN) this would again not be an =
issue, I believe. =20

[SM] I believe this to be just as viable as having L4S AQMs interpret =
ECT(1) as pulse-modulated continuous congestion information. In the end, =
after the dust has settled, one of these is going to happen, as there is =
only going to be a single graded congestion signaling (if at all). IMHO =
the jury is still out which approach will win.


>=20
> [...]
>    (Yes, we have a real solution sketched out for SCE.  It will be =
tested soon.  We already have running code.)
>=20
>     - Jonathan Morton
>=20
>    _______________________________________________
>    iccrg mailing list
>    iccrg@irtf.org
>    https://www.irtf.org/mailman/listinfo/iccrg
>=20
>=20


From nobody Thu Apr  4 03:53:56 2019
Return-Path: <moeller0@gmx.de>
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 BFAD0120013; Thu,  4 Apr 2019 03:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 XkPDhAj4PlaW; Thu,  4 Apr 2019 03:53:45 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 1EC9C12000E; Thu,  4 Apr 2019 03:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554375178; bh=+Kq7vPOLVw4u0HPC5DIBFV1j/PLmpCk6aU+bdkEaBHg=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=ImH+cUmv83NKEJZOlRZIc9MF4LEGOUueWHU6+QJPWuKZ3LuPFYH21nARKZG90B9pC 1gNi5yaPdh+TjIK9dK/teptG0VGnZ1yRa7GMjvb76HLQX0CWkoZENQXi9ML/QqeiGy uWrKR8yXk1nNE6/zr/5aiWnwALHWskKRVomb76bk=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [172.16.12.10] ([134.76.241.253]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LjZEm-1ges9x3djU-00banl; Thu, 04 Apr 2019 12:52:57 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
Date: Thu, 4 Apr 2019 12:52:55 +0200
Cc: Jonathan Morton <chromatix99@gmail.com>, Bob Briscoe <in@bobbriscoe.net>,  "iccrg@irtf.org" <iccrg@irtf.org>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <851D37C7-2B52-4949-8957-818760909C20@gmx.de>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Provags-ID: V03:K1:J1M7Kn3i2SuiaeeyDFX+xmglSzSFtLcepIDdpfPRLG0rqx74tsy wwHzQ1O6DJeFDEX7CZnfL3usEHAJLOL4c5X/7kbuRQlIU0uZhh9+f0IFUFILvxKywTivLQl t02CGXvntGgFRL89aLMoLQuI3yQ+4P3rWYqiewxpMmWbrjvi1romfwl4fDGDjEzQZf0Z9qh 1FqZGPZ4ktqatysjochsQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:s21jByTzcmU=:KI0le84Ylv/8fAOuQefQGF RoUYHNckKOUQ86kAoFrQRPVNHaLED/JlNYm+9H2bnwftV3UAgnnTFdzNv3cS6x0fHalNAL7B0 8bCITYBStUAmbNsNdk7xfdXairzAoj35m05t+Clnhg9DUjQOsiYOzWDJyytIv6IcOuevfwAiR lwtWts3CdVImf5/GsWU2y0M3sMnLur6zfyUOQ44Anhkql9FIaHYF3CLF6ii/JsKz69dKJwjVC FqKUbjhNPxAfuvk/ql2XDUagi3Y7FjhpU0Uvvr28vKE0+G4a5U8ozZhW3p5zot/N5EM3eTuJl DWJnYRxWXIqjAmSK6ZLXG/7onIf+7gnK/O8LgQibqnhLeZSTLkCrZbogwt7D92y61V0M88U6N aNRpN2z91+BBbBGESUvyq9sqaxxqmXwaHDbDlsLK1MvAmStrAhN5SaDGCXlDWbLVwv1wiihEa GqQ45wiw1BHS+bu4FQxkZeoO8FYbDBVfmb+gN+ppAre5wqqyXCRSilZWd9pdn7JB9v9KZHsPz Cjr4S+uT41Cl0e0JPc+aeC9K3P2ezraacUlAtc4QGyjRdhb8zEJn/nkYVd48J0D3GsmZd79Cc j83d5YOTBeO0T7HwxsUop0rKssyry92ZthhomfEMMfgwQsA4hn21EP2amRbrbkPTuHVbBpc3W ElZhH9GIDDIcyS6Q3nmOa2OCKSU52O0WvxflbW3SbihdGQ4YXw23fNAC+r3pmLD4YNxmjBTk3 QT7KPo/t+KHycX7x7nnlbBMaKW0W6AMGN3g5ZbEcRik2taV9kbLa6mbjHgAoaY0qSh7Oqr0K0 J73Db8DOAXrDByAuJd64G0x6aFtqbBLZ8UhNyHqNrUr95jgFdW9CU298Ir/+jkBaZaV8/mH5U xkv7xRrsi6gyv+akBlk1L220laj1zj8tHBqmOeNBp+mUMHfGP9s1XOWDaHYuFufxhcu2qw+3F 3JK4gtlwJ3A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/4S_5KbFmDxSj15D5c-Ep-XLtgpg>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 10:53:48 -0000

> On Apr 4, 2019, at 11:40, Greg White <g.white@CableLabs.com> wrote:
>=20
>=20
>=20
> =EF=BB=BFOn 4/4/19, 1:28 AM, "Jonathan Morton" <chromatix99@gmail.com> =
wrote:
> [...]   =20
>    The present out-of-tree version of Cake supports an L4S-style =
high-fidelity ECN marking method, simultaneously with conventional ECN =
marking.  It does so using the SCE signalling method, with ECT(1) being =
an output rather than an input.  This is, in fact, the running code we =
had at the time of our TSVWG presentation.
>=20
> [GW] Has any progress been made on a variant of Cake that utilizes the =
L4S ECT(1) semantic?  It would be useful for comparison purposes. =20
>=20
> [...]   =20
>> Alternatively, if fq_codel/CAKE were to treat ECT(1) as non-ECT (or =
implement the L4S style ECN) this would again not be an issue, I =
believe.
>=20
>    Perhaps, but I thought FQ AQMs weren't much of a problem to begin =
with - aside from the ingress-queuing problem? =20
>=20
> [GW] Well, a goal would be for FQ AQMs to provide appropriate =
high-fidelity congestion signals to L4S flows so that they can achieve =
all four Ls and the S.  Failing that, to not provide weaker congestion =
signals for L4S flows as compared to classic TCP.  It isn't a problem =
from a fairness perspective, but the goal is low latency after all.    =
This seems like a fairly simple change to FQ.
>=20
>    I'm also reluctant to interpret ECT(1) or CE incompatibly with =
RFC-3168, unless given very good reason - and I currently have a good =
counter-argument.  If I may quote from that document, it does =
specifically contemplate use of the fourth codepoint to signal "mild =
congestion":
>=20
>>   One possibility might have been for the data sender to use the =
fourth
>>   ECN codepoint to indicate an alternate semantics for ECN.  However,
>>   this seems to us more appropriate to be signaled using a
>>   differentiated services codepoint in the DS field.
>>=20
>>   A second possible use for the fourth ECN codepoint would have been =
to
>>   give the router two separate codepoints for the indication of
>>   congestion, CE(0) and CE(1), for mild and severe congestion
>>   respectively.
>=20
> [GW] I don't believe that the RFCs are on your side here.   RFC 3168 =
contemplates, and rejects, that definition of ECT(1),

[SM I believe this to be caused by not considering pulse modulation =
though, as the argument is that a single code-point might not be "rich" =
enough to signal graded congestion information, but IMHO DCTCP shows =
that this is solved. In any way RFC 3168 seems a bit dated for this =
discussion as all agree to go beyond it, no?


> so I'm not sure how you read it as supporting the use. RFC 3168 =
explicitly defines ECT(1) as being a transport sender signal that it is =
"ECN Capable Transport".  I don't see how you can claim adherence to RFC =
3168, yet use ECT(1) to mean (S)CE.  Moreover, RFC 3168 has been updated =
by (Standards-Track) RFC 8311, which enables the L4S experiments, and =
which the SCE approach also violates. =20
>=20
> [...]=20
>    I can't help noticing, meanwhile, that DualQ seems to be designed =
for use wherever a single-queue AQM would normally fit (though I have my =
doubts that it will work on much hardware already deployed at crucial =
locations). =20
>=20
> [GW] We have worked very closely with all of the DOCSIS equipment =
vendors to ensure that Low Latency DOCSIS (including dual-queue) is =
implementable via a firmware update to ALL existing DOCSIS 3.1 CMs and =
CMTS that are in the field today.  In some markets that is more than 90% =
of deployed CMTSs. I obviously can't speak to other access network =
technologies, but to the extent that forwarding architectures are =
similar, I would presume that doubling the number of queues is =
significantly simpler than multiplying by 1000.

	But why, in the end memory is linear and your proposed mandatory =
"Annex P Queue Protection Algorithm (Normative") seems to care all the =
costs of tracking flows already, so why is that considerably cheaper =
than using that information also for scheduling purposes?

>=20
>    Yet at the same time, you claim such single-queue AQMs are =
presently (and will remain) so rare that you haven't even developed a =
method of reliably detecting them.  This seems like an important =
discrepancy.
>=20
> [GW] The concern would be single-queue *ECN* AQMs. Single-queue packet =
drop AQMs do exist.

[SM] What about my hobby-horse "ingress-ECN-aware-fq-AQM"?


>=20
>    Meanwhile, work continues.
>=20
> [GW] Why?  It seems to me that the L4S approach can be implemented =
easily in fq_codel and CAKE, as well as in systems that can only =
realistically support dual-queue.

[SM] if that system has memory and a CPU it _can_ support fq as well, =
that is a _choice_ not an _impossibility_. It might be un-economically, =
sure. But again, why will such a device be able to do Queue Protection =
then?


>  It has been demonstrated to provide scalable throughput and ultra-low =
loss and queuing delay

Which sounds greater than it is since most applications care for =
end-to-end latency, and L4S basically moves (a part of) the queueing =
delay from the bottleneck AQM back into the sending application, it does =
not remove that latency completely.

> (which, I think, is the goal of SCE as well), and has quite a bit of =
support and momentum behind it. The philosophical debate as to which is =
better, dualq-coupled-aqm or FQ, can continue and implementers can =
choose whichever they like.  I don't doubt that the SCE signaling method =
could be used in a variant of DCTCP, but the *huge* downside is that it =
can only work on bottleneck links that are able (or willing) to support =
FQ,

[SM] Why, the AQM will simply supply all ECN enabled with the graded =
information about the queueing load of the AQM, it is up to the =
endpoints to make sense out of this.

> which will be precious few.  In 2-3 years' time, 10s of millions of =
actual bottleneck links in broadband networks will be supporting =
dual-queue.

[SM]	I guess most bottlenecks nowadays support a variant of RED but =
support dies not equal exercise it. But sure I like how the DOCSIS =
standards-process  can influence a large swath of critical bottleneck =
links, more power to you.

>  It seems that the only real argument in favor of the SCE signaling =
method is the fallback in presence of single-queue classic ECN (unless =
you think blocking implementers from supporting dual-queue is some kind =
of perverse benefit). =20

[SM] I see the SCE proposal as the better more evolutionary approach =
forward, the L4S approach basically spells, the current state is =
unrecoverable and we need to start fresh, but then does no much of that =
sort (re-using PIE and DCTCP is also nicely evolutionary).

> Help analyzing (and addressing if need be) that situation would be the =
most effective way of achieving the shared goal of low latency scalable =
congestion control.  Continuing to push for (or worse, deploy) an =
incompatible solution just increases the risk that no one will be able =
to achieve that goal.

[SM] these wise words typically apply to both sides of a discussion and =
have just as much merits one way or he other. I note that in reality we =
often see something else, alternative approaches duking it out and =
driving their evolution exactly because they are not the only game in =
town....


Best Regards
	Sebastian=


From nobody Thu Apr  4 04:02:17 2019
Return-Path: <chromatix99@gmail.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 EA84C1206B3 for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 04:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Bm_KiD-zYVAt for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 04:02:05 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 054E9120092 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 04:00:18 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id l7so1672351ljg.6 for <tsvwg@ietf.org>; Thu, 04 Apr 2019 04:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yLUsri1lMCJQLYQZe3aC1zLMmpTkfroqUkIv1PhMlZ4=; b=iafGRhFiHis874eDxG56oq3MJMMKUi4gqzQ84TdDFSOjZhO40bJwVx0KeysFC2L32S n6gjcakhgGpRQz+EWtRmrY7mxQJ8QDAYF6yfb+x/hAtzLKETrOIhIh5c5F5G4E1RkZQM 99VqcMxCCmQm4RvjHnfp81StgztAbY2GBLPxvcPq9nsY3p2Jm76ob2+gErRQCyXPbYxM 8nKgNj1sOQ6JRxGsyTf6G2cO0WWl/PMKTxN7K2+jqQ4r6LfXsV6mKr3szP/OASVNjWYS DQsd1rAKmGEkfQHw/V6dAfx8fWDma3kE2DCSDZfyXt72VyNhuTznQA/kUlJM+d2dpiDA mkZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=yLUsri1lMCJQLYQZe3aC1zLMmpTkfroqUkIv1PhMlZ4=; b=J05AyFOI+Bzjp2m5JX6f1djX6RcrENwTvTUBcP1kgu7Xfw+Z2dPZjWrSZbsg8jSrqx opuZLCLoRtFXWtFFyM/epiJkF+TomFtGenohBBudkEU3khmunXl9eMYV08uDMDG5FCj2 kjAiEpbwTlqJC39dXZyXdmfo35gXIZuHKb/h50mw83eXmEB+6y3fqA17h1OfFlZyvZkZ q/C7/1YRprHC20fOEvZtxDDqmk85T6QdTzIdnRudfnibuXtihwlJxkw7tE4+9sgUj3T2 d1w2sFmGJAGxGF10wluoGz1nddLrn6+Pku2aXLDIcdbEex3acm8SuiASPe/rzwvCwhm9 nRmQ==
X-Gm-Message-State: APjAAAUu37+Qo2r1potwEAhsHtNsuDx2rMtGSkxLhlXBSswc7DAQSZsj 3v927gvFrJo92lNv3D8OZ0E=
X-Google-Smtp-Source: APXvYqzUStgNgi3TzoFS4gUNOcg3lBpdnSW6uiGpbruVPmM5nkoZnrAD99IxagSR51q5lf7sf39ouw==
X-Received: by 2002:a2e:9843:: with SMTP id e3mr2980897ljj.28.1554375616282; Thu, 04 Apr 2019 04:00:16 -0700 (PDT)
Received: from jonathartonsmbp.lan (85-76-23-211-nat.elisa-mobile.fi. [85.76.23.211]) by smtp.gmail.com with ESMTPSA id d3sm3851109ljc.15.2019.04.04.04.00.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Apr 2019 04:00:15 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
Date: Thu, 4 Apr 2019 14:00:14 +0300
Cc: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/WTgKXPhDOMylXjjPDQTy6AidUAQ>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 11:02:09 -0000

> On 4 Apr, 2019, at 12:40 pm, Greg White <g.white@CableLabs.com> wrote:
>=20
> I don't doubt that the SCE signaling method could be used in a variant =
of DCTCP, but the *huge* downside is that it can only work on bottleneck =
links that are able (or willing) to support FQ, which will be precious =
few.

Let me stop you right there.  You are remembering a discussion we had at =
least two weeks ago, based on an early concept of SCE which has since =
been superseded.

We have running code which converges rapidly to fairly sharing the link =
between two SCE flows, with only a single-queue SCE-aware AQM.  That is, =
we used the "besteffort" and "flowblind" modes of Cake, which disable =
its Diffserv and flow-isolation capabilities, specifically to test that =
aspect of our work.  Since our prototype SCE response is DCTCP-like, =
that result should not be a surprise to you.

We *also* believe we have a solution for fairly sharing a single queue =
between SCE and non-SCE flows.  We haven't implemented and tested it =
yet, however.  Work continues.

> (unless you think blocking implementers from supporting dual-queue is =
some kind of perverse benefit)

Dual-queue AQM can still be supported through Diffserv, as I have =
repeatedly pointed out.  The associated PHB can specify the "short =
queue" and "no reordering" behaviours you're so keen on.

Now, reading back up your post:

> Has any progress been made on a variant of Cake that utilizes the L4S =
ECT(1) semantic?  It would be useful for comparison purposes.

We have not done so.  The code is freely available if you wish to try it =
yourself; it should not be difficult.  Cake also offers an excellent =
platform for exploring the behaviour of single-queue ECN-aware AQMs, =
which I think you would find valuable.

> I don't believe that the RFCs are on your side here.  RFC 3168 =
contemplates, and rejects, that definition of ECT(1)=E2=80=A6

It also contemplates, rejects, and suggests a better alternative for =
L4S' use of ECT(1), right there in the quote.  And on the subject of =
RFC-8311, that document contains a section entitled "Effective =
Congestion Control Is Required", and it specifically leaves alone the =
several suggested uses of ECT(1) in its edits to RFC-3168.

I note in passing that SCE has the support of the TSVWG Chairs.  That is =
sufficient motivation to continue work to establish its true merits and =
limitations.

 - Jonathan Morton


From nobody Thu Apr  4 04:09:29 2019
Return-Path: <in@bobbriscoe.net>
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 0C854120092 for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 04:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=bobbriscoe.net
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 t1NTCxi2UzSr for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 04:09:23 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (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 4EB8B12007C for <tsvwg@ietf.org>; Thu,  4 Apr 2019 04:09:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-Transfer-Encoding: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=wI3tJvsUtXbNlKZC5c6PkRFdGrwvB/MIme6OmFUFayo=; b=0lQ4wV64bjlv8xWQPpQNJfDEz FJTpihyJWzyqZ/p94vYXXycV+6tyiI19L40+tbojzotcS1hjcHH05ROFTtLSkT1ZipDrVHsMfP0ge AiEfNcKDGX0mU+PfA8xu3qPJEdDOlBLZEx7P/zd+t7Llkl3lyMarMuznBQardvygRDbjuFRZ5qsdT DmV0md43kH8iISGBvSL5HZbSqA6waoJd+3ITse9hVrNJW9adrokDhea7b8LsYQYx95gUZtOrzRCB/ dajCdh+RRthlRb5UMPd9Lu6ynDb7rHv5O3qPO0zrkCUrVbNvjIB/Gqds5UtFKTmdZ0raiAVF6TfVE FheO8kEig==;
Received: from [77.76.75.108] (port=59614 helo=[10.15.95.128]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <in@bobbriscoe.net>) id 1hC0FC-0003yU-Ew; Thu, 04 Apr 2019 12:09:20 +0100
To: Luca Muscariello <luca.muscariello@gmail.com>, Greg White <g.white@cablelabs.com>, tsvwg IETF list <tsvwg@ietf.org>
References: <0289E1B3-9AFF-4633-A9B1-6BAEE96B7692@cablelabs.com> <CAHx=1M6US_HYjXfqtRr8RbGEe5QxPjjnivLkKMHHBpqMQRyP8g@mail.gmail.com> <C689234C-6A08-47B1-90B5-07DE77112BBD@cablelabs.com> <CAHx=1M5z4fpViHbV+3+VchpyXsPJwwCuhWzNvZ7EU-An3gS0qQ@mail.gmail.com> <300857A4-9483-473E-8D9E-799F6077A4FF@cablelabs.com> <CAHx=1M53q0DG8AmhSxQXFhDfr4UzgrRR+iebmCwrZMcVnMvS5g@mail.gmail.com> <CAHx=1M4y=bEHQ1xt1G59B-DzuU195s4hMapAFmjP0UFqSn403A@mail.gmail.com>
From: Bob Briscoe <in@bobbriscoe.net>
Message-ID: <b19e6ec3-ff4e-6c71-4dd3-524524f307e7@bobbriscoe.net>
Date: Thu, 4 Apr 2019 12:09:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <CAHx=1M4y=bEHQ1xt1G59B-DzuU195s4hMapAFmjP0UFqSn403A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------885B6DAA912926147FB16947"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/t_PDM3khNasxmi9N8izLzur7kJ4>
Subject: Re: [tsvwg] Fwd: New Version Notification for draft-white-tsvwg-lld-00.txt
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: Thu, 04 Apr 2019 11:09:28 -0000

This is a multi-part message in MIME format.
--------------885B6DAA912926147FB16947
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Luca,

In reviewing this thread I think you haven't received a full answer to a 
question you raised in your email early in the thread (below).

On 17/03/2019 08:02, Luca Muscariello wrote:
> One point that is not specified anywhere is when a mflow entry is 
> removed front the flow table.
>
> As the table is used to blacklist mflows my intuition was that it has 
> to be based on some sort of timer. Which is another parameter to set 
> in the mechanism.
>
> The table then is tracking flows that are in progress or maybe not. 
> For sure an entry is maintained even for flows w/o packets in the 
> queues.  This has poor scalability properties compared to fq where an 
> entry is maintained for flows with actual data in the queues.
[BB] The queue protection algorithm ages out the queuing score held for 
each microflow (mflow) at a constant rate. In fact, the queuing score is 
normalized to time, so that the only value held in the bucket for each 
flow is the bucket's expiry time. For well-behaved flows, this expiry 
time will typically be exceeded before the next packet of the same flow 
arrives. If it has not expired when the next packet of the mflow 
arrives, the algo adds an additional amount of time to the mflow's 
bucket for the new packet.

Thus, only ill-behaved flows persistently consume flow-state memory, 
while well-behaved flows recycle flow-state memory between themselves as 
their packets interleave each other.

The amount of time that the algo adds to an mflow's bucket is the 
queuing score of each of the mflow's packets, normalized to a duration, 
using the following per-packet calculation:
     qscore = pkt_size * p / V
where:
     p is the current AQM marking probability of the low latency queue 
(dimensionless, in [0,1])
     V is the (constant) congestion-bit-rate deemed acceptable for a 
single mflow (see below for rationale) [b/s]

The division by V normalizes qscore to a duration, because the units are 
[congestion-bit / (congestion-bit / s) = s]. Of course, because V is a 
constant, the division can be implemented as a per-packet integer 
multiply by 1/V. We also choose V to be a power of 2 so a bit-shift can 
be used if more efficient.

The intuition is that the queuing score of an mflow is higher the more 
queuing delay there is when its packets arrive. And the faster the 
mflow's packets arrive, the more likely qscore will accumulate faster 
than the passage of time ages it out. But the formula for qscore is not 
just based on intuition - it comes from shadow pricing theory.

Congestion-bit-rate can be conceptualized as the bit-rate of those 
packets of a flow that are ECN-marked. A scalable congestion control 
averages a constant congestion-bit-rate for any flow-rate (i.e. any 
link-rate and any number of flows). So we set V a few times greater than 
that (currently 4x), to allow some variability in a flow without risking 
sanction. This does not mean that flows have to use a scalable 
congestion control to get through Q Protection into the low latency 
queue, it just sets an upper bound under which all scalable congestion 
controls will be able keep. It also sets the bar for unresponsive flows, 
to prevent them causing significantly more queuing than responsive 
scalable flows.

I hope the rest of your questions have been answered satisfactorily 
already by others.

Cheers


Bob

>
> The protection mechanism assumes that one queue has soft priority over 
>  the other. Strict priority would be stupid, so there must be a wfq 
> weight to schedule the classic queue less frequently. I did not find 
> the magic number that  is set in the DOCSIS specs but whatever number 
> is chosen I wonder which opitimization objective would be the 
> foundation of that.
> 10%, 20%, 30% or any number would imply that if the priority queue is 
> used at 100% utilization the other apps would get a small fraction of 
> the link capacity.
>
> What number is chosen and based on which calculations?
>
> Thanks
> Luca
>
> On Fri 15 Mar 2019 at 00:42, Greg White <g.white@cablelabs.com 
> <mailto:g.white@cablelabs.com>> wrote:
>
>     Yes, it is easy for applications to access the low latency queue,
>     and the job of QP is to redirect those that shouldn’t have been
>     there.  We could instead run all traffic through QP and let it be
>     automatically sorted, but if there is some traffic that can be
>     excluded a priori, then doing so reduces the queue delay (recall
>     that the QP algorithm only sanctions packets if the queue delay is
>     above the 1ms threshold), reduces the potential that a
>     well-behaving application is sanctioned (perhaps due to hash
>     collisions), etc.   Also, since sanctioning could result in
>     out-of-order delivery for a microflow, presuming that this is ok
>     for all applications might not be advisable.  We have some ideas
>     in the works for modifications that might be useful to reduce the
>     need for packet marking.
>
>     I don’t believe that this mechanism increases DoSability (is that
>     a word?) compared with single queue or fq systems, but would be
>     interested in some validation of that. Yes it is possible for a
>     malicious sender to mark its packets as NQB, and send at a high
>     rate with various port numbers (to get unique flow ids), and thus
>     have some percentage of packets avoid sanctioning, and in the
>     worst case drive queue delay up.  The default threshold values are
>     being adjusted from what is shown in the spec currently, so when
>     using the new default values, the worst case with carefully
>     crafted attack streams is ~32 ms of queuing delay (which, using
>     brute force, would require the malicious sender to launch ~400
>     Mbps of traffic at the QP function).  Similar traffic patterns in
>     a single queue system (or fq) could, depending on egress rate,
>     result in much more queue delay than this.   Also, if the attacker
>     does not mark their packets NQB, then the system protects the NQB
>     flows from the attack, so in this sense it is also slightly less
>     susceptible than single queue (and maybe fq).
>
>     *From: *Luca Muscariello <luca.muscariello@gmail.com
>     <mailto:luca.muscariello@gmail.com>>
>     *Date: *Wednesday, March 13, 2019 at 4:07 PM
>     *To: *Greg White <g.white@CableLabs.com>
>     *Cc: *"tsvwg@ietf.org <mailto:tsvwg@ietf.org>" <tsvwg@ietf.org
>     <mailto:tsvwg@ietf.org>>
>     *Subject: *Re: [tsvwg] New Version Notification for
>     draft-white-tsvwg-lld-00.txt
>
>     Greg,
>
>     Is there any intention to also grant access to the low latency
>     queue to applications that do not mark?
>
>     Also, if I got this whole mechanism right (big IF), it seems like
>     entering the low latency queue is only based on marking.
>
>     This way it looks like the queue is  easy to access and the
>     mechanism reacts to bad behaviour afterwards.
>
>     Does not this risk to create spurious packet enqueues into the low
>     latency queue? Or worse malicious sources
>
>     to make the low latency queue DoSable?
>
>     Luca
>
>     On Wed, Mar 13, 2019 at 2:03 PM Greg White <g.white@cablelabs.com
>     <mailto:g.white@cablelabs.com>> wrote:
>
>         Luca,
>
>         We may work on improving the informative text in that section
>         in order to make the behavior more clear without puzzling
>         through the pseudocode.
>
>         1.A packet enters the QP algorithm if it is classified to the
>         low latency queue.  By default, the intention is to use
>         ((DSCP==NQB) OR (ECN==ECT(1)) OR (ECN==CE)) (see the NQB draft
>         and ECN-L4S-ID draft) to identify likely NQB flows (but this
>         can be changed if needed).  The algorithm of course doesn’t
>         care how the packets get marked, but our view is that the
>         original application (or OS) should be the one that does the
>         marking. For either marking, there is no incentive to lie.
>
>         2.The algorithm sanctions (redirects to the classic queue) on
>         a per-packet basis.  So, a microflow that only briefly causes
>         queuing will have some of its packets sanctioned during that
>         episode only, and even during that episode, all of its packets
>         are scored. Note, in some cases this could result in
>         out-of-order delivery, which might be a minor disincentive for
>         persistently QB flows mismarking themselves as NQB.
>
>         3.See above.
>
>         Greg
>
>         *From: *Luca Muscariello <luca.muscariello@gmail.com
>         <mailto:luca.muscariello@gmail.com>>
>         *Date: *Wednesday, March 13, 2019 at 2:37 PM
>         *To: *Greg White <g.white@CableLabs.com>
>         *Cc: *"tsvwg@ietf.org <mailto:tsvwg@ietf.org>" <tsvwg@ietf.org
>         <mailto:tsvwg@ietf.org>>
>         *Subject: *Re: [tsvwg] New Version Notification for
>         draft-white-tsvwg-lld-00.txt
>
>         Greg,
>
>         Thanks for the reference.
>
>         I have a few questions. I read the document just once so,
>         don't be surprised if I got something wrong.
>
>         1) A packet enters the low latency queue if it is marked. Who
>         is responsible for the marking?
>
>         Is the original application to do that?
>
>         2) Once a packet enters the low latency queue, the flow, or
>         microflow,
>
>         is tracked in a (micro)flow table by reporting a function of
>         the queue occupancy.  How do updates of the table
>
>         take place? Insert is clear unless the flow is banned, update
>         is clear.. Remove is only clear to me when the flow is moved
>
>         out of the low latency queue once it  started to get too much
>         resources. Remove in the general case is not clear to me. Timers?
>
>         3)  It seems like the mechanism trusts the packet marker until
>         the queue protection mechanism takes
>
>         a different decision. How can a marker be redeemed and related
>          packets be readmitted to the low latency queue?
>
>         Thanks
>
>         Luca
>
>         On Mon, Mar 11, 2019 at 7:18 PM Greg White
>         <g.white@cablelabs.com <mailto:g.white@cablelabs.com>> wrote:
>
>             Hi Luca,
>
>             You can find the details in Annex P of the DOCSIS
>             MULPIv3.1 spec.
>             https://specification-search.cablelabs.com/CM-SP-MULPIv3.1
>
>             -Greg
>
>
>             From: Luca Muscariello <luca.muscariello@gmail.com
>             <mailto:luca.muscariello@gmail.com>>
>             Date: Monday, March 11, 2019 at 6:26 PM
>             To: Greg White <g.white@CableLabs.com>
>             Cc: Dave Taht <dave@taht.net <mailto:dave@taht.net>>,
>             Jonathan Morton <chromatix99@gmail.com
>             <mailto:chromatix99@gmail.com>>, "tsvwg@ietf.org
>             <mailto:tsvwg@ietf.org>" <tsvwg@ietf.org
>             <mailto:tsvwg@ietf.org>>
>             Subject: Re: [tsvwg] New Version Notification for
>             draft-morton-taht-tsvwg-sce-00.txt
>
>             Hi Greg,
>
>             I'm curious about the queue protection function in the LLD
>             document.
>             It seems to assume that a flow table is maintained to
>             determine if a flow
>             has the right to enter the low latency queue.
>
>             Can you give more details about that component? Or point
>             me to a reference?
>
>             Thanks
>             Luca
>
>
>             On 3/11/19, 5:29 PM, "tsvwg on behalf of Greg White"
>             <tsvwg-bounces@ietf.org <mailto:tsvwg-bounces@ietf.org> on
>             behalf of g.white@CableLabs.com> wrote:
>
>                 TSVWG,
>
>                 I've posted a new informative draft that gives an
>             overview of the new Low Latency DOCSIS specification (see
>             links below).  This overview may be interesting to TSVWG
>             participants because it includes support for L4S
>             (https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-aqm-dualq-coupled)
>             and for the NQB PHB
>             (https://datatracker.ietf.org/doc/html/draft-white-tsvwg-nqb).
>
>                 Best Regards,
>                 Greg
>
>
>
>                 On 3/11/19, 5:05 PM, "internet-drafts@ietf.org
>             <mailto:internet-drafts@ietf.org>"
>             <internet-drafts@ietf..org
>             <mailto:internet-drafts@ietf.org>> wrote:
>
>
>                     A new version of I-D, draft-white-tsvwg-lld-00.txt
>                     has been successfully submitted by Greg White and
>             posted to the
>                     IETF repository.
>
>                     Name:  draft-white-tsvwg-lld
>                     Revision:       00
>                     Title:          Low Latency DOCSIS - Technology
>             Overview
>                     Document date:  2019-03-11
>                     Group:          Individual Submission
>                     Pages:          25
>                     URL:
>             https://www.ietf.org/internet-drafts/draft-white-tsvwg-lld-00.txt
>
>                     Status:
>             https://datatracker.ietf.org/doc/draft-white-tsvwg-lld/
>                     Htmlized:
>             https://tools.ietf.org/html/draft-white-tsvwg-lld-00
>                     Htmlized:
>             https://datatracker.ietf.org/doc/html/draft-white-tsvwg-lld
>
>
>                     Abstract:
>                        NOTE: This document is a reformatted version of
>             [LLD-white-paper].
>
>                        The evolution of the bandwidth capabilities -
>             from kilobits per
>                        second to gigabits - across generations of
>             DOCSIS cable broadband
>                        technology has paved the way for the
>             applications that today form our
>                        digital lives.  Along with increased bandwidth,
>             or "speed", the
>                        latency performance of DOCSIS technology has
>             also improved in recent
>                        years.  Although it often gets less attention,
>             latency performance
>                        contributes as much or more to the broadband
>             experience and the
>                        feasibility of future applications as does speed.
>
>                        Low Latency DOCSIS technology (LLD) is a
>             specification developed by
>                        CableLabs in collaboration with DOCSIS vendors
>             and cable operators
>                        that tackles the two main causes of latency in
>             the network: queuing
>                        delay and media acquisition delay.  LLD
>             introduces an approach
>                        wherein data traffic from applications that
>             aren't causing latency
>                        can take a different logical path through the
>             DOCSIS network without
>                        getting hung up behind data from applications
>             that are causing
>                        latency, as is the case in today's Internet
>             architectures. This
>                        mechanism doesn't interfere with the way
>             applications share the total
>                        bandwidth of the connection, and it doesn't
>             reduce one application's
>                        latency at the expense of others.  In addition,
>             LLD improves the
>                        DOCSIS upstream media acquisition delay with a
>             faster request-grant
>                        loop and a new proactive scheduling mechanism. 
>             LLD makes the
>                        internet experience better for latency
>             sensitive applications without
>                        any negative impact on other applications.
>
>                        The latest generation of DOCSIS equipment that
>             has been deployed in
>                        the field - DOCSIS 3.1 - experiences typical
>             latency performance of
>                        around 10 milliseconds (ms) on the Access
>             Network link. However,
>                        under heavy load, the link can experience delay
>             spikes of 100 ms or
>                        more.  LLD systems can deliver a consistent 1
>             ms delay on the DOCSIS
>                        network for traffic that isn't causing latency,
>             imperceptible for
>                        nearly all applications. The experience will be
>             more consistent with
>                        much smaller delay variation.
>
>                        LLD can be deployed by field-upgrading DOCSIS
>             3.1 cable modem and
>                        cable modem termination system devices with new
>             software. The
>                        technology includes tools that enable automatic
>             provisioning of these
>                        new services, and it also introduces new tools
>             to report statistics
>                        of latency performance to the operator.
>
>                        Cable operators, DOCSIS equipment
>             manufacturers, and application
>                        providers will all have to act in order to take
>             advantage of LLD.
>                        This white paper explains the technology and
>             describes the role that
>                        each of these parties plays in making LLD a
>             reality.
>
>
>
>
>                     Please note that it may take a couple of minutes
>             from the time of submission
>                     until the htmlized version and diff are available
>             at tools.ietf.org <http://tools.ietf.org>.
>
>                     The IETF Secretariat
>
>
>

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------885B6DAA912926147FB16947
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Luca,<br>
    <br>
    In reviewing this thread I think you haven't received a full answer
    to a question you raised in your email early in the thread (below).<br>
    <br>
    <div class="moz-cite-prefix">On 17/03/2019 08:02, Luca Muscariello
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAHx=1M4y=bEHQ1xt1G59B-DzuU195s4hMapAFmjP0UFqSn403A@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div>One point that is not specified anywhere is when a mflow
        entry is removed front the flow table. <br>
      </div>
      <div>
        <div class="gmail_quote">
          <div dir="auto"><br>
          </div>
          <div dir="auto">As the table is used to blacklist mflows my
            intuition was that it has to be based on some sort of timer.
            Which is another parameter to set in the mechanism. </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">The table then is tracking flows that are in
            progress or maybe not. For sure an entry is maintained even
            for flows w/o packets in the queues.  This has poor
            scalability properties compared to fq where an entry is
            maintained for flows with actual data in the queues.</div>
        </div>
      </div>
    </blockquote>
    [BB] The queue protection algorithm ages out the queuing score held
    for each microflow (mflow) at a constant rate. In fact, the queuing
    score is normalized to time, so that the only value held in the
    bucket for each flow is the bucket's expiry time. For well-behaved
    flows, this expiry time will typically be exceeded before the next
    packet of the same flow arrives. If it has not expired when the next
    packet of the mflow arrives, the algo adds an additional amount of
    time to the mflow's bucket for the new packet. <br>
    <br>
    Thus, only ill-behaved flows persistently consume flow-state memory,
    while well-behaved flows recycle flow-state memory between
    themselves as their packets interleave each other.<br>
    <br>
    The amount of time that the algo adds to an mflow's bucket is the
    queuing score of each of the mflow's packets, normalized to a
    duration, using the following per-packet calculation:<br>
        qscore = pkt_size * p / V<br>
    where:<br>
        p is the current AQM marking probability of the low latency
    queue (dimensionless, in [0,1])<br>
        V is the (constant) congestion-bit-rate deemed acceptable for a
    single mflow (see below for rationale) [b/s]<br>
    <br>
    The division by V normalizes qscore to a duration, because the units
    are [congestion-bit / (congestion-bit / s) = s]. Of course, because
    V is a constant, the division can be implemented as a per-packet
    integer multiply by 1/V. We also choose V to be a power of 2 so a
    bit-shift can be used if more efficient.<br>
    <br>
    The intuition is that the queuing score of an mflow is higher the
    more queuing delay there is when its packets arrive. And the faster
    the mflow's packets arrive, the more likely qscore will accumulate
    faster than the passage of time ages it out. But the formula for
    qscore is not just based on intuition - it comes from shadow pricing
    theory.<br>
    <br>
    Congestion-bit-rate can be conceptualized as the bit-rate of those
    packets of a flow that are ECN-marked. A scalable congestion control
    averages a constant congestion-bit-rate for any flow-rate (i.e. any
    link-rate and any number of flows). So we set V a few times greater
    than that (currently 4x), to allow some variability in a flow
    without risking sanction. This does not mean that flows have to use
    a scalable congestion control to get through Q Protection into the
    low latency queue, it just sets an upper bound under which all
    scalable congestion controls will be able keep. It also sets the bar
    for unresponsive flows, to prevent them causing significantly more
    queuing than responsive scalable flows.<br>
    <br>
    I hope the rest of your questions have been answered satisfactorily
    already by others.<br>
    <br>
    Cheers<br>
    <br>
    <br>
    Bob<br>
    <br>
    <blockquote type="cite"
cite="mid:CAHx=1M4y=bEHQ1xt1G59B-DzuU195s4hMapAFmjP0UFqSn403A@mail.gmail.com">
      <div>
        <div class="gmail_quote">
          <div dir="auto"><br>
          </div>
          <div dir="auto">The protection mechanism assumes that one
            queue has soft priority over  the other. Strict priority
            would be stupid, so there must be a wfq weight to schedule
            the classic queue less frequently. I did not find the magic
            number that  is set in the DOCSIS specs but whatever number
            is chosen I wonder which opitimization objective would be
            the foundation of that.</div>
          <div dir="auto">10%, 20%, 30% or any number would imply that
            if the priority queue is used at 100% utilization the other
            apps would get a small fraction of the link capacity.</div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">What number is chosen and based on which
            calculations? </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">Thanks</div>
          <div dir="auto">Luca </div>
          <div dir="auto"><br>
          </div>
          <div>
            <div class="gmail_quote">
              <div dir="ltr" class="gmail_attr">On Fri 15 Mar 2019 at
                00:42, Greg White &lt;<a
                  href="mailto:g.white@cablelabs.com" target="_blank"
                  moz-do-not-send="true">g.white@cablelabs.com</a>&gt;
                wrote:<br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div link="blue" vlink="purple" lang="EN-US">
                  <div
                    class="m_5835055731700897654m_-5320430196720197056WordSection1">
                    <p class="MsoNormal">Yes, it is easy for
                      applications to access the low latency queue, and
                      the job of QP is to redirect those that shouldn’t
                      have been there.  We could instead run all traffic
                      through QP and let it be automatically sorted, but
                      if there is some traffic that can be excluded a
                      priori, then doing so reduces the queue delay
                      (recall that the QP algorithm only sanctions
                      packets if the queue delay is above the 1ms
                      threshold), reduces the potential that a
                      well-behaving application is sanctioned (perhaps
                      due to hash collisions), etc.   Also, since
                      sanctioning could result in out-of-order delivery
                      for a microflow, presuming that this is ok for all
                      applications might not be advisable.  We have some
                      ideas in the works for modifications that might be
                      useful to reduce the need for packet marking.</p>
                    <p class="MsoNormal"> </p>
                    <p class="MsoNormal">I don’t believe that this
                      mechanism increases DoSability (is that a word?)
                      compared with single queue or fq systems, but
                      would be interested in some validation of that. 
                      Yes it is possible for a malicious sender to mark
                      its packets as NQB, and send at a high rate with
                      various port numbers (to get unique flow ids), and
                      thus have some percentage of packets avoid
                      sanctioning, and in the worst case drive queue
                      delay up.  The default threshold values are being
                      adjusted from what is shown in the spec currently,
                      so when using the new default values, the worst
                      case with carefully crafted attack streams is ~32
                      ms of queuing delay (which, using brute force,
                      would require the malicious sender to launch ~400
                      Mbps of traffic at the QP function).  Similar
                      traffic patterns in a single queue system (or fq)
                      could, depending on egress rate, result in much
                      more queue delay than this.   Also, if the
                      attacker does not mark their packets NQB, then the
                      system protects the NQB flows from the attack, so
                      in this sense it is also slightly less susceptible
                      than single queue (and maybe fq). </p>
                    <p class="MsoNormal"> </p>
                    <p class="MsoNormal"> </p>
                    <p class="MsoNormal"> </p>
                    <div style="border:none;border-top:solid #b5c4df
                      1.0pt;padding:3.0pt 0in 0in 0in">
                      <p class="MsoNormal" style="margin-left:.5in"><b><span
                            style="font-size:12.0pt;color:black">From:
                          </span></b><span
                          style="font-size:12.0pt;color:black">Luca
                          Muscariello &lt;<a
                            href="mailto:luca.muscariello@gmail.com"
                            target="_blank" moz-do-not-send="true">luca.muscariello@gmail.com</a>&gt;<br>
                          <b>Date: </b>Wednesday, March 13, 2019 at
                          4:07 PM<br>
                          <b>To: </b>Greg White
                          <a class="moz-txt-link-rfc2396E" href="mailto:g.white@CableLabs.com">&lt;g.white@CableLabs.com&gt;</a><br>
                          <b>Cc: </b>"<a href="mailto:tsvwg@ietf.org"
                            target="_blank" moz-do-not-send="true">tsvwg@ietf.org</a>"
                          &lt;<a href="mailto:tsvwg@ietf.org"
                            target="_blank" moz-do-not-send="true">tsvwg@ietf.org</a>&gt;<br>
                          <b>Subject: </b>Re: [tsvwg] New Version
                          Notification for draft-white-tsvwg-lld-00.txt</span></p>
                    </div>
                    <div>
                      <p class="MsoNormal" style="margin-left:.5in"> </p>
                    </div>
                    <div>
                      <p class="MsoNormal" style="margin-left:.5in">Greg,
                      </p>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in"> </p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">Is
                          there any intention to also grant access to
                          the low latency queue to applications that do
                          not mark?</p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">Also,
                          if I got this whole mechanism right (big IF),
                          it seems like entering the low latency queue
                          is only based on marking.</p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">This
                          way it looks like the queue is  easy to access
                          and the mechanism reacts to bad behaviour
                          afterwards.</p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">Does
                          not this risk to create spurious packet
                          enqueues into the low latency queue? Or worse
                          malicious sources</p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">to
                          make the low latency queue DoSable?</p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in"> </p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">Luca</p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in"> </p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in"> </p>
                      </div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in"> </p>
                      </div>
                    </div>
                    <p class="MsoNormal" style="margin-left:.5in"> </p>
                    <div>
                      <div>
                        <p class="MsoNormal" style="margin-left:.5in">On
                          Wed, Mar 13, 2019 at 2:03 PM Greg White &lt;<a
                            href="mailto:g.white@cablelabs.com"
                            target="_blank" moz-do-not-send="true">g.white@cablelabs.com</a>&gt;
                          wrote:</p>
                      </div>
                      <blockquote style="border:none;border-left:solid
                        #cccccc 1.0pt;padding:0in 0in 0in
                        6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class="MsoNormal"
                              style="margin-left:.75in">
                              Luca, </p>
                            <p class="MsoNormal"
                              style="margin-left:.75in">
                               </p>
                            <p class="MsoNormal"
                              style="margin-left:.75in">
                              We may work on improving the informative
                              text in that section in order to make the
                              behavior more clear without puzzling
                              through the pseudocode.</p>
                            <p class="MsoNormal"
                              style="margin-left:1.0in">
                               </p>
                            <p
class="m_5835055731700897654m_-5320430196720197056gmail-m-4898144742516953859msolistparagraph"
                              style="margin-left:1.0in">
                              <span>1.<span style="font:7.0pt
                                  &quot;Times New Roman&quot;">     
                                </span></span>A packet enters the QP
                              algorithm if it is classified to the low
                              latency queue.  By default, the intention
                              is to use ((DSCP==NQB) OR (ECN==ECT(1)) OR
                              (ECN==CE)) (see the NQB draft and
                              ECN-L4S-ID draft) to identify likely NQB
                              flows (but this can be changed if
                              needed).  The algorithm of course doesn’t
                              care how the packets get marked, but our
                              view is that the original application (or
                              OS) should be the one that does the
                              marking. For either marking, there is no
                              incentive to lie.</p>
                            <p
class="m_5835055731700897654m_-5320430196720197056gmail-m-4898144742516953859msolistparagraph"
                              style="margin-left:1.0in">
                              <span>2.<span style="font:7.0pt
                                  &quot;Times New Roman&quot;">     
                                </span></span>The algorithm sanctions
                              (redirects to the classic queue) on a
                              per-packet basis.  So, a microflow that
                              only briefly causes queuing will have some
                              of its packets sanctioned during that
                              episode only, and even during that
                              episode, all of its packets are scored. 
                              Note, in some cases this could result in
                              out-of-order delivery, which might be a
                              minor disincentive for persistently QB
                              flows mismarking themselves as NQB.</p>
                            <p
class="m_5835055731700897654m_-5320430196720197056gmail-m-4898144742516953859msolistparagraph"
                              style="margin-left:1.0in">
                              <span>3.<span style="font:7.0pt
                                  &quot;Times New Roman&quot;">     
                                </span></span>See above.</p>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <div link="blue" vlink="purple" lang="EN-US">
                  <div
                    class="m_5835055731700897654m_-5320430196720197056WordSection1">
                    <div>
                      <blockquote style="border:none;border-left:solid
                        #cccccc 1.0pt;padding:0in 0in 0in
                        6.0pt;margin-left:4.8pt;margin-right:0in">
                        <div>
                          <div>
                            <p class="MsoNormal"
                              style="margin-left:.5in">
                               </p>
                            <p class="MsoNormal"
                              style="margin-left:.5in">
                              Greg</p>
                            <p class="MsoNormal"
                              style="margin-left:.5in">
                               </p>
                            <div style="border:none;border-top:solid
                              #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
                              <p class="MsoNormal"
                                style="margin-left:1.0in">
                                <b><span
                                    style="font-size:12.0pt;color:black">From:
                                  </span></b><span
                                  style="font-size:12.0pt;color:black">Luca
                                  Muscariello &lt;<a
                                    href="mailto:luca.muscariello@gmail.com"
                                    target="_blank"
                                    moz-do-not-send="true">luca.muscariello@gmail.com</a>&gt;<br>
                                  <b>Date: </b>Wednesday, March 13,
                                  2019 at 2:37 PM<br>
                                  <b>To: </b>Greg White
                                  <a class="moz-txt-link-rfc2396E" href="mailto:g.white@CableLabs.com">&lt;g.white@CableLabs.com&gt;</a><br>
                                  <b>Cc: </b>"<a
                                    href="mailto:tsvwg@ietf.org"
                                    target="_blank"
                                    moz-do-not-send="true">tsvwg@ietf.org</a>"
                                  &lt;<a href="mailto:tsvwg@ietf.org"
                                    target="_blank"
                                    moz-do-not-send="true">tsvwg@ietf.org</a>&gt;<br>
                                  <b>Subject: </b>Re: [tsvwg] New
                                  Version Notification for
                                  draft-white-tsvwg-lld-00.txt</span></p>
                            </div>
                            <div>
                              <p class="MsoNormal"
                                style="margin-left:1.0in">
                                 </p>
                            </div>
                            <div>
                              <div>
                                <p class="MsoNormal"
                                  style="margin-left:1.0in">
                                  Greg, </p>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                     </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    Thanks for the reference. </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    I have a few questions. I read the
                                    document just once so, don't be
                                    surprised if I got something wrong.</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                     </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    1) A packet enters the low latency
                                    queue if it is marked. Who is
                                    responsible for the marking?</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    Is the original application to do
                                    that?</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                     </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    2) Once a packet enters the low
                                    latency queue, the flow, or
                                    microflow,</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    is tracked in a (micro)flow table by
                                    reporting a function of the queue
                                    occupancy.  How do updates of the
                                    table</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    take place? Insert is clear unless
                                    the flow is banned, update is
                                    clear.. Remove is only clear to me
                                    when the flow is moved </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    out of the low latency queue once it
                                     started to get too much resources.
                                    Remove in the general case is not
                                    clear to me. Timers?</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                     </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    3)  It seems like the mechanism
                                    trusts the packet marker until the
                                    queue protection mechanism takes</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    a different decision. How can a
                                    marker be redeemed and related
                                     packets be readmitted to the low
                                    latency queue?</p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                     </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                     </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    Thanks </p>
                                </div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    Luca </p>
                                </div>
                              </div>
                            </div>
                            <div>
                              <p class="MsoNormal"
                                style="margin-left:1.0in">
                                 </p>
                              <div>
                                <div>
                                  <p class="MsoNormal"
                                    style="margin-left:1.0in">
                                    On Mon, Mar 11, 2019 at 7:18 PM Greg
                                    White &lt;<a
                                      href="mailto:g.white@cablelabs.com"
                                      target="_blank"
                                      moz-do-not-send="true">g.white@cablelabs.com</a>&gt;
                                    wrote:</p>
                                </div>
                                <blockquote
                                  style="border:none;border-left:solid
                                  #cccccc 1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
                                  <p class="MsoNormal"
                                    style="margin-bottom:12.0pt;margin-left:1.0in">
                                    Hi Luca, <br>
                                    <br>
                                    You can find the details in Annex P
                                    of the DOCSIS MULPIv3.1 spec.<br>
                                    <a
                                      href="https://specification-search.cablelabs.com/CM-SP-MULPIv3.1"
                                      target="_blank"
                                      moz-do-not-send="true">https://specification-search.cablelabs.com/CM-SP-MULPIv3.1</a><br>
                                    <br>
                                    -Greg<br>
                                    <br>
                                    <br>
                                    From: Luca Muscariello &lt;<a
                                      href="mailto:luca.muscariello@gmail.com"
                                      target="_blank"
                                      moz-do-not-send="true">luca.muscariello@gmail.com</a>&gt;<br>
                                    Date: Monday, March 11, 2019 at 6:26
                                    PM<br>
                                    To: Greg White
                                    <a class="moz-txt-link-rfc2396E" href="mailto:g.white@CableLabs.com">&lt;g.white@CableLabs.com&gt;</a><br>
                                    Cc: Dave Taht &lt;<a
                                      href="mailto:dave@taht.net"
                                      target="_blank"
                                      moz-do-not-send="true">dave@taht.net</a>&gt;,
                                    Jonathan Morton &lt;<a
                                      href="mailto:chromatix99@gmail.com"
                                      target="_blank"
                                      moz-do-not-send="true">chromatix99@gmail.com</a>&gt;,
                                    "<a href="mailto:tsvwg@ietf.org"
                                      target="_blank"
                                      moz-do-not-send="true">tsvwg@ietf.org</a>"
                                    &lt;<a href="mailto:tsvwg@ietf.org"
                                      target="_blank"
                                      moz-do-not-send="true">tsvwg@ietf.org</a>&gt;<br>
                                    Subject: Re: [tsvwg] New Version
                                    Notification for
                                    draft-morton-taht-tsvwg-sce-00.txt<br>
                                    <br>
                                    Hi Greg,<br>
                                    <br>
                                    I'm curious about the queue
                                    protection function in the LLD
                                    document.<br>
                                    It seems to assume that a flow table
                                    is maintained to determine if a flow
                                    <br>
                                    has the right to enter the low
                                    latency queue.<br>
                                    <br>
                                    Can you give more details about that
                                    component? Or point me to a
                                    reference?<br>
                                    <br>
                                    Thanks<br>
                                    Luca<br>
                                    <br>
                                    <br>
                                    On 3/11/19, 5:29 PM, "tsvwg on
                                    behalf of Greg White" &lt;<a
                                      href="mailto:tsvwg-bounces@ietf.org"
                                      target="_blank"
                                      moz-do-not-send="true">tsvwg-bounces@ietf.org</a>
                                    on behalf of
                                    <a class="moz-txt-link-abbreviated" href="mailto:g.white@CableLabs.com">g.white@CableLabs.com</a>&gt; wrote:<br>
                                    <br>
                                        TSVWG,<br>
                                    <br>
                                        I've posted a new informative
                                    draft that gives an overview of the
                                    new Low Latency DOCSIS specification
                                    (see links below).  This overview
                                    may be interesting to TSVWG
                                    participants because it includes
                                    support for L4S (<a
href="https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-aqm-dualq-coupled"
                                      target="_blank"
                                      moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-aqm-dualq-coupled</a>)
                                    and for the NQB PHB (<a
                                      href="https://datatracker.ietf.org/doc/html/draft-white-tsvwg-nqb"
                                      target="_blank"
                                      moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-white-tsvwg-nqb</a>).<br>
                                    <br>
                                        Best Regards,<br>
                                        Greg<br>
                                    <br>
                                    <br>
                                    <br>
                                        On 3/11/19, 5:05 PM, "<a
                                      href="mailto:internet-drafts@ietf.org"
                                      target="_blank"
                                      moz-do-not-send="true">internet-drafts@ietf.org</a>"
                                    &lt;<a
                                      href="mailto:internet-drafts@ietf.org"
                                      target="_blank"
                                      moz-do-not-send="true">internet-drafts@ietf..org</a>&gt;
                                    wrote:<br>
                                    <br>
                                    <br>
                                            A new version of I-D,
                                    draft-white-tsvwg-lld-00.txt<br>
                                            has been successfully
                                    submitted by Greg White and posted
                                    to the<br>
                                            IETF repository.<br>
                                    <br>
                                            Name:         
                                     draft-white-tsvwg-lld<br>
                                            Revision:       00<br>
                                            Title:          Low Latency
                                    DOCSIS - Technology Overview<br>
                                            Document date:  2019-03-11<br>
                                            Group:          Individual
                                    Submission<br>
                                            Pages:          25<br>
                                            URL:            <a
                                      href="https://www.ietf.org/internet-drafts/draft-white-tsvwg-lld-00.txt"
                                      target="_blank"
                                      moz-do-not-send="true">
https://www.ietf.org/internet-drafts/draft-white-tsvwg-lld-00.txt</a> <br>
                                            Status:         <a
                                      href="https://datatracker.ietf.org/doc/draft-white-tsvwg-lld/"
                                      target="_blank"
                                      moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-white-tsvwg-lld/</a>
                                    <br>
                                            Htmlized:       <a
                                      href="https://tools.ietf.org/html/draft-white-tsvwg-lld-00"
                                      target="_blank"
                                      moz-do-not-send="true">https://tools.ietf.org/html/draft-white-tsvwg-lld-00</a>
                                    <br>
                                            Htmlized:       <a
                                      href="https://datatracker.ietf.org/doc/html/draft-white-tsvwg-lld"
                                      target="_blank"
                                      moz-do-not-send="true">https://datatracker.ietf.org/doc/html/draft-white-tsvwg-lld</a>
                                    <br>
                                    <br>
                                    <br>
                                            Abstract:<br>
                                               NOTE: This document is a
                                    reformatted version of
                                    [LLD-white-paper].<br>
                                    <br>
                                               The evolution of the
                                    bandwidth capabilities - from
                                    kilobits per<br>
                                               second to gigabits -
                                    across generations of DOCSIS cable
                                    broadband<br>
                                               technology has paved the
                                    way for the applications that today
                                    form our<br>
                                               digital lives.  Along
                                    with increased bandwidth, or
                                    "speed", the<br>
                                               latency performance of
                                    DOCSIS technology has also improved
                                    in recent<br>
                                               years.  Although it often
                                    gets less attention, latency
                                    performance<br>
                                               contributes as much or
                                    more to the broadband experience and
                                    the<br>
                                               feasibility of future
                                    applications as does speed.<br>
                                    <br>
                                               Low Latency DOCSIS
                                    technology (LLD) is a specification
                                    developed by<br>
                                               CableLabs in
                                    collaboration with DOCSIS vendors
                                    and cable operators<br>
                                               that tackles the two main
                                    causes of latency in the network:
                                    queuing<br>
                                               delay and media
                                    acquisition delay.  LLD introduces
                                    an approach<br>
                                               wherein data traffic from
                                    applications that aren't causing
                                    latency<br>
                                               can take a different
                                    logical path through the DOCSIS
                                    network without<br>
                                               getting hung up behind
                                    data from applications that are
                                    causing<br>
                                               latency, as is the case
                                    in today's Internet architectures. 
                                    This<br>
                                               mechanism doesn't
                                    interfere with the way applications
                                    share the total<br>
                                               bandwidth of the
                                    connection, and it doesn't reduce
                                    one application's<br>
                                               latency at the expense of
                                    others.  In addition, LLD improves
                                    the<br>
                                               DOCSIS upstream media
                                    acquisition delay with a faster
                                    request-grant<br>
                                               loop and a new proactive
                                    scheduling mechanism.  LLD makes the<br>
                                               internet experience
                                    better for latency sensitive
                                    applications without<br>
                                               any negative impact on
                                    other applications.<br>
                                    <br>
                                               The latest generation of
                                    DOCSIS equipment that has been
                                    deployed in<br>
                                               the field - DOCSIS 3.1 -
                                    experiences typical latency
                                    performance of<br>
                                               around 10 milliseconds
                                    (ms) on the Access Network link. 
                                    However,<br>
                                               under heavy load, the
                                    link can experience delay spikes of
                                    100 ms or<br>
                                               more.  LLD systems can
                                    deliver a consistent 1 ms delay on
                                    the DOCSIS<br>
                                               network for traffic that
                                    isn't causing latency, imperceptible
                                    for<br>
                                               nearly all applications. 
                                    The experience will be more
                                    consistent with<br>
                                               much smaller delay
                                    variation.<br>
                                    <br>
                                               LLD can be deployed by
                                    field-upgrading DOCSIS 3.1 cable
                                    modem and<br>
                                               cable modem termination
                                    system devices with new software. 
                                    The<br>
                                               technology includes tools
                                    that enable automatic provisioning
                                    of these<br>
                                               new services, and it also
                                    introduces new tools to report
                                    statistics<br>
                                               of latency performance to
                                    the operator.<br>
                                    <br>
                                               Cable operators, DOCSIS
                                    equipment manufacturers, and
                                    application<br>
                                               providers will all have
                                    to act in order to take advantage of
                                    LLD.<br>
                                               This white paper explains
                                    the technology and describes the
                                    role that<br>
                                               each of these parties
                                    plays in making LLD a reality.<br>
                                    <br>
                                    <br>
                                    <br>
                                    <br>
                                            Please note that it may take
                                    a couple of minutes from the time of
                                    submission<br>
                                            until the htmlized version
                                    and diff are available at <a
                                      href="http://tools.ietf.org"
                                      target="_blank"
                                      moz-do-not-send="true">
                                      tools.ietf.org</a>.<br>
                                    <br>
                                            The IETF Secretariat<br>
                                    <br>
                                    <br>
                                    <br>
                                  </p>
                                </blockquote>
                              </div>
                            </div>
                          </div>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </div>
              </blockquote>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------885B6DAA912926147FB16947--


From nobody Thu Apr  4 04:53:46 2019
Return-Path: <dave.taht@gmail.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 992F112000E for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 04:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=unavailable 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 4DZYbfl__KHT for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 04:53:36 -0700 (PDT)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 5C304120489 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 04:53:36 -0700 (PDT)
Received: by mail-qk1-x729.google.com with SMTP id o129so1391103qke.8 for <tsvwg@ietf.org>; Thu, 04 Apr 2019 04:53:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MWi4kABLAoGA97QyLPYpSSSS+5MNty8pYx3p8n+eFXg=; b=tRNBt65cQS9GFqAGWPmUqHGhq0L7+V4XiuhrmveQP/8ID8KGa5BMIzHuV8ADFq9G2i ouL6F7vQyZCv7d+yH+itiMKKvRuxr3FMzUuyewmR7mB0/RiaivJtsGQKYbqk5MNpWYrS E+AmKNonGjw3h4D6fA68CHwVbg/P1tpoR4Uywfz76ng0ocSPP8LGU+u3Uxjkkx8/S9Px 35hQFrMItWfXFSiMW+V/rz1p7o+OeHpTVVoMRfwpVUH5EtAKqjJj27kELs/n3rZQv/Gu pkRedyGNzY6o9rsbEM+vkVbkFu20vHqMisDw+Z8joyzd8vpxfVs1yrVj5S94fuCES+O7 uPuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MWi4kABLAoGA97QyLPYpSSSS+5MNty8pYx3p8n+eFXg=; b=nwzfdcGAKFEAhwPFP54ppra9Sl+XswqqnrSmS2H2FxbHHKwkU4OY7dIDayaQqwjaS/ /0aHHBVLpusLpqQVZNV2jQ4ucmZ+o2KCoI7W1MhiGJJXHpe+g7OWh8gZIU5z33UnW6u+ QHxEdEqqZeVoNyl0LTpuV1oUKQzfNNqMolhLgy416OMq5+/e3pUeI/+yeoPrrxwwtJ4C FnqXPFNcbKRm9/Jl1GJqvvJ3g9gs0iRzosac62/0uh4gWuQYQR7f/SParW7vj0NmYz8v U+zoT5AY6WtYh9gENZ1RhwpfxutPDGx7TCBUlplEnbhx4ppe23TX/sQ5s8UsPwtvrc60 6xuw==
X-Gm-Message-State: APjAAAW5T6PzlcXSdfkSh1MphkiNaeYrAub8pyxFUjt2CdTYalwEy/Og gNu1pXzhDknH/yTBb0s03t7BkXlQxhT0H8g7+XQ=
X-Google-Smtp-Source: APXvYqzHfxQ1vqf6gkRuNfNPdD/8GWSJuaeBcmPW3Y0Hf86IPvG3iLGI5umKW+g2bptsK28kWIfxtuPv5NVMxbc5K7E=
X-Received: by 2002:a37:a5d8:: with SMTP id o207mr4753507qke.0.1554378815382;  Thu, 04 Apr 2019 04:53:35 -0700 (PDT)
MIME-Version: 1.0
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com> <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com>
In-Reply-To: <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com>
From: Dave Taht <dave.taht@gmail.com>
Date: Thu, 4 Apr 2019 13:52:54 +0200
Message-ID: <CAA93jw6L66jNgvO9M6CVvQjX66Ha_SWaomzBrFs9QO0pGC-ASg@mail.gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Greg White <g.white@cablelabs.com>, "iccrg@irtf.org" <iccrg@irtf.org>,  Sebastian Moeller <moeller0@gmx.de>, Bob Briscoe <in@bobbriscoe.net>, tsvwg IETF list <tsvwg@ietf.org>,  ECN-Sane <ecn-sane@lists.bufferbloat.net>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/kWLX9E78qq2ygpt5QDaXKZG5KAY>
Subject: Re: [tsvwg] [iccrg]  IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 11:53:39 -0000

Several things...

I find discussions of ECN in general very stressful, as I am firmly on
the ecn-sane "yellow" team. ECN scares me on the general internet.
More than anything else, I'd like to get a big DDOS protection
provider and university to tackle all my outstanding issues with using
ECN in a general deployment - ranging from what happens with tcp syn
ecn enabled attacks, to ddos protection from udp based packet floods,
as I outlined in the ecn-sane project's charter:
https://www.bufferbloat.net/projects/ecn-sane/wiki/ before I can
endorse this work.

I have friends that regularly deal with 2TByte/sec DDOS attacks and
they have worse blood pressure problems than I do.

I've long had no problem with ecn in specialized deployments, under
rigidly controlled conditions. The SCE work, in particular, looks to
be useful for technologies like nvme over tcp and roce and stuff like
that, and I look forward to results there.

One of the proudest things I have ever had going in my life is that
the backhauls and groundstations for the arkyd-6 spacecraft, used
fq_codel with ECN enabled... running lede (openwrt). And though I
can't talk about that project much, and probably shouldn't have
mentioned even that much here  - I tend to feel that any non-backward
compatible change to ecn will muck with *my* bird in a 25 year orbit,
and I kind of take it a bit personally any naive interference with
that contribution to the US space program.

I am unsubscribing from the ietf lists as of now, so I can focus on
getting testbeds and analytical tools up, as well as finishing up my
work on the ipv4 unicast extensions project, which is entirely
separate, that I wish I could get more folk to pay attention to.

If there is a productive conversation of interest to me, here, using
debating techniques I can live with (
https://www.bufferbloat.net/projects/ecn-sane/wiki/rules/ ) please
either send a link or cc ecn-sane@lists.bufferbloat.net.

Thank you.

Dave


From nobody Thu Apr  4 08:37:19 2019
Return-Path: <g.white@CableLabs.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 ACAAD120645 for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 08:37:07 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 bgFl24pLbvmN for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 08:37:05 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760134.outbound.protection.outlook.com [40.107.76.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C2E112064A for <tsvwg@ietf.org>; Thu,  4 Apr 2019 08:37:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IjQEgpijuwnBNI8y/3jWXSa9t1sbjoZ5MgRNvyMB/W4=; b=G9E4XEYxsBbOnxD1oA0dIFnBWXPARXK9a5LYQiO5i6Kh/Ywrm2EKbL3gkFYhJ9tbbRgTdyYR0iErMfBi8EQC/VP+c0RvrE+psoJgwRLZjCOgvgQxeeyVfvkhjfmwdvD4QcbebQ/xuT234sqgot4Y5uDkilSsQ8aaKmGATtFYKw8=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB4736.namprd06.prod.outlook.com (52.135.117.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.17; Thu, 4 Apr 2019 15:37:02 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c%6]) with mapi id 15.20.1750.021; Thu, 4 Apr 2019 15:37:02 +0000
From: Greg White <g.white@CableLabs.com>
To: Jonathan Morton <chromatix99@gmail.com>
CC: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: [iccrg] [tsvwg]  IETF104 ICCRG TCP Prague presentation
Thread-Index: AQHU6ksFATQlV6AwuEyVhJCWJn+a66YrJhqA////44CAAKshgIAABXQAgABeGYA=
Date: Thu, 4 Apr 2019 15:37:02 +0000
Message-ID: <817A985F-2974-4755-B294-8CEEBFCAC744@cablelabs.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com> <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com>
In-Reply-To: <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.14.0.181208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com; 
x-originating-ip: [77.76.75.108]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ca302598-9ea2-42e0-b902-08d6b913625c
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR06MB4736; 
x-ms-traffictypediagnostic: SN6PR06MB4736:
x-microsoft-antispam-prvs: <SN6PR06MB4736E70FC56B0509646CD5BFEE500@SN6PR06MB4736.namprd06.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(366004)(376002)(136003)(39850400004)(396003)(189003)(199004)(1411001)(82746002)(53936002)(6116002)(97736004)(8936002)(229853002)(102836004)(25786009)(6916009)(186003)(6506007)(86362001)(53546011)(5660300002)(71200400001)(8676002)(106356001)(478600001)(105586002)(93886005)(14454004)(81156014)(33656002)(36756003)(81166006)(76176011)(99286004)(71190400001)(68736007)(26005)(6246003)(446003)(7736002)(476003)(305945005)(2906002)(3846002)(66066001)(11346002)(256004)(316002)(486006)(83716004)(58126008)(54906003)(6512007)(6486002)(4326008)(2616005)(6436002)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB4736; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: WLDHTtNDS9Tqpg4KyzJ0k0rM6xoW3IPWDD29zqC80Cpi95btzoJ1HWCsWGMxgRs3s1hvQZIUoP45Znq3NYnmgychfcpJ9ONl97esEgGe236+zXCHw4nVvVKVNCmbTDCjjriKb9v0vG8b6fEzuJJciMytw/hIj9ztmytdFJcNyPCPRtamtc3kZbnpgwbnwIJomWJy9419mOkWwhn9lFweoDSZeHQLFbldAhxjW9khTtqaBasJQUrSJNZglsO2R8yotKvvd1/le7igif2EmsUqBZtdVMVkybvco80/++q63oGxm+sYZXzLrNRjxLpTl0VarwqdENDwWR5mpB/Y/SkYehh8DZUly0JVlRQfkwGRbQsexVRO99JNO+YtnPFvCA7B5D2wp+FKh3wydIQCu7clWahSiPCt87iulcPonSFWJFY=
Content-Type: text/plain; charset="utf-8"
Content-ID: <64B65CC8C0DF554A8763BBF04F4E283E@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ca302598-9ea2-42e0-b902-08d6b913625c
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 15:37:02.3753 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB4736
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/EOtuqhiUfVDo8VQA57T3LRuLACw>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 15:37:13 -0000

T24gNC80LzE5LCAxMjowMCBQTSwgIkpvbmF0aGFuIE1vcnRvbiIgPGNocm9tYXRpeDk5QGdtYWls
LmNvbT4gd3JvdGU6DQoNCiAgICA+IE9uIDQgQXByLCAyMDE5LCBhdCAxMjo0MCBwbSwgR3JlZyBX
aGl0ZSA8Zy53aGl0ZUBDYWJsZUxhYnMuY29tPiB3cm90ZToNCiAgICA+IA0KICAgID4gSSBkb24n
dCBkb3VidCB0aGF0IHRoZSBTQ0Ugc2lnbmFsaW5nIG1ldGhvZCBjb3VsZCBiZSB1c2VkIGluIGEg
dmFyaWFudCBvZiBEQ1RDUCwgYnV0IHRoZSAqaHVnZSogZG93bnNpZGUgaXMgdGhhdCBpdCBjYW4g
b25seSB3b3JrIG9uIGJvdHRsZW5lY2sgbGlua3MgdGhhdCBhcmUgYWJsZSAob3Igd2lsbGluZykg
dG8gc3VwcG9ydCBGUSwgd2hpY2ggd2lsbCBiZSBwcmVjaW91cyBmZXcuDQogICAgDQogICAgTGV0
IG1lIHN0b3AgeW91IHJpZ2h0IHRoZXJlLiAgWW91IGFyZSByZW1lbWJlcmluZyBhIGRpc2N1c3Np
b24gd2UgaGFkIGF0IGxlYXN0IHR3byB3ZWVrcyBhZ28sIGJhc2VkIG9uIGFuIGVhcmx5IGNvbmNl
cHQgb2YgU0NFIHdoaWNoIGhhcyBzaW5jZSBiZWVuIHN1cGVyc2VkZWQuDQogICAgDQogICAgV2Ug
aGF2ZSBydW5uaW5nIGNvZGUgd2hpY2ggY29udmVyZ2VzIHJhcGlkbHkgdG8gZmFpcmx5IHNoYXJp
bmcgdGhlIGxpbmsgYmV0d2VlbiB0d28gU0NFIGZsb3dzLCB3aXRoIG9ubHkgYSBzaW5nbGUtcXVl
dWUgU0NFLWF3YXJlIEFRTS4gIFRoYXQgaXMsIHdlIHVzZWQgdGhlICJiZXN0ZWZmb3J0IiBhbmQg
ImZsb3dibGluZCIgbW9kZXMgb2YgQ2FrZSwgd2hpY2ggZGlzYWJsZSBpdHMgRGlmZnNlcnYgYW5k
IGZsb3ctaXNvbGF0aW9uIGNhcGFiaWxpdGllcywgc3BlY2lmaWNhbGx5IHRvIHRlc3QgdGhhdCBh
c3BlY3Qgb2Ygb3VyIHdvcmsuICBTaW5jZSBvdXIgcHJvdG90eXBlIFNDRSByZXNwb25zZSBpcyBE
Q1RDUC1saWtlLCB0aGF0IHJlc3VsdCBzaG91bGQgbm90IGJlIGEgc3VycHJpc2UgdG8geW91Lg0K
ICAgIA0KICAgIFdlICphbHNvKiBiZWxpZXZlIHdlIGhhdmUgYSBzb2x1dGlvbiBmb3IgZmFpcmx5
IHNoYXJpbmcgYSBzaW5nbGUgcXVldWUgYmV0d2VlbiBTQ0UgYW5kIG5vbi1TQ0UgZmxvd3MuICBX
ZSBoYXZlbid0IGltcGxlbWVudGVkIGFuZCB0ZXN0ZWQgaXQgeWV0LCBob3dldmVyLiAgV29yayBj
b250aW51ZXMuDQogICAgDQoNCltHV10gRmFpcmx5IHNoYXJpbmcgdGhlIGxpbmsgd2Fzbid0IHRo
ZSBjb25jZXJuIHRoYXQgSSB3YXMgYWxsdWRpbmcgdG8gYnkgc2F5aW5nIHRoYXQgU0NFIG9ubHkg
d29ya3Mgd2l0aCBGUS4gIE15IHByZXN1bXB0aW9uIHdhcyB0aGF0IHRoaXMgd291bGQgYmUgcG9z
c2libGUuICAgTXkgY29uY2VybiBpcyB0aGF0IHRoZSBTQ0Ugc2VuZGVyIGdldHMgKnplcm8qIGJl
bmVmaXQgZnJvbSBzdXBwb3J0aW5nIFNDRSBzaWduYWxpbmcgdW5sZXNzIHRoZSBib3R0bGVuZWNr
IGxpbmsgaXMgYW4gRlEgbGluay4gICBJbiBteSB2aWV3IHRoZSBJRVRGIHNob3VsZCBub3QgY29u
c2lkZXIgYnVybmluZyB0aGUgbGFzdCBjb2RlIHBvaW50IGZvciBzdWNoIGEgbGltaXRlZCBwdXJw
b3NlLiAgVGhlIEw0UyBkZWZpbml0aW9uIHByb3ZpZGVzICp2YWx1ZSogKGkuZS4gdWx0cmEtbG93
IGxhdGVuY3kpIHdoZW4gdGhlIGJvdHRsZW5lY2sgaXMgZWl0aGVyIEZRIG9yIER1YWxRLg0KDQoN
Cg0K


From nobody Thu Apr  4 08:43:31 2019
Return-Path: <chromatix99@gmail.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 67D911200A0 for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 08:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 Nbbg64VpygUo for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 08:43:22 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 C0F79120606 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 08:43:21 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id k8so2503919lja.8 for <tsvwg@ietf.org>; Thu, 04 Apr 2019 08:43:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JomifhIsprqPr4+8ytbURkfsrEqwf8oUjTEMpRvh5o4=; b=vKieuN0OjbiwW2HT62wKFBNkKQggwFtz5FCtw9qAyiCAwbCWrEjCNGrAivtyGGarJn PO5wHLfr5+GlZVqgUw+GNSWqN59qfTfGt0dccI/QC6/OiqzE3RLDlgFM668ZPcmllIPu DMeQt7VEqfwJfrQ7QG3707BZAUugTlX6Hvoj9Nmv5b5xVW1ZIOG0Egc8MmYvHiSvQLZU aJ4raaLbgEV79UawRKq190DpZzIMrUW4IejcJNq01eb1DMGu69vLd1K8ogugd6hypTO7 XCLezyH2/5xMfudtNMPxS7GQNuyyJv4lLnp1V/tJBCyOv4SC3M+QLNccXHTs9NHlA3ho oPhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JomifhIsprqPr4+8ytbURkfsrEqwf8oUjTEMpRvh5o4=; b=RqUcTKPRJ8HvZjni3mrw+XQq1X2nUWOnXQiMCQ/cR2+waJ+IHmF8IgUd8EYcAnsoBG XBKUOEO6Yirs3D3MUOY8T/kJzIKH9/wRvlRrbJIWWqOL/uwMOS8v8O7y1jAXEQpdCTFe 5Q+98EE0x1gSKMQhRhcEyAwAlVbl6PZzkL9VIi6dDe/4SWy4/Fc4iqPQ8Qa8BRX3fIyz jOM9mlZQPQEzmqNigniUPHMUbBcdoFeqdTRkHD8Cp7e+BiyZlLUB5C1Ij6qEm5Ujd99P 8g2CXPGp49u176JsknJ1Ew9f+kIRGZJLd2tmeNzFbYqCV3qoKE0ILPGOALD0MTuaxoaI xkaA==
X-Gm-Message-State: APjAAAUt4Swj2FgJgVUNKkVosjZ9ILXVow/cWxgAWu8F9c+N49jZsYMb y6hr5wC00zMsaaHJoEdmClo=
X-Google-Smtp-Source: APXvYqxvFnCDmdY9TNqyArRjxhKAfYD7TBIGUIVrm4vma31ihOja4hcAOOlRxITKLqB7ddvmlraRxw==
X-Received: by 2002:a2e:8648:: with SMTP id i8mr3903272ljj.166.1554392600060;  Thu, 04 Apr 2019 08:43:20 -0700 (PDT)
Received: from jonathartonsmbp.lan (83-245-225-56-nat-p.elisa-mobile.fi. [83.245.225.56]) by smtp.gmail.com with ESMTPSA id s67sm3992716lja.57.2019.04.04.08.43.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Apr 2019 08:43:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <817A985F-2974-4755-B294-8CEEBFCAC744@cablelabs.com>
Date: Thu, 4 Apr 2019 18:43:17 +0300
Cc: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <019569E3-9D93-41B9-8D0A-D1E3501D9B3D@gmail.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com> <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com> <817A985F-2974-4755-B294-8CEEBFCAC744@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/OHtGq_sB8tLQ3pZeMGnd5lvySkA>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 15:43:24 -0000

> On 4 Apr, 2019, at 6:37 pm, Greg White <g.white@CableLabs.com> wrote:
>=20
> My concern is that the SCE sender gets *zero* benefit from supporting =
SCE signaling unless the bottleneck link is an FQ link.

Our early results suggest otherwise.  However, I would like to flesh =
them out before further detailed discussion.

 - Jonathan Morton=


From nobody Thu Apr  4 10:06:26 2019
Return-Path: <g.white@CableLabs.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 053141201DC for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 10:06:25 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 GiEigdm93T7L for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 10:06:23 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-eopbgr790127.outbound.protection.outlook.com [40.107.79.127]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BB0B120104 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 10:06:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=okr8I2vE4XkUoLkaPUBGQ9LvgbpidJupCdijcDUaSXM=; b=QmYjtE3v0X7iv/WTCAxzEZQk8OPf1I5aDzKC7nUic526eIXLNiMP7NAL4JKTfRUNVxwOh8KPKN6Rlu+1FTRNk2vfA6MyaNCE0Ip9rVTsG6CCmKqfNmq6Nma87yLa7c87+uUO+ly04uLVFxNFsKyQgtRQOlhGkFPJmrfgDVMHrAE=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB4607.namprd06.prod.outlook.com (52.135.115.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.17; Thu, 4 Apr 2019 17:06:18 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c%6]) with mapi id 15.20.1750.021; Thu, 4 Apr 2019 17:06:18 +0000
From: Greg White <g.white@CableLabs.com>
To: Sebastian Moeller <moeller0@gmx.de>
CC: Jonathan Morton <chromatix99@gmail.com>, Bob Briscoe <in@bobbriscoe.net>,  "iccrg@irtf.org" <iccrg@irtf.org>, tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: [iccrg] [tsvwg]  IETF104 ICCRG TCP Prague presentation
Thread-Index: AQHU6ksFATQlV6AwuEyVhJCWJn+a66YrJhqAgACn9oCAAH+LAA==
Date: Thu, 4 Apr 2019 17:06:18 +0000
Message-ID: <AD99A4E5-B7F9-49CC-BFAC-E33DDD97BCCC@cablelabs.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <59D6B58C-C966-493C-B3B9-CAD3AD7AD5F9@gmx.de>
In-Reply-To: <59D6B58C-C966-493C-B3B9-CAD3AD7AD5F9@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.14.0.181208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com; 
x-originating-ip: [176.12.107.132]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ce942540-7bdf-488b-7bf6-08d6b91fdabb
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:SN6PR06MB4607; 
x-ms-traffictypediagnostic: SN6PR06MB4607:
x-microsoft-antispam-prvs: <SN6PR06MB460740D466F57EA5B5564440EE500@SN6PR06MB4607.namprd06.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(39850400004)(396003)(366004)(346002)(199004)(189003)(476003)(97736004)(486006)(82746002)(446003)(33656002)(11346002)(36756003)(2616005)(2906002)(5660300002)(14454004)(26005)(68736007)(6916009)(3846002)(6116002)(25786009)(4326008)(76176011)(81166006)(81156014)(256004)(6506007)(99286004)(71200400001)(8936002)(71190400001)(229853002)(102836004)(6246003)(83716004)(93886005)(186003)(54906003)(316002)(6512007)(53936002)(478600001)(66066001)(7736002)(106356001)(58126008)(86362001)(6436002)(305945005)(105586002)(6486002)(53546011)(8676002)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB4607; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: iVFLwozEVT6jFQhmTC6xgGvJTplG1V+u1rupRLGaekxzRlQL1qMWAafHCBEG4C4OfSgJenRYvwkRh1X+rZ/CEq4LD3d7qQw7t2inGGVgZ7S1NhamodpTCCGFvFNoiuP2gjMlXx0NuoU/H/O+8dVkFJiAFtwJbqWQq05jmz7pHwpmemBYbeGlyALCh4g+84Aneewr0YTNim6tf3/+611k7mRyLUhRtdTM9XDyUH2bEjU/iyiuEPhbHur+27zFhhGH9Xg377XUOvsjP2JymewJbg3oAcz/fdaz1AFbpuJJ07SiOWlhaOH6sKGDi21rIZVjBPZPesw/S5MBZAuwJ1K8aavmSboDvmmNvLvwL7LO2rmf4uZY5C97/jpP+td4WzPq5BLwvPN8VVa4M+gwzGW5tNgICGy/0SZDhNLcM9XUgiI=
Content-Type: text/plain; charset="utf-8"
Content-ID: <D9D1D83BD93F3C4FBD8B86CFFC25C9D9@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ce942540-7bdf-488b-7bf6-08d6b91fdabb
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 17:06:18.2857 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB4607
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/lresBXGfn0O4do5WjfmLsbyK3_A>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 17:06:25 -0000

T24gNC80LzE5LCAxMToyOSBBTSwgIlNlYmFzdGlhbiBNb2VsbGVyIiA8bW9lbGxlcjBAZ214LmRl
PiB3cm90ZToNCg0KICAgIEhpIEdyZWcsDQogICAgDQogICAgW1NNXTogSSBoYXBwZW4gdG8gYmVs
aWV2ZSB0aGF0IGhlYWQtZW5kIEFRTSB3aWxsIGFtZWxpb3JhdGUgdGhlIG5lZWQgZm9yIGFuIGlu
Z3Jlc3MgQVFNIGZvciBhIGxvdCBvZiBjYXN1YWwgdXNlcnMsIGJ1dCBhbGwgdGhvc2UgdGhhdCBh
cmUgY29uc3RhbnRseSBydW5uaW5nIGFnYWluc3QgY2FwYWNpdHkgbGltaXRzICh0aGluayBBRFNM
KSB0eXBpY2FsbHkgZGVzaXJlIGEgbW9yZSBmaW5lLWdyYWluZWQgcHJpb3JpdGl6YXRpb24gdGhh
biBhIGhlYWQtZW5kIEFRTSBpcyBnb2luZyB0byBvZmZlciwgaW5jbHVkc2luZyByZXN0cmljdGlu
ZyBiYW5kd2lkdGggdG8gY2VydGFpbiBwcm9pb3JldHkgY2xhc3NlcyB0byBzYXkga2VlcCBsYXRl
bmN5IGluY3JlYXMgZm9yIGdhbWUgdHJhZmZpYyB0aWdodGx5IGJvdW5kLiBJIGJlbGlldmUgaW4g
dGhhdCBjYXNlIHRoZSBndWFyYW50ZWVzIEw0UyBvZmZlcnMgYXJlIG5vdCBzdWZmaWNpZW50LCBh
cyB0aGUgZ2FtaW5nIGNhc2UgcmVxdWlyZXMgImd1YXJhbnRlZWQgYmFuZHdpZHRoIGF0IGEgY2Vy
dGFpbiBsYXRlbmN5IGxldmVsIiBhcyBjb21wYXJlZCB0byB0aGUgbG93X3F1ZXVldW5nIGxhdGVu
Y3kgZ3VhcmFudGVlIEw0UyBvZmZlcnMgKHdoaWNoIGJhc2ljYWxseSBtb3ZlcyB0aGUgcXVlIGJh
Y2sgaW50byB0aGUgc2VuZGluZyBlbmQtaG9zdCwgd2hpY2ggaXMgZmluZSwgYnV0IGFsbCBpdCBk
b2VzIG5vdCBoZWxwIGlmIEkgbmVlZCB0byBzZW5kIEAgWCBIeikuDQogICAgDQpbR1ddICBJbiBh
biBMNFMgd29ybGQsIHRoZXJlIGlzIG5vdGhpbmcgdGhhdCBwcmV2ZW50cyBhIHVzZXIgcnVubmlu
ZyBhbiAiaW5ncmVzcyBBUU0iIG9mIHRoZWlyIGNob2ljZSB3aXRoIHdoYXRldmVyIHRyYWZmaWMg
Y29udHJvbHMgdGhleSBsaWtlIChhcyBsb25nIGFzIHRoZSBFQ1QoMSkgaW1wbGVtZW50YXRpb24g
bGluZXMgdXAgd2l0aCB0aGUgTDRTIGRlZmluaXRpb24sIHdoaWNoIGlzIHRvdGFsbHkgZG9hYmxl
IGluIGZxX2NvZGVsIGFuZCBDQUtFKS4gICAgVGhlIGlzc3VlIHdlIGhhdmUgYmVlbiBkaXNjdXNz
aW5nIGlzIHdoZXJlIHRoZSB1c2VyIGlzIHJ1bm5pbmcgYW4gb2xkIHZlcnNpb24gb2YgZnFfY29k
ZWwvQ0FLRSB0aGF0IGhhc24ndCBiZWVuIHVwZGF0ZWQgdG8gdGhlIEw0UyB2ZXJzaW9uIG9mIEVD
VCgxKS4gIEluIHRoYXQgY2FzZSwgdGhlIEw0UyB0cmFmZmljIHdvdWxkIHNlZSB3b3JzZSBxdWV1
aW5nIGxhdGVuY3kgdGhhbiBjbGFzc2ljIFRDUC4NCg0KDQpbLi4uXQ0KICAgID4gW0dXXSBBbHRl
cm5hdGl2ZWx5LCBpZiBmcV9jb2RlbC9DQUtFIHdlcmUgdG8gdHJlYXQgRUNUKDEpIGFzIG5vbi1F
Q1QgKG9yIGltcGxlbWVudCB0aGUgTDRTIHN0eWxlIEVDTikgdGhpcyB3b3VsZCBhZ2FpbiBub3Qg
YmUgYW4gaXNzdWUsIEkgYmVsaWV2ZS4gIA0KICAgIA0KICAgIFtTTV0gSSBiZWxpZXZlIHRoaXMg
dG8gYmUganVzdCBhcyB2aWFibGUgYXMgaGF2aW5nIEw0UyBBUU1zIGludGVycHJldCBFQ1QoMSkg
YXMgcHVsc2UtbW9kdWxhdGVkIGNvbnRpbnVvdXMgY29uZ2VzdGlvbiBpbmZvcm1hdGlvbi4gWy4u
Ll0NCg0KW0dXXSBIb3c/ICBUaGF0IHNlZW1zIGltcG9zc2libGUgdG8gbWUuICBXaGF0IGlzIHRo
ZSBjbGFzc2lmaWVyIHRoYXQgZGlyZWN0cyB0cmFmZmljIHRvIHRoZSBMTCBxdWV1ZSB2cyBDbGFz
c2ljPyAgDQogICAgDQogDQoNCg==


From nobody Thu Apr  4 10:29:35 2019
Return-Path: <g.white@CableLabs.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 A2F701201CC for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 10:29:32 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cablelabs.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 uZBWV1mF5tCy for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 10:29:30 -0700 (PDT)
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (mail-eopbgr730095.outbound.protection.outlook.com [40.107.73.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 276F31204D7 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 10:29:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cablelabs.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x0PdqJMrNbGiFP/5m+zkuU4etXzblhbV0meDtD+3gaE=; b=Qlfo0/oW07+Oj1PQPkRnouAYxCWynE5yeLos6p35d5/G55fSwZ3zX1gX3pygSuXmmqV7AVouYyLut3ZybnnehwQC5DtsSz/rKZRGgYCPt+nmiTTgCXdPMIJvEiyU2EKBAxIlaVlWSj/TOUez3vc3keVSTEvISBsBB3eF/cmFE5g=
Received: from SN6PR06MB4655.namprd06.prod.outlook.com (52.135.117.85) by SN6PR06MB6383.namprd06.prod.outlook.com (20.177.254.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.13; Thu, 4 Apr 2019 17:29:14 +0000
Received: from SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c]) by SN6PR06MB4655.namprd06.prod.outlook.com ([fe80::75ce:14bc:e5e2:573c%6]) with mapi id 15.20.1750.021; Thu, 4 Apr 2019 17:29:14 +0000
From: Greg White <g.white@CableLabs.com>
To: Jonathan Morton <chromatix99@gmail.com>
CC: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Thread-Topic: [iccrg] [tsvwg]  IETF104 ICCRG TCP Prague presentation
Thread-Index: AQHU6ksFATQlV6AwuEyVhJCWJn+a66YrJhqA////44CAAKshgIAABXQAgABeGYD///D9gIAALlQA
Date: Thu, 4 Apr 2019 17:29:13 +0000
Message-ID: <8008B232-8E76-4E2B-8DEE-5C6A5391D0B1@cablelabs.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com> <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com> <817A985F-2974-4755-B294-8CEEBFCAC744@cablelabs.com> <019569E3-9D93-41B9-8D0A-D1E3501D9B3D@gmail.com>
In-Reply-To: <019569E3-9D93-41B9-8D0A-D1E3501D9B3D@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.14.0.181208
authentication-results: spf=none (sender IP is ) smtp.mailfrom=g.white@CableLabs.com; 
x-originating-ip: [176.12.107.132]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d86c31f3-875b-4734-16ba-08d6b9230ea5
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:SN6PR06MB6383; 
x-ms-traffictypediagnostic: SN6PR06MB6383:
x-microsoft-antispam-prvs: <SN6PR06MB6383E843399F12B44E513BD1EE500@SN6PR06MB6383.namprd06.prod.outlook.com>
x-forefront-prvs: 0997523C40
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400004)(136003)(346002)(396003)(376002)(366004)(189003)(199004)(6486002)(71200400001)(4326008)(5660300002)(71190400001)(8936002)(82746002)(1411001)(256004)(6436002)(99286004)(4744005)(305945005)(7736002)(97736004)(229853002)(6246003)(14454004)(478600001)(25786009)(33656002)(86362001)(66066001)(83716004)(93886005)(316002)(476003)(53936002)(2906002)(11346002)(81166006)(8676002)(6512007)(6916009)(58126008)(54906003)(68736007)(446003)(3846002)(6116002)(105586002)(53546011)(186003)(106356001)(102836004)(26005)(36756003)(6506007)(486006)(2616005)(76176011)(81156014)(85282002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR06MB6383; H:SN6PR06MB4655.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: CableLabs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: LMO/AhG2tH+EWbHwEzLVOiMO+ix37b+rSMH53O0YYDkKmV4+6+JR70iKIMpTFObThux6L8bYCibX1J5KG6C3D79HTHG3O/phgDHXHgvUCukoN93hpaiv/73IMhRBVOyRAzAQvuMcA88PPdzo7youw9Omt/PHX7ZTKcJsBags8GtuxUsxpDQzZ52oD2wnMtpFhmHOtcyhehCinNzapDdzENlnlJwzu1frcTxcSXGOxw8Itk9c22LoWryhqyxn+VeuZm+/RgTEE+2Yr3RxvPqkVqhp2s6Vg+6atTSNctoubaguDz74y718OrVPCk8Jz8mamsPdweXHLMDXEmWxvgp0yfFNLPqqgZxVG3ynsUrQ/BtEQJH2U6RZhxpcE8v79RA3VQ4eHTNyOXSQBbuTIL0sI/QdY+AeO+146aJtEJY9g8s=
Content-Type: text/plain; charset="utf-8"
Content-ID: <24E658553D52CF45B296E8DF9ED1532E@namprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: cablelabs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d86c31f3-875b-4734-16ba-08d6b9230ea5
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2019 17:29:13.9277 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: ce4fbcd1-1d81-4af0-ad0b-2998c441e160
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR06MB6383
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/GKmPnI7Zly7Y9LMuimxqOWzG9Y4>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 17:29:33 -0000

T24gNC80LzE5LCA0OjQzIFBNLCAiSm9uYXRoYW4gTW9ydG9uIiA8Y2hyb21hdGl4OTlAZ21haWwu
Y29tPiB3cm90ZToNCg0KICAgID4gT24gNCBBcHIsIDIwMTksIGF0IDY6MzcgcG0sIEdyZWcgV2hp
dGUgPGcud2hpdGVAQ2FibGVMYWJzLmNvbT4gd3JvdGU6DQogICAgPiANCiAgICA+IE15IGNvbmNl
cm4gaXMgdGhhdCB0aGUgU0NFIHNlbmRlciBnZXRzICp6ZXJvKiBiZW5lZml0IGZyb20gc3VwcG9y
dGluZyBTQ0Ugc2lnbmFsaW5nIHVubGVzcyB0aGUgYm90dGxlbmVjayBsaW5rIGlzIGFuIEZRIGxp
bmsuDQogICAgDQogICAgT3VyIGVhcmx5IHJlc3VsdHMgc3VnZ2VzdCBvdGhlcndpc2UuICBIb3dl
dmVyLCBJIHdvdWxkIGxpa2UgdG8gZmxlc2ggdGhlbSBvdXQgYmVmb3JlIGZ1cnRoZXIgZGV0YWls
ZWQgZGlzY3Vzc2lvbi4NCiAgICANCiBJIHdpbGwgYmUgaW50ZXJlc3RlZCB0byBzZWUgaG93IHRo
aXMgaXMgcG9zc2libGUuICBXaGVuIGFuIFNDRSBzZW5kZXIgYW5kIGEgbm9uLUVDVCBzZW5kZXIg
c2hhcmUgYSBzaW5nbGUgcXVldWUsIHRoZSBub24tRUNUIHNlbmRlciB3aWxsIGJlIGRyaXZpbmcg
dGhlIHF1ZXVlIGRlbGF5IHRvIHRoZSBjbGFzc2ljIEFRTSB0YXJnZXQsIGFuZCB0aGUgU0NFIHNl
bmRlciB3aWxsIGV4cGVyaWVuY2UgdGhlIHNhbWUgcXVldWUgZGVsYXkgYXMgdGhlIG5vbi1FQ1Qg
c2VuZGVyLiAgIEkndmUgbm90IGJlZW4gYWJsZSB0byBpbWFnaW5lIGEgZHVhbCBxdWV1ZSBpbXBs
ZW1lbnRhdGlvbiB0aGF0IGNhbiBpZGVudGlmeSBTQ0Ugc2VuZGVycyBzbyB0aGF0IHRoZXkgY2Fu
IGFjaGlldmUgcmVsaWFibGUgdWx0cmEtbG93IGRlbGF5ICh1bmxlc3MgeW91IGFyZSBzdWdnZXN0
aW5nIHRoYXQgU0NFIHNlbmRlcnMgYXJlIGFsbCByZXF1aXJlZCB0byBtYXJrIHRoZWlyIHRyYWZm
aWMgd2l0aCBhIHBhcnRpY3VsYXIgRFNDUCkuDQoNCg0KDQoNCg0KDQoNCg==


From nobody Thu Apr  4 10:49:06 2019
Return-Path: <moeller0@gmx.de>
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 BA760120119; Thu,  4 Apr 2019 10:49:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 WDb2cgWxIIdr; Thu,  4 Apr 2019 10:49:01 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 7D5D912011E; Thu,  4 Apr 2019 10:48:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1554400089; bh=4t+vMlpwUciD/a1buZQFYtv8t6bIqGkFB365cWxb9j0=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=hkOoET2205RCCufXZ3RD0aIGy4/5GHOZ8egSYX4iq4NGtSRfnSNJTlEF1Wme2JBHL uzJug1dZinG76/d+xSjSzfQuKgN4gbFFrGm+w3oKNDj1Sar/8w+VKRASR07Ex8YPl7 0M46HEKx3i6GMcw7CdXlfQmtGs+iDNqVTG6P0PSU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.42.222] ([77.189.99.139]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MYbFe-1hOjVa3xhq-00VTKh; Thu, 04 Apr 2019 19:48:09 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Sebastian Moeller <moeller0@gmx.de>
In-Reply-To: <AD99A4E5-B7F9-49CC-BFAC-E33DDD97BCCC@cablelabs.com>
Date: Thu, 4 Apr 2019 19:48:05 +0200
Cc: Jonathan Morton <chromatix99@gmail.com>, Bob Briscoe <in@bobbriscoe.net>,  "iccrg@irtf.org" <iccrg@irtf.org>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7D3B8AD-E2C3-446D-9838-746651E6592E@gmx.de>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <59D6B58C-C966-493C-B3B9-CAD3AD7AD5F9@gmx.de> <AD99A4E5-B7F9-49CC-BFAC-E33DDD97BCCC@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-Provags-ID: V03:K1:0i2kj44l+cZj6zzB20ja+sfYRukMgtZJ/p7tF+MxPcvCU//Eq4B js/lB2NBTHls2+iEfWkXCfE+gZjtfcByzhBfK+Zbbbhjp1liDFSmLrLTlUiyqBJ6NLuV+Um vqmZ6uMzQWM17baHu1vGIMukEXKOEAOafaOfwq4lGRwK3lZuJN0O8TkLuNrad0f4+XdSnCp h97pGBpB2wIFVgANCMxDw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Gf8pzzNaP4s=:NmBTIiwTEZItVM91/2BLaS BNXevr+hiwwCEJXASFtBYWbgftLjH7Qo+JeLn70/rLk9eWBNEA3AFHOOAwIIAyOqvUG2YfV9V 03BobGzHFZU5HkoHr5YGt4UwO5Ov3k0mhF5TpeVTwpZi6br/8IFicdB8S2hiqG1eKmDofBz7Y EiludxjmtjQ2DeWgxV9DHLZV1mGVs9FvE3VeLtTpOQSMFHRgew+0qzgLUZ4U1ziBxSg8HAgwj 7RJe4pTMCfNjk0elX4e2+NfNI3y7o1p7gqxHhzyrrV2BN6vt9vB6BF9bYrCpqgZqXlGa9IA6J 21QjdDey3CSyozOP1wij8T9Vfo2RgdhMvkpy5aZ4FjmaTG43NSDRaw+dAfqIbGXz45CPYnI1V LK3JL0ODaIZ5t062dis2whm92DogfvLk7ghceFflK6U2ioJAoQFAXourzUzWM/j6+7TghclWd zwyo5s4LevbQuVINmqkcFugU9X6mIB6Rnvaxb4nGIP5m7a3dyzIK45bhAy3/DQu47GQJAIbxy Ymmd/a53BLDcnsz+yXqOOanmYFeZ01NPsU5tgD+VGOJUynNpLxOUkQrmFxaFVcdJkotVjSJCe n6F1esKSnMmei0gPuP4bVhvj2MjBzNZAuoXeAISNRh7o60r17hmNIi2Y8T8rGeeV3CJz0DXz9 eGTl6JNFf4LJVLPeBRc3sxscAYcWWwkhKAC09Lgvsh7o284vb7L13stZByxpyXCui/BTpqC6B cqYMg+r3Z5/alMdPVKTDWGUSOxUrtb0YgQ2Lz40MlIE3PxSAclY46qHp7+jrn+n55jCWjd979 2eTuYtOgAQJhXjyPEP10h/+erQ1bqkJQYjvErb1VRb+DDqn9etNp+RJq5q3khEnGk7121gyy0 AM0JhugtfRD9e+wjFTpF+qeL5ZP63vis8YvBNvMfmkCWVNEw0cyySS5lh6pbUVJSyAM7+ik3r NWdNfyUWWWg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/8lBzccJ3y6s7pZlT7dyCK2VvLqk>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 17:49:04 -0000

Hi Greg,



> On Apr 4, 2019, at 19:06, Greg White <g.white@CableLabs.com> wrote:
>=20
> On 4/4/19, 11:29 AM, "Sebastian Moeller" <moeller0@gmx.de> wrote:
>=20
>    Hi Greg,
>=20
>    [SM]: I happen to believe that head-end AQM will ameliorate the =
need for an ingress AQM for a lot of casual users, but all those that =
are constantly running against capacity limits (think ADSL) typically =
desire a more fine-grained prioritization than a head-end AQM is going =
to offer, includsing restricting bandwidth to certain proiorety classes =
to say keep latency increas for game traffic tightly bound. I believe in =
that case the guarantees L4S offers are not sufficient, as the gaming =
case requires "guaranteed bandwidth at a certain latency level" as =
compared to the low_queueung latency guarantee L4S offers (which =
basically moves the que back into the sending end-host, which is fine, =
but all it does not help if I need to send @ X Hz).
>=20
> [GW]  In an L4S world,

	But we are not living in an L4S world, so it would behoove L4S =
to play nicely with the existing world, no?

> there is nothing that prevents a user running an "ingress AQM" of =
their choice with whatever traffic controls they like (as long as the =
ECT(1) implementation lines up with the L4S definition, which is totally =
doable in fq_codel and CAKE).   =20

	So "my way or the highway", eh?


> The issue we have been discussing is where the user is running an old =
version of fq_codel/CAKE that hasn't been updated to the L4S version of =
ECT(1).  In that case, the L4S traffic would see worse queuing latency =
than classic TCP.

	In the case of ingress Shaping this is simply not true and L4S =
flows have the potential to aggressively use more than their fair share =
in a way that fq post-bottleneck can only react to too slowly. This is a =
use case that exists in the real world right now, and I dislike the idea =
that this will only continue to be possible under the assumption that I =
need to upgrade my AQM.

>=20
>=20
> [...]
>> [GW] Alternatively, if fq_codel/CAKE were to treat ECT(1) as non-ECT =
(or implement the L4S style ECN) this would again not be an issue, I =
believe. =20
>=20
>    [SM] I believe this to be just as viable as having L4S AQMs =
interpret ECT(1) as pulse-modulated continuous congestion information. =
[...]
>=20
> [GW] How?  That seems impossible to me.  What is the classifier that =
directs traffic to the LL queue vs Classic? =20

Well, my point is, 1 single code-point does not make a robust =
classifier, as seen in the fact that the ECT(1) flow identity does not =
survive a CE-marking, Really the L4S RFCs are quite verbose in showing =
why ECT(1) can not serve as a reliable identifier of L4S-flows, only to =
then turn around and argue why this does not matter. I would propose to =
simply use a new protocol and you have a perfect identifier in the IP =
header that can unambiguously identify your flows, problem solved. And =
once you done that you do not need to overlay two different meanings on =
the CE mark anymore, just teach your AQM to set a field in the new =
protocol's header and you are set (for bonus you could use 8 bits and =
directly encode a graded load signal which would allow even more =
fidelity and temporal precision than essentially doing PCM, no). That =
wat CE can keep its meaning and L4S and the TCP-friendly world stay =
nicely separated. Now, you might bring tunneling as an example, to which =
I say let's cross that bridge once we get there.
That seems like a clean implementation for a new protocol, IMHO. Is that =
easy to roll out, hell no, but it is not unique in that regard.


Best Regards
	Sebastian=


From nobody Thu Apr  4 10:54:56 2019
Return-Path: <chromatix99@gmail.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 4436A1201DE for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 10:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 OIiBa_iUEiga for <tsvwg@ietfa.amsl.com>; Thu,  4 Apr 2019 10:54:52 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 ECA9E1201B3 for <tsvwg@ietf.org>; Thu,  4 Apr 2019 10:54:51 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id o19so2439138lfl.4 for <tsvwg@ietf.org>; Thu, 04 Apr 2019 10:54:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=o7WWoxRdhq4tsBiUgVDZeoOHxa0jKvTJfSfCX9EAxy4=; b=JNgXg13RT/TRCcCs24eWmhe/1hV/uXQhkZc2OKdZ5NAIcI6StJfTf6xiVxxCmJmsxT PvG93Qo84guwA/yi9LWip1XVGCBnRdg+qKP8HjXZP7yEFbbBp6Xh73pVy2ck/1AckTQQ pz01alb5FJX7bJ/tJCRL8joU7RV3L2I8lCpDy1PzUzOlE76GN8mfFP9URJ5MJUtFiRIL RRfHBVDxorsDzabljp3oLio/2VuDjfdvA53CP0snoucUcmvANg6UfLAehmjNVXapr9fV T9lwdkVzjOm7MSmXJ+B+hlBRGylJMeW9Cotofd7KmPtGm7NReqHD7bBxz39180TPcXcT 6x+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=o7WWoxRdhq4tsBiUgVDZeoOHxa0jKvTJfSfCX9EAxy4=; b=tbnsxe04ly/55DjYqZNC/50Kvu1T/aGsk20M2zsHS/Bsc+uGMqCZpV9r8M0OSUQBMQ iCg2uXJtvoODGab2p/9oEGVEPa7CNCDZ91J4KFXzgmmjdz1sdu1RTdY8fNQ3hbdkYsBr 2CCERGBom+sxrJcuXex7v5ivWSXG90nWfwwKRGgKwe98mO3DID82tH9BY0qlWjiE4F7S sBosm1X+b4a3dPVo4i9X4wF7Hhk/Q7sFsKiK0sLAGbMAoB+hRzwZI9ALrcMk/dBjstqI OhMhdeACI9mwHLvzXeYgq+eT9E+te9MgGSosapJ9A+8bvoP/ufofcKX312FVFstUhzQY uc2A==
X-Gm-Message-State: APjAAAXISazmfViERnIyGpMgloOdMovfnifG8skxRQw9ozNLe/xdx8xy wubbTnlRZsshzwfseu3Fb+Q=
X-Google-Smtp-Source: APXvYqxlsT1qiG6V4qNG+fkthXGPxKlasFCE5wVbfltE166LBPW7UCPyNvV3jmr8a8beZWdWEAKx6A==
X-Received: by 2002:ac2:44c3:: with SMTP id d3mr3912676lfm.14.1554400490266; Thu, 04 Apr 2019 10:54:50 -0700 (PDT)
Received: from jonathartonsmbp.lan (83-245-225-56-nat-p.elisa-mobile.fi. [83.245.225.56]) by smtp.gmail.com with ESMTPSA id n9sm4152158lfg.9.2019.04.04.10.54.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 04 Apr 2019 10:54:49 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <8008B232-8E76-4E2B-8DEE-5C6A5391D0B1@cablelabs.com>
Date: Thu, 4 Apr 2019 20:54:48 +0300
Cc: Bob Briscoe <in@bobbriscoe.net>, "iccrg@irtf.org" <iccrg@irtf.org>, Sebastian Moeller <moeller0@gmx.de>, tsvwg IETF list <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <31986531-2057-4DA1-878B-93E429B78F48@gmail.com>
References: <623CA1C6-3425-46E6-AFD9-6FD7D0DBE422@gmx.de> <a7bf3c8d-bb9e-e7e8-3343-ccdbac795591@bobbriscoe.net> <82B40A22-F2C2-4D56-868A-F53D7AEA37D7@gmail.com> <4507BFFD-A68A-4E8A-8FFB-347F95E3F2E8@cablelabs.com> <2491A216-4522-4942-BDEB-301D61CC5D03@gmail.com> <FD7FA874-3413-4F62-81CB-0F68B9038CC7@cablelabs.com> <B0F75E09-9264-4AC0-BF35-F084CC6213FC@gmail.com> <817A985F-2974-4755-B294-8CEEBFCAC744@cablelabs.com> <019569E3-9D93-41B9-8D0A-D1E3501D9B3D@gmail.com> <8008B232-8E76-4E2B-8DEE-5C6A5391D0B1@cablelabs.com>
To: Greg White <g.white@CableLabs.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/EG2p0DXAQsH4Nx-7WeR3IxB5v-w>
Subject: Re: [tsvwg] [iccrg]   IETF104 ICCRG TCP Prague presentation
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: Thu, 04 Apr 2019 17:54:54 -0000

> On 4 Apr, 2019, at 8:29 pm, Greg White <g.white@CableLabs.com> wrote:
>=20
> When an SCE sender and a non-ECT sender share a single queue, the =
non-ECT sender will be driving the queue delay to the classic AQM =
target, and the SCE sender will experience the same queue delay as the =
non-ECT sender.=20

This is true.  However, this is no worse a situation, in terms of peak =
delay, than a single-queue AQM is today.

The immediate benefit to SCE is the ability to use path capacity left =
unused by a conventional multiplicative-decrease response, without =
incurring a latency hit relative to conventional TCP, and without losing =
TCP-friendly characteristics.  This is easily seen when a single SCE =
flow occupies the link (we measured roughly 50% greater goodput versus =
plain NewReno over 30 seconds), and is not materially degraded when a =
second SCE flow joins it.

What we have not yet had the opportunity to test is the behaviour of an =
SCE flow versus a non-SCE flow sharing a single queue.  The interactions =
here are expected to be subtle, involving a mixture of SCE and CE =
responses.  An important property, however, is that we are sure that =
conventional TCPs will not be squeezed out of the path by SCE flows - =
rather, we are working to avoid the opposite scenario.

Just as soon as GitHub stops breaking on us=E2=80=A6

> I've not been able to imagine a dual queue implementation that can =
identify SCE senders so that they can achieve reliable ultra-low delay =
(unless you are suggesting that SCE senders are all required to mark =
their traffic with a particular DSCP).

SCE senders are not required to use any particular DSCP.  Nor are they =
enjoined from doing so.

Understand this: SCE's primary purpose is not to ensure minimal queue =
delays in all possible circumstances.  It is to improve the quality of =
congestion control in a thoroughly backwards-compatible manner.  Relying =
too heavily on Diffserv, which is rarely implemented at bottlenecks =
today, would defeat that goal.

The combination of SCE with a DSCP associated with an appropriate PHB =
could work with your preferred DualQ architecture, as an *enhancement* =
to standard SCE or ECN behaviour.  The only additional requirement is =
that the DSCP survives the path as far as the bottleneck.  I suggest =
that the cable industry is in a better position than most Internet =
entities to solve the latter problem.

 - Jonathan Morton


From nobody Fri Apr  5 01:14:08 2019
Return-Path: <Ruediger.Geib@telekom.de>
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 BE8BA12038D for <tsvwg@ietfa.amsl.com>; Fri,  5 Apr 2019 01:14:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de
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 OCsMUkd9qs0u for <tsvwg@ietfa.amsl.com>; Fri,  5 Apr 2019 01:14:03 -0700 (PDT)
Received: from mailout11.telekom.de (mailout11.telekom.de [194.25.225.207]) (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 5AB0C120350 for <tsvwg@ietf.org>; Fri,  5 Apr 2019 01:14:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1554452042; x=1585988042; h=from:to:cc:subject:date:message-id:mime-version; bh=ZiiLkwFdEpxWt2lZhiF2b8jkXNcuHJA1IHnU9jUhJ9Y=; b=jQ211Kbuv0ekWH7DZcJj3EUnsw7vUhqbpdBvJ7JBN6NVUnjFFjCm8aq1 ckeNIg7WzuxpHB7vYrzbwTb7lbSbkUSby2YDzXPbyMnn0w9/AsSyfC4Ls PElC5fkOvjHbiuNo0lqjmGtKd+yCgXt/QLqjwVygLyc/qd/HJ1RBYpy1u sUnUqenBVp6VxZLQhjb12bmV4MgEfZgI3IbrjHZ+xVnEY+n7xODrLcdO6 o7UXjFn34u15i9GjjYoTdd/i92bcI77cB/JgYnYbqqQLvBA+UZ0FvtJwI taOALbLarI2KI56mgBTHuOCmbw3eh3YOsesEQVxYvTWhUNyamDPwaS9nD A==;
Received: from qdezc2.de.t-internal.com ([10.171.255.37]) by MAILOUT11.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Apr 2019 10:13:57 +0200
Received: from he105665.emea1.cds.t-internal.com ([10.169.118.62]) by qde0ps.de.t-internal.com with ESMTP/TLS/AES256-SHA; 05 Apr 2019 10:11:12 +0200
Received: from HE105870.EMEA1.cds.t-internal.com (10.169.118.67) by HE105665.emea1.cds.t-internal.com (10.169.118.62) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 5 Apr 2019 10:11:10 +0200
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105870.EMEA1.cds.t-internal.com (10.169.118.67) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 5 Apr 2019 10:11:10 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.19) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 5 Apr 2019 10:11:10 +0200
Received: from LEJPR01MB0460.DEUPRD01.PROD.OUTLOOK.DE (10.158.142.153) by LEJPR01MB0459.DEUPRD01.PROD.OUTLOOK.DE (10.158.142.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.22; Fri, 5 Apr 2019 08:11:10 +0000
Received: from LEJPR01MB0460.DEUPRD01.PROD.OUTLOOK.DE ([fe80::24cc:c867:203f:204d]) by LEJPR01MB0460.DEUPRD01.PROD.OUTLOOK.DE ([fe80::24cc:c867:203f:204d%3]) with mapi id 15.20.1750.023; Fri, 5 Apr 2019 08:11:10 +0000
From: <Ruediger.Geib@telekom.de>
To: <thomas.fossati@nokia.com>
CC: <tsvwg@ietf.org>
Thread-Topic: Comments on draft-fossati-tsvwg-lola-00
Thread-Index: AdTrff86X1B9cahtQWuU/QwB2S17KA==
Date: Fri, 5 Apr 2019 08:11:10 +0000
Message-ID: <LEJPR01MB04606975D1C9384F1B334F269C510@LEJPR01MB0460.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Ruediger.Geib@telekom.de; 
x-originating-ip: [164.19.4.90]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bc712cf0-7534-4257-418c-08d6b99e4329
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:LEJPR01MB0459; 
x-ms-traffictypediagnostic: LEJPR01MB0459:
x-microsoft-antispam-prvs: <LEJPR01MB0459706464A81801A864F9BD9C510@LEJPR01MB0459.DEUPRD01.PROD.OUTLOOK.DE>
x-forefront-prvs: 0998671D02
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(376002)(346002)(396003)(39860400002)(366004)(189003)(199004)(486006)(14454004)(26005)(9686003)(86362001)(6306002)(476003)(7696005)(105586002)(52396003)(316002)(2501003)(81156014)(75402003)(55016002)(106356001)(4326008)(74482002)(8936002)(5640700003)(7736002)(186003)(81166006)(8676002)(5660300002)(102836004)(33656002)(68736007)(14444005)(97736004)(2906002)(296002)(53936002)(66066001)(71200400001)(2351001)(478600001)(71190400001)(54896002)(19627235002)(3846002)(6116002)(790700001)(72206003)(6916009)(256004); DIR:OUT; SFP:1101; SCL:1; SRVR:LEJPR01MB0459; H:LEJPR01MB0460.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: twi+fgyTTvoK/hWU42baCw1g+hHT+71oUP4k5olzNuMny4RvEVp4TB13jYIgDuKe7fFdLSc43Mk5cluLgXZhv7TO/9SpU2xw9NBfAF0LRXIf1O7MtSPb0xHNZfuXio8j/Z6jrsIaU4Iz6HLl3IAwrtffJrI6JlZklAWnz9knt/G8MUPQ+dCwaGVHXfZfrsNgBOG/DBrAZczTPVLJ9SQmcGHyJHGOQh7q9UBl/9zX0jprNz4Vk6/Fb2b2aoHqdSfAgEu1v/jPDimAoROex8YXnCVcCKwpYCWGSWCmzvrLNZ72TTY8SnfVJNwCWsJF+p3LQNOf4km+KMclJYqKJ3DL3A3thvZurqH3dBLIZ02nFvzpRnB7nEiZ88GWxKpjFxaXMg/5/xueCcN8YGFxYX58ntyLyP4B4Z7E63qxiTwzCok=
Content-Type: multipart/alternative; boundary="_000_LEJPR01MB04606975D1C9384F1B334F269C510LEJPR01MB0460DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bc712cf0-7534-4257-418c-08d6b99e4329
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Apr 2019 08:11:10.1912 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEJPR01MB0459
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/bjXzJhFuFyGB-EtyaHmDY1ok3vI>
Subject: [tsvwg] Comments on draft-fossati-tsvwg-lola-00
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: Fri, 05 Apr 2019 08:14:06 -0000

--_000_LEJPR01MB04606975D1C9384F1B334F269C510LEJPR01MB0460DEUP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

I've just read the draft and have a couple of comments.

I agree that it is likely important to think about alignment of IP transpor=
t protocols with 5G RTT requirements. If there's a
business case justifying the latter, which I can't judge (and don't want to=
 discuss here). If these RTT requirements need to
be honored, then a reliable low latency transport using ECN as a congestion=
 feedback may be more useful, than state
of the art TCP mechanisms.

I note that the draft-fossati-tsvwg-lola is suggested for standards track. =
It needs to see some improvement, I think:

There's a lack of 3GPP references. The draft refers to 3GPP standards and t=
erminology, but doesn't yet provide a reference.

The draft states:

   The Mobile network is configured to give UEs a dedicated, low-
   latency, non-GBR, EPS bearer with QCI 7 in addition to the default
   EPS bearer.

   A packet carrying the NQB DSCP shall be routed through the dedicated
   low-latency EPS bearer.  A packet that has no associated NQB marking
   shall be routed through the default EPS bearer.

I've been investigating DiffServ interworking with 3GPP LTE QoS some five t=
o six years ago. I stopped all activities due to the following facts at tha=
t time:


  1.  It was virtually impossible to liaise with 3GPP
  2.  The 3GPP 4G standards came with a set of 9 standard QCIs. Support of
any single of them is optional, if I recall correctly, and there was
no interconnection standard related to the standard QCIs.
  3.  There exists a set of private QCIs, and these are many more than the
standard QCIs. I learned that these were largely deployed by the time
I've been working on that subject.
  4.  By that time, DSCPs were ignored by the RAN policy decision points.

I'd like to have a reference to a 3GPP standard confirming support of the a=
bove draft-fossati-tsvwg-lola statements (and I frankly don't see a point i=
n
any IETF standard defining 3GPP QCI interworkings without a corresponding 3=
GPP standard explicitly confirming the IETF sight). If this isn't possible
for the time being, is there a draft-fossati-tsvwg-lola related standardiza=
tion activity seeing support within 3GPP?

Please note, there's an IR34 by GSMA. It suggests DSCP to QCI mappings in T=
able 3. Draft-fossati-tsvwg-lola should explain
(and suggest changes?) to the recommendations given there, I think.

Regards,

Ruediger

--_000_LEJPR01MB04606975D1C9384F1B334F269C510LEJPR01MB0460DEUP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Vorformatiert Zchn";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.E-MailFormatvorlage17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLVorformatiertZchn
	{mso-style-name:"HTML Vorformatiert Zchn";
	mso-style-priority:99;
	mso-style-link:"HTML Vorformatiert";
	font-family:"Courier New";
	mso-fareast-language:DE;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:268894741;
	mso-list-type:hybrid;
	mso-list-template-ids:673464422 1556669892 67567619 67567621 67567617 6756=
7619 67567621 67567617 67567619 67567621;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1774284293;
	mso-list-type:hybrid;
	mso-list-template-ids:349858154 67567639 67567641 67567643 67567631 675676=
41 67567643 67567631 67567641 67567643;}
@list l1:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"DE" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi Thomas,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;ve just read the draft =
and have a couple of comments.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I agree that it is likely impor=
tant to think about alignment of IP transport protocols with 5G RTT require=
ments. If there&#8217;s a
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">business case justifying the la=
tter, which I can&#8217;t judge (and don&#8217;t want to discuss here). If =
these RTT requirements need to
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">be honored, then a reliable low=
 latency transport using ECN as a congestion feedback may be more useful, t=
han state
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">of the art TCP mechanisms.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I note that the draft-fossati-t=
svwg-lola is suggested for standards track. It needs to see some improvemen=
t, I think:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There&#8217;s a lack of 3GPP re=
ferences. The draft refers to 3GPP standards and terminology, but doesn&#82=
17;t yet provide a reference.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The draft states:<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE">&nbsp;&nbsp; The Mo=
bile network is configured to give UEs a dedicated, low-<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE">&nbsp;&nbsp; latenc=
y, non-GBR, EPS bearer with QCI 7 in addition to the default<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE">&nbsp;&nbsp; EPS be=
arer.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE">&nbsp;&nbsp; A pack=
et carrying the NQB DSCP shall be routed through the dedicated<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE">&nbsp;&nbsp; low-la=
tency EPS bearer.&nbsp; A packet that has no associated NQB marking<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Courier New&quot;;mso-fareast-language:DE">&nbsp;&nbsp; shall =
be routed through the default EPS bearer.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;ve been investigating D=
iffServ interworking with 3GPP LTE QoS some five to six years ago. I stoppe=
d all activities due to the following facts at that time:<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<ol style=3D"margin-top:0cm" start=3D"1" type=3D"a">
<li class=3D"MsoListParagraph" style=3D"margin-left:0cm;mso-list:l1 level1 =
lfo2"><span lang=3D"EN-US">It was virtually impossible to liaise with 3GPP<=
o:p></o:p></span></li><li class=3D"MsoListParagraph" style=3D"margin-left:0=
cm;mso-list:l1 level1 lfo2"><span lang=3D"EN-US">The 3GPP 4G standards came=
 with a set of 9 standard QCIs. Support of
<br>
any single of them is optional, if I recall correctly, and there was <br>
no interconnection standard related to the standard QCIs. <o:p></o:p></span=
></li><li class=3D"MsoListParagraph" style=3D"margin-left:0cm;mso-list:l1 l=
evel1 lfo2"><span lang=3D"EN-US">There exists a set of private QCIs, and th=
ese are many more than the
<br>
standard QCIs. I learned that these were largely deployed by the time <br>
I&#8217;ve been working on that subject.<o:p></o:p></span></li><li class=3D=
"MsoListParagraph" style=3D"margin-left:0cm;mso-list:l1 level1 lfo2"><span =
lang=3D"EN-US">By that time, DSCPs were ignored by the RAN policy decision =
points.<o:p></o:p></span></li></ol>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;d like to have a refere=
nce to a 3GPP standard confirming support of the above draft-fossati-tsvwg-=
lola statements (and I frankly don&#8217;t see a point in
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">any IETF standard defining 3GPP=
 QCI interworkings without a corresponding 3GPP standard explicitly confirm=
ing the IETF sight). If this isn&#8217;t possible<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">for the time being, is there a =
draft-fossati-tsvwg-lola related standardization activity seeing support wi=
thin 3GPP?
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please note, there&#8217;s an I=
R34 by GSMA. It suggests DSCP to QCI mappings in Table 3. Draft-fossati-tsv=
wg-lola should explain
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">(and suggest changes?) to the r=
ecommendations given there, I think.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Ruediger<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_LEJPR01MB04606975D1C9384F1B334F269C510LEJPR01MB0460DEUP_--


From nobody Sat Apr  6 16:14:31 2019
Return-Path: <dave.taht@gmail.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 0442012017C for <tsvwg@ietfa.amsl.com>; Sat,  6 Apr 2019 16:14:29 -0700 (PDT)
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 OKFcpYswDKhB for <tsvwg@ietfa.amsl.com>; Sat,  6 Apr 2019 16:14:27 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 22976120096 for <tsvwg@ietf.org>; Sat,  6 Apr 2019 16:14:27 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id z16so11513467qtn.4 for <tsvwg@ietf.org>; Sat, 06 Apr 2019 16:14:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=cDETWL01udU73+OyTXSdbwDcTBH6dAJMyedIAZoNpNk=; b=R/kIkCBPwzn7kR1K+CINZw9FU/FE7yCQAACvfHLLShWe6v5E4bZrexceJNYB0jC4c0 jfKdRRuOrzHt2hRdEWlA6obkkGAw0LAy0GCFHVQNr12V5QeWuSZiOmGJrA4XNCoTZ40X KKpwPmsRNrP7oUKMG57WapYX0pmhxgSGJD9VLwYWyDodyBCfsJM/lMsIaUgse7exIvMF C+5SAaPs2yk5rbfGOjnbiU8xni+Bj18xRXxfxO1E31PqMvSWXE1GMRd7avQx4j+iL4yo cJoVfUPcXPXms4xH3bEmImozFyOmhvud2qzBrVzJhpWWL6nIrYPl0hXQZx9G47i+U0ra HsNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=cDETWL01udU73+OyTXSdbwDcTBH6dAJMyedIAZoNpNk=; b=tdkSGm8YODxTYMm7y+1TIB6KcghapMS5FCyIch2OZcTAKqi9XJ7bg9PImhCAdaKXSI rh7+0YvDyhBRJWo/Ida2G/zUjUuAvBeDhpopTWIDaNCXUqMRLF0Ztmwu1PtZy0rIXaoi oGTxUxRbaPibGkgnP3eN5OOgCqDRKnOp0iUpsYVztI4da+H/yLU6EQuFykfsQqi2qUNB BojzMPq+Kzp8cIqYzH7lCMsEqn0NJmO2ZPNDGRY46Fuurom4z13pngbdr+kfp3u/uAz8 AZkRadZ8gqHLYUK8zHyuEem/KECQNcPxlyRllxhMmCMSS+FBsPG66XsEl92UuT8RP58s c/xQ==
X-Gm-Message-State: APjAAAVVp6HC4wOkohGTstfkM60kGTId4sEV5AlcqWImuMEUqhngRNHr i/i5RS4XXkNCGrsdC83+2rQL+kCDVg5NAq6Id5w=
X-Google-Smtp-Source: APXvYqxZBdsRpfxTdC/+8f820Vd/knzbvISPKZXCvqjAqyDZg3mNwu7ooj/5T1wI/4FZwTfBzXcJrBXo+NRpUsWlg3U=
X-Received: by 2002:ac8:1b63:: with SMTP id p32mr18313867qtk.173.1554592466105;  Sat, 06 Apr 2019 16:14:26 -0700 (PDT)
MIME-Version: 1.0
From: Dave Taht <dave.taht@gmail.com>
Date: Sun, 7 Apr 2019 01:14:14 +0200
Message-ID: <CAA93jw67_9AwbYZSSf6F+JzqMd7zP0EfvpKxfd=Nzs5h0As_eA@mail.gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>, tsvwg IETF list <tsvwg@ietf.org>, iccrg IRTF list <iccrg@irtf.org>, bloat <bloat@lists.bufferbloat.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/G20rjWuteJBXTGaPsMouGCUubww>
Subject: [tsvwg] =?utf-8?q?TCP=E2=80=99s_Initial_Window_=E2=80=93_Deploym?= =?utf-8?q?ent_in_the_Wild_and_its_Impact_on_Performance?=
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, 06 Apr 2019 23:14:29 -0000

Lots of good takeaways in this 2019 paper about IW sizing, pacing, etc.

https://sci-hub.tw/10.1109/TNSM.2019.2896335

--=20

Dave T=C3=A4ht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740


From nobody Mon Apr  8 00:07:57 2019
Return-Path: <internet-drafts@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D59B8120157; Mon,  8 Apr 2019 00:07:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.94.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: tsvwg@ietf.org
Message-ID: <155470726879.6371.6156184416874197957@ietfa.amsl.com>
Date: Mon, 08 Apr 2019 00:07:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/dEgUt1s89_FiGOrHv8ZyMCuIMnM>
Subject: [tsvwg] I-D Action: draft-ietf-tsvwg-tinymt32-01.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Apr 2019 07:07:49 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group WG of the IETF.

        Title           : TinyMT32 Pseudo Random Number Generator (PRNG)
        Authors         : Mutsuo Saito
                          Makoto Matsumoto
                          Vincent Roca
                          Emmanuel Baccelli
	Filename        : draft-ietf-tsvwg-tinymt32-01.txt
	Pages           : 10
	Date            : 2019-04-08

Abstract:
   This document describes the TinyMT32 Pseudo Random Number Generator
   (PRNG) that produces 32-bit pseudo-random unsigned integers and aims
   at having a simple-to-use and deterministic solution.  This PRNG is a
   small-sized variant of Mersenne Twister (MT) PRNG, also designed by
   M.  Saito and M.  Matsumoto.  The main advantage of TinyMT32 over MT
   is the use of a small internal state, compatible with most target
   platforms including embedded devices, while keeping a reasonably good
   randomness.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-tsvwg-tinymt32-01
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-tinymt32-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-tinymt32-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Apr 15 10:07:49 2019
Return-Path: <jerhenry@cisco.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 924D91203B0 for <tsvwg@ietfa.amsl.com>; Mon, 15 Apr 2019 10:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=l/QF3GO3; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=GTxSRiRt
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 1-KosTIE-_So for <tsvwg@ietfa.amsl.com>; Mon, 15 Apr 2019 10:07:46 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C9712041F for <tsvwg@ietf.org>; Mon, 15 Apr 2019 10:07:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=830; q=dns/txt; s=iport; t=1555348066; x=1556557666; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=/yKjVWAVSRQPEWLpaIQHNXDO7TWIFOkJAKAWb2Bsclk=; b=l/QF3GO3Sizq1id1OccZ/p7rmI7QlpDypXKSZvm2i4kTrlz1U+yluVDy UkueYZF04o1AWk7GPLT3sZUaugWuLv7q4g7oEzITnjCPd9wxgI1zGo4P9 e0jxje7eLYt3BHMT8EfPi8bX3QoEhCb444P7DjLjzTLjxd+n9kviDMnHO I=;
IronPort-PHdr: =?us-ascii?q?9a23=3AqzVSaBa6f61DyPlBQDqaH+3/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn?= =?us-ascii?q?1NksAKh0olCc+BB1f8KavoYjY6EcJYRXdu/mqwNg5eH8OtL1A=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BrAACyubRc/51dJa1mHQEBBQEHBQG?= =?us-ascii?q?BUQgBCwGBPVADaFUgBAsohA6DRwOEUopFSoFolz+BLhSBEANUDgEBIwqEQBm?= =?us-ascii?q?FbSM0CQ4BAwEBCgECAQJtHAyFSwYjEQwBASUTEQEIGgImAgQwFRIEgzUBgWk?= =?us-ascii?q?DHAECDJxrAooUcYEvgnkBAQWBRkFAgjYYgg0DBoELJwGLSReBQD+BEScME4J?= =?us-ascii?q?MPoJhAgMBgSU4gwoxgiaNKYwbjHEJAoIFhgmGHIVyGoF4EJJrjQOFD41vAgQ?= =?us-ascii?q?CBAUCDgEBBYFPOIFWcBVlAYJBggqDb4UUhT9ygSmPSQEB?=
X-IronPort-AV: E=Sophos;i="5.60,354,1549929600"; d="scan'208";a="258556008"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 15 Apr 2019 17:07:45 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x3FH7jA4016243 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <tsvwg@ietf.org>; Mon, 15 Apr 2019 17:07:45 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 15 Apr 2019 12:07:44 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 15 Apr 2019 12:07:44 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 15 Apr 2019 13:07:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/yKjVWAVSRQPEWLpaIQHNXDO7TWIFOkJAKAWb2Bsclk=; b=GTxSRiRteVGdPk0BFKsXJO+NTvTbufLcwSGaZYbyPESVzTehbENOgboWxIxQGZrRjM431hSGAMxhYcNhEg1IULvnQdsgIuafIa2/oT9FtYvJs1hPEPOOBV3gK9g5Z9PJifO4AsV3HwGovo1nMh/1ognwMYFVwqsalU1MbVRVAts=
Received: from BN8PR11MB3745.namprd11.prod.outlook.com (20.178.221.22) by BN8PR11MB3731.namprd11.prod.outlook.com (20.178.220.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1792.19; Mon, 15 Apr 2019 17:07:42 +0000
Received: from BN8PR11MB3745.namprd11.prod.outlook.com ([fe80::94b9:6e48:63ff:e3c6]) by BN8PR11MB3745.namprd11.prod.outlook.com ([fe80::94b9:6e48:63ff:e3c6%4]) with mapi id 15.20.1792.018; Mon, 15 Apr 2019 17:07:42 +0000
From: "Jerome Henry (jerhenry)" <jerhenry@cisco.com>
To: Tsvwg IETF List <tsvwg@ietf.org>
Thread-Topic: [tsvwg] updated version of QCI to Diffserv draft
Thread-Index: AQHU8628NK4b0jncFUO1yh6liwgWsA==
Date: Mon, 15 Apr 2019 17:07:42 +0000
Message-ID: <1B26509A-4838-4C6D-931E-1E6756A6F42C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jerhenry@cisco.com; 
x-originating-ip: [2001:420:302:1252:3d69:bb4c:f879:ea79]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2b25314d-9817-4bbd-cee0-08d6c1c4df4a
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600140)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:BN8PR11MB3731; 
x-ms-traffictypediagnostic: BN8PR11MB3731:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BN8PR11MB3731D73D5D640C98DCF5ADE9D52B0@BN8PR11MB3731.namprd11.prod.outlook.com>
x-forefront-prvs: 000800954F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(376002)(366004)(136003)(396003)(346002)(189003)(199004)(2616005)(33656002)(97736004)(36756003)(476003)(14444005)(7736002)(486006)(25786009)(105586002)(256004)(305945005)(71190400001)(71200400001)(82746002)(8676002)(86362001)(81156014)(8936002)(81166006)(4744005)(106356001)(6116002)(186003)(2906002)(102836004)(6436002)(14454004)(478600001)(413944005)(5660300002)(6306002)(966005)(99286004)(6916009)(6486002)(68736007)(6506007)(83716004)(53936002)(6246003)(15650500001)(46003)(229853002)(316002)(6512007)(564094006); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR11MB3731; H:BN8PR11MB3745.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: mwtAklDnkVZe/UadxmvXxUaW2zysLQwutyoTNE24IZ/lZkqO1vuKTpgB2RNpAuJ5BkMQSZ+9V+RwAgBXkAchSCv1HefOfGThvXdb8plOfOuqjKWyz9GZbTOmVO2GB+FNWNHqiug5w0cFSljszu2VCvCyh14aH1V+jCz+WKCWaFm0rxQdDQd5uPUSxFYdGl0+4hOBGk2V/tccYMEzBG/4OTMRiYFlkkNU8jYIoFYNh2/0bsTC+9a4cSS5eDnd4nc/n0oXd8oM65T8Bz0TglkyVHQ9n12Uj6o13bKPAqTTMkel4jRh5wVJpEQx5PF27Ey9/JHCJNBqurFAsAqN2IQuY+p4XbcsDrdyDHkg26e2080xR/dfPP1YDEGZysoXGPvAazxOLs7wuh2mpx7i3QCeKP4pmi9PPkkjtm4c5wGiIig=
Content-Type: text/plain; charset="utf-8"
Content-ID: <0591CFE2A37FF544B3808F3E092E3708@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2b25314d-9817-4bbd-cee0-08d6c1c4df4a
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Apr 2019 17:07:42.0834 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR11MB3731
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Q-nr60cGfrlkqeyz7p7UMYEH0_c>
Subject: Re: [tsvwg] updated version of QCI to Diffserv draft
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: Mon, 15 Apr 2019 17:07:49 -0000

RGVhciBhbGwsDQoNCldlIHN1Ym1pdHRlZCBhbiB1cGRhdGUgdG8gdGhlIERpZmZzZXJ2IHRvIFFD
SSBtYXBwaW5nIGRvY3VtZW50LiBBcyBwYXJ0IG9mIHRoZSA1RyBmaW5hbGl6YXRpb24sIHRoZW4g
M0dQUCBhZGRlZCBhIGZldyAgUUNJcywgYW5kIHdlIHVwZGF0ZWQgdGhlIGRyYWZ0IGFjY29yZGlu
Z2x5Lg0KDQpXZSBhcmUgbG9va2luZyBmb3J3YXJkIHRvIGlucHV0IGFuZCBmZWVkYmFjaywgdGhy
b3VnaCB0aGUgbWFpbGVyIGFuZCBpbiBNb250cmVhbC4gT3VyIGFtYml0aW9uIGlzIHRvIChldmVu
dHVhbGx5KSBnZXQgdGhpcyBkcmFmdCB0byBhIGNvbnNlbnN1cyBzdGF0ZSB3aGVyZSB3ZSBjYW4g
c2hhcmUgaXQgd2l0aCBHU01BLCB3aG8gZG9jdW1lbnRzIGhvdyBRQ0kgbWFya2luZ3MgY2FuIGJl
IHRyYW5zbGF0ZWQgdG8gb3RoZXIgdmFsdWVzIHdoZW4gZXhjaGFuZ2VkIHRocm91Z2ggb3RoZXIg
ZG9tYWlucyAoZS5nLiBEaWZmc2VydikgYmV0d2VlbiBjYXJyaWVycy4NCg0KVGhhbmtzIQ0KDQpK
ZXJvbWUNCg0KDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1oZW5yeS10
c3Z3Zy1kaWZmc2Vydi10by1xY2kvDQoNCg0KDQogDQoNCg==


From nobody Mon Apr 15 13:36:32 2019
Return-Path: <brian.e.carpenter@gmail.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 0032D12039E; Mon, 15 Apr 2019 13:36:30 -0700 (PDT)
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 k1UiNwzL2uyI; Mon, 15 Apr 2019 13:36:29 -0700 (PDT)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 8AA79120112; Mon, 15 Apr 2019 13:36:26 -0700 (PDT)
Received: by mail-pf1-x42a.google.com with SMTP id t21so9198729pfh.2; Mon, 15 Apr 2019 13:36:26 -0700 (PDT)
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=oJX1bVdi7O2ymbQs2tav0NF8/SQkADck7HBKc0HdFrU=; b=O+923OexNxifw79owi7T8bWTzKYtnzRq01dHokWHr7xme/3aI0hEifownClHluC7dG 6CU1PAMyXWDMbZsPLkgiHoB+JFbwXMs9pZaMWIETjRsXszVzBIHkFYPBvV93rh//Q59e Mb/8wGAz8CJU9+wiiQcjSqpw8L4op4mw4PdFW+0CAHejVMgnGiYzA79iNWKd94/7sIhk FpwmjhNfPd2RcZME10KDCrDsd3gNW9vdr6QEGwKEqv4JJoqCtNf+3vupOiwYg9wlmClM N22aiNtu69l/Oic1vUPXT0hyMEDnssMY4tVV1xo9J3CCfzqp/WpnyhTTigk9KzAVhbQ6 DYMw==
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=oJX1bVdi7O2ymbQs2tav0NF8/SQkADck7HBKc0HdFrU=; b=mRY33IaF92BoTyD/6RB/hAFjWPwRPvnPmdBkHpeFZRvOjjPc002qWtZNjmRWgNCKeR OOXY9IHcCkTxJV0yny7xWHVJwOlw25JAXYNAyqPOBxilxt2WQKRCfRIyfE18ufkZ27+V nUG9oA66jndW8md2rGj9iHW6ZydoM/XX/+NdqNRejd1ArNTbZVj6oP1Lyef0vO2xVnqh 3Qq1kWeM/lgZ/lZIa6O0dS9Jzp+m6AudCkbS5FpA2AcGen4/T0JLDMCrnxhNSaesJjIa OW9jBAYp8s5QVI4/QIOAPcY3oqmf49ljCdR1PhoV2T3+oo+1yYrROn9IU8DuCvcX3P8r f/7g==
X-Gm-Message-State: APjAAAW3299B8Dvq251uv7bue3sIEUFkFlW0SF2xnj+9TKExRc3bogPy 9Bi99lL6PTIAnEiooczltsLq9hEf
X-Google-Smtp-Source: APXvYqwo44gV/6dGDWXLx2NfDntvRh8FV9jQNIQ7iqmcpp+q5/AbYTJTT/V2okC6D/OJ3g69fETwvA==
X-Received: by 2002:a63:4a5a:: with SMTP id j26mr72312379pgl.361.1555360585688;  Mon, 15 Apr 2019 13:36:25 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id w3sm98108875pfn.179.2019.04.15.13.36.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Apr 2019 13:36:25 -0700 (PDT)
To: "Jerome Henry (jerhenry)" <jerhenry@cisco.com>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "draft-henry-tsvwg-diffserv-to-qci@ietf.org" <draft-henry-tsvwg-diffserv-to-qci@ietf.org>
References: <153971927528.9352.418104757398396031@ietfa.amsl.com> <184d1317-b08c-9f0b-dc08-44d92f3fa2bd@gmail.com> <34D4E941-B88A-4B39-86B5-CE9EA8BB14CB@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <569bc04f-8122-8917-8666-97b96f453d96@gmail.com>
Date: Tue, 16 Apr 2019 08:36:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <34D4E941-B88A-4B39-86B5-CE9EA8BB14CB@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/-o2VB40-fuQXaAEcKxOXfN1JN88>
Subject: Re: [tsvwg] I-D Action: draft-henry-tsvwg-diffserv-to-qci-00.txt
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: Mon, 15 Apr 2019 20:36:31 -0000

Hi,

I note that the change noted below hasn't happened in
https://tools.ietf.org/html/draft-henry-tsvwg-diffserv-to-qci-01#section-=
4.2.10

Since draft-ietf-tsvwg-le-phb has been fully approved and is in
the RFC Editor queue, and the LE code point has been fixed (00001),
IMHO the recommendation for LE should be updated, and a warning
inserted that CS1 is ambiguous.

Regards
   Brian Carpenter

On 30-Oct-18 05:09, Jerome Henry (jerhenry) wrote:
> Thank you Brian,
>=20
> We'll make that correction in the next iteration of the draft, great to=
 hear the news!
>=20
> Best,
>=20
> Jerome=20
>=20
> =EF=BB=BFOn 10/28/18, 9:19 PM, "Brian E Carpenter" <brian.e.carpenter@g=
mail.com> wrote:
>=20
>     Hi,
>    =20
>     In https://tools.ietf.org/html/draft-henry-tsvwg-diffserv-to-qci-00=
#section-4.2.10
>     we find:
>    =20
>     >    ...recommend Low-Priority Data be marked CS1 DSCP.
>     >=20
>     >    Note: This marking recommendation may change in the future, as=
 [LE-
>     >    PHB] defines a Lower Effort (LE) PHB for Low-Priority Data tra=
ffic
>     >    and recommends an additional DSCP for this traffic.
>    =20
>     It seems to me that [LE-PHB] has advanced to the point where this r=
ecommendation
>     should be the other way round: recommend the new LE codepoint, with=
 a note
>     that historically the CS1 codepoint has been (mis)used for this pur=
pose.
>    =20
>     Regards
>        Brian Carpenter
>    =20
>=20


From nobody Wed Apr 17 11:51:45 2019
Return-Path: <David.Black@dell.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 498D812037D for <tsvwg@ietfa.amsl.com>; Wed, 17 Apr 2019 11:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.637
X-Spam-Level: 
X-Spam-Status: No, score=-0.637 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=1.363, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dell.com header.b=Vvrzm/ot; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=fVRAMSlX
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 AQL1Rl3YmD5i for <tsvwg@ietfa.amsl.com>; Wed, 17 Apr 2019 11:51:42 -0700 (PDT)
Received: from mx0a-00154904.pphosted.com (mx0a-00154904.pphosted.com [148.163.133.20]) (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 724C312037A for <tsvwg@ietf.org>; Wed, 17 Apr 2019 11:51:42 -0700 (PDT)
Received: from pps.filterd (m0170389.ppops.net [127.0.0.1]) by mx0a-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3HIeQiY002084 for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : subject : date : message-id : content-type : mime-version; s=smtpout1; bh=VcDdv763bX8hMYM4+CEo99jDZ4wuOrSS0DsyqdvPg8k=; b=Vvrzm/otUxEG5jwznKxyIPqSVgD/OmquN1HD4SLkAdmOIKS3vo7i41tG5hGRUIyCiRH8 ElP8R+yY2cIY1+7UlItdv81WEC4933A5ZuPq7optmVmqt+7qG9I/7xS2GhDiR7LmEouO c1pIemLzznF37/MVs3BzH4So/TP8Y/k198hv4cMh+dAF+70Q5wuYs0VrIQfWaRUxUsW6 3OgYdPG//pT6D1HcaBIO3JiKI2hahziBh0PJxqmj3+3wQzaJdrA782o02ZFZOLAiA0Bd 4TDtTQo5eZPa7N5+7KL+95vjcJzsKZdTM1Eusj0UHH2Nbk8raqczI1ALqbASAOliPJa7 5w== 
Received: from mx0a-00154901.pphosted.com (mx0a-00154901.pphosted.com [67.231.149.39]) by mx0a-00154904.pphosted.com with ESMTP id 2rx3ph9nce-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:41 -0400
Received: from pps.filterd (m0142693.ppops.net [127.0.0.1]) by mx0a-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x3HIgra9016100 for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:40 -0400
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by mx0a-00154901.pphosted.com with ESMTP id 2rx786aehh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:40 -0400
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x3HIpd0K019591 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:39 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com x3HIpd0K019591
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1555527099; bh=7+pHkNA43gUO+h1VZQ7yWCgEGYo=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=fVRAMSlXLaVVKFZlc91A1lNfb8xFux43ufIEQvZr7bZ3/SpP6kDwWNTRsKGTU/74q 3whj6NdoJheYkUUyS4fowxjGcTOR6vcY2gZFVxQqxKHqFvNI5i8vp5Wi5oAPFAmi6Z lbutrT3cQeVxc5rwZexG/5rl/I8xa02nepzfzheY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com x3HIpd0K019591
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd06.lss.emc.com (RSA Interceptor) for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:24 -0400
Received: from MXHUB319.corp.emc.com (MXHUB319.corp.emc.com [10.146.3.97]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id x3HIpP8u006367 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL) for <tsvwg@ietf.org>; Wed, 17 Apr 2019 14:51:25 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB319.corp.emc.com ([10.146.3.97]) with mapi id 14.03.0415.000; Wed, 17 Apr 2019 14:51:25 -0400
From: "Black, David" <David.Black@dell.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: 2nd WGLC on ecn-encap-guidelines and rfc6040-update-shim drafts, closes 6 May 2019
Thread-Index: AdT1TiSYq5Z6qA8uT0uYFsyWjQzaLg==
Date: Wed, 17 Apr 2019 18:51:24 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949363051175A@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.21.130]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949363051175AMX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-04-17_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=330 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904170124
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=367 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904170124
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gaW-0_MKroUbmIg4xiw06mNS2ko>
Subject: [tsvwg] 2nd WGLC on ecn-encap-guidelines and rfc6040-update-shim drafts, closes 6 May 2019
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: Wed, 17 Apr 2019 18:51:44 -0000

--_000_CE03DB3D7B45C245BCA0D243277949363051175AMX307CL04corpem_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This email announces a 2nd TSVWG Working Group Last Call (WGLC) on two draf=
ts:



[1] Guidelines for Adding Congestion Notification to Protocols that

                             Encapsulate IP

                draft-ietf-tsvwg-ecn-encap-guidelines-12

https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines/

This draft is intended to become a Best Current Practice RFC



[2] Propagating Explicit Congestion Notification Across IP Tunnel Headers

                          Separated by a Shim

                 draft-ietf-tsvwg-rfc6040update-shim-08

https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/

This draft is intended to become a Proposed Standard RFC.



This WGLC will run through the end of the day on Monday, May 6, 2019.



Comments should be sent to the tsvwg@ietf.org<mailto:tsvwg@ietf.org> list, =
although purely

editorial comments may be sent directly to the author. Please cc: the

WG chairs at tsvwg-chairs@ietf.org<mailto:tsvwg-chairs@ietf.org>  if you wo=
uld like the chairs to

track such editorial comments as part of the WGLC process.



No IPR disclosures have been submitted directly on either draft



Thanks,

David, Gorry and Wes

(TSVWG Co-Chairs)


--_000_CE03DB3D7B45C245BCA0D243277949363051175AMX307CL04corpem_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">This email announces a 2nd TSVWG Working Group La=
st Call (WGLC) on two drafts:
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[1] Guidelines for Adding Congestion Notification=
 to Protocols that<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Encapsulate IP<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-tsvwg-ecn-encap-guidel=
ines-12<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://datatracker.ietf.org/doc/draft=
-ietf-tsvwg-ecn-encap-guidelines/">https://datatracker.ietf.org/doc/draft-i=
etf-tsvwg-ecn-encap-guidelines/</a><o:p></o:p></p>
<p class=3D"MsoPlainText">This draft is intended to become a Best Current P=
ractice RFC<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">[2] Propagating Explicit Congestion Notification =
Across IP Tunnel Headers<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; Separated by a Shim<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-tsvwg-rfc6040upd=
ate-shim-08<o:p></o:p></p>
<p class=3D"MsoPlainText"><a href=3D"https://datatracker.ietf.org/doc/draft=
-ietf-tsvwg-rfc6040update-shim/">https://datatracker.ietf.org/doc/draft-iet=
f-tsvwg-rfc6040update-shim/</a><o:p></o:p></p>
<p class=3D"MsoPlainText">This draft is intended to become a Proposed Stand=
ard RFC.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">This WGLC will run through the end of the day on =
Monday, May 6, 2019.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Comments should be sent to the <a href=3D"mailto:=
tsvwg@ietf.org">
tsvwg@ietf.org</a> list, although purely<o:p></o:p></p>
<p class=3D"MsoPlainText">editorial comments may be sent directly to the au=
thor. Please cc: the<o:p></o:p></p>
<p class=3D"MsoPlainText">WG chairs at <a href=3D"mailto:tsvwg-chairs@ietf.=
org">tsvwg-chairs@ietf.org</a>&nbsp; if you would like the chairs to<o:p></=
o:p></p>
<p class=3D"MsoPlainText">track such editorial comments as part of the WGLC=
 process.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">No IPR disclosures have been submitted directly o=
n either draft<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">David, Gorry and Wes<o:p></o:p></p>
<p class=3D"MsoPlainText">(TSVWG Co-Chairs)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CE03DB3D7B45C245BCA0D243277949363051175AMX307CL04corpem_--


From nobody Thu Apr 18 07:14:39 2019
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 BD4FF120343 for <tsvwg@ietfa.amsl.com>; Thu, 18 Apr 2019 07:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 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] 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 B2I6s_EcLK-4 for <tsvwg@ietfa.amsl.com>; Thu, 18 Apr 2019 07:14:36 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 D88161200DF for <tsvwg@ietf.org>; Thu, 18 Apr 2019 07:14:35 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id p20so2280791qtc.9 for <tsvwg@ietf.org>; Thu, 18 Apr 2019 07:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=8b1OfRoSe8KDAEKRYFc1Jg2vh9thIL4ZL3H1TkZA3wA=; b=JWUbv1rNYllFxkoAn85HFSWE/45rt3ElNbS6JXvrPg6MCbvvY65FiwWNQEfeeCs1Mr FyXaQ/s5vovGvbtoR1jvxPeeBnPUJU37K8Ayi1BW7+H0vhWRPePshTAicI0zXhQKvO/l kbed1dGYoL0f+Ft5ZYG/VBiC9BBYJeGqBUqLzqxUv3ZFjGW+dl+J0TFmnqcajr40YfpA sarEECxRcF53YeQB0nYF0p4amMRs8CAIT8DkXSBpne5wT5SrQu9LP/SN8IcWqsWKs9y8 wyl6LEZgiQHlL1iNOymYXD8B1Ao0dD3HhBTuEq8UfowJffFw1PIer2352POULIIdpDEs 2YvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=8b1OfRoSe8KDAEKRYFc1Jg2vh9thIL4ZL3H1TkZA3wA=; b=Ya2q5oe90areIGh43kgQLaiIfcNMBEvvmZzGbchIF33sJDXBcJKXLzdVtLmGUP+Otj 3ELlI8SCcblGZi+0ZCjrg2POpIB6pu8IKao/fCZ0Xultq3irUthfO67t/lI76X9Y29ab c/Fq2baBrrACKetbQzQbWAAZ9+2xkBxnCr8t7FLUJEBFXcuPNqS8yuuOH9oJq0IWMajo 5f85GqFHq6ZDzDOieqWRrXl5ShVE8NX/wgGgQig4Monlql/xn1+WlK1e/u56VLx8T0R6 DVyaXefu/ZSfNVk9F0aj4ge/COHw6yg0R643IUCqU4ClZKMnuKveuEcDNmIQSzLKOSXk g0xQ==
X-Gm-Message-State: APjAAAVoSc5MZZixPOleIKKb6Hex+1ahofs5gHeQVACE7TY6BIUzt0zF d6U41sUSqy6kEq+PM2eyqKpXy3LCVRI=
X-Google-Smtp-Source: APXvYqxA0Dn2Ex5vmIe+ivuVu/bnXvqdeYLrxQDk+Pehef32jaPyzX97kYwBdusoKR0SPueRZRetqA==
X-Received: by 2002:ac8:3687:: with SMTP id a7mr75866241qtc.284.1555596874470;  Thu, 18 Apr 2019 07:14:34 -0700 (PDT)
Received: from [192.168.1.119] (rrcs-69-135-1-122.central.biz.rr.com. [69.135.1.122]) by smtp.gmail.com with ESMTPSA id x13sm987990qts.93.2019.04.18.07.14.33 for <tsvwg@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Apr 2019 07:14:33 -0700 (PDT)
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <39b542ad-b345-4b93-7d10-7dab04c31d80@mti-systems.com>
Date: Thu, 18 Apr 2019 10:14:32 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/LpoTpZIerngGqX375ezjIy1hpZQ>
Subject: [tsvwg] closing WGLC on TinyMT32 draft
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: Thu, 18 Apr 2019 14:14:38 -0000

Hello, we've had the TinyMT32 draft in working group last call, and 
haven't heard any significant issues with moving it forwards.

https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/

I've put a draft shepherd write-up into the tracker and plan to submit 
this for AD review late next week, unless there are any objections or 
significant new reviews that come in.



From nobody Tue Apr 23 03:53:32 2019
Return-Path: <session-request@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 250FC120045; Tue, 23 Apr 2019 03:53:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: gorry@erg.abdn.ac.uk, magnus.westerlund@ericsson.com, tsvwg-chairs@ietf.org, tsvwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155601681007.32477.5277531941168620623.idtracker@ietfa.amsl.com>
Date: Tue, 23 Apr 2019 03:53:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/FghoEajahnPrRFg3ZsUX9rJtISc>
Subject: [tsvwg] tsvwg - New Meeting Session Request for IETF 105
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 23 Apr 2019 10:53:30 -0000

A new meeting session request has just been submitted by Gorry Fairhurst, a Chair of the tsvwg working group.


---------------------------------------------------------
Working Group Name: Transport Area Working Group
Area Name: Transport Area
Session Requester: Gorry Fairhurst

Number of Sessions: 2
Length of Session(s):  1 Hour, 2 Hours
Number of Attendees: 100
Conflicts to Avoid: 
 First Priority: opsarea rtgwg tcpinc quic ippm taps mptcp tcpm rmcat iccrg tsvarea intarea saag detnet 6man
 Second Priority: dtn rtcweb v6ops tram dispatch
 Third Priority: artarea ccamp


People who must be present:
  David L. Black
  Magnus Westerlund
  Gorry Fairhurst
  Spencer Dawkins
  Wesley Eddy
  Mirja Kuehlewind

Resources Requested:

Special Requests:
  Must not conflict with Transport Area BoFs. 
Either the 1 hour or 2 hour session may be timetabled first, non-adjacent day if possible.
---------------------------------------------------------


From nobody Wed Apr 24 04:03:40 2019
Return-Path: <rs.ietf@gmx.at>
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 2825412008B; Wed, 24 Apr 2019 04:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 qQh-Thmk3hUJ; Wed, 24 Apr 2019 04:03:35 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 6050412003F; Wed, 24 Apr 2019 04:03:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1556103812; bh=dPMilXXjIEKX29d+dMB7JnAbpywXCi8TjDervKQNBxs=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=CYkUPV9iNtulEt1QwBT5B/ntJUDQyEZvcDoz5xOJGentccg4SxV6D7YUEir7edqTC bUV6lXiL1FkIQNKRt++hiOTMiaFEjj3Tovj9Az9t/Iyq/rEqWnZhD0x/0AOXy8pKKt k/VUHvd/1qqFrkvfBrvYssxT4dRQyvfyDBOuAiCU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [10.249.68.248] ([217.70.210.6]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MKYLf-1hLBEB03Oh-001vPc; Wed, 24 Apr 2019 13:03:32 +0200
To: tsvwg@ietf.org, internet-drafts@ietf.org, i-d-announce@ietf.org
References: <155234888454.23211.14096201623514072643@ietfa.amsl.com>
From: "Scheffenegger, Richard" <rs.ietf@gmx.at>
Message-ID: <3d296bef-c316-d9ca-9b14-a08917a4ab0d@gmx.at>
Date: Wed, 24 Apr 2019 13:03:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <155234888454.23211.14096201623514072643@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:v885HBOKpoic2c6gMIp26Bxgvw99N9KKcXvRYhZwXn+nLwyIKzT Xc2waz2EpASEKb2cN2LZ5A/RPzAk7EU4vYrJYhYHpVL1j/nn1TrFu5z9vgdbJ8c3kMaP2Y7 j+UMdagZFTu2A9XmJCk9P2tntyscllnedNuQc99MWPzD/62AlICuHUeM/xxI9bGYc84Wql9 0atkpKtZ3QjrmMxFEoNRg==
X-UI-Out-Filterresults: notjunk:1;V03:K0:g7Km/zJUfMs=:cI6df5HUKudyzw9kZdl04i 8Pot2my0L1kZeOObEnZSom/pyFbGbCEh7jTLjDi9TNhbymHDmybGHjjbuGwFi/z2zYLqim63H Mb0PP6dYkZnQXOxgBHHhY2YArNGmPwIC7b8lvgL6LHC7keVnCAGFA4Avd3QQL86XAWPPzPWVz EsArrsaE43rpCMiIyfhtcMEYo01ObHnQOdreHrKwX3LdAb7xNC9kpO1uWHDjqLNg4rnciG7mv IY9c9vOtocqe8RAZtSJpQkyRny3LfDG/SrcH5iWM4NAitFYiASpifZC0LdsKTHYIvxLTzibTr I19TpunYraJvHCZoAyiv6bggVTQdyysp05duELfWWukajJBH4QN4JRbunDbb3dmeZguVN6G9G ZlV6yPS0hL8xvCXglvk7uwNt+obiKz7m9rPylo/3yL22QCjaT9J5SHsn+dWLszoEZ7aGTr+Pl jWuAYCeoOmUbC4G0NomuHgthdmnOueCYAek9tCa4Vi8CjXW1zsl325GoJlf6AzZ3NzWbvgwji m5FtJErx/Xowz2Vgf09+iNz8YuK9EKNPBbJzGRpi3AoTi0lnFQ66fAIcsXY+aQ4dcIJeWemXq d03TMrzGSgzTch+7chK2z8dppd1webz7Bq3a1omL/OKD4UF5YJAkzZeS68LAXoahHh/RM+vGM VdOUkRjvnMXrtPGb4iPSD1vNR5eBPP4zo8tI/E10MayZRGYwJw8LjkI05iyHyv1hL7DQrJqr3 NcEhp6cfCd4/hJI/Ph93PrOiipexZesZ7U6ZIAg2xIMC+bH5quXCwQV3aJSSzjvG8KfOis52j ZHnVO2kt6vesm2WdDXocwxr1EFedS8ngcgbibJcUslm1TwUX3q4GoxOCvWoqb/9Gw8qp8iV0c SJsW8FqKJoJ/38QdRpR45bKuU1bpC3m7Ozr2DZY6pxShW5NXyEIimCc/pDNGdhI39pIq+nsW3 Ofw7d8QS1og==
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/bsvEWdGsS4Gr6m8jRPGKp8DPx4o>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-ecn-l4s-id-06.txt
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: Wed, 24 Apr 2019 11:03:39 -0000

Forwarding to the entire list:

Hi Bob,

I=E2=80=99m ok with all the answers you provided.
I would like to encourage that draft to the attention of implementers of
current RDMA hardware, for them to think about L4S implications =F0=9F=98=
=8A

Regarding appendix B.1:

My suggestion would be to mention DSACK as another technique (currently
only used by Linux) to mitigate the effect of spurious CC reactions,
when it turns out that the reaction was unnecessary.

With RFC6675 ("New" SACK), there is a slightly higher chance of
triggering loss recovery then three consecutive, reordered packets. For
regular non-SACK flows and the old three-dupack rule, you are correct
that singular reorderings are not an issue, ever.




 >> Apdx A.1.7, ~para 5
 >>
 >> As another example, LACP restricts individual flows to use only
 >> one specific constituent link - effectively restricting the
 >> maximum bandwidth attainable for a single flow to no more than
 >> the bandwidth of a single link - even when the majority of the
 >> remaining links is idle. (this is a common misconception by
 >> enterprise network operators, who believe LACP can "scale up"
 >> the bandwidth available for  a single mount)

 > Yup. As long as LACP is still being used e2e, this single link
 > constraint would have to remain. The L4S requirement about counting
 > in time units might be applied to whatever e2e protocol replaced LACP
 > in future, then it would scale with the transfer rate.

LACP is p2p not e2e =F0=9F=98=8A. And many devices already allow a round-r=
obin
load balancing (some devices really don=E2=80=99t like this though =E2=80=
=93 older
silicon switching engines usually). TCP RACK  /time based loss detection
would allow the use of RR load balancing for LACP (ethernet), to
actually increase the single-flow throughput across LACP trunks . Sorry
for not making this point more clear.


[removed invalid objection discussed privately]

From: Bob Briscoe <ietf@bobbriscoe.net>
Sent: Montag, 25. M=C3=A4rz 2019 01:49
To: Scheffenegger, Richard <Richard.Scheffenegger@netapp.com>;
gorry@erg.abdn.ac.uk; koen.de_schepper@nokia.com
Cc: tsvwg-chairs@ietf.org; 'Wesley Eddy' <wes@mti-systems.com>
Subject: Re: Review on tsvwg of one of the L4S WG drafts

NetApp Security WARNING: This is an external email. Do not click links
or open attachments unless you recognize the sender and know the content
is safe.

Richard,

Thx for your obviously v thorough review. Inline...
On 24/03/2019 12:52, Scheffenegger, Richard wrote:
Review of draft-ietf-tsvwg-ecn-l4s-id:

Overall, a well-written document. However, I found the following nits,
clarification questions that may need to be answered by Mellanox, before
referenced in the draft, and one incorrect claim about the CE
classification into the L4S Queue:



Nit: I understand Bobs urge to use the British English (borrowed from
French?) centre instead of center. However, at least in "Data Center
TCP" I think the spelling should be US-english.
OK


Section 1.2:

L4S:

May need to solicit input from Mellanox around their RoCEv2 CC mechanism
DCQCN - if this would also fall - and be interoperable with - the L4S
definition. Based on the publicly available info, they designed DCQCN to
work along with instantaneous queue marking, and a variable-extent
feedback mechanism (inspired by QCN). However, I've not seen and
independent studies where DCTCP and DCQCN would run in the same Q.

(RDMA is currently en-vogue in DC environments; Mellanox doing the dev
on RoCE behind closed doors doesn't really inspire too much confidence
in the outcome with me though.
I don't think you're asking me to do anything here. Whatever the outcome
of this question, it doesn't alter what section 1.2 defines L4S to be,
or what it should be.

RoCEv2 is a proprietary protocol. And it's only used in controlled
environments. If it falls under the definition of L4S given here, fine.
If it doesn't, also fine. Whether or not it is compatible with this
definition of L4S does not stop it being used in the same controlled
environments as it is today. Or am I missing something?




Section 5.2.

Cross ref link not yet exists.
Thx for catching this.


Section 5.3

Is text around this eventuality really required in the draft? Wouldn't
long-term identification of flows beyond a single packet be outside the
scope  normally? Just wondering if this complicates the draft more than
it helps.
An FQ implementation with L4S AQM in some queues and Classic in others
is a valid alternative to the DualQ Coupled AQM.

In the stateless case it's straightforward: ECT(1) identifies a packet
as L4S.
But with flow state, we need to define what an L4S flow is, which
implies we have to deal with the case where there's a mix of ECT(0) and
ECT(1) in the flow.




Section 5.4

Another example of a protocol that would benefit from low-latency
treatment, but is low volume would be NTP, and perhaps LDAP (but the
latter can be voluminous at times).
I've added them both.



Regarding ECN++ - references to it are currently only in the appendices.
It appears to me, that and successful operational deployment of a L4S
transport might be dependent on this, to warrant mentioning it somewhere
in the body of the draft too?
The reason it's only in the Appendix is because the Prague requirements
are split into mandatory requirements and optional performance
improvements. Only the mandatory reqs are in the body.

Altho a performance improvement is important, it doesn't need to be
mandated (cos there's no interop implication or downside so it's a
no-brainer without having to be a requirement).




Apdx A.1.7, ~para 5

As another example, LACP restricts individual flows to use only one
specific constituent link - effectively restricting the maximum
bandwidth attainable for a single flow to no more than the bandwidth of
a single link - even when the majority of the remaining links is idle.
(this is a common misconception by enterprise network operators, who
believe LACP can "scale up" the bandwidth available for  a single mount)
Yup. As long as LACP is still being used e2e, this single link
constraint would have to remain. The L4S requirement about counting in
time units might be applied to whatever e2e protocol replaced LACP in
future, then it would scale with the transfer rate.


Para6: type "ussed".
Thx
Note that the wording might incorrectly imply that only RoCE can be used
for RDMA, while at least one IETF alternative exists (iWARP). Also, I
believe the extremely strict in-order requirement was with RoCEv1, while
RoCEv2 did learn from real-world deployments where in-order and
loss-less delivery is not always attainable... Again, something to get
Mellanox to comment about.
Good point. So I could say:
    Also note that in some controlled environments no reordering is
    tolerated by some transports (e.g.  RoCEv2 used for RDMA, in
contrast to iWARP),




Apdx B.1

 >> A reference to DSACK could be made here - while no stack (perhaps
 >> Linux does) performs cwnd unwinding in case of a DSACK for fast
 >> retransmissions (more stacks to unrolling of RTO state changes
 >> when DSACK is found), this would be a mechanism which also mitigates
 >> the problem of spurious retransmissions.

 > What point are you wanting me to make here? I'm not sure a point
about > DSACK would be relevant to the thread of the argument here.
 >
 > Regards and thanks again...
 >
 >Bob





Best regards,
    Richard


Am 12.03.2019 um 01:01 schrieb internet-drafts@ietf.org:
>
> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.
> This draft is a work item of the Transport Area Working Group WG of the =
IETF.
>
>          Title           : Identifying Modified Explicit Congestion Noti=
fication (ECN) Semantics for Ultra-Low Queuing Delay (L4S)
>          Authors         : Koen De Schepper
>                            Bob Briscoe
> 	Filename        : draft-ietf-tsvwg-ecn-l4s-id-06.txt
> 	Pages           : 40
> 	Date            : 2019-03-11
>
> Abstract:
>     This specification defines the identifier to be used on IP packets
>     for a new network service called low latency, low loss and scalable
>     throughput (L4S).  It is similar to the original (or 'Classic')
>     Explicit Congestion Notification (ECN).  'Classic' ECN marking was
>     required to be equivalent to a drop, both when applied in the networ=
k
>     and when responded to by a transport.  Unlike 'Classic' ECN marking,
>     for packets carrying the L4S identifier, the network applies marking
>     more immediately and more aggressively than drop, and the transport
>     response to each mark is reduced and smoothed relative to that for
>     drop.  The two changes counterbalance each other so that the
>     throughput of an L4S flow will be roughly the same as a 'Classic'
>     flow under the same conditions.  However, the much more frequent
>     control signals and the finer responses to them result in ultra-low
>     queuing delay without compromising link utilization, and low delay i=
s
>     maintained during high load.  Examples of new active queue managemen=
t
>     (AQM) marking algorithms and examples of new transports (whether TCP=
-
>     like or real-time) are specified separately.  The new L4S identifier
>     is the key piece that enables them to interwork and distinguishes
>     them from 'Classic' traffic.  It gives an incremental migration path
>     so that existing 'Classic' TCP traffic will be no worse off, but it
>     can be prevented from degrading the ultra-low delay and loss of the
>     new scalable transports.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-l4s-id/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tsvwg-ecn-l4s-id-06
> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-ecn-l4s-id-06
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-tsvwg-ecn-l4s-id-06
>
>
> Please note that it may take a couple of minutes from the time of submis=
sion
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>


From nobody Thu Apr 25 08:51:20 2019
Return-Path: <gorry@erg.abdn.ac.uk>
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 EF51A120161 for <tsvwg@ietfa.amsl.com>; Thu, 25 Apr 2019 08:51:18 -0700 (PDT)
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] 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 V3Cqv_tYyqOU for <tsvwg@ietfa.amsl.com>; Thu, 25 Apr 2019 08:51:16 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB88120019 for <tsvwg@ietf.org>; Thu, 25 Apr 2019 08:51:15 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id A7CB01B00226 for <tsvwg@ietf.org>; Thu, 25 Apr 2019 16:51:12 +0100 (BST)
Message-ID: <5CC1D770.60809@erg.abdn.ac.uk>
Date: Thu, 25 Apr 2019 16:51:12 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <155620706460.23438.15285479573015945377.idtracker@ietfa.amsl.com>
In-Reply-To: <155620706460.23438.15285479573015945377.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/XKKs4BVsDALiOF1lgCyJ2VgogTg>
Subject: Re: [tsvwg] New Version Notification for draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt
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: Thu, 25 Apr 2019 15:51:19 -0000

Following discussions at the last IETF with my co-chairs, I was asked to 
resubmit the UDP Options text for DPLPMTUD as a separate draft.  This 
removes dependencies on completing the UDP-Options work before the 
DPLPMTUD I-D can be published, which is hoped to allow earlier publication.

This will allow new methods to be developed to work with DPLPMTUD in 
pararllel with the completion of the work on UDP-Options.

We'll publish a new revision of the DPLPMTUD draft shortly that removes 
this text.

Gorry

Best wishes, Gorry and Tom.
> A new version of I-D, draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt
> has been successfully submitted by Godred Fairhurst and posted to the
> IETF repository.
>
> Name:		draft-fairhurst-tsvwg-udp-options-dplpmtud
> Revision:	00
> Title:		Datagram PLPMTUD for UDP Options
> Document date:	2019-04-25
> Group:		Individual Submission
> Pages:		8
> URL:            https://www.ietf.org/internet-drafts/draft-fairhurst-tsvwg-udp-options-dplpmtud-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-fairhurst-tsvwg-udp-options-dplpmtud/
> Htmlized:       https://tools.ietf.org/html/draft-fairhurst-tsvwg-udp-options-dplpmtud-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-fairhurst-tsvwg-udp-options-dplpmtud
>
>
> Abstract:
>     This document describes how a UDP Options sender may implement
>     Datagram Packetization Layer Path Maximum Transmission Unit Discovery
>     (DPLPMTUD) as a robust method for Path Maximum Transmission Unit
>     Discovery.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat


From nobody Thu Apr 25 11:05:07 2019
Return-Path: <noreply@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BB61200FE; Thu, 25 Apr 2019 11:05:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Wesley Eddy via Datatracker <noreply@ietf.org>
To: <magnus.westerlund@ericsson.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: wes@mti-systems.com, iesg-secretary@ietf.org, tsvwg-chairs@ietf.org, Wesley Eddy <wes@mti-systems.com>, tsvwg@ietf.org
Message-ID: <155621550580.15078.1583175807086851133.idtracker@ietfa.amsl.com>
Date: Thu, 25 Apr 2019 11:05:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/AgjqxqHhhDCEZ81pT724wdBjWeQ>
Subject: [tsvwg] Publication has been requested for draft-ietf-tsvwg-tinymt32-01
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 25 Apr 2019 18:05:06 -0000

Wesley Eddy has requested publication of draft-ietf-tsvwg-tinymt32-01 as Proposed Standard on behalf of the TSVWG working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/


From nobody Sat Apr 27 10:14:08 2019
Return-Path: <touch@strayalpha.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 F276112018C; Sat, 27 Apr 2019 10:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level: 
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 40Jt-YMjl6MK; Sat, 27 Apr 2019 10:13:57 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 257D812015A; Sat, 27 Apr 2019 10:13:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding: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=CBmoxce9Y41f1lFpglVXx2yQb12UOQpKlz5BZEcF8SY=; b=PRbeUo1L3EuMx/J/VxjZ4ImHG SU1Z34IdNEDYO6bq0kcqYBafaVIW18PgSNuwsSsaVC0HgVQRBQNRPn8VbtzTRscIMAo6CbKXg/I9p vYnLlHDPs+/UbHEkVCLA/LmA8KK9QVIsUbev9uzpabfbNHPBqQdPeMjg+dhnJ6QIUAj7xeMAPPC2D n5/BBJudKnqPB4Y4oBGatsI+jO1iNeynh6aRPr+Px7JvPV3vsLjJqYJPjaezgFIUYV93m4+VhPONi upOb+QhpxGe+NDVjjRTBG4ozTdFr4jiPiYKb8n8HW6o6FlmUKSMfQ1vcF4ap5wdiosK7fGZkWPjct pU6AiwYgA==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:50510 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1hKQtb-001x3G-RG; Sat, 27 Apr 2019 13:13:56 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_E2396DA2-7037-4414-8BB0-87F9202A2692"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949363052958E@MX307CL04.corp.emc.com>
Date: Sat, 27 Apr 2019 10:13:51 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>, tsvwg <tsvwg@ietf.org>
Message-Id: <598B8434-3B6D-434A-B963-7FEE04D9770B@strayalpha.com>
References: <CE03DB3D7B45C245BCA0D243277949363052958E@MX307CL04.corp.emc.com>
To: "Black, David" <David.Black@dell.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/He8DGJDr8Zva1moVXByCUTQbnzU>
Subject: Re: [tsvwg] [Int-area] 2nd TSVWG WGLC on ecn-encap-guidelines and rfc6040-update-shim drafts, closes 6 May 2019
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, 27 Apr 2019 17:13:59 -0000

--Apple-Mail=_E2396DA2-7037-4414-8BB0-87F9202A2692
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Cross-posting to let both communities know:

- it would be useful for these documents to address how fragmentation =
and reassembly affects these signals
	(esp. if reassembling fragments with different ECN values)

- it would be useful for these documents to consider =
draft-ietf-intarea-tunnels (which relates to the above) and its =
discussion on many of the protocols cited

Joe

> On Apr 26, 2019, at 1:50 PM, Black, David <David.Black@dell.com> =
wrote:
>=20
> This may be of interest to INT folks who are interested in tunnels and =
encapsulations.
> =20
> Comments by the WGLC deadline are encouraged, but comments after the =
deadline are ok, as they=E2=80=99d have to be dealt with anyway at IETF =
Last Call.
> =20
> Thanks, --David
> =20
> From: tsvwg <tsvwg-bounces@ietf.org <mailto:tsvwg-bounces@ietf.org>> =
On Behalf Of Black, David
> Sent: Wednesday, April 17, 2019 2:51 PM
> To: tsvwg@ietf.org <mailto:tsvwg@ietf.org>
> Subject: [tsvwg] 2nd WGLC on ecn-encap-guidelines and =
rfc6040-update-shim drafts, closes 6 May 2019
> =20
> [EXTERNAL EMAIL]=20
>=20
> This email announces a 2nd TSVWG Working Group Last Call (WGLC) on two =
drafts:
> =20
> [1] Guidelines for Adding Congestion Notification to Protocols that
>                              Encapsulate IP
>                 draft-ietf-tsvwg-ecn-encap-guidelines-12
> =
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines/ =
<https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidelines/>
> This draft is intended to become a Best Current Practice RFC
> =20
> [2] Propagating Explicit Congestion Notification Across IP Tunnel =
Headers
>                           Separated by a Shim
>                  draft-ietf-tsvwg-rfc6040update-shim-08
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/ =
<https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-shim/>
> This draft is intended to become a Proposed Standard RFC.
> =20
> This WGLC will run through the end of the day on Monday, May 6, 2019.
> =20
> Comments should be sent to the tsvwg@ietf.org <mailto:tsvwg@ietf.org> =
list, although purely
> editorial comments may be sent directly to the author. Please cc: the
> WG chairs at tsvwg-chairs@ietf.org <mailto:tsvwg-chairs@ietf.org>  if =
you would like the chairs to
> track such editorial comments as part of the WGLC process.
> =20
> No IPR disclosures have been submitted directly on either draft
> =20
> Thanks,
> David, Gorry and Wes
> (TSVWG Co-Chairs)
> =20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org <mailto:Int-area@ietf.org>
> https://www.ietf.org/mailman/listinfo/int-area =
<https://www.ietf.org/mailman/listinfo/int-area>

--Apple-Mail=_E2396DA2-7037-4414-8BB0-87F9202A2692
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Cross-posting to let both communities know:<div class=3D""><br =
class=3D""></div><div class=3D"">- it would be useful for these =
documents to address how fragmentation and reassembly affects these =
signals</div><div class=3D""><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>(esp. if reassembling fragments =
with different ECN values)</div><div class=3D""><br class=3D""></div><div =
class=3D"">- it would be useful for these documents to consider =
draft-ietf-intarea-tunnels (which relates to the above) and its =
discussion on many of the protocols cited</div><div class=3D""><br =
class=3D""></div><div class=3D"">Joe<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Apr =
26, 2019, at 1:50 PM, Black, David &lt;<a =
href=3D"mailto:David.Black@dell.com" =
class=3D"">David.Black@dell.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: rgb(153, 51, 102);" class=3D"">This may be of interest =
to INT folks who are interested in tunnels and encapsulations.<o:p =
class=3D""></o:p></span></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><span =
style=3D"color: rgb(153, 51, 102);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(153, 51, 102);" class=3D"">Comments =
by the WGLC deadline are encouraged, but comments after the deadline are =
ok, as they=E2=80=99d have to be dealt with anyway at IETF Last =
Call.<o:p class=3D""></o:p></span></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(153, 51, 102);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(153, 51, 102);" class=3D"">Thanks, =
--David<o:p class=3D""></o:p></span></div></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><span style=3D"color: rgb(153, 51, 102);" class=3D""><o:p =
class=3D"">&nbsp;</o:p></span></div><div class=3D""><div =
style=3D"border-style: solid none none; border-top-width: 1pt; =
border-top-color: rgb(225, 225, 225); padding: 3pt 0in 0in;" =
class=3D""><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><b class=3D"">From:</b><span=
 class=3D"Apple-converted-space">&nbsp;</span>tsvwg &lt;<a =
href=3D"mailto:tsvwg-bounces@ietf.org" style=3D"color: rgb(149, 79, =
114); text-decoration: underline;" =
class=3D"">tsvwg-bounces@ietf.org</a>&gt;<span =
class=3D"Apple-converted-space">&nbsp;</span><b class=3D"">On Behalf =
Of<span class=3D"Apple-converted-space">&nbsp;</span></b>Black, David<br =
class=3D""><b class=3D"">Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Wednesday, April 17, 2019 =
2:51 PM<br class=3D""><b class=3D"">To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tsvwg@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">tsvwg@ietf.org</a><br =
class=3D""><b class=3D"">Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[tsvwg] 2nd WGLC on =
ecn-encap-guidelines and rfc6040-update-shim drafts, closes 6 May =
2019<o:p class=3D""></o:p></div></div></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><p =
class=3D""><span style=3D"color: rgb(206, 17, 38);" class=3D"">[EXTERNAL =
EMAIL]<span class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></span></p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This email announces a 2nd TSVWG Working Group Last Call =
(WGLC) on two drafts:<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">[1] Guidelines for Adding Congestion Notification to =
Protocols that<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Encapsulate IP<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; draft-ietf-tsvwg-ecn-encap-guidelines-12<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-guidel=
ines/" style=3D"color: rgb(149, 79, 114); text-decoration: underline;" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-ecn-encap-gui=
delines/</a><o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This draft is intended to become a Best Current Practice =
RFC<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">[2] =
Propagating Explicit Congestion Notification Across IP Tunnel =
Headers<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; Separated by a Shim<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
draft-ietf-tsvwg-rfc6040update-shim-08<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update-sh=
im/" style=3D"color: rgb(149, 79, 114); text-decoration: underline;" =
class=3D"">https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rfc6040update=
-shim/</a><o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This draft is intended to become a Proposed Standard RFC.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">This WGLC =
will run through the end of the day on Monday, May 6, 2019.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Comments =
should be sent to the<span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:tsvwg@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">tsvwg@ietf.org</a><span =
class=3D"Apple-converted-space">&nbsp;</span>list, although purely<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">editorial =
comments may be sent directly to the author. Please cc: the<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">WG chairs =
at<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:tsvwg-chairs@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline;" class=3D"">tsvwg-chairs@ietf.org</a>&nbsp; =
if you would like the chairs to<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">track such editorial comments as part =
of the WGLC process.<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">No IPR disclosures have been submitted directly on either =
draft<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Thanks,<o:p=
 class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">David, =
Gorry and Wes<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">(TSVWG Co-Chairs)<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><span style=3D"caret-color: rgb(0, 0, =
0); font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none; float: none; display: inline !important;" =
class=3D"">_______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Int-area mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:Int-area@ietf.org" style=3D"color: rgb(149, 79, 114); =
text-decoration: underline; font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">Int-area@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/int-area" style=3D"color: =
rgb(149, 79, 114); text-decoration: underline; font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/int-area</a></div></block=
quote></div><br class=3D""></div></body></html>=

--Apple-Mail=_E2396DA2-7037-4414-8BB0-87F9202A2692--


From nobody Sun Apr 28 06:16:01 2019
Return-Path: <dave.taht@gmail.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 9F66B12003E; Sun, 28 Apr 2019 06:15:58 -0700 (PDT)
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 Ix862cwTeD33; Sun, 28 Apr 2019 06:15:56 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (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 8C3091200CC; Sun, 28 Apr 2019 06:15:56 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id h26so6758555ioj.1; Sun, 28 Apr 2019 06:15:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=/IcVpYLZHvheZz/hovsVN6CKrqkz+UXohDfNKzalfq4=; b=R2jfqtO7iLQP9po7d/japovXmmYPfZBRKtkDCjnxyhYzM6wlVbGPPltMY/F/asxSgq HDy+n+m8vCOF6kZl1kI98HCh4GqhndffDbGkePSMVGec8UdW5bF/40K8+72/Jvz7apDA Pip/22p+JTyUDKG8ux94jn2yoPpim6LT0p8FNVDiHuigo/WU/AWZKEIMKuYxnOlfUvPb PMMhuMYEhH66262k0yV7euWlBUdsk3R66hRWljnt+S64OzjJfjAG4OTUT8o/MCneTlZy jcxAOTM1b0oBC/HsCQZ7hMqaovoy8ZifuGp/vQHHF6o7OaNhgie2Q5NFzdDEWOASwcrp UQaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=/IcVpYLZHvheZz/hovsVN6CKrqkz+UXohDfNKzalfq4=; b=Cv7L0/zmA6icDNL+eBWntCI45U0Y8BA/dUrcG+EKphaLvVi8FnMrAfCY6csNf13Ajf MjlIaFT0YecfCrY1jFJCDgrCfJqvLa7RgFpHt/0wITD+QEFpI1BeIqWMO9yZcn+lHGNI MBSBtSs23gdN64/3OsxXuWsC9lisbK6mrfcqgM2QjYLRfKyvT1BtYRPoA9bAYm3PACxA UGiin/IYI+G3mmIA/rmsSFhLAp/A0ybfAi+Yt3Na8lh1wtxLc7Hd8FRPsmKpGd/E3R0i sTmninsbxxc/mMevaTEaZqT/7iWqqVjxHXkIS8/4fDyGi9+A01Ug6SbNd98kduyJgPch eKUA==
X-Gm-Message-State: APjAAAV/VU435tM6YdE/XVF+fpldT4/AVgYOWJk/hhKnHC8VNBAlon5K //6dEJpDro8x9NehbG7ZU/60BKp3WSUxQ2k8wn8=
X-Google-Smtp-Source: APXvYqyA615LkbisQtvppstkt1Q1fLLnFFy/3CmVw7ko0e+H4x3nhcTVER74bZormnoLp1po0oVnPCqgmt3uolbFRiY=
X-Received: by 2002:a6b:f809:: with SMTP id o9mr37300915ioh.232.1556457355796;  Sun, 28 Apr 2019 06:15:55 -0700 (PDT)
MIME-Version: 1.0
From: Dave Taht <dave.taht@gmail.com>
Date: Sun, 28 Apr 2019 15:15:44 +0200
Message-ID: <CAA93jw5eU8f7Ldp1-ssHyfO104GOGbQh8m28guTum5KMafoPtw@mail.gmail.com>
To: Cake List <cake@lists.bufferbloat.net>, tsvwg IETF list <tsvwg@ietf.org>,  iccrg IRTF list <iccrg@irtf.org>, rmcat@ietf.org, BBR Development <bbr-dev@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/jhBWVQ-DzhFKD0j1LVT-Ehe9J1c>
Subject: [tsvwg] sch_cake shaper/aqm/fq implementation in linux slides and paper
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: Sun, 28 Apr 2019 13:15:59 -0000

Since sch_cake has been generally available as dual licensed (BSD/GPL)
open source since last august (as of linux 4.19), and shipping in
openwrt and evenroute for 3 years, I have generally longed for more
folk to be fiddling with it in the ietf. The most current stable
version is in openwrt 18.02, which shipped in january. Cake is in
general is too complicated and addresses too many things to
encapsulate into an RFC, but in particular, the DOCSIS/DSL/Ethernet
framing compensation modes are excellent (unlike the BSD pfsense one),
and we have many other improvements to multiple components of the SQM
systems we've been shipping for 8 years. such as per host/per flow FQ,
sane diffserv support, and ack-filtering being theprimary ones covered
in slides from my IEEE lanman talk:

http://www.taht.net/~d/sch_cake_ieee_lanman2018%20(2).pdf

One major feature not brought out in paper or slides is that cake
works the same whether it has backpressure from the device or via
"BQL", OR in shaping in software. Another important feature -
GRO-splitting, we haven't gone into much in print yet. In the extra
slides section are some nice results from a GPON fiber network. It can
also be used as a local host-only qdisc; there is a brief comparison
of cake vs sch_fq also in the slides above. As well as in network
namespaces, vms, docker containers, multi-tenant dcs, etc, etc.

All the features of cake were developed in close collaboration with
the actual users of SQM in the field.

That paper: https://arxiv.org/pdf/1804.07617.pdf - talks about "Home"
gateways but since then we got it to scale past 50GigE in software
alone. I look forward to more independent benchmarkings in other
scenarios, and we do take bug reports on the github.

Some of the new SCE ("Some Congestion Experienced") related work has
landed in the https://github.com/dtaht/sch_cake repo already (as well
as fq_codel_fast) but the majority of work is taking place over in
jonathan's repos presently.

There is a paper pending, also, on the improvements to codel that
jonathan (primarily) made in the COBALT AQM that I hope will be
published soon.

One thing I've longed for is some coherent testing of the modern
videoconferencing and quic and bbr congestion control algorithms
against it. Is there anyone out there able to do this and possibly
collaborate on a paper on it?

I was really quite unaware until this past ietf that so few had had a
taste of cake yet.

thx!

--=20

Dave T=C3=A4ht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740


From nobody Sun Apr 28 06:54:16 2019
Return-Path: <dave.taht@gmail.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 7C81B1200CC; Sun, 28 Apr 2019 06:54:01 -0700 (PDT)
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 EdsYpq4SUd2z; Sun, 28 Apr 2019 06:53:59 -0700 (PDT)
Received: from mail-it1-x136.google.com (mail-it1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 92562120075; Sun, 28 Apr 2019 06:53:59 -0700 (PDT)
Received: by mail-it1-x136.google.com with SMTP id v8so8574297itf.0; Sun, 28 Apr 2019 06:53:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=bOYsmW993aQnD8gP1AtW+kXEvxFrthwFF7j8qUalFPs=; b=OdFIaGwWNhJ8dE3ev4ajSpAsLL/EjfOB7OBoGvZnaox5Zryro3vRUchy8KLCHd9pma S+b6b4jW5pFcFAumtFQAvAuKeIYX2YpPPwULi17oZsrKhrKLGi7QC91h7lEc+gXfL6e9 S5O9uHWn+gks+epwAkrc3dS7LqSQk/Bv4ZlmrThxi/eSpbscVhigQ68P5MFRynV8GNDC Sn0wQAVGhKNFHzY4hxjWY+idtCDjfzkO5qazYwXJiPxET+n/c+ExhA/rzQhjaoJ4epDW v7QPzIPYPulWtRemPJSere6Wjpp6uqBr/gGHzRAgWCWBoTn+Vpvf1p/8XoOznSmiXezX fMVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=bOYsmW993aQnD8gP1AtW+kXEvxFrthwFF7j8qUalFPs=; b=W8kgowbu7Hr60wmR2WZe1MZxCzpsxuUgZnVbfV2GegONtviILjrKtEKq1gTdOTgByu Q6C/Jyzt0g0AZbhfH1dR/aIS4Zg1CnOaJjor/WDzUsUVRswAgqKifAfoUJbBAaY/K5sC sgYsRv5BGKEWAtC+l//McR1nxlFVhI+meF55CJAQGOrFXgnnALKiUvVAjMJnK0mRoqX+ H7IWw8RxY/6qI86SHtefkM7LAAzWKOFiDFpWk7JzbaIHkXw8Ob8TfwkkowGW4VOz/sr5 yKVizqlUEpVnRQjjjEYjw/c5uIQIHRBpBymxkiXKid4shS+FetjP+ffzbd19PbygVg0V aPSw==
X-Gm-Message-State: APjAAAVttXg0htg3K3HemEiXBxKgovBZckv9Sasn1FGiJciRI/FIgy2l CqJrW/aQbhnPWJRGPQVsic7RefVtBuy1YgUhWf9LRJkVh97RxA==
X-Google-Smtp-Source: APXvYqzIvgTxoG5vyoUI+LbcOdOicifD+QLBh96GniP5ifn2EsEd2I6TtgMmhLgcgRy0dSp3gfs+9vagQbRb9qI10jE=
X-Received: by 2002:a24:493:: with SMTP id 141mr3216366itb.76.1556459638648; Sun, 28 Apr 2019 06:53:58 -0700 (PDT)
MIME-Version: 1.0
From: Dave Taht <dave.taht@gmail.com>
Date: Sun, 28 Apr 2019 15:53:47 +0200
Message-ID: <CAA93jw7eZ0Rfvc+tUKx0mG_Bdxqos-DTBn=ojYJCM0UCh38ScA@mail.gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>,  Andrew Sullivan <ajs@anvilwalrusden.com>, chair@ietf.org, The IESG <iesg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Fuc2Ars_xsfrBj0VmR4Fbda8bEM>
Subject: [tsvwg] travel funds for ietf for the next SCE talk?
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: Sun, 28 Apr 2019 13:54:02 -0000

Several members of the open source "bufferbloat.net" group do
regularly participate in ietf mailing lists and remote meetings, but
it is rare that any of us
can actually afford to attend IETF. In fact, we've had no travel
budget for 3 years running. I'd mostly reduced my involvement to BABEL
after the AQM wg closed, and that remotely only.

This past IETF, we had to hold a bake sale on the bloat mailing list
as well as melt all my credit cards in order to get our new SCE "Some
Congestion Experienced" AQM concept in front of the tsvwg and iccrg
working groups in contrast to the cablelabs dualpi proposal.

(if anyone cares, the TSVWG talk and slides are here:
https://www.youtube.com/watch?v=3DJQmWyr0JDJM&t=3D1h3m50s ) -

The controversy in the open source community, covered here:
https://lwn.net/Articles/783673/

We've been *very strongly encouraged* to present again at the upcoming
ietf in montreal, but I'm now in no position to sponsor the 2-3 core
people again that need to present the follow-on results in the 5 or so
related wgs. Is there an org, a fund, a means, a way, to get a bunch
of rather poor, but innovative, open source devs and theorist, out
there, that we can apply to? raise the ~9k needed? isoc? Something?

(and if it were possible i'd rather like to have what I had had to
spend back, so I can pour it into recreating a network testbed for
this work. I'm not planning to attend, myself. The one trip alone
wiped out ecn-sane's budget for the year)

--=20

Dave T=C3=A4ht
CTO, TekLibre, LLC
Co-Founder, Bufferbloat.net
http://www.teklibre.com
Tel: 1-831-205-9740


From nobody Mon Apr 29 06:54:17 2019
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: tsvwg@ietf.org
Delivered-To: tsvwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 775DA12031D; Mon, 29 Apr 2019 06:54:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
CC: magnus.westerlund@ericsson.com, tsvwg@ietf.org, wes@mti-systems.com, draft-ietf-tsvwg-tinymt32@ietf.org, tsvwg-chairs@ietf.org, Wesley Eddy <wes@mti-systems.com>
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <155654604944.15841.16662074904783767531.idtracker@ietfa.amsl.com>
Date: Mon, 29 Apr 2019 06:54:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/qSv1GLC3pCEf1xdxClF5pe5EhhE>
Subject: [tsvwg] Last Call: <draft-ietf-tsvwg-tinymt32-01.txt> (TinyMT32 Pseudo Random Number Generator (PRNG)) to Proposed Standard
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 29 Apr 2019 13:54:10 -0000

The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document: - 'TinyMT32 Pseudo Random Number
Generator (PRNG)'
  <draft-ietf-tsvwg-tinymt32-01.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-05-13. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   This document describes the TinyMT32 Pseudo Random Number Generator
   (PRNG) that produces 32-bit pseudo-random unsigned integers and aims
   at having a simple-to-use and deterministic solution.  This PRNG is a
   small-sized variant of Mersenne Twister (MT) PRNG, also designed by
   M.  Saito and M.  Matsumoto.  The main advantage of TinyMT32 over MT
   is the use of a small internal state, compatible with most target
   platforms including embedded devices, while keeping a reasonably good
   randomness.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-tinymt32/ballot/


No IPR declarations have been submitted directly on this I-D.





From nobody Mon Apr 29 08:33:04 2019
Return-Path: <magnus.westerlund@ericsson.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 06D84120025; Mon, 29 Apr 2019 08:33:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 rXnzuimsZCKy; Mon, 29 Apr 2019 08:33:00 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00053.outbound.protection.outlook.com [40.107.0.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D4A112034C; Mon, 29 Apr 2019 08:32:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=o2czkA11BVLEbPMihiQ2QKuZw9KZlrHsWYxzejdSqyw=; b=hEe//namcDzCfCeL5u3larTG8AaPKfB7/zLbuqgoDLfQtfM/Ea9WX4OpciFfTkUuMUXFblAa4cxF+FyKExzzHwEarSOQJLM7Z03MOM5HMCbmkGV1T1PNuG1zbTjcqF0kOsodRF6/nf1V1QM0ag73BvJRiyL8prIJlv6q+2qIWwA=
Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com (10.168.128.149) by HE1PR0701MB2283.eurprd07.prod.outlook.com (10.168.36.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.7; Mon, 29 Apr 2019 15:32:55 +0000
Received: from HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::b161:fb77:e4ea:4723]) by HE1PR0701MB2522.eurprd07.prod.outlook.com ([fe80::b161:fb77:e4ea:4723%3]) with mapi id 15.20.1856.008; Mon, 29 Apr 2019 15:32:55 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Dave Taht <dave.taht@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>, Andrew Sullivan <ajs@anvilwalrusden.com>, The IESG <iesg@ietf.org>
Thread-Topic: travel funds for ietf for the next SCE talk?
Thread-Index: AQHU/cneO/MepbMfKEimxUTyWE/Y/Q==
Date: Mon, 29 Apr 2019 15:32:55 +0000
Message-ID: <HE1PR0701MB25221DA057496B1A89FD391B95390@HE1PR0701MB2522.eurprd07.prod.outlook.com>
References: <CAA93jw7eZ0Rfvc+tUKx0mG_Bdxqos-DTBn=ojYJCM0UCh38ScA@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=magnus.westerlund@ericsson.com; 
x-originating-ip: [192.176.1.86]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1e8e3e1e-984a-4508-8d4e-08d6ccb7f3b0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:HE1PR0701MB2283; 
x-ms-traffictypediagnostic: HE1PR0701MB2283:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <HE1PR0701MB228335F3C87AA0A02C1906E695390@HE1PR0701MB2283.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0022134A87
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(366004)(396003)(376002)(346002)(136003)(189003)(199004)(99286004)(74316002)(305945005)(7696005)(44832011)(966005)(7736002)(68736007)(229853002)(5660300002)(8936002)(86362001)(476003)(2906002)(52536014)(486006)(478600001)(256004)(53936002)(33656002)(26005)(446003)(3846002)(66066001)(73956011)(110136005)(25786009)(561944003)(6506007)(76176011)(66556008)(66476007)(6436002)(97736004)(316002)(66946007)(9686003)(6306002)(55016002)(81166006)(102836004)(81156014)(8676002)(6116002)(186003)(14454004)(53546011)(64756008)(71200400001)(66446008)(71190400001)(14444005)(6246003)(76116006); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0701MB2283; H:HE1PR0701MB2522.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Gns03ubGBz+xkL2wVgc7ECYcprkOcSzBGYVN80youHPUYMqevm7sXysQjjVK9zCnq/EYuPOCrKwe4jdx9+Fnw27wTlmLyAnLwA2F6c+7oqD3ZrTRPnS2Ug+7SbXFdVAuJYm3+71BJSsaqiXqyPADLyI5VwfJBpCmBEDoWgg0Bh6lcEgLAPmtlv7k4zSGVRJfoCmjMoxVePOYsBelgbPWFA+kqHkOZV+lGAV0pr9KU5o1nHw4Y1mjWWkFuQAonks8bgYPvHqU1nO5/svhNLe0dC+hGKzWZiUHwR9rXTRLhdTDoaW17pQ44KXesFEECHZ+FR3F+r7XUyLBQ3g9N6wVaM6rD3prVlOUOuud2CZ40DqCZcN6g0nK42HDwUV39YqLA1X1jVlIcy7Yp76DwrznfYJPsUqxBil+PZPizPpBMOI=
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1e8e3e1e-984a-4508-8d4e-08d6ccb7f3b0
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Apr 2019 15:32:55.7287 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2283
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/MUYMRTZ-xzgY_6PJ58_Y6eHYVvQ>
Subject: Re: [tsvwg] travel funds for ietf for the next SCE talk?
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: Mon, 29 Apr 2019 15:33:03 -0000

Hi Dave,=0A=
=0A=
Thanks for bring this work to the IETF. Yes, I would also like to encourage=
 you to discuss your proposal in TSVWG using the mailing list and eventuall=
y present this work at the next TSVWG meeting. However, there is not requir=
ed to participate in-person. We frequently have remote presentations and fr=
om my experience that works well. I=92m sure the TSVWG chairs can further a=
dvise you on this.=0A=
=0A=
Cheers=0A=
=0A=
Magnus Westerlund=0A=
=0A=
=0A=
=0A=
On 2019-04-28 15:54, Dave Taht wrote:=0A=
> Several members of the open source "bufferbloat.net" group do=0A=
> regularly participate in ietf mailing lists and remote meetings, but=0A=
> it is rare that any of us=0A=
> can actually afford to attend IETF. In fact, we've had no travel=0A=
> budget for 3 years running. I'd mostly reduced my involvement to BABEL=0A=
> after the AQM wg closed, and that remotely only.=0A=
>=0A=
> This past IETF, we had to hold a bake sale on the bloat mailing list=0A=
> as well as melt all my credit cards in order to get our new SCE "Some=0A=
> Congestion Experienced" AQM concept in front of the tsvwg and iccrg=0A=
> working groups in contrast to the cablelabs dualpi proposal.=0A=
>=0A=
> (if anyone cares, the TSVWG talk and slides are here:=0A=
> https://www.youtube.com/watch?v=3DJQmWyr0JDJM&t=3D1h3m50s ) -=0A=
>=0A=
> The controversy in the open source community, covered here:=0A=
> https://lwn.net/Articles/783673/=0A=
>=0A=
> We've been *very strongly encouraged* to present again at the upcoming=0A=
> ietf in montreal, but I'm now in no position to sponsor the 2-3 core=0A=
> people again that need to present the follow-on results in the 5 or so=0A=
> related wgs. Is there an org, a fund, a means, a way, to get a bunch=0A=
> of rather poor, but innovative, open source devs and theorist, out=0A=
> there, that we can apply to? raise the ~9k needed? isoc? Something?=0A=
>=0A=
> (and if it were possible i'd rather like to have what I had had to=0A=
> spend back, so I can pour it into recreating a network testbed for=0A=
> this work. I'm not planning to attend, myself. The one trip alone=0A=
> wiped out ecn-sane's budget for the year)=0A=
>=0A=
=0A=
-- =0A=
=0A=
Magnus Westerlund =0A=
=0A=
----------------------------------------------------------------------=0A=
Network Architecture & Protocols, Ericsson Research=0A=
----------------------------------------------------------------------=0A=
Ericsson AB                 | Phone  +46 10 7148287=0A=
Torshamnsgatan 23           | Mobile +46 73 0949079=0A=
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com=0A=
----------------------------------------------------------------------=0A=
=0A=

