Exit Zen
20
../../exercises/sockets.rst:175
English
Using this code, the program will read and print an arbitrary message received from an arbitrary peer who knows the program's socket address. If we want to know the address of the peer that sent us the message, we can use the ``recvfrom`` system call. This is what a modified version of ``bind_and_receive_from_peer`` is doing below.
0/3330 · 333
20
../../exercises/transport.rst:142
English
DATA segments contain a sequence number that is incremented for each DATA segment transmitted
0/930 · 93
20
../../principles/naming.rst:112
English
To retrieve the mapping for host `h2.dom`, a client sends its query to the name server that is responsible for domain `.dom`. The name server directly answers the query. To retrieve a mapping for `h3.a.sdom1.dom` a DNS client first sends a query to the name server that is responsible for the `.dom` domain. This nameserver returns the nameserver that is responsible for the `sdom1.dom` domain. This nameserver can now be contacted to obtain the nameserver that is responsible for the `a.sdom1.dom` domain. This nameserver can be contacted to retrieve the mapping for the `h3.a.sdom1.dom` name. Thanks to this structure, it is possible for a DNS client to obtain the mapping of any host inside the `.dom` domain or any of its subdomains. To ensure that any DNS client will be able to resolve any fully qualified domain name, there are special nameservers that are responsible for the root of the domain name hierarchy. These nameservers are called :term:`root nameserver`.
0/9720 · 972
20
../../principles/network.rst:87
English
the network layer address of the destination host
0/490 · 49
20
../../principles/reliability.rst:54
English
:math:`10^{12}`
0/150 · 15
20
../../principles/sharing.rst:103
English
In the above network, the allocation of all flows would grow until `A1-A2` and `B1-B2` reach 5 Mbps. At this point, link `R1-R2` becomes congested and these two flows have reached their maximum. The allocation for flow `C1-C2` can increase until reaching 15 Mbps. At this point, link `R2-R3` is congested. To increase the bandwidth allocated to `C1-C2`, one would need to reduce the allocation to flow `B1-B2`. Similarly, the only way to increase the allocation to flow `B1-B2` would require a decrease of the allocation to `A1-A2`.
0/5320 · 532
20
../../principles/transport.rst:50
English
Alice : `3.1415`
0/160 · 16
20
../../protocols/dns.rst:67
English
Reverse DNS
0/110 · 11
21
../../bibliography.rst:67
English
Francois, P., Filsfils, C., Evans, J., and Bonaventure, O., `Achieving sub-second IGP convergence in large IP networks <http://doi.acm.org/10.1145/1070873.1070877>`_. SIGCOMM Computer Communication Review 35, 3 (Jul. 2005), 35-44.
0/2300 · 230
21
../../glossary.rst:158
English
The Border Gateway Protocol is the interdomain routing protocol used in the global Internet.
0/920 · 92
21
../../exercises/ex-sharing.rst:491
English
In general, the links have a non-zero delay. This is illustrated in the figure below where a delay has been added on the link between `R` and `C`.
0/1460 · 146
21
../../exercises/network.rst:180
English
Is it possible to achieve these paths and if so what are the required forwarding tables ?
0/890 · 89
21
../../exercises/reliability.rst:44
English
Same question when using selective repeat instead of go-back-n. Note that the answer is not necessarily the same.
0/1130 · 113
21
../../exercises/sockets.rst:213
English
This function is now using the ``recvfrom`` system call that will also provide the address of the peer who sent the message. As addresses are generic and can have different sizes, ``recvfrom`` also tells us the size of the address that it has written.
0/2510 · 251
21
../../exercises/transport.rst:144
English
Some transport protocols use 32 bits sequence numbers while others use 64 bits sequence number. What are the advantages and drawbacks of each approach ?
0/1520 · 152
21
../../principles/naming.rst:114
English
Each root nameserver maintains the list [#froot]_ of all the nameservers that are responsible for each of the top-level domain names and their addresses [#frootv6]_. All root nameservers cooperate and provide the same answers. By querying any of the root nameservers, a DNS client can obtain the nameserver that is responsible for any top-level-domain name. From this nameserver, it is possible to resolve any domain name.
0/4220 · 422
21
../../principles/network.rst:88
English
its own network layer address
0/290 · 29
21
../../principles/reliability.rst:59
English
To understand some of the principles behind the physical transmission of information, let us consider the simple case of an electrical wire that is used to transmit bits. Assume that the two communicating hosts want to transmit one thousand bits per second. To transmit these bits, the two hosts can agree on the following rules :
0/3300 · 330
21
../../principles/sharing.rst:106 • ../../principles/sharing.rst:172
English
Network congestion
0/180 · 18
21
../../principles/transport.rst:51
English
Bob : `This is not the correct password.`
0/410 · 41