Re: [tcpm] [tsvwg] New Version Notification for draft-grimes-tcpm-tcpsce-00.txt

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Thu, 25 July 2019 20:06 UTC

Return-Path: <Michael.Scharf@hs-esslingen.de>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 294851201F8; Thu, 25 Jul 2019 13:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hs-esslingen.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 amlGAIG2fagu; Thu, 25 Jul 2019 13:06:33 -0700 (PDT)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de [134.108.32.78]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14CD21201EC; Thu, 25 Jul 2019 13:06:32 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id 2D20625A19; Thu, 25 Jul 2019 22:06:31 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1564085191; bh=pegGRKVy25CpdGeQfMzAjiiVHOvtnj+f3DNfiESXlF0=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=bvYKTB60WDUi+iWCgSU+e6KcjIehPsMmqt9znY80m9f105V/kmXgnOno21/OAoNSG lUcMHUAofRH6w9n8xuM0Wqrc1pe+22WxcN6ZCEx9KllZjEnjoVX0SB8cTAHvZtmJ/l nmql1NVci5kl8/v9pVMeUFj13i/bfCMwhIGZcS7k=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([127.0.0.1]) by localhost (hs-esslingen.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILVT4qYFes99; Thu, 25 Jul 2019 22:06:30 +0200 (CEST)
Received: from rznt8102.rznt.rzdir.fht-esslingen.de (rznt8102.rznt.rzdir.fht-esslingen.de [134.108.29.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Thu, 25 Jul 2019 22:06:30 +0200 (CEST)
Received: from RZNT8114.rznt.rzdir.fht-esslingen.de ([169.254.3.191]) by rznt8102.rznt.rzdir.fht-esslingen.de ([fe80::f977:d5e6:6b09:56ac%10]) with mapi id 14.03.0468.000; Thu, 25 Jul 2019 22:06:29 +0200
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: Bob Briscoe <in@bobbriscoe.net>, Jonathan Morton <chromatix99@gmail.com>
CC: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, "tcpm@ietf.org" <tcpm@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] [tcpm] New Version Notification for draft-grimes-tcpm-tcpsce-00.txt
Thread-Index: AQHVQxiePohoWEl9KE+uYb+QgVUmZKbbwGLw
Date: Thu, 25 Jul 2019 20:06:29 +0000
Message-ID: <6EC6417807D9754DA64F3087E2E2E03E2D3C9D1C@rznt8114.rznt.rzdir.fht-esslingen.de>
References: <364514D5-07F2-4388-A2CD-35ED1AE38405@akamai.com> <17B33B39-D25A-432C-9037-3A4835CCC0E1@gmail.com> <AM4PR07MB345956F52D92759F24FFAA13B9F50@AM4PR07MB3459.eurprd07.prod.outlook.com> <52F85CFC-B7CF-4C7A-88B8-AE0879B3CCFE@gmail.com> <AM4PR07MB3459B471C4D7ADAE4CF713F3B9F60@AM4PR07MB3459.eurprd07.prod.outlook.com> <D231681B-1E57-44E1-992A-E8CC423926B6@akamai.com> <AM4PR07MB34592A10E2625C2C32B9893EB9F00@AM4PR07MB3459.eurprd07.prod.outlook.com> <A6F05DD3-D276-4893-9B15-F48E3018A129@gmx.de> <AM4PR07MB3459487C8A79B1152E132CE1B9CB0@AM4PR07MB3459.eurprd07.prod.outlook.com> <87ef2myqzv.fsf@taht.net> <a85d38ba-98ac-e43e-7610-658f4d03e0 f4@mti-systems.com> <CE03DB3D7B45C245BCA0D243277949363062879C@MX307CL04.corp.emc.com> <803D9CA8-220E-4F98-9B8E-6CE2916C3100@gmail.com> <1468777263.2671021.1563730029999@mail.yahoo.com> <6EC6417807D9754DA64F3087E2E2E03E2D3C0A43@rznt8114.rznt.rzdir.fht-esslingen.de> <D9D3805B-A277-414B-9268-170C2DD56D1C@gmail.com> <b60ae321-5c51-fa09-25fa-29e5a7e804f7@bobbriscoe.net>
In-Reply-To: <b60ae321-5c51-fa09-25fa-29e5a7e804f7@bobbriscoe.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [134.108.29.249]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/Su7gpfVmY3W1JVPlwrBmXtSokAQ>
Subject: Re: [tcpm] [tsvwg] New Version Notification for draft-grimes-tcpm-tcpsce-00.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jul 2019 20:06:35 -0000

> > I do however note that SYN is described as the most important packet to
> protect with ECN, and this is of course sent before AccECN negotiation has
> completed.  Further, if the SYN-ACK then indicates that AccECN is *not*
> supported by the remote end - which would be the case for both an SCE
> endpoint and any conventional one - a conservative IW of 1 segment SHOULD
> be conservatively selected, with no modification for the increasingly common
> IW10 case (the default for current versions of Linux).  This incurs a flow
> completion time delay of approximately 3 RTTs, which could be perceptible to
> end users.
> The draft explains: the reduction to IW1 is in the client to server
> direction. It cites measurement studies that show it's unusual to get >1
> initial packet in that direction anyway. And the reduction to 1 is only
> a SHOULD. An implementation could choose 2 for instance.
> 
> When new to the IETF, it's even more important to read the draft before
> sending critique (cos you won't have heard all the previous discussion).
> Otherwise it burns busy people's time on the list unnecessarily.

I'd like to remind people that comments from people new to the IETF _are_ welcome in TCPM and elsewhere in the IETF.

Michael (as chair)