Quality of Service over Specific Link Layers: state of the art report

The Integrated Services concept is proposed as an enhancement to the current Internet architecture, to provide a better Quality of Service (QoS) than that provided by the traditional Best-Effort service. The features of the Integrated Services are explained in this report. To support Integrated Services, certain requirements are posed on the underlying link layer. These requirements are studied by the Integrated Services over Specific Link Layers (ISSLL) IETF working group. The status of this ongoing research is reported in this document. To be more specific, the solutions to provide Integrated Services over ATM, IEEE 802 LAN technologies and low-bitrate links are evaluated in detail. The ISSLL working group has not yet studied the requirements, that are posed on the underlying link layer, when this link layer is wireless. Therefore, this state of the art report is extended with an identification of the requirements that are posed on the underlying wireless link, to provide differentiated Quality of Service

TCP throughput guarantee in the DiffServ Assured Forwarding service: what about the results?

Since the proposition of Quality of Service architectures by the IETF, the interaction between TCP and the QoS services has been intensively studied. This paper proposes to look forward to the results obtained in terms of TCP throughput guarantee in the DiffServ Assured Forwarding (DiffServ/AF) service and to present an overview of the different proposals to solve the problem. It has been demonstrated that the standardized IETF DiffServ conditioners such as the token bucket color marker and the time sliding window color maker were not good TCP traffic descriptors. Starting with this point, several propositions have been made and most of them presents new marking schemes in order to replace or improve the traditional token bucket color marker. The main problem is that TCP congestion control is not designed to work with the AF service. Indeed, both mechanisms are antagonists. TCP has the property to share in a fair manner the bottleneck bandwidth between flows while DiffServ network provides a level of service controllable and predictable. In this paper, we build a classification of all the propositions made during these last years and compare them. As a result, we will see that these conditioning schemes can be separated in three sets of action level and that the conditioning at the network edge level is the most accepted one. We conclude that the problem is still unsolved and that TCP, conditioned or not conditioned, remains inappropriate to the DiffServ/AF service

DiffServ resource management in IP-based radio access networks

The increasing popularity of the Internet, the flexibility of IP, and the wide deployment of IP technologies, as well as the growth of mobile communications have driven the development of IP-based solutions for wireless networking. The introduction of IP-based transport in Radio Access Networks (RANs) is one of these networking solutions. When compared to traditional IP networks, an IP-based RAN has specific characteristics, due to which, for satisfactory transport functionality, it imposes strict requirements on resource management schemes. In this paper we present the Resource Management in DiffServ (RMD) framework, which extends the DiffServ architecture with new admission control and resource reservation concepts, such that the resource management requirements of an IP-based RAN are met. This framework aims at simplicity, low-cost, and easy implementation, along with good scaling properties. The RMD framework defines two architectural concepts: the Per Hop Reservation (PHR) and the Per Domain Reservation (PDR). As part of the RMD framework a new protocol, the RMD On DemAnd (RODA) Per Hop Reservation (PHR) protocol will be introduced. A key characteristic of the RODA PHR is that it maintains only a single reservation state per PHB in the interior routers of a DiffServ domain, regardless of the number of flows passing through