HTTP uses TCP. It is not in and of itself a transport protocol. Your article requires correction on this point. Firewalls generally don't have an issue with HTTP unless they are doing application inspection in which case HTTP *still* uses TCP but the application message structure may be unrecognized.
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Item 11 is not correct as well.
IPSec is not the only way of protecting privacy. Many applications provide their own encryption, for instance SSL, which helps protect privacy, though no mechanism is 100% guaranteed to protect your privacy.
Yawn
Did this bonehead just graduate? Everyone with any networking experience knows this stuff. Typical Microsoftie trying to market old hat as new shoes.
A Boneheaded Comment
It's probably just as well that you've posted your comment anonymously, because you've embarrassed yourself with it.
Dave Thaler is a member of the Internet Architecture Board and made this presentation on behalf of the IAB, with the rest of the board on the dais with him. The presentation was well-received by the IETF.
As a matter of fact, not everyone understands the IP service model, or at least doesn't acknowledge it, which was the intention of publishing the draft that this presentation summarized (http://tools.ietf.org/id/draft-iab-ip-model-evolution).
APIs continue to be written, applications created, and networks designed with some of these myths firmly in place.
I highly recommend reading the draft.
--Jeff
Where the freak is Algore?
All these myths can be answered by the God of Internet, Algore. Until I see Algore's answers to these perplexing questions I'm going to hold my breath! hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm....
ditto monkey
ditto monkey
ditto monkey
ditto monkey
Excuse me
8. New transport-layer protocols will work across the Internet.
IP was designed to support new transport protocols underneath it, but increasingly this isn't true, Thaler says. Most NATs and firewalls only allow Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) for transporting packets. Newer Web-based applications only operate over Hypertext Transfer Protocol (HTTP).
============
HTTP is not a transport layer protocol, it's an application layer protocol. HTTP can only work if you have an functioning transport/network layers, usually TCP/IP.
I was just thinking...
I was just thinking the same thing while reading this article. Reminds me that one should never take articles for face value without cross-referencing.
Source addresses cannot be spoofed
This is true for a tcp connection, which is the only context i have ever heard this statement made in.
#3
on #3, what existing problems occur with WLAN's and multicast?
Post new comment