[tcpm] Re: New Internet-Draft: The Session Recovery Option (SRO) for TCP (draft-cmcc-tcp-sro)

"lluozy@yeah.net" <lluozy@yeah.net> Thu, 13 August 2026 09:28 UTC

Return-Path: <lluozy@yeah.net>
X-Original-To: tcpm@mail2.ietf.org
Delivered-To: tcpm@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8597A1290CD5B for <tcpm@mail2.ietf.org>; Thu, 13 Aug 2026 02:28:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1786613293; bh=ZTAPloMZtMGtXRYfKvA/U+ZKBgu8aVpH77vOdwi204o=; h=Date:From:To:Cc:Subject:References; b=WZBzhmcdeSO4XmFzWfakVyv2a0tp993/EhK7qxfvjdTjobi+PArBQQv7mitL1TlGm GDppR6X0aqFAJpVwfRy8K2fBd1TS9WKsaWAQuk9/l8cqjZkmGOFT/oPDii/iYGJ4OE Z18mxsxjf9VZZaJGL1ShnLwKVEeMouAP5pzkshMA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=yeah.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJ21cR1kCIqi for <tcpm@mail2.ietf.org>; Thu, 13 Aug 2026 02:28:10 -0700 (PDT)
Received: from mail-m16.yeah.net (mail-m16.yeah.net [1.95.21.16]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CF2191290CD54 for <tcpm@ietf.org>; Thu, 13 Aug 2026 02:28:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yeah.net; s=s110527; h=Date:From:To:Subject:Mime-Version:Message-ID: Content-Type; bh=7+L4kbDNkC/6yxrTiqiY7Jx5XZ90zIRjA1fk9Km/+Fk=; b=FFXfqm4O7bhfCbzv+pLFEdUhGVWbSfLOvFeRbqTZxhapH97OH6OY6WsMXhgaE6 PgKACPzmNr7ULQ0f7PWG1+knRBpAqJMzFSsZYpilpiprkyMhB0bHkqWSNdfjwMc2 8K653gu5kcWXiwIbXI1zxKadEsEUVXjhYYgfZiBD89+HU=
Received: from LAPTOP-OLN30EF1 (unknown []) by gzsmtp3 (Coremail) with UTF8SMTPA id M88vCgA3H0odjn1qZNgoBg--.4303S2; Thu, 13 Aug 2026 17:27:58 +0800 (CST)
Date: Thu, 13 Aug 2026 17:27:50 +0800
From: "lluozy@yeah.net" <lluozy@yeah.net>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>
References: <2026081210244682293618@yeah.net>, <24148AAF-FFB3-4C94-9D1F-C5BC3EEBE506@lurchi.franken.de>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.563[cn]
Mime-Version: 1.0
Message-ID: <202608131727497801442@yeah.net>
Content-Type: multipart/alternative; boundary="----=_001_NextPart043055712306_=----"
X-CM-TRANSID: M88vCgA3H0odjn1qZNgoBg--.4303S2
X-Coremail-Antispam: 1Uf129KBjvJXoWxAr18CryUtr4rKw43GrW7Arb_yoW5Cw1UpF s5t34UKFs5tFyfWw4kZw48Xryru395JrW5GFn0qry7Aas8JF10vr1Ikw1Yva4jkr15Cw4Y vr4j93Z8XaykZFJanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x0zRUUUUUUUUU=
X-Originating-IP: [223.108.79.99]
X-CM-SenderInfo: poox063161vtnkoqv3/1tbiOB+kRGp9jh80IQAA3U
Message-ID-Hash: WHZJZIQDMQTABE6SR3WJGLALWUHSRSTF
X-Message-ID-Hash: WHZJZIQDMQTABE6SR3WJGLALWUHSRSTF
X-MailFrom: lluozy@yeah.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tcpm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tcpm <tcpm@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tcpm] Re: New Internet-Draft: The Session Recovery Option (SRO) for TCP (draft-cmcc-tcp-sro)
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/D24XX8cwlTYGtEoAIyCM32yna9A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Owner: <mailto:tcpm-owner@ietf.org>
List-Post: <mailto:tcpm@ietf.org>
List-Subscribe: <mailto:tcpm-join@ietf.org>
List-Unsubscribe: <mailto:tcpm-leave@ietf.org>

We have uploaded revision-01 of draft-cmcc-tcp-sro, available at:
https://datatracker.ietf.org/doc/draft-cmcc-tcp-sro/

This revision incorporates the comments received on the list:

SNAT and LB are expanded on first use, with RFC 2663 added as an
informative reference.
The two option kinds are consolidated into a single kind.
The MTU consideration in Section 4.2 is removed.

We thank Mike Heard and Michael Tuexen for their review comments.

Any further comments are welcome.

Best regards,
Zhaoyu Luo

From: Michael Tuexen
Date: 2026-08-12 19:11
To: lluozy
CC: tcpm
Subject: Re: [tcpm] New Internet-Draft: The Session Recovery Option (SRO) for TCP (draft-cmcc-tcp-sro)
 
 
> On 12. Aug 2026, at 04:24, lluozy@yeah.net wrote:
> 
> Hello TCPM,
> I would like to announce a new Internet-Draft that may be of interest to this working group.
> draft-cmcc-tcp-sro: "The Session Recovery Option (SRO) for TCP"
> https://datatracker.ietf.org/doc/draft-cmcc-tcp-sro/
> SNAT and LB are among the most common network services, yet their reliability still depends on HA pairs or clusters, which are closed and complex to implement and scale, especially in NFV service clusters in cloud environments. We have been working on a novel approach: the network node backs up the session state to the client or server side. This improves the reliability of LB and SNAT services and greatly simplifies cluster implementation; even a single serving node can recover a session after a failure. This approach is described in a related Internet-Draft, draft-cmcc-asrp (the Available Session Recovery Protocol): https://datatracker.ietf.org/doc/draft-cmcc-asrp/
> In this approach, one key challenge is locating the endpoint that holds the session backup. SRO addresses this in the most direct way: during the TCP handshake, the client and the server exchange small identifiers (4 octets by default); when a session must be recovered, an endpoint conveys the identifier of the peer on timeout retransmission, and the network node locates the backup holder precisely. Other mechanisms exist, but SRO is the simplest and most direct one.
> SRO is deliberately lightweight:
>     • It is carried only in the SYN, the SYN-ACK, and segments sent on timeout retransmission; normal data segments carry no overhead.
>     • Clients that do not support SRO are fully compatible: they simply do not include the option, and session recovery falls back to existing mechanisms.
> We would appreciate any review comments, and would be happy to present the draft at a TCPM session if the chairs consider it useful.
Hi,
 
two comments:
1. Isn't using one option kind good enough?
2. TCP is a byte stream, so a retransmission does not need to have
   the same byte boundaries. Therefore there should be no MTU issue
   when retransmitting with an additional option (first bullet point
   in Section 4.2).
 
Best regards
Michael (as an individual)
> Best regards,
> Zhaoyu Luo
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org