From: Andrew Lunn <andrew@lunn.ch>
To: Peter Enderborg <peterend@axis.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Daniel Golle <daniel@makrotopia.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for net-next] if_ether.h: Clarify ethertype validity for gsw1xx dsa
Date: Mon, 17 Nov 2025 14:28:55 +0100 [thread overview]
Message-ID: <7000f777-d082-4b06-88dd-67f947c85d2a@lunn.ch> (raw)
In-Reply-To: <5a7f0105-801d-41d9-850c-03783d76f3e1@axis.com>
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.
Andrew
next prev parent reply other threads:[~2025-11-17 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251114135935.2710873-1-peterend@axis.com>
[not found] ` <3feaff7a-fcec-49d9-a738-fa2e00439b28@lunn.ch>
2025-11-17 9:02 ` Peter Enderborg
2025-11-17 13:28 ` Andrew Lunn [this message]
2025-11-17 14:59 ` Peter Enderborg
2025-11-17 15:16 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7000f777-d082-4b06-88dd-67f947c85d2a@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterend@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®