ROADMAP: QUIC and TLS 1.3
This commit is contained in:
Родитель
545562f13e
Коммит
57ac61a469
|
@ -14,6 +14,26 @@ over HTTP/1. Some of that difference can be attributed the inefficient window
|
||||||
size handling currently in use but there are probably more to be learned and
|
size handling currently in use but there are probably more to be learned and
|
||||||
worked on to optimize this.
|
worked on to optimize this.
|
||||||
|
|
||||||
|
QUIC
|
||||||
|
----
|
||||||
|
|
||||||
|
The standardization process of QUIC has been taken to the IETF and can be
|
||||||
|
followed on the [IETF QUIC Mailing
|
||||||
|
list](https://www.ietf.org/mailman/listinfo/quic). I'd like us to get on the
|
||||||
|
bandwagon. Ideally, this would be done with a separate library/project to
|
||||||
|
handle the binary/framing layer in a similar fashion to how HTTP/2 is
|
||||||
|
implemented. This, to allow other projects to benefit from the work and to
|
||||||
|
thus broaden the interest and chance of others to participate.
|
||||||
|
|
||||||
|
TLS 1.3
|
||||||
|
-------
|
||||||
|
|
||||||
|
The new version of the TLS protocol is in the pipeline and will soon start to
|
||||||
|
get used out in the wild. It offers some new interesting features and will
|
||||||
|
need the TLS libraries to adapt and quite likely provide additional or
|
||||||
|
modified APIs. libcurl needs to adapt accordingly.
|
||||||
|
|
||||||
|
|
||||||
HTTP cookies
|
HTTP cookies
|
||||||
------------
|
------------
|
||||||
|
|
||||||
|
|
Загрузка…
Ссылка в новой задаче