Re: [tcpm] Meeting Notes // TCP silent close issue

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Sun, 14 November 2021 11:07 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 BB17A3A03AA for <tcpm@ietfa.amsl.com>; Sun, 14 Nov 2021 03:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=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 WotYU-x218LL for <tcpm@ietfa.amsl.com>; Sun, 14 Nov 2021 03:07:34 -0800 (PST)
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 570D13A033F for <tcpm@ietf.org>; Sun, 14 Nov 2021 03:07:34 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.hs-esslingen.de (Postfix) with ESMTP id C3EBA25A2D; Sun, 14 Nov 2021 12:07:31 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1636888051; bh=Yfu0Gp71OlowAnXV2+n7EsO8fFeBo9Hk0AUn2KYu96Q=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=nspQLAe/MHlYDozzg64mfmGO9oMO3Xc0wsSIw334GPTOo7DdOkkVUiGHkMCJZHWou A6i1o3U4EwGm3gBL7pMXvuUoxooVkoEr06gFpEcYpINqlBSQGFjv9Is8GaBEIg9Yiy Qi4CQvLBOWwTYKzRHsASqxURES/Vim28UQhuZ3l0=
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 yYjRTFcNAo6R; Sun, 14 Nov 2021 12:07:30 +0100 (CET)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (rznt8202.hs-esslingen.de [134.108.48.165]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS; Sun, 14 Nov 2021 12:07:30 +0100 (CET)
Received: from rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) by rznt8202.rznt.rzdir.fht-esslingen.de (134.108.48.165) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.14; Sun, 14 Nov 2021 12:07:29 +0100
Received: from rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0]) by rznt8202.rznt.rzdir.fht-esslingen.de ([fe80::aca4:171a:3ee1:57e0%3]) with mapi id 15.01.2176.014; Sun, 14 Nov 2021 12:07:29 +0100
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: "touch@strayalpha.com" <touch@strayalpha.com>, Michael Tuexen <tuexen@fh-muenster.de>
CC: Extensions <tcpm@ietf.org>
Thread-Topic: [tcpm] Meeting Notes // TCP silent close issue
Thread-Index: AQHX1+aV9sWC/sevcUaWR/BglCX56awAKBEAgAF99ACAATVRMA==
Date: Sun, 14 Nov 2021 11:07:29 +0000
Message-ID: <3b11cedb842b4103ad9268a1cec48aa2@hs-esslingen.de>
References: <96A7D17B-D8EC-4724-8E2B-532FEDD3C4B8@fh-muenster.de> <C8B8411B-9332-4A0C-BDF6-C440EC391408@strayalpha.com> <EFEFC910-0859-454E-B988-C41ED5C22B1D@fh-muenster.de> <C9AF93C3-8A6C-4F9A-B6E7-3098B2727EBF@strayalpha.com>
In-Reply-To: <C9AF93C3-8A6C-4F9A-B6E7-3098B2727EBF@strayalpha.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [134.108.140.248]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0030_01D7D950.31B36350"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/ThKS484h-6I7kU_AkpE2WujA_zc>
Subject: Re: [tcpm] Meeting Notes // TCP silent close issue
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: Sun, 14 Nov 2021 11:07:40 -0000

Hi Joe,

 

At least since I chair TCPM (i.e., since 2011), there has been no formal requirement of list discussion prior to a presentation at the very end of the TCPM meeting. This in particular applies to any TCP topic related to running code.

 

My impression is that in many cases such talks at the end of the TCPM slot have triggered interesting follow-up discussions.

 

In over 10 years I only recall some very few cases in which such presenations clearly were a waste of time (yes, the chairs indeed have made mistakes!).

 

So, all in all, I believe that the relatively liberal policy of accepting presentations has served us well. In a nutshell, my own philosophy has always been: Be liberal in accepting presentation requests, and be conservative in sending WG adoption calls…

 

Of course, such policies can be changed in future. There will be opportunities, soon-ish…

 

Michael

 

 

From: tcpm <tcpm-bounces@ietf.org> On Behalf Of touch@strayalpha.com
Sent: Saturday, November 13, 2021 6:24 PM
To: Michael Tuexen <tuexen@fh-muenster.de>
Cc: Extensions <tcpm@ietf.org>
Subject: Re: [tcpm] Meeting Notes // TCP silent close issue

 

On the issue below:

 

On Nov 12, 2021, at 10:37 AM, tuexen@fh-muenster.de <mailto:tuexen@fh-muenster.de>  wrote:

 

(Incidentally, a question to the chair: aren’t topics with meeting times slots supposed to have at least been discussed on the list or drafted?)

Just on this question:

If time permits, we accept presentations without IDs if we think that having a discussion
in TCPM makes sense. In this particular case, the presentation was the last one and we used
only the remaining meeting time.

 

Without IDs sure, but without a single mention on the list?





In my experience a presentation in the meeting is triggering a discussion much easier than
just a post to the mailing list.

 

It trades a limited resource (meeting time) for the presenter’s effort; that seems the wrong optimization to me.

 

FWIW, it didn’t take all that long for me to summarize the issue, the proposed approach, *and* a solution not presented to the list.

 

Joe