linux-kernel - Re: [PATCH for net-next] if_ether.h: Clarify ethertype validity for gsw1xx dsa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b072d237-2bc0-4930-a8f0-2adb7eb81043@lunn.ch>
Date: Mon, 17 Nov 2025 16:16:18 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Peter Enderborg <peterend@...s.com>
Cc: Andrew Lunn <andrew+netdev@...n.ch>,
	"David S . Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	netdev@...r.kernel.org, Daniel Golle <daniel@...rotopia.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH for net-next] if_ether.h: Clarify ethertype validity for
 gsw1xx dsa

On Mon, Nov 17, 2025 at 03:59:13PM +0100, Peter Enderborg wrote:
> You have to pay us$4000 to get a ethertype.
> 
> On 11/17/25 14:28, Andrew Lunn wrote:
> > On Mon, Nov 17, 2025 at 10:02:05AM +0100, Peter Enderborg wrote:
> > > (resend due to html bounce)
> > > On 11/15/25 21:41, Andrew Lunn wrote:
> > > > On Fri, Nov 14, 2025 at 02:59:36PM +0100, Peter Enderborg wrote:
> > > > > Ref https://standards-oui.ieee.org/ethertype/eth.txt
> > > > > 
> > > > > 
> > > > Is this actually registered with IANA?
> > > No.
> > > 
> > > > https://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml
> > > > 
> > > > Does not list it. Please keep the "NOT AN OFFICIALLY REGISTERED ID" if
> > > > it is not.
> > > IEEE is the official source to use for ethertype number assignment.
> > What i want to make clear is, if IEEE officially allocate this to
> > something else, this is an unofficial allocation, and the official use
> > can replace it. We have a few ID like this, and never had a collision
> > yet, but it could happen.
> 
> This is the public list from IEEE. It wont get more official. Yes, official
> allocation can be changed in non backward compatible way. It happen
> in 1983 so it can happen again. If the standard changes we need to adopt.
> 
> "NOT AN OFFICIALLY REGISTERED ID" is wrong, it is "Infineon Technologies Corporate Research ST".

Ah. Let me see if i have this correct.....

Infineon made a spin off called Lantiq.

Lantiq was acquired by Intel

MaxLinear acquired Intels Connected Home division.

Assuming the rights to this ID transferred along the way, it is
O.K. for MaxLinear to use this ID. But, IANAL...

Please expand the commit message with this history, which is then a
justification for removing the NOT AN OFFICIALLY REGISTERED ID, and
why it is O.K. for MaxLinear to use it.

	Andrew