Peter Welcher

Edge (Computing, Networking, Security, etc.) is one of the recent hot topics, getting some well-deserved attention lately. And of course, edge security goes with that. (Does that make security the [...]

This continues some of the thoughts around NAAS, shifting focus away from what types of things the vendors do and what the future might bring, to how we consume such [...]

This blog is a follow-up to two prior blogs about Elisity. I suggest reading them first if you have not already done so. Elisity Zero Trust (ZTNA) is Hot! Taking [...]

Forward Networks presented at Cloud Field Day (#CFD) 16 in January of this year. They’ve been on my mental “interesting company to watch” list since I was at their launch [...]

As you may know, I’m an occasional TechFieldDay (#TFD) delegate, mostly at general Networking (#NFD) and Service Provider events, because it’s a great way to learn about startups and young [...]

Sometimes, things just come together. This happened to me recently while finalizing my prior blog, NAAS Taxonomy (NAAS = Network As A Service). The focus of the prior NAAS blog [...]

NetCraftsmen, a BlueAlly company has had staff members doing forms of network (and security) automation for several years. Part of the commitment to network-related automation is to better publicize some [...]

My NetCraftsmen/BlueAlly blogs get a couple of rounds of editing and then enter a publication queue. That means that weeks can pass between writing and publication. For that reason, I’ve [...]

I’ve been listening and talking to BlaZop about their interesting product. Maybe you will also find that it sounds interesting and useful… Note: I provided a draft to BlaZop for [...]

For various reasons, NetCraftsmen staff and I have been applying a critical eye to various forms of Network as a Service, or NaaS. I’ve found it useful to mentally place [...]

This blog follows a previous blog about Elisity, which described its position in the Zero Trust / ZT / ZTNA market, doing ID/device type / context-based authentication and internal access [...]

One of the challenges with larger-scale LISP-Pub/Sub-based Cisco SD-Access designs has been how to accommodate having two (or more) Internet-connected border sites with failover. Up until recently, the more obvious [...]