Until we can support connection migration, or at least can validate whether a peer has changed remote address without changing destination connection id (see #316), we should issue a stateless reset when the peer's remote address changes. Currently we will just drop the packets, and the peer will eventually time out.
camshaft
commented
3 months ago
Until we can support connection migration, or at least can validate whether a peer has changed remote address without changing destination connection id (see #316), we should issue a stateless reset when the peer's remote address changes. Currently we will just drop the packets, and the peer will eventually time out.