agent: verify the best nominated pair after priorities recalculation
When we get a set_remote_candidate late after the start of the conncheck, some remote candidates type may change from peer-reflexive to server-reflexive. This required a recalculation of the foundations and of the priorities of the related pairs. This recalculation may change the pairs ordering in the conncheck list: a srflx:prflx pair becoming a srflx:srflx pair will have a lower priority (RFC 8445, section 5.1.2.1 "Recommended Formula", "the type preference for peer-reflexive candidates MUST be higher than that of server-reflexive candidates.") This recalculation is required to maintain the same pairs ordering in both agent. But in some cases, in aggressive nomination mode, this may also change the selected pair, if this recalculation changed the highest priority pair with the nominated flag.
Showing
Please register or sign in to comment