Metcalfe and others at the event were clear only two things remain of the original Ethernet--the name and the packet format.
As for spanning tree, no one mentioned prior art. I'll see if I can get Radia to chime in.
BTW, I was intrigued by the notion of "routing by name." Seems understandable enough that a name, assuming it's unique, is just as good an identifier as a 48-bit MAC address. My problem is, though, that unless names are carefully constructed, they will end up being just as un-hierarchical as MAC addresses are. Which makes actual "routing" a matter of every router having a list of all names. Hmmm.
Not to detract from the achievements of these smart people, but I don't think that this is the whole story. Necessarily.
For example, what Metcalfe did was brilliant, but little of it survives in today's Ethernet. The format of the basic "type" frame, yes. The carrier sense and collision detect protocol, with backoff, not really. That's not how the Ethenets work anymore. Ethernets of today are actually much simpler. Just fire off those frames, and if there's a traffic jam at a merge point, put them in a queue. (And all sorts of more or less implemented schemes for prioriting frames in a queue, which are not really standardized.)
If that original CSMA/CD protocol is used at all, it's only as a legacy protocol in a single host-switch interface. Does nothing to control traffic jams anymore.
The spanning tree protocol, I studied that from a book called "Flows in Networks," L.K Ford and D.R. Fulkerson, where the initial edition was dated 1962. It was applied to Ethernet, later on when switches were used to tie together Ethernet links, true enough. And it works very well indeed. And Radia's book is a good read, humorous, and even engrossing. But how about those other two very smart people, back in 1962?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.