HTTP/3 为什么基于 QUIC 而非 TCP？它解决了什么问题？
Why is HTTP/3 built on QUIC rather than TCP, and what problem does it solve?
HTTP/3 把传输层从 TCP 换成基于 UDP 的 QUIC，核心动机是消除 TCP 的队头阻塞：在 TCP 中一个丢包会阻塞同一连接上的所有流，而 QUIC 在 UDP 之上实现多路复用，单流丢包不影响其他流。QUIC 还内置加密与 0-RTT 建连，降低延迟。相关标准由 IETF 通过 RFC 9000（QUIC）与 RFC 9114（HTTP/3）发布。
HTTP/3 moves the transport from TCP to the UDP-based QUIC mainly to eliminate TCP head-of-line blocking: in TCP a single lost packet stalls every stream on the connection, whereas QUIC multiplexes streams over UDP so one stream's loss does not block others. QUIC also integrates encryption and 0-RTT connection setup to cut latency. The standards are published by the IETF as RFC 9000 (QUIC) and RFC 9114 (HTTP/3).
难度 专业 · 适合 高中(15-18)
CC BY 4.0 · 已核验 · Verified 2026-11-05
来源 · Source
互联网工程任务组（IETF）,《QUIC: A UDP-Based Multiplexed and Secure Transport》,RFC 9000,2021 (DOI: 10.17487/rfc9000)
IETF, 'QUIC: A UDP-Based Multiplexed and Secure Transport', RFC 9000, 2021, DOI: 10.17487/rfc9000
独立核验依据 · Independent verification: 核验依据 1 Crossref DOI 10.17487/rfc9000; RFC 9000
#HTTP/3 #QUIC #队头阻塞 #IETF
DNS（域名系统）的作用是什么？它通常使用什么传输协议和端口？
What is the role of DNS, and what transport protocol and port does it usually use?
DNS 把人类易记的域名（如 example.com）解析为机器使用的 IP 地址，是互联网的电话簿。普通查询通常使用 UDP 的 53 端口以获得低延迟，而区域传送或响应过大时改用 TCP。DNS 的层次结构由根、顶级域、权威服务器和递归解析器协作完成。其规范由 IETF 的 RFC 1034 与 RFC 1035 定义。
DNS resolves human-friendly domain names (e.g., example.com) into the IP addresses machines use, acting as the Internet's phone book. Ordinary queries usually run over UDP port 53 for low latency, while zone transfers or oversized responses fall back to TCP. Its hierarchical design involves root, top-level, authoritative servers and recursive resolvers working together, and is specified by IETF RFC 1034 and RFC 1035.
难度 进阶 · 适合 小学高段(9-12)
CC BY 4.0 · 已核验 · Verified 2026-11-03
来源 · Source
IETF RFC 1034 / RFC 1035；Kurose & Ross《计算机网络》
IETF RFC 1034 / RFC 1035; Kurose & Ross, Computer Networking
独立核验依据 · Independent verification: 核验依据 1 OPENLIBRARY 标识 /works/OL56272W：Computer networking（首版 19
#DNS #域名解析 #UDP #IETF
TCP 和 UDP 协议的核心区别是什么？
What is the core difference between the TCP and UDP protocols?
TCP 是面向连接、可靠传输的协议，通过三次握手建立连接，并用序号、确认与重传保证数据不丢不乱；UDP 是无连接、不可靠的协议，直接发送数据报、不保证到达或顺序。TCP 适合网页、邮件等要求准确的场景，UDP 适合视频通话、游戏等容忍丢包但追求低延迟的场景。TCP 最初由 RFC 793（1981）定义、现已被 RFC 9293（2022）取代，UDP 由 RFC 768（1980）定义。
TCP is a connection-oriented, reliable protocol that sets up a connection via a three-way handshake and uses sequence numbers, acknowledgments, and retransmission to prevent loss and reordering. UDP is connectionless and unreliable, sending datagrams without guaranteeing arrival or order. TCP suits accuracy-critical uses like web and email, while UDP fits latency-sensitive, loss-tolerant uses like voice/video and games. TCP was originally specified in RFC 793 (1981) and is now superseded by RFC 9293 (2022); UDP is specified in RFC 768 (1980).
难度 进阶 · 适合 初中(12-15)
CC BY 4.0 · 已核验 · Verified 2026-11-02
来源 · Source
IETF RFC 9293（2022，取代 RFC 793）；IETF RFC 768；Kurose & Ross《计算机网络：自顶向下方法》第 3 章
IETF RFC 9293 (2022, obsoletes RFC 793); IETF RFC 768; Kurose & Ross, Computer Networking: A Top-Down Approach, ch. 3
独立核验依据 · Independent verification: 核验依据 1 OPENLIBRARY 标识 /works/OL45032796W：Computer Networking a
#TCP #UDP #可靠传输 #IETF
IPv4 和 IPv6 地址有什么主要区别？
What is the main difference between IPv4 and IPv6 addresses?
IPv4 地址为 32 位，理论上约 43 亿个，已在全球耗尽；IPv6 地址扩展到 128 位，空间大到足以给地球上每粒沙分配地址，用以解决枯竭并简化路由。IPv4 用点分十进制（如 192.168.1.1），IPv6 用冒号分隔的十六进制。二者由 IETF 分别通过 RFC 791 与 RFC 8200 标准化。
An IPv4 address is 32 bits, allowing about 4.3 billion addresses that are now exhausted globally; IPv6 expands to 128 bits, a space large enough to address far more than every grain of sand, solving exhaustion and simplifying routing. IPv4 uses dotted decimal (e.g., 192.168.1.1) while IPv6 uses colon-separated hexadecimal. They are standardized by the IETF in RFC 791 and RFC 8200 respectively.
难度 入门 · 适合 大众
CC BY 4.0 · 来源待核验 · Source pending review
来源 · Source
出处备注：此条未指向带版次的可引用著作（通识性内容、机构文件或未展开的英文书名），本库不提供独立书目出处；如需精确引用，需由编辑补全具体篇目与版次。
IETF RFC 791；IETF RFC 8200
IETF RFC 791; IETF RFC 8200
#IPv4 #IPv6 #地址空间 #IETF