Exit Zen
9
../../protocols/rpc.rst:18
English
This model was developed with a single host in mind. How should it be modified if the caller and the callee are different hosts connected through a network ? Since the two hosts can be different, the two main problems are the fact they do not share the same memory and that they do not necessarily use the same representation for numbers, characters, ... Let us examine how the five steps identified above can be supported through a network.
0/4410 · 441
9
../../protocols/ssh.rst:84
English
key exchange
0/120 · 12
9
../../protocols/tcp.rst:22
English
On the global Internet, most of the applications used in the wide area rely on TCP. Many studies [#ftcpusage]_ have reported that TCP was responsible for more than 90% of the data exchanged in the global Internet.
0/2130 · 213
9
../../protocols/tls.rst:43
English
POP3
0/100 · 4
9
../../protocols/transport-service.rst:20
English
On the Internet, the `port number` is an integer and the `host` is identified by its network address. There are two types of Internet addresses :
0/1450 · 145
9
../../protocols/udp.rst:49
English
UDP Header Format
0/170 · 17
9
../../protocols/wifi.rst:19
English
Max bandwidth
0/130 · 13
10
../../bibliography.rst:35
English
Bux, W., `Token-ring local-area networks and their performance <http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=18625>`_, Proceedings of the IEEE, Vol 77, No 2, p. 238-259, Feb. 1989
0/1870 · 187
10
../../index.rst:160
English
Indices and tables
15/180 · 18
10
../../glossary.rst:268
English
ARP
0/100 · 3
10
../../exercises/ex-sharing.rst:175
English
Same question as above, but now assume that the retransmission timer of each host is set to 50 microseconds.
0/1080 · 108
10
../../exercises/network.rst:96
English
the router located in `New York`
29/320 · 32
10
../../exercises/sockets.rst:110
English
Sending data to a peer using a socket
48/370 · 37
10
../../exercises/transport.rst:86
English
Same question as above, but consider now that the transport protocol tries to send large DATA segments whenever possible. For this exercise, we consider that a DATA segment can contain up to 8 bytes of data in the payload. Do not forget to show the acknowledgments in your answer.
318/2800 · 280
10
../../principles/naming.rst:54
English
The syntax of the domain names has been defined more precisely in :rfc:`1035`. This document recommends the following :term:`BNF` for fully qualified domain names (the domain names themselves have a much richer syntax).
241/2190 · 219
10
../../principles/referencemodels.rst:38
English
the Physical layer may change, e.g. due to electromagnetic interference, the value of a bit being transmitted
121/1090 · 109
10
../../principles/network.rst:35
English
As a first step, let us assume that we only need to exchange a small amount of data. In this case, there is no issue with the maximum length of the frames. However, there are other more interesting problems that we need to tackle. To understand these problems, let us consider the network represented in the figure below.
363/3210 · 321
10
../../principles/reliability.rst:44 • ../../principles/reliability.rst:49
English
Bit rate
5/100 · 8
10
../../principles/transport.rst:30
English
Bob : `Hello`
13/130 · 13
10
../../protocols/dns.rst:40
English
The `RD` (recursion desired) bit is set by a client when it sends a query to a resolver. Such a query is said to be `recursive` because the resolver will recursively traverse the DNS hierarchy to retrieve the answer on behalf of the client. In the past, all resolvers were configured to perform recursive queries on behalf of any Internet host. However, this exposes the resolvers to several security risks. The simplest one is that the resolver could become overloaded by having too many recursive queries to process. Most resolvers [#f8888]_ only allow recursive queries from clients belonging to their company or network and discard all other recursive queries. The `RA` bit indicates whether the server supports recursion. The `RCODE` is used to distinguish between different types of errors. See :rfc:`1035` for additional details. The last four fields indicate the size of the `Question`, `Answer`, `Authority` and `Additional` sections of the DNS message.
1057/9620 · 962