On Thu, Oct 31, 2019 at 03:24:50PM +1100, Zenaan Harkness wrote: > On Thu, Oct 31, 2019 at 02:36:27PM +1100, Zenaan Harkness wrote: > > > - When we do achieve internet wide QoS contracts at the network > > > layer, a privacy issue (depending on your threat model) will be > > > which QoS modes to utilize - e.g. you may be better off using > > > "bulk fill", rather than "telephone audio" class QoS, in order to > > > better hide your important phone call. > > > > One way to use bulk fill for real time data, is for links (i.e. peer > > nodes), to simply "maintain excess headroom during requisite (phone > > call) time". > > > > This implies the need to hide a node's (downwards) phys link > > utilization: > > > > - either all nodes always reserve a relevant phys link %, e.g.: > > - 2%, or 10KiB/s, whichever is greater, > > - unless total phys link is less than 30 KiB/s, > > in which case this node must essentially act as a client only > > node (a comparatively unsafe option (presumably)) > > - or, we institute a randomization protocol, so that at one time or > another links are "normally, but randomly" headroom shaped down a > bit > > Again, achieving actual randomness, ain't easy. > > And we must (!) modulo against user requirements as well, every time > we plan to institute some randomization scheme. > > Further, for the use case of phone calls, we are talking randomized > appearance of "headroom shaped routes", and -not- randomized > appearance of "headroom shaped links" - these are similar, but quite > different, things. > > Phone calls require routes. > > If all "usable" links are independent, (link set) intersections > constituting usable links would be greatly diminished - ahh,
s/links/routes/ > probably, since perhaps not - if we consider links between known > friends, where such links (when they randomly appear) can be used as > single hop p2p link for phone calls. > > Maths, especially statistical, set and algebraic math, can be pretty > interesting since it can be so useful. >
