simmervigor

6 ms·

1.
HTTP Integrity Digests: Past, Present, and Future(lucaspardue.com)
2 points by simmervigor 1mo ago|0 comments
2.
Go and enhance your calm: demolishing an HTTP/2 interop problem(blog.cloudflare.com)
5 points by simmervigor 11mo ago|1 comments
3.
Defending QUIC from acknowledgement-based DDoS attacks(blog.cloudflare.com)
11 points by simmervigor 11mo ago|0 comments
4.
by simmervigor 1y ago
> If anyone from Cloudflare happens to be reading this, you should know that you have some kind of misconfiguration Thanks for the detailed information. I'm a someone from Cloudflare responsible for this, we'll get it looked at
5.
by simmervigor 1y ago
We certainly like it at Cloudflare. Look out for more blogs from the team related to the topics.
6.
by simmervigor 1y ago
Very nice work. From a qlog and MASQUE enthusiast
7.
Technical Advisory – Hash DoS Attack in Multiple QUIC Implementations(github.com)
2 points by simmervigor 2y ago|0 comments
8.
Degox – Taking back my internet privacy and presence(lucaspardue.com)
8 points by simmervigor 3y ago|2 comments
9.
by simmervigor 4y ago
tools.ietf.org hosted a range of tools or links to resources. That is what i mean by service, which has been in the process of migration to other subdomains of ietf.org
10.
by simmervigor 4y ago
From the page: > The IETF Datatracker is the day-to-day front-end to the IETF database for people who work on IETF standards. It contains data about the documents, working groups, meetings, agendas, minutes, presentations, and more, of t
11.
by simmervigor 4y ago
Odd this appeared on the front page. The service is deprecated and the tools will soon have been entirely migrated under https://datatracker.ietf.org
12.
by simmervigor 4y ago
Yes it was, there was a pretty lengthy discussion dating back to 2017 on the issue tracker https://github.com/quicwg/base-drafts/issues/253 TL;DR just like HTTP/2, we wanted to avoid friction in deployi
13.
by simmervigor 4y ago
103 Early Hints is RFC 8297. It defines a status code. Because status codes are an HTTP semantic, they are common across all HTTP/1.1, HTTP/2, and HTTP/3. There's nothing special that needs to be done from a specificatio
14.
by simmervigor 4y ago
For what it's worth, the HTTP/2 specification contains almost identical phrasing as HTTP/3 [1]. That's not unexpected, the considerations are similar: using a single connection with connection-specific values has potenti
15.
by simmervigor 4y ago
Co-chair of the QUIC WG here. Early in the process, we decided it was important that HTTP/3 provide parity with HTTP/2. That helps application developers to migrate back and forth between versions with less friction. So we include
16.
by simmervigor 4y ago
You could build this as an application mapping over QUIC. Within a single QUIC connection use reliable streams for the metadata delivery, and unreliable datagrams [1] for the payload. The benefit of a single connection is shared security co
17.
by simmervigor 4y ago
> If I were the Internet Dictator, I'd be a big fan of standardizing the semantics of http separate from the physical transport and then defining best practices for using alternative transports in the wild, and then eventually stand
18.
by simmervigor 4y ago
Some related discussion in this Twitter thread: https://twitter.com/alagoutte/status/1532013841718120449?t=W...
19.
by simmervigor 4y ago
Proxy components are officially called Intermediaries in thr HTTP semantic specification; see https://httpwg.org/http-core/draft-ietf-httpbis-semantics-la... . Intermediaries can have different purposes. The official al
20.
by simmervigor 4y ago
The vanilla CONNECT method is an instruction to open a TCP connection to the target server. What is sent over that is entirely up to client and target the server it doesn't need to match. Its often TLS carrying HTTP but it could be any