CTOvision.com

Context for the CTO, CIO, CISO and Data Scientist

You are here: Home / Archives for IBM

IBM

IBM Claims Advances In Fully Homomorphic Encryption (and I’m claiming advances in an anti-gravity device)

For years computer scientists have talked about the very interesting challenge regarding the desire to be able to operate over encrypted data in an advanced way called Homomorphic Encryption. This is a field that gets nuanced fast, with terms like “partially homomorphic” relevant to many existing systems that are in place, but Fully Homomorphic thought by many to be so far away to be just a dream.

No computer system on the market today can do fully homomorphic processing. Data might be stored on hard drives encrypted, and might be moved around between computers encrypted, and might even be stored in RAM or moved around places on boards in computers while encrypted.  But when it comes to processing, the data must always be operated on by the computer in the clear. That is just the way computers work. So, while there have been great advances in security, there is always going to be a place in time and space where data is totally unencrypted and therefore, in theory, a malicious actor could exploit this to their advantage. It might be hard to do, but when the data is valuable bad guys always find a way.

Some very interesting research on theoretical implementations is available. As far as I can tell, most working ideas flow from those written by Craig Gentry, an incredibly bright IBM researcher. You can catch him explaining some of his research at the video at this link and below:

It is clear this research is producing some working homomorphic encryption schemes. But I have seen nothing in any of the research that makes me think a solution can be put in place that cannot be defeated by bad guys. And if that can’t be done then the solution will not solve any problems, it will just add processing overhead. So in the end I remain a skeptic regarding any claims of a working fully homomorphic solution.

Said another way, when I read of claims that this can be done I think there must be a catch and wanted to give you that warning before you read the below. I imagine that if this were put to a test by a team of security professionals they would find alarming vulnerabilities. The only thing I have that backs up this assertion is years of experience that says the bad guys can always get in when they try, plus a deep belief that true fully homomorphic encryption can only be done in ways that introduce new vulnerabilities. 

That said, I am providing IBM’s release below, and plan on tracking this and other reporting on this topic:

From: http://ctolink.us/1k2bhfO

Made in IBM Labs: Advancing Privacy and Security in the Cloud

Patented cryptography invention enables unlimited analysis of encrypted data

ARMONK, N.Y. – 23 Dec 2013: IBM (NYSE: IBM) inventors have received a patent for a breakthrough data encryption technique that is expected to further data privacy and strengthen cloud computing security.

The patented breakthrough, called “fully homomorphic encryption,” could enable deep and unrestricted analysis of encrypted information —intentionally scrambled data — without surrendering confidentiality. IBM’s solution has the potential to advance cloud computing privacy and security by enabling vendors to perform computations on client data, such as analyzing sales patterns, without exposing or revealing the original data.

IBM’s homomorphic encryption technique solves a daunting mathematical puzzle that confounded scientists since the invention of public-key encryption over 30 years ago.

Invented by IBM cryptography Researcher Craig Gentry, fully homomorphic encryption uses a mathematical object known as an “ideal lattice” that allows people to interact with encrypted data in ways previously considered impossible. The breakthrough facilitates analysis of confidential encrypted data without allowing the user to see the private data, yet it will reveal the same detailed results as if the original data was completely visible.

IBM received U.S. Patent #8,565,435: Efficient implementation of fully homomorphic encryption for the invention, which is expected to help cloud computing clients to make more informed business decisions, without compromising privacy and security.

“Our patented invention has the potential to pave the way for more secure cloud computing services – without having to decrypt or reveal original data,”  said Craig Gentry, IBM Researcher and co-inventor on the patent. “Fully homomorphic encryption will enable companies to confidently share data and more easily and quickly overcome challenges or take advantage of emerging opportunities.”

Following initial revelation of the homomorphic encryption breakthrough in 2009 Gentry and co-inventor Shai Halevi began testing, refining and pursuing a working implementation of the invention. In 2011, the scientists reported a number of optimizations that advanced their goal of implementing of the scheme. The researchers continue to investigate homomorphic encryption and test its practical applicability.

