I think if I were a Computer Engineer I'd constantly be having existential crises, as I wondered just why I was worried about shaving nanoseconds off instruction pipelines when the software guys are just going to use the CPU to run 50 layers of interpreted code on it; and how maybe I wouldn't have to worry about my job so much if only the damned programmers worried a little bit more about system performance.
Reminds me of IPv6 arguments at work.
"Why are we allocating 18 quintillion addresses? We only need eight."
"We can't route anything smaller than that publicly."
Reminds me of IPv6 arguments at work.
"Why are we allocating 18 quintillion addresses? We only need eight."
"We can't route anything smaller than that publicly."
Should have just done IPv4.1 and added another octet on the front, assumed 0. when absent, and called it a day.
The telephone companies already dealt with this problem, and it was pretty easy for them.
I'm impressed you have IPv6 arguments at all.
I work for a crazy person. We're doing it, whether anyone likes it or not. The only question is how much we can slow it down.
Funnily enough, most network problems on BYOD networks can be fixed by dropping all v6 traffic at the edge.