The MPC sub-channel feature for AS4 is not only intended for the multi-hop context, as it may also be used for partitioning of messages on an MPC where different pulling partners may access only the messages in the specified sub-channel. Ie. messages on an MPC may be partitioned for different pulling partners based on the sub-channel. With that I propose that the intro paragraph for 3.5 be reworded as follows The sub-channel feature as defined in section 2 of ebMS V3 Part 2 ( [ebMS3ADV] ) MAY be supported by an AS4 MSH either for partitioning messages for different pulling partners and/or for routing purposes in a multi-hop context. If used in a multi-hop context, the sub-channel feature applies to a sending AS4 MSH in the same way as it applies to the edge intermediary as described in ebMS V3 Part 2.