Exit Zen
58
../../protocols/tcp.rst:202
English
the high order bits contain the low order bits of a counter that is incremented slowly
0/860 · 86
58
../../protocols/tls.rst:313
English
The TLS record protocol
0/230 · 23
59
../../bibliography.rst:353
English
ITU-T, recommendation X.200, `Open Systems Interconnection - Model and Notation <http://www.itu.int/rec/T-REC-X.200-199407-I/en>`_, 1994
0/1360 · 136
59
../../glossary.rst:182
English
A relay operating in the physical layer.
0/400 · 40
59
../../principles/network.rst:259
English
The first organization, which is the one that we have implicitly assumed until now, is the `flat addressing` scheme. Under this scheme, each host and network node has a unique address. The unicity of the addresses is important for the operation of the network. If two hosts have the same address, it can become difficult for the network to forward packets towards this destination. `Flat addresses` are typically used in situations where network nodes and hosts need to be able to communicate immediately with unique addresses. These `flat addresses` are often embedded inside the network interface cards. The network card manufacturer creates one unique address for each interface and this address is stored in the read-only memory of the interface. An advantage of this addressing scheme is that it easily supports unstructured and mobile networks. When a host moves, it can attach to another network and remain confident that its address is unique and enables it to communicate inside the new network.
0/10040 · 1004
59
../../principles/reliability.rst:224
English
01111110
0/100 · 8
59
../../principles/transport.rst:203
English
the `connectionless network layer service` can only transfer SDUs of *limited size*
0/830 · 83
59
../../principles/security.rst:664
English
Here, Bob simply sends a random nonce to Alice and verifies her signature. Since the random nonce and the signature could be captured by an eavesdropper, they cannot be used as a secret key to encrypt further data. However Bob could propose a secret key and send it encrypted with Alice's public key in response to the signed nonce that he received.
0/3490 · 349
59
../../exercises/ipv6.rst:535
English
Let us start our exploration of IPv6 routing with a simple network topology that contains two hosts and three routers and uses static routes.
0/1410 · 141
59
../../exercises/routing-protocols.rst:843
English
The first of these two routes is preferred as indicated by the `>` character because it has a higher ``local-preference` (150) than the second one (100). For prefix ``2001:cafe:3::/48``, the route learned via ``fe80::3c81:2eff:fe19:465d`` is also preferred for the same reason.
0/2770 · 277
59
../../exercises/tcp-2.rst:740
English
In question 1, we assumed that the receiver acknowledged every segment received from the sender. In practice, many deployed TCP implementations use delayed acknowledgments. Assuming a delayed acknowledgment timer of 50 milliseconds, modify the time-sequence diagram below to reflect the impact of these delayed acknowledgment. Does their usage decreases or increased the transmission delay ?
0/3910 · 391
59
../../protocols/bgp.rst:256
English
The bogon filters
0/170 · 17
59
../../protocols/email.rst:234 • ../../protocols/email.rst:236
English
1
0/100 · 1
59
../../protocols/ethernet.rst:261
English
One of the selling points of Ethernet networks is that, thanks to the utilization of 48 bits MAC addresses, an Ethernet LAN is plug and play at the datalink layer. When two hosts are attached to the same Ethernet segment or hub, they can immediately exchange Ethernet frames without requiring any configuration. It is important to retain this plug and play capability for Ethernet switches as well. This implies that Ethernet switches must be able to build their MAC address table automatically without requiring any manual configuration. This automatic configuration is performed by the `MAC address learning` algorithm that runs on each Ethernet switch. This algorithm extracts the source address of the received frames and remembers the port over which a frame from each source Ethernet address has been received. This information is inserted into the MAC address table that the switch uses to forward frames. This allows the switch to automatically learn the ports that it can use to reach each destination address, provided that this host has previously sent at least one frame. This is not a problem since most upper layer protocols use acknowledgments at some layer and thus even an Ethernet printer sends Ethernet frames as well.
0/12370 · 1237
59
../../protocols/http.rst:194
English
As an illustration of HTTP/1.0, the transcript below shows a HTTP request for `http://www.ietf.org <http://www.ietf.org>`_ and the corresponding HTTP response. The HTTP request was sent using the curl_ command line tool. The `User-Agent:` header line contains more information about this client software. There is no MIME document attached to this HTTP request, and it ends with a blank line.
0/3920 · 392
59
../../protocols/ipv6.rst:199
English
Now, consider how a router inside ``alpha.com`` would reach a host in the ``UCLouvain`` network. This router has two routes towards ``2001:6a8:3080::1``. The first one, for prefix ``2001:6a8:3080::/48`` is via the direct link between the commercial ISP and UCLouvain. The second one, for prefix ``2001:6a8::/32`` is via the Internet and Belnet. Since :rfc:`1519` when a router knows several routes towards the same destination address, it must forward packets along the route having the longest prefix length. In the case of ``2001:6a8:3080::1``, this is the route ``2001:6a8:3080::/48`` that is used to forward the packet. This forwarding rule is called the `longest prefix match` or the `more specific match`. All IP routers implement this forwarding rule.
0/7580 · 758
59
../../protocols/ethernet.rst:179 • ../../protocols/ethernet.rst:358
English
10 Gbps
0/100 · 7
59
../../protocols/tcp.rst:203
English
the low order bits contain a hash value computed over the local and remote IP addresses and ports and a random secret only known to the server
0/1420 · 142
59
../../protocols/tls.rst:315
English
The handshake is now finished. The client and the server will exchange authenticated and encrypted records. TLS defines different formats for the records depending on the cryptographic algorithms that have been negotiated for the session. A detailed discussion of these different types of records is outside the scope of this introduction. For illustration, we briefly describe one record format.
0/3960 · 396
60
../../bibliography.rst:357
English
Zimmermann, H., `OSI Reference Model - The ISO Model of Architecture for Open Systems Interconnection <https://dx.doi.org/10.1109/TCOM.1980.1094702>`_, IEEE Transactions on Communications, vol. 28, no. 4, April 1980, pp. 425 - 432.
0/2320 · 232