- CNET NETWORKS UK BUSINESS SITES:
- atlarge.com
- BNET UK
- silicon.com
- SmartPlanet.com
- ZDNet.co.uk
119 stories on
Sort by: Date | Relevance
Round-Up Podcast Brits suffering IT low self-esteem, the laptop scam, mobile dangers and nomo-phobia are the hot topics discussed in this week's Weekly Round-Up podcast. Andy McCue hosts and is joined in the studio by Julian Goldsmith, Tim Ferguson and Bethan Jones.
[04 Apr 2008]
Comment His claim: of all the senior managers in a business, the CIO is the least likely to get the sack. HR directors, of course, can be judged on the number of people they sack and the quantities of pointless forms they manage to get staff to complete.
[06 Mar 2008]
whitepaper In the present implementation of Transmission Control Protocol (TCP) selective acknowledgment (SACK), every SACK block needs 8 bytes to carry information about the received packets, back to the sender.
[14 Jan 2008]
whitepaper For SACK and NewReno TCP, the paper finds that a restoration objective of 600 ms to 1 s is appropriate. The de facto requirement in traditional telephone networks is to restore failures in 50 milliseconds or less.
[14 Jan 2008]
whitepaper In this paper protocol refinements for TCP-Peach are proposed to allow it to be utilized in cooperation with FACK/SACK options. TCP-Peach has recently been proposed for IP network scenarios characterized by long round trip times and high bit error...
[14 Jan 2008]
whitepaper The most up-to-date TCP version, SACK TCP, was designed to be capable of surviving multiple segment loss. SACK TCP tends to send out segments in clusters and congest bottleneck routers, which could potentially degrade SACK TCP performance...
[14 Jan 2008]
whitepaper The most up-to-date TCP version, SACK TCP, was designed to be capable of surviving multiple segment loss. However, it has been found that if too many segments in one transmission window are lost, even if SACK TCP transitions into Fast Recovery, it...
[14 Jan 2008]
whitepaper The most up-to-date TCP version, SACK TCP, was designed to be capable of surviving multiple segment loss. However, it has been found that if too many segments in one transmission window are lost, even if SACK TCP transitions into Fast Recovery, it...
[14 Jan 2008]
whitepaper This paper reports the study on the performance enhancements of two extensions to the standard TCP implementation - Selective Acknowledgement (SACK) and Header Checksum (HACK) - over satellite links that are characterized by high latency and high...
[14 Jan 2008]
whitepaper This paper describes an ns-based simulation analysis of TCP Tahoe, Reno, NewReno and SACK congestion control over hybrid wireless and wired networks. The paper compares the throughput performance between the four TCP versions.
[14 Jan 2008]
whitepaper This paper compares Reno, New-Reno and Selective Acknowledgements (SACK), the three most common TCP implementations today in (future) optical burst switched (OBS) networks. In general, SACK, which considers multiple Triple Duplicated ACKed (TD...
[14 Jan 2008]
whitepaper It was found that TCP-SACK provides a performance increase and recommends its further deployment. As broadband Internet grows in popularity, it is important to determine if improvements can be made to broadband hardware and TCP.
[14 Jan 2008]
whitepaper It presents simulation results on performance gains achievable for TCP Reno and TCP SACK, using ETEN mechanisms over a wide range of bit error rates and traffic conditions. This paper is a summary of the BBN Technical Report No.
[14 Jan 2008]
whitepaper This key idea can be implemented on top of any TCP flavor, from Tahoe to SACK, and requires modifications to the server behavior only. This paper proposes an enhancement to the TCP protocol, called TCP Smart-Framing (TCP-SF), that enables the Fast...
[14 Jan 2008]
whitepaper The results indicated that SCPSTP congestion-friendly options perform slightly better than TCP SACK protocols at moderate and high error-rates whereas IP rate-based protocols performed slightly better than SCPS-TP rate-based options.
[14 Jan 2008]
whitepaper The TCP extensions: NewReno, SACK and Limited Transmit, are compared under different traffic scenarios. This paper compares TCP Loss Recovery mechanisms that were proposed by the IETF to overcome TCP Reno lack of ability to recover efficiently from...
[14 Jan 2008]
whitepaper The existence of several versions of TCP such as TCP-Tahoe, Reno, Vegas, New Reno, and Selective Acknowledgement (SACK) is evidence of the attention TCP has received over the years. This paper makes use of hybrid systems to model the transient and...
[14 Jan 2008]
whitepaper The purpose of these experiments was to evaluate the ATM QoS requirements for applications that utilize advance TCP/IP protocols implemented with large windows and Selective ACKnowledgements (SACK). Asynchronous Transfer Mode (ATM) Quality of...
[14 Jan 2008]
whitepaper This paper first studies, through extensive simulations, the performance characteristics of four representative TCP schemes, namely TCP New Reno, SACK, Veno, and Westwood, under the network conditions of asymmetric end-to-end link capacities...
[14 Jan 2008]
whitepaper SACK TCP was designed to be capable of surviving multiple segment loss. This paper studies the resilience behavior of SACK TCP in both cases and finds that there is a critical point at which the behavior of SACK TCP changes significantly.
[26 Dec 2007]
Sort by: Date | Relevance
Copyright ©1995-2008 CNET Networks, Inc. All rights reserved. Top of page
