RECORD
Surfing the Web quicker than QUIC via a shared Address Validation
Cryptography and Security · Submitted 22 Mar 2019
abstract compiled · 2026-09-23 · no language-model review
The authors' main claim Our results suggest that a shared address validation saves a round-trip time on almost 60% of the required handshakes to different hosts during the first loading of an average website.
The compiled record
The paper's own sentences, arranged. Each label is drawn from a closed vocabulary; the number beside it is the probability the classifier gave that label. Numbers in the tables are the authors', checked by code. No sentence in this record was written by a model.
Open the compiled record
The abstract, sentence by sentence
QUIC is a performance-optimized secure transport protocol and a building block of the upcoming HTTP/3 standard. To protect against denial-of-service attacks, QUIC servers need to validate the IP addresses claimed by their clients. So far, the QUIC protocol conducts address validation for each hostname separately using validation tokens. In this work, we review this practice and introduce a new QUIC transport parameter to allow a shared address validation across hostnames. This parameter indicates to the client, that an issued validation token can be used to abbreviate the address validation when connecting to specific other hostnames. Based on trust-relations between real-world hostnames we evaluate the performance benefits of our proposal. Our results suggest that a shared address validation saves a round-trip time on almost 60% of the required handshakes to different hosts during the first loading of an average website. Assuming a typical transatlantic connection with a round-trip time of 90ms. We find that deploying our proposal reduces the delay overhead to establish all required connections for an average website by 142.2ms.
background contribution method result interpretation main claim
| # | sentence | role | the authors' own work | states the main conclusion | strength |
|---|---|---|---|---|---|
| s0 | QUIC is a performance-optimized secure transport protocol and a building block of the upcoming HTTP/3 standard. | background 1.00 | 0.04 | 0.02 | asserted 1.00 |
| s1 | To protect against denial-of-service attacks, QUIC servers need to validate the IP addresses claimed by their clients. | background 1.00 | 0.04 | 0.02 | asserted 1.00 |
| s2 | So far, the QUIC protocol conducts address validation for each hostname separately using validation tokens. | background 0.89 | 0.05 | 0.02 | asserted 1.00 |
| s3 | In this work, we review this practice and introduce a new QUIC transport parameter to allow a shared address validation across hostnames. | contribution 1.00 | 0.90 | 0.11 | asserted 0.99 |
| s4 | This parameter indicates to the client, that an issued validation token can be used to abbreviate the address validation when connecting to specific other hostnames. | method 0.77 | 0.60 | 0.06 | asserted 0.60 |
| s5 | Based on trust-relations between real-world hostnames we evaluate the performance benefits of our proposal. | method 0.88 | 0.91 | 0.04 | asserted 0.75 |
| s6 | Our results suggest that a shared address validation saves a round-trip time on almost 60% of the required handshakes to different hosts during the first loading of an average website. | result 1.00 | 0.96 | 0.77 | hedged possibility 0.99 |
| s7 | Assuming a typical transatlantic connection with a round-trip time of 90ms. | method 0.43 | 0.21 | 0.02 | asserted 0.55 |
| s8 | We find that deploying our proposal reduces the delay overhead to establish all required connections for an average website by 142.2ms. | result 1.00 | 0.96 | 0.41 | asserted 0.99 |
What was examined, and what was not
- arXiv listing abstract v1
- full text
- figures and tables
- references and citing sentences
- relations to other papers
- P abstract
- S sections
- T body sentences
- C citations
- R cross-paper relations
The paper
Original abstract
QUIC is a performance-optimized secure transport protocol and a building block of the upcoming HTTP/3 standard. To protect against denial-of-service attacks, QUIC servers need to validate the IP addresses claimed by their clients. So far, the QUIC protocol conducts address validation for each hostname separately using validation tokens. In this work, we review this practice and introduce a new QUIC transport parameter to allow a shared address validation across hostnames. This parameter indicates to the client, that an issued validation token can be used to abbreviate the address validation when connecting to specific other hostnames. Based on trust-relations between real-world hostnames we evaluate the performance benefits of our proposal. Our results suggest that a shared address validation saves a round-trip time on almost 60% of the required handshakes to different hosts during the first loading of an average website. Assuming a typical transatlantic connection with a round-trip time of 90ms. We find that deploying our proposal reduces the delay overhead to establish all required connections for an average website by 142.2ms.
Human review
How the literature uses it
1 arXiv paper cite this in 2 sentences
Papers citing it
Contests it 1 paper
-
[ref] does not mitigate a stateless retry during the first connection to a member of a group of hostnames that have an exiting trust-relation with each other.
QUICker connection establishment with out-of-band validation tokens · Related work · contest 0.84
Cites it as background 1 paper
-
So far, these discussions focus on extending the number of entities that are allowed to issue address validation tokens for other hostnames either based on existing TLS trust-relations [ref] or based on the source address from which a respective hostname is served [ref] .
QUICker connection establishment with out-of-band validation tokens · Related work · 0.91
Discussion
Know something about this paper? Leave a comment, or highlight any passage above to comment on it.