Abstract

Proceeding of: IEEE International Conference on Communications (ICC 2018) Enterprise Networking has a strong set of requirements in terms of resiliency, reliability and resources usage. With current approaches being based on monolithic and expensive infrastructures using dedicated overlay links, providers are moving to more economical hybrid solutions that encompass private dedicated links with public/regular Internet connections. However, these usually rely on complex, hardware-dependent and/or proprietary Traffic Engineering (TE) solutions, which are computationally costly, in particular for the forwarding nodes. In this paper, we propose SEMPER: a lightweight TE solution based on MP-TCP that, in contrast to other TE solutions, moves the complexity to the endpoints of the connection, and relieves the forwarding elements from complex operations or even maintaining state. As our evaluation shows, SEMPER efficiently makes use of all available paths between the endpoints while maintaining fairness, and properly adapts to variations on the available capacity. This work has been partly supported by the H2020 5GMoNArch project (grant agreement 761445), and by the Madrid Regional Government through the TIGRE5-CM program (S2013/ICE-2919).

Abstract

In this paper we present a comprehensive set of mechanisms that restore to the site administrator the capacity of enforcing traffic engineering (TE) policies in a multiaddressed IPv6 scenario. The mechanisms rely on the ability of SHIM6 to securely perform locator changes in a transparent fashion to transport and application layers. Once an outgoing path has been selected for a communication by proper routing configuration in the site, the source prefix of SHIM6 data packets is rewritten by the site routers to avoid packet discarding due to ingress filtering. The SHIM6 locator preferences exchanged in the context establishment phase are modified by the site routers to influence in the path used for receiving traffic. Scalable deployment is ensured by the stateless nature of these mechanisms. Publicado

Abstract

Broadband satellite constellation networks will be required to carry all types of IP traffic, real time interactive traffic as well as non-real time traffic, warranting the need for appropriate QoS for these different traffic flows. In this paper we investigate the need for MPLS traffic engineering in GEO/MEO/LEO satellite networks to address QoS issues. We compare the service received by TCP and UDP flows when they share a link and when they are routed on explicit MPLS traffic trunks. Since MPLS traffic trunks allow non-shortest path links also to be used, the total network throughput goes up with proper traffic engineering. If UDP and TCP flows are mixed in a trunk, TCP flows receive reduced service as the UDP flows increase their rates. Also, we found that with MPLS traffic engineering we can protect real time traffic and VoIP traffic from packet loss and excessive jitter by separating them from other congestion unresponsive flows Peer Reviewed

Abstract

Date of Conference: 1-3 Oct. 2003 Conference name: Proceedings of the 3rd IEEE Workshop on IP Operations & Management (IPOM 2003) We propose a novel traffic engineering architecture for IP networks with multiprotocol label switching (MPLS) backbones. In this architecture, two (primary and secondary) label switched paths (LSPs) are established among every pair of IP routers located at the edge of an MPLS cloud. Traffic between a source-destination pair is then split between the primary and secondary LSPs using an ABR-like explicit-rate feedback gathered from the network. Taking into consideration the packet reordering effect of packet-based load balancing schemes, we propose a novel traffic splitting mechanism that operates on a per-flow basis. We show, using a variety of scenarios, that deploying flow-based multipath traffic engineering not only provides significantly and consistently better throughput than that of a single path, but is also void of any packet reordering. © 2003 IEEE.

Abstract

It is expected that IPv6 multihomed sites will obtain as many global prefixes as direct providers they have, so traffic engineering techniques currently used in IPv4 multihomed sites is no longer suitable. However, traffic engineering is required for several reasons, and in particular, for being able to properly support multimedia communications. In this paper we present a framework for traffic engineering in IPv6 multihomed sites with multiple global prefixes. Within this framework, we have included several tools such as DNS record manipulation and proper configuration of the policy table defined in RFC 3484. To provide automation in the management of traffic engineering, we analyzed the usage of two mechanisms to configure the policy table. This work has been partly supported by the European Union under the E-Next Project FP6-506869 and by the OPTINET6 project TIC-2003-09042-C03-01. Publicado

Abstract

Schemes described in the literature on network congestion management are in general based on queue management. Also it is widely accepted that Poisson model is not sufficient to characterize the traffic in current Internet. In this paper, we present the details of some simulation studies carried out on an alternate RED (random early detection) algorithm for traffic congestion management in IP networks having self similar input. We first discuss the basic scheme of normal as proposed by Floyd et al., for the Poisson input model, and then explain a new AQM proposed by us. Our modification to the RED algorithm takes into consideration probability values corresponding to the average queue lengths for computing the marking/dropping probability. Verification of the algorithms proposed vis-a-vis that of Floyd as well as the ones proposed by us, has been done by simulating self-similar traffic. Results of the verification have been discussed in the paper