Jordan Becker, BAE Systems, Inc.
"The early developers were universities, government labs and industrial research organizations," he said. "None of these were particularly security conscious. Back in those days, security was thought of as IP protection. They didn't think about threats and denial of service.
"If I could do that over again is source routing. The internet is based on destination routing -- you're worried about what the destination is, and you don't care what the source address is. And that turns out to be a big problem with voice and streaming video. The internet today remains a destination-based routing environment.
"In the early days, nobody cared if anyone could intercept traffic, because nobody is going to go out and try to intercept packets. Encryption came much later to the Internet world, and it is still an end-to-end problem, where the devices on the end points do encryption, not the Internet itself.
"There were a lot of accommodations made later on for how to do billing and payment that weren't designed up front. The early designers reserved a bit in the Internet header for type of service... But it's only one bit, so you don't have a lot of discretion.
"There wasn't a lot of thought put into those things. Later on, as we discovered the real requirements, we wound up building application protocols that were much more robust and sophisticated to deal with these issues. That's become big business for network equipment vendors, but it could have been designed up front and much cheaper had they thought about it in the early days."