Intra-AS and Inter-AS Routing: Gateways
Intra-AS and Inter-AS Routing: Gateways
C.b
Gateways:
B.a
A.a
A.c
d
A
a
b
c
B
perform inter-AS
routing among
themselves
perform intra-AS
routers with other
routers in their
AS
network layer
inter-AS, intra-AS
routing in
gateway A.c
link layer
physical layer
a
Host
h1
A.a
Inter-AS
routing
between
A and B
A.c
d
c
b
A
Intra-AS routing
within AS A
B.a
a
c
B
Host
h2
b
Intra-AS routing
within AS B
Internet Structure
Today
Large corporation
Consumer ISP
Peering
point
Backbone service provider
Peering
point
Consumer ISP
Large corporation
Small
corporation
Consumer ISP
Protocol messages
neighbor acquisition: one router requests that another
be its peer; peers exchange reachability information
neighbor reachability: one router periodically tests if
the another is still reachable; exchange HELLO/ACK
messages; uses a k-out-of-n rule
routing updates: peers periodically exchange their
routing tables (distance-vector)
R3
Autonomous System 1
R2
Border Router
R4
R5
Autonomous System 2
R6
BGP Example
Speaker for AS2 advertises reachability to P and Q
network 128.96, 192.4.153, 192.4.32, and 192.4.3, can be reached
directly from AS2
networks
192.12.69,
192.4.54,
192.4.23
can be
reached along
the path (AS1,
AS3).
Regional provider A
(AS 2)
Backbone network
(AS 1)
Regional provider B
(AS 3)
transit networks
Customer P
(AS 4)
128.96
192.4.153
Customer Q
(AS 5)
192.4.32
192.4.3
Customer R
(AS 6)
192.12.69
Customer S
(AS 7)
192.4.54
192.4.23
stub networks
Destination-based forwarding
R3
10.1.1/24
R1
R2
0
1
0
Prefix
10.1.1
10.3.3
Interface
0
0
Prefix
10.1.1
10.3.3
R4
Interface
1
0
10.3.3/24
When MPLS is enabled on a router the router allocates a label for each
prefix in its routing table and advertise both the label and the predix that it
represent to its neighboring routers.
The advertisement is carried in the Label Distribution Protocol
Advertise the
label and
their bindings
R3
Label=16, Prefix=10.3.3
10.1.1/24
R1
R2
0
R4
0
Prefix
10.1.1
10.3.3
Interface
0
0
Label
Prefix
Interface
15
16
10.1.1
10.3.3
1
0
10.3.3/24
Advertising labels
R3
10.1.1/24
R1
R2
0
R4
0
Prefix
10.1.1
10.3.3
Interface
0
0
Remote
Label
15
16
Outgoing Label
Label
Prefix
Interface
15
16
10.1.1
10.3.3
1
0
10.3.3/24
Advertising labels
Label=24, Prefix=10.1.1
R3
10.1.1/24
R1
R2
R4
0
Prefix
Interface
Remote
Label
Label
Prefix
Interface
Remote
Label
10.1.1
10.3.3
0
0
15
16
15
16
10.1.1
10.3.3
1
0
24
Outgoing Label
Outgoing Label
10.3.3/24
Label switching
10.1.1/24
R3
LER
Label Edge Router
INFO
IP Dest
10.1.1.5
R1
INFO
IP Dest
10.1.1.5
15
R2
R4
0
Prefix
Interface
Remote
Label
Label
Prefix
Interface
Remote
Label
10.1.1
10.3.3
0
0
15
16
15
16
10.1.1
10.3.3
1
0
24
10.3.3/24
Label swapping
There is no need to examine the
IP header* at router R2:
10.1.1/24
exact Match using labels
R3
LER
Label Edge Router
INFO
IP Dest
10.1.1.5
IP Dest
10.1.1.5
INFO
R1
R2
0
24
R4
0
Prefix
Interface
Remote
Label
Label
Prefix
Interface
Remote
Label
10.1.1
10.3.3
0
0
15
16
15
16
10.1.1
10.3.3
1
0
24
10.3.3/24
* IP addresses are always of the same length but IP prefixes are of variable
length and the IP dest. addr. look-up algorithm needs to find the longest match
ATM:
just use VPI/VCI
as labels
ATM Header
Format
Option 1
VPI
Label
PT
CLP
HEC
Label
Combined Label
Option 2
Option 3
VCI
Label
Frame
Relay
DLCI
C/ E
R A
DLCI
FE BE D E
CN CN E A
1
Network Layer Header
and Info (IP or L3)
Layer 2 Header
(PPP, 802.3)
4 Byte
Label Stack
Entry Format
Label
Exp.
TTL
Overlay networks
R1
R6
R5
R2
ATM
Backbone
IP
Backbone
R3
R4
Five routing adjacencies
Overlay networks
Il routing L2 (ATM o FR)
implementa lingegneria del
traffico
A livello L3 si vedono solo
collegamenti diretti tra
router
Svantaggi:
L3
L3
L2
L3
L2
L2
L2
L3
costo maggiore
network management non integrato tra i due livelli
impossibilit di routing esplicito
L2
L2
L3
L3
Peer-to-peer networking
R1
R6
LSR1
LSR2
R5
R2
IP
Backbone
LSR3
R3
R4
Five routing adjacencies
27
Explicit Routing
IP routing is destination-based; IP has a source routing option
but limited in number of hops and processed outside the fast
path on most routers
R1
R6
R7
R3
R8
R2
R4
R5
FISH PICTURE
9
Explicit Routing
How do all the routers in the network agree on what labels to use
and how to forward packets with particular labels?
A new mechanism is needed. It turns out that the protocol used
for this task is the Resource Reservation Protocol (RSVP).
It is possible to send an RSVP message along an explicitly
specified path (e.g. R1-R3-R6-R7-R8) and use it to set up label
forwarding entries all along that path.
This is very similar to the process related to the opening packet
which establish a virtual circuit
Head
Tail
R1
R4
R2
R3
Tunneled data
arrives at tail
Pseudowire emulation
Tunnel header consist of an MPLS header rather than an IP header
INFO
202
Head
Tail
R1
R4
R2
R3
101
Tunneled data
arrives at tail
5. Demux Label
examined
INFO
DL
101
INFO
INFO
101
INFO
Pseudowire emulation
Labels can be stacked
101
INFO
L3 VPN
VPN A / Site 2
VPN B / Site 2
VPN B / Site 1
VPN B / Site 3
Provider Network
VPN A / Site 1
VPN A / Site 3
Virtually private networks
33
Architectural Evolution
L3
L3 Total mesh
L2
L3
L2
L2
L3
L3
L2
L2
L2
OVERLAY
MODEL
L3
L3
L3
L3
L2
L2
L2
L2
L3
PEER to PEER
MODEL
L2
L2
L3
L3
IP
ATM
IP/MPLS
IP/MPLS
SDH
ATM
SDH
IP/GMPLS
Optical
Optical
Optical
Optical
time
L3