QUIC Address Discovery
draft-seemann-quic-address-discovery-04
| Document | Type |
Replaced Internet-Draft
(quic WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marten Seemann , Christian Huitema | ||
| Last updated | 2025-03-03 (Latest revision 2024-10-11) | ||
| Replaced by | draft-ietf-quic-address-discovery | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-quic-address-discovery | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Unless they have out-of-band knowledge, QUIC endpoints have no information about their network situation. They neither know their external IP address and port, nor do they know if they are directly connected to the internet or if they are behind a NAT. This QUIC extension allows nodes to determine their public IP address and port for any QUIC path.
Authors
Marten Seemann
Christian Huitema
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)