News for hackers. Stuff that matters.
Re:FAA lifted National Ground Stop at 0119Z by sneak on Friday November 13, 2026 @10:28PM (#50493510)
TBH TDM is far superior and it’s sad that the world discarded it. Packet switching is the worst thing to ever happen to phone calls. Kids today have no idea how good it used to be (albeit at $0.50/min).
Re:FAA lifted National Ground Stop at 0119Z by locusofself on Friday November 13, 2026 @10:38PM (#50493576)
I mean the fidelity of modern mics/converters/codecs in devices now is much better, but ya the tradeoff of VoIP is latency/jitter/dropouts etc
Re:FAA lifted National Ground Stop at 0119Z by doctorshady on Friday November 13, 2026 @11:03PM (#50493784)
TDM only implies (in the traditional 8-bit framing format, at least) that you're giving a 64 kbps timeslot to a caller. You can put any arbitrary payload in there, like AAC, Opus, or whatever. Preferably a codec without an intrinsic lookahead delay though. You can bond multiple 64k timeslots too.

Glad someone else appreciates circuit switched technologies though :) . It really does shine in any application that isn't burst-y data transfers.

Re:FAA lifted National Ground Stop at 0119Z by adgjlsfhk1 on Friday November 13, 2026 @11:46PM (#50494031)
has there been work on good real time audio codecs? I wonder how good you can do if you limit yourself to a latency of <1 sample?
Re:FAA lifted National Ground Stop at 0119Z by hdgvhicv on Saturday November 14, 2026 @04:33AM (#50495507)
Professional audio works in profiles down to 125us packets, so at 48khz that’s 6 samples per packet. For IP/Ethernet that means 18 byte payload translating to 76 byte Ethernet after the various headers, and another 20 bytes of preamble. That’s 800ns at 1gbit.

if you’re using IPv6 (nobody does) that increases another 20 bytes.

You’d typically have a receive buffer in the 1ms range though , although in theory you’d get away with 500us or even 375us on paper.

I believe (not really my area, in video we deal with timings starting in the tens in the tens of microseconds, and quantisation in the milliseconds) the rule of thumb is the total system latency between microphone and speaker have to be all within 5ms to avoid problems

Re:FAA lifted National Ground Stop at 0119Z by jpc0 on Saturday November 14, 2026 @06:03AM (#50496007)
Exactly this but it is still running on the age old RTP stack with raw PCM packets.

Using FPGAs you can get to very low latency.

Also at some point the latency is a non-issue.

Speed of light even in fiber optics is significantly faster than the speed put sound.

And compared to TDM which is the comparison here the only thing added in packet networks latency wise is buffers, for network switches that can be nearly instant so it is only on the send and receive side.

So pretty much if you want to drop dark fiber between endpoints you can get the exact same benefits of TDM on packet switched networks without the disadvantages.

The people asking for TDM are ignoring the fact the literally several industries and some that care greatly about audio quality and latency have prettier much determined that packet switched networks are fine.

Re:FAA lifted National Ground Stop at 0119Z by kevin_nisbet on Saturday November 14, 2026 @02:09AM (#50494761)
> Glad someone else appreciates circuit switched technologies though :) I worked on VoLTE, the amount of twisting we had to do to make the packet network work kinda-sorta like the circuit network was interesting. Overall I think it was a win to make voice another service, but it was a huge investment.
Re:FAA lifted National Ground Stop at 0119Z by xnx on Friday November 13, 2026 @11:05PM (#50493793)
It was painful not having full duplex calls for so long.
Re:FAA lifted National Ground Stop at 0119Z by meonkeys on Saturday November 14, 2026 @10:49AM (#50497963)
This! Full duplex felt so much more like a warm, live conversation. Talking in person can overlap a lot, in a Good way.
Re:FAA lifted National Ground Stop at 0119Z by FabHK on Saturday November 14, 2026 @12:50AM (#50494391)
Fact: With the good old phone (POTS), when it rang you picked up and said "hello" and started talking. It just worked.

Now, on many calls, the first few seconds are spent on "Do you hear me? Hello? Yes I hear you.". (At work, we call it the Microsoft Teams Random Number Generator - every call gives you one bit with around 50/50 chance (aka one bit)).

Re:FAA lifted National Ground Stop at 0119Z by hylaride on Saturday November 14, 2026 @10:03AM (#50497581)
To be fair, that usually has nothing to do with the network and 99% to do with operating system permissions and mute, microphone, or bluetooth issues.
Re:FAA lifted National Ground Stop at 0119Z by jjtheblunt on Friday November 13, 2026 @11:07PM (#50493800)
wait what? show me the data.

by far the clearest phone calls i've ever been on which were not landline were 2001 era Sprint CDMA, probably because the vocoder bitrate was higher than in later configurations (like LTE), or the MOS scores were held to a higher standard then.

Re:FAA lifted National Ground Stop at 0119Z by novok on Saturday November 14, 2026 @12:39AM (#50494340)
It's really enshittification / phone quality shrinkflation because most normies are not able to articulate what the differences are. Proper QoS, prioritization and bit rate at full duplex would've still worked.
Re:FAA lifted National Ground Stop at 0119Z by bdamm on Saturday November 14, 2026 @01:23AM (#50494545)
Sprint's "pin drop" ads were bold.

Phones of old could be high quality, and they were always extremely low latency. But usually they were scratchy or muffled or noisy or otherwise compressed. A Teams call on a low-latency low-loss line with good microphones on each side is a far better experience than any long distance call from the 90's. It's just that normally the data connection is not so good.

Re:FAA lifted National Ground Stop at 0119Z by epcoa on Saturday November 14, 2026 @04:07AM (#50495366)
Calls within and across major networks in the US are crystal clear HD voice (16 kHz sampling) with a decent codec. CDMA of yore was never that good.
Re:FAA lifted National Ground Stop at 0119Z by trollbridge on Saturday November 14, 2026 @10:49AM (#50497970)
Latency used to be a lot better though.
Re:FAA lifted National Ground Stop at 0119Z by Animats on Friday November 13, 2026 @11:08PM (#50493802)
How do you "overload" a TDM system? It's just a multiplexer that turns one wideband link into N lower bandwidth links by bitwise interleaving. You can't "overload" it. Whatever assigns links might be overloaded, and that's usually something like a telephone switch.

There's an unverified mention of a fiber cut, which might result in fewer circuits being available. That usually returns an "all circuits busy" signal.

None of the explanations will make sense until they stop coming from unqualified political appointees.

Re:FAA lifted National Ground Stop at 0119Z by dboreham on Friday November 13, 2026 @11:27PM (#50493931)
It's probably not TDM end to end nowadays. If they're backhauling it via MPLS or similar then loss of fiber capacity might render the legacy link inoperable.
Re:FAA lifted National Ground Stop at 0119Z by stackghost on Saturday November 14, 2026 @12:38AM (#50494334)
>How do you "overload" a TDM system? It's just a multiplexer that turns one wideband link into N lower bandwidth links by bitwise interleaving. You can't "overload" it.

A TDM system can't have infinite throughput, can it? Either you operate with fixed slot windows, as legacy systems usually do, in which case excess data has to wait and buffers fill up, or else you operate with variable time slots, and at some point the windows get too narrow to transmit usable information.

It doesn't make sense to me to claim you "cannot overload" a TDM system. Bandwidth is finite.

Re:FAA lifted National Ground Stop at 0119Z by axus on Saturday November 14, 2026 @12:45AM (#50494368)
Maybe busy signals that prevent new calls from connecting instead of packet loss / disconnections. Kids these days have never heard a busy signal.
Re:FAA lifted National Ground Stop at 0119Z by vel0city on Saturday November 14, 2026 @11:48AM (#50498456)
If clients are failing to connect because the link has no more capacity, isn't that an "overloaded" failure mode?
Re:FAA lifted National Ground Stop at 0119Z by stackghost on Saturday November 14, 2026 @03:25PM (#50500467)
> Kids these days have never heard a busy signal.

Busy signals are literally a capacity limit being hit.

Re:FAA lifted National Ground Stop at 0119Z by crackez on Saturday November 14, 2026 @05:11PM (#50501502)
I'm most cases, a capacity of one... Eg. the callee (destination) is already on an active call.
Re:FAA lifted National Ground Stop at 0119Z by red75prime on Saturday November 14, 2026 @01:16AM (#50494516)
> Kids today have no idea how good it used to be

Ah, the glorious 3kHz frequency range of old.

Re:FAA lifted National Ground Stop at 0119Z by sneak on Saturday November 14, 2026 @10:07AM (#50497615)
…that never had 100-5000ms audio dropouts once a call was connected. I’d take that any day over the public IP network.
Re:FAA lifted National Ground Stop at 0119Z by wyager on Saturday November 14, 2026 @01:25AM (#50494561)
You can still pay for dedicated TDM internet slots if you're a corporate customer on a shared PON or something. Unfortunately there's not much consumer demand for figuring out how to make this work smoothly for consumer telephony via QoS tiers or something.
Re:FAA lifted National Ground Stop at 0119Z by mirmor23 on Saturday November 14, 2026 @01:53AM (#50494681)
> TBH TDM is far superior and it’s sad that the world discarded it. Packet switching is the worst thing to ever happen to phone calls.

Your feelings here have no technical basis. TDM is pre-provisioned, bandwith-reserved, latency-capped network that was probably hard for packet switched network 25 years ago. But with all that has gone in -- switched ethernet, qos, oam -- there is absolutely no reason to go back. Heck, even whatsapp calls across 12-hour time zones are quite crisp and free.

Re:FAA lifted National Ground Stop at 0119Z by ucyo on Saturday November 14, 2026 @02:27AM (#50494850)
Because you mentioned WhatsApp. There is an interesting podcast about the Western Electric 500 phones and the architecture of actual phone lines. There is a section where they compare it to WhatsApp and time delay. Maybe of interest…

https://pca.st/episode/a12e4bb6-4e1f-4b57-8f1c-b627b4275869

Re:FAA lifted National Ground Stop at 0119Z by Karrot_Kream on Saturday November 14, 2026 @03:18AM (#50495136)
Ooh cool podcast link, thanks for the rec. Surprised I didn't catch a 99% Invisible podcast on one of my favorite topics.

Good to remember that a WhatsApp call is being routed over a much more diverse, heterogeneous set of networks than a Western Electric 500 phone was. 32-bit stereo raw audio is roughly 2.82 Mbps, which is a lot better than what an older phone did. On any link between two endpoints with 20 Mbps or more symmetric, you can do this trivially. WhatsApp can give you good performance between two crowded venues on completely different parts of the world. Just a very different experience.

Re:FAA lifted National Ground Stop at 0119Z by throw0101d on Saturday November 14, 2026 @07:44AM (#50496591)
Re:FAA lifted National Ground Stop at 0119Z by mirmor23 on Saturday November 14, 2026 @10:20AM (#50497730)
> There is an interesting podcast about the Western Electric 500 phones and the architecture of actual phone lines.

Thank you! learnt about Henry Dreyfuss. It's sad the way he died, but can understand.

https://en.wikipedia.org/wiki/Henry_Dreyfuss

Re:FAA lifted National Ground Stop at 0119Z by stingraycharles on Saturday November 14, 2026 @03:28AM (#50495187)
Yeah as someone who has video calls across the globe every day, it’s absolutely fine as long as your internet provider doesn’t cheap out on provisioning / uplinks. But in the end that’s a “you get what you pay for” issue.
Re:FAA lifted National Ground Stop at 0119Z by eecc on Saturday November 14, 2026 @03:57AM (#50495318)
Codecs are exceptionally good at adapting to available bandwidth and latency.

What kills realtime is buffer bloat

Re:FAA lifted National Ground Stop at 0119Z by vlan0 on Saturday November 14, 2026 @07:08AM (#50496382)
Right, hence their comment about uplinks. They cheap out, that saturates, then we buffer
Re:FAA lifted National Ground Stop at 0119Z by stingraycharles on Saturday November 14, 2026 @07:53AM (#50496638)
bufferbloat is actually more than that; it’s actually that the buffers are oversized, which is typically not what you want. This causes a lot of jitter and increases latency.

basically, for realtime stuff, you want to prefer packets being dropped rather than buffered.

this is an excellent resource on the subject: https://www.bufferbloat.net/projects/bloat/wiki/Introduction...

Re:FAA lifted National Ground Stop at 0119Z by jacquesm on Saturday November 14, 2026 @12:57PM (#50499175)
And it makes echo cancellation terrible.
Re:FAA lifted National Ground Stop at 0119Z by crackez on Saturday November 14, 2026 @05:07PM (#50501473)
That's why auto_qos was invented...
Re:FAA lifted National Ground Stop at 0119Z by jd3 on Saturday November 14, 2026 @09:42AM (#50497395)
zero latency and no jitter
Re:FAA lifted National Ground Stop at 0119Z by mirmor23 on Saturday November 14, 2026 @10:14AM (#50497674)
> zero latency and no jitter

this would beat the laws of physics. realistically, it is more like "fixed latency, and very little jitter".

Re:FAA lifted National Ground Stop at 0119Z by cryptonector on Saturday November 14, 2026 @04:05PM (#50500806)
Zero _extra_ latency. It's like 'no sugar added' but the food is sweet anyway, just less sweet than if sugar had been added.
Re:FAA lifted National Ground Stop at 0119Z by e12e on Saturday November 14, 2026 @11:39AM (#50498375)
> Heck, even whatsapp calls across 12-hour time zones are quite crisp and it is free

I don't think anyone seriously think that 5g and VoIP voice quality is bad - but latency is absolutely a problem, especially in group calls.

Re:FAA lifted National Ground Stop at 0119Z by willis936 on Saturday November 14, 2026 @12:39PM (#50498982)
I mean, there is technical basis. This is a classic latency vs. throughput tradeoff. Obviously reserving most the channel for quiet lines is not good for throughput, but it does work wonders for worst case latency. Bandwidth reservation is not without merit.
Re:FAA lifted National Ground Stop at 0119Z by Karrot_Kream on Saturday November 14, 2026 @03:03AM (#50495039)
Definitely think circuit switching has merit for real time comms even today, but that's a separate discussion. Over physically private links, whether you're using MPLS or TDM shouldn't matter.
Re:FAA lifted National Ground Stop at 0119Z by hdgvhicv on Saturday November 14, 2026 @04:20AM (#50495435)
MPLS typically wouldn’t be physically private, no more than any other IP network, just a different forwarding technology. You can run MPLs over ip networks and ip networks over MPLs.

I have everything from dedicated inter building fibre cables, through cores, wavelengths, ethernet services, IP circuits (still have one international MPLS and a VPLS network eoth 4 exit nodes), to normal internet with varying levels of contention.

Even the fibres aren’t private - they are patched through other people’s equipment rooms, even on short runs if a few miles, and even on the circuits that don’t, they run through ducts over other people’s land.

Packet switching has variable latency. This can be controlled with ptp and qos, and in reality we’re talking sub microsecond differences if you need it, switch latency is measured in nanoseconds And that’s way below the timing ministry is worried about (which is in the tens of microsecond level). TDM will give you guarenteed latency though, you get a slot every X time units regardless, jitter isn’t 2us, it’s zero.

I don’t believe any application needs sub microsecond jitter, but there may well be some scientific applications that do, but at that level you’re running on dedicated cores or maybe wavelengths, between specific equipment.

Re:FAA lifted National Ground Stop at 0119Z by Karrot_Kream on Saturday November 14, 2026 @05:11AM (#50495708)
What stack do you think the FAA is using? I would expect they have private links but maybe I'm wrong.
Re:FAA lifted National Ground Stop at 0119Z by hdgvhicv on Saturday November 14, 2026 @06:50AM (#50496266)
They don’t own the land the fibres run on, I suspect that many will be patched through exchanges and data centres they don’t own.

It won’t surprise me ifs y places are services provided by other companies - either ip or ethernet, to connect to larger sites. I suspect some will even be connected via public networks.

Major sites may have dedicated fibres between them but whether that’s just a wavelength on someone else’s core, or even a dark fibre but just one core on someone else’s cable, is anyone’s guess. I’d be surprised if they could justify the cost of a highly resilient network dedicated to themselves rather than renting capacity.

What I’m certain is they don’t own their own fibres to every end point.

Re:FAA lifted National Ground Stop at 0119Z by Karrot_Kream on Saturday November 14, 2026 @09:44PM (#50503482)
Thanks for the context. I've never touched the physical end of this industry, so this is good info.
Re:FAA lifted National Ground Stop at 0119Z by hylaride on Saturday November 14, 2026 @10:00AM (#50497555)
The FAA is using a mish-mash of tech, because it's been layered on over the years and is constantly starved of funds and investment because it's a government agency that needs congress to sign off on changes. Some network links are modern fibre optic lines, while others are still over decades old copper. Canada's ATC provider, NAV Canada, is not a direct government agency but a regulated nonprofit funded by fees - so it has the ability to modernize as it makes sense. The US still largely uses Radar and voice instead of satellites and data links that Canada moved to decades ago! The story is similar in other western jurisdictions that have modernized long ago.

Some US airports (~90) are still using paper flight strips while other jurisdictions long ago moved on: https://enotrans.org/article/electronic-flight-strips-brief-...

Re:FAA lifted National Ground Stop at 0119Z by Karrot_Kream on Saturday November 14, 2026 @09:45PM (#50503491)
Yeah I'm aware of some of this through the woes of ATC modernization. Sadly I didn't know anything about how NAV Canada was a nonprofit funded by user fees. I know a lot of folks in the US oppose privatization of ATC, but this is an interesting example. Thanks!
Re:FAA lifted National Ground Stop at 0119Z by adrian_b on Saturday November 14, 2026 @12:41PM (#50499002)
The difference between TDM and packet switching is the same as between static memory allocation and dynamically allocating heap memory.

If you can afford to allocate statically the space for all the variables that your program will ever use, you will certainly increase a lot both the performance and the reliability of your program.

Alas, for many tasks this would result in a requirement for more memory than you can afford, especially today.

To use more efficiently the limited amount of memory that you have, you need to use dynamic memory allocation.

The same happens with your communication infrastructure. Using it with packet switching reduces the reliability and the performance of individual communications, but it uses the capacity much more efficiently, i.e. the aggregated throughput of all communications passing through a given infrastructure is greatly increased.

Re:FAA lifted National Ground Stop at 0119Z by boznz on Saturday November 14, 2026 @12:43PM (#50499029)
[delayed]
Re:FAA lifted National Ground Stop at 0119Z by miki123211 on Saturday November 14, 2026 @01:26PM (#50499430)
I think the superiority of TDM is diminished if there's a wireless link somewhere in the mix (and there very often is for modern consumer tech).

TDM was more stable because nobody was hopping on meetings while walking their dog on a noisy street and then taking the elevator back home. The expectations have shifted.

Modern consumer links (even over WiFi) are usually adequate enough to do reliable, high-quality voice calls over the public internet. We basically choose not to; most VOIP apps are optimized to work decently in a noisy car driving through a forest when on speakerphone, instead of working very well in a quiet room on headphones and crapping out everywhere else. This is a choice we make; there are apps out there that make different choices. Once upon a time, I was very unhappy with that choice, then I grew up and have experienced what the consequences of making different choices really are.

With that said, classical Bluetooth audio urgently needs to die. There's no reason for it to be as bad as it is, and it is truly abhorrent. Better protocol design is definitely possible; most wireless (2.4GHz, gaming) headphones have much better quality and much lower latency. BLE audio will fix most of Bluetooth's warts, and it is slowly, so very slowly appearing on the market.

Re:FAA lifted National Ground Stop at 0119Z by fffrantz on Saturday November 14, 2026 @07:38PM (#50502685)
ISDN calls are of such good quality and so stable that public radios used ISDN links for their reporters in other countries. It still was the norm 15/20 years ago, and now you get awful quality every time someone’s joining a broadcast through Zoom/Teams/etc.