Connected: An Internet Encyclopedia
RFC 1035 - 2.3.2. Data Transmission Order

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1035
Up: 2. INTRODUCTION
Up: 2.3. Conventions
Prev: 2.3.1. Preferred name syntax
Next: 2.3.3. Character Case

### 2.3.2. Data Transmission Order

The order of transmission of the header and data described in this document is resolved to the octet level. Whenever a diagram shows a group of octets, the order of transmission of those octets is the normal order in which they are read in English. For example, in the following diagram, the octets are transmitted in the order they are numbered.

         0                   1
         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |       1       |       2       |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |       3       |       4       |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        |       5       |       6       |
        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Whenever an octet represents a numeric quantity, the left most bit in the diagram is the high order or most significant bit. That is, the bit labeled 0 is the most significant bit. For example, the following diagram represents the value 170 (decimal).

         0 1 2 3 4 5 6 7
        +-+-+-+-+-+-+-+-+
        |1 0 1 0 1 0 1 0|
        +-+-+-+-+-+-+-+-+

Similarly, whenever a multi-octet field represents a numeric quantity the left most bit of the whole field is the most significant bit. When a multi-octet quantity is transmitted the most significant octet is transmitted first.

Next: 2.3.3. Character Case

Connected: An Internet Encyclopedia
RFC 1035 - 2.3.2. Data Transmission Order