4 ms·
also, what do you count as bandwith? Simply sending packets down a wire usually limits one to the physical speed of the interface, but even then some kind of p
by kazen44 4y ago
also, what do you count as bandwith?
Simply sending packets down a wire usually limits one to the physical speed of the interface, but even then some kind of packets might get dropped by various filters/mechanisms along the way.
For instance, should i be able to use my full bandwith of my connection by sending purely BUM traffic down the link? Somewhere in the network, some policer is going to start dropping BUM traffic to protect the network against flooding.
- pixl97 4y agoI remember years ago working with ISPs and many of their monitoring systems assumed that packet = 1500 bytes as a fixed measure. Running a DNS server at full throttle could lead to a situation where you'd get bandwidth charges for amounts higher than could be served at line rate. I'm assuming modern systems do this better, but I've learned never to make assumptions when they benefit the billing party more.
- kazen44 4y agoit gets even more fun if you think about what people are actually paying for. For instance, do you charge for the overhead of the Ethernet frame? What about additional size thanks to tunneling/encapsulation? One could argue that no, you should not charge a customer for that because that is part of local transport inside a layer 2 domain, which is not in control of the customer. But what about things like MPLS labels? you could go and on and on..