Source string Source string

9/10000 · 9
English Actions
To create these virtual circuits, we need to configure the `label forwarding tables` of all routers. For simplicity, assume that a label forwarding table only contains two entries. Assume that `R5` wants to receive the packets from the virtual circuit created by `R1` (resp. `R2`) with `label=1` (`label=0`). `R4` could use the following `label forwarding table`:
R4's label forwarding table
->R2
->R5
Since a packet received with `label=1` must be forwarded to `R5` with `label=1`, `R2`'s `label forwarding table` could contain :
R2's label forwarding table
Two virtual circuits pass through `R3`. They both need to be forwarded to `R4`, but `R4` expects `label=1` for packets belonging to the virtual circuit originated by `R2` and `label=0` for packets belonging to the other virtual circuit. `R3` could choose to leave the labels unchanged.
R3's label forwarding table
->R4
With the above `label forwarding table`, `R1` needs to originate the packets that belong to the `R1->R3->R4->R2->R5` circuit with `label=0`. The packets received from `R2` and belonging to the `R2->R1->R3->R4->R5` circuit would then use `label=1` on the `R1-R3` link. `R1` 's label forwarding table could be built as follows :
R1's label forwarding table
->R3
The figure below shows the path followed by the packets on the `R1->R3->R4->R2->R5` path in red with on each arrow the label used in the packets.
MultiProtocol Label Switching (MPLS) is the example of a deployed networking technology that relies on label switching. MPLS is more complex than the above description because it has been designed to be easily integrated with datagram technologies. However, the principles remain. `Asynchronous Transfer Mode` (ATM) and Frame Relay are other examples of technologies that rely on `label switching`.
Nowadays, most deployed networks rely on distributed algorithms, called routing protocols, to compute the forwarding tables that are installed on the routers. These distributed algorithms are part of the `control plane`. They are usually implemented in software and are executed on the main CPU of the routers. There are two main families of routing protocols : distance vector routing and link state routing. Both are capable of discovering autonomously the network and react dynamically to topology changes.
Footnotes
We will see later a more detailed description of Multiprotocol Label Switching, a networking technology that is capable of using one or more labels.
The control plane
One of the objectives of the `control plane` in the network layer is to maintain the routing tables that are used on all routers. As indicated earlier, a routing table is a data structure that contains, for each destination address (or block of addresses) known by the router, the outgoing interface over which the router must forward a packet destined to this address. The routing table may also contain additional information such as the address of the next router on the path towards the destination or an estimation of the cost of this path.
In this section, we discuss the main techniques that can be used to maintain the forwarding tables in a network.
Distance vector routing
Distance vector routing is a simple distributed routing protocol. Distance vector routing allows routers to automatically discover the destinations reachable inside the network as well as the shortest path to reach each of these destinations. The shortest path is computed based on `metrics` or `costs` that are associated to each link. We use `l.cost` to represent the metric that has been configured for link `l` on a router.
Each router maintains a routing table. The routing table `R` can be modeled as a data structure that stores, for each known destination address `d`, the following attributes :
`R[d].link` is the outgoing link that the router uses to forward packets towards destination `d`
`R[d].cost` is the sum of the metrics of the links that compose the shortest path to reach destination `d`
`R[d].time` is the timestamp of the last distance vector containing destination `d`
A router that uses distance vector routing regularly sends its distance vector over all its interfaces. This distance vector is a summary of the router's routing table that indicates the distance towards each known destination. This distance vector can be computed from the routing table by using the pseudo-code below.
When a router boots, it does not know any destination in the network and its routing table only contains its local address(es). It thus sends to all its neighbors a distance vector that contains only its address at a distance of `0`. When a router receives a distance vector on link `l`, it processes it as follows.
The router iterates over all addresses included in the distance vector. If the distance vector contains a destination address that the router does not know, it inserts it inside its routing table via link `l` and at a distance which is the sum between the distance indicated in the distance vector and the cost associated to link `l`. If the destination was already known by the router, it only updates the corresponding entry in its routing table if either :
the cost of the new route is smaller than the cost of the already known route `((V[d].cost + l.cost) < R[d].cost)`
the new route was learned over the same link as the current best route towards this destination `(R[d].link == l)`

Showing only subset of the strings as there were too many matches.

Component Translation Difference to current string
This translation Propagated Read only cnp3-ebook/principles/network
The following strings have the same context and source.
Propagated Read only cnp3-ebook/exercises/transport
Propagated Read only cnp3-ebook/principles/naming
Propagated Read only cnp3-ebook/principles/referencemodels
Propagated Read only cnp3-ebook/principles/security
Propagated Read only cnp3-ebook/exercises/dns
Propagated Read only cnp3-ebook/exercises/http
Propagated Read only cnp3-ebook/exercises/tcp
Propagated Read only cnp3-ebook/exercises/tls
Propagated Read only cnp3-ebook/protocols/bgp
Propagated Read only cnp3-ebook/protocols/dnssec
Propagated Read only cnp3-ebook/protocols/http2
Propagated Read only cnp3-ebook/protocols/ppp
Propagated Read only cnp3-ebook/protocols/rpc
Propagated Read only cnp3-ebook/protocols/ipv6
Propagated Read only cnp3-ebook/protocols/tls
Propagated Read only cnp3-ebook/principles/sharing
Propagated Read only cnp3-ebook/protocols/udp
Propagated Read only cnp3-ebook/protocols/wifi
Propagated Read only cnp3-ebook/exercises/sockets

Loading…

No matching activity found.
Browse all component changes

Glossary

English English
No related strings found in the glossary.

String information

Flags
read-only
Source string location
../../principles/network.rst:600 • ../../principles/linkstate.rst:379
String age
4 years ago
Source string age
4 years ago
Translation file
locale/pot/principles/network.pot, string 117