Exit Zen
36
../../exercises/network.rst:332
English
Let us now consider the transient problems that mainly happen when the network topology changes. For this, consider the network topology shown in the figure below and assume that all routers use a distance vector protocol that uses split horizon.
314/2460 · 246
36
../../exercises/sockets.rst:288
English
The port number identifying the program running on the computer
48/630 · 63
36
../../principles/naming.rst:148
English
A copy of the information maintained by each root nameserver is available at http://www.internic.net/zones/root.zone
138/1160 · 116
36
../../principles/referencemodels.rst:137
English
the Transport layer
19/190 · 19
36
../../principles/reliability.rst:154
English
the `Physical layer service` may deliver `fewer` bits to the receiver than the bits sent by the sender
116/1020 · 102
37
../../exercises/reliability.rst:80
English
ten frames
10/100 · 10
37
../../exercises/network.rst:356
English
If you compute the routing tables of all routers in this network, you would obtain a table such as the table below :
132/1160 · 116
37
../../exercises/sockets.rst:290
English
A program can use the ``struct sockaddr_in6`` to represent IPv6 socket addresses. The following program creates a ``struct sockaddr_in6`` that identifies the program that reserved the port number ``55555`` on the computer identified by the ``::1`` IPv6 address.
276/2610 · 261
37
../../principles/referencemodels.rst:138
English
the Internet layer which is equivalent to the network layer of our reference model
86/820 · 82
37
../../principles/reliability.rst:160
English
Many other types of encodings have been defined to transmit information over an electrical cable. All physical layers are able to send and receive physical symbols that represent values `0` and `1`. However, for various reasons that are outside the scope of this chapter, several physical layers exchange other physical symbols as well. For example, the Manchester encoding used in several physical layers can send four different symbols. The Manchester encoding is a differential encoding scheme in which time is divided into fixed-length periods. Each period is divided in two halves and two different voltage levels can be applied. To send a symbol, the sender must set one of these two voltage levels during each half period. To send a `1` (resp. `0`), the sender must set a high (resp. low) voltage during the first half of the period and a low (resp. high) voltage during the second half. This encoding ensures that there will be a transition at the middle of each period and allows the receiver to synchronize its clock to the sender's clock. Apart from the encodings for `0` and `1`, the Manchester encoding also supports two additional symbols : `InvH` and `InvB` where the same voltage level is used for the two half periods. By definition, these two symbols cannot appear inside a frame which is only composed of `0` and `1`. Some technologies use these special symbols as markers for the beginning or end of frames.
1614/14290 · 1429
38
../../exercises/reliability.rst:81
English
hundred frames
11/140 · 14
38
../../exercises/network.rst:360
English
Destination
11/110 · 11
38
../../exercises/sockets.rst:301
English
Now, we have built everything we need to send a message to the remote program. The ``create_socket_and_send_message`` function below assembles all the building blocks we created until now in order to send the message ``"hello"`` to the program running on port ``55555`` on the computer identified by the ``::1`` IPv6 address.
369/3250 · 325
38
../../principles/naming.rst:152
English
It is interesting to note that to prevent any homograph attack, Google Inc. registered the `g00gle.com` domain name but does not apparently use it.
166/1470 · 147
38
../../principles/referencemodels.rst:139
English
the Link layer which combines the functions of the physical and datalink layers of our five-layer reference model
130/1130 · 113
38
../../principles/reliability.rst:167
English
Manchester encoding
20/190 · 19
39
../../exercises/reliability.rst:83
English
Is it possible for a go-back-n receiver to inter-operate with a selective-repeat sender ? Justify your answer.
105/1100 · 110
39
../../exercises/network.rst:360
English
Routes on A
12/110 · 11
39
../../exercises/sockets.rst:322
English
Note that we can reuse our ``send_hello_to_peer`` function without any modification as we wrote it to handle any kind of sockets, including sockets using the IPv6 network protocol.
215/1800 · 180
39
../../principles/referencemodels.rst:141
English
Besides this difference in the lower layers, the TCP/IP reference model is very close to the five layers that we use throughout this document.
155/1420 · 142