[tcpm] Working group acceptance of draft-touch-tcpm-2140bis-06 targeting informational status

"Scharf, Michael" <Michael.Scharf@hs-esslingen.de> Wed, 06 March 2019 22:48 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 0210F131065 for <tcpm@ietfa.amsl.com>; Wed, 6 Mar 2019 14:48:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
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, RCVD_IN_DNSWL_NONE=-0.0001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id leE7pS_6E5Cp for <tcpm@ietfa.amsl.com>; Wed, 6 Mar 2019 14:48:30 -0800 (PST)
Received: from mail.hs-esslingen.de (mail.hs-esslingen.de []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE043130F70 for <tcpm@ietf.org>; Wed, 6 Mar 2019 14:48:29 -0800 (PST)
Received: from localhost (localhost.localdomain []) by mail.hs-esslingen.de (Postfix) with ESMTP id 1809725A13 for <tcpm@ietf.org>; Wed, 6 Mar 2019 23:48:28 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hs-esslingen.de; s=mail; t=1551912508; bh=laSZk9WnaG0lfuF4eQ4JuDbCm6BMy6OYg+rd7RtFJNc=; h=From:To:Subject:Date:From; b=pRzd92+fRyWCWA6EEbOJo5yVMio2QEmN7lmiG5UpjgHSanf4UuufhuLRsC+5wrEZh pYT70ybd0sUnCT7SVTUcMWyOkOHtaT9NU6iuss3L94sv8PczYmGyeH69u8NRy1Y22M u8UEh1PoIPaqJJqy8Em4o42AwkIRXwWnKARI7SyM=
X-Virus-Scanned: by amavisd-new-2.7.1 (20120429) (Debian) at hs-esslingen.de
Received: from mail.hs-esslingen.de ([]) by localhost (hs-esslingen.de []) (amavisd-new, port 10024) with ESMTP id VXbKWZ1TePau for <tcpm@ietf.org>; Wed, 6 Mar 2019 23:48:27 +0100 (CET)
Received: from rznt8101.rznt.rzdir.fht-esslingen.de (rznt8101.rznt.rzdir.fht-esslingen.de []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail.hs-esslingen.de (Postfix) with ESMTPS for <tcpm@ietf.org>; Wed, 6 Mar 2019 23:48:27 +0100 (CET)
Received: from RZNT8114.rznt.rzdir.fht-esslingen.de ([]) by rznt8101.rznt.rzdir.fht-esslingen.de ([fe80::bd73:d6a9:24d7:95f1%10]) with mapi id 14.03.0415.000; Wed, 6 Mar 2019 23:48:26 +0100
From: "Scharf, Michael" <Michael.Scharf@hs-esslingen.de>
To: "tcpm@ietf.org" <tcpm@ietf.org>
Thread-Topic: Working group acceptance of draft-touch-tcpm-2140bis-06 targeting informational status
Thread-Index: AQHU1G616iHOJHkpoEO6XOB3g3fkFQ==
Date: Wed, 06 Mar 2019 22:48:26 +0000
Message-ID: <6EC6417807D9754DA64F3087E2E2E03E2D24EEA4@rznt8114.rznt.rzdir.fht-esslingen.de>
Accept-Language: de-DE, en-US
Content-Language: de-DE
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/Oc-8qGMPxH3jphjDfr1PNWo3U-w>
Subject: [tcpm] Working group acceptance of draft-touch-tcpm-2140bis-06 targeting informational status
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: Wed, 06 Mar 2019 22:48:34 -0000

Hi all,

The document draft-touch-tcpm-2140bis has been discussed quite a bit in TCPM. One question has been the status (BCP or INFO). The version draft-touch-tcpm-2140bis-06 explicitly targets informational status and plans to obsolete RFC 2140 (which is informational, too).

The intention of this e-mail is to confirm that draft-touch-tcpm-2140bis-06 should be adopted as informational TCPM working group item, i.e., that a new item should be added to the TCPM charter:

  Nov. 2019  Submit document on TCP Control Block Interdependence to the IESG for publication as Informational RFC 

The adoption call runs on the TCPM mailing list until March 22. Please let us know if you support adoption of the document, or if there are any concerns.

Best regards

(TCPM co-chair)

-------- Forwarded Message --------
From: tcpm [mailto:tcpm-bounces@ietf.org] On Behalf Of Joe Touch
Sent: Friday, January 4, 2019 5:52 PM
To: tcpm@ietf.org
Subject: [tcpm] Fwd: New Version Notification for draft-touch-tcpm-2140bis-06.txt

FYI - 
This version:
    - obsoletes 2140
    - says so in the abstract and intro
    - includes a "changes from 2140" section summarizing the differences
Note that the earlier versions did cite 2140, but did not as directly indicate that this is intended as its replacement.

-------- Forwarded Message -------- 
New Version Notification for draft-touch-tcpm-2140bis-06.txt
Fri, 04 Jan 2019 08:49:25 -0800
Safiqul Islam <safiquli@ifi.uio.no>, Michael Welzl <michawe@ifi.uio.no>, Joseph Touch <touch@strayalpha.com>, Joe Touch <touch@strayalpha.com>

A new version of I-D, draft-touch-tcpm-2140bis-06.txt
has been successfully submitted by Joe Touch and posted to the
IETF repository.

Name: draft-touch-tcpm-2140bis
Revision: 06
Title: TCP Control Block Interdependence
Document date: 2019-01-04
Group: Individual Submission
Pages: 22
URL: https://www.ietf.org/internet-drafts/draft-touch-tcpm-2140bis-06.txt
Status: https://datatracker.ietf.org/doc/draft-touch-tcpm-2140bis/
Htmlized: https://tools.ietf.org/html/draft-touch-tcpm-2140bis-06
Htmlized: https://datatracker.ietf.org/doc/html/draft-touch-tcpm-2140bis
Diff: https://www.ietf.org/rfcdiff?url2=draft-touch-tcpm-2140bis-06

This memo updates and replaces RFC 2140's description of
interdependent TCP control blocks, in which part of the TCP state is
shared among similar concurrent or consecutive connections. TCP
state includes a combination of parameters, such as connection
state, current round-trip time estimates, congestion control
information, and process information. Most of this state is
maintained on a per-connection basis in the TCP Control Block (TCB),
but implementations can (and do) share certain TCB information
across connections to the same host. Such sharing is intended to
improve overall transient transport performance, while maintaining
backward-compatibility with existing implementations. The sharing
described herein is limited to only the TCB initialization and so
has no effect on the long-term behavior of TCP after a connection
has been established.

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