Changes between Version 12 and Version 13 of Ticket #25882, comment 32


Ignore:
Timestamp:
Aug 25, 2018, 2:54:36 PM (11 months ago)
Author:
cypherpunks2
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25882, comment 32

    v12 v13  
    1717
    1818Also, it is not true that the only possible fix is to have the client wait for the end-to-end ACK from the service.  The intro point could deliver two (2) ACK messages, the first being the one that is currently given and the second being the end-to-end ACK that you describe.  After receiving the first ACK, the client could reach out to the rendezvous point optimistically, and then if it does not hear the second ACK (i.e. the one from the service via the intro point) within a particular period of time, then it would mark the intro point as unreachable, toward re-fetching the descriptor for the service.  That is the essence of [comment:20 Proposal A] and ultimately my recommendation for a long-term solution.
     19
     20Also, a small correction to your last sentence: the problem is not that the rendezvous circuit is failing on the service-side, but that the intro circuit is failing.