If an endpoint needs to know its public IP address and port, I suppose it needs to know when it changes. Would not it be better to have endpoints automatically send NEW_OBSERVED_ADDRESS frames at the beginning of the connection and when they detect an IP address or port change instead of relying on the request/response semantics in the proposal?
-Igor From: QUIC <[email protected]> On Behalf Of Marten Seemann Sent: Thursday, October 19, 2023 6:20 AM To: QUIC WG <[email protected]> Subject: QUIC Address Discovery I just published an I-D that defines a mechanism for QUIC endpoints to discover their (public) IP address and helps them determine their position in the network (e.g. if they're behind a NAT): https://datatracker.ietf.org/doc/draft-seemann-quic-address-discovery/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-seemann-quic-address-discovery/__;!!GjvTz_vk!QoSZ25mYlBnrg59ziKYDPS_Bz72TQQMlK5_SFFEV5OYWItpP1DRqlfc6c2QCY9LIeyWPWkL_myuholwN48_gig$> This is especially helpful for QUIC nodes running in a p2p setting. A similar result could be achieved by using STUN on the same UDP socket, but there are several advantages of doing it inside of QUIC. See the draft for details.
