Mike Belshe

Last updated

Mike Belshe (born 1971) is an American computer scientist and entrepreneur. He's a co-founder and CEO of BitGo, Inc. [1] and a cofounder of Lookout Software in 2004. [2] He is the co-inventor of the SPDY protocol and one of the principal authors of the HTTP/2.0 specification.

Contents

Early life and education

Belshe received his bachelor's degree in computer science from California Polytechnic State University, San Luis Obispo.

He is also an inventor with over 10 technology patents.

He is a lifelong Bay Area resident and grew up just outside of Berkeley.

Career

Belshe started his career at Hewlett-Packard, followed by Silicon Valley startup Netscape Communications Corp., where he worked on the Netscape Enterprise Server. [3] where he worked closely with Ben Horowitz as one of the critical engineers on the Netscape Enterprise Server.

After Netscape he joined Good Technology before co-founding Lookout Software with Eric Hahn. [4] Microsoft eventually acquired Lookout and it became a key feature of Outlook.

Joining in 2006, he was one the early hires on the Google Chrome team, [5] and was part of the Google Chrome Comic. [6] As part of the Chrome team he worked on protocol research, [7] and later co-authored the SPDY protocol. [8] He submitted SPDY to the IETF in 2011, and was an author of HTTP/2. [7]

As part of the IETF standardization effort, Belshe argued for encryption by default within the protocol. [9] [10] The encrypted-by-default approach was later adopted by all major browsers.

Mike went on to co-found the industry-leading cryptocurrency company, BitGo, in 2013. He was quickly named CEO.

BitGo is the largest independent qualified custodian worldwide and remains the best way for institutions and investors to secure, manage, and grow their digital asset portfolio.

Related Research Articles

<span class="mw-page-title-main">HTTP</span> Application protocol for distributed, collaborative, hypermedia information systems

HTTP is an application layer protocol in the Internet protocol suite model for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.

<span class="mw-page-title-main">HTTPS</span> Extension of the HTTP communications protocol to support TLS encryption

Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP). It uses encryption for secure communication over a computer network, and is widely used on the Internet. In HTTPS, the communication protocol is encrypted using Transport Layer Security (TLS) or, formerly, Secure Sockets Layer (SSL). The protocol is therefore also referred to as HTTP over TLS, or HTTP over SSL.

<span class="mw-page-title-main">Internet Explorer</span> Web browser series by Microsoft

Internet Explorer is a retired series of graphical web browsers developed by Microsoft that were used in the Windows line of operating systems. While IE has been discontinued on most Windows editions, it remains supported on certain editions of Windows, such as Windows 10 LTSB/LTSC. Starting in 1995, it was first released as part of the add-on package Plus! for Windows 95 that year. Later versions were available as free downloads or in-service packs and included in the original equipment manufacturer (OEM) service releases of Windows 95 and later versions of Windows. Microsoft spent over US$100 million per year on Internet Explorer in the late 1990s, with over 1,000 people involved in the project by 1999. New feature development for the browser was discontinued in 2016 and ended support on June 15, 2022 for Windows 10 Semi-Annual Channel (SAC), in favor of its successor, Microsoft Edge.

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network, such as the Internet. The protocol is widely used in applications such as email, instant messaging, and voice over IP, but its use in securing HTTPS remains the most publicly visible.

In computing, the User-Agent header is an HTTP header intended to identify the user agent responsible for making a given HTTP request. Whereas the character sequence User-Agent comprises the name of the header itself, the header value that a given user agent uses to identify itself is colloquially known as its user agent string. The user agent for the operator of a computer used to access the Web has encoded within the rules that govern its behavior the knowledge of how to negotiate its half of a request-response transaction; the user agent thus plays the role of the client in a client–server system. Often considered useful in networks is the ability to identify and distinguish the software facilitating a network session. For this reason, the User-Agent HTTP header exists to identify the client software to the responding server.

<span class="mw-page-title-main">HTTP pipelining</span> Computer communication technique

HTTP pipelining is a feature of HTTP/1.1, which allows multiple HTTP requests to be sent over a single TCP connection without waiting for the corresponding responses. HTTP/1.1 requires servers to respond to pipelined requests correctly, with non-pipelined but valid responses even if server does not support HTTP pipelining. Despite this requirement, many legacy HTTP/1.1 servers do not support pipelining correctly, forcing most HTTP clients to not use HTTP pipelining.

This article lists communication protocols that are designed for file transfer over a telecommunications network.

Comet is a web application model in which a long-held HTTPS request allows a web server to push data to a browser, without the browser explicitly requesting it. Comet is an umbrella term, encompassing multiple techniques for achieving this interaction. All these methods rely on features included by default in browsers, such as JavaScript, rather than on non-default plugins. The Comet approach differs from the original model of the web, in which a browser requests a complete web page at a time.

SPDY is an obsolete open-specification communication protocol developed for transporting web content. SPDY became the basis for HTTP/2 specification. However, HTTP/2 diverged from SPDY and eventually HTTP/2 subsumed all usecases of SPDY. After HTTP/2 was ratified as a standard, major implementers, including Google, Mozilla, and Apple, deprecated SPDY in favor of HTTP/2. Since 2021, no modern browser supports SPDY.

<span class="mw-page-title-main">WebSocket</span> Computer network protocol

WebSocket is a computer communications protocol, providing a simultaneous two-way communication channel over a single Transmission Control Protocol (TCP) connection. The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011. The current specification allowing web applications to use this protocol is known as WebSockets. It is a living standard maintained by the WHATWG and a successor to The WebSocket API from the W3C.

