John C. White, NETBLT (Network Block Transfer Protocol), draft-white-protocol-stack-00.txt, April 1997 - work in progress.

 Home/Search   Document Not in Database   Summary   Related Articles  

This paper is cited in the following contexts:
Long Thin Wireless Networks - Montenegro, al.   (Correct)

....that now delays may become a problem due to the additional retransmissions, and the fact that packet transmission time increases with a larger MTU. 2.3. 2 Non TCP Proposals Other proposals assume an underlying IP datagram service, and implement an optimized transport either directly on top of IP [NETBLT] or on top of UDP [MNCP] Not relying on TCP is a bold move, given the wealth of experience and research related to it. It could be argued that the internet has not collapsed because its main protocol, TCP, is very careful in how it uses the network, and generally treats it as a black box assuming ....

....to congestion and prudently backing off. This avoids further congestion. However, in the wireless medium, packet losses may also be due to corruption due to high BER, fading, and so on. Here, the right approach is to try harder, instead of backing off. Alternative transport protocols are: NETBLT [NETBLT, RFC1986, RFC1030] MNCP [MNCP] ESRO [RFC2188] RDP [RFC908, RFC1151] VMTP [VMTP] 3 TCP or not This is one of the most hotly debated issues in the wireless arena. Here are some arguments against it: It is generally recognized that TCP does not perform well in the presence of significant levels of non congestion ....

John C. White, NETBLT (Network Block Transfer Protocol), draft-white-protocol-stack-00.txt, April 1997 - work in progress.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC