From: Ian Jackson Date: Wed, 15 May 2019 21:42:10 +0000 (+0100) Subject: polypath asymmetric routing: Priority to mobile sites X-Git-Tag: v0.4.4~14 X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~mdw/git/secnet/commitdiff_plain/b2de6bd2d9b5e9047a660e926c4adb17da54fc29?hp=b2de6bd2d9b5e9047a660e926c4adb17da54fc29 polypath asymmetric routing: Priority to mobile sites It is better for the mobile peer to win the key setup priority battle. That makes handling the transport address implications, particularly those of the MSG1, easier. Since both ends must agree on who has priority, this must be negotiated. We use a capability bit for this. Since the decision is taken when we have only seen each other's MSG1, it must be an early capability. For compatibility with ancient (and security-buggy) secnets, we can avoid advertising it if neither end is mobile. In practice, in my tests, this change avoids a spurious key setup failure when my laptop's secnet is restarted: the new secnet gets a new NATted address, but the server has priority and insists on talking to the old address. Signed-off-by: Ian Jackson --- v2: Document in NOTES following rebase over "NOTES: Describe the current allocation of capability bits." ---