2.2.1.1 MESSAGE_HEADER
Request messages use MESSAGE_HEADER as a common header, which consists of the following fields.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Version |
Type |
||||||||||||||||||||||||||||||
Padding |
Version (2 bytes): The message version, expressed as major and minor values. The version MUST be 1.0 or 2.0.<4>
-
Note that the order of the subfields is reversed; the MinorVersion subfield occurs first.
-
0
1
2
3
4
5
6
7
8
91
0
1
2
3
4
5
6
7
8
92
0
1
2
3
4
5
6
7
8
93
0
1MinorVersion
MajorVersion
-
MinorVersion (1 byte): The minor part of the version, which MUST be 0x00.
-
MajorVersion (1 byte): The major part of the version, which MUST be 0x01 or 0x02.<5>
Type (2 bytes): A 16-bit unsigned integer that specifies the message type.
-
Value
Meaning
0x0001
The message is an INITIAL_OFFER_MESSAGE (section 2.2.1.3).
0x0002
The message is a SEGMENT_INFO_MESSAGE (section 2.2.1.4).
0x0003
The message is a BATCHED_OFFER_MESSAGE (section 2.2.1.5).
Padding (4 bytes): The value of this field is indeterminate and MUST be ignored on processing.