FASTRA – SAFE AND SECURE

The innovative congestion control algorithm named FASTRA (Fast Active Stability TCP) is aimed for high-speed long-latency networks. Four major difficulties in FASTRA are highlighted at both packet and flow levels. The architecture and characterization of equilibrium and stability properties of FASTRA are robust. Experimental results of FASTRA outsmart TCP Reno, HSTCP, and STCP in terms of throughput, fairness, stability, and responsiveness. FASTRA aims to rapidly stabilize high-speed long-latency networks into steady, efficient and fair operating points, in dynamic sharing environments, and the preliminary results are produced as output of our project. The Proposed architecture is explained with the help of an existing real-time example as to explain why FASTRA download is chosen rather than FTP download. The Paper is concluded with the results of the new congestion control algorithm aided with the graphs obtained during its simulation in NS2. On proper implementation, many safe, FASTRA downloads and data transfers can be carried over a high speed internet network

FAST TCP: Motivation, Architecture, Algorithms, Performance

We describe FAST TCP, a new TCP congestion control algorithm for high-speed long-latency networks, from design to implementation. We highlight the approach taken by FAST TCP to address the four difficulties which the current TCP implementation has at large windows. We describe the architecture and summarize some of the algorithms implemented in our prototype. We characterize its equilibrium and stability properties. We evaluate it experimentally in terms of throughput, fairness, stability, and responsiveness

Enabling Compatibility Between TCP Reno and TCP Vegas

Despite research showing the superiority of TCP Vegas over TCP Reno, Reno is still the most widely deployed variant of TCP. This predicament is due primarily to the alleged incompatibility of Vegas with Reno. While Vegas in isolation performs better with respect to overall network utilization, stability, fairness, throughput and packet loss, and burstiness; its performance is generally mediocre in any environment where Reno connections exist. Hence, there exists no incentive for any operating system to adopt TCP Vegas. In this paper, we show that the accepted (default) configuration of Vegas is indeed incompatible with TCP Reno. However, with a careful analysis of how Reno and Vegas use buffer space in routers, Reno and Vegas can be compatible with one another if Vegas is configured properly. Furthermore, we show that overall network performance actually improves with the addition of properly configured Vegas flows competing head-to-head with Reno flows

Journal of Telecommunications and Information Technology, 2006, nr 1

kwartalni

Modelo extendido de QoS sobre IPv6

En este trabajo se estudian y analizan los modelos actuales de QoS en redes IP, como se aplican a IPv4 y en particular a IPv6. Se analizan varias propuestas que ofrecen diferentes métodos de QoS sobre ambos protocolos. Se proponen modelos y se realizan pruebas sobre una implementación de referencia, testing, con un esquema de QoS sobre IPv6. El esquema que sigue la implementación de referencia se basa en la utilización del campo del datagrama IPv6: Flow Label (Etiqueta de flujo), del cual IPv4 carece. Se pretende mostrar que un modelo de QoS sobre un sistema operativo real, haciendo uso del campo Flow Label, es posible y la utilización del mismo para el manejo de tráfico puede ser provechosa.Facultad de Informátic