This read-write INTEGER specifies the maximum number of 256-byte blocks that should be queued up for transmission to a node. An administrator uses this queue-depth limit to protect against unbounded buildup of pending signaling data destined for one particular peer, for example if that peer becomes slow to acknowledge messages. For example, hitting this block limit for a given node would cause the network handler to stop queuing further data to it until existing queued blocks are transmitted.