Sorry, you are incorrect. I do assume liability for the designs in the contracts that are written between the company that I work for and the customer. In fact, the liability assumption is so prevalent in the industry that all contracts must be reviewed by BOTH contracting and legal before they are signed.
As for responsible charge, the reason most top engineers in networking do not have or want anyone with lesser skill working under them and making decisions is responsible charge. More likely than not, if there is more than one engineer, the senior engineer will do the work and then tell the jr engineer(s) what they did and why rather than allow them input into the design. This is because they need to be able to answer each and every question about the design. An many times, for large project, or high value (cost), or critical (life and limb) we will call in other engineers (one has a PHD in Computer Science from a State Tech school) to review our designs. Likewise, I will review their designs as well.
I have no problem being accountable to an peer review or engineering board. Show me one that understands networking well enough to be able to review my work. They didn’t exist back in 2003 when this article/post first came out ... and they don’t exist now. Further, even after 9 years, the education system is just now getting to point where it is offering a BA/BS in Computer Networking.
Regulatory liability - putting your ability to work in jeopardy should you drop the ball, not standard business liability.
Still, what you describe is good business practice for any complex project - you can’t catch everything all the time.
So why is it so important for you to call yourself an engineer?
Computer and Network Engineering are general offshoots of Electrical Engineering - they aren’t new as you state. You can get registered as a PE in Electrical Engineering, and contrary to what you may have heard, you CAN pass the test with a computer/networking background.
Unfortunately, you do not exhibit the temperament to be in responsible charge of anything if you insist that nobody can review your work. If your work is good enough, and your design is properly documented and is solid, it can be reviewed by someone with a reasonable skill level in networking.
I don’t know if this is you, nor am I accusing you of this, but what most folks doing “network engineering” do is rely on vendors to help put their designs together, and then rely on the performance claims of vendors, and interoperability claims of vendors.
You assert that it is somehow too complex for a technical person to review your work in a responsible charge capacity- and if you were an engineer, you would recognize that this highlights a failure in your design - that it is not documented sufficiently, and that your technical arrogance will be your downfall.