2. cnp3-ebook
3. English
4. Zen

2 ../../protocols/email.rst:11
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Electronic mail, or email, is a very popular application in computer networks such as the Internet. Email `appeared <http://openmap.bbn.com/~tomlinso/ray/firstemailframe.html>`_ in the early 1970s and allows users to exchange text based messages. Initially, it was mainly used to exchange short messages, but over the years its usage has grown. It is now not only used to exchange small, but also long messages that can be composed of several parts as we will see later. 470/10000 · 470
2 ../../protocols/ethernet.rst:12
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Ethernet was designed in the 1970s at the Palo Alto Research Center [Metcalfe1976]_. The first prototype [#fethernethistory]_ used a coaxial cable as the shared medium and 3 Mbps of bandwidth. Ethernet was improved during the late 1970s and in the 1980s, Digital Equipment, Intel and Xerox published the first official Ethernet specification [DIX]_. This specification defines several important parameters for Ethernet networks. The first decision was to standardize the commercial Ethernet at 10 Mbps. The second decision was the duration of the `slot time`. In Ethernet, a long `slot time` enables networks to span a long distance but forces the host to use a larger minimum frame size. The compromise was a `slot time` of 51.2 microseconds, which corresponds to a minimum frame size of 64 bytes. 798/10000 · 798
2 ../../protocols/http2.rst:10
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — During the last decade, a growing number of services have been supported by world wide web servers. The web protocols are not only used to deliver static documents, they are also used to deliver streaming music or video. They also enable clients to use interactive applications including games or productivity applications. These services and applications have more stringent performance requirements than the delivery of static documents. Many researchers and companies have proposed solutions to improve the performance of web services and protocols during the last decade [KR2001]_ [WBK2014]_. We discuss a subset of them in this section. 641/10000 · 641
2 ../../protocols/ipv6.rst:9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The main objective of the network layer is to allow hosts, connected to different networks, to exchange information through intermediate systems called :term:`router`. The unit of information in the network layer is called a :term:`packet`. 240/10000 · 240
2 ../../protocols/lan.rst:8
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In this section, we review the key characteristics of several datalink layer technologies. We discuss in more detail the technologies that are widely used today. A detailed survey of all datalink layer technologies would be outside the scope of this book. 255/10000 · 255
2 ../../protocols/ppp.rst:9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Many point-to-point datalink layers [#flapb]_ have been developed, starting in the 1960s. In this section, we focus on the protocols that are often used to transport IP packets between hosts or routers that are directly connected by a point-to-point link. This link can be a dedicated physical cable, a leased line through the telephone network or a dial-up connection with modems on the two communicating hosts. 412/10000 · 412
2 ../../protocols/routing.rst:7
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In a large IP network such as the global Internet, routers need to exchange routing information. The Internet is an interconnection of networks, often called domains, that are under different responsibilities. As of this writing, the Internet is composed on more than 40,000 different domains and this number is still growing [#fas]_. A domain can be a small enterprise that manages a few routers in a single building, a larger enterprise with a hundred routers at multiple locations, or a large Internet Service Provider managing thousands of routers. Two classes of routing protocols are used to allow these domains to efficiently exchange routing information. 662/10000 · 662
2 ../../protocols/rpc.rst:8
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In the previous sections, we have described several protocols that enable humans to exchange messages and access to remote documents. This is not the only usage of computer networks and in many situations applications use the network to exchange information with other applications. When an application needs to perform a large computation on a host, it can sometimes be useful to request computations from other hosts. Many distributed systems have been built by distributing applications on different hosts and using `Remote Procedure Calls` as a basic building block. 570/10000 · 570
2 ../../protocols/ssh.rst:11
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — One of the initial motivations for building computer networks was to allow users to access remote computers over the networks. In the 1960s and 1970s, the mainframes and the emerging minicomputers were composed of a central unit and a set of terminals connected through serial lines or modems. The simplest protocol that was designed to access remote computers over a network is probably :term:`telnet` :rfc:`854`. :term:`telnet` runs over TCP and a telnet server listens on port `23` by default. The TCP connection used by telnet is bidirectional, both the client and the server can send data over it. The data exchanged over such a connection is essentially the characters that are typed by the user on the client machine and the text output of the processes running on the server machine with a few exceptions (e.g. control characters, characters to control the terminal like VT-100, ...) . The default character set for telnet is the ASCII character set, but the extensions specified in :rfc:`5198` support the utilization of Unicode characters. 1049/10000 · 1049
2 ../../protocols/tcp.rst:12
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The Transmission Control Protocol (TCP) was initially defined in :rfc:`793`. Several parts of the protocol have been improved since the publication of the original protocol specification [#ftcpspecs]_. However, the basics of the protocol remain and an implementation that only supports :rfc:`793` should inter-operate with today's implementation. 346/10000 · 346
2 ../../protocols/tls.rst:11
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The Transport Layer Security family of protocols were initially proposed under the name Secure Socket Layer (SSL). The first deployments used this name and many researchers still refer to this security protocol as SSL [FKC1996]_. In this chapter, we use the official name that was standardized by the IETF: TLS for `Transport Layer Security`. 342/10000 · 342
2 ../../protocols/transport-service.rst:8
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Networked applications rely on the transport service. As explained earlier, there are two main types of transport services : 124/10000 · 124
2 ../../protocols/transport.rst:9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Transport protocols rely on the service provided by the network layer. On the Internet, the network layer provides a connectionless service. The network layer identifies each (interface of a) host by using an IP address. It enables hosts to transmit packets that contain up to 64 KBytes of payload to any destination reachable through the network. The network layer does not guarantee the delivery of information, cannot detect transmission errors and does not preserve sequence integrity. 489/10000 · 489
2 ../../protocols/udp.rst:11
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The User Datagram Protocol (UDP) is defined in :rfc:`768`. It provides an unreliable connectionless transport service on top of the unreliable network layer connectionless service. The main characteristics of the UDP service are : 230/10000 · 230
2 ../../protocols/wifi.rst:7
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The radio spectrum is a limited resource that must be shared by everyone. During most of the twentieth century, governments and international organizations have regulated most of the radio spectrum. This regulation controls the utilization of the radio spectrum, in order to prevent interference among different users. A company that wants to use a frequency range in a given region must apply for a license from the regulator. Most regulators charge a fee for the utilization of the radio spectrum and some governments have encouraged competition among companies bidding for the same frequency to increase the license fees. 624/10000 · 624
2 ../../exercises/network.rst:12
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Building a network 18/10000 · 18
2 ../../exercises/sockets.rst:7
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — Popular operating systems allow isolating different programs by executing them in separate `processes`. A :term:`socket` is a tool provided by the operating system that enables two separated processes to communicate with each other. A socket takes the form of a file descriptor and can be seen as a communication pipe through which the communicating processes can exchange arbitrary information. In order to receive a message, a process must be attached to a specific :term:`address` that the peer can use to reach it. 518/10000 · 518
2 ../../protocols/dns.rst:9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — We have already explained the main principles that underlie the utilization of names on the Internet and their mapping to addresses in section :ref:`naming`. 157/10000 · 157
2 ../../protocols/http.rst:9
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — In the early days, the Internet was mainly used for remote terminal access with telnet_, email and file transfer. The default file transfer protocol, `FTP`, defined in :rfc:`959` was widely used. `FTP` clients and servers are still included in some operating systems. 267/10000 · 267
3 ../../exercises/sockets.rst:52
	English ↹ ↵ NBS … “ ” ‘ ’ ﹙-﹚ ‐ – — The socket is a powerful abstraction as it allows processes to communicate even if they are located on different computers. In this specific cases, the inter-processes communication will go through a network. 208/10000 · 208