above interactions. This is why in the protocol calls the participating sides "requester" and "responder" while the above interactions are called "request streams" or simply "requests". These are the Request-Stream and Channel, back pressure signals travel between requester and responder, allowing a requester to slow down a responder at the source, hence reducing reliance on network layer congestion control REQUEST_CHANNEL, or REQUEST_FNF. Each of those frames carries one message from the requester to the responder. The responder may then return PAYLOAD frames with response messages, and in the case of REQUEST_CHANNEL

above interactions. This is why in the protocol calls the participating sides "requester" and "responder" while the above interactions are called "request streams" or simply "requests". These are the Request-Stream and Channel, back pressure signals travel between requester and responder, allowing a requester to slow down a responder at the source, hence reducing reliance on network layer congestion control REQUEST_CHANNEL, or REQUEST_FNF. Each of those frames carries one message from the requester to the responder. The responder may then return PAYLOAD frames with response messages, and in the case of REQUEST_CHANNEL