Exit Zen
63
../../protocols/ethernet.rst:293
English
The `MAC address learning` algorithm combined with the forwarding algorithm work well in a tree-shaped network such as the one shown above. However, to deal with link and switch failures, network administrators often add redundant links to ensure that their network remains connected even after a failure. Let us consider what happens in the Ethernet network shown in the figure below.
0/3850 · 385
63
../../protocols/http.rst:255
English
This problem was solved by extending HTTP to support persistent TCP connections :rfc:`2616`. A persistent connection is a TCP connection over which a client may send several HTTP requests. This is illustrated in the figure below showing the persistent connection of HTTP 1.1.
0/2750 · 275
63
../../protocols/ipv6.rst:217
English
a packet with destination ``2001:6a8:3080::1234`` matches three routes : ``::/0``, ``2001:6a8::/32`` and ``2001:6a8:3080::/48``. The packet is forwarded via gateway ``fe80::bad:cafe``
0/1830 · 183
63
../../protocols/ethernet.rst:193
English
Additional information about the history of the Ethernet technology may be found at http://ethernethistory.typepad.com/
0/1190 · 119
63
../../protocols/tcp.rst:215
English
As explained earlier, TCP segments may contain an optional header extension. In the `SYN` and `SYN+ACK` segments, these options are used to negotiate some parameters and the utilization of extensions to the basic TCP specification.
0/2310 · 231
63
../../protocols/tls.rst:335
English
a `Protocol Version` field that indicates the version of the TLS protocol used. This version is composed of two sub fields : a major and a minor version number.
0/1600 · 160
64
../../glossary.rst:241
English
ICANN
0/100 · 5
64
../../principles/network.rst:295
English
In the above figure, assume that the network uses 16 bits addresses and that the prefix `01001010` has been assigned to the entire network. Since the network contains four routers, the network operator could assign one block of sixty-four addresses to each router. `R1` would use address `0100101000000000` while `A` could use address `0100101000000001`. `R2` could be assigned all addresses from `0100101001000000` to `0100101001111111`. `R4` could then use `0100101011000000` and assign `0100101011000001` to `B`. Other allocation schemes are possible. For example, `R3` could be allocated a larger block of addresses than `R2` and `R4` could use a sub-block from `R3` 's address block.
0/6890 · 689
64
../../principles/reliability.rst:238
English
`A` : `1000011` b
0/170 · 17
64
../../principles/transport.rst:219
English
Transport layer services
0/240 · 24
64
../../principles/sharing.rst:267
English
All Local Area Network technologies rely on a `Medium Access Control` algorithm to regulate the transmissions to either minimize or avoid collisions. There are two broad families of `Medium Access Control` algorithms :
0/2180 · 218
64
../../principles/security.rst:771
English
Alice sends her random nonce, :math:`R2`. Bob signs :math:`R2` and sends his nonce : :math:`R1`. Alice signs :math:`R1` and both are authenticated.
0/1470 · 147
64
../../exercises/ipv6.rst:611
English
``2001:db8:1341:1::/64`` on the link between ``a`` and ``r1``
0/610 · 61
64
../../exercises/routing-protocols.rst:866
English
Another interesting utilization of IPMininet_ is to explore how routers react to link failures. We start from the same network as with the previous example and disable the link between ``AS2`` and ``AS3``. For this, we log on one of the two routers and issue the following commands.
0/2820 · 282
64
../../protocols/bgp.rst:274
English
This network contains three routers : `R1`, `R2` and `R3`. Each router is attached to a local IPv6 subnet that it advertises using BGP. There are two BGP sessions, one between `R1` and `R2` and the second between `R2` and `R3`. A `/127` subnet is used on each interdomain link (`2001:db8::4/127` on `R1-R2` and `2001:db8::0/127` on `R2-R3`) in conformance with the latest recommendation :rfc:`6164`. The BGP sessions run above TCP connections established between the neighboring routers (e.g. `2001:db8::5 - 2001:db8::6` for the `R1-R2` session).
0/5460 · 546
64
../../protocols/email.rst:234
English
j
0/100 · 1
64
../../protocols/ethernet.rst:300
English
Ethernet switches in a loop
0/270 · 27
64
../../protocols/http.rst:306
English
To allow the clients and servers to control the utilization of these persistent TCP connections, HTTP 1.1 :rfc:`2616` defines several new HTTP headers:
0/1510 · 151
64
../../protocols/ipv6.rst:218
English
a packet with destination ``2001:1890:123a::1:1e`` matches one route : ``::/0``. The packet is forwarded via ``fe80::dead:beef``
0/1280 · 128
64
../../protocols/ethernet.rst:195
English
Initially, the OUIs were allocated by Xerox [DP1981]_. However, once Ethernet became an IEEE and later an ISO standard, the allocation of the OUIs moved to IEEE. The list of all OUI allocations may be found at http://standards.ieee.org/regauth/oui/index.shtml
0/2590 · 259