IBM invests more than $6 billion annually in R&D and consistently explores new approaches to cloud computing that will deliver a competitive advantage to the company and its clients.

For 20 consecutive years, IBM has topped the list of U.S. patent recipients. The company’s invention and patent leadership is illustrated at http://ibm.co/11k6fRn.

IBM has a tradition of making major cryptography breakthroughs, such as the design of the Data Encryption Standard (DES); Hash Message Authentication Code (HMAC); the first lattice-based encryption with a rigorous proof-of-security; and numerous other solutions that have helped advance data security.

More information about how IBM inventors are propelling cloud computing innovations is available at http://ibm.co/174A8tS.

Contact(s) information

Chris Andrews
IBM Media Relations
1 (914) 499-4045
candrews@us.ibm.com

 

Public-Private Information Sharing and Lessons for the Government CIO/CTO

Public-Private Information Sharing, or a varient of that concept, has been a part of federal government strategic plans for as long as I can remember. Every cyber security related study I know of, including the famous 1966 President’s Commission on Critical Infrastructure Protection, has made public-private information sharing a key strategy.  Federal agencies and studies have made important suggestions regarding public-private information sharing part of most every major IT study.  I’ve seen this type of information sharing work very well, but as a technologist I’ve also seen a need for (and urged) improvements to the model.

For example, too frequently the way government executives are forced to do public-private information sharing is through processes that flow from the Federal Acquisition Regulations (FAR).  The FAR mandates market assessments and surveys to be done in ways that do not give one company an unfair advantage over another. This is smart of course, but results in some industrial age information gathering that is not very timely.

Federal technologists also do quite a bit of direct coordination with industry to learn and they do this under the watchful eye of procurement executives to make sure this is all above board, and this sort of coordination with industry technologists is absolutely critical to the smooth functioning of federal enterprises. The executives in DC who make trips to Silicon Valley or great hubs of innovation like Boston or Raleigh or Boulder (home of WayIn) come back with information that can help their strategic planning and this sort of public-private info exchange also helps industry know important things about government mission needs.

But too frequently government is tempted to just ask their local industry reps for info and advice on the future of technology. This is still public-private info sharing, and when budgets get tight is can be incredibly cost effective to just turn to a favored federal systems integrator that you already have on contract and ask them questions and consider this your public-private information exchange. There are many great integrators in the DC area and I know and love them but this is not optimal long term, since most integrators serving government become captured by government and talking to them is almost like talking to yourself.

There are also many non profit collegial organizations and consortia in the federal space that government frequently turns to for public-private information sharing and coordination.  These include many great organizations that I volunteer time with, like the Intelligence and National Security Alliance (INSA), the Armed Forced Computer and Electronics Association (AFCEA), and the National Defense Industrial Association (NDIA).  I volunteer with these groups because I love them and strongly support the positive change they make in the world. But when government turns to these groups for their public-private information exchange it is sub-optimized. They are full of people like me, former government executives who might be easy to talk with but who might not be as up to date with the best information industry has to offer.

Some lucky few government technologists get to interact with In-Q-Tel, a collective of very savvy technology and business professionals who absolutely master the art of surveying industry for best technology. The entire government would be well served if this model were replicated for all. But for now In-Q-Tel cannot serve the entire federal space. And it also serves mostly in the new technology space, not in areas like process, procedure and lessons learned exchanges. In-Q-Tel is only part of a solution.

I always recommend to government friends that they make the most of the great resources American industry has to offer and that includes learning from locals in the DC ecosystem but should also include a program of focused interaction with others far from DC.  You will make great friends doing this and the connections you make can turn into long term trust-based relationships that can help both the government and American industry advance.  Time is precious to all of us, so government executives need to plan how this is done wisely, but periodic visits to the champions of industry like Oracle, Microsoft, IBM, Apple, HP, VMware, EMC, Cloudera, Cleversafe, Terracotta, AT&T and the great Venture Capital and Private Equity firms for reviews of their portfolios are critically important. I’ve also been so fortunate in my career to have spent time with chip makers, security firms, and even great institutions like Disney. It is all a learning experience.

