Abstract-in SGPMPLS VPNs, Traffic
Engineering (TE) achieved by using
Multiprotocd Label Switching (MPIS) was
predominantly limited to intra-domain and
single administrative domain. However
with the rapid expansion of enterprise
scale. a Virtual Private Network (VPN) has
spanned a large number of administrative
domains, so effective management of inkr-
domain traffic is urgently demanded. This
paper presents the simplest step called as
BGP-based inter-domain TE. The method is
on the basis of various Border Gateway
Protocol (BCP) attributes. BCP policy and
Autonomous System (AS) relationship. To
implement TE, the method applies diverse
routing policies by configured BGP
attributes to control the outgoing and
incoming trafic in an AS. We ensure that
the best route inan AS depends on the
routes coming from its neighboring ASes
that apply export policies, as well as the
import policies of the AS. Simulation shows
that our approach can effectively
implement inter-domain "E in BGPMPLS
VPNs.
Index Terms-AS, BGP, MPLS, VPN
I. INTRODUCTION
VPN is a network where customers have
connectivity A across a shared
infrastructure using the same access
and security policies as a private network.
One of methods to build VI" has been
defined in RFC2547[1] (i.e. BGPlMPLS
VPNs), In BGPlMPLS VPNs, BGP is used to
distribute VPN routing information and
MPLS is used to forward VPN data traffic
across Service Provider (SP) backbone
network (it. Internet). As we know, the
Internet consists of a number of ASes
(also called as domains). Each AS can use a
multiple of intra-domain routing protocols,
such as OSPF, IS-IS and MPLS, but they
must present themselves as a single
technique administration with a coherent
routing plan to the other AS. In BGPlMPLS
VPNs, TE achieved by MPLS was
predominantly limited to intra-domain and
single administrative domain. Nevertheless
with the rapid expansion of enterprise
scale. a VPN spans a large number
of administrative domains, on the other
hand, today's operators acknowledge that
the edges of their networks
where they forward traffic to other domain
is the source of their greatest costs, so
effective management of their
inter-domain traffic is demanded.
A route in the Inremet may take a longer
AS path than the shortest AS path due to
routing policies. The extent of
AS path inflation observed from the Route
View routing tables. From an ISP, at least
55% of As paths are inflated by
at least one AS hap and AS paths can be
inflated by as long as 6 AS hops [2].
In this paper, the authors present the
simplest step called as BGP-based inter-
domain TE. The method is on the basis
of various BGP attributes, inbound and
outbound filter policy and AS relationship.
We apply diverse routing policies for
selecting routes from and for propagating
reachability information to other
corresponding ASes. This policies can be
implemented by configured BGP attributes
to control the outgoing and incoming
traffic in an AS in order to implementing
TE. Simulation shows that our approach
can effectively implement inter-domain TE
in BGPlMPLS VPNs. We organize the
context of this paper as folIowing.
Section I1 overviews BGPNPLS VPNs.
Section 111 presentsBGP attributes and
policies. Secdon IV describes in detail
our approach to implement BGP-based
inter-domain TE in BGP/MPL,S VPNs and
section V presents simulation results,
followed by a conclusion in Section VI.
11. OVERVIEW OF BGPMLS VPNS
The infrastructure of BGP/MPLS VPNs
shown in Fig.1
consists of three components, Customer
Edge (CE) devices, Provider Edge (PE)
routers and Provider (P) routers. A CE
router is a customer border device that
exchanges routing information for network
reachability of a customer VPN with its
directly connected PE routers using static
routing, Interior Gateway Protocol (IGP) or
BGP. PE routers are border routers in the
SP backbone network that attach directly
to CE devices. The PE router first learns
local VPN routes from CE devices, and then
exchanges VPN routing information with
other PE routers or Autonomous System
Border Routers (ASBRs) using BGP. P
routers are core routers in the SP backbone
network that does not attach to CE devices.
Two fundamental flows occur in BGPlMPLS
VPNs [3]. A control flow is used for VPN
route distribution and Label

Switched Path (LSP) establishment, and a

data flow is used to forward customer data
traffic. The control flow consists of two
sub-flows. The first one is responsible for
the exchange of routing information
between CE and PE routers ar the edges of
the SP backbone, as we11 as the
information distribution berween PE
routers or PE router and ASBR across the
SP backbone. If two sites of a VPN artach io
PE routers that are in the same AS, PE
routers can exchange these routes with
other PE routers by BGP. If two sites of a
VPN are connected to different ASes (as
shown in Fig.11, the ingress PE routers use
BGP to redistribute rouies to an ASBR in
source AS. The ASBR then uses BGP to
redistribute those routes to ASBRs in other
ASes. By this means, finally rhose routes
are distributed to the egress PE routers in
destination AS. The second control sub-
ffow is responsible for establishment of
LSPs in an AS by LDP(Label Distribution
Protocol), CR-LDP(Constraint-basecl
Roucing LDP) or RSVP(Resource
Reservation Protocol).