IETF Logo Mail Archive

Re: [tsvwg] L4S status tracking

Wesley Eddy <wes@mti-systems.com> Mon, 09 September 2019 19:08 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22E01200F5 for <tsvwg@ietfa.amsl.com>; Mon, 9 Sep 2019 12:08:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 vuIpaUyt8yMr for <tsvwg@ietfa.amsl.com>; Mon, 9 Sep 2019 12:08:54 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 BD540120020 for <tsvwg@ietf.org>; Mon, 9 Sep 2019 12:08:54 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id x134so14254781qkb.0 for <tsvwg@ietf.org>; Mon, 09 Sep 2019 12:08:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mti-systems-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=7x0zxVNl8NMas7TI/LY6Ka0OWhiOOQlKx5bvFrjAqmI=; b=LNfmprd4zlM1+HgmiZbQ9qg/tpzH4FTG5UEaeQxdaqhYn7M/eb1bWGvBkPXlwuko0g S/6R7gHgsRz/fmZynxu5dKoPu01VDrLALKD1B3XTk+wxTXj2Ant1qr98cvznYpJ+Ql7o BI4hwxvlPsR4V8qWLcbfIXTgSKXxMQmrSu8AGchfMqvECwdWrYIJ0GSIFgCcKofgaOzJ 4xAPXEZQJIBAG7ArWjl540f2UEmfOy3FHtIEpMmxEcsYRLYYk4+4usbwetW2bfF+ynhR FXdlVfe88qCPVw+96FtMunYKBbB/EQvsawkeiaIP2ovavV3ljqFjLQ7GfpOTSTwpVI5Z aYag==
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; bh=7x0zxVNl8NMas7TI/LY6Ka0OWhiOOQlKx5bvFrjAqmI=; b=cEfpFKp44zyPhNO1iyW5dnCAnQPWljYRBzXD0U9mA3eQOxHq4dd8SoZLSV1GJeIMbp lNT68FZfIO5cLRi9oSJgdViSUVezWn88qkLgkM22QG2Zv5IGBaewlyp+ct694Ge4MiGy f6K5eUoYZuykzBNCGxl0Df+tIJs1/6T/3paZW/gyBQKX5Li+zHkbrKRQkN1Og17wdHnL g1AfE8NG2I2KkQIz6DVt+TOvPKIhg+KSdHaVNJARryOeE0nmJTif0MzXpY44hHuqSKEN L8E6B5wlTFBPJ3tnbGee9qBqEEK+gGJPohmyAP0ceoSW22jM0RMudTrxMi5/uJwDygoR sYYQ==
X-Gm-Message-State: APjAAAV4ctedEZCiIIKu/5VbFS+e2gk8mc/PX7PnysrGm/ldx9A3uldT RpFT5f7JztuW3LdIaLK3hxHHpg==
X-Google-Smtp-Source: APXvYqzMi4X2kZsXJhf+V+BgpldmQXN6fmc6ubUVmRXZ/fl6k+jZI5OagF8/Dl9eOQA05fSY1c/L2A==
X-Received: by 2002:a37:4b54:: with SMTP id y81mr3492633qka.344.1568056133827; Mon, 09 Sep 2019 12:08:53 -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 y58sm2390938qta.1.2019.09.09.12.08.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Sep 2019 12:08:53 -0700 (PDT)
To: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
References: <8321f975-dfe7-694c-b5cc-09fa371b9b61@mti-systems.com> <6EC6417807D9754DA64F3087E2E2E03E2D40EB7E@rznt8114.rznt.rzdir.fht-esslingen.de>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <14d35e2f-f6c3-8ca8-0567-79cd19a86de4@mti-systems.com>
Date: Mon, 09 Sep 2019 15:08:51 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <6EC6417807D9754DA64F3087E2E2E03E2D40EB7E@rznt8114.rznt.rzdir.fht-esslingen.de>
Content-Type: multipart/alternative; boundary="------------4D38955E1FDC954BC93E9083"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/QfFXm5pSO0zr5ypeBt6xpRMwrrA>
Subject: Re: [tsvwg] L4S status tracking
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, 09 Sep 2019 19:08:57 -0000

On 8/23/2019 10:01 AM, Scharf, Michael wrote:
>
> Hi Wes,
>
> I’d like to add a smaller item that is mostly editorial and can 
> hopefully be sorted just out by re-wording, albeit it may require a 
> careful analysis of all documents.
>
> As already noted in 
> https://mailarchive.ietf.org/arch/msg/tsvwg/zZkYZKF-hDvWO3I5MudwpNkKyHY 
> , I object to the terms „traditional TCP“ and also „classic TCP“ or 
> „legacy“ TCP when referring to a TCP implementation according to IETF 
> standards-track RFCs.
>
>  ...
>

Hello Michael, thanks for noting this.  I've added a ticket in the issue 
tracker pointing back to this thread.

v2.23.0 | Report a Bug | By Email