Direct interaction is best for these long term trust based relationships, but when that is hard you can also meet industry online. One great place to do that is through venues like the Enterprise CIO Forum. Since this is a forum backed by CXO Media (the parent company of CIO magazine) it is a well resourced venue that includes a world class community manager (John Dodge).  If you are a CTO or CIO in the federal space you probably already read CIO Magazine. Why not join the Enterprise CIO Forum to interact directly with people from outside the federal ecosystem?

Related Posts:

Changing Government Requirement For Market Research to Continuous Market Assessment

Thoughts on the Government Shutdown: from a technologist perspective

The Role of the CTO: Four Models for Success

Want To Know The Future Of Enterprise IT? Track Venture Capital

I know of only three models that enterprise technologists can use to make accurate predictions of future technology, and all three models have failings.

The first model is to track mega trends in the IT industry. This provides broad insights on topics like Big Data, Cloud Computing, Cybersecurity, Commoditization of IT, Social Media and Open Source Software, but the broad insights this model provides are frequently too general to guide the planning actions of IT professionals.

The second model is to make linear projections on the state of specific categories of IT. Assessments like these can help in the short term by informing IT planners on what to expect in areas like hardware, communications systems, storage systems, analytical tools, development environments, mobile devices and a wide range of other categories. But the problems with linear projections like these is that it is impossible to predict, with accuracy, when the linear trend breaks due to surprise and disruption. Projections like this are important, but they too are flawed.

The third method is to interact with people who are making the future. This is perhaps the best way to predict coming technology disruptions. If you can learn what today’s engineers are developing and if you can get a sense of which of these hold the greatest potential of adding value to the enterprise market it can help IT decision-makers better prepare for the future. The flaw in this model is that entrepreneurs and engineers are not always successful, but in general the Alan Kay observation that “the best way to predict the future is to invent it” holds true.

This third method happens to also be the most fun! Examining this element of the future means you can dive deep into study of the great techno-capitalists of our age. The founders and lead technologists of firms like Microsoft, Oracle, Sun Microsystems, Apple, HP, Dell, IBM continue to innovate and are important to track (and we do so at our Tech Titans list).  But increasingly it is the smaller disruptors that are causing the most change. To find and track these future disruptors we need to follow the investments of the great venture capital (VC) players.

Our interactions with VC have long influenced the firms we write about here and in our CTOlabs.com company directory and we will keep writing about the individual tech companies we believe should be on your radar. But we are also launching a new series of posts on the key VC firms we believe enterprise technologists should be tracking. We have overviews in the works now on:

And others are coming soon!  Stay tuned for more.

To ensure you are on distro for our posts on these and related topics, sign up now for our newsletter distribution at http://j.mp/ctonews

Related Posts:

CTO Guide to the Business of Artificial Intelligence

Blockchain Capital Closes New $150 Million Fund Focused on Crypto Ecosystem

Blockchain Capital: One of the earliest and most active investors in blockchain technologies

 

 

 

A CTO Perspective: Consider The Message The Elders of the Internet Have A Message for the U.S. Congress

The EFF (Electronic Frontier Foundation) was founded in 1990 as a donor funded non-profit with a focus on fighting for internet freedoms. They frequently bring those fights to the courts by bringing lawsuits against large corporations and the government. They also work to provide information to inform legislators and the public at large. The EFF is cool, but of course you don’t have to agree with every position they have ever taken. That said, all in all I have to say I think they are focused on very important principles. In my opinion, their best actions are those where they base their positions on well reasoned technical thought. The letter below is one of these times.

In fact, this may be the most well thought out, well coordinated technical based position they have ever established. In an open letter to the US congress coordinated by EFF’s Parker Higgins and Peter Eckersley, 83 of the Internet’s greatest engineers come together to provide a well reasoned opposition to  SOPA and PIPA Internet blacklist bills.

Thanks EFF.  And thanks for providing your content under the creative commons attribution policy, which makes it so conducive to sharing. That too is nice of you.

This letter is printed below:
From: https://www.eff.org/deeplinks/2011/12/internet-inventors-warn-against-sopa-and-pipa 

