2. 1. Introduction to HTTP/3
2. Evolution of HTTP
3. HTTP/2 vs. HTTP/3
4. Key Features of HTTP/3
5. Benefits of HTTP/3
6. Implementation and Adoption
7. Challenges and Concerns
8. How HTTP/3 Works
10. Future Developments
12. Q&A
13. Conclusion
16. References
3. • INTRODUCTION
• HTTP/3 is the third major version of the
Hypertext Transfer Protocol.
• It's designed to improve web communication
and performance.
• HTTP/3 is becoming increasingly important as
websites and web applications demand faster
and more efficient data transfer.
4. Evolution of HTTP
• HTTP (Hypertext Transfer Protocol) has evolved
over time.
• Mention HTTP/1.0 and its limitations.
• Highlight the improvements brought by
HTTP/1.1.
• Explain the need for further enhancements in
the form of HTTP/2 and HTTP/3.
5. • HTTP/2 vs. HTTP/3
• HTTP/2 is the second major version of the Hypertext Transfer Protocol (HTTP).
• Standardized in 2015.
• Certainly, here's a concise comparison of HTTP/2 and HTTP/3 in 5 bullet points:
• HTTP/2
• 1. Uses a single multiplexed connection.
• 2. Implements header compression for reduced overhead.
• 3. Supports prioritization of requests.
• 4. Provides improved performance compared to HTTP/1.1.
• 5. Does not require encryption but encourages it (HTTPS).
• **HTTP/3
• 1. Utilizes the QUIC transport protocol, not TCP.
• 2. Implements multiplexing and header compression like HTTP/2.
• 3. Offers even better performance due to reduced latency.
• 4. Uses mandatory encryption (HTTPS is a requirement).
• 5. Designed to handle packet loss and connection migration effectively.
• HTTP/2 introduces several improvements over the previous version, HTTP/1.1, such
as
• Multiplexing: This allows multiple requests and responses to be sent over a single
TCP connection.
6. HTTP/2 vs. HTTP/3
• The main distinction between HTTP/2 and HTTP/3 is the transport layer protocol they use: TCP for
HTTP/2 and UDP for HTTP/3.
• TCP and UDP: Two fundamental transport protocols.
• Each has its strengths and weaknesses.
• TCP - Dependable but Complex
• TCP assures packet delivery in the correct order.
• Drawbacks include head-of-line blocking.
• Requires a three-way handshake for connection establishment.
• Adjusts transmission rate based on network conditions.
• UDP - Simple and Lightweight
• UDP is unreliable and unordered.
• No guarantee of packet delivery or order.
• Advantages include no head-of-line blocking.
• No TCP handshake needed for connection setup.
7. • BENEFITS OF HTTP/3 OVER HTTP 2.
• Certainly, I can help you create bullet points for a PowerPoint
presentation based on the provided article about HTTP/3. Here are
the key points you can use:
• Faster Connection Establishment:
• HTTP/3 establishes connections faster than HTTP/2.
• It achieves this using 0-RTT or a single round-trip handshake.
• Faster connections enhance user experience and overall
performance.
• Improved Handling of Packet Loss:
• HTTP/3 is more resilient to packet loss compared to HTTP/2.
• It employs forward error correction and selective
acknowledgments.
• This reduces retransmissions and minimizes delays in data
transmission.
• Enhanced Connection Migration:
• HTTP/3 excels in supporting connection migration.
• It utilizes connection IDs and path validation mechanisms.
• This enables seamless transitions between different network
interfaces or IP addresses.
8. • Key Features of HTTP/3
• HTTP/3 is the third major version of the Hypertext Transfer Protocol
(HTTP) currently in development, though not yet widely adopted
• Key features of HTTP/3 include QUIC, multiplexing, and improved security.
• It is based on a new protocol called QUIC, developed by Google.
• HTTP/3 inherits the features of HTTP/2, such as multiplexing, header
compression, server push, and prioritization, as well as introducing new
features such as connection migration, 0-RTT, and encryption by default
with Transport Layer Security (TLS)
• Explain how QUIC enhances data transfer over UDP.
• UDP is a connectionless and unreliable protocol that does not
guarantee delivery or order of packets, but is faster and more flexible than
TCP.
• Describe how multiplexing enables multiple requests and responses
simultaneously.
• Connection migration allows clients and servers to switch between
different network interfaces or IP addresses without interrupting the
connection, while 0-RTT enables clients and servers to resume previous
connections without performing a full handshake.
• Mention improved security due to mandatory encryption.
9. • Benefits of HTTP/3
• Faster loading times and reduced latency.
• Improved performance for websites and web
applications.
• Enhanced user experience, especially on mobile
devices.
10. • Implementation and Adoption
• Discuss the status of HTTP/3 adoption across
the web.
• Mention major browsers (e.g., Chrome, Firefox)
and websites (e.g., Google, Facebook) that have
adopted HTTP/3.
11. • Challenges and Concerns
• Address potential challenges like compatibility
issues with older protocols.
• Mention concerns related to network
congestion and the need for proper
configuration.
12. • How HTTP/3 Works
• Explain how HTTP/3 works, including the role of
QUIC and encryption.
• Describe how data is divided into packets and
transmitted.
• Highlight the benefits of this approach for web
performance.
13. • ase Studies
• Provide real-world examples of organizations or
websites that have benefited from implementing
HTTP/3.
• Share performance improvements and user
experience enhancements.
14. • Future Developments
• Discuss potential future developments and
improvements in HTTP/3, such as ongoing
protocol enhancements.
• Mention how HTTP/3 will continue to evolve to
meet changing web demands.
18. • In summary, HTTP3 offers
substantial benefits in terms
of performance and security
and more efficient.
• Http 3 also helps to provide
users with faster and more
secure web experience but it
it also has various challenges.
• Despite all these challenges
HTTP3 plays a critical role in
shaping the future of the web
by optimizing how data is
delivered.
21. REFERNCES
• First draft presented at IETF 104 (March 2019)
https://datatracker.ietf.org/doc/draft-ferrieuxhamchaoui-quic-
lossbits
• Orange-Akamai trial presented at IETF 105 (July 2019)
https://datatracker.ietf.org/meeting/105/materials/slides-105-
maprg-packet-loss-signaling-for-encrypted-protocols-01
• Akamai+lightspeed step-in at IETF 106 (November 2019)
https://datatracker.ietf.org/doc/draft-ferrieuxhamchaoui-tsvwg-
lossbits/
• Satcom trial presented at IETF 106 (November 2019)
https://datatracker.ietf.org/meeting/106/materials/slides-106-
maprg-losses-in-satcom-systems-identification-and-impact
• Joint draft with Telecom Italia (mars 2020)
https://datatracker.ietf.org/doc/draft-mdt-ippm-explicit-flow-
measurements/
• Independent evaluation from Ike Kunze et al. (Aachen university)
• L, Q, R, and T: which spin bit cousin is here to stay? (ANRW '21)
22. THANK YOU
GROUP 3
• Emmanuel Odamtten
• Kumi Justice
• Hans Adoto Choukpin
• Theressa Afreh
• David Oreoluwa Ezekiel
• Ngaibona Delano Francklin
