RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC 3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This document defines how an operator ...

Differentiated Services (DiffServ) is scalable for deployment in today’s Internet, and Multiprotocol Label Switching (MPLS) provides fast packet switching and the opportunity for traffic engineering. Thus, the combination of DiffServ and MPLS presents a very attractive strategy to backbone network providers. This paper attempts to explain the concepts of DiffServ + MPLS and illustrate its effec...

Various Multi-Protocol Label Switching-Traffic Engineering (MPLS-TE) Routing Systems have been proposed in the literature to achieve optimization of resources utilization, Quality-of-Service (QoS) and Fast Recovery. This paper proposes a generic architecture for MPLS-TE Routing Systems, which aims to ease the classification and the analysis of these systems. Then this paper defines a set of MPL...

In this paper, we present multicast traffic engineering and we compare it to unicast traffic engineering. We study the advantages given by the integration of multicasting and MPLS. We present current proposals for multicast traffic engineering and using MPLS network. We describe our approach, the MPLS multicast tree (MMT) protocol. In order to reduce forwarding states and enhance scalability, M...

A scenario of a service provider network when heavily congested due to heavy traffic flow is brought into play to confirm the attribute of MPLS to significantly improve Latency especially in a highly congested network. The service provider network was congested by sending heavy packets through the ingress and egress port of the network. The network was simulated and ping tests were carried out ...

For a perfect network it must have ability to keep all the tasks and services running even when a link or node fails. This feature of any network is usually known as network resilience. The basic working of resilient network is that it can recover from a failure by automatically diverting the traffic from the failed portion of the network to another active part of the network. This process must...

This article reviews the key differences between traditional IP routing and the emerging MPLS approach, and identifies where MPLS adds value to IP networking. In various corners of the industry MPLS has been held up as the solution to IP QoS, gigabit forwarding, network scaling, and traffic engineering. Each of these expectations is critically considered in the light of developments in conventi...

This document specifies how Label Edge Routers (LERs) should behave when determining whether to MPLS encapsulate an IPv4 packet with header options. Lack of a formal standard has resulted in different LER forwarding behaviors for IPv4 packets with header options despite being associated with a prefix-based Forwarding Equivalence Class (FEC). IPv4 option packets that belong to a prefix-based FEC...

Currently we see a discussion on the transition from ATM-based transport to IP transport in the UMTS Terrestrial Radio Access Network (UTRAN). Issues that result from the transition to IP are QoS, esp. delay, jitter, loss, bandwidth guaranties and in sequence delivery of packets for voice traffic. The paper compares two solutions for future UTRANs, native IP multi-path transport and MPLS (Multi...