Ivan Pepelnjak

Author Archives: Ivan Pepelnjak

Lesson Learned: The Way Forward

I tried to wrap up my Lessons Learned presentation on a positive note: what are some of the things you can do to avoid all the traps and pitfalls I encountered in the almost four decades of working in networking industry:

  • Get invited to architecture and design meetings when a new application project is starting.
  • Always try to figure out what the underlying actual business needs are.
  • Just because you can doesn’t mean that you should.
  • Keep it as simple as possible, but no simpler.
  • Work with your peers, and explain how networking works and why you’re facing certain limitations.
  • Humans are not perfect – automate as much as it makes sense but no more.
You’ll need a Free ipSpace.net Subscription to watch the video.

Lesson Learned: The Way Forward

I tried to wrap up my Lessons Learned presentation on a positive note: what are some of the things you can do to avoid all the traps and pitfalls I encountered in the almost four decades of working in networking industry:

  • Get invited to architecture and design meetings when a new application project starts.
  • Always try to figure out what the underlying actual business needs are.
  • Just because you can doesn’t mean that you should.
  • Keep it as simple as possible, but no simpler.
  • Work with your peers and explain how networking works and why you face certain limitations.
  • Humans are not perfect – automate as much as it makes sense, but no more.
You’ll need a Free ipSpace.net Subscription to watch the video.

Do a Cleanup Before Automating Your Network

Remington Loose sent me an interesting email describing his views on the right approach to network automation after reading my Network Reliability Engineering Should Be More than Software or Automation rant – he’s advocating standardizing network services and cleaning up your network before trying to deploy full-scale automation.


I think you are 100% right to start with a thorough cleanup before automation. Garbage in, garbage out. It is also the case that all that inconsistency and differentiation makes for complexity in automation (as well as general operations) that makes it harder to gain traction.

Do a Cleanup Before Automating Your Network

Remington Loose sent me an interesting email describing his views on the right approach to network automation after reading my Network Reliability Engineering Should Be More than Software or Automation rant – he’s advocating standardizing network services and cleaning up your network before trying to deploy full-scale automation.


I think you are 100% right to start with a thorough cleanup before automation. Garbage in, garbage out. It is also the case that all that inconsistency and differentiation makes for complexity in automation (as well as general operations) that makes it harder to gain traction.

Worth Reading: The Network Does Too Much

Tom Hollingsworth published a more eloquent version of what I’ve been saying for ages:

  • Complexity belongs to the end nodes;
  • Network should provide end-to-end packet transport, not a fix for every stupidity someone managed to push down the stack;
  • There’s nothing wrong with being a well-performing utility instead of pretending your stuff is working on unicorn farts and fairy dust.

Obviously it’s totally against the vested interest of any networking vendor out there to admit it.

Worth Reading: The Network Does Too Much

Tom Hollingsworth published a more eloquent version of what I’ve been saying for ages:

  • Complexity belongs to the end nodes;
  • Network should provide end-to-end packet transport, not a fix for every stupidity someone managed to push down the stack;
  • There’s nothing wrong with being a well-performing utility instead of pretending your stuff is working on unicorn farts and fairy dust.

Obviously it’s totally against the vested interest of any networking vendor out there to admit it.

Video: Kubernetes Architecture

Yesterday I mentioned the giant glob of complexity called Kubernetes (see also more nuanced take on the topic). If you want to slowly unravel it, Kubernetes Architecture video from the excellent Kubernetes Networking Deep Dive webinar by Stuart Charlton is a pretty good starting point.

Parts of Kubernetes Networking Deep Dive webinar (including this video) are available with Free ipSpace.net Subscription.

Three Dimensions of BGP Address Family Nerd Knobs

Got into an interesting BGP discussion a few days ago, resulting in a wild chase through recent SRv6 and BGP drafts and RFCs. You might find the results mildly interesting ;)

BGP has three dimensions of address family configurability:

  • Transport sessions. Most vendors implement BGP over TCP over IPv4 and IPv6. I’m sure there’s someone out there running BGP over CLNS1, and there are already drafts proposing running BGP over QUIC2.
  • Address families enabled on individual transport sessions, more precisely a combination of Address Family Identifier (AFI) and Subsequent Address Family Identifier.
  • Next hops address family for enabled address families.
1 73 74 75 76 77 187