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.

Career

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

Belshe started his career at Hewlett-Packard, followed by Silicon Valley startup Netscape Communications Corp., where he worked on the Netscape Enterprise Server. [3] After Netscape he joined Good Technology before co-founding Lookout Software with Eric Hahn. [4] 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]

Related Research Articles

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

The Hypertext Transfer Protocol (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">Web browser</span> Software used to navigate the internet

A web browser is an application for accessing websites and the Internet. When a user requests a web page from a particular website, the browser retrieves its files from a web server and then displays the page on the user's screen. Browsers are used on a range of devices, including desktops, laptops, tablets, and smartphones. In 2020, an estimated 4.9 billion people have used a browser. The most used browser is Google Chrome, with a 65% global market share on all devices, followed by Safari with 18%.

Transport Layer Security (TLS) is a cryptographic protocol designed to provide communications security over a computer network. 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.

Mike "Pink" Pinkerton is an American software engineer who is known for his work on the Mozilla browsers. He lectures on Development of Open Source Software at George Washington University.

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

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.

about is an internal URI scheme implemented in various Web browsers to reveal internal state and built-in functions. It is an IANA officially registered scheme, and is standardized.

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

<span class="mw-page-title-main">HTTP referer</span> HTTP header field

In HTTP, "Referer" is an optional HTTP header field that identifies the address of the web page, from which the resource has been requested. By checking the referrer, the server providing the new web page can see where the request originated.

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 simultaneous two-way communication channels 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.

Robert Martin McCool, more commonly known as Rob McCool, is a software developer and architect.

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 to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plugins or download native apps.

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 HTTP/2 specification was published as RFC 7540 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.

CRIME is a security vulnerability in HTTPS and SPDY protocols that utilize compression, which can leak the content of secret web cookies. When used to recover the content of secret authentication cookies, it allows an attacker to perform session hijacking on an authenticated web session, allowing the launching of further attacks. CRIME was assigned CVE-2012-4929.

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

<span class="mw-page-title-main">HTTP/3</span> Version of the HTTP network protocol

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. On 6 June 2022, IETF published HTTP/3 as a Proposed Standard in RFC 9114.

<span class="mw-page-title-main">Jim Roskind</span> American software engineer

Jim Roskind is an American software engineer best known for designing the QUIC protocol in 2012 while being an employee at Google. Roskind co-founded Infoseek in 1994 with 7 other people, including Steve Kirsch. Later that year, Roskind wrote the Python profiler which is part of the standard library. From 1995 to 2003 he was chief architect at Netscape during which time he developed Netscape's Java security module.

References

  1. "Mike Belshe, Bitgo Inc: Profile and Biography". Bloomberg.com. Retrieved 2023-11-07.
  2. Evers, Joris. 2004-7-16. “Microsoft Scoops Up Search Company”. PCWorld.
  3. O’Reilly Velocity Conference. 2011-6-16. “Mike Belshe Archived 2015-09-24 at the Wayback Machine ”. O’Reilly Velocity Conference Archived 2015-09-08 at the Wayback Machine .
  4. Belshe, Mike. 2015-8-4. "About [ permanent dead link ]". Mike's Lookout.
  5. Chan, Min Li. 2009-12-3. “Technically speaking, what makes Google Chrome fast?”. Chromium Blog.
  6. Google, Inc.; McCloud, Scott. 2008-9-1. "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. 2011-6-16. “Mike Belshe Archived 2015-09-24 at the Wayback Machine ”. O’Reilly Velocity Conference Archived 2015-09-08 at the Wayback Machine .
  9. "Next version of the web will have resistance to surveillance at its core | Naked Security". 24 August 2013. Retrieved 2015-12-18.
  10. "SPDY and What to Consider for HTTP/2.0". 2013-02-17.{{cite journal}}: Cite journal requires |journal= (help)