Re:I'm on the FCC. Please stop us from killing net neutrality
by Retric on Thursday November 23, 2017 @05:11PM
(#15768143)
That's more an abstraction than reality. Frequency hopping means N senders may overlap but the abstraction is independent the IP part of TCP/IP or UDP so the device knows things failed instead of waiting for a timeout on a dropped packet. Thus IP software never sees latency spikes just lowered bandwidth or dropped connections.
Re:I'm on the FCC. Please stop us from killing net neutrality
by Retric on Friday November 24, 2017 @10:14AM
(#15771262)
To clarify, in the past the over subscription might have required dedicated bandwidth for voice but that's no longer the case.
Voice is very low bandwidth as long as the minimum bandwidth per device is over 100 kpbs and the device to prioritize voice data towers don't need to bother with QoS for traffic. They still do this for various reasons, including the fact they are sending the voice data to a separate network not the internet.
TLDR; Total bandwidth / devices > 100kbps and it's not actually over subscribed.
All that being said, that's why cell networks, until 4G, used actual circuits for voice, rather than having it be packet-based; and that's why 4G+ networks use IMS (a layer 1+2+3 protocol suite that all middle boxes are aware of for QoS purposes) rather than just relying on layer-3 https://en.wikipedia.org/wiki/Differentiated_services QoS fields (which are handled by full layer-3 switches within a given LAN, but get dropped the moment the packet crosses onto the public Internet and are just ignored by layer-2 switches.)
(And even on large LANs—like your cable provider's ATM network—DiffServ tags aren't relied upon, because QoS is just so much easier when layers 1 and 2 are aware of it. If you get a IP phone line from your ISP, it'll be using https://en.wikipedia.org/wiki/Multiprotocol_Label_Switching tags instead, to give its packets QoS priority across even the dumbest middleboxes.)