[tcpm] Re: draft-ietf-tcpm-rst-diagnostic-payload: reason-code Size and Allocation Policy

Michael Tuexen <michael.tuexen@lurchi.franken.de> Wed, 22 April 2026 16:49 UTC

Return-Path: <michael.tuexen@lurchi.franken.de>
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 5625EE0F89CA; Wed, 22 Apr 2026 09:49:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776876549; bh=A+4SCtA6hlYuvoEtWCfs4wjxxrysYhvdfBee9WSY3sY=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=mnrMI0O2dLurWgIHTyw+EfeON2QpXymF8m7EZMTOZlNxL8MFsQ5VZ2PUljtR38lKM zEm5K3MyXvbsnkvQWSxH83L1vRlDbx3pHaqX1XsF5/lgr8ogyzJOh3IJNXi+wMwH2V 3Q1o8yE4Gujf8CGa5YplkcsXbidFEZpZxSzZIH24=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
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 TYRcZzknnrUx; Wed, 22 Apr 2026 09:49:08 -0700 (PDT)
Received: from drew.franken.de (unknown [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 67680E0F86A6; Wed, 22 Apr 2026 09:46:34 -0700 (PDT)
Received: from smtpclient.apple (unknown [IPv6:2a02:8109:1101:be00:9cb7:f6c2:1c71:65d]) (Authenticated sender: lurchi) by drew.franken.de (Postfix) with ESMTPSA id 57283721E2806; Wed, 22 Apr 2026 18:46:16 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
From: Michael Tuexen <michael.tuexen@lurchi.franken.de>
In-Reply-To: <MR0P264MB6764850CBCD9AA00D79BF9A9882D2@MR0P264MB6764.FRAP264.PROD.OUTLOOK.COM>
Date: Wed, 22 Apr 2026 18:46:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <276FCA20-6C41-4B34-B4F7-5333F7F13678@lurchi.franken.de>
References: <MR0P264MB6764850CBCD9AA00D79BF9A9882D2@MR0P264MB6764.FRAP264.PROD.OUTLOOK.COM>
To: mohamed.boucadair@orange.com
X-Mailer: Apple Mail (2.3864.500.181)
Message-ID-Hash: J57HB73UD2HIKMT6SLHD6QOI7KNCNS3E
X-Message-ID-Hash: J57HB73UD2HIKMT6SLHD6QOI7KNCNS3E
X-MailFrom: michael.tuexen@lurchi.franken.de
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@ietf.org Extensions" <tcpm@ietf.org>, "draft-ietf-tcpm-rst-diagnostic-payload@ietf.org" <draft-ietf-tcpm-rst-diagnostic-payload@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [tcpm] Re: draft-ietf-tcpm-rst-diagnostic-payload: reason-code Size and Allocation Policy
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/-uwBGFfXqy5NOmIF0WZj7EUOrYg>
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>


> On 22. Apr 2026, at 17:47, mohamed.boucadair@orange.com wrote:
> 
> Hi all,
>  The reason-code is currently encoded in 32 bits with the full range being governed by Expert Review policy. The main
Just to be precise: the reason code is a 16-bit entity.
> motivation was to make sure a registered code is technically sound. In the meantime, we would like to encourage codes to be registered. Registering a reason-code allows to avoid using pen-specific codes.
>  Please let us know if you think that using an FCFS policy would be sufficient or if reserving an FCFS range is needed. Also, we are interested in feedback on size.Cheers,
I plan to implement sending the diagnostic information for kernel triggered RST segments in
FreeBSD over the weekend at a hackathon. So hopefully, I can provide some feedback next week.

Best regards
Michael (as an individual).
> Med (no AD fez)
> ____________________________________________________________________________________________________________
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.
> _______________________________________________
> tcpm mailing list -- tcpm@ietf.org
> To unsubscribe send an email to tcpm-leave@ietf.org