QUIC, HTTP/3 근황

QUIC (Quick UDP Internet Connections) : A UDP-Based Multiplexed and Secure Transport

 

 

 

QUIC is an IETF Working Group that is chartered to deliver the next transport protocol for the Internet.

    https://quicwg.org/

    https://github.com/quicwg/base-drafts

.... experimental implementations in progress.

    https://github.com/quicwg/base-drafts/wiki/Implementations

IETF QUIC The following stacks implement the IETF versions of QUIC Transport. They may include an application layer mapping other than IETF HTTP over QUIC e.g. HTTP/0.9 ..... IETF HTTP over QUIC The following implement IETF HTTP over QUIC. The "Transport library" field identifies one (or more) of the above stacks if applicable. QPACK Google QUIC

    https://datatracker.ietf.org/doc/draft-ietf-quic-transport/?include_text=1

 

 

 

QUIC (pronounced 'quick')

    https://en.wikipedia.org/wiki/QUIC

Source code[edit] The following implementations of QUIC or gQUIC are available in source form: Chromium. Language: C++. This is the source code of the Chrome web browser and the reference gQUIC implementation. It contains a standalone gQUIC client and server programs that can be used for testing. Browsable source code LSQUIC Client Library. Language: C. This is the QUIC implementation used in LiteSpeed Web Server, minus server-specific bits. Quiche. Language: Rust. Socket-agnostic and exposes a C API for use in C/C++ applications. quicly. Language: C. This library is the QUIC implementation for the H2O web server. quic-go. Language: Go. This library provides QUIC support in Caddy web server. Client functionality is also available. Quinn. Language: Rust.

 

2018/07/26 The Road to QUIC

    https://blog.cloudflare.com/the-road-to-quic/

2018/09/25 Get a head start with QUIC

    https://blog.cloudflare.com/head-start-with-quic/

 

 

 

 

아직 HTTP/2도 보편화되지 않았는데, HTTP/3으로 rename되었다고?

 

2018/11/12 HTTP-over-QUIC to be renamed HTTP/3

    https://www.zdnet.com/article/http-over-quic-to-be-renamed-http3/

"In a mailing list discussion last month, Mark Nottingham, 
 Chair of the IETF HTTP and QUIC Working Group,
 made the official request to rename HTTP-over-QUIC as HTTP/3,
 and pass it's development from the QUIC Working Group to the HTTP Working Group."

 

 

What is HTTP/3?

    https://medium.com/devgorilla/what-is-http-3-94335c57823f

 

HTTP/2.0이 언제쯤 보편화될지 생각했었는데, HTTP/3으로 바로 갈 수도 있겠는데?

이미 구글이 QUIC을 사용하던 시점 - 4년전(2015년)-에 표준화를 염두하고 있었나보네.

    https://techcrunch.com/2015/04/18/google-wants-to-speed-up-the-web-with-its-quic-protocol/

 

 

기회가 닿으면 QUIC한번 만져보고 싶네.

"TCP Fast Open" 기술은 어찌되고 있지? 흠...

 

 

[기타 : 참고]

2016/10/25 NaveD2 - QUIC을 이용한 네트워크 성능 개선 - 데브시스터즈

    https://www.slideshare.net/deview/quic-67614063

 

안드로이드 기기에 앱 설치 후 "safebrowsing.google.com"에 QUIC로 데이터를 보내는 구만...