RFC 9040 on TCP Control Block Interdependence

rfc-editor@rfc-editor.org Wed, 28 July 2021 05:51 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 795303A1E52; Tue, 27 Jul 2021 22:51:43 -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 S_h2pBK-4rAv; Tue, 27 Jul 2021 22:51:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F4143A1E53; Tue, 27 Jul 2021 22:51:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CAC44F4070A; Tue, 27 Jul 2021 22:51:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkwNDAgb24gVENQIENvbnRyb2wgQmxvY2sgSW50ZXJkZXBlbmRlbmNl?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tcpm@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210728055115.CAC44F4070A@rfc-editor.org>
Date: Tue, 27 Jul 2021 22:51:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/fxGRvlUdUpv2d45-J8vFS67m8Ds>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jul 2021 05:51:44 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9040

        Title:      TCP Control Block Interdependence 
        Author:     J. Touch,
                    M. Welzl,
                    S. Islam
        Status:     Informational
        Stream:     IETF
        Date:       July 2021
        Mailbox:    touch@strayalpha.com,
                    michawe@ifi.uio.no,
                    safiquli@ifi.uio.no
        Pages:      29
        Obsoletes:  RFC 2140

        I-D Tag:    draft-ietf-tcpm-2140bis-11.txt

        URL:        https://www.rfc-editor.org/info/rfc9040

        DOI:        10.17487/RFC9040

This memo provides guidance to TCP implementers that is intended to
help improve connection convergence to steady-state operation without
affecting interoperability. It updates and replaces RFC 2140's
description of sharing TCP state, as typically represented in TCP
Control Blocks, among similar concurrent or consecutive connections.

This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC