On Sun, Oct 27, 2019 at 11:48:58AM +1100, Zenaan Harkness wrote: > On Sat, Oct 26, 2019 at 05:32:59PM -0400, grarpamp wrote: > > ie: Bittorrent nodes (clients) ignore nodes that send corrupted > > datas... overlays should drop peer nodes that exhibit non > > conformant traffic characteristics... such as unclocked, > > bursty waves, etc that was not agreed to, that would present > > risk to observability. > > "Bursty" anything, without negotiation of graduated/ stepped up/down > link management, must not be permitted in the first instance.
Except of course, where bursty is high bandwidth, low priority traffic which can be buffered and used effectively as a form of chaff fill when higher prio traffic is satisfied. By making such streams a first class citizen (design wise - e.g. low risk torrents), we may find that chaff/wheat ratio ultimately gets really low (i.e., very efficient overall network b/w utilization).
