Exit Zen
6
../../exercises/reliability.rst:22
English
A version of the Alternating Bit Protocol supporting variable length frames uses a header that contains the following fields :
122/1260 · 126
6
../../exercises/network.rst:67
English
Routing protocols used in data networks only use positive link weights. What would happen with a distance vector routing protocol in the network below that contains a negative link weight ?
248/1890 · 189
6
../../exercises/sockets.rst:102
English
A detailed discussion of the socket API is outside the scope of this section and the references cited above provide a detailed discussion of all the details of the socket API. As a starting point, it is interesting to compare the socket API with the service primitives that we have discussed in the previous chapter. Let us first consider the connectionless service that consists of the following two primitives :
422/4140 · 414
6
../../exercises/transport.rst:38
English
Continue the connection so that `Host B` sends `Hello` as data and `Host A` replies by sending `Pleased to meet you`. After having received the response, `Host B` closes the connection gracefully and `Host A` does the same. Discuss on the state that needs to be maintained inside each host.
291/2900 · 290
6
../../principles/naming.rst:19
English
The first solution that allowed applications to use names was the :term:`hosts.txt` file. This file is similar to the symbol table found in compiled code. It contains the mapping between the name of each Internet host and its associated address [#fhosts]_. It was maintained by SRI International that coordinated the Network Information Center (NIC). When a new host was connected to the network, the system administrator had to register its name and address at the NIC. The NIC updated the :term:`hosts.txt` file on its server. All Internet hosts regularly retrieved the updated :term:`hosts.txt` file from the SRI_ server. This file was stored at a well-known location on each Internet host (see :rfc:`952`) and networked applications could use it to find the address corresponding to a name.
890/7940 · 794
6
../../protocols/dns.rst:26
English
The DNS header
13/140 · 14
6
../../protocols/dnssec.rst:51
English
DNS header
10/100 · 10
7
../../index.rst:54
English
Part 2: Protocols
20/170 · 17
7
../../exercises/reliability.rst:24
English
a `number` (0 or 1)
20/190 · 19
7
../../exercises/network.rst:86
English
When a network specialist designs a network, one of the problems that he needs to solve is to set the metrics the links in his network. In the USA, the Abilene network interconnects most of the research labs and universities. The figure below shows the topology of this network in 2009.
315/2870 · 287
7
../../exercises/sockets.rst:104
English
`DATA.request(destination,message)` is used to send a message to a specified destination. In this socket API, this corresponds to the ``send`` method.
162/1500 · 150
7
../../exercises/transport.rst:40
English
A transport connection that provides a message-mode service has been active for some time and all data has been exchanged and acknowledged in both directions. As in the exercise above, the sequence number is incremented after the transmission of each segment. At this time, `Host A` sends two DATA segments as shown in the figure below.
377/3360 · 336
7
../../principles/naming.rst:21
English
A :term:`hosts.txt` file can be used when there are up to a few hundred hosts on the network. However, it is clearly not suitable for a network containing thousands or millions of hosts. A key issue in a large network is to define a suitable naming scheme. The ARPANet initially used a flat naming space, i.e. each host was assigned a unique name. To limit collisions between names, these names usually contained the name of the institution and a suffix to identify the host inside the institution (a kind of poor man's hierarchical naming scheme). On the ARPANet few institutions had several hosts connected to the network.
735/6240 · 624
7
../../principles/referencemodels.rst:32 • ../../principles/referencemodels.rst:49
English
The Physical layer
18/180 · 18
7
../../principles/network.rst:26
English
There are two main types of datalink layers. The simplest datalink layer is when there are only two communicating systems that are directly connected through the physical layer. Such a datalink layer is used when there is a point-to-point link between the two communicating systems. These two systems can be hosts or routers. PPP (Point-to-Point Protocol), defined in :rfc:`1661`, is an example of such a point-to-point datalink layer. Datalink layer entities exchange `frames`. A datalink :term:`frame` sent by a datalink layer entity on the left is transmitted through the physical layer, so that it can reach the datalink layer entity on the right. Point-to-point datalink layers can either provide an unreliable service (frames can be corrupted or lost) or a reliable service (in this case, the datalink layer includes retransmission mechanisms).
1111/8500 · 850
7
../../principles/reliability.rst:35
English
`wireless`. In this case, a radio signal is used to encode the information exchanged between the communicating devices. Many types of modulation techniques are used to send information over a wireless channel and there is lot of innovation in this field with new techniques appearing every year. While most wireless networks rely on radio signals, some use a laser that sends light pulses to a remote detector. These optical techniques allow to create point-to-point links while radio-based techniques can be used to build networks containing devices spread over a small geographical area.
760/5890 · 589
7
../../protocols/dns.rst:28
English
The `Transaction ID` (transaction identifier) is a 16-bits random value chosen by the client. When a client sends a question to a DNS server, it remembers the question and its identifier. When a server returns an answer, it returns in the `Transaction ID` field the identifier chosen by the client. Thanks to this identifier, the client can match the received answer with the question that it sent.
449/3980 · 398
7
../../exercises/tcp.rst:63
English
Footnotes
21/100 · 9
8
../../index.rst:86
English
Part 3: Practice
18/160 · 16
8
../../glossary.rst:117
English
API
3/100 · 3