He played a key role in moving HPE into the SDN and NFV space.
On this episode of the History of Networking over at the Network Collective, we interviewed Radia Perlman about the origin of Spanning Tree. She is really delightful, and we plan on bringing her back on in the future to talk about other topics in the history of networking technology.
The post History of Networking: Radia Perlman and Spanning Tree appeared first on rule 11 reader.
Company executives had touted its cloud business as part of its Q2 results.
IT is flooded with acronyms. It takes a third of our working life to figure out what they all mean. Protocols aren’t any easier to figure out if it’s just a string of three or four letters that look vaguely like a word. Which, by the way, you should never pronounce.
But what if the acronyms of our favorite protocols didn’t describe what the designers wanted but instead described what they actually do?
Obscurity Sends Packets Flying
Expensive Invention Gets Routers Puzzled
Vexing Router Firmware
Really Intensive Protocol
Someone Doesn’t Worry About Networking
Somewhat Quixotic Language
Blame It oN DNS
Cisco’s Universal Call Misdirector
Some Mail’s Thrown Places
Mangles Packets, Looks Silly
Amazingly Convoluted Lists
ImProperly SECured
May Push Lingering Sanity To Expire
Are there any other ones you can think of? Leave it in the comments.
The data center software also integrates with Kubernetes.
The new book should be out around the 29th of December, give or take a few days. For readers interested in what Ethan and I (and Ryan, and Pete Welcher, and Jordan Martin, and Nick Russo, and… the entire list is in the front matter), the general idea is essentially grounded in RFC1925, rule 11. There is really only a moderately sized set of problems computer system needs to solve in order to carry data from one application to another. For instance, in order to transport data across a network, you need to somehow format the data so everyone can agree on how to write and read it, ensure the data is carried without errors, ensure neither the sender nor the receiver overrun or underrun one another, and find some way to allow multiple applications (hosts, etc.), to talk over the same media. These four problems have somewhat proper names, of course: marshaling, which involves dictionaries and grammars; error control; flow control; and multiplexing. So the first step in understanding network engineering is to figure out what the problems are, and how to break them apart.
Once you understand the problems, then you can start thinking about solutions. As Continue reading
Analysis of large volumes of real-time network data can help optimize network forwarding mechanisms.
Analysis of large volumes of real-time network data can help optimize network forwarding mechanisms.
Radia Perlman joins Network Collective to talk about the history of the Spanning Tree Protocol. Love it or hate it, it’s been a fundamental part of every Ethernet network for the past 30 years and isn’t likely to fade away any time soon.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post History Of Networking – Radia Perlman – Spanning Tree appeared first on Network Collective.
Radia Perlman joins Network Collective to talk about the history of the Spanning Tree Protocol. Love it or hate it, it’s been a fundamental part of every Ethernet network for the past 30 years and isn’t likely to fade away any time soon.
Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/
The post History Of Networking – Radia Perlman – Spanning Tree appeared first on Network Collective.
The company’s virtualization effort is Project Ocean.
The post Worth Reading: GDPR and Personal Data appeared first on rule 11 reader.
“Do we have any copper FEXen on those switches?”
Fexen is the plural of FEX (the Cisco Nexus Fabric Extender modules). Oh, I know, “FEXes” is just as easy to say, but somehow FEXen seems to work better. Try and use this word in conversation today and see how it feels.
“We have about 20 FEXen distributed around the data center.”
I think you’ll like it.
If you liked this post, please do click through to the source at My Lexicon: Fexen and give me a share/like. Thank you!
Cloudflare helps make over 6 million websites faster and more secure. In doing so, Cloudflare has a vast and diverse community of users throughout the world. Whether discussing Cloudflare on social media, browsing our community forums or following Pull Requests on our open-source projects; there is no shortage of lively discussions amongst Cloudflare users. Occasionally, however, it is important to move these discussions out from cyberspace and take time to connect in person.
A little while ago, we did exactly this and ran a meetup in the Cloudflare London office. Ivan Rustic from Hardenize was our guest speaker, he demonstrated how Hardenize developed a Cloudflare App to help build a culture of security. I presented two other talks which included a primer on how the Cloudflare network is architected and wrapped up with a discussion on how you can build and monetise your very own Cloudflare App.
Since we presented this meet-up, I've received a few requests to share the videos of all the talks. You can find all three of the talks from our last London office meet-up in this blog post.