[kevhito]

Instead of adding 3 bits, maybe they should have dropped 3 bits. A rollover every ~20 years is just asking for latent buts to blow up. A rollover every ~2.5 years is just business as usual. Go big or go small. Don't design things to break just after you retire but before your coworkers do.

[Rebelgecko]

OTOH, with the current setup a receiver will know the correct date as long as it is turned on at least once every 1024 weeks, since it can detect the rollover. More frequent rollovers might cause issues with timing on devices that are infrequently turned on. It's sort of a moot point for most of us once there's greater adoption of the L2 and L5 CNAV signals— those use a week counter that won't roll over until most if not all of us are dead. Then it can be someone else's problem :)

[throw0101a]

> OTOH, with the current setup a receiver will know the correct date as long as it is turned on at least once every 1024 weeks, since it can detect the rollover

Actually, probably every 512 weeks, as it needs to know (or assume) with side of the +/- it is on:

* https://en.wikipedia.org/wiki/Serial_number_arithmetic

* https://en.wikipedia.org/wiki/Date_windowing

* https://docs.ntpsec.org/latest/rollover.html#ntp_pivots

[koyote]

I believe that's what GLONASS used as a strategy:

Roll over so often that firmware/software implementations pretty much have to take it into account.