Re: Is IETF is being shunned for new protocol development?

Joel Halpern <jmh@joelhalpern.com> Thu, 15 January 2026 16:01 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@mail2.ietf.org
Delivered-To: ietf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2D8CCA8215DD for <ietf@mail2.ietf.org>; Thu, 15 Jan 2026 08:01:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=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=joelhalpern.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 QENTkCLYLmG9 for <ietf@mail2.ietf.org>; Thu, 15 Jan 2026 08:01:01 -0800 (PST)
Received: from maila1.tigertech.net (maila1.tigertech.net [208.80.4.151]) (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 A5D5FA8215D6 for <ietf@ietf.org>; Thu, 15 Jan 2026 08:01:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1768492855; bh=Knqy1RRBddR8viTNspnXmuusvAdfNmbSx9J/9ToURos=; h=Date:Subject:To:References:From:In-Reply-To:From; b=O5Zl0Fh4fJzVhwQPaqcbjNiKnXWkd2Va8G4zb9+tJ9gk+1dvg3+E4bqRiXMJ6g32k GXQWjvpjMvOAT8ypoLD6/RL0F2ORRyHf2EVUNuOKVQ88fnFHfs/7g8B8VtSIuBgfXZ DjGLVEYeicZLHL2+Bdy+ejjnoezGVcEOKyEWauRU=
Received: from localhost (localhost [127.0.0.1]) by maila1.tigertech.net (Postfix) with ESMTP id 4dsSPz5TL5z4TFL2; Thu, 15 Jan 2026 08:00:55 -0800 (PST)
X-Quarantine-ID: <ahdmmG1SCS7a>
X-Virus-Scanned: Debian amavis at a1.tigertech.net
Received: from [IPV6:2600:8806:103:9500:8c61:c509:34ca:d335] (unknown [IPv6:2600:8806:103:9500:8c61:c509:34ca:d335]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila1.tigertech.net (Postfix) with ESMTPSA id 4dsSPz1rCZz4TFpm; Thu, 15 Jan 2026 08:00:55 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------UsgMLkFkcGA7mOpI08zdU7N5"
Message-ID: <0b22ba19-df6d-4a00-a6d5-2ba1a8c9d49f@joelhalpern.com>
Date: Thu, 15 Jan 2026 11:00:52 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Is IETF is being shunned for new protocol development?
To: Craig Partridge <craig@tereschau.net>, IETF discussion list <ietf@ietf.org>
References: <176849135496.24849.1696091446616631661@mail2.ietf.org> <CAHQj4CdqNLanXG3WWQDycTpMUNKonikO4N1CXK4x3Jbtx7OScw@mail.gmail.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <CAHQj4CdqNLanXG3WWQDycTpMUNKonikO4N1CXK4x3Jbtx7OScw@mail.gmail.com>
Message-ID-Hash: CNRM53W5KATO2H5J3E4VYSF2XQZ4Z7LA
X-Message-ID-Hash: CNRM53W5KATO2H5J3E4VYSF2XQZ4Z7LA
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf.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
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jcZjqcvWUJ21LaPYy8X4Na6LcBw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-owner@ietf.org>
List-Post: <mailto:ietf@ietf.org>
List-Subscribe: <mailto:ietf-join@ietf.org>
List-Unsubscribe: <mailto:ietf-leave@ietf.org>

There is one observation about repeated history I would like to add to 
Craig's clear note.  We periodically get folks who say "but my case is 
so important that we should redesign the stack to optimize for my case.  
All you need to do is wait 5 years, and something else will be "so 
important".

Yours,

Joel

On 1/15/2026 10:54 AM, Craig Partridge wrote:
>
>
>     Take a look at ESUN in OCP. They are developing a new network
>     layer header
>     for use in scale-up networks. The perceived problem is that IP is
>     too much
>     overhead. It's really the IP header plus UDP header since
>     convention is
>     that new transport protocols are encapsulated in UDP. There is a
>     four byte
>     header proposed that would be used instead of 28 or 48 bytes for
>     IP v4/v6.
>
>
> I've been watching but staying out of this discussion as it is as old 
> as IETF (it was an issue when I was on the first IESG) and I'm not 
> sure I have anything new to offer.
>
> But as a protocol nerd, I couldn't let this technical statement go 
> past...  We have been down this path of smaller headers/simpler 
> headers/headers multiple times in the past 50 years (cf. LOCUS, XTP, 
> etc.).  They work in tightly constrained environments and then fail 
> miserably at wide area scale and they show up at IETF and say "how can 
> we layer this on top of TCP?"  [Meta point -- they almost inevitably 
> want to scale to wider areas]
>
> Those headers field in IP are there for very good reasons. Yes many 
> are not needed in certain situations (a great way to see this is to 
> look back at TCP header compression - on a point-to-point in-order 
> link you can get TCP+IP headers down to, if I remember right, a 
> byte).  But if you want a fully general solution (and most folks who 
> think they don't need a general solution, cf. NetWare, eventually 
> discover they do), there's not a lot of wastage.
>
> Thanks!
>
> Craig
>
> PS: Hugh Holbrooke, as my PhD student in the distant past, presumably 
> is aware.
> -- 
> *****
> Craig Partridge's email account for professional society activities 
> and mailing lists.