Exit Zen
80
../../protocols/tcp.rst:251
English
`window`. a TCP receiver uses this 16 bits field to indicate the current size of its receive window expressed in bytes.
0/1190 · 119
80
../../protocols/tls.rst:408
English
Since 2014, latency has become an important concern for web services. As access networks bandwidth continue to grow, latency is becoming a key factor that affects the performance of interactive web services. With TLS 1.2, the download of a web page requires a minimum of four round-trip-times, one to create the underlying TCP connection, one to exchange the ClientHello/ServerHello, one to exchange the keys and then one to send the HTTP GET and retrieve the response. This can be very long when the server is not near the client. TLS 1.3 aimed at reducing this handshake to one round-trip-time and even zero by placing some of the cryptographic handshake in the TCP handshake. This part will be discussed in the TCP chapter. We focus here on the reducing the TLS handshake to a single round-trip-time.
0/8030 · 803
81
../../glossary.rst:75
English
IP
0/100 · 2
81
../../principles/network.rst:347
English
verifying that packets can reach a given destination
0/520 · 52
81
../../principles/reliability.rst:261
English
`DLE STX` **1** **2** **3** **DLE** `DLE` **STX** `4` `DLE ETX`
0/630 · 63
81
../../principles/transport.rst:487
English
Reliability of the connection-oriented service
0/460 · 46
81
../../principles/sharing.rst:341
English
Amateur packet radio
0/200 · 20
81
../../principles/security.rst:931
English
Alice selects a random integer, :math:`a` and sends :math:`A=g^{a} \mod p` to Bob
0/810 · 81
81
../../exercises/ipv6.rst:743
English
The ``links`` command lists the links that have been instantiated and shows that mapping between the named interfaces on each node.
0/1310 · 131
81
../../exercises/routing-protocols.rst:1190
English
Let us now consider another example. The network contains nine ASes with one host per AS. Assuming that ``AS9`` announces prefix `p9` and that ``AS2`` announces prefix `p2`.
0/1730 · 173
81
../../protocols/bgp.rst:315
English
The `local-pref` attribute is often used to prefer some routes over others.
0/750 · 75
81
../../protocols/email.rst:240
English
E
0/100 · 1
81
../../protocols/ethernet.rst:353
English
Cost
0/100 · 4
81
../../protocols/http.rst:447
English
The list of standard URI schemes is maintained by IANA_ at http://www.iana.org/assignments/uri-schemes.html
0/1070 · 107
81
../../protocols/ipv6.rst:329
English
The IP version 6 header (:rfc:`2460`)
0/370 · 37
81
../../protocols/ethernet.rst:309
English
The first Ethernet relays that operated in the datalink layers were called `bridges`. In practice, the main difference between switches and bridges is that bridges were usually implemented in software while switches are hardware-based devices. Throughout this text, we always use `switch` when referring to a relay in the datalink layer, but you might still see the word `bridge`.
0/3800 · 380
81
../../protocols/tcp.rst:255
English
The Transmission Control Block
0/300 · 30
81
../../protocols/tls.rst:410
English
To simplify both the design and the implementations, TLS 1.3 uses only a small number of cipher suites. Five of them are specified in :rfc:`8446` and ``TLS_AES_128_GCM_SHA256`` must be supported by all implementations. To ensure privacy, all cipher suites that did not provide Perfect Forward Secrecy have been removed. Compression has also been removed from TLS since several attacks on TLS 1.2 exploited its compression capability :rfc:`7457`.
0/4450 · 445
82
../../glossary.rst:77
English
Internet Protocol is the generic term for the network layer protocol in the TCP/IP protocol suite. IP version 4 is widely used but IP version 6 is being deployed globally.
0/1710 · 171
82
../../principles/network.rst:349
English
We will discuss these functions in more details when we will describe the protocols that are used in the network layer of the TCP/IP protocol suite.
0/1480 · 148