5 ms·
Dave Mills has died
- pushedx 3y agoWe get the news from Vint Cerf himself. Thanks Dave, rest in peace.
- gala8y 3y agoGiants. Seriously, I get this vibe when looking at all these people, the early internet culture. Sometimes I feel as if I was there... or rather really wanted to be.
- mista2nith 3y ago[dead]
- andrewl 3y agoMore about him: https://en.wikipedia.org/wiki/David_L._Mills https://en.wikipedia.org/wiki/David_L._Mills
- m463 3y agoI just imagine all the ntp daemons becoming falsetickers for a moment
- ajdude 3y agoI had the opportunity to meet him at UD earlier last year, very bright man who was still actively working on many things.
- thinkerswell 3y agoHis talk on the early internet https://youtu.be/08jBmCvxkv4?feature=shared https://youtu.be/08jBmCvxkv4?feature=shared
- move-on-by 3y agoI’ve recently gotten very into NTP with GPS and PPS as a fun personal project. Just a couple weeks ago I was reading about him on Wikipedia and I could relate to this quote (as no one else I’ve talked to about PPS has shown any interest): > he enjoyed working on synchronized time because no one else was working on it, giving him his own "little fief" Debian recently switched to NTPSec, and I was happy to see how familiar their website style was to the main NTP site. In the FAQ I found: > [Q] Why do these web pages look so 1990s > [A] Because that simple look is good for people with visual impairments, and as a tribute to Dr. David Mills, the original architect of NTP who is himself visually impaired. Dr. Mills has very particular ideas about Web visuals, and this site is carefully styled to resemble his NTP documentation pages. I’ve never had an opportunity to meet him, but he has certainly made a positive impact on my life. Rest in peace Dr. Mills.
- geerlingguy 3y agoSame here, getting into PTP, you end up studying a lot about timing on computers, and Dr. Mills is one of the main players in building up modern timing foundations! RIP, and thanks for all your contributions!
- icehawk 3y agoHe really was. I remember encountering him on comp.protocols.time.ntp two decades ago and the breath of knowledge he had on computers keeping time was astounding, both at the time, and now that I look back at it.
- parker-3461 3y agoWhich NTP site are you referring to? I’m keen to check out some examples.
- liamwire 3y agontpsec.org
- 3y ago
- nixgeek 3y agoAnother black ribbon day for HN. RIP Dr Mills. The internet wouldn’t be the same were it not for you.
- wyclif 3y agoOught to be a black ribbon for Dave Mills...
- wannacboatmovie 3y agoThey tried to apply the ribbon for a time, but the server's clock was wrong.
- rvz 3y agoThere should be one for Dave Mills. Another legend that deserves recognition for the foundations of the internet that hundreds of millions use today. RIP Dave Mills.
- pjsg 3y agoThis is sad news. I worked (a little bit) with him when I added the adjtime system call to linux back in the 0.99 days.... He built stuff that worked and is run everywhere. That is a great legacy. He will be remembered.
- thrdbndndn 3y agoJust curious: what is 0.99 in this context?
- eimrine 3y agoAlmost sure this is the linux kernel version.
- ugh123 3y agoAccording to wikipedia, this is circa '92 era https://en.wikipedia.org/wiki/Linux_kernel_version_history https://en.wikipedia.org/wiki/Linux_kernel_version_history
- pjsg 3y agoYes -- that is right. Back in those days, you could build the linux kernel from scratch on a laptop with 16MB of memory! I used to commute (on a weekly basis) from Boston to NYC, and you could build and boot and test a kernel between taking off from Logan airport and landing in La Guardia! I can't recall the vendor of the laptop that I used, and the internet is indicating that maybe the 16MB was an overestimate. I think that the adjtime call went in in Linux 0.99pl15 (there were different numbering conventions back then).
- flopsamjetsam 3y agoI first got Linux (Slackware) around about that time. I had a desktop with 4MB (later with 8), so I'd say 16MB in a laptop would've probably not been right too. I remember the interesting "plXX" patch numbers too.
- deleted 3y ago[deleted]
- shadowbanned4 3y ago[flagged]
- Jtsummers 3y agoNo. It's been more like "Pioneers of our industry are dying as they are now largely in their 70s, 80s, and 90s." If you don't know who they are, then either you're not part of the computer and software industry (fine), or you should take this as an opportunity to learn about the industry you're participating in rather than celebrating your own ignorance.
- tobinfekkes 3y agoIt is likely due to people who had their "prime" years overlap with early computing years. Add 30, 40, or 50 years, and you have people we've never heard of in their 80s and 90s that built the foundation we enjoy today. Or as they say, "standing on the shoulders of giants".
- shadowbanned4 3y ago[dead]
- packetslave 3y agoEither spend 10 seconds on Google, or show some respect by being silent.
- looopTools 3y agoThank you Dave! Rest in peace
- briHass 3y agoTook a class of his at University of Delaware around the turn of the century. He was a great professor that clearly had a love for the subject. NTP was much more complex and nerdy than some of the other trivial protocol RFCs, especially by v3 (https://www.rfc-editor.org/rfc/rfc1305 https://www.rfc-editor.org/rfc/rfc1305), which was the first one I read. A legend; RIP
- mbrevoort 3y agoSame, I took several of his classes in the late 90’s at UD. I remember him fondly. RIP
- 299332jUUdd 3y agoI had professor Mills in the mid 90s. He knowledge and application of hardware and software was truly impressive. A true hacker (In the finest sense of the word). RIP
- jimmytucson 3y agoThe New Yorker published a piece on Network Time Protocol a little more than a year ago[0] - highly recommend it to anyone interested in how the internet works. RIP Dave, and thank you. [0] https://www.newyorker.com/tech/annals-of-technology/the-thorny-problem-of-keeping-the-internets-time https://www.newyorker.com/tech/annals-of-technology/the-thor...
- jwilk 3y agoDiscussed on HN back then: https://news.ycombinator.com/item?id=33131195 https://news.ycombinator.com/item?id=33131195 (41 comments)
- phkamp 3y agoHe influenced my career as much as Dennis and Ken did. Our "nanokernel" paper brought NTP into the nanosecond domain and gave FreeBSD "timecounters". But our true shared passion was Loran-C Dave even invented the 16-pulse "tactical Loran-C" during the Vietnam War. I borrowed his ISA card Loran-C receiver (serial #1 & only) and later I built two generations of SDR receivers, and he was so proud when I showed him this dancing pulse received with a cheap ARM chip: https://phk.freebsd.dk/AducLoran/animation2.gif https://phk.freebsd.dk/AducLoran/animation2.gif And boy was he pissed when USA shut down Loran-C, he really loved his "loudenboomers" RIP
- TedDoesntTalk 3y agoWhat is the difference between Loran-C and tactical Loran-C? I googled "loran-c vs tactical loran-c" but did not come up anything. Thanks.
- phkamp 3y agoTactical Loran, also known as "Loran-D" was a concept Dave was involved in during the Korea war. There's a pdf about it somewhere on the web. Remember: This is way before GPS, so pilots could not just look at an instrument and know where their plane was, and many planes, both civil and military would regularly get lost (in the meaning: loose track of where they were). In friendly skies you could have your own Loran-C, but you couldn't expect the enemy to provide that for you, so "tactical" meant that you could rig up a naviation chain where you needed it, in a matter of days. (In the end both USSR and China set up Loran-C chains, some of them operating jointly with the US chains, and today the Rusian "Chayka" and possibly the chinese chains are the only ones left.) So tactical Loran was basically Loran-C transmitters in containers or trucks, and because they would be much weaker than real Loran-C, being both power constrained and having much smaller antenna, they used a 16 pulse code instead of an 8/9 pulse code. Loran-C&D is spread-spectrum transmission, but decades before the theory was fleshed out, but it was well understood that a longer pattern would improve S/N. But Loran-C/D was just one of many DoD radionav systems that project 621B (=GPS) was supposed to kill, and eventually did kill.
- Animats 3y agoI hadn't heard from him in decades, but I knew him back when TCP/IP was starting up and his Fuzzballs were used as routers. John Nagle
- junon 3y agoAre you John Nagle, of the Nagle algorithm?
- mrspuratic 3y agohttps://news.ycombinator.com/item?id=9048947 https://news.ycombinator.com/item?id=9048947
- kristianp 3y agoFuzzballs? https://en.wikipedia.org/wiki/Fuzzball_router https://en.wikipedia.org/wiki/Fuzzball_router The Fuzzball paper: https://dl.acm.org/doi/pdf/10.1145/52324.52337 https://dl.acm.org/doi/pdf/10.1145/52324.52337
- fagnerbrack 3y agoSad day for the Internet, Rest in Peace David L. Mills , and that time keeps going on forever to you and your energy to be felt across time and space. I'm sure the artifacts of your work will never be forgotten. ---- On a sidenote Last year I had a chat with one of the members of the early Web and we understood there's a serious issue of knowledge transfer to future web devs generations. Few people reads books, and even if they do, the books written by technical people are not pedagogical enough as to allow the reader to capture the Tacit Knowledge and experience from the author as to be able to reproduce new ideas. We are LOSING fundamental knowledge of the internet for every mind who dies. If you think that mailing lists, web archives, books and blog posts are enough then you're being naive. At some point nobody will understand how the Web works. The curve where the Web is going is not pretty. This is extremely troubling to me and I'm trying on the sidelines to have some sort of way to run Tacit Knowledge extraction from those ppl. Known techniques are ACTA and CTA (Advanced Cognitive Task Analysis and Cognitive Task Analysis). If you have any other idea, please let me know.
- wyclif 3y agoWhat can we do to stop this erosion of knowledge?
- toomuchtodo 3y agoReach out to folks who are in the last chapter of their life and collect the knowledge, Story Corps [1] meets ArchiveTeam. Interview them, create or add to their Wikipedia page and upload other artifacts to the Internet Archive. [1] https://storycorps.org/ https://storycorps.org/
- fagnerbrack 3y agoThat and CTA/ACTA. Extract Their Tacot Knowledge using those techniques and convert them into simulations that can be use to mentor/teach new engineers with the WHY they did what they did by putting them in their actual shows. Nobody has done that as far as I know
- 3y ago
- zoobab 3y agoNo NTP means no crypto. Most of crypto cyphers nowadays relies on having both computers in sync clock wise. I learned it the hard way with openwrt routers disconnected from the internet.
- Retr0id 3y agoNot exactly, timestamps only commonly matter for handling certificate expiry, and you'll still be fine if you're a few minutes out.
- abricq 3y agoIf someone is interested, here is the Reference and Implementation Guide of the latest NTP version (2006, was revised in 2010), written by Dave Mills: https://www.eecis.udel.edu/~mills/database/reports/ntp4/ntp4.pdf https://www.eecis.udel.edu/~mills/database/reports/ntp4/ntp4... Quite well written, in my opinion.
- CarRamrod 3y agoIf I could save time in a protocol The first thing that I'd like to do Is to save every day 'Til eternity passes away Just to spend them with you
- hnwizard 3y agoExtraordinary wizards. Founding fathers. True legends. RIP
- paulsutter 3y ago[flagged]
- redog 3y agoCould have? Sounds like the bar lowering. What's your PhD in?
- mhandley 3y agoI met Dave a few times in the 90s, first when he was visiting Peter Kirstein at UCL. I'd taken network time as simple to get right until that evening chatting with him in the pub. Fascinating discussion of what can go wrong - and a lot of patience with a young networking researcher who didn't know what he was talking about. I've had a high respect for the attention to detail he embedded in NTP ever since. RIP.
- cornflake23 3y agoTruly a sad event. I never met him but found his work to be so well explained, even in writing and practice. Wrote him an email once and got an informative and kind response. Highly recommend folks to read his website to get to know how to write well and convey complexity in detail, as a story.
- sremani 3y agoI took his class @ University of Delaware in 2002. R.I.P Professor Mills.
- NelsonMinar 3y agoDave Mills was helpful to me as a student. I did some research into NTP in 1999. I knew a little bit about it but not a lot and I said and did a lot of brash things (including sending query packets to every NTP server on the Internet). In response to my random poorly written mailing list and questions Dave answered me and gave me some useful pointers. I felt a little like I was talking to a celebrity. NTP is a remarkable technology. Getting millisecond synchronization out of megahertz computers and barely-megabit computers was not easy. Honestly I'm not sure I would have thought it was even possible until I read the papers explaining how it worked. And Mills didn't just make it on his own, he helped create a small community of timekeeping experts on the Internet that persists to this day.
- kabdib 3y agoI enjoyed his writeups about the fuzzballs back in the day, I learned a lot and had fun doing it.
- DamonHD 3y agoI contributed to NTP. The manufacturers of the cheap device I cajoled within ntpd into generating more than an order of magnitude more precision than they expected offered me decent money to write them a commercial driver. But I pointed out that they could just steer their customers towards NTP for most platforms and it was already done!
- dadadad100 3y agoI’ve never looked at NTP so I followed a link here to RFC 1305. I found this gem of humility. > Note that since some time in 1968 the most significant bit (bit 0 of the integer part) has been set and that the 64-bit field will overflow some time in 2036. Should NTP be in use in 2036, some external means will be necessary to qualify time relative to 1900 and time relative to 2036 The 2036 problem is fixed in RFC 5905 as there is no doubt it will be needed.
- KomoD 3y agoWas there no black bar? Or did I miss it?
- stevenAthompson 3y agoThere should be. Mods are asleep.
- chrisweekly 3y agoFTR, the black bar atop the site header (as of Fri 01/19 at 10p ET) is intended to honor Dave Mills. See also https://news.ycombinator.com/item?id=39063870 https://news.ycombinator.com/item?id=39063870
- Alifatisk 3y agoI discovered NTP through Computerphile & Tom Scott. What a great invention.