> For the complete documentation index, see [llms.txt](https://http3-explained.haxx.se/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://http3-explained.haxx.se/es/why-quic.md).

# Por qué QUIC

QUIC es un nombre, no un acrónimo. Se pronuncia exactamente como la palabra "quick" en inglés.

QUIC es un nuevo protocolo de transporte fiable y seguro que es adecuado para un protocolo como HTTP y que puede solucionar algunas de las deficiencias conocidas de hacer HTTP/2 sobre TCP y TLS. Es el siguiente paso lógico en la evolución del transporte web.

QUIC no se limita a transportar HTTP. El deseo de hacer que la web y los datos en general lleguen más rápido a los usuarios finales es probablemente la mayor razón y el impulso que desencadenó inicialmente la creación de este nuevo protocolo de transporte.

Entonces, ¿por qué crear un nuevo protocolo de transporte y por qué hacerlo sobre UDP?

![QUIC logo](/files/-LvW36QJguX0FR2qaPtX)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://http3-explained.haxx.se/es/why-quic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.