WebRTC is a free and open-source project providing web browsers and mobile applications with real-time communication (RTC) via application programming interfaces (APIs). It allows audio and video communication and streaming to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plugins or download native apps.

<span class="mw-page-title-main">Internet Explorer 11</span> Web browser by Microsoft for Windows released in 2013

Internet Explorer 11 (IE11) is the eleventh and final version of the Internet Explorer web browser. It was initially included in the release of Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2 on October 17, 2013, and was later released for Windows 7 and Windows Server 2008 R2 on November 7, 2013. It is the successor to Internet Explorer 10, released the previous year, and was the original, default browser in Windows 8.1 and Windows Server 2012 R2. Internet Explorer 11 was also included in the release of Windows 10 on July 29, 2015, as well as in Windows Server 2016 and Windows Server 2019. On April 16, 2019, Internet Explorer 11 was made available to Windows Server 2012 and Windows Embedded 8 Standard as the final expansion of Internet Explorer 11 availability. Internet Explorer 11, like its predecessor, is not available for Windows 8, Windows Vista, Windows Server 2008, and earlier versions of Windows and Windows Server.

HTTP Speed+Mobility was an experimental open-specification communication protocol developed primarily at Microsoft for transporting web content. HTTP Speed+Mobility was similar to HTTP, with particular goals to reduce web page load latency and improve web security. As a revision of Google's SPDY protocol, Microsoft's HTTP Speed+Mobility protocol achieved reduced latency through SPDY's use of compression, multiplexing, and prioritization.

HTTP/2 is a major revision of the HTTP network protocol used by the World Wide Web. It was derived from the earlier experimental SPDY protocol, originally developed by Google. HTTP/2 was developed by the HTTP Working Group of the Internet Engineering Task Force (IETF). HTTP/2 is the first new version of HTTP since HTTP/1.1, which was standardized in RFC 2068 in 1997. The Working Group presented HTTP/2 to the Internet Engineering Steering Group (IESG) for consideration as a Proposed Standard in December 2014, and IESG approved it to publish as Proposed Standard on February 17, 2015. The initial HTTP/2 specification was published as on May 14, 2015.

Application-Layer Protocol Negotiation (ALPN) is a Transport Layer Security (TLS) extension that allows the application layer to negotiate which protocol should be performed over a secure connection in a manner that avoids additional round trips and which is independent of the application-layer protocols. It is used to establish HTTP/2 connections without additional round trips.

QUIC is a general-purpose transport layer network protocol initially designed by Jim Roskind at Google. It was first implemented and deployed in 2012 and was publicly announced in 2013 as experimentation broadened. It was also described at an IETF meeting. The Chrome web browser, Microsoft Edge, Firefox, and Safari all support it. In Chrome, QUIC is used by more than half of all connections to Google's servers.

Logjam is a security vulnerability in systems that use Diffie–Hellman key exchange with the same prime number. It was discovered by a team of computer scientists and publicly reported on May 20, 2015. The discoverers were able to demonstrate their attack on 512-bit DH systems. They estimated that a state-level attacker could do so for 1024-bit systems, then widely used, thereby allowing decryption of a significant fraction of Internet traffic. They recommended upgrading to at least 2048 bits for shared prime systems.

HTTP/2 Server Push is an optional feature of the HTTP/2 and HTTP/3 network protocols that allows servers to send resources to a client before the client requests them. Server Push is a performance technique aimed at reducing latency by sending resources to a client preemptively before it knows they will be needed. In practice, Server Push frequently results in wasted bandwidth because the server rarely knows which resources are already loaded by the client and transmits the same resource multiple times, resulting in slowdowns if the resources being pushed compete for bandwidth with resources that were requested.

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web, complementing the widely-deployed HTTP/1.1 and HTTP/2. Unlike previous versions which relied on the well-established TCP, HTTP/3 uses QUIC, a multiplexed transport protocol built on UDP.

References

  1. ↑ "Mike Belshe, Bitgo Inc: Profile and Biography". Bloomberg.com. Retrieved November 7, 2023.
  2. ↑ Evers, Joris. July 16, 2004. "Microsoft Scoops Up Search Company". PCWorld.
  3. ↑ O’Reilly Velocity Conference. June 16, 2011. "Mike Belshe Archived 2015-09-24 at the Wayback Machine ". O’Reilly Velocity Conference Archived September 8, 2015, at the Wayback Machine .
  4. ↑ Belshe, Mike. August 4, 2015. "About [ permanent dead link ]". Mike's Lookout.
  5. ↑ Chan, Min Li. December 3, 2009. "Technically speaking, what makes Google Chrome fast?". Chromium Blog.
  6. ↑ Google, Inc.; McCloud, Scott. September 1, 2008. "Google Chrome Comic". Google, Inc.
  7. 1 2 Belshe, M.; Peon, R.; Thomson, M.; Melnikov, A.. 2015–5. "Hypertext Transfer Protocol Version 2 (HTTP/2)". Internet Engineering Task Force.
  8. ↑ O’Reilly Velocity Conference. June 16, 2011. "Mike Belshe Archived 2015-09-24 at the Wayback Machine ". O’Reilly Velocity Conference Archived September 8, 2015, at the Wayback Machine .
  9. ↑ "Next version of the web will have resistance to surveillance at its core | Naked Security". August 24, 2013. Retrieved December 18, 2015.
  10. ↑ "SPDY and What to Consider for HTTP/2.0". February 17, 2013.{{cite journal}}: Cite journal requires |journal= (help)
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.