[TLS] Re: WG Status: -super-jumbo-record-limit
Sean Turner <sean@sn3rd.com> Wed, 15 April 2026 15:56 UTC
Return-Path: <sean@sn3rd.com>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 8600DDCDEF4D for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 08:56:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776268580; bh=pWbdYQZBEHPukRwBr00uxy4FDDKoDWFfZ0LVmn+c9wc=; h=From:Subject:Date:References:To:In-Reply-To; b=P6Pxp01wuFjfN+m13zoxHyb+Y9e/u8LSBFMOXrTkGSVPCh5063TUIGoV5Phqe6kPM /hx32BBtgFydg9YBcGoxBzhiub9LG/lpBPPcfAdbH7RfDWlLA7nUpjikcjLpESyKe4 +c+QqAUga+6f9G6YrjZ0LGSs2zcIBrja9jZBwd2g=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 7mu5dNBRj8X8 for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 08:56:19 -0700 (PDT)
Received: from mail-qv1-xf44.google.com (mail-qv1-xf44.google.com [IPv6:2607:f8b0:4864:20::f44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id F1268DCDED20 for <tls@ietf.org>; Wed, 15 Apr 2026 08:54:00 -0700 (PDT)
Received: by mail-qv1-xf44.google.com with SMTP id 6a1803df08f44-899d6b7b073so70588026d6.2 for <tls@ietf.org>; Wed, 15 Apr 2026 08:54:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; t=1776268440; x=1776873240; darn=ietf.org; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:from:to:cc:subject:date:message-id :reply-to; bh=pWbdYQZBEHPukRwBr00uxy4FDDKoDWFfZ0LVmn+c9wc=; b=HvsAl2PhduU58Gh+u+uq5fBnrAHGdYDvoy0Lpc5f18Q6dZCBZxJmXpafwBjCfYvKWh ytlxbPyXy/2PIcpcrFbp6C2a4sK0ivqEGKd7jjWU164Fv0QcAm58B/5yMEuR3Uje111X 5zyTfaSCbO/nS+ZN7rzYIPkZLLD8yjpWDTIp0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776268440; x=1776873240; h=message-id:in-reply-to:to:references:date:subject:mime-version :content-transfer-encoding:from:x-gm-gg:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=pWbdYQZBEHPukRwBr00uxy4FDDKoDWFfZ0LVmn+c9wc=; b=dHpxYzuYQRa9vcoZQLvg/JgxdZ6N11F7o4qlAmf76qa4kyfFcJ0KOS03RNv9h4Qslt pO0JcBnEVxXSE5L0iI27mrkRnwRxwnb4k45WLZzrM4rtqb9BCRPNE2Vh8zzaQsFCquGD NdoVGWl+ntwS1OA9SXSQdTu6yhlH4MAo4VDbMiRYCb2wPso5x+Y5e8RUdX5sgk424Ogs qQLMo+4B7wlkY+baCCd7rNWQzBprZaGEgU7eMsADrmrTAgdoUylKAPcMDW6Gcr2nOOSh j3VdRQjSH+3vVxbFwUzdIlAuNzt3LmpoyI+Dqd1c+Gllvj8jf58uYb8kLZi4Z7Nqf8gR L1CA==
X-Gm-Message-State: AOJu0YzpOhu8fulrm1UQi3coCbHPFH/LlCtoH7PWI+KExD6vgw7no4Ih ivDDiPR9DHOk0+QjItfc32yDwmjWeb2Sz17m+TcWwJbtw3rg0G6i4pqfScJ2raL1t6mtsgqniGh f0v6qhGqhaQ==
X-Gm-Gg: AeBDietp8XfmwaIdYrkm5/ObTPRqWcywdIogjfKPZny5gPS7l068Tqn9tRNIrc17KDH kHcRZiORhv1mVrGc+tJLPYowrm7PRXl+pXXcrfwXgYdx92ZG1/IPxAkPN4nIEAf2wN3GgAeqvrP vb9TuCcvGwv5o8vLbbuICge5HdOczc0tjc+x9/PbcWAdbZcj+b9mbU0Kl8vbb7lOmgqinEq0y7H JL4ii7w7+3AYuWefWs7amlotDpE4KFEILlqmEZ7JCSdfo9Q+hJ9kCW+OK8v6IThtg9jpvgpsz2r iewL0GtDDoiaVgSZYEqIKkIa2omCylae1V/NJ+0LgP56gN8uAmQND2xEzM31h1SvsunQ37u2plA sR9icgmlDdRADEsBcGOgyjR7FAVs9JkLV3Kca9PG1I/BRraEoJyQdd8NBp+2U8ZHAP0Q5pWipL+ TRbv8Y7KngM8yB4uxPGS5PRjY4OStVqn+/6EAc6BqSZCKOi3/C
X-Received: by 2002:a05:6214:c2b:b0:8ac:7d13:d189 with SMTP id 6a1803df08f44-8ac862ad1d5mr364465226d6.41.1776268440435; Wed, 15 Apr 2026 08:54:00 -0700 (PDT)
Received: from smtpclient.apple ([2600:4040:2555:6800:3ca6:affb:5154:42a0]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-8ae6c93830esm18588976d6.9.2026.04.15.08.53.58 for <tls@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Apr 2026 08:53:58 -0700 (PDT)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.500.181\))
Date: Wed, 15 Apr 2026 11:53:38 -0400
References: <0CB72E61-1FA3-4E15-8355-0EE90245703A@sn3rd.com>
To: TLS List <tls@ietf.org>
In-Reply-To: <0CB72E61-1FA3-4E15-8355-0EE90245703A@sn3rd.com>
Message-Id: <9795EF2A-B31C-41DC-846E-F041ECDE1F07@sn3rd.com>
X-Mailer: Apple Mail (2.3864.500.181)
Message-ID-Hash: ZGX2SBLIFYGRT6AD37ETKDJCRMOVPVHU
X-Message-ID-Hash: ZGX2SBLIFYGRT6AD37ETKDJCRMOVPVHU
X-MailFrom: sean@sn3rd.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: WG Status: -super-jumbo-record-limit
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Egdf9z0XsfWHYsVByT1QlpYlLY4>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>
Hi! Just a reminder that the chairs were looking for input on this too. spt > On Apr 9, 2026, at 14:42, Sean Turner <sean@sn3rd.com> wrote: > > -super-jumbo-record-limit completed WGLC back in November. There were some edits that were made as a result of WGLC and a new version has been submitted; see [1]. Assuming this version addresses the WGLC comments, the document would be ready to proceed. > > During the Shepherd write-up process, Hannes noted that there are two implementations but that he did both of them; Mbed TLS and WolfSSL. Two questions: > > 1. Does anybody else have, know of, or have plans for an implementation of -super-jumbo-record-limit? > > 2. If the answer to #1 is no, are we okay with progressing the document? > > Cheers, > TLS Chairs - Deirdre, Joe, & Sean > > [1] https://datatracker.ietf.org/doc/draft-ietf-tls-super-jumbo-record-limit/
- [TLS] WG Status: -super-jumbo-record-limit Sean Turner
- [TLS] Re: WG Status: -super-jumbo-record-limit Sean Turner