Howdy,
The protocol documentation in chapter 15, section 15.3.4 (Reply Message Body) doesn't correspond to what Ice 1.1 sends. The documentation states that a message header with a message type of Reply will be followed by a byte indicating the status of the request, and then one of the structures depending on the status type. Each of the structures has a requestId int32 as the first member. In Ice 1.1, it seems that the requestId is being sent first, followed by the reply type byte, and then the remainder of the structure as described in chapter 15.
I understand why the requestId is being sent first, so that the request invocation can proceed and a response be written without having to carry the requestId, so you might want to update this section of the documentation
