Exit Zen
41
../../principles/transport.rst:88
English
send the most significant byte followed by the least significant byte
0/690 · 69
42
../../principles/transport.rst:89
English
send the least significant byte followed by the most significant byte
0/690 · 69
43
../../principles/transport.rst:91
English
The first possibility was named `big-endian` in a note written by Cohen [Cohen1980]_ while the second was named `little-endian`. Vendors of CPUs that used `big-endian` in memory insisted on using `big-endian` encoding in networked applications while vendors of CPUs that used `little-endian` recommended the opposite. Several studies were written on the relative merits of each type of encoding, but the discussion became almost a religious issue [Cohen1980]_. Eventually, the Internet chose the `big-endian` encoding, i.e. multi-byte fields are always transmitted by sending the most significant byte first, :rfc:`791` refers to this encoding as the :term:`network-byte order`. Most libraries [#fhtonl]_ used to write networked applications contain functions to convert multi-byte fields from memory to the network byte order and the reverse.
0/8440 · 844
44
../../principles/transport.rst:93
English
Besides 16 and 32 bit words, some applications need to exchange data structures containing bit fields of various lengths. For example, a message may be composed of a 16 bits field followed by eight, one bit flags, a 24 bits field and two 8 bits bytes. Internet protocol specifications will define such a message by using a representation such as the one below. In this representation, each line corresponds to 32 bits and the vertical lines are used to delineate fields. The numbers above the lines indicate the bit positions in the 32-bits word, with the high order bit at position `0`.
0/5870 · 587
45
../../principles/transport.rst:99
English
Message format
0/140 · 14
46
../../principles/transport.rst:101
English
The message mentioned above will be transmitted starting from the upper 32-bits word in network byte order. The first field is encoded in 16 bits. It is followed by eight one bit flags (`A-H`), a 24 bits field whose high order byte is shown in the first line and the two low order bytes appear in the second line followed by two one byte fields. This ASCII representation is frequently used when defining binary protocols. We will use it for all the binary protocols that are discussed in this book.
0/4990 · 499
47
../../principles/transport.rst:105
English
The peer-to-peer model emerged during the last ten years as another possible architecture for networked applications. In the traditional client-server model, hosts act either as servers or as clients and a server serves a large number of clients. In the peer-to-peer model, all hosts act as both servers and clients and they play both roles. The peer-to-peer model has been used to develop various networked applications, ranging from Internet telephony to file sharing or Internet-wide filesystems. A detailed description of peer-to-peer applications may be found in [BYL2008]_. Surveys of peer-to-peer protocols and applications may be found in [AS2004]_ and [LCP2005]_.
0/6720 · 672
48
../../principles/transport.rst:109 • ../../principles/transport.rst:122 • ../../principles/transport.rst:213 • ../../principles/transport.rst:526
English
The transport layer
0/190 · 19
50
../../principles/transport.rst:115
English
The network layer ensures the delivery of packets on a hop-by-hop basis through intermediate nodes. As such, it provides a service to the upper layer. In practice, this layer is usually the `transport layer` that improves the service provided by the `network layer` to make it usable by applications.
0/3000 · 300
51
../../principles/transport.rst:125
English
Most networks use a datagram organization and provide a simple service which is called the `connectionless service`.
0/1160 · 116
52
../../principles/transport.rst:127
English
The figure below provides a representation of the connectionless service as a `time-sequence diagram`. The user on the left, having address `S`, issues a `Data.request` primitive containing Service Data Unit (SDU) `M` that must be delivered by the service provider to destination `D`. The dashed line between the two primitives indicates that the `Data.indication` primitive that is delivered to the user on the right corresponds to the `Data.request` primitive sent by the user on the left.
0/4910 · 491
53
../../principles/transport.rst:146
English
There are several possible implementations of the connectionless service. Before studying these realizations, it is useful to discuss the possible characteristics of the connectionless service. A `reliable connectionless service` is a service where the service provider guarantees that all SDUs submitted in `Data.requests` by a user will eventually be delivered to their destination. Such a service would be very useful for users, but guaranteeing perfect delivery is difficult in practice. For this reason, network layers usually support an `unreliable connectionless service`.
0/5790 · 579
54
../../principles/transport.rst:148
English
An `unreliable connectionless` service may suffer from various types of problems compared to a `reliable connectionless service`. First of all, an `unreliable connectionless service` does not guarantee the delivery of all SDUs. This can be expressed graphically by using the time-sequence diagram below.
0/3030 · 303
55
../../principles/transport.rst:165
English
In practice, an `unreliable connectionless service` will usually deliver a large fraction of the SDUs. However, since the delivery of SDUs is not guaranteed, the user must be able to recover from the loss of any SDU.
0/2160 · 216
56
../../principles/transport.rst:167
English
A second imperfection that may affect an `unreliable connectionless service` is that it may duplicate SDUs. Some packets may be duplicated in a network and be delivered twice to their destination. This is illustrated by the time-sequence diagram below.
0/2520 · 252
57
../../principles/transport.rst:185
English
Finally, some unreliable connectionless service providers may deliver to a destination a different SDU than the one that was supplied in the `Data.request`. This is illustrated in the figure below.
0/1970 · 197
58
../../principles/transport.rst:201
English
As the transport layer is built on top of the network layer, it is important to know the key features of the network layer service. In this book, we only consider the `connectionless network layer service` which is the most widespread. Its main characteristics are :
0/2660 · 266
59
../../principles/transport.rst:203
English
the `connectionless network layer service` can only transfer SDUs of *limited size*
0/830 · 83
60
../../principles/transport.rst:204
English
the `connectionless network layer service` may discard SDUs
0/590 · 59
61
../../principles/transport.rst:205
English
the `connectionless network layer service` may corrupt SDUs
0/590 · 59