WHOA! TCP/IP get's pwned!
- Mobius
- DBB_Master
- Posts: 7940
- Joined: Sun Jun 03, 2001 2:01 am
- Location: Christchurch, New Zealand
- Contact:
WHOA! TCP/IP get's pwned!
http://www.ncsu.edu/news/press_releases/04_03/099.htm
The article specifically mentions Internet gamers. That's gotta be great news.
The article specifically mentions Internet gamers. That's gotta be great news.
- Wolf on Air
- DBB Admiral
- Posts: 1872
- Joined: Mon Dec 13, 1999 3:01 am
- Location: Stockholm, Sweden
- Contact:
I call bovine excrement. Besides, wasn't this posted some 6 months ago, too? I seem to recall reading this before.
Still, I could always be wrong, but I'll believe it when I see it.
Here they aren't talking about the protocol, but rather whatever gigabit fiber connection they tested it on. In other words, sensationalist writing. A protocol upgrade could possibly mean a 5-10% gain. Anything more is technically impossible. Since you seem to take pride in understanding the workings of the world, Moobie, maybe you should engage your brain before posting.Dr. Injong Rhee, associate professor of computer science, said BIC can achieve speeds roughly 6,000 times that of DSL and 150,000 times that of current modems.
Still, I could always be wrong, but I'll believe it when I see it.
- CDN_Merlin
- DBB_Master
- Posts: 9781
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Capital Of Canada
I'll rephrase that...Wolf on Air wrote:I call bovine excrement. Besides, wasn't this posted some 6 months ago, too? I seem to recall reading this before.
Here they aren't talking about the protocol, but rather whatever gigabit fiber connection they tested it on. In other words, sensationalist writing. A protocol upgrade could possibly mean a 5-10% gain. Anything more is technically impossible. Since you seem to take pride in understanding the workings of the world, Moobie, maybe you should engage your brain before posting.Dr. Injong Rhee, associate professor of computer science, said BIC can achieve speeds roughly 6,000 times that of DSL and 150,000 times that of current modems.
Still, I could always be wrong, but I'll believe it when I see it.
They're talking about the hugely increased scaling possibilities, the new protocol can be scaled to WAY higher speeds than regular TCP/IP. Their wording is just poorly chosen, or as WoA said, it's just sensationalist writing.
- Admiral LSD
- DBB Admiral
- Posts: 1240
- Joined: Sun Nov 18, 2001 3:01 am
- Location: Northam, W.A., Australia
- Contact:
You guys are scrambling everything.
There is a protocol stack, which can be seen here. The rightmost part of the diagram is the physical layer (actual cables), on which the data link layer operates (frame synchronisation, basic checksumming). This layer connects one physical network device to another (e.g. a modem to a modem bank, or a PC to a switch, etc.). After that comes the network protocol, in the case of internet IP (Internet Protocol). At this point, two versions can be used, IPv4 and IPv6. Note that the underlaying data link layer does not restrict the choice of IPv4 or IPv6. IP provides two transport layers, which are more known. UDP provides a connectionless, datagram-based delivery service, with no guarantees in terms of speed, integrity or delivery. TCP is a lot more complex, is connection-oriented, and provides among integrity and delivery guarantees also congestion control and flow control. It is this protocol they are talking about in the article.
It is no problem to define a third transport protocol next to UDP and TCP, but the problem is that no application uses it. Everything is built on TCP, so you can't switch to something else. You could discard TCP and replace it with the new protocol and make it so that the upper layers do not see any change, but this would require every host on the internet to upgrade at the same time.
WoA is right. TCP is not maximizing bandwidth throughput, but in exchange it provides flow control (if the PC on receiving end is on a slow link (e.g. dialup) the server will automatically adjust it's transmission speed to match the client) and it also provides congestion control (if TCP detects packet loss, it will ask for a retransmit at half the speed of the lost packet). This has as side effect that TCP is fair (two TCP connections over the same physical link will roughly get the same bandwidth, it's not that one connection will get everything and the other one no bandwidth at all).
TCP is actually far more complex than most of you imagine. Also, TCP/IP is senseless since you are mixing two layers. You could as well use TCP over another network layer, such as IPv6 or AppleTalk. Or, you could use UDP over IP, but we don't say UDP/IP do we?
There is a protocol stack, which can be seen here. The rightmost part of the diagram is the physical layer (actual cables), on which the data link layer operates (frame synchronisation, basic checksumming). This layer connects one physical network device to another (e.g. a modem to a modem bank, or a PC to a switch, etc.). After that comes the network protocol, in the case of internet IP (Internet Protocol). At this point, two versions can be used, IPv4 and IPv6. Note that the underlaying data link layer does not restrict the choice of IPv4 or IPv6. IP provides two transport layers, which are more known. UDP provides a connectionless, datagram-based delivery service, with no guarantees in terms of speed, integrity or delivery. TCP is a lot more complex, is connection-oriented, and provides among integrity and delivery guarantees also congestion control and flow control. It is this protocol they are talking about in the article.
It is no problem to define a third transport protocol next to UDP and TCP, but the problem is that no application uses it. Everything is built on TCP, so you can't switch to something else. You could discard TCP and replace it with the new protocol and make it so that the upper layers do not see any change, but this would require every host on the internet to upgrade at the same time.
WoA is right. TCP is not maximizing bandwidth throughput, but in exchange it provides flow control (if the PC on receiving end is on a slow link (e.g. dialup) the server will automatically adjust it's transmission speed to match the client) and it also provides congestion control (if TCP detects packet loss, it will ask for a retransmit at half the speed of the lost packet). This has as side effect that TCP is fair (two TCP connections over the same physical link will roughly get the same bandwidth, it's not that one connection will get everything and the other one no bandwidth at all).
TCP is actually far more complex than most of you imagine. Also, TCP/IP is senseless since you are mixing two layers. You could as well use TCP over another network layer, such as IPv6 or AppleTalk. Or, you could use UDP over IP, but we don't say UDP/IP do we?
- CDN_Merlin
- DBB_Master
- Posts: 9781
- Joined: Thu Nov 05, 1998 12:01 pm
- Location: Capital Of Canada
Of course there is! Do it in whitespace, idiot.fliptw wrote:umm...
There isn't a really easier way of representing 32-bit and 128-bit numbers than what IPv4 and IPv6 are already using.
1. More secure - No one can see what your address is!
2. More fast - Nothing is faster to transmit than empty space!
3. More economical - Something from nothing is always good.
Yah, what Tricord said.
"Researchers in North Carolina State Universityâ??s Department of Computer Science have developed a new data transfer protocol for the Internet that makes todayâ??s high-speed Digital Subscriber Line (DSL) connections seem lethargic."
"The protocol is named BIC-TCP, which stands for Binary Increase Congestion Transmission Control Protocol."
"Dr. Injong Rhee, [..], said BIC can achieve speeds roughly 6,000 times that of DSL and 150,000 times that of current modems."
That doesn't make sense to me -- is it a new hardware or transprort layer ? Also 6000 times the speed of DSL ? I seriousely doubt one could do that w/ phone lines.
"The protocol is named BIC-TCP, which stands for Binary Increase Congestion Transmission Control Protocol."
"Dr. Injong Rhee, [..], said BIC can achieve speeds roughly 6,000 times that of DSL and 150,000 times that of current modems."
That doesn't make sense to me -- is it a new hardware or transprort layer ? Also 6000 times the speed of DSL ? I seriousely doubt one could do that w/ phone lines.
- Admiral LSD
- DBB Admiral
- Posts: 1240
- Joined: Sun Nov 18, 2001 3:01 am
- Location: Northam, W.A., Australia
- Contact:
-
- MIA Host/Admin
- Posts: 4265
- Joined: Fri Jan 01, 1999 3:01 am
- Location: Antelope Valley, Ca.
- Contact:
Grendelm - don't confuse what is said
The article didn't say it WOULD speed up DSL 6000x
It said given a PERFECT MEDIA, it could move 6000 times more data than a DSL connection on TCP/IP
Frankly - it is not very amazing to me that better protocols are available or could be created. BIG FRICKEN DEAL
The article is so poorly wrirren it makes it sound like if you could/did switch to the protocol you DSL would get 6000 times faster - pure BS
DSL running TCP/IP moving data (not game packets) has about 10% overhead worst case. So a magic protocol could only buy you 10%
the BIC-TCP is a concept to handle more data in bigger pipes
The article didn't say it WOULD speed up DSL 6000x
It said given a PERFECT MEDIA, it could move 6000 times more data than a DSL connection on TCP/IP
Frankly - it is not very amazing to me that better protocols are available or could be created. BIG FRICKEN DEAL
The article is so poorly wrirren it makes it sound like if you could/did switch to the protocol you DSL would get 6000 times faster - pure BS
DSL running TCP/IP moving data (not game packets) has about 10% overhead worst case. So a magic protocol could only buy you 10%
the BIC-TCP is a concept to handle more data in bigger pipes
If you were going to eliminate overhead youd have to completely rework the MAC layer too. Presently layers 2-7 all add some kind of overhead in some way. Mostly just "where to send" data and CRC's and stuff. The way data travels over the network it would be impossible to make a routeable network protocol without some overhead. Even non-routeable protocols like NetBEUI have some overhead. And speed advertized by anyone or any device is always layer one speed, the actual number of bits that can be transmitted per second. Many of those bits arent actual data but the overhead that is needed to get your data from point A to point B.
Only on a 2 computer network with a perfectly loss-less, distroetion-less medium would you be able to use a system with no overhead. But then youd only be able to use exactly one application across the network because app differentiation would add overhead! Oh no!
As for this "TCP/IP gets pwned" stuff,
I'll believe it when I see it. TCP/IP works quite nicely for the global network that is the internet.
Only on a 2 computer network with a perfectly loss-less, distroetion-less medium would you be able to use a system with no overhead. But then youd only be able to use exactly one application across the network because app differentiation would add overhead! Oh no!
As for this "TCP/IP gets pwned" stuff,
I'll believe it when I see it. TCP/IP works quite nicely for the global network that is the internet.
- Vindicator
- DBB Benefactor
- Posts: 3166
- Joined: Mon Dec 16, 2002 3:01 am
- Location: southern IL, USA
- Contact: