I I want to know if there is a solution to the “disconnection problem”: two peers A and B communicate with each other, it should be an offense for any one of the peers to cut the connection. Is it possible to prove that the disconnection is caused by a specific party of?
Of course, if the two are connected by a direct line, then there is no way to define the responsible party for the loss of the connection. Therefore, we must include some environmental networks and will lose the connection with the third “arbiter” node The party of is defined as disconnection. However, if A wants to disconnect, he can selectively block only the connection with B while maintaining communication with the arbiter.
Is there an encryption solution? , A and B continue to exchange Keepalives through this solution and forward them to the arbitrator to ensure that they can always tell who caused the deliberate disconnection?
Let us say you are in touch
arbiter
/\
/ \
/ \
/ \
/ \
peerA --- peerB
And now one of the peers has cut off the peerA-peerB link.
All possible situations may exist before disconnection. (Send data To B, or B received or B->A or third.)
Since there are no more A-<-> B links you cannot tell who is disconnected. Both parties can claim
p>
a) They sent the last packet
b) They did not receive the package
The point is that when the A<->B link disappears, you can’t tell who broke it, because It may even be an intermediate third party.
A practical solution made me think that once this happens, you will reroute all traffic from the arbiter, which now acts as a proxy. During this period, both parties will send the tracking path to each other and send the results to the arbiter. Even if this fails and the scammer implements forged ICMP packets, this cheating method will not work, and they will abandon this cheating method sooner or later. At the worst In this case, you will have to reroute some traffic and act as a router, but you may be able to track the cheaters statistically and take appropriate action against them.
This is more like It is an encryption/algorithm rather than a programming problem, so if this is not suitable, please feel free to tell me to go elsewhere.
I want to know if there is a solution to the “disconnect problem”: Two peers A and B communicate with each other. It should be an offense for any peer to cut the connection. Is it possible to prove that the disconnection is caused by a specific party?
Of course, if the two are connected by a direct line, then there is no way to define the responsible party for the loss of the connection. Therefore, we must include some environmental networks and will lose the connection with the third “arbiter” node The party of is defined as disconnection. However, if A wants to disconnect, he can selectively block only the connection with B while maintaining communication with the arbiter.
Is there an encryption solution? , A and B continue to exchange Keepalives through this solution and forward them to the arbitrator to ensure that they can always tell who caused the deliberate disconnection?
I think such an agreement is impossible.
Let us say you are in touch
arbiter
/\
/ \
/ \
/ \
/ \
peerA --- peerBAnd now one of the peers has cut off the peerA-peerB link.
There may be all possible situations before the disconnection. (Send data to B, or B receives or B-> A Or third.)
Since there are no more A-<-> B links you cannot tell who is disconnected. Both parties can claim
a) They sent the last data Package
b) They did not receive the packageThe point is that when the A<->B link disappears, you can't tell who broke it, because it may even be a third party in between.
A practical solution made me think that once this happens, you will reroute all traffic from the arbiter, and the arbiter now acts as a proxy. During this period, both parties will send tracking paths to each other and The result is sent to the arbiter. Even if this fails and the scammer implements forged ICMP packets, this cheating method will not work, and sooner or later they will abandon this cheating method. In the worst case, you will have to reroute some traffic and Acting as a router, but you may be able to track the cheaters statistically and take appropriate action against them.