An Open Letter From Internet Engineers to the U.S. Congress

Today, a group of 83 prominent Internet inventors and engineers sent an open letter to members of the United States Congress, stating their opposition to the SOPA and PIPA Internet blacklist bills that are under consideration in the House and Senate respectively.

We, the undersigned, have played various parts in building a network called the Internet. We wrote and debugged the software; we defined the standards and protocols that talk over that network. Many of us invented parts of it. We’re just a little proud of the social and economic benefits that our project, the Internet, has brought with it.

Last year, many of us wrote to you and your colleagues to warn about the proposed “COICA” copyright and censorship legislation. Today, we are writing again to reiterate our concerns about the SOPA and PIPA derivatives of last year’s bill, that are under consideration in the House and Senate. In many respects, these proposals are worse than the one we were alarmed to read last year.

If enacted, either of these bills will create an environment of tremendous fear and uncertainty for technological innovation, and seriously harm the credibility of the United States in its role as a steward of key Internet infrastructure. Regardless of recent amendments to SOPA, both bills will risk fragmenting the Internet’s global domain name system (DNS) and have other capricious technical consequences. In exchange for this, such legislation would engender censorship that will simultaneously be circumvented by deliberate infringers while hampering innocent parties’ right and ability to communicate and express themselves online.

All censorship schemes impact speech beyond the category they were intended to restrict, but these bills are particularly egregious in that regard because they cause entire domains to vanish from the Web, not just infringing pages or files. Worse, an incredible range of useful, law-abiding sites can be blacklisted under these proposals. In fact, it seems that this has already begun to happen under the nascent DHS/ICE seizures program.

Censorship of Internet infrastructure will inevitably cause network errors and security problems. This is true in China, Iran and other countries that censor the network today; it will be just as true of American censorship. It is also true regardless of whether censorship is implemented via the DNS, proxies, firewalls, or any other method. Types of network errors and insecurity that we wrestle with today will become more widespread, and will affect sites other than those blacklisted by the American government.

The current bills — SOPA explicitly and PIPA implicitly — also threaten engineers who build Internet systems or offer services that are not readily and automatically compliant with censorship actions by the U.S. government. When we designed the Internet the first time, our priorities were reliability, robustness and minimizing central points of failure or control. We are alarmed that Congress is so close to mandating censorship-compliance as a design requirement for new Internet innovations. This can only damage the security of the network, and give authoritarian governments more power over what their citizens can read and publish.

The US government has regularly claimed that it supports a free and open Internet, both domestically and abroad. We cannot have a free and open Internet unless its naming and routing systems sit above the political concerns and objectives of any one government or industry. To date, the leading role the US has played in this infrastructure has been fairly uncontroversial because America is seen as a trustworthy arbiter and a neutral bastion of free expression. If the US begins to use its central position in the network for censorship that advances its political and economic agenda, the consequences will be far-reaching and destructive.

Senators, Congressmen, we believe the Internet is too important and too valuable to be endangered in this way, and implore you to put these bills aside.

Signed,

  • Vint Cerf, co-designer of TCP/IP, one of the “fathers of the Internet”, signing as private citizen
  • Paul Vixie, author of BIND, the most widely-used DNS server software, and President of the Internet Systems Consortium
  • Tony Li, co-author of BGP (the protocol used to arrange Internet routing); chair of the IRTF’s Routing Research Group; a Cisco Fellow; and architect for many of the systems that have actually been used to build the Internet
  • Steven Bellovin, invented the DNS cache contamination attack; co-authored the first book on Internet security; recipient of the 2007 NIST/NSA National Computer Systems Security Award and member of the DHS Science and Technology Advisory Committee
  • Jim Gettys, editor of the HTTP/1.1 protocol standards, which we use to do everything on the Web
  • Dave Kristol, co-author, RFCs 2109, 2965 (Web cookies); contributor, RFC 2616 (HTTP/1.1)
  • Steve Deering, Ph.D., invented the IP multicast feature of the Internet; lead designer of IPv6 (version 6 of the Internet Protocol)
  • David Ulevitch, David Ulevitch, CEO of OpenDNS, which offers alternative DNS services for enhanced security.
  • Elizabeth Feinler, director of the Network Information Center (NIC) at SRI International, administered the Internet Name Space from 1970 until 1989 and developed the naming conventions for the internet top level domains (TLDs) of .mil, .gov, .com, .org, etc. under contracts to DoD
  • Robert W. Taylor, founded and funded the beginning of the ARPAnet; founded and managed the Xerox PARC Computer Science Lab which designed and built the first networked personal computer (Alto), the Ethernet, the first internet protocol and internet, and desktop publishing
  • Fred Baker, former IETF chair, has written about 50 RFCs and contributed to about 150 more, regarding widely used Internet technology
  • Dan Kaminsky, Chief Scientist, DKH
  • Esther Dyson, EDventure; founding chairman, ICANN; former chairman, EFF; active investor in many start-ups that support commerce, news and advertising on the Internet; director, Sunlight Foundation
  • Walt Daniels, IBM’s contributor to MIME, the mechanism used to add attachments to emails
  • Nathaniel Borenstein, Chief Scientist, Mimecast; one of the two authors of the MIME protocol, and has worked on many other software systems and protocols, mostly related to e-mail and payments
  • Simon Higgs, designed the role of the stealth DNS server that protects a.root-servers.net; worked on all versions of Draft Postel for creating new TLDs and addressed trademark issues with a complimentary Internet Draft; ran the shared-TLD mailing list back in 1995 which defined the domain name registry/registrar relationship; was a root server operator for the Open Root Server Consortium; founded coupons.com in 1994
  • John Bartas, was the technical lead on the first commercial IP/TCP software for IBM PCs in 1985-1987 at The Wollongong Group. As part of that work, developed the first tunneling RFC, rfc-1088
  • Nathan Eisenberg, Atlas Networks Senior System Administrator; manager of 25K sq. ft. of data centers which provide services to Starbucks, Oracle, and local state
  • Dave Crocker, author of Internet standards including email, DKIM anti-abuse, electronic data interchange and facsimile, developer of CSNet and MCI national email services, former IETF Area Director for network management, DNS and standards, recipient of IEEE Internet Award for contributions to email, and serial entrepreneur
  • Craig Partridge, architect of how email is routed through the Internet; designed the world’s fastest router in the mid 1990s
  • Doug Moeller, Chief Technology Officer at Autonet Mobile
  • John Todd, Lead Designer/Maintainer – Freenum Project (DNS-based, free telephony/chat pointer system), http://freenum.org/
  • Alia Atlas, designed software in a core router (Avici) and has various RFCs around resiliency, MPLS, and ICMP
  • Kelly Kane, shared web hosting network operator
  • Robert Rodgers, distinguished engineer, Juniper Networks
  • Anthony Lauck, helped design and standardize routing protocols and local area network protocols and served on the Internet Architecture Board
  • Ramaswamy Aditya, built various networks and web/mail content and application hosting providers including AS10368 (DNAI) which is now part of AS6079 (RCN); did network engineering and peering for that provider; did network engineering for AS25 (UC Berkeley); currently does network engineering for AS177-179 and others (UMich)
  • Blake Pfankuch, Connecting Point of Greeley, Network Engineer
  • Jon Loeliger, has implemented OSPF, one of the main routing protocols used to determine IP packet delivery; at other companies, has helped design and build the actual computers used to implement core routers or storage delivery systems; at another company, installed network services (T-1 lines and ISP service) into Hotels and Airports across the country
  • Jim Deleskie, internetMCI Sr. Network Engineer, Teleglobe Principal Network Architect
  • David Barrett, Founder and CEO, Expensify
  • Mikki Barry, VP Engineering of InterCon Systems Corp., creators of the first commercial applications software for the Macintosh platform and the first commercial Internet Service Provider in Japan
  • Peter Rubenstein,helped to design and build the AOL backbone network, ATDN.
  • David Farber, distinguished Professor CMU; Principal in development of CSNET, NSFNET, NREN, GIGABIT TESTBED, and the first operational distributed computer system; EFF board member
  • Bradford Chatterjee, Network Engineer, helped design and operate the backbone network for a nationwide ISP serving about 450,000 users
  • Gary E. Miller Network Engineer specializing in eCommerce
  • Jon Callas, worked on a number of Internet security standards including OpenPGP, ZRTP, DKIM, Signed Syslog, SPKI, and others; also participated in other standards for applications and network routing
  • John Kemp, Principal Software Architect, Nokia; helped build the distributed authorization protocol OAuth and its predecessors; former member of the W3C Technical Architecture Group
  • Christian Huitema, worked on building the Internet in France and Europe in the 80’s, and authored many Internet standards related to IPv6, RTP, and SIP; a former member of the Internet Architecture Board
  • Steve Goldstein, Program Officer for International Networking Coordination at the National Science Foundation 1989-2003, initiated several projects that spread Internet and advanced Internet capabilities globally
  • David Newman, 20 years’ experience in performance testing of Internet
    infrastructure; author of three RFCs on measurement techniques (two on firewall performance, one on test traffic contents)
  • Justin Krejci, helped build and run the two biggest and most successful municipal wifi networks located in Minneapolis, MN and Riverside, CA; building and running a new FTTH network in Minneapolis
  • Christopher Liljenstolpe, was the chief architect for AS3561 (at the time about 30% of the Internet backbone by traffic), and AS1221 (Australia’s main Internet infrastructure)
  • Joe Hamelin, co-founder of Seattle Internet Exchange (http://www.seattleix.net) in 1997, and former peering engineer for Amazon in 2001
  • John Adams, operations engineer at Twitter, signing as a private citizen
  • David M. Miller, CTO / Exec VP for DNS Made Easy (IP Anycast Managed Enterprise DNS provider)
  • Seth Breidbart, helped build the Pluribus IMP/TIP for the ARPANET
  • Timothy McGinnis, co-chair of the African Network Information Center Policy Development Working Group, and active in various IETF Working Groups
  • Richard Kulawiec, 30 years designing/operating academic/commercial/ISP systems and networks
  • Larry Stewart, built the Etherphone at Xerox, the first telephone system working over a local area network; designed early e-commerce systems for the Internet at Open Market
  • John Pettitt, Internet commerce pioneer, online since 1983, CEO Free Range Content Inc.; founder/CTO CyberSource & Beyond.com; created online fraud protection software that processes over 2 billion transaction a year
  • Brandon Ross, Chief Network Architect and CEO of Network Utility Force LLC
  • Chris Boyd, runs a green hosting company and supports EFF-Austin as a board member
  • Dr. Richard Clayton, designer of Turnpike, widely used Windows-based Internet access suite; prominent Computer Security researcher at Cambridge University
  • Robert Bonomi, designed, built, and implemented, the Internet presence for a number of large corporations
  • Owen DeLong, member of the ARIN Advisory Council who has spent more than a decade developing better IP addressing policies for the internet in North America and around the world
  • Baudouin Schombe, blog design and content trainer
  • Lyndon Nerenberg, Creator of IMAP Binary extension (RFC 3516)
  • John Gilmore, co-designed BOOTP (RFC 951), which became DHCP, the way you get an IP address when you plug into an Ethernet or get on a WiFi access point; current EFF board member
  • John Bond, Systems Engineer at RIPE NCC maintaining AS25152 (k.root-servers.net.) and AS197000 (f.in-addr-servers.arpa. ,f.ip6-servers.arpa.); signing as a private citizen
  • Stephen Farrell, co-author on about 15 RFCs
  • Samuel Moats, senior systems engineer for the Department of Defense; helps build and defend the networks that deliver data to Defense Department users
  • John Vittal, created the first full email client and the email standards still in use today
  • Ryan Rawdon, built out and maintains the network infrastructure for a rapidly growing company in our country’s bustling advertising industry; was on the technical operations team for one of our country’s largest residential ISPs
  • Brian Haberman, has been involved in the design of IPv6, IGMP/MLD, and NTP within the IETF for nearly 15 years
  • Eric Tykwinski, Network Engineer working for a small ISP based in the Philadelphia region; currently maintains the network as well as the DNS and server infrastructure
  • Noel Chiappa, has been working on the lowest level stuff (the IP protocol level) since 1977; name on the ‘Birth of the Internet’ plaque at Stanford); actively helping to develop new ‘plumbing’ at that level
  • Robert M. Hinden, worked on the gateways in the early Internet, author of many of the core IPv6 specifications, active in the IETF since the first IETF meeting, author of 37 RFCs, and current Internet Society Board of Trustee member
  • Alexander McKenzie, former member of the Network Working Group and participated in the design of the first ARPAnet Host protocols; was the manager of the ARPAnet Network Operation Center that kept the network running in the early 1970s; was a charter member of the International Network Working Group that developed the ideas used in TCP and IP
  • Keith Moore, was on the Internet Engineering Steering Group from 1996-2000, as one of two Area Directors for applications; wrote or co-wrote technical specification RFCs associated with email, WWW, and IPv6 transition
  • Guy Almes, led the connection of universities in Texas to the NSFnet during the late 1980s; served as Chief Engineer of Internet2 in the late 1990s
  • David Mercer, formerly of The River Internet, provided service to more of Arizona than any local or national ISP
  • Paul Timmins, designed and runs the multi-state network of a medium sized telephone and internet company in the Midwest
  • Stephen L. Casner, led the working group that designed the Real-time Transport Protocol that carries the voice signals in VoIP systems
  • Tim Rutherford, DNS and network administrator at C4
  • Mike Alexander, helped implement (on the Michigan Terminal System at the University of Michigan) one of the first EMail systems to be connected to the Internet (and to its predecessors such as Bitnet, Mailnet, and UUCP); helped with the basic work to connect MTS to the Internet; implemented various IP related drivers on early Macintosh systems: one allowed TCP/IP connections over ISDN lines and another made a TCP connection look like a serial port
  • John Klensin, Ph.D., early and ongoing role in the design of Internet applications and coordination and administrative policies
  • L. Jean Camp, former Senior Member of the Technical Staff at Sandia National Laboratories, focusing on computer security; eight years at Harvard’s Kennedy School; tenured Professor at Indiana Unviersity’s School of Informatics with research addressing security in society.
  • Louis Pouzin, designed and implemented the first computer network using datagrams (CYCLADES), from which TCP/IP was derived
  • Carl Page, helped found eGroups, the biggest social network
    of its day, 14 million users at the point of sale to Yahoo for around $430,000,000, at which point it became Yahoo Groups
  • Phil Lapsley, co-author of the Internet Network News Transfer Protocol (NNTP), RFC 977, and developer of the NNTP reference implementation
  • Jack Haverty (MSEE, BSEE MIT 1970), Principal Investigator for several DARPA projects including the first Internet development and operation; Corporate Network Architect for BBN; Founding member of the IAB/ICCB; Internet Architect and Corporate Founding Member of W3C for Oracle Corporation
  • Glenn Ricart, Managed the original (FIX) Internet interconnection point
  • Ben Laurie, Apache Software Foundation founder, OpenSSL core team member, security researcher. Over half the secure websites on the Internet are powered by his software.
  • Chris Wellens President & CEO InterWorking Labs

More Content

Cyber War

SciFi

Super Bowl Ads Indicate Big Businesses Think You Are Afraid of AI

Tom Loftus provided an insightful review of some of Super Bowl ads in the 4 Feb 2019 Wall Street Journal. Like AI parody in SNL, these ads really poked fun at computers: Seriously, did anyone catch the commercials? If the Super Bowl is the zeitgeist, then it is safe to say that America is not […]

HBO’s Westworld: The Man In Black is a special kind of Twitter user

HBO’s Westworld is a modern take on the Michael Crichton SciFi tale of a robotic amusement park. The HBO version has a new twist. The creators/writers were all exposed to years of Twitter, which has influenced every episode and the entire arch of two seasons of the show. Now that season two is wrapping up, […]