target = "https://www.rfc-editor.org/rfc/rfc9000#section-9.4"

[[exception]]
quote = '''
On confirming a peer's ownership of its new address, an endpoint MUST
immediately reset the congestion controller and round-trip time
estimator for the new path to initial values (see Appendices A.3 and
B.3 of [QUIC-RECOVERY]) unless the only change in the peer's address
is its port number.
'''
reason = '''
s2n-quic creates a new congestion controller for each path so there
is no need to reset to initial values after path validation.
'''

[[exception]]
quote = '''
Because port-only changes are commonly the
result of NAT rebinding or other middlebox activity, the endpoint MAY
instead retain its congestion control state and round-trip estimate
in those cases instead of reverting to initial values.
'''
reason = '''
We create a new congestion controller for each path. At this time an
unintentional rebind will cause the CC to start from an initial state.
The path is amplification limited anyway, so there will always be a
short drop in performance during a rebind.
'''

[[exception]]
quote = '''
This timer SHOULD be set as described in Section 6.2.1 of
[QUIC-RECOVERY] and MUST NOT be more aggressive.
'''
reason = '''
s2n-quic does not use a timer for re-transmitting the PATH_CHALLENGE.

Instead of using a timer, the PATH_CHALLENGE holds state to transmit
twice in the `on_tranmit` function.
'''