I think op was just saying as a bus on a local network for some very specialized application.

But you can do that already. DNS, ARP, TCP/UDP, and IP are all completely optional.

Just write a program to send and receive Ethernet frames. I believe it doesn’t have to contain IP.

Indeed - see industrial protocols such as EtherCAT or Powerlink, which use Ethernet frames with their own non-IP protocol on top.

aren't also ATMs using a protocol of the same "species"?

> let me open my big yellow pages of globally unique MAC addresses

Yeah, well, you've basically described IPv6.

rfc4941 is from 2011 if you use an OS that isn't using it you have bigger problems.

How do networks manage the larger number of IPv6 addresses?

My cursory digging indicates that the secret sauce is to grant large IPv6 prefixes and delegate routing to the prefix. An informative-looking Reddit comment says there are 100k IPv6 prefixes (as of Oct. 2020), and each active route takes 1 KiB. [1]

So, IPv6 differs significantly from MAC addresses because you only need to track prefixes.

[1]: https://old.reddit.com/r/networking/comments/j9twgq/how_much...

Prefixes are routed. ARP, in IPv6, is replaced by a function of Neighbor Discovery Protocol (NDP) called Neighbor Advertisment (NA) and Neighbor Solicitation (NS) where L2 MAC is sent in it's messaging. The NS messaging leverages multicast to communicate with the broader set of hosts for discovery. Basically it sends a message to the multicast address containing the IPv6 address such that it can discover it's MAC. So the flooding/broadcasting for MAC of v4 is replaced by a much more efficient L3 to L2 lookup in v6.

I think you mean white pages.