Exit Zen
19
../../principles/referencemodels.rst:85
English
The Transport layer
19/190 · 19
19
../../principles/network.rst:85
English
The first and most popular organization of the network layer is the datagram organization. This organization is inspired by the organization of the postal service. Each host is identified by a `network layer address`. To send information to a remote host, a host creates a packet that contains:
324/2940 · 294
19
../../principles/reliability.rst:54
English
1 Tbps
6/100 · 6
19
../../protocols/dns.rst:65
English
`CNAME` (or canonical names) are used to define aliases. For example `www.example.com` could be a `CNAME` for `pc12.example.com` that is the actual name of the server on which the web server for `www.example.com` runs.
236/2180 · 218
19
../../protocols/routing.rst:65
English
OSPF
4/100 · 4
20
../../exercises/reliability.rst:42
English
when every second acknowledgment is discarded due to transmission errors
80/720 · 72
20
../../exercises/network.rst:178
English
`R3->R2->R4->R5` and `R1->R2->R5`
32/330 · 33
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.
369/3330 · 333
20
../../exercises/transport.rst:142
English
DATA segments contain a sequence number that is incremented for each DATA segment transmitted
108/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`.
1014/9720 · 972
20
../../principles/network.rst:87
English
the network layer address of the destination host
55/490 · 49
20
../../principles/reliability.rst:54
English
:math:`10^{12}`
15/150 · 15
20
../../principles/transport.rst:50
English
Alice : `3.1415`
16/160 · 16
20
../../protocols/dns.rst:67
English
Reverse DNS
11/110 · 11
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.
130/1130 · 113
21
../../exercises/network.rst:180
English
Is it possible to achieve these paths and if so what are the required forwarding tables ?
97/890 · 89
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.
276/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 ?
208/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.
483/4220 · 422
21
../../principles/network.rst:88
English
its own network layer address
38/290 · 29