Exit Zen
7
../../protocols/rpc.rst:15
English
The callee places the return value(s) at a location (register, stack, ...) where the caller can access them
0/1070 · 107
7
../../protocols/ssh.rst:70
English
The next message is the ``SSH_MSG_KEX_INIT`` message that is used to negotiate the cryptographic algorithms that will be used for the ``ssh`` session. It is very important for security protocols to include mechanisms that enable a negotiation of the cryptographic algorithms that are used. First, these algorithms provide different levels of security. Some algorithms might be considered totally secure and are recommended today while they could become deprecated a few years later after the publication of some attacks. Second, these algorithms provide different levels of performance and have different CPU and memory impacts.
0/6280 · 628
7
../../protocols/tcp.rst:19
English
remote computer access : :term:`telnet`, :term:`ssh`, :term:`X11`, :term:`VNC`, ...
0/830 · 83
7
../../protocols/tls.rst:41
English
TCP port
0/100 · 8
7
../../protocols/transport-service.rst:17
English
the `host` on which the application is running
0/460 · 46
7
../../protocols/udp.rst:19
English
The figure below shows a typical usage of the UDP port numbers. The client process uses port number `1234` while the server process uses port number `5678`. When the client sends a request, it is identified as originating from port number `1234` on the client host and destined to port number `5678` on the server host. When the server process replies to this request, the server's UDP implementation will send the reply as originating from port `5678` on the server host and destined to port `1234` on the client host.
0/5200 · 520
7
../../protocols/wifi.rst:19
English
Frequency
0/100 · 9
8
../../bibliography.rst:24
English
Bonomi, F. and Fendick, K.W., `The rate-based flow control framework for the available bit rate ATM service <https://dx.doi.org/10.1109/65.372653>`_, IEEE Network, Mar/Apr 1995, Volume: 9, Issue: 2, pages : 25-39
0/2140 · 214
8
../../index.rst:86
English
Part 3: Practice
18/160 · 16
8
../../glossary.rst:117
English
API
3/100 · 3
8
../../exercises/ex-sharing.rst:119
English
Same question as above, but now consider that the hosts transmit 1000 bits frames at 100 Mbps. The cable has a length of 2 kilometers. C is in the middle of the cable. Each square in the figure below corresponds to 10 microseconds.
0/2310 · 231
8
../../exercises/reliability.rst:25
English
a `length` field that indicates the length of the data
60/540 · 54
8
../../exercises/network.rst:92
English
The Abilene network
17/190 · 19
8
../../exercises/sockets.rst:105
English
`DATA.indication(message)` is issued by the transport service to deliver a message to the application. In the socket API, this corresponds to the return of the ``recv`` method that is called by the application.
208/2100 · 210
8
../../exercises/transport.rst:57
English
What are the acknowledgments sent by `Host B`. How does `Host A` react and how does it terminate the connection ?
119/1130 · 113
8
../../principles/naming.rst:23
English
However, the limitations of a flat naming scheme became clear before the end of the ARPANet and :rfc:`819` proposed a hierarchical naming scheme. While :rfc:`819` discussed the possibility of organizing the names as a directed graph, the Internet opted for a tree structure capable of containing all names. In this tree, the top-level domains are those that are directly attached to the root. The first top-level domain was `.arpa` [#fdnstimeline]_. This top-level name was initially added as a suffix to the names of the hosts attached to the ARPANet and listed in the `hosts.txt` file. In 1984, the `.gov`, `.edu`, `.com`, `.mil` and `.org` generic top-level domain names were added. :rfc:`1032` proposed the utilization of the two letter :term:`ISO-3166` country codes as top-level domain names. Since :term:`ISO-3166` defines a two letter code for each country recognized by the United Nations, this allowed all countries to automatically have a top-level domain. These domains include `.be` for Belgium, `.fr` for France, `.us` for the USA, `.ie` for Ireland or `.tv` for Tuvalu, a group of small islands in the Pacific or `.tm` for Turkmenistan. The set of top-level domain-names is managed by the Internet Corporation for Assigned Names and Numbers (:term:`ICANN`). :term:`ICANN` adds generic top-level domains that are not related to a country and the `.cat` top-level domain has been registered for the Catalan language. There are ongoing discussions within :term:`ICANN` to increase the number of top-level domains.
1745/15250 · 1525
8
../../principles/referencemodels.rst:34
English
Starting from the bottom, the first layer is the Physical layer. Two communicating devices are linked through a physical medium. This physical medium is used to transfer an electrical or optical signal between two directly connected devices.
257/2410 · 241
8
../../principles/network.rst:29
English
The second type of datalink layer is the one used in Local Area Networks (LAN). Conceptually, a LAN is a set of communicating devices such that any two devices can directly exchange frames through the datalink layer. Both hosts and routers can be connected to a LAN. Some LANs only connect a few devices, but there are LANs that can connect hundreds or even thousands of devices. In this chapter, we focus on the utilization of point-to-point datalink layers. We describe later the organization and the operation of Local Area Networks and their impact on the network layer.
787/5740 · 574
8
../../principles/reliability.rst:39
English
The physical layer
18/180 · 18
8
../../principles/transport.rst:27
English
An `application-level protocol` is similar to a structured conversation between humans. Assume that Alice wants to know the current time but does not have a watch. If Bob passes close by, the following conversation could take place :
0/2330 · 233