Exit Zen
28
../../exercises/ipv6.rst:290
English
Do your forwarding tables impose the path used to reach host ``B`` which is attached to router ``R4`` or do you need to configure an additional entry in these tables ?
0/1670 · 167
28
../../exercises/routing-protocols.rst:360
English
the responses that contain the router's routing table
0/530 · 53
28
../../exercises/tcp-2.rst:165
English
The ``tcpi_state`` variable used in this script is returned by ``TCP_INFO`` [#ftcpinfo]_. It tracks the state of the TCP connection according to TCP's finite state machine [#fstates]_. This script is available from :download:`/exercises/packetdrill_scripts/client.pkt`.
0/2690 · 269
28
../../protocols/bgp.rst:92
English
Import and export policies
0/260 · 26
28
../../protocols/congestion.rst:175
English
The last point that needs to be discussed about Explicit Congestion Notification is the algorithm that is used by routers to detect congestion. On a router, congestion manifests itself by the number of packets that are stored inside the router buffers. As explained earlier, we need to distinguish between two types of routers :
0/3280 · 328
28
../../protocols/dnssec.rst:317
English
If a resolver queries `delta.example.org`, the server will parse its zone. If this name were present, it would have been placed, in lexicographical order, between the `beta.example.org` and the `gamma.example.org` names. To confirm that the `delta.example.org` name does not exist, the server returns the `NSEC` record for `beta.example.org` that indicates that the next valid name after `beta.example.org` is `gamma.example.org`. If the server receives a query for `pi.example.org`, this is the `NSEC` record for `gamma.example.org` that will be returned. Since this record contains a name that is before `pi.example.org` in lexicographical order, this indicates that `pi.example.org` does not exist.
0/7010 · 701
28
../../protocols/email.rst:166
English
Initially, email was used to exchange small messages of ASCII text between computer scientists. However, with the growth of the Internet, supporting only ASCII text became a severe limitation for two reasons. First of all, non-English speakers wanted to write emails in their native language that often required more characters than those of the ASCII character table. Second, many users wanted to send other content than just ASCII text by email such as binary files, images or sound.
0/4850 · 485
28
../../protocols/ethernet.rst:171
English
10Base5
0/100 · 7
28
../../protocols/http.rst:118
English
an optional MIME document attached to the request
0/490 · 49
28
../../protocols/http2.rst:195
English
The length of the HTTP/2.0 frames obviously affects how different web objects can be multiplexed over the underlying transport connection. If HTTP/2.0 frames are long, the overhead of the frame header is minimal, but long frames can block short web objects. On the other hand, if the frame length is small, then the overhead due to the HTTP/2.0 frame header could become significant.
0/3830 · 383
28
../../protocols/ipv6.rst:114
English
``2001:db8:0:0:8:800:200c:417a``
0/320 · 32
28
../../protocols/ethernet.rst:89
English
Ethernet 802.3 frame format
0/270 · 27
28
../../protocols/routing.rst:92
English
Hierarchical routing with OSPF
0/300 · 30
28
../../protocols/rpc.rst:107
English
The JSON-RPC is encoded as a JSON object. For example, the example below shows an invocation of a method called `sum` with `1` and `3` as parameters.
0/1490 · 149
28
../../protocols/ssh.rst:223
English
``length`` : this is the length of the message in bytes, excluding the MAC and length fields
0/920 · 92
28
../../protocols/tcp.rst:56
English
the `Reserved` field was initially reserved for future utilization. It is now used by :rfc:`3168`.
0/980 · 98
28
../../protocols/tls.rst:95
English
When used to interact with a regular web server, the TLS handshake has three important objectives:
0/980 · 98
28
../../protocols/udp.rst:94
English
The complete list of allocated port numbers is maintained by IANA_ . It may be downloaded from http://www.iana.org/assignments/port-numbers
0/1390 · 139
28
../../protocols/wifi.rst:26
English
2.4/5 GHz
0/100 · 9
29
../../bibliography.rst:95
English
Jain, R., `Congestion control in computer networks : Issues and trends <https://dx.doi.org/10.1109/65.56532>`_, IEEE Network Magazine, May 1990, pp. 24-30
0/1540 · 154