Counter-Argument #1 - This comes up occasionally, and may appear to be a strong (albeit short term) argument for discriminating against peering with Content heavy ISPs. A company can essentially say we can only peer with Access Heavy networks due to backbone links in one direction being saturated. However, keep in mind what this signals to the Internet community: the congestion on the network is or will soon affect the customers of this ISP. Therefore, this ISP can not meet the needs of its customers and is probably delivering poor performance at peak periods. This may signal that you are neither a good peering nor a good transit provider candidate. 

Counter-Argument #2 - This loading problem can best be solved with better traffic engineering, with the allocation of more resources to the backbone, or by temporarily denying peering until the needed upgrades are done. In any case, denying peering based on the peering traffic ratio rationale is the least attractive of all of these other options.