<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>On 2 May 2018, at 22:39, teor <<a href="mailto:teor2345@gmail.com">teor2345@gmail.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div><blockquote type="cite"><div><div dir="ltr"><div><div>> Tor accepts zero bandwidths, but they trigger bugs in older Tor<br>> implementations. Therefore, implementations SHOULD NOT produce zero<br>> bandwidths. Instead, they SHOULD use one as their minimum bandwidth.<br></div></div></div></div></blockquote><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">And if there are zero bandwidths, the parser MAY ignore them.</span></div></div></blockquote><div><br></div><div>Bandwidth files also need to respect MaxAdvertisedBandwidth and</div><div>RelayBandwidthRate/Burst. We need to specify that the relay descriptor</div><div>bandwidth rate and burst should limit the bandwidths in the file.</div><br><div>Torflow supports <span style="background-color: rgba(255, 255, 255, 0);">MaxAdvertisedBandwidth by putting relays in partitions</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">that match their bandwidth. Maybe it also does some other adjustments.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">sbws can probably just do a min() using the measured bandwidth:</span></div><div><a href="https://github.com/pastly/simple-bw-scanner/issues/155">https://github.com/pastly/simple-bw-scanner/issues/155</a></div><div><br></div><div>For details, see:</div><div><a href="https://trac.torproject.org/projects/tor/ticket/8494#comment:5">https://trac.torproject.org/projects/tor/ticket/8494#comment:5</a></div><div><br></div><div>T</div></body></html>