Exit Zen
21
../../protocols/email.rst:109
English
A simple email message containing the `From:`, `To:`, `Subject:` and `Date:` header lines and two lines of body is shown below.
0/1270 · 127
21
../../protocols/ethernet.rst:118
English
The introduction of the twisted pairs led to two major changes to Ethernet. The first change concerns the physical topology of the network. 10Base2 and 10Base5 networks are shared buses, the coaxial cable typically passes through each room that contains a connected computer. A 10BaseT network is a star-shaped network. All the devices connected to the network are attached to a twisted pair cable that ends in the telecom closet. From a maintenance perspective, this is a major improvement. The cable is a weak point in 10Base2 and 10Base5 networks. Any physical damage on the cable broke the entire network and when such a failure occurred, the network administrator had to manually check the entire cable to detect where it was damaged. With 10BaseT, when one twisted pair is damaged, only the device connected to this twisted pair is affected and this does not affect the other devices. The second major change introduced by 10BaseT was that is was impossible to build a 10BaseT network by simply connecting all the twisted pairs together. All the twisted pairs must be connected to a relay that operates in the physical layer. This relay is called an `Ethernet hub`. A `hub` is thus a physical layer relay that receives an electrical signal on one of its interfaces, regenerates the signal and transmits it over all its other interfaces. Some `hubs` are also able to convert the electrical signal from one physical layer to another (e.g. 10BaseT to 10Base2 conversion).
0/14740 · 1474
21
../../protocols/http.rst:100
English
More complex HTML elements can also include optional attributes in the start tag ::
0/830 · 83
21
../../protocols/http2.rst:146
English
Let us first examine how HTTP/2.0 structures the bytestream of the underlying connection.
0/890 · 89
21
../../protocols/ipv6.rst:100
English
The IPng address size
0/210 · 21
21
../../protocols/ethernet.rst:49
English
The fourth part of the Ethernet frame is the payload. The minimum length of the payload is 46 bytes to ensure a minimum frame size, including the header of 512 bits. The Ethernet payload cannot be longer than 1500 bytes. This size was found reasonable when the first Ethernet specification was written. At that time, Xerox had been using its experimental 3 Mbps Ethernet that offered 554 bytes of payload and :rfc:`1122` required a minimum MTU of 572 bytes for IPv4. 1500 bytes was large enough to support these needs without forcing the network adapters to contain overly large memories. Furthermore, simulations and measurement studies performed in Ethernet networks revealed that CSMA/CD was able to achieve a very high utilization. This is illustrated in the figure below based on [SH1980]_, which shows the channel utilization achieved in Ethernet networks containing different numbers of hosts that are sending frames of different sizes.
0/9430 · 943
21
../../protocols/routing.rst:71
English
Compared to the basics of link-state routing protocols that we discussed in section :ref:`linkstate`, there are some particularities of OSPF that are worth discussing. First, in a large network, flooding the information about all routers and links to thousands of routers or more may be costly as each router needs to store all the information about the entire network. A better approach would be to introduce hierarchical routing. Hierarchical routing divides the network into regions. All the routers inside a region have detailed information about the topology of the region but only learn aggregated information about the topology of the other regions and their interconnections. OSPF supports a restricted variant of hierarchical routing. In OSPF's terminology, a region is called an `area`.
0/7960 · 796
21
../../protocols/rpc.rst:94
English
Compared with XDR, the main advantage of JSON is that the transfer syntax is easily readable by a human. However, this comes at the expense of a less compact encoding. Some data encoded in JSON will usually take more space than when it is encoded with XDR. More compact encoding schemes have been defined, see e.g. [BH2013]_ and the references therein.
0/3520 · 352
21
../../protocols/ssh.rst:193
English
Single use keys
0/150 · 15
21
../../protocols/tcp.rst:48
English
the `SYN` flag is used during connection establishment
0/540 · 54
21
../../protocols/tls.rst:47
English
FTP
0/100 · 3
21
../../protocols/transport-service.rst:60
English
`0:0:0:0:0:0:0:1` is represented as `::1`
0/410 · 41
21
../../protocols/udp.rst:71
English
The checksum of the UDP segment is computed over :
0/500 · 50
21
../../protocols/wifi.rst:24
English
802.11b
0/100 · 7
22
../../bibliography.rst:68
English
Sally Floyd and Van Jacobson. 1993. `Random early detection gateways for congestion avoidance <https://dx.doi.org/10.1109/90.251892>`_. IEEE/ACM Transactions Networking 1, 4 (August 1993), 397-413.
0/1970 · 197
22
../../glossary.rst:235
English
BNF
0/100 · 3
22
../../exercises/ex-sharing.rst:538 • ../../exercises/ex-sharing.rst:613
English
Consider the network depicted in the figure below.
0/500 · 50
22
../../exercises/reliability.rst:50
English
Practice
9/100 · 8
22
../../exercises/network.rst:182 • ../../exercises/network.rst:214
English
Same question with virtual circuits.
41/360 · 36
22
../../exercises/sockets.rst:216
English
``connect``: connecting a socket to a remote address
54/520 · 52