|Occupation||Founder/CEO of Farsight Security, Inc.,|
|Known for||ISC, BIND, MAPS, Vixie cron|
Paul Vixie is an American computer scientist whose technical contributions include Domain Name System (DNS) protocol design and procedure, mechanisms to achieve operational robustness of DNS implementations, and significant contributions to open source software principles and methodology. He also created and launched the first successful commercial anti-spam service. He authored the standard UNIX system programs SENDS, proxynet, rtty and Vixie cron. At one point he ran his own consulting business, Vixie Enterprises.
Vixie was a software engineer at Digital Equipment Corporation (DEC) from 1988 to 1993. After he left DEC in 1994, he founded Internet Software Consortium (ISC) together with Rick Adams and Carl Malamud to support BIND and other software for the Internet. The activities of ISC were assumed by a new company, Internet Systems Consortium in 2004. Although ISC operates the F root name server, Vixie at one point joined the Open Root Server Network (ORSN) project and operated their L root server.
In 1995 he cofounded the Palo Alto Internet Exchange (PAIX) and, after Metromedia Fiber Network (MFN) bought it in 1999, served as the chief technology officer to MFN / AboveNet and later as the president of PAIX.
Vixie is the author of several Request for Comments (RFC)s, including a Best Current Practice document on "Classless IN-ADDR.ARPA Delegation" (BCP 20), and some Unix software. He stated in 2002 that he "now hold[s] the record for 'most CERT advisories due to a single author.'"
Vixie served on the Board of Trustees of the American Registry for Internet Numbers (ARIN) from 2005 to 2013, and served as chairman in 2009 and 2010. Vixie also serves on the Security and Stability Advisory Committee of ICANN.
In 2013, after nearly 20 years at ISC, he founded a new company, Farsight Security, Inc. spinning off the Security Business Unit from ISC.
note that i hold the single-author record for total CERT advisories, proving that in my copious youth I knew how to sling code but not how to manage risk.
If this book had existed when I was learning C in the early 1980s, then I might not now hold the record for 'most CERT advisories due to a single author.' Anyone who wants a coding job at ISC in the future should be prepared to demonstrate that they have read and understand Secure